Related
Hey guys,
Running ILWT CM7. Flashed about two weeks ago. My phone has been working fine except for the past few days where it's been constantly freezing, requiring a battery-out and turn on, and rebooting on it's own.
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. After ~25minutes, I took the battery out and tried again.
Phone seems completely dead, won't respond to power on, volume down and power on, no lights come on when charger cable is plugged in. When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
Tried leaving battery out for 30minutes and trying again, but no luck.
Any suggestions?
Cheers!
Stuck in RUU mode?
Kaph said:
Hey guys,
...
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. ...
Phone seems completely dead ... When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
... Any suggestions?
Cheers!
Click to expand...
Click to collapse
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
catherall said:
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
Click to expand...
Click to collapse
Thanks for the help
When plugged in with the USB cable -> computer, I still get no response from the phone itself. Screen doesn't turn on, still seems dead. My laptop still says "Installing device driver software" to no avail, and phone is still dead. No lights, screen is off, nada. As though it was powered-off.
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Remarks
Kaph said:
Thanks for the help
My laptop still says "Installing device driver software" to no avail, and phone is still dead
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Click to expand...
Click to collapse
Windows seems to need a driver installation for using fastboot. Did you try to automaticall install device driver software? Have you installed HTC sync on your Windows computer?
When your device does not respond at all, and even refuses to connect in fastboot, then nobody can tell that you have been rooted.
Best regards,
Catherall
Sounds like your EMMC is fried, as of now I don't think there's a solution other than sending it back. Many say HTC accept and fix it even though it is s-off
Sent from my HTC Vision using XDA
did you get this worked out? i had a similar problem, ended up booting into fastboot by holding the trackpad and the power button, then just selected reboot and my phone powered on like nothing had happened, i was running the same rom.
Hey, did you alreasy tourned your phone to the fastboot mode?
Or does your device still have a black screen during boot?
I rooted this phone and when I was done trying S-OFF, phone would not respond to anything. It would only blink the orange notification light when I pressed Power and Vol+, or it would stay steady green with both Vol keys and Power. But the phone screen would never turn on. So after trying for hours to figure it out. I finally took the battery off, plugged the phone held pressed the power button and then put the battery in place the phone finally turned on and it worked. I turned the phone off again and it was doing the same issue. So I did the same step but this time with power and vol- to get in the bootloader and changed the hboot version to Desire Z. After that phone works perfectly, turns on and off with out any issues.
I did have to try the trick a couple of times idk why but it would work once in a while not everytime i tried it. Hope this helps anyone who also ends up with a similar issue.
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
azeem.droid said:
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
Click to expand...
Click to collapse
The question is what did you do to the Verizon "unlocked bootlader" phone to get you to this point?
Hello everyone,
a friend of mine is having problem with his M9. He recently downloaded an update to the phone, but after restart the phone no longer boots, says 0% battery and would not charge (just keeps heating). After a while on the charger it tries to boot (white screen with HTC logo), but after like 20 seconds it reboots.
I can make it enter the "service menu" (or how is it called) - white screen saying "Software status - modified, LOCKED, S-ON" and some menu items (I would post a picture but the forum won't let me because I am new...)
the problem is that Recovery mode does not work, there is just black HTC logo in infinite reboot loop. Reboot to bootloader just reboots to the same menu. The download mode basically says "Failed to boot to download mode. This build is for development purposes only..."
If I plug the phone to PC, while the menu is present, I hear a sound that is was plugged to PC, but a second later it's unplugged, so I was unsuccessful trying to make some sense to it using ADB.
Can the phone be saved? Thanks for help
Whats annoying is that the phone keeps rebooting until it runs out of battery power, I haven't found a way to prevent it from rebooting. So-called "smartphone"...
I tried to update the firmware using RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe, but it said I don't have sufficient battery charge. So I plan to use the Fastboot-battery-recharge.bat overnight to give it a charge.
The problem however is that the command
Code:
fastboot getvar battery-voltage
returns "battery-voltage: " without the voltage itself. Anyone experienced this? I am using the latest minimal ADB and fastboot (1.4.3)
BTW the phone is originally EE UK.
Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you
same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.
If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?
The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
wenyendev said:
Is it still possible to back up all your data at this point?
Have you tried adb pull your userdata partition?
Click to expand...
Click to collapse
They can’t boot….adb only works when booting or booted, and if it bootloops, they won’t have time to pull their data.
afresh said:
Hello there,
Last Tuesday (January the 17th), my Note 8 Pro rebooted while I was typing on it, and since then, it just bootloops.
I see the "Redmi" logo for 5 secondes, then the screen goes dark, the smartphone vibrates and here we go again.
Even Fastboot mode is not working: I can get access to the mode, but it only last for about 10 seconds, then blackscreen, vibration, Redmi logo.
No matter what I do (even this tutorial to unlock the Booloader by MTKClient), the smartphone keeps rebooting.
I'm desperate, since this device holds too many unsaved memories and my 2FA authentication app...
I even tried to change the battery (I've read that a dead battery, with not enough power, could lead to such behavoir), but no luck...
Another fact: when I have the phone connected on my laptop, all of my USB devices are disconnected for 1-2 seconds at each reboot.
Any help is very welcome
Click to expand...
Click to collapse
Bootloader locked or unlocked?
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Unfortunately, USB debugging was not enabled. I stopped developing for Android quite a while back now, and I don't turn on USB debugging anymore.
@Arealhooman My bootloader is locked... I tried unlocking it with MTKClient, but no success since the phone reboots during the process.
wenyendev said:
Hope it helps.
https://forum.xda-developers.com/t/bootloop-on-mi4w.3558835/
Click to expand...
Click to collapse
This helped a lot actually!
It seems that the power button got faulty and got constantly pressed, making the phone constantly hard-rebooting itself.
I have a piece of paper preventing the buttons from contacting the motherboard, and the phone stopped rebooting when charging!
Ingenious method. Glad you solved the issue.
I enabled USB debugging to be able to reboot into fastboot / bootloader without the buttons (since my piece or paper prevents all the button from working xD)
wenyendev said:
Even if you cannot boot into system, but if
- USB debugging is enabled, and operational;
- a cable works;
- you can boot into recovery.
Adb shall work in recovery.
Click to expand...
Click to collapse
Only custom. Stock doesn’t support it.
Bro first check if your power button is working fine, if it is being pressed by any hardware issue it can happen, and when you fastboot try flashing recovery within that time fastboot remains.