Develop Bugs

Question regarding stock apps and other things...

Hi!
I got an M8 a few weeks ago, and regretfully wasn't thinking and allowed a few OTA updates.
So I was at firmware version 2.22.531.5, Android 4.4.3. There were 2 other OTA updates pending that I ignored because I realized that it may make it harder to root or s-off. I realize now I already performed the updates which would make Firewater not work.
I unlocked the bootloader, and flashed TWRP 2.8.0.1, then flashed the latest SuperSU.
Now the update notices stopped.
Few questions:
1. Does anyone know what updates beyond the version above were sent OTA, and how beneficial these updates are?
2. I'll probably get sunshine...but might wait. Can I install a different ROM without S-off?
3. Since I'm at 4.4.3, I may stay with stock until 4.5 (or whatever L is). But I definitely want to get some junk off the phone. I was going to use Titanium and uninstall a bunch of stuff... I have had a few HTC phones before and could identify what apps were part of the ROM framework, but it's not as easy to discern what apps I need to keep on this phone. Does anyone know of a thread that talks about what stock apps can be uninstalled? Or, in the alternative, if you have deleted apps, can you let me know which ones?
I know that's a lot of questions... Thank you in advance for any answers!

syntropic said:
Hi!
I got an M8 a few weeks ago, and regretfully wasn't thinking and allowed a few OTA updates.
So I was at firmware version 2.22.531.5, Android 4.4.3. There were 2 other OTA updates pending that I ignored because I realized that it may make it harder to root or s-off. I realize now I already performed the updates which would make Firewater not work.
I unlocked the bootloader, and flashed TWRP 2.8.0.1, then flashed the latest SuperSU.
Now the update notices stopped.
Few questions:
1. Does anyone know what updates beyond the version above were sent OTA, and how beneficial these updates are?
2. I'll probably get sunshine...but might wait. Can I install a different ROM without S-off?
3. Since I'm at 4.4.3, I may stay with stock until 4.5 (or whatever L is). But I definitely want to get some junk off the phone. I was going to use Titanium and uninstall a bunch of stuff... I have had a few HTC phones before and could identify what apps were part of the ROM framework, but it's not as easy to discern what apps I need to keep on this phone. Does anyone know of a thread that talks about what stock apps can be uninstalled? Or, in the alternative, if you have deleted apps, can you let me know which ones?
I know that's a lot of questions... Thank you in advance for any answers!
Click to expand...
Click to collapse
1, pretty sure that's latest update
2, u can still install custom roms etc. u won't be able to downgrade firmware/change variant of m8 without s off
3, Check HERE

Thank you!
I had one follow up question...
If I had just gone with sunshine from the start (and not gone with the token from HTC to unlock the bootloader), would I have still gotten OTA updates?
Which change (custom recovery, unlocked bootloader) stops the OTA updates?
Thanks to anyone again in advance!

syntropic said:
Thank you!
I had one follow up question...
If I had just gone with sunshine from the start (and not gone with the token from HTC to unlock the bootloader), would I have still gotten OTA updates?
Which change (custom recovery, unlocked bootloader) stops the OTA updates?
Thanks to anyone again in advance!
Click to expand...
Click to collapse
you would have been fine with OTA from the start, the following stops OTA updates:
custom recovery installed
missing system apps removed
incorrect firmware etc

You can freeze apps with Titanium, and if doing so doesn't cause any issues, go ahead and uninstall.

