My Fuze was running PROven ROM 2.2 and various others before that fine, Hard-SPL and everything done correctly.
Now the device will not turn on with the power button, however i CAN get to the BootLoader and the HardReset Screen, i've tried hard-resseting and re-flashing with multiple roms- they say its succeful and then i still CAN'T power on
please anyone help if you can, thanks in advance
try flashing the stock rom
tried that..
i did, both the SD card and the USB method- no luck :/
says flash was successful- still won't boot up...
remove the sd card then try restarting it
i've tried that also, no luck
Plug in your phone via USB to your computer and boot into the tricolored bootloader screen without your SD Card. It should say USB at the bottom.
Download and run stock AT&T ROM (Assuming you have an AT&T branded phone since you said Fuze): http://rapidshare.com/files/157242627/RUU_Raphael_Cingular_US_.exe
This should install your original shipped package.
Now if you still get a black screen, at this point, remove your SIM Card and reset your phone.
nothing
thanks for the link, tried it, yet again, no luck.....
is the back light on but the screen is black or does the phone look completely dead with no back light? Plug in your AC adapter and see if the light fades in and out to indicate charging.
I know this might sound retarded but have you tried pressing the reset button on the bottom of your phone?
I'm sure you tried so try this step. Pull out the battery and let the phone sit there for a good 2 minutes then try reflashing to your stock ROM.
If you still have a black screen, pull out the battery again for another 2 minutes, put it back in but this time plug in your phone using the AC adapter and just charge the phone for a few minutes then try turning your phone on.
thanks
thanks variablex, however i cannot try your last step because i had already given up and used my warranty by the time you posted it, i will be receiving a new fuze in the mail soon - would've rather not used it yet and tried more steps but now its too late :-\
thanks anyways though
Phone wont turn on no download mode, no recovery mode, nothing....when i plug it in to the charger it vibrates and shows the battery icon but thats it
mcooper113084 said:
Phone wont turn on no download mode, no recovery mode, nothing....when i plug it in to the charger it vibrates and shows the battery icon but thats it
Click to expand...
Click to collapse
If you do a battery pull then plug it into the charger then put battery back does the notification led go red?
yes....
that happened to em and from what i read on the forums there's nothing you can do but replace it. Verizon wont know its rooted since it wont even turn on.
^this. verizon cant deny a new phone if they check if its rooted.
fr8cture said:
If you do a battery pull then plug it into the charger then put battery back does the notification led go red?
Click to expand...
Click to collapse
This happened to me.. all I had to do was leave the phone on the charger for fifteen minutes and it worked. Same thing happened to some guys with the T-Mobile version and that's how they solved it.
Sent from my SGH-T999
joshnichols189 said:
This happened to me.. all I had to do was leave the phone on the charger for fifteen minutes and it worked. Same thing happened to some guys with the T-Mobile version and that's how they solved it.
Sent from my SGH-T999
Click to expand...
Click to collapse
Didn't work for me. I had it on the charger overnight.
mcooper113084 said:
Phone wont turn on no download mode, no recovery mode, nothing....when i plug it in to the charger it vibrates and shows the battery icon but thats it
Click to expand...
Click to collapse
This happened to me. My phone had been rooted and I had pushed some apps to the system, but I had not used any custom roms or kernels at all. After my small modifications my phone worked for a month or so. Out of the blue while using navigation, it died and would no longer turn on. It would boot into recovery or download mode only when on the charger. If I left it on the charger for a long period then it would boot to the homescreen sometimes but then turn off very quickly. I tried all I could through odin to fix it. Since I could boot to the homescreen sometimes, I could see that odin had returned my phone to stock and my flash counter was still at 0. Still would never boot into any mode when off the charger. I had to return to verizon for a refurb as I believe it is a hardware issue imo.
elreydenj said:
This happened to me. My phone had been rooted and I had pushed some apps to the system, but I had not used any custom roms or kernels at all. After my small modifications my phone worked for a month or so. Out of the blue while using navigation, it died and would no longer turn on. It would boot into recovery or download mode only when on the charger. If I left it on the charger for a long period then it would boot to the homescreen sometimes but then turn off very quickly. I tried all I could through odin to fix it. Since I could boot to the homescreen sometimes, I could see that odin had returned my phone to stock and my flash counter was still at 0. Still would never boot into any mode when off the charger. I had to return to verizon for a refurb as I believe it is a hardware issue imo.
Click to expand...
Click to collapse
sounds like a bad battery.
mcooper113084 said:
Phone wont turn on no download mode, no recovery mode, nothing....when i plug it in to the charger it vibrates and shows the battery icon but thats it
Click to expand...
Click to collapse
** UPDATE** I dont know how but i managed to get my phone into download mode by holding only vol down and home while plugged into computer. I was able to odin back to stock using *how to unbrick a soft brick* yaaayyyyyy!!!!! i got my phone back...now to re-root but this time i wont wipe internal sd card..lol
It wont let me post link to form....but hope this might help anyone else with what i would like to call a medium brick like mine
SO if your notification light comes on (red) when battery is out and plugged into computer try holding ONLY vol down and home to get into download mode...it worked for mine
Hello, a friend of mine got a nexus s and the phone is working well while its connected to the charger or to PC, but when I unplug it everything lags. I can't do anything on the phone, nothing responses. If I plug it again, it runs as it should. I managed to unlock it and install CM11, but absolutely the same result. The bootloader launches well even while not connected, recovery starts too but its very laggy. If I try to start it normal, the nexus starts in the download mode(yellow android with a shovel). How do you think, the battery does not have enough power to maintain the OS, but it can start the bootloader and the recovery because they need less power? I tried charging it whole night, even charged it with nexus 7 charger which is bigger, but the same. Also, when connected and in recovery, the battery shows 75+ and if I unplug it it goes to 3-6+, could it be software issue and can I test it somehow...
Get back to stock. Put a Custom ROM again. Also, try a different battery. Let's see what the results are.
smit.sanghavi said:
Get back to stock. Put a Custom ROM again. Also, try a different battery. Let's see what the results are.
Click to expand...
Click to collapse
Tried another battery, the same result, which makes me think that the problem isn't the battery. Also, flashed stock GB bootloader, radio, system, user data and then the phone rebooted well. Removed the cable and its working well, except the front camera which I found not working. Then I turned the phone off and the power button does nothing, i can only enter in bootloader and reboot from there. Another thing I noticed, if I remove the battery and insert it again, no matter what I do (normal, or power+volume up) the phone boots in download mode when the bootloader is unlocked, and if its locked the phone boots only into the unlock- bootloader screen which is unresponsive. However, if its plugged in, it boots normaly and then works ok even when unplugged... Really cant find a solution
P.S. this is only with gb, i installed cm11 later and cant use it without cable, just like in the beginning...
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
The Stig 04 said:
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
Click to expand...
Click to collapse
I would love to go back to stock if I could get the device to turn on.
This was the first SuperSU update that I can remember having installed, so yes, I've always installed through recovery. The update even prompted me that, for HTC devices, better luck is had via updates through recovery.
dottat said:
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
Click to expand...
Click to collapse
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
devmage said:
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
Click to expand...
Click to collapse
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
devmage said:
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
Click to expand...
Click to collapse
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
dottat said:
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
Click to expand...
Click to collapse
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
devmage said:
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
Click to expand...
Click to collapse
I would suggest warranty route through HTC. You have got a brick.
dottat said:
I would suggest warranty route through HTC. You have got a brick.
Click to expand...
Click to collapse
That is my fear. Thank you for your help.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
Thanks TIA for any help!
Matt
Click to expand...
Click to collapse
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Thanks for the info...I appreciate the response. I'm hoping that there's something that can be done but after 2 hours, trying every trick I could find via
Google with nothing to show for it, I'm keeping fingers crossed that it's something simple I'm missing. If I could just get into the dang bootloader!
Thanks again!
Sent from my SM-P600 using XDA Free mobile app
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
Click to expand...
Click to collapse
To add to this, I've let the phone sit for about an hour, untouched, and now the green light is blinking like it does when there's a SMS/email. Pushing the power button doesn't do anything.
devmage said:
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Click to expand...
Click to collapse
For what it's worth for anyone that finds this info useful...can't take credit for this as I found it over in the One M8 forum. Thanks to @mpogr
I quote his post: "The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot."
I held Power/Vol Up for 10 seconds (as he described) and then let go and immediately held Vol Down only...after about 3 seconds, bootloader screen came up and I was able to get into recovery and restore a backup.
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Cloud2F said:
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Click to expand...
Click to collapse
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
cooltt said:
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
Click to expand...
Click to collapse
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Cloud2F said:
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Click to expand...
Click to collapse
the way to test if it has power but blank screen is to hold power+volume down+home. If it has power it will turn off and boot into download mode
After the Forst Crash all such combinations didnt Seen to work either. Once odin recognized is while having a black screen. At that point I flashed stock :/ but still, not even the led was showing something