Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
I don't know that CWM was ever fixed to work properly on this device, which means that, combined with trying to flash firmware with a low battery could be bad news.
Leave it on a charger all day, and then come back to it and see if it turns on.
leeoniya said:
Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
Click to expand...
Click to collapse
Did you ever get this working? I've got the same symptoms with my phone. Appears to be off and wont turn on but when plugged into the pc, the pc detects it.
Related
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Has anyone experienced this or am I the only one?
M5devil said:
Has anyone experienced this or am I the only one?
Click to expand...
Click to collapse
Sorry I have never heard of this or witnessed it while flashing anything to my device. Obviously the battery screen signifies that the phone is off but is in charging mode and hitting the power button will boot the device up. (I'm sure you already know of this). Never heard of it being stuck at that screen after flashing. Hopefully you can get this solved soon. Good luck
M5devil said:
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Click to expand...
Click to collapse
Slow down for a second. Your phone is definitely not bricked. Ive been over the edge, and been able to bring my phone back to life.
To clarify, you flashed vibrant6.zip through clockwork mod, and then the phone got stuck on the samsung S? How long did you let it sit there?
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
I flashed the stock ROM via Odin and then wanted to install Vibrant6.zip. For that I entered into a recovery mode via Clockwork and as someone in the other thread advised, I formatted system and also data, don't recall exactly. Then it looped to a standard recovery mode and I just rebooted the phone. This is where it got stuck... Vibrant in the center and Samsung at the bottom of the screen. To test it I left it like that from night till this morning. In the morning I woke up it was on the same boot screen.
Before that at night, after seeing it hand at the boot, I held both volume keys and power, waited for it to reboot, and immediately it showed a circular progress bar, but not moving just highlighted the 12 o'clock bar and second later I see the battery image all in gray and nothing else. It just sits on that grey static image without actually charging it (no green section or flashing dots)
Boot logo only appears if I am trying to reset without the USB cable. On the boot loop I plug in the cable and I hear the USB connecting it, I see the 2 Removable disks, but both inaccessible and adb commands don't recognize the device.
Very weird, as in turned off mode it's not charging at all.. just shows this grey battery image with a circle progress froze on 12 o'clock bar.
That's pretty much it.... I was never able to enter into recovery nor download via the buttons. It would just always reboot into this grey battery screen....
Completely helpless.... I did order a new battery from TMO, maybe the battery is fried and that's why it's not charging and just sits on this stupid static grey battery screen.
ArbitrageMan said:
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
Click to expand...
Click to collapse
Holding both volume keys and releasing power once screen goes blank, only show Vibrant logo again... I have tried this a million times
With USB cable it shows grey battery screen, without the cable just a Vibrant boot loop...
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
zephiK said:
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
Click to expand...
Click to collapse
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
M5devil said:
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
Click to expand...
Click to collapse
Are you sure that you're doing the right things to get to download? I've been in this situation and I wasn't able to get into recovery but I was able to get back into download mode.
I believe if you return it back and they find out it was rooted, they will charge you for it. If not, it'll appear on your bill.
I'm sure that you're doing the wrong things to get into download mode. If something is appearing on your screen it is a soft-brick and you're not bricked.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (powers on its own when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
Click to expand...
Click to collapse
A tip to get into download mode is to put the phone HORIZONTALLY (sideways) and it will make it a lot easier.
I am pretty much positive about it. I know a lot of people can easily enter into recovery or download modes, but I know many can't and I am one of them. It would just load the grey battery image instantly as I let go of the power button.
1. Take out battery, put it back in. (to turn the phone fully off) DONE
2. Don't turn it the phone on! DONE
3. Plug the phone into your PC, do not hit the power button! DONE
4. See if the phone shows anything on the screen (powers on its own when plugged in) FIRST THING THAT APPEARS IS A CIRCULAR PROGRESS BAR THAT CHANGES TO A GREY BATTERY IMAGE WITH A BAR IN THE MIDDLE OF IT. STATIC IMAGE, NOTHING ELSE.
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons. DONE
6. Hold the power button as well as the volume buttons until the screen goes black. DONE
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons! DONE
THE STUPID GREY COLOR BATTERY IMAGE APPEARS AS BEFORE....
I'm thinking maybe battery is fried and that's why the grey color screen appears and not the usual screen where you see the battery charging...
After reading this thread it's clear that my handset is one of the new ones that have recovery/download modes disabled via the volume+power buttons.
So that pretty much covers it... I hope TMO will not ***** about the files that are on the internal sd that I am unable to access and remove... unless anyone else has any fresh ideals how to gain access to the disk
I think I might have a similar problem.
I accidentally deleted the touchwiz framework so I can't do anything ON the phone. It boots up, and gets me to the lock screen. As soon as I unlock, I am greeted with dozens of unending force closes.
I can get into both download and recovery mode, however, I have not been able to get ADB to recognize the device. I am attempting to push the stock ROM to the internal memory to flash over everything.
I'm not sure what to do to get ADB to work but it's driving me nuts!
Stuck at vibrant? I have a fix
Check out android Dev Section... I figured out how to access download mode or stock recovery mode when you are stuck at the vibrant screen!!!! BACK IN BUSINESS VIBRANT OWNERS!!!
i got the same problem and nothing seems to work
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
eduardo_reflex said:
i got the same problem and nothing seems to work
Click to expand...
Click to collapse
... do i even have to say it?
droyd666 said:
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Click to expand...
Click to collapse
this problem is most likely solved. After 2 years!
mylostlonelysoul said:
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
Click to expand...
Click to collapse
Try asking another question. But I suggest using a USB jig. They usually work. Then odin
Sent from Mount Olympus via Hermes
Did you ever get it fixed man? I literally did the very same to mine a while back and It works like butter as we speak. It is fixable with a mini-usb jig or dongle. You can make your own with about $3 worth of parts from radio shack but I recommend buying one, it will be easier. I for the record made mine simply twisting together the resistors and though it was tough to touch the right pins it did eventually work and get me back into download mode.
Hopefully you already got it fixed though. If not I can help you out.
Hello, my nephew rooted his fascinate and then got it locked up where it could only get to the Samsung screen (said he tried installing some lockscreen app) - he tried odin with no luck (the yellow triangle WAS working), now when attempting odin again (was going to try the unbricking procedures) the download screen (Yellow triangle) does not come up, nor can he get into recovery (stock recovery, he never loaded CWR). The only thing that happens is the lights light up on the softkeys, but the screen stays dark. Even with a fresh battery (his mom also has a fascinate) the same thing occurs, even while plugged into the wall charger. Any ideas?
take a deep breath
after you plug your phone into the computer sometimes it takes a minute before you can get into download mode make sure your hitting the volume down key and power button with the battery out, as long as you can get into download mode you should be fine just follow the directions found here http://forum.xda-developers.com/showthread.php?t=1026746:) hope it helps
Yep, the easiest way to get to download mode is to pull the battery out hold volume down and plug it into the pc... I prefer to odin with battery out, as it lets me fully control a reboot timing.
I have had many a time that the pc would not recognize the phone, but a quick reinstall of the drivers (pc to samsung drivers that is) corrects that issue...
GL! You'll get there, from what I read this phone is very tough to totally brick. The unbrick steps are exactly what you need, but of course you need odin to see the phone to do that...
Swyped...
Hi All,
So, I tried to flash Cyanogen mod last night using the instructions here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide. I was coming from a BIONIX ROM that flashed fine.
Anyways, the phone went into a reboot loop in the recovery screen and I foolishly just held the power button until it stopped. When I turned it back on it was broken. That is, now all it does is display the white Vibrant logo in the middle of the screen with the smaller Samsung logo below it. If I hold the power button for about 8 seconds the screen goes black for about 2 seconds and then comes right back up to where it was. I can't seem to even turn the phone off any more. It just stays on that screen permanently unless I hold the power button, in which case the screen is off for 2 out of every 10 seconds. Yanking the battery of course turns it off, but putting it back in immediately returns it to the state I've described.
I've scoured these forums and tried every button press + battery state + cable state + SD card/SIM state combo suggested, but the phone won't go to download or recovery mode. I found one thread describing the exact same problem. The OP said he'd try a jig and then disappeared without any further updates. I'm going to try to get my friend to make a jig using one of these sets of instructions
http://forum.xda-developers.com/showthread.php?t=819551
http://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
but until then my questions is: does anyone have any experience with this problem (can't even turn the phone off)? If so, do you have any recommendations? Did a Jig work?
keep trying to get to download mode, pull battery, plug usb in to computer and to the phone, while holding both volume up and volume down pop in the battery. People have tried hundreds of times with it not working and then all of a sudden *bam* download mode.
So... my friend made me a jig and it works in that I can see the shoveling droid indicating download mode. However Heimdall/Odin won't recognize my phone. Heimdall's zadig utility won't locate the phone either, even with the cable plugged in. I'm, once again, stumped.
Just an update; I've tried Odin on three different computers, two Windows 7 (64 bit) and a Mac (with Heimdall). None of them seem to recognize the phone. Device manager on the Windows 7 machine does not update when I plug the phone in (in Download mode via the jig or not) and I can't find anything about Samsung in it anywhere. However I have installed the Samsung drivers; a few different sets I've found around the forums. I've also tried a couple utilities like the Vibrant toolbox and one click unbrick. Nothing seems to have any effect. I was so hopeful when the jig worked and got me to download mode, but now it's seeming I'm actually bricked. Has anyone seen a phone that could get to download mode but still be bricked? Oh, and I checked the cable using a friend's phone; her Mac recognized her phone using the cable. Haven't tried her phone on my Window's machines though.
Once again, any help is more than appreciated.
Have you tried to see if adb is working? If it does then try adb reboot recovery? If it works there is a file I can post for you later (is in my pc) that can restore your sbl.bin and fix your download mode problems.
Thanks for your help everyone, the problem was apparently resolved by a new cable; which is strange because the old one works for data transfers... just not for flashing apaprently. :S
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
If you can get into hboot you arn't bricked.. Tho you usb port may be dicked like a broken part..
I would try to go stock for the hell of it.. I haven't had any issues.. I have in the past hung my phone locked it and dicked sense up.. But a battery pull always helped get back into hboot
So I wonder what is going on with yours.
Have you tried using a different usb cable ?? Or pluggin the phone in and let it charge over night ??
#Root-Hack_Mod*Always\
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
youre not bricked... you get into hboot fine... its running that you have a problem with so we go tier up...the eMMC of it all...there is a post by unknownforce that is for downgrading hboot 1.5 to .14 or less but follow those directions to the T and it willrewrite everything in there and then if you choose to do so you caqn update to hboot 1.5 and the new RUU and all from there
Can't get into hboot anymore.
can't get into hboot anymore, and if I'm s-off I can't run the process.
thermbug said:
can't get into hboot anymore, and if I'm s-off I can't run the process.
Click to expand...
Click to collapse
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
w0rdOo said:
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
Click to expand...
Click to collapse
A slight wiggle is alright. If your led light is coming on and off then somethin is broke.
Sent from my PG86100 using xda premium
Try taking the battery out for a few hours and letting the phone rest. This worked somehow for a few users.
Hello friends, I come to report here a problem I'm having with my device.
It is not charging my battery, I thought it was a problem in the battery itself, I made the replacement for an original, but the problem was not solved. the device uses all the battery power, it stays at 0% and it does not charge, besides, it recognizes my SIM card, but there is no signal from the operator to make calls or use the 4G network, I did a lot of research I saw that it was a problem related to Software, regarding the CQA test, I saw several tutorials, where none succeeded, lastly, I would like to install a custom rom to see if the problem would be solved, but I went to do the bootloader unlock process, but when Fastboot displays the code and I enter the site of the motorola, it returns me with an error that I can not unlock the bootloader of my cell phone, and I need to unlock to be able to customize the android.
follows a video showing what is happening with my device.
https://www.youtube.com/watch?v=17roum_XlzQ
sorry if my text contains errors, I'm from Brazil and I used the translator to write
Thank you if anyone can help me because I have the device stopped because of this.
Thank you!
Hi, had the same issue. What helped me was connecting
power cable, going to bootloader, from there navigate to recovery. When it boots to recovery, regardless if there is any, leave it for some time. After about 5-10 minutes try rebooting, and it might picked up some charge, then it should charge as normally but very slowly, cellular connection also appeared.
Last time when my phone went to 0% and after going through this procedure my phone was at 17% after charging in recovery mode but didn't charge in normal mode after reboot. I also needed to toggle some setting regarding CQA in bootloader menu. Then everything went back to normal.
I will do this procedure to see if it solves my problem, remembering that my battery is in 0% and with it connected in the device it is only displaying the lightning, informing that the battery is without load.
what settings did you make regarding the CQA?
vNo said:
Hi, had the same issue. What helped me was connecting
power cable, going to bootloader, from there navigate to recovery. When it boots to recovery, regardless if there is any, leave it for some time. After about 5-10 minutes try rebooting, and it might picked up some charge, then it should charge as normally but very slowly, cellular connection also appeared.
Last time when my phone went to 0% and after going through this procedure my phone was at 17% after charging in recovery mode but didn't charge in normal mode after reboot. I also needed to toggle some setting regarding CQA in bootloader menu. Then everything went back to normal.
Click to expand...
Click to collapse
My device does not hold 5 seconds on bootloader because my battery is at 0% I believe the power supplied by the cable in the charger is not enough to keep it powered on. and now?
Original charger is definitely more than enough to keep phone on in bootloader mode. Try to make sure that usb C connection is dust and grease free.
Regarding CQA mode setting I can't remember exactly, but that is second thing.
Maybe even 5 seconds in bootloader should be just fine to navigate to recovery.
I wish you good luck, i was almost desperate when it firstly happened to me.
i had the same problem. after lot of trial and error i found a solution.
connect to power source (wall adaptor/modo battery mod.) get into bootloader menu and wait for 5 mins pressing vol up or down frequently.
then select reboot to recovery. on red triangle screen holding power button press and release volume up button one time. you will get into android stock recovery
select option wipe cache partition. and select yes when asked.
keep charging the device upto half hour in recovery mode and then select option reboot to bootloader.
after bootloader menu appears scroll down to BPTools and select it.
Your Phone will reboot and you will get Network and Your Phone will also charge normally.
Warning: Do not let your phone discharge to 0% or you might have to perform all above steps again.
This method worked for me as well. I recently replaced the battery on my Moto z force droid but couldn't get it to charge and signal was gone, after trying several things the Bp tools worked great, thanks dude.