Related
device was rooted and on LU6200_162_CN_Yang_0704 ROM.
Today, the gf was prompted to update/upgrade system by LG and she chose to do so after feeling harassed by the update notices. now the devices goes directly into CWM after booting from LG screen (it won't load). She tried restoring from zip, but it has no effect; it reboots into CWM after the bootup page. We restore using every backup file available, tried wiping cache, data, and dalvik, then restoring, tried going into advanced restore and restoring boot (presumably the boot.img), tried re-installing the ROM, but to no avail.
I'm guessin the official update clashed with the bootloaders.
I'm planning on re-flashing the v142 .kdz on Sunday since I don't see her until then, but could use any advice/suggestions in the meanwhile.
thanks!
alljokingaside said:
device was rooted and on LU6200_162_CN_Yang_0704 ROM.
Today, the gf was prompted to update/upgrade system by LG and she chose to do so after feeling harassed by the update notices. now the devices goes directly into CWM after booting from LG screen (it won't load). She tried restoring from zip, but it has no effect; it reboots into CWM after the bootup page. We restore using every backup file available, tried wiping cache, data, and dalvik, then restoring, tried going into advanced restore and restoring boot (presumably the boot.img), tried re-installing the ROM, but to no avail.
I'm guessin the official update clashed with the bootloaders.
I'm planning on re-flashing the v142 .kdz on Sunday since I don't see her until then, but could use any advice/suggestions in the meanwhile.
thanks!
Click to expand...
Click to collapse
I got the same problem, did you fixed it?
Xainsterr said:
I got the same problem, did you fixed it?
Click to expand...
Click to collapse
Sorry for the late re:
Yah, totally fixed. Just went through the step again, starting from v142 to ROM [x]. Worked like a lucky charm in milk
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
mikewelch5 said:
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
Click to expand...
Click to collapse
If you do a factory reset (with the kdz tool, its the best way if you want to reinstall the stock firmware), you lose everything (root, recovery, etc..) because it will flash the phone completely.
I recommend you to take a look at this for all the thing that you need to do: http://forum.xda-developers.com/showthread.php?t=2785089
And make sure you never do a factory reset from within Android w/ a custom recovery like TWRP installed, otherwise your phone will end up in a continuous boot loop. There's no reason for you to go back to stock anyway, as you're planning on reinstalling CM12 or installing a different ROM. You'll be doing a factory reset (wiping System, Data, Cache, and Dalvik) from within TWRP before flashing anyway, so there's no need to go back to stock beforehand.
mikewelch5 said:
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
Click to expand...
Click to collapse
If you flash your phone with kdz, yes, like the guy above said you will lose both root and recovery. What I'm curious about is reason you want to do it? You already have custom recovery so if you want to do factory reset (that is wiping data and cache partitions) why not do it manually there?
And what is the point of it? As you said you will flash CM12 or another ROM, so that will basically do a factory reset, you will wipe all (system, data, cache) to install your new ROM...
Of course before flashing or wiping system partition with TWRP I recommend doing a backup just in case.
Thanks for the info everyone. The reason I wanted to do a clean factory install instead of just putting on CM12 is because if I didn't like it, I could just go back to a stock, rooted KK.
Like I said it has been acting up lately, so maybe a clean install of factory can help it. That way, if I don't like CM I can just restore my clean copy.
Where as now, if I didn't like CM I would have to restore my messed up backup.
But I will probably flash back to stock firmware, root it again and put a custom recovery on it again. Make a backup of that, then play around with some ROMS.
But once again, I appreciate the help!
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
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.
I tried Factory Reseting my phone earlier today through Recovery, It said everything was reset so I restarted my phone. My phone is now in a bootloop, it vibrates, shows the "erasing" screen, then the hidden LED light turns on and the screen goes black, then the phone does that forever. It's on the erasing screen for about 3 seconds before restarting. Trying to enter Recovery Mode just sends me back to the "erasing" screen.
Any help would be wonderful!
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
victorhbm15 said:
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
Click to expand...
Click to collapse
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Dubstepwolf123 said:
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Click to expand...
Click to collapse
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
victorhbm15 said:
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
Click to expand...
Click to collapse
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Dubstepwolf123 said:
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Click to expand...
Click to collapse
Why not fastboot install stock firmware?
Isn't that available, here?
pizza_pablo said:
Why not fastboot install stock firmware?
Isn't that available, here?
Click to expand...
Click to collapse
In the end I was able to install the Stock Moto Z2 Play firmware... I hate when people don't include the fix in their answers for other people, but currently I am unable to post any links because they are on a different device. I'll get back later with the links.