Unlocked and rooted my phone last night using the latest version of TWRP. I mistakenly (not knowing at the time) used the Cyanogenmod installer kit which gave me an error during install. Now my phone is stuck on that spinning CM loading screen. When I go to get into the bootloader (power + volume down) my phone restarts and goes to the bright HTC screen with the red writing on the bottom, then goes right back to the CM loading screen and not into the bootloader menu like I want.
I have not yet tried the trick of holding the phone near bright lights to try and get it into bootloader. The USB cable I think is fine as well and not a cause of anything.
Any suggestions please? I have searched through this forum a lot, but haven't found this exact problem yet.
Try keeping volume down pressed even after it restarts
Sent from my HTC One using Tapatalk
Related
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
This happened this moring for no apparent reason, i moved a file for a game to be installed (final fantasy iv) in the android/oob folder and rebooted, and it never fully did.
Im stuck on the HTC logo forever.
At 1st i said to myself, lets go to hboot and make a factory reset, so i pressed volume - and power, and when i did, instead of restoring the device (wich was unlocked and rooted) it went back to the neverending htc logo, and it does the same for the recovery and the erase everything one, so from that point i tried installing a few firmwares from my carrier which is videotron, and it alway failed either because the signature is not compatible or simply because the device is not detected... it seems to get worst try by try...
I also tried to install from the sd card, adb or Amaze_All-In-One_Kit_V5.1 and 4.0.
Nothing works, please help me.
I just bought this phone used a month ago, and i loved it, and its unfair for it to die for no serious reason.
Are you able to access bootloader?
stuck
syedbilal093 said:
Are you able to access bootloader?
Click to expand...
Click to collapse
If it went to the HTC logo, you probably accidentally bypassed the recovery.
Turn the phone off, remove battery wait 10 seconds, install battery, wait 10 seconds, hold the volume DOWN button, while holding the volume DOWN button, press and release the power button. Keep holding the volume DOWN button until the bootloader screen appears, and then release it.
See what you can do with that.
If it doesn't help, find the RUU for your carrier--there's a list of RUU's in General section, "They're all here now" thread, and find the instructions for properly renaming it and placing it where it needs to go to have it install.
I have my Nexus 7 (2012) with android version 4.4.3
I rooted it by using Nexus root toolkit developed by Wugfresh and it is rooted correctly according to root checker.
Today i tried to install cyanogenmod from its website (i cannot post the link as i am not allowed becase i am new member)
I did all the steps correctly and the installer had started and then it booted up in the bootloader mode.
then on the top of the screen it was showing "Loading booted image"
then it is now showing a blue man with a white circle on its body.
After some time the installer said that theres an error (i dont remember what error it was)
then my N7 screen is on that screen of blue man with a white circle on its body (sorry for the bad language as i dont know the technical term for that thing) and is not passing that screen.
i tried to enter into bootloader mode so that i can flash it but when i press all the 3 buttons that time it loads the google screen and then it again loads up to the screen of blue man!
i tried removing battery and then thought that now its switched off so bootloader mode should switch on but it did not, instead of it again that blue man screen (i guess its the cyanogenmod's logo) came up.
i then tried pressing the power button and the volume up button but still it did not work. I am totally confused what to do now. Please help!!
It got normal like a charm!!
i kept my device as it is with that blue man. Then on that blule man android logo came up which comes when we select recovery in bootloader mode adn then i pressed the power button for approx 10 second and then it booted up normally (how android boots up).....no data loss and all normal....i d k how this happened but i am very happy!!!!
Heeth21 said:
I have my Nexus 7 (2012) with android version 4.4.3
I rooted it by using Nexus root toolkit developed by Wugfresh and it is rooted correctly according to root checker.
Today i tried to install cyanogenmod from its website (i cannot post the link as i am not allowed becase i am new member)
I did all the steps correctly and the installer had started and then it booted up in the bootloader mode.
then on the top of the screen it was showing "Loading booted image"
then it is now showing a blue man with a white circle on its body.
After some time the installer said that theres an error (i dont remember what error it was)
then my N7 screen is on that screen of blue man with a white circle on its body (sorry for the bad language as i dont know the technical term for that thing) and is not passing that screen.
i tried to enter into bootloader mode so that i can flash it but when i press all the 3 buttons that time it loads the google screen and then it again loads up to the screen of blue man!
i tried removing battery and then thought that now its switched off so bootloader mode should switch on but it did not, instead of it again that blue man screen (i guess its the cyanogenmod's logo) came up.
i then tried pressing the power button and the volume up button but still it did not work. I am totally confused what to do now. Please help!!
Click to expand...
Click to collapse
Heeth21 said:
i kept my device as it is with that blue man. Then on that blule man android logo came up which comes when we select recovery in bootloader mode adn then i pressed the power button for approx 10 second and then it booted up normally (how android boots up).....no data loss and all normal....i d k how this happened but i am very happy!!!!
Click to expand...
Click to collapse
Usually after flashing a new ROM, the first booting is bit longer, as it loads arts, caches, apps for the first time.
In future whenever you'll flash new ROM, just don't worry it'll boot up after its loading
hitman-xda said:
Usually after flashing a new ROM, the first booting is bit longer, as it loads arts, caches, apps for the first time.
In future whenever you'll flash new ROM, just don't worry it'll boot up after its loading
Click to expand...
Click to collapse
Thanx for the knowldge...!
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
I had recently installed evolution x, everything worked fine, but i stupidly hit the update button today and now im stuck on the twrp splash screen...
When it turns on i get the galaxy s9 plus splash screen then the twrp 3.5.2_9-0 splash screen.
I am not able to turn the phone off with the power button, i have to hold both volume down and power to restart it.
I have also left the phone overnight just incase it needed a bit of time but no luck, still just stuck on the twrp splash screen.
I have tried many hardware button combinations with no luck. I am unable to see the device on adb or fastboot, and i am unable to see the device when plugged in to install drivers for odin.
How do i fix this? (To be clear i dont care about the data on the phone, it is backed up but the phone is currently a paperweight in this state)
Edit [SOLVED]:
After weeks of googling i was able to find one thread for a different phone with a slightly different problem that said letting the phone run out of battery let them boot into download mode and it worked, as soon as i plugged in the phone and held the button combination i was able to get into download mode and install a later twrp version.
Hopefully other people can find this solution faster than i did
I am still looking for information on this if anyone has any.
I have also had to let the phone run out of battery and am hoping that doesnt make things worse.