So I have a weird bootloop issue. I am running 4.4.4 firmware, with GPE 5.0, s-off, unlocked.
The phone gets hung on the android boot screen (where the little dots circle around). I can restart the phone, and get it into the recovery screen with power and vol down. However, once there, the phone automatically tosses me into HBOOT where my only option is to update the HBOOT or cancel the update. Either way I go, it asks to restart the phone, and I am right back where i started. I cannot for the life of me figure out how to get out of this.
Thanks for the help in advance.
DrMurawski said:
So I have a weird bootloop issue. I am running 4.4.4 firmware, with GPE 5.0, s-off, unlocked.
The phone gets hung on the android boot screen (where the little dots circle around). I can restart the phone, and get it into the recovery screen with power and vol down. However, once there, the phone automatically tosses me into HBOOT where my only option is to update the HBOOT or cancel the update. Either way I go, it asks to restart the phone, and I am right back where i started. I cannot for the life of me figure out how to get out of this.
Thanks for the help in advance.
Click to expand...
Click to collapse
Pull your sd card and you will be able to enter recovery.
Related
In December of last year, I had my friend root and install CyanogenMod onto my Mytouch 3G Slide. Everything was working fine until I wanted to update my ROM and tried to boot my phone into recovery mode to make a NANDroid backup. A screen with a picture of a phone and a red exclamation point inside a triangle would appear, and I'd have to pull the battery out to restart the phone.
Then, I tried to access the bootloader by holding the volume down and power buttons. After some loading, it asked me if I wanted to update. Not knowing what it was asking, I said no, and tried to access the actual recovery menu, but the same screen showed up.
I tried again, this time accepting the update. Now, when my phone boots, the stock mytouch splash screen appears and the phone does nothing from there.
At this point, what would be the best solution? Is my phone just bricked, or is there a way to restore it to the stock firmware/recover CyanogenMod?
EDIT: For clarification, I can still access the bootloader, where I have four options: Fastboot, Recovery (See problem above), Clear Storage, and Simlock.
EDIT 2: I left it on the splash screen and discovered that it seems to have just thrown my phone into a stock factory state, running 2.1-update 1. Not sure if it's still rooted.
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
I was having terrible GPS reception and I tried the antenna fix- sliding a tiny peace of thick paper under the antenna connectors:
https://www.youtube.com/watch?v=K1-uCIb-t8I
After powering up the phone booted once, then rebooted after couple of seconds and has been bootlooping on Google logo since.
- Takes much more time than normally to power on, then falls into Google logo bootloop,
- Cannot go into bootloader, power + vol buttond doesn't do a thing,
- If I hold vol up + vol down while bootlooping it powers off,
- Plugging in doesn't change anything, no charging indicator when powered off.
Is there anything I can do ?
Did I kill my phone ? If so, how ? What could I have damaged by simply prying the cover open ?
Are all the connections secure?
I checked all the connectors, they're ok.
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Heniuro said:
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Click to expand...
Click to collapse
Might need to wait for 5.1
5.0 is buggy
I was trying to update my recovery, TWRP 2.7 or something, to the newest version through the TWRP Manager app and I did that, or so I thought, and rebooted the device. Now it gets to the white screen where it says rebooting recovery in pink text but nothing happens, reboot it, same thing. I can tell that it is in recovery because I can feel the vibrations of the buttons when I press them, like the home and back buttons in the bottom corners, it is just that the white HTC logo screen is still overtop of it. Tried sideloading CWM but got an error so not sure if I did it right, can't really show any pictures though. Any suggestions?
**I am rooted, s-off, unlocked ****I have an SD card in it if that would help with any specific processes
I am very angry as I don't have the money to go out and just purchase a new phone I really hope there is something I can do, because things like this have happened before but I have been able to fix them within an Hour and it has been 3 hours now :/
Is there any way to keep it from rebooting by itself? Can I factory reset it through ADB?
I've had my rooted N5 on 5.0.1 for a while now. I recently unrooted it to upgrade to 5.1.1, and then I would reroot it. I downloaded 5.1.1 and the phone asked if I wanted to install the upgrade. I said yes and the phone then reboots. But when I looked at which software I was running it said 5.0.1. At that point I went through another reset so I could start over. And that's when the problem began. When the phone boots up it tries to boot into TWRP. My screen flashes TEAMWIN, but won't go any further. It just continues flashing without actually going into TWRP. If I hold the power button and the down volume button I can get the phone into bootloader mode, and that allows me to shut the phone off but that's all I can do. Can someone tell me where I screwed up and how can I get the phone to quit trying unsuccessfully to boot into TWRP? Thanks in advance.
Mark
Austexcat said:
I've had my rooted N5 on 5.0.1 for a while now. I recently unrooted it to upgrade to 5.1.1, and then I would reroot it. I downloaded 5.1.1 and the phone asked if I wanted to install the upgrade. I said yes and the phone then reboots. But when I looked at which software I was running it said 5.0.1. At that point I went through another reset so I could start over. And that's when the problem began. When the phone boots up it tries to boot into TWRP. My screen flashes TEAMWIN, but won't go any further. It just continues flashing without actually going into TWRP. If I hold the power button and the down volume button I can get the phone into bootloader mode, and that allows me to shut the phone off but that's all I can do. Can someone tell me where I screwed up and how can I get the phone to quit trying unsuccessfully to boot into TWRP? Thanks in advance.
Mark
Click to expand...
Click to collapse
Flash the 5.1.1 factory image with fastboot and start all over.
Sent from my Nexus 9 using XDA Free mobile app