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
Related
hi all
i am trying to do a factory reset to my nexus S but i faced some problems, the phone cant be reset to factory settings. my phone is on 2.3.4 and is rooted
i had tried the following steps
1) going to Settings>Privacy>Reset phone
after i confirm to wipe everything, the phone rebooted and it will stuck at the "Google" logo (in words) with the fastboot unlock logo at the bottom. i took off the battery to shutdown the phone (anything i press at this moment does not get any response from the phone) and start it up again. once it is started (it get pass the google word logo if i do it this way) all my application and even my themes are still there
2) shutting down the phone. press volume up + power button. choose recovery
same thing happen as above. it cant get pass the google word logo and once i restart the phone by plugging out the batt, it went back to previous state without wiping anything
i search online guide and also youtube video and all of them shows that the recovery will bring you to a android with a exclamation mark (in the triangle) but i cant get to the screen. i had left my phone there for 30 minutes but it is still stuck at the google logo.
Please help
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
polobunny said:
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
Click to expand...
Click to collapse
thanks for the feedback. now i am trying to flash it but i faced "adb device not found" error
ok done
managed to flash it back to an older version and everything works now
thanks a lot for your help! cheers
Make sure to update it eventually because you could run into issues when flashing stuff if your recovery isn't up to date.
No problem!
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
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
Hi all,
I just tried to update my XT1541 (I didn't see what version it was to, sorry), but was rewarded by an endless boot loop -- the phone wouldn't progress past the white splash screen, and lasted about 15-20 seconds per cycle.
Holding the [Volume Down] button got me to the bootloader screen, from which I was able to go into recovery. However, this only displayed an error message, 'No command found', with a red warning symbol over the android image.
I could get round this, however, by holding down [Power] then [Volume Up], and was able to both wipe the cache and do a factory reset. Neither of these helped fix the issue, however. I am unable to flash from the SD Card, either, as attempting this results in the error message, 'internal and external memory cannot be mounted'.
At this, point, I imagine I can try adb and fastboot, but does anyone have any guidance first?
Go into that bootloader screen and flash the stock rom with fastboot.
maarten2001 said:
Go into that bootloader screen and flash the stock rom with fastboot.
Click to expand...
Click to collapse
Ach, now I can't unzip the factory ROM -- sparsechunk.4 is broken and refuses to be extracted :/
rosyatrandom said:
Ach, now I can't unzip the factory ROM -- sparsechunk.4 is broken and refuses to be extracted :/
Click to expand...
Click to collapse
Make sure you have downloaded the correct version for your device or try to download it again.
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