Develop Bugs

[Q] About 3rd party recoveries and 5.0

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.

[Q] Bootloop on recovery

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.

TWRP question #2

What is this warning on the TWRP site regarding the S6:
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
And how does one install the above mentioned kernel without a custom recovery like TWRP?
Tyvm

spacer89 said:
What is this warning on the TWRP site regarding the S6:
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
And how does one install the above mentioned kernel without a custom recovery like TWRP?
Tyvm
Click to expand...
Click to collapse
No clue what this means, but i flashed over CPL3 the latest TWRP and it boots fine using stock kernel.
I just have the fingerprint issue... waiting for @amieldl143 to post latest bigdaddyrom build and am flashing that over CPL3 via TWRP.

What's the easiest method to replace CWM recovery with TWRP recovery?

Hi,
I have a non-rooted i747 that runs latest OctOS .
What is the easiest way to replace CWM with TWRP?
can I flash TWRP from within CWM?
Also, will TWRP replace CWM or install sidelines with CWM?
Thanks,

You can use Odin to flash tar version of twrp over Cwm.

.
.

audit13 said:
You can use Odin to flash tar version of twrp over Cwm.
Click to expand...
Click to collapse
Thanks! Flashing with Odin was a breeze. It overrode CWM for sure, although couple questions:
1) why is my splash screen still showing that ClockworkMod's alien image?
2) why installing TWRP recovery forced a reset of the OS. is there some dependency?

Unfortunately, I haven't used CWM for a long time; therefore, I'm not sure why the splash screen still shows the alien image.
I have flashed from older to newer versions of twrp without resetting the ROM. Maybe the switch in recovery causes the reset? I know that I have flashed twrp over the stock recovery without affecting the ROM.

user-747 said:
Thanks! Flashing with Odin was a breeze. It overrode CWM for sure, although couple questions:
1) why is my splash screen still showing that ClockworkMod's alien image?
2) why installing TWRP recovery forced a reset of the OS. is there some dependency?
Click to expand...
Click to collapse
Did it actually force a factory reset? I've never had TWRP do that. Newer versions of TWRP will usually ask if you want to keep system read only the first time you boot into it with a fresh rom. Are you sure that isn't what it did?

jason2678 said:
Did it actually force a factory reset? I've never had TWRP do that. Newer versions of TWRP will usually ask if you want to keep system read only the first time you boot into it with a fresh rom. Are you sure that isn't what it did?
Click to expand...
Click to collapse
Yes it factory reset, although still kept many residual folder/files from installation from about 3 years ago. I just went with default twrp's settings and used the most recent twrp .tar file (Dec 2017). Either way (os reset or not) is fine, I just did not expect that...

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!

Flash the stock patch recovery as boot??

orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up

i have just helped someone through this on TG so it defo works :good::good::good:

It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.

drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!

@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.

Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?

KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?

I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device