exocetdj said:
you would have been fine with OTA from the start, the following stops OTA updates:
custom recovery installed
missing system apps removed
incorrect firmware etc
Click to expand...
Click to collapse
Ok...But before I read this, I was just going through settings and I checked the "check for updates" section, and it wants to install firmware version 2.22.531.6. So maybe if you are still using stock (despite installing custom recovery), you still get OTA updates?
The update sounds minor given it's incremental version (but tmous/HTC claims it's for important security updates), and I'd probably ignore it... But unfortunately, because I checked in the first place and perhaps because I'm on stock (minus a few apps I'm trying to delete: Amazon, Facebook, Kid Mode), for whatever reason the update reminder stays in my notifications and is pretty insistent.
Can I install this without calamity?
Thank you!

syntropic said:
Ok...But before I read this, I was just going through settings and I checked the "check for updates" section, and it wants to install firmware version 2.22.531.6. So maybe if you are still using stock (despite installing custom recovery), you still get OTA updates?
Click to expand...
Click to collapse
You will get the OTA notification just fine with custom recovery, and it will download as well. The problem is, when you go to install, OTA requires stock recovery and will fail when it doesn't find it. Might also bootloop looking for stock recovery, can't remember exactly.

redpoint73 said:
You will get the OTA notification just fine with custom recovery, and it will download as well. The problem is, when you go to install, OTA requires stock recovery and will fail when it doesn't find it. Might also bootloop looking for stock recovery, can't remember exactly.
Click to expand...
Click to collapse
Oh boy... So what's the solution? It finally downloaded on its own and is now pestering me to install. I don't want to deal with a bootloop. ****...
Can I delete the update from recovery, it just disable the updater and delete it?
What are my options? Thanks!!

syntropic said:
Oh boy... So what's the solution? It finally downloaded on its own and is now pestering me to install. I don't want to deal with a bootloop. ****...
Can I delete the update from recovery, it just disable the updater and delete it?
What are my options? Thanks!!
Click to expand...
Click to collapse
The OTA zip should be in your download folder on internal memory, delete this then uncheck auto update checking and u should be without the constant notifications.
If you want to update, u will need to reinstall a fresh nand with all stock apps included

exocetdj said:
The OTA zip should be in your download folder on internal memory, delete this then uncheck auto update checking and u should be without the constant notifications.
If you want to update, u will need to reinstall a fresh nand with all stock apps included
Click to expand...
Click to collapse
I think I'm going to do this (install nand). I am going to get sunshine/s-off, then flash fresh stock RUU... will I still need to then lock bootloader?
Could you just give me a short list of steps to do this? I want to lock bootloader with s-off because I want get the @$&)!& HTC free 100GB Google Drive promo and all the updates.
I really appreciate it Archer...

No problem
1, sunshine s off
2, Flash relevant nand/firmware
3, use this guide to stock lock (not relock) bootloader HERE
4, u will have a stock m8 with S off ready for future OTAs (remember not to remove any apps preinstalled in the nand)
not sure of the 100GB promo as i use dropbox lol :silly::highfive::good:
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
syntropic said:
I think I'm going to do this (install nand). I am going to get sunshine/s-off, then flash fresh stock RUU... will I still need to then lock bootloader?
Could you just give me a short list of steps to do this? I want to lock bootloader with s-off because I want get the @$&)!& HTC free 100GB Google Drive promo and all the updates.
I really appreciate it Archer...
Click to expand...
Click to collapse
see above buddy

exocetdj said:
see above buddy
Click to expand...
Click to collapse
Cool... And I have read that as long as you do it that way (using echo -ne '\x00....' and not "fastboot oem lock" when in fastboot mode with adb running) you will get "***LOCKED***" back and not RELOCKED.
When it's RELOCKED Google can't confirm your information so the promo won't work...But if locked, you can do it.
Now I just have to do it all..
Thanks!!

syntropic said:
Cool... And I have read that as long as you do it that way (using echo -ne '\x00....' and not "fastboot oem lock" when in fastboot mode with adb running) you will get "***LOCKED***" back and not RELOCKED.
When it's RELOCKED Google can't confirm your information so the promo won't work...But if locked, you can do it.
Now I just have to do it all..
Thanks!!
Click to expand...
Click to collapse
U are all set dude

OTA Update? How shall I do it when rooted and unlocked?

So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?

You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.

Twrp is working fine but I have nothing to flash to test...????

networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build

Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon

So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.

I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks

s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.

What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.

DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.

TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks

jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.

TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk

I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.

If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.

jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.

TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk

Sideloading OTA vs flashing full factory image

I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?

There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.

Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.

savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...

5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?

sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...

sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...

5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.

savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...

5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.

sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...

sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/

alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...

alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.

Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/

savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...

PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.

shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.

PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.

Secure Boot: Enabled (no RPMB)

Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?

Banan PL said:
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Click to expand...
Click to collapse
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Click to expand...
Click to collapse
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs

Banan PL said:
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
There's a temporary workaround if you're a stock rooted user:
Here's a reddit link regarding a workaround:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
However, this isn't helpful if you're a regular custom rom user as you'll notice in the details.
As for DRM, I think so. I have been looking for confirmation about DRM being impacted by this "No RPMB" status. I've only seen one other person outright mention this. It's hard to find users who get this issue and even harder to get them to respond on my inquiry on whether they can use DRM apps. What issue are you seeing with Play Movies? Can you open the app? Or are you given an error message of any kind? I'm interested from the troubleshooting perspective so that I can help ID when others have the same issue. Also, can you confirm this affects other multimedia apps with DRM protection? I was thinking that Hulu, Netflix, HBO would be apps that utilize DRM if you have subscriptions.
Sent from my Nexus 5X using Tapatalk

