Develop Bugs

is Rooting PD1 as simple as using Odin to flash the latest Version of TWRP?

I am running Stock PD1 unrooted.
Is Rooting PD1 as simple as using Odin to flash the latest Version of TWRP? Will doing this install the necessary files, or is there a different method for build?
UPDATE: I flashed the latest version TWRP using Odin. Everything worked, except that when I booting into bootloader there was no TWRP, it was stock android bootloader.
What did I do wrong?

Right after flashing TWRP, you need to boot into recovery to boot into TWRP, if not, the phone boots normally restoring the Stock Recovery. As soon as the phone reboots, after the flashing TWRP, hold the Volume Up + Home Button + Power until it boots into Recovery mode. Should boot up into TWRP. Once TWRP boots the first time it will overwrite the stock recovery and become the default recovery. As for Rooting the Note 4, the only safe method is using Systemless Root, I just flashed this custom stock rom and all is done for you. Here is the thread link: http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832

Went to flash TWRP through ODIN and got a message- custom recovery blocked by A/L. Any solution please?

Same here. Get a FAIL with any TWRP flash. Same with Stock Rom Tar as well. Stuck with no ability to flash.

Oneplus 3 OTA fails- 3.2.8 Please help!

My device fails to install the 3.2.8 OTA. Device was rooted but it now unrooted with unlocked bootloader running stock 3.2.7 Oxygen. Currently has TWRP recovery but I have also flashed stock recovery back and tried the OTA with the same result. Any ideas?

why don't you flash the full rom without wipe /data with TWRP ?

This is normal, the OTA updates restore the OnePlus recovery.
Reflash TWRP with TOOL ALL IN ONE (or any other way) and reflash SuperSU.
That's what I did and everything is ok

TWRP gets overwritten

I'm on latest ob18. I am able to flash it, and run it once, but after reboot, the stock recovery gets Back. Any ideas?

Just Reflash twrp via flashify or adb in fastboot mode, that could be normal if u r flash an unmodified stock rom

Yep. On latest ob-Oos or H2o for me recovery stays, after instaltion of the rom. But on a second reboot, stock recovery shows and i reflash custom recovery again.

Guys I flashed latest H2OS beta over OOS Beta18 and lost access to recovery. These are the steps I followed, please help.
1. Backup current ROM (OB18)
2. Dirty Flash New H2OS version
3. Flash recovery image again
4. Reboot system
ROM booted without any problems and all my data is present but I lost access to TWRP.
Solution attempted: Reboot to fastboot and flash recovery image again, the process is successful but still TWRP is not coming up.
Please help. Thanks in advance

Stock rom always over writes recovery best way to get it to stick is flash stock zip than twrp reboot to twrp and reboot or flash mods/root

liam_davenport said:
Stock rom always over writes recovery best way to get it to stick is flash stock zip than twrp reboot to twrp and reboot or flash mods/root
Click to expand...
Click to collapse
Thanks this worked

flashing stock factory image without -w flag

Hi there. I wanted to go back to stock ROM, but with TWRP, caesium kernel and root/magisk. Right now I am on a custom ROM. So I wanted to backup with swift backup pro, TWRP. Then flash stock image to both slots / full wipe. Then boot to TWRP with fastboot, flash TWRP zip and kernel plus magisk, reboot TWRP and flash my debloater script. Then next month flash the factory image without the -w flag in the batch, and repeat the process above to have kernel and root. Am I missing something? Is the planned process proper? Or did I plan wrong steps?

I think you're fine, except an OTA will be more efficient the second time around.
Backup.
Connect P2XL to PC and Flash stock image to both slots.
Boot into TWRP using fastboot.
Install TWRP to the recovery ramdisk (as of TWRP 3.3.0-0).
Flash Magisk.
Flash your (unnecessary IMHO) debloater script.
Boot.
Enjoy the device until the next update, then...
Download a full OTA to the device.
Boot into TWRP.
Install the OTA.
Install TWRP to the recovery ramdisk (as of TWRP 3.3.0-0).
Flash Magisk.
Boot.
As of the release of TWRP 3.3.0-0 zip files are no longer available for installing TWRP to boot.img. TWRP will install itself into the boot.img by selecting "Install Image", then selecting "Install to recovery ramdisk".

Thanks, Sir.
OTA does not overwrite TWRP then?
Or flash OTA, boot to TWRP, flash TWRP as image, kernel & magisk? I guess I'll decrypt before flashing OTA?

An OTA will overwrite both TWRP and Magisk since it flashes a stock boot image. However, you are installing the OTA using TWRP and thus have TWRP resident in memory, so as long as you do not reboot you can flash TWRP to the ramdisk and then flash Magisk.

Strephon Alkhalikoi said:
An OTA will overwrite both TWRP and Magisk since it flashes a stock boot image. However, you are installing the OTA using TWRP and thus have TWRP resident in memory, so as long as you do not reboot you can flash TWRP to the ramdisk and then flash Magisk.
Click to expand...
Click to collapse
Thanks again, Sir.

stock recovery zip?

Now I have twrp recovery with custom rom but I want to flash stock recovery.Anyone have this?

nikkky said:
Now I have twrp recovery with custom rom but I want to flash stock recovery.Anyone have this?
Click to expand...
Click to collapse
This device hasn´t recovery partition, stock recovery interface is a part of the stock boot, when you flashed a custom rom it was overwritten but if you already flashed the TWRP installer what you can do now is to flash stock boot or a backup of the boot that you´re using but you´ll lose Magisk or a custom kernel if you have it.
The better is then to set up all included Magisk not to flash TWRP installer.