Develop Bugs

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

Best way to upgrade to O from current state? Stock 7.1.1 rooted.

So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!

If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.

simply flash the OTA, then re-root

xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O

Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!

xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.

quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.

gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.

Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe

toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!

Twrp and flashing a Rom

So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565

wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.

noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!

if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.

How to upgrade O+5T to OxygenOS 5.1.0 when rooted with stock recovery?

Greetings. I received the OTA update (which I did not install!) on my OnePlus 5T today. I'm on OxygenOS 5.0.4 with magisk installed, phone is rooted, bootloader unlocked, stock recovery (no TWRP).
What's the right path to upgrade to 5.1.0?
I'm experienced with the command line and have no problems with it.
Based on my ideas, I think the path should be:
- Download full Oxygen OS 5.1.0 Full Zip
- Start TWRP using adb
Code:
fastboot boot
(which TWRP version?)
- Wipe dalvik and cache
- Flash the downloaded file
- Wipe dalvik and cache
- Flash magisk
That's it. Am I missing something? Do I need to reinstall magisk as specified as last step? Which TWRP version should I use (from the official website?)?
Thanks for your help :good:

Please go through the dedicated update thread that ive made for the update
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
The thread has all the instructions and files needed to update. As far as twrp is concerned i recommend latest codeworkx or or bluspark recovery. The links are available on the thread.
Feel free to post on the thread if you have any further doubts.

Thanks @Funk Wizard , I read that thread (I linked it in my post) but it mentions "For Stock Non Rooted Users with Stock Recovery" and "For Rooted Users with TWRP Recovery" while in my case I'm rooted with STOCK recovery, which doesn't fit any of those 2 sentences. Which one should I follow?

As you are rooted you can flash the full zip from stock recovery that would remove root or you need follow and flash via twrp. If rooted stock recovery is no good TBH and i recommend staying on TWRP.
You can flash twrp from fastboot and then follow the instructions on the flashing post.
In case you dont need root anymore you can just flash the full zip from stock recovery. It will remove root and you will stay on stock recovery. In both the cases, use the full zip to flash via twrp or stock recovery.

No good? Please be more specific, why it's no good? From my understanding keeping stock recovery with magisk installed and bootloader unlocked allows me to pass all SafetyNet checks, which is very helpful if you don't want to deal with apps complaining that you are rooted. I can easily boot to TWRP as long as I can plug my phone into my computer by just using the fastboot command. The only downside I could see is if I brick my phone and have usb debugging disabled, I can't fastboot from adb.
Flashing TWRP would make me fail SafetyNet checks, which I'm not interested into.
After I flash the full zip, do I also need to flash the OTA update?
Thanks by the way, basically the only real "special" thing I need to do is install Magisk again after flashing.

Flashing twrp doesn't break safety net. So it's upto you if you want to stay on stock recovery with no additional benefits or on twrp.
Also, if have full time zip then you don't need to flash ota zip again.

That's good! I'll definitely flash twrp in that case.

@sshivampp Sorry to resurrect this thread, but looks like it's important. On TWRP website itself it's stated that installing TWRP would break dm-verity. What's the consequence of this? https://twrp.me/oneplus/oneplus5t.html

TWRP - Permanent Installation or Temp?

Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.

My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!

I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.