I noticed that when using the last dev preview for my N7 2013, it keeps killing TWRP and putting back the stock recovery. Now the final release does this. If I flash TWRP again, it just gets overwritten after a normal boot then back to recovery.
Why? Is there a way to stop this? This is the first time I've dealt with this. Nothing else does this to me. I haven't found a clear answer yet to this while searching this site or others.
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
rguilamo said:
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
Click to expand...
Click to collapse
Well it is just 5.0 that does this.
Since I posted this there is a sane reason for them to do this - it might be the way they enforce the factory reset protection. It has to use their recovery to do so. Still annoying.
But thanks for a workaround, that it simply is the kernel, or boot image. That and I want root
You can try Chainfire's CF-AutoRoot, It modifies Boot.img so root is granted in boot time, I already had a custom kernel when I rooted, but you can try to root first and see if it stops auto-writing the stock recovery.
Here's the download link: http://download.chainfire.eu/347/CF-Root/CF-Auto-Root/CF-Auto-Root-flo-razor-nexus7.zip
Extract it, and run root-windows.bat (or the one suitable to your OS) while in fastboot.
Related
Using "CWM-based Recovery v5.0.2.7 FULL".
I can't get my device to boot. I'm running the previous version of Energy's ROM (not most recent). However, I can get into recovery and fastboot easily.
All I have tried is to factory reset, wipe caches, and re-install Energy, but it still will not boot. It's gotten close - can see the splashscreen, but no further.
Battery is at 100.
What do I need to do get this baby going again!
P.S. The original problem is that I let the battery drain too low for it to fully boot.
Always read the OP for the ROM before you flash...
http://forum.xda-developers.com/showthread.php?t=1528024
NRGZ28 said:
...
How to Flash this ROM:
- Root your device
- Install TWRP custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
Click to expand...
Click to collapse
The 3.0 Kernel discussions also mention the the symptoms you will encounter if you do not follow instructions...
http://forum.xda-developers.com/showthread.php?t=1591869
Hashcode said:
PLEASE use TWRP to flash this ROM. You will probably bootloop if you don't. If you experience a really long boot animation, double check your recovery (change if necessary) and try it again.
Click to expand...
Click to collapse
Oddly enough I used TWRP to flash. Somehow it reverted me back to CWM. I don't have a clue.
It's currently trying very hard to boot. Once I get there what should be my first steps?
If it doesn't boot, should I try and push TWRP through fastboot?
Edit: pushed TWRP (latest). Wiped and reinstalled. Still won't get past boot animation.
Can I transfer a new ROM file using fastboot or will I need to use 'fastboot update' to install a different ROM?
Should I try reverting to stock image?
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.
My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
[email protected] said:
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/xpe...-recoveries-custom-roms-t3016507/post58515438
The reason this happen is that Xperia smartphones do not have recovery partition. The recovery is part of the kernel (boot.img), so the kernel comes with a recovery. The link above has a recovery with is flashed onto the FOTA (over-the-air) upgrade partition, which is not used if you have an unlocked bootloader.
Works great
Thanks for that. I had previously tried it but used the latest twrp zip file instead of the 2 in lower box and recovery was totally unstable. However now done FOTA-TWRP.zip and flashed 2 different roms retaining twrp recovery everytime.
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.
Has anyone noticed the recovery image is no longer a part of the full factory image?
I thought i had a bad/corrupt download at first, but after downloading on my other pc i got the same results, no recovery image.
Its nice that i dont have to boot and flash twrp after a factory flash, but i noticed some other weird things.
first time i flashed the January image after the process was completed it booted straight into twrp, i hit reboot to system, and when it booted all my personal data was still there. it remembered my password, wallpaper, all text and calls were still there, etc. i hadnt removed -w from the script and i couldnt figure out why it was like this.
All of this aside, anyone know why google didnt include the recovery in the latest factory image?
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Pain-N-Panic said:
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Click to expand...
Click to collapse
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
noidea24 said:
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
Click to expand...
Click to collapse
Pain-N-Panic is correct, recovery is included in the boot.img and your TWRP installation *should* have been replaced by stock when flashing a full factory build. Every build I've flashed has always said recovery.sig not found. That is normal as far as I'm aware. I've noticed that it all depends on how the flash-all script/an OTA flash handles seeing a TWRP installation. There have been a few circumstances where my TWRP installation stayed in tact as well.