Related
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
razi914 said:
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
Click to expand...
Click to collapse
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Carlos_Manuel said:
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Click to expand...
Click to collapse
You better get some rest bro, u didn't read anything,! This issue also happened to you also, you said a 10-15 pages back that ur stuck on google too after rebooting, ! P.s i will install dreams 4.1.x , and wait for a 110% stable cm10.2 by you!
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
lastforone said:
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
Click to expand...
Click to collapse
no didnt worked for me,, had to flash factrory image
Hey guys, Ive had an issue that I just cant seem to fix.
A friend of mine has an LG GPad 8.3 like mine, and it has TWRP custom recovery with one of the new 4.4.2 w/root flashable firmware US version. He made the mistake of going into Backup and Reset in the settings menu in the OS and selected Restore Device to factory settings, and now Its locked into a permanent TWRP boot loop. I've tried everything I know including flashing numerous other ROMs, formatting virtually everything you can format in TWRP. Even after a new rom is successfully flashed, and you factory reset and everything else, upon reboot it will only go back to TWRP again. Over and over. Is there any way you guys can think of that can stop it from going into recovery and click into the proper boot sequence again? Cheers
djleez82 said:
Hey guys, Ive had an issue that I just cant seem to fix.
A friend of mine has an LG GPad 8.3 like mine, and it has TWRP custom recovery with one of the new 4.4.2 w/root flashable firmware US version. He made the mistake of going into Backup and Reset in the settings menu in the OS and selected Restore Device to factory settings, and now Its locked into a permanent TWRP boot loop. I've tried everything I know including flashing numerous other ROMs, formatting virtually everything you can format in TWRP. Even after a new rom is successfully flashed, and you factory reset and everything else, upon reboot it will only go back to TWRP again. Over and over. Is there any way you guys can think of that can stop it from going into recovery and click into the proper boot sequence again? Cheers
Click to expand...
Click to collapse
Reset FOTA? http://forum.xda-developers.com/showthread.php?t=2639822
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .
Hello XDA. I'm here with a request of help regarding my Samsung Galaxy Nexus (GSM/ MAGURO). Yesterday i wanted to swap from CM11 to CM12 and backed up my apps using Titanium and backed my photos and stuff. The thing is when i finally got the rom itself and GAPPS in the device memory i performed a factory reset in the device before flashing. So i went to ClockworkMod Recovery like always and wiped dalvik but instead of wiping the cache i wiped the data and cache as many of you know its one option above of the wipe option so i deleted all the files from the device. The other issues is that i wiped my ROM and zip files that i wanted to flash. I wanted to boot into bootloader but my PC didnt recognize the device. I intalled the WUG's Nexus Root Toolkit and i did a second mistake by trying to flash stock rom and i dont have recovery now even. I can only boot into bootloader and its unlocked. No recovery, no ROM not files. Tried almost everything on my mind but it didnt help. The funny thing it i flash different ROM for years now across many deviced but for the first time i completely didnt pay any attention.
Can you guys please tell me what to do next? Thanks!
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.