Hi,
This is my first post on this forum and I might sound like a total dummy (cos I am when it comes to rooting/flashing android devices).
My Nexus 4 was suffering from poor battery performance and to correct that I thought of trying my hands at rooting it and flashing it with a custom ROM. However, being a noob, little did I realize what I was getting myself in to.
Now, after unlocking the boot loader, when I tried to boot my device from recovery mode, it just wouldn't fire up, but kept showing the rotating dots of lollipop boot screen.
After a lot of fiddling, I managed to mess up even further as now, the rotating dots are also not appearing and I just get Google logo twice and after that the device's screen just keeps blinking with a faded background light on the screen.
I used Nexus4Root to root the device and have ADB installed on my Mac OS X machine.
Is there anything I can do to bring my Nexus 4 back to life?
Any help is appreciated.
Thanks.
ajxkid said:
Seems like unlocking your Boot loader have not been successful , Toolkits are not always dependable. I think you should unlock ur Boot loader manually with adb and fastboot .
You could find guides for that all over the web. Go on and try that..
Good luck
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response. I think I did manage to unlock the Boot loader, as I can see that in the status when I switch ON the phone in 'recovery mode'. The problem is that I am not able to boot the phone through recovery mode. As I said, it goes in a sort of boot loop. It does not boot from normal mode, same thing happens (boot loop).
Is it possible to flash the factory image in the current state of device? The device is not detected by my Mac when I try to fastboot it.
Any guides/threads I can look at with similar information? Have been looking up quite a lot online, but to no avail.
Thanks again!
Related
Hi
I got somehow a big problem.
I tried to update my Nexus S by mistake with the I9020A 2.3.6 Rom. It failed. At least somehow it said so.
Now i cannot load my phone normally. Sometimes I have to battery pull several times before the Nexus S boots up again. The other times it stays with a nasty "Google" on screen.
Even more strange. I cannot access the recovery submenu. It does stay at the same nasty "Google" on screen. It does no longer show up the triangle where you the can load an update.zip
What can I do?
Nexus S: GT-I9020
I9020XXXKB1
EUR
Thanks for help
Cheers
Martin
Since you said you can't access the recovery console and it gives you a google logo, I'm going to have to ask: Do you have access to the fastboot bootloader?
If so, are you rooted? If no, you have the option to take it in to get fixed or to root your phone.
If you decided to root/are already rooted, connect your phone to your computer while in fastboot, make sure all drivers are installed and use a command prompt to use the fastboot tools. The Unlockr's Nexus S rooting guide will be a huge help in guiding you where to be.
Does "fastboot devices" return anything on your computer, or is it empty?
(Sorry if you know most of this crap, but number of posts + lack of information in the OP + you saying you don't have a custom recovery = assuming you need a bot more in depth instruction.)
Thanks god I have been able to push the fastboot recovery console!
I did manage to access backup & restore and then load the stock 2.3.3 rom. I am back in business
Thanks for help. I think it is solved.
Cheers
Martin
Now make sure to make a backup.... helps save your a$$
Sent from my Nexus S using xda premium
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
I had the same problem.
Dawezilla said:
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
Click to expand...
Click to collapse
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
pbone771 said:
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Click to expand...
Click to collapse
UPDATE:
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Ryan_Shea said:
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
HAd backup. Was with TWRP. BUT could not get to Recovery mode. All good now though.
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Glad to hear it. There is an updated boot loader in the forum somewhere that fixes the "unable to boot in to recovery via fast boot" which can save a lot of hassle if you happen to boot loop again. Makes it a hell of a lot easier to recover. I had the same issue when I first rooted too. Had to just full wipe and recover to stock because I rooted first and then unlocked the boot loader which made the root not stick so when I tried to flash the first ROM got a boot loop and couldn't get to recovery, such a pain in the ass the nexus is.
Sent from my Nexus 7 using xda app-developers app
Hello, back in december I was trying to load up an app on my phone but in a video the guy said to download chainfire so I did and installed the driver and my phone got stuck in the warning unlocked bootloader screen and I really can't remember what I did but I did something with downloading the system restore image but it wouldn't work so I changed up the files and now my phone is stuck in fastboot and no longer is usable so I just threw it in my drawer and never used it again up until now here I am asking for help on how to resolve this issue. I'm no android techie so I really don't know much about anything other than rooting phones. My phone is a Moto G XT1031. Also I can't charge my phone because when I leave it, the phone just keeps rebooting and it really doesn't charge much.
UPDATE:
I managed to unlock the bootloader but now when I power it up, the device is stuck on the motorola screen.
If you can get into fastboot mode, try flashing a stock ROM for your phone.
audit13 said:
If you can get into fastboot mode, try flashing a stock ROM for your phone.
Click to expand...
Click to collapse
Thank bro it worked for me thanks a lot
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.