Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands
Related
Reverted back to "Locked" bootloader, but still get error when updating to 5.1.1 OTA
I just used Nexus Root Toolkit 2.0.5 to revert back to an OEM "Locked" state which I ahd confirmed by rebooting into bootloader. The reason I did this was so I would be able to update my device with OTA updates, but I keep getting an error every time I try to update to 5.1.1.
What are my options?
Unlock, flash Nexus Factory Images.
From what I've read if you get a failed OTA install it won't let you un-root, re-lock, etc... and take the OTA. This is to protect your device.
ETA: Do you even have to have the BL flag locked to take an OTA? I don't think so...
livinginavacuum said:
I just used Nexus Root Toolkit 2.0.5 to revert back to an OEM "Locked" state which I ahd confirmed by rebooting into bootloader. The reason I did this was so I would be able to update my device with OTA updates, but I keep getting an error every time I try to update to 5.1.1.
What are my options?
Click to expand...
Click to collapse
NEVER NEVER NEVER NEVER NEVER LOCK YOUR BOOTLOADER!!!!
1) This does not in ANY WAY impact OTAs.
2) This has the potential to *LOCK YOU OUT*.
Get your updates here:
https://developers.google.com/android/nexus/images
So then how can I go back to being able to update via OTA?
livinginavacuum said:
So then how can I go back to being able to update via OTA?
Click to expand...
Click to collapse
If you want to get OTA's, fastboot flash the stock system.img and boot.img > https://developers.google.com/android/nexus/images
But if you're going to do that, why not just fastboot flash the 5.1.1 factory images?
As posted above, do not relock your bootloader. It does not impact your ability to accept OTA's and can end up bricking your device.
cam30era said:
If you want to get OTA's, fastboot flash the stock system.img and boot.img > https://developers.google.com/android/nexus/images
But if you're going to do that, why not just fastboot flash the 5.1.1 factory images?
As posted above, do not relock your bootloader. It does not impact your ability to accept OTA's and can end up bricking your device.
Click to expand...
Click to collapse
Is there an idiot's proof guide to this?
And besides helping me unlock my device once again as you guys recommend, can the Nexus Root Toolkit make my life easier by flashing the the stock system.img and boot.img so that I can get OTA's?
livinginavacuum said:
Is there an idiot's proof guide to this?
And besides helping me unlock my device once again as you guys recommend, can the Nexus Root Toolkit make my life easier by flashing the the stock system.img and boot.img so that I can get OTA's?
Click to expand...
Click to collapse
Here's a guide. Note: use the "Long method" > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Toolkits are OK if you understand how to fix a problem when you run into trouble. I'd suggest that you use the manual method, but it's your decision. There's a thread in the Development section for NRT if you choose to go that way.
Due to a bug, I have been able to get root on my OnePlus 2 running Oxygen 2.1.1 without a wipe.
DISCLAIMER: This may not give you root on yours, and obviously it may also loose you data, so don't do it unless you know you can cope with that. YMMV, but I've documented here for posterity how to do it!
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
The basic steps are :
Encrypt your device
Unlock the bootloader (this won't wipe because of encryption!)
Boot TWRP
use adb to push SuperSu to your device and then flash it
Then you will have root. Step by step instructions below.
Note that TWRP currently doesn't support encryption on our devices, so you'll have to use something other than that to back up your data if you want to use a custom rom. This simply gives you rooted stock Oxygen.
After rooting :
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Step 1: Encrypt your device.
This is irritating but fairly simple. You have to have fully charged your device AND keep it plugged in, and it takes ~50 minutes to complete. It's the standard android encryption, so follow any guide for this, such as https://support.google.com/nexus/answer/2844831?hl=en-GB
Step 2: Unlock the bootloader.
Again, this is well documented - here's a guide : http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568 - The important thing is that if you're encrypted, this does not do a wipe, in my experience.
Step 3: Boot TWRP
Download TWRP from https://dl.twrp.me/oneplus2/ and save it somewhere you can find it later - I'm going to assume you're on linux and have saved it in ~/Downloads/TWRP.img
Reboot into bootloader mode (Power and Volume up) and start TWRP by issuing the following command (substituting your path to twrp) :
Code:
~$ fastboot boot Downloads/twrp-2.8.7.0-oneplus2.img
Step 4: Root it!
This is a bit tricky because once you're encrypted you can't access the SDCard, so you need a bit of magic to flash the zip.
First, do the swipe to enable modifications, then in mount, tick the /system option.
Then, on your PC, download SuperSU's .zip update from https://download.chainfire.eu/696/supersu/ (similar to above, assuming same download location) and use adb push to put it on the device in /tmp :
Code:
adb push Downloads/UPDATE-SuperSU-v2.46.zip /tmp/su.zip
Next, from the main TWRP menu, select Install. Navigate up (you start in sdcard that is empty) and into tmp, then select the su.zip file in there.
Swipe to install the zip - TWRP will complain because it can't access /data, but handily, /data is not needed to root!
Select Reboot, and viola, you have SuperSU and root! Now you can install Titanium Backup and back up your device.
Cool, perhaps renaming the title like "Unlock and root without wiping" could make more sense?
ranyardm said:
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
Click to expand...
Click to collapse
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Spannaa said:
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Click to expand...
Click to collapse
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
ranyardm said:
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
Click to expand...
Click to collapse
Maybe my post should have said "OTAs don't re-lock the bootloader since 2.1.0"
Anyway, if your method works then great :good:
There's another way to do it here.
Can everyone who's done this attest that the data indeed doesn't get wiped?
cheekrox said:
Can everyone who's done this attest that the data indeed doesn't get wiped?
Click to expand...
Click to collapse
I'd also be very happy to have this confirmed by another party!
Confirmed. Data does NOT get wiped.
cheekrox said:
Confirmed. Data does NOT get wiped.
Click to expand...
Click to collapse
Confirmed on 2.2.0 or still on 2.1.X?
Can confirm, this still works on 2.2.0.
i didnt try this tutorial, but when i rooted my phone, my data didnt got wiped either.
will root on 6p running android n dev preview wipe phone?
Any chance this works also on 1+1? I'm desperate for a way to root without unlocking so I can install titanium/nandroid and do a full proper backup before wiping clean (battery life is utter crap). Running latest stock 6.01 COS. Never unlocked, never wiped since 15R.
Thanks!
anyone tried this on OOS 3 ?
Yeah, bump!
Now my OP2 is on Oxygen 3.0.2, and Android 6.0.1 - stock.
My phone had always been (bootloader) unlocked and rooted, since the day after I got it.
But to get the new OTA update to Oxygen 3, I tried a different method this time, where some people said you can do a temporary un-root, get the stock OTA update, and then re-root.
I followed their instructions, but I can't re-root as simple and easy as they said.
Before the process, I didn't do a nandroid backup because my sdcard doesn't have room :-|
So now I need to re-root without losing data.
And I've tried helium before, many times, and it never works for me.
Any other ideas, or has anyone tried this encryption trick yet with Oxygen 3?
Thanks!
tried it on oos 3.1:
everything worked until a bootloop at the last restart.
also twrp asked me to unlock the phone, i did that.
what to do now?
Did anyone ever have any success with this approach on 3.1?
LoL How do you boot/flash TWRP on locked bootloader?
aIecxs said:
LoL How do you boot/flash TWRP on locked bootloader?
Click to expand...
Click to collapse
Lol, you can't.
Basically the title. Is there a difference?
Also, I have a RN3P-Kate. I'm seeing there are a few methods to root and install TWRP. Which is the easiest/safest/best way?
No, it's not the same thing.
They are all pretty much the same, you need to have an unlocked bootloader (request from xiaomi), then you go to fastboot mode, install TWRP through fastboot, and then you can flash supersu to root.
goofball2k said:
No, it's not the same thing.
They are all pretty much the same, you need to have an unlocked bootloader (request from xiaomi), then you go to fastboot mode, install TWRP through fastboot, and then you can flash supersu to root.
Click to expand...
Click to collapse
Thanks!
Will I still receive OTA updates if I root, or will I have to manually update (via flashing) and reroot again?
oroboros74 said:
Thanks!
Will I still receive OTA updates if I root, or will I have to manually update (via flashing) and reroot again?
Click to expand...
Click to collapse
You'll have to manually update and then reroot.
goofball2k said:
You'll have to manually update and then reroot.
Click to expand...
Click to collapse
I'm getting some conflicting information about this. According to some people on reddit, if I use Global Dev for example, I would need to unlock the bootloader to change from Global Stable to Dev, and then Dev would offer OTA (maintaining bootloader unlocked, i.e. staying rooted), or am I misunderstanding this?
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.
Hi,
I'm using HD01BA (= EU version) with unlocked bootloader and root with Magisk. I understand that updating OOS or updating Magisk is quite annonying as there's no TWRP and as it needs specific precautions such as disabling Magisk modules and reinstalling them after updating.
Since I now barely use root, I think I would benefit more from being able to get OTA updates than having root. I'd like to know how to unroot - and relock bootloader if necessary - without bricking the phone.
Would I have to wipe everything ? Will unrooting enable OTA updates or do I need to relock bootloader as well ?
Thanks
Edit : Wrong category, I asked moderators to delete this and have posted it in Questions & Answers
Use MSMTool. it will take care everything for you.
Lossyx said:
Use MSMTool. it will take care everything for you.
Click to expand...
Click to collapse
Thanks for the reply. Will it erase all data ? Will it relock bootloader ?
DrBazinga said:
Thanks for the reply. Will it erase all data ? Will it relock bootloader ?
Click to expand...
Click to collapse
It will erase everything and lock the bootloader, yes.
Is there a way to only unroot (flashing a clean boot maybe?) in order to get OTA updates? Even if the bootloader remains unlocked
DrBazinga said:
Is there a way to only unroot (flashing a clean boot maybe?) in order to get OTA updates? Even if the bootloader remains unlocked
Click to expand...
Click to collapse
Yes you can unroot by flashing stock boot.img, but why?
You get new updates when they are available through system updates in your settings/updater app regardless of the bootloader/root conditions.
The additional steps that has to happen after the OOS update is to keep Magisk/root.
Hw4ng3r said:
Yes you can unroot by flashing stock boot.img, but why?
You get new updates when they are available through system updates in your settings/updater app regardless of the bootloader/root conditions.
The additional steps that has to happen after the OOS update is to keep Magisk/root.
Click to expand...
Click to collapse
I don't think I do, I'm still on 10.0.9 and there's no update showing up, even in the settings. I remember reading somewhere that on this phone, unlocking bootloader or rooting (I forgot which one) disables updates notifications.
What bothers me is that i) if I want to update OOS I need to delete all Magisk modules then reinstall them to avoid bootloop and ii) if I want to update Magisk, I'd have to do all the steps again including flashing a patched boot, right ?
In addition, Magisk may no longer be able to hide bootloader unlocking from apps with Android 11.
DrBazinga said:
I don't think I do, I'm still on 10.0.9 and there's no update showing up, even in the settings. I remember reading somewhere that on this phone, unlocking bootloader or rooting (I forgot which one) disables updates notifications.
What bothers me is that i) if I want to update OOS I need to delete all Magisk modules then reinstall them to avoid bootloop and ii) if I want to update Magisk, I'd have to do all the steps again including flashing a patched boot, right ?
In addition, Magisk may no longer be able to hide bootloader unlocking from apps with Android 11.
Thanks
Click to expand...
Click to collapse
You can use Oxygen Updater https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
And the bootloader unlock check is Google's doing with hardware key attestation. This may not get cracked.