Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Jesse402 said:
Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Click to expand...
Click to collapse
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Hope this will help, good luck.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Click to expand...
Click to collapse
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Jesse402 said:
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Click to expand...
Click to collapse
Hi,
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Click to expand...
Click to collapse
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Jesse402 said:
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Click to expand...
Click to collapse
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Click to expand...
Click to collapse
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Jesse402 said:
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Click to expand...
Click to collapse
You're welcome. If I can, I will always try to help.
Hope you will enjoy your OP 7 pro, think it's a nice phone.
It's a shame it did'nt bring you 3 years of pleasure, hope mine will, but will see.
Cheers
Sent from my Google Pixel using XDA Labs
Related
Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
any solution?
hi guys.i have the same issue.does anyone have a solution for this?
i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )
Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.
Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App
Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.
twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).
matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.
Hi.
My OnePlus One wont boot up anymore.
I was playing dead trigger 2, when suddenly the phone froze (first time the it happend)
I restarted it with holding down the power button.
After restart, it hung on CM11 boot screen, not boot loop, but let it load for 10min, still at CM11 boot screen.
Restart again with power button, but this time it wont boot past OnePlus One boot screen, after the first boot screen, it is a never ending boot loop.
I was able to get to recovery (TWRP), tried to reinstall ROM (CM11 nightly 04.10.14), still boot loop after OnePlus One boot screen.
Tried to wipe date, cache, dalvik, and reinstall, still boot loop.
I am able to get to fastboot.
So what is the next thing to do?
Try to flash back to stock? How can I do this without format internal storage?
Use "adb pull" to extract any files you want to recover.
Then flash back to stock. It will automatically wipe everything.
Gamm86 said:
Use "adb pull" to extract any files you want to recover.
Then flash back to stock. It will automatically wipe everything.
Click to expand...
Click to collapse
Well, I got the 64GB version, and last time I checked, I had 4GB free.
Can I pull whole titanium backup folder?
ole12 said:
Well, I got the 64GB version, and last time I checked, I had 4GB free.
Can I pull whole titanium backup folder?
Click to expand...
Click to collapse
Sure...assuming it is still there...
Code:
adb pull /sdcard/TitaniumBackup/
ole12 said:
Hi.
My OnePlus One wont boot up anymore.
I was playing dead trigger 2, when suddenly the phone froze (first time the it happend)
I restarted it with holding down the power button.
After restart, it hung on CM11 boot screen, not boot loop, but let it load for 10min, still at CM11 boot screen.
Restart again with power button, but this time it wont boot past OnePlus One boot screen, after the first boot screen, it is a never ending boot loop.
I was able to get to recovery (TWRP), tried to reinstall ROM (CM11 nightly 04.10.14), still boot loop after OnePlus One boot screen.
Tried to wipe date, cache, dalvik, and reinstall, still boot loop.
I am able to get to fastboot.
So what is the next thing to do?
Try to flash back to stock? How can I do this without format internal storage?
Click to expand...
Click to collapse
data/wipe and then advanced and wipe system as well. then reflash rom and gapps. do this after you backup all your stuff but you should not try and restore with TB after you get it back up and running. Just my opinion
Same Issue here..
playya said:
data/wipe and then advanced and wipe system as well. then reflash rom and gapps. do this after you backup all your stuff but you should not try and restore with TB after you get it back up and running. Just my opinion
Click to expand...
Click to collapse
I tried literally everything..
I was on multi rom and using Mahdi and CM11s(Internal).
Then i stuck in black screen that my phone wont wake up but LED was blinking. Did a reboot holding power button.
After that when I selected the internal rom it just gave a vibration and came to CM boot logo. Now I tried reflashing 3-4 roms doing whole wipe but no change. Then I flashed Stock with toolkit and it says successful but no booting..
Totally worried.. Please someone help here.. :crying:
rana103 said:
I tried literally everything..
I was on multi rom and using Mahdi and CM11s(Internal).
Then i stuck in black screen that my phone wont wake up but LED was blinking. Did a reboot holding power button.
After that when I selected the internal rom it just gave a vibration and came to CM boot logo. Now I tried reflashing 3-4 roms doing whole wipe but no change. Then I flashed Stock with toolkit and it says successful but no booting..
Totally worried.. Please someone help here.. :crying:
Click to expand...
Click to collapse
you flashed stock with toolkit? first off leave toolkit alone.... Did you flash the .img files? or you flashed a zip file to get back to stock?
I know you are upset but you say you have tried everything. Did you try this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Edit: Also there's no crying in rooting!
So, I just used fastboot to restore it back to stock, and it is STILL bootlooping after OnePlus One screen.
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Downloaded files from this site, and extraced the XNPH33R zip file, and run the flash.all file.
It says completed after writing everything, no error. But still wont boot up:/
So I tried installing every file manually following this guide: http://www.androidheadlines.com/page/2. No luck
The same problem here. I started facebook, It rebooted, 10 mins of CM logo, power off - neverending bootloop.
Reinstalled all via fastboot, ... still in bootloop.
RMA ?
peyooo said:
The same problem here. I started facebook, It rebooted, 10 mins of CM logo, power off - neverending bootloop.
Reinstalled all via fastboot, ... still in bootloop.
RMA ?
Click to expand...
Click to collapse
ole12 said:
So, I just used fastboot to restore it back to stock, and it is STILL bootlooping after OnePlus One screen.
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Downloaded files from this site, and extraced the XNPH33R zip file, and run the flash.all file.
It says completed after writing everything, no error. But still wont boot up:/
So I tried installing every file manually following this guide: http://www.androidheadlines.com/page/2. No luck
Click to expand...
Click to collapse
flash persist.img and reserve4.img as decribed here: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BACKUP FIRST!
I have the same issue! Suddenly the screen froze. He did not respond to any button, either physical or capacitive. It was well for several minutes (20). Finally I opted for a "hard reset". I turned it on again and this time the screen froze while loading Cyanogen (Hexagon logo). Never happened there. 30 minutes later, I opted for a new "hard reset". Since then, never goes to the home screen (1 + logo and "powered by android"), reseteándose again and again, over and over again without end. Bootlooping :crying::crying:
I have tried everything to get it back, enter in the "recovery", delete data, cache, factory reset ... nothing makes then pass the initial screen.
I even managed to flash with CWM recovery and ADB one posteriomente whole mod, nothing works...
---------- Post added at 04:42 PM ---------- Previous post was at 04:02 PM ----------
luka1002 said:
flash persist.img and reserve4.img as decribed here: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BACKUP FIRST!
Click to expand...
Click to collapse
YOU ARE MY HERO!! THANK A LOT... at least it's working again. Flashing persist.img and reserve4.img was the right key! :good::laugh:
For the records, I flash too the XNPH30O... upgradeing it now to 38R
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
I just flashed my nexus 5. i am getting the *.sig error too. After flashing, it was taking very long time in boot animation. I nearly to force shutdown. But after around 10 minutes, it is successfully boot.
sorry for my english, just wanted to share my experience. hopefully it help
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
The first boot takes a LONG time. Just let it go for a while.
jsgraphicart said:
The first boot takes a LONG time. Just let it go for a while.
Click to expand...
Click to collapse
So, I did try as you said. I left it but it kept booting for more than 20 minutes. What to do now?
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
manujosephv said:
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
Click to expand...
Click to collapse
Incredible. That, worked! I did a rookie mistake by pressing both at the same time which led to nothing. Got it up and running. Thank you everyone for their inputs, couldn't have done without it
The factory wide and reset does not work for me. Stills tuck at the boot animation.
I recently had the same issue with my Nexus 5 and have been back and forth with Google Play support to resolve the issue with no success on that front. However I did get my issue resolved, which was caused by a corrupt /persist filesystem. What I did was this:
Flash CWM Recovery
Reboot into Recovery
notice that /persist isn't mounted, try mounting it and it will fail
Launch and ADB shell
run 'e2fcsk /dev/block/platform/msm_sdcc.1/by-name/persist'
let it fix any errors found
try to mount the /persist partition, it should work now
(Optional) reboot to bootloader, flash whichever recovery you want or stay with CWM
reboot into system, all should be fine now
After successfully repairing and mounting /persist within CWM Recovery I powered off and just flashed the stock 5.0 image from the Google Factory Images page.
A special thanks to bitdomo for his information here which ultimately fixed my issues:
http://forum.xda-developers.com/showpost.php?p=54252961&postcount=3
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.