I don't care much about custom OS, at least for now. I can open Play Movies browse feed and library, but it ain't play any video (Couldn't fetch license (error -1)). Unfortunately I don't have subscriptions in these services, but I used local TV streaming app that uses DRM and it showed error 203 (whatever that means). I tried also watch movies from Google's app on YouTube, no luck.
Sent from my Nexus 5X using XDA Labs

Hi there, same case, no rpmb after replacing motherboard, Netflix won't start (error 500 device failure). Tried with stock but now PureNexus rom.
Sent from my Nexus 5X using Tapatalk

send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb

tuningsea said:
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
Click to expand...
Click to collapse
Thanks for the advise, however I want to find a way to create this Rpmb at home, for users who warranty has gone, still looking..
Sent from my Nexus 5X using Tapatalk

Netflix norpmb
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused

kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
I confirm it's working. Has anybody found a different solution for no rpmb from the one posted on reddit?
Inviato dal mio Nexus 5X utilizzando Tapatalk

kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
Netflix app will crash few times, try to hide with Magisk Btw. Re open few times, like 10 and login. Then you will be redirected to the homepage.
Envoyé de mon Nexus 5X en utilisant Tapatalk

hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!

androidfreak11 said:
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
Click to expand...
Click to collapse
I'm also looking for a solution all the time
but I haven't found one yet

openyourmind said:
I'm also looking for a solution all the time
but I haven't found one yet
Click to expand...
Click to collapse
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs

Banan PL said:
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
i was able to flash stock rom via fastbook (had to unlock bootloader 3 times, everytime it rebooted, but it worked tho)
only problem, when i install twrp and press reboot phone, it will only boot to twrp! and i have to type in a decription password or something, because i unlocked the bootloader and android should have deleted everything, but didn't cause i would have to reboot for that, but it will only boot in twrp .. so yeah, that's where i got stuck .. any idea?
otherwise i'll resell this thing and maybe get an htc 10 or a nexus 5x with stock mobo

Hi all,
I currently have stock 8.1 installed on my refurbished Nexus 5X with NO RPMB, and would like to install a custom ROM (Pixel2ROM from argraur).
If possible, I prefer NOT to get root. Maybe it helps passing safetynet.
As I understood, I should do following steps:
- Unlock bootloader
- Flash stock ROM. -> Is this step necessary since I already have stock 8.1 installed?
- Flash TWRP
- Reboot directly into TWRP
- Wipe data and cache
- Flash custom ROM
- Flash Magisk or superSU -> Without this step, would TWRP get replaced with stock recovery? Is Magisk or superSU better?
Can you please check if the steps are right, and answer the 3 questions.
Thanks!
EDIT: I tried without flashing the stock ROM nor root. Everything went fine and TWRP remains installed.

Hello I created a thread trying to help with this cases.. If someone with better knowledge see a better option, please say it there to update it..
NO RPMB (how to install TWRP, a new ROM and using Magisk)

Hi Pedro,
what will happen in case of rom update? e.g. Nightly?

ciorci said:
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
Click to expand...
Click to collapse
Without the magisk part its like you are using a normal rom with a normal boot image, just need to dirty flash the new rom..
With the magisk part it would need to make a new patched boot image..
So at least you will need to extract the new boot image of the new rom file, use it on magisk and patch it, after that I dont know... to my method work the first time it was needed a clean installation, but didn't tried it yet because the new update of my rom developer needed to be a clean installation due to many changes on the rom, so i didn't have opportunity to try update normally but when I do I will update my thread with what to do on that case and if it works..

Repairing damaged recovery partition on Huawei Y560-U02 - Solved

I watched a few videos on YouTube on how to upgrade the Android O/S but none of them mentioned that it needs to unlock the bootloader 1st.
So before I found out that I need to unlock it I tried installing ROM before I knew that.
The phone came with Android Kitkat 4.4.2 and there is an official Lollipop for it that I want to install.
The device is rooted with Kingroot.
I tried the installations two times and the phone still works but I can no longer boot into recovery mode or fastboot mode. It just hangs and then I need to remove the battery to get it to work again.
I just want to restore it back to what it was before and then I will work on unlocking the bootloader.
I prefer to use tools that are free of cost.

Issue has been resolved.
I flashed the device with a pac file using SPD upgrade tool and now all is back to default.

Johncoool said:
Issue has been resolved.
I flashed the device with a pac file using SPD upgrade tool and now all is back to default.
Click to expand...
Click to collapse
Hi. I recently messed up my phone (Y560-U02)! Please help me.
Can you please tell me where I can find the "pac file" and "SPD upgrade tool"?
Johncoool said:
there is an official Lollipop for it that I want to install.
Click to expand...
Click to collapse
You meant un-official, right?

Sorry for the delay. I check the linked email once per month.
Do you still need help on this?
I thought that it was official Lollipop. But it does not exist for this phone.
Yes I can help you get it to what ever you need but it is not easy if you want to do more than just resorted it back to default.
I will tell you more if you still need it.