Develop Bugs

[HELP GUIDE] - Can't flash TWRP on Oxygen OS 3.2.1

Today I have faced a strange situation, I installed TWRP (after unlocking the bootloader) on my OP3 as soon as I received the device then I flashed custom ROM by @Grarak http://forum.xda-developers.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089.
After using for some days I decided to give Oxygen OS another try, so I wiped the cache,data,system and Flashed full OTA provided by @namanbhalla https://forums.oneplus.net/threads/...ficial-oxygen-os-roms-and-ota-updates.450783/
Every thing went smooth but after starting up I wasn't able to goto twrp, for some strange reason twrp was automatically replaced with stock recovery. OK, I decided to reflash twrp, but bang! after so many flashing I wasn't able to boot into twrp, still there was stock recovery.
Solution:
1) fastboot oem unlock (re run even if it says already unlocked)
2) fastboot flash recovery twrp-3.0.2-0-oneplus3.img
now TWRP is installed.
I not Android Developer and cant guarantee above will work and wont harm your device. Try at your own risk.

that is all not needed, i have had this happen to me multiple times reflashing Stock and Stock recovery replaces TWRP, all u have to do is boot up to fastboot mode and flash TWRP, do not reboot, use Power + Vol + and when the Unlocked bootloader screen comes up press the VOL key and click recovery and TWRP is back. no need to do the unlock bootloader again, unless u unchecked it, just make sure it is checked when flashing the Stock rom again or u can just use flashify if u rooted stock before the recovery got replaced somehow, i have even had this happen on FreedomOS 3.2.1

Custom recovery won't boot, how to procede?

I finally got around to rooting/etc my Z00AD, only to get stuck at the custom recovery stage.
I have found a dozen other identical cases on the forums, but sadly none have been resolved.
Rooting went swimmingly, and my bootloader also unlocked flawlessly (I believe). The new recovery (TWRP first) flashed over with no issues. Then I rebooted and selected 'recovery' from the fastboot menu, and the phone just reboots back into the fastboot stage. I can boot normally from there, just not to recovery. I have also tried flashing other recoveries, with no luck.
Since the ROM is still stock, I can boot to Android and it re-writes the recovery to stock after my custom recovery fails to boot.
My thoughts are that my bootloader did not unlock properly, even though installation itself seemed to go well. How should I 'redo' that process?
Any other thoughts?
FW Vers. WW Z00AD 2.20.40.195
Thanks everyone

Either reflash the correct recovery (download a fresh file, in case of faulty download) or follow unbricking instructions.
Verstuurd vanaf mijn ASUS_Z00A met Tapatalk

ztoundas said:
I finally got around to rooting/etc my Z00AD, only to get stuck at the custom recovery stage.
I have found a dozen other identical cases on the forums, but sadly none have been resolved.
Rooting went swimmingly, and my bootloader also unlocked flawlessly (I believe). The new recovery (TWRP first) flashed over with no issues. Then I rebooted and selected 'recovery' from the fastboot menu, and the phone just reboots back into the fastboot stage. I can boot normally from there, just not to recovery. I have also tried flashing other recoveries, with no luck.
Since the ROM is still stock, I can boot to Android and it re-writes the recovery to stock after my custom recovery fails to boot.
My thoughts are that my bootloader did not unlock properly, even though installation itself seemed to go well. How should I 'redo' that process?
Any other thoughts?
FW Vers. WW Z00AD 2.20.40.195
Thanks everyone
Click to expand...
Click to collapse
Have you tried booting into fastboot and typing "fastboot oem device-info" without the quotes? It should tell you whether your bootloader is truly unlocked. If it is unlocked I would boot into stock recovery, wipe the cache, and do a factory reset. Then you can try installing twrp again. Have you updated the SuperSu binaries? I'm no expert this is just what I would do.

Same problem here, it seems that 2.20.40.195 is the problem.
I can also do fastboot flash but anything but official recovery won't start and returns to bootloader. fastboot oem device-info returns FAILED (remote: unknown OEM command)
.
Is it possible to downgrade?

willcall said:
Have you tried booting into fastboot and typing "fastboot oem device-info" without the quotes? It should tell you whether your bootloader is truly unlocked.
Click to expand...
Click to collapse
....aaand it wasn't truly unlocked. While I didn't test it using your method, before reading your response I tried re-unlocking the bootloader, and I got the proper white background upon reboot (last attempt I flashed the original black background immediately after I thought I had unlocked the bootloader, thinking it was required. Thus I never had a repeated confirmation I had failed the unlocking).
After ACTUALLY unlocking the bootloader, each further step worked perfect. Running CM13 flawlessly.
2 days later I shattered my screen. oh well. Ordered a new screen, we'll see how I do with a hardware repair...

The terrible fate of refurbished N5X

Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?

Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.

negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.

CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?

negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.

CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.

negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader

sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot

Help needed in understanding bootloader.

So, I had an unlocked BL, rooted phone, with TWRP 3.3.1 deestroy.
For some reason, I booted into my recovery, wiped all my data, through format and advanced wipe feature. I even changed slots (just to make sure) and formatted data, and advanced wipe.
I then locked my bootloader, through adb fastboot command. Rebooted my phone, which had nothing to boot to. Then I unlocked my bootloader, rebooted my phone again, and it got booted into TWRP 3.3.1
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?

This might be helpful for you:
https://github.com/tkchn/daisyinstall

Lol. I didn't ask for how to flash a custom ROM.
Just need help understanding how the bootloader works? Where does TWRP get installed? Why after wiping did TWRP survive?

shazee666 said:
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?
Click to expand...
Click to collapse
Different things live on different partitions.
TWRP does not live on the userdata partition so wiping data cannot remove TWRP.
You need to use fastboot or miflash to do a full flash and restore a phone to stock.

Okay. This cleared somethings...

If you have tampered with the phone's partitions (TWRP patches itself into boot.img) you should never lock the Bootloader. Basically when the Bootloader is locked, the phone checks all the partitions of the phone if they've been tampered or still the same as Xiaomi designed it. In the case that they've been tampered, the phone won't boot itself, this helps with a lot of security issues. Never lock your Bootloader if you've made changes to the system, boot or other partitions (except userdata, this is why enabling cam2api and locking the BL won't mess up your device because the persist command stores the command in data partition). If you want to lock the BL, just flash the stock rom beforehand. Cheers.

Phone only boots to System from Bootloader - anything else boots to Recovery

Hi! I've unlocked bootloader, latest TWRP and Latest AICP. No root. The phone will never boot to System from power off, from TWRP or normal reboot.
It will, however boot normally from bootloader screen, when I choose Start.
Have already wiped every partition, tried to reinstall ROM, the problem always persists.
Any idea what is causing this?
Thanks

dainezi said:
Hi! I've unlocked bootloader, latest TWRP and Latest AICP. No root. The phone will never boot to System from power off, from TWRP or normal reboot.
It will, however boot normally from bootloader screen, when I choose Start.
Have already wiped every partition, tried to reinstall ROM, the problem always persists.
Any idea what is causing this?
Thanks
Click to expand...
Click to collapse
Did you remember to make fastboot oem fb_mode_clear?