Database Info

[Q] If I update a rooted device OTA, will I have to run OEM unlock to root again

Hi,
I have an LG Nexus 5 (KTU84P, or "hammerhead") running Android KitKat 4.4.4. It is rooted using Chainfire's AutoRoot for the Nexus 5 for Android 4.4.4, and I have no custom ROM, simply Vanilla Android but with SuperSU. I am looking to update to Android L, version 5, and I have received a notification for the OTA update.
I understand that with OTA updates, your data will not be wiped, but you will lose root access. I have researched ways to keep the root, but they only appear to be for older versions of Android. I understand that I will lose root.
My question is, will I have to run the "oem unlock" (which I understand is the part of the whole rooting process which actually wipes your device), or will I just have to load Chainfire's AutoRoot? If I go through with it, I will use his AutoRoot for hammerhead for Android L, but basically my end goal is to root and update and not lose any data.
Thanks, if you need more info, let me know?

Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.

Nope. Once unlocked it stays unlocked unless you lock it yourself

frenziedfemale said:
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Click to expand...
Click to collapse
musclehead84 said:
Nope. Once unlocked it stays unlocked unless you lock it yourself
Click to expand...
Click to collapse
Thank you both very much!

Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware

rootSU said:
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
Click to expand...
Click to collapse
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?

AudaxNovus said:
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
Click to expand...
Click to collapse
If its unlocked, it can't be unlocked again.

Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.

D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
Odd. Hasn't locked for anyone else afaik

D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
There's a REALLY easy way to test that theory.
Open the factory image archives and check the script. Unless it runs 'fastboot oem lock' it isn't relocking it.
#stayparanoid

Don't you think this makes the trick?
"fastboot flash bootloader bootloader-hammerhead-hhz12d.img"

SAFE rooting to HUAWEI MATE 9

hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all

one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting

Thx to reply. Like the others i wanna root to have root apps in my phone ,

Thx . Wanna have apps requires root in my phone . That simple

You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+

super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action

nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.

ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!

I failed install su however still waiting for any updates

nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?

ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!

FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.

Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk

FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD

ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310

nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.

mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
 @st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.

mr. ante0 ..... u r the man , thank you so much

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

TWRP error honor 8 l19

Hi. I have a problem when flashing TWRP on my honor 8 L19. I have unlocked bootloader the official way and Emui 5.0 Android 7.0. When trying to flash TWRP through ADB I get the error: Failed(Remote: Command not allowed) I have tried different TWRP files. I can't factory reset as the recovery needs an update to work properly. I wonder if you have some idea or solution for me? Is there any official software that I can flash? Or point me to some help sites?
Mvh Jonas

Put your twrp file in the adb folder. Open command prompt while you're in that folder

Rommco05 said:
check FRP status in fastboot, is locked or unlocked?
Click to expand...
Click to collapse
FRP is locked. What is FRP?

zakariya tomal said:
Put your twrp file in the adb folder. Open command prompt while you're in that folder
Click to expand...
Click to collapse
That's what I always do. There is no problem with ADB only that it will not overwrite rescue partition.

Rommco05 said:
This is the problem... Is only one way, you need to make rollback to Marshmallow, isn't another
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
FRP is security feature by Google. Try find on Google more info
---------- Post added at 08:19 PM ---------- Previous post was at 08:15 PM ----------
After rollback check this:
https://forum.xda-developers.com/ho...m-roms-tested-openkirin-t3638445/post73072337
edit: OEM is in developer section
Click to expand...
Click to collapse
Thanks for fast reply. I will try the rolback to mashmallows. Found the nessesery files on Honors support sites.
I will take a look on the link after that.
Jonas

Falkemann said:
Hi. I have a problem when flashing TWRP on my honor 8 L19. I have unlocked bootloader the official way and Emui 5.0 Android 7.0. When trying to flash TWRP through ADB I get the error: Failed(Remote: Command not allowed) I have tried different TWRP files. I can't factory reset as the recovery needs an update to work properly. I wonder if you have some idea or solution for me? Is there any official software that I can flash? Or point me to some help sites?
Mvh Jonas
Click to expand...
Click to collapse
in developer option tick the oem unlocking

Rommco05 said:
Whit unlocked bootloader he can't, is greyed
Click to expand...
Click to collapse
no bro , whrn i was in nougat emui ,i was able to switch

Rommco05 said:
With unlocked bootloader? I don't think so, if is this able no one have problems with FRP
Click to expand...
Click to collapse
yes with bootloader unlock

Rommco05 said:
Whit unlocked bootloader he can't, is greyed
Click to expand...
Click to collapse
Have to agree. it was greyed out. Have now done the rollback sucessfully and i oem unlocking i switchable. I have run the phone for some days and it working well on mashmallows. I will now proceed with twrp, backup, root and upgrade to nougat. . Shall i leave OEM unlocking enabled then?

That answer was lightning fast, were you sitting just waiting for me to answer ??

Upgrade to nougat?
I have now unlocked bootloader. OEM unlocked Active, marshmallows, twrp and root. Everything works smooth and perfect When i upgraded to nougat the phone returned to locked bootloader again and (i think) locked OEM. So i had to do the whole process again . Is there any way to upgrade to nougat without getting locked bootloader and OEM? Or is there any nougat Rom thats works?

