Hello,
I was flashing the latest version of AOKP using TWRP, and the update failed. I verified the MD5 hash before attempting the flash, but figured I'd the file had gotten corrupt somehow. So I went to reboot my phone, and it hung on the boot loader screen. I Pulled the battery and tired again, but same result. So I booted back into TWRP, restored from the backup I took just prior to attempting the flash, and upon booting my phone went directly to the Setup Wizard. I rebooted, tried the restore again, but same result. I went through the wizard, and confirmed my phone had factory reset (Note, I didn't manually wipe anything).
Does anyone know what might cause this, and if I have any way to restore the backup I have? I was going from AOKP JB Builld 3 to 4, so I didn't take a Titanium Backup first. I've been using CWM since I got my GNex in January and have never had an issue (I've switched ROMs several times, and done many backup.restores with CWM. So i'd like to think I know what I'm doing ). This is the first time I've tried out TWRP, and everything seemed to go smoothly (Except for the failed flash).
Any help would be greatly appreciated. I've been searching around and haven't found anyone else reporting this.
Not sure why it factory reset but if you still have cwm back ups flash cwm and restore one of those. Factory reset isn't a bad thing though staying fresh is the best way to start a new ROM. I don't recommend restoring anything.
Sent from my Galaxy Nexus using xda premium
Related
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Start over
Nand recovery then root again. Find a stable rom. There are tons that float to the top of the forum. I'm on Damage Control 3.5, works great.
Tried to Nand, It error's out and won't restore.
Like I said, DC 3.5 is what gave me the trouble to begin with, at least thats when my troubles started.
My phones gone completely unstable..and at the moment, unusable.
Also, be patient. After a flash, it may take a while for it to load. You seem overly anxious, by your post. I've flashed 30x and probably only bootlooped twice and those were Fresh's 3rd to last rom.
I let it sit there for 10 minutes saying fresh 1000x over a couple times, pretty sure I'm not being impatient.
battery is now dead.
Full wipe
Are you wiping everything? Dalvik wipe, user data wipe, cache wipe? Can you get back to recovery? How did you root?
Yes I can get into recovery, yes I'm wiping everything.
I used Simpleroot to get Root.
Rerun
I would try to re-run the second button in simple root to unlock nand. It doesn't hurt to re-run. You really shouldn't have a problem recovering nand if that process worked the first time. If you can't get that to run, you might want to adb it, but since you simplerooted your phone, you might have to read up on that. Once you take care of nandroid, you are good to go.
Nand is giving me an error that backup cannot be found <even tho I most definitely did Nand backup my stable setup> so IDK what fixing nand would do even if it is broken if it cant find the restore files. erm..
End of the Road
I suggest you do a forum search for more opinions/solutions. You are not the only one on here that has been through this. I did a quick search and found a handful of threads with this exact same topic.
Alanmw86 said:
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Click to expand...
Click to collapse
How did you install a different recovery if your stuck in a boot loop? As for your problem, i had a bootloop before on freshz's older rom, and some of the solutions i had read werent working, i ended up booting into recovery, and rewiping without doing a reinstall of the rom, and it solved my problem, also have read that pulling the battery has gotten some people out of there loops. Hope this helps
I pulled the battery booted into recovery and wiped the rom, flash an alternate, booted up, changed to Amon and started over, was the one time I was able to get it to boot threw, after that same results.. I couldn't explain how it managed to boot up just one time either.
Hey all, never posted on here before because I've had good luck with ROMS in the past but here goes.
Haven't rooted since the 4.3 update. Rooted the other day with cfautoroot. Everything went fine. Decided to try slimrom, so I installed TWRP 2.7.0, made a backup, ect. Went to install the ROM and it gave me errors. So I restored my backup. I had a hell of a time getting past the at&t screen but I finally got it to boot. The minute I unlocked, I was bombarded by "com.processes.gapps has unexpectedly quit" among every other app telling me it failed. So I got to the backup and restore and did a factory restore. Everything seemed to be normal. So I looked online for some information on the errors. Found a forum that indicated I was using a TWRP version that was too new. So I installed 2.6.1. Because I apparently enjoy being aggravated, I did the whole process over again. The same result happened. After more research I discovered that TWRP may have been the culprit along with ROM manager. So I installed Clockwork and did the whole process AGAIN! I got slimrom to install without problems. I was able to make a backup of slimrom as well. Just to be sure, I went and did a wipe in clockwork and tried to restore the backup I made of stock. Restarted, same error messages. Every second. Did a factory restore and everything was fine. So then I did a backup again and restored my backup of slimrom. It works fine! If I try to restore the backup of stock, I get errors. What's going on here!?
What I tried:
Clearing caches and data of the apps that were throwing errors
Stopping download manager and restarting it.
Clearing cache and delvik cache in CWM
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Hello,
My galaxy nexus suddenly crashed yesterday. I don't know what happened, I only know that I had the xPrivacy installer and "App Ops". It's a rooted phone with TWRP recovery v2.8.6.0 and CyanogenMod 10.2. The only problem I had so far was WhatsApp not displaying any chats and had to restore my chats. I do suspect these two are linked to each other
When I try to boot it normally, it crashes after a couple seconds and gets stuck booting and crashing again until I take out the battery.
After fiddling around for a while, all the errors pointed at the data partition, but it seems like I just can't write anything to the internal SD.
What I've tried to fix it is (not necessarily in this order):
Wiped (Dalvik)Cache
Factory reset via TWRP
Restore a recent nandroid backup via TWRP (this says it failed)
Restore a nandroid backup that I made after a factory reset via TWRP (this says it failed)
Restore a nandroid backup via Nexus Root Toolkit
Create a backup (just to test if I could write, it said it succeeded but after a reboot there was no backup)
Wipe data partition TWRP
Used "fix permissions" on TWRP
Formatting SD via TWRP
Wiped all partitions via TWRP
"Flash Stock + Unroot" on Nexus Root Toolkit (Soft-Bricked/Bootloop mode)
Flashed CM10.2 via TWRP
Flashed CM10.2 via Nexus Rootkit
Flashed stock ROM via ADB
Deleted all data via Windows Explorer
Hard Factory reset via ADB
Everything says it was successful, except when restoring a backup via TWRP and a single time I tried wiping the Data partition. I once got an error message saying a file was opened too many times, but I think that is just because it couldn't read the file.
Besides unlocking, rooting and flashing CM, I haven't done much software wise. I have done some handiwork hardware wise, because when I got this phone from a friend, the pins for reading the SIM card were broken off. This was a couple months ago and I don't think I broke anything.
I hope that I have been clear enough explaining my problem, I sadly cannot give a logcat file.
Thank you in advance
I'm having your issue too. I wrote here some days ago, here it is my post http://forum.xda-developers.com/galaxy-nexus/help/unable-to-reset-strange-behavior-t3116856.
Hope we will find a solution!
Same issue for me.
I tried also with odin and it dosen't work.
I have Cyanogenmod 11 and clockworkmod recovery.
and same thing here, try to install CWM from flashify app... see if you can wipe and install roms with that... i know that CWM is outdated, but most of the times it still gets the job done...
This is so weird. 2 days ago the same thing happened to me, my phone is stuck in a boot loop, and I can't bring it back to stock, since I can't wipe or flash. This is so frustrating.
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.