Falkemann said:
I have now unlocked bootloader. OEM unlocked Active, marshmallows, twrp and root. Everything works smooth and perfect When i upgraded to nougat the phone returned to locked bootloader again and (i think) locked OEM. So i had to do the whole process again . Is there any way to upgrade to nougat without getting locked bootloader and OEM? Or is there any nougat Rom thats works?
Click to expand...
Click to collapse
we cannot stop the locking process while updating,you have to unlock again and root.
there is nougat ROM check this --> https://forum.xda-developers.com/honor-8/development/frd-l09-tastynoogat-v1-0-04-12-17-t3588491

venugopalu007 said:
no bro , whrn i was in nougat emui ,i was able to switch
Click to expand...
Click to collapse
@Rommco05 is right. There is no way to turn it on or off because the OEM unlocking button is not solid anymore.

Then talk after seeing this

Rommco05 said:
Good one man, how you do it? Is some magic on your phone because I can't and other members too
Click to expand...
Click to collapse
I just unlock the bootloader after the update of EMUI 5.0.

Rommco05 said:
You unlock bootloader in M and after make upgrade to Make, right? Hm I have H8 will try...
Click to expand...
Click to collapse
no ,i remained locked in emui 4.1 and after updated to emui 5.0 , i unlocked the bootloader

Rommco05 said:
I doing the same but was can't switch this option, after first u setup Google account or skip them?
Click to expand...
Click to collapse
After emui 5.0 updated , i done setup the google accounts.

venugopalu007 said:
Then talk after seeing this
Click to expand...
Click to collapse
It's custom ROM. Show it in stock if it's possible

Saeem said:
It's custom ROM. Show it in stock if it's possible
Click to expand...
Click to collapse
Dafaq .. it is stock bro

Have a look here. Right after unlocking.....
Hmmm

Relock Bootloader with Non-MIUI ROM

Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.

vibranze said:
Hello, not sure if someone has asked the same question before but is it possible to relock the bootloader with a custom ROM and not MIUI official ROM?
The main reason behind the question is I want a pure pixel experience ROM and due to an unlocked bootloader and root, I can't use some banking and company apps even with MagiskHide so I'm thinking of relocking the bootloader and unroot and at the same time maintaining the custom ROM.
I'm using a Pixel Experience ROM btw.
Thank you.
Click to expand...
Click to collapse
Afaik not possible..i mean if u lock bootloader on any custom rom or even official with modifications u will stuck at bootlooop. dm verity

As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.

Which version of magisk are you using, it should be better with hiding stuff in the latest verison

huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
Interesting, I am wondering if it is MIUI thing.
malimukk said:
Which version of magisk are you using, it should be better with hiding stuff in the latest verison
Click to expand...
Click to collapse
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.

huyizheng said:
As far as I know, relock the bootloader is not possible.
However, it's possible to hide the bootloader unlock status without installing magisk. For example, xiaomi.eu's ROM hides it, and SafetyNet passes without magisk. But I don't know how to do this.
Click to expand...
Click to collapse
You dont have to do anything. Simply Install their Rom and IT will Work directly. Used Banking Apps etc without a Problem on their Rom

vibranze said:
Interesting, I am wondering if it is MIUI thing.
Thank you, I am using Magisk 18. Some of my apps still force me to close even after I added it in MagiskHide.
Click to expand...
Click to collapse
I've found with a few apps that I had to turn off USB debugging as well, before it would let me use them. Maybe give that a try.

!!SOLVED!! Brand new U11 says ***RELOCKED***

Hi
I just ordered a "brand new unlocked" U11 on eBay from a decent seller which arrived in an unopened package everything fully sealed and wrapped.
I want to flash TWRP and Magisk root which I have done with my previous M9 and HTC 10, however, I'm getting ***RELOCKED*** and ***Software status: modified*** in Download mode and Bootloader before I've done anything to it - see pics.
Its arrived with Android 9 on it and June2019 Security patch and I don't get any OTA's
I'm in Australia on Telstra network.
Am I OK to unlock Bootloader via HTC dev and flash TWRP and Magisk or do I need to RUU this thing?
Thanks.

Bump

HsHTCsen said:
Bump
Click to expand...
Click to collapse
no, just unlock the bootloader as you've done before then flash twrp, then flash magisk if you want root.
be sure to go into developer options and enable oem unlock for bootloader and usb debugging(do this before flashing twrp). and also flash magisk after twrp before you boot to system.
flash-- twrp-3.3.1-0-ocn.img

Aldo101t said:
no, just unlock the bootloader as you've done before then flash twrp, then flash magisk if you want root.
be sure to go into developer options and enable oem unlock for bootloader and usb debugging(do this before flashing twrp). and also flash magisk after twrp before you boot to system.
flash-- twrp-3.3.1-0-ocn.img
Click to expand...
Click to collapse
Thank you for the reply! I ended up emailing a recognized dev and what you just told me is everything they said which I have done and all has worked 100%.
Thanks again for taking the time.