So I unlocked my bootloader using ADB
Earlier I updated to october security patch
Does this mean I will get Android 10 or I should re-lock my bootloader
maiden04 said:
So I unlocked my bootloader using ADB
Earlier I updated to october security patch
Does this mean I will get Android 10 or I should re-lock my bootloader
Click to expand...
Click to collapse
Ya you will have to relock it or you won't get the update
garylawwd said:
Ya you will have to relock it or you won't get the update
Click to expand...
Click to collapse
Nothing like that my bootloader is unlocked from very first day & OTA has no issue
garylawwd said:
Ya you will have to relock it or you won't get the update
Click to expand...
Click to collapse
So I just have to use ADB tools to re-lock it and I'm ready to update?
maiden04 said:
So I just have to use ADB tools to re-lock it and I'm ready to update?
Click to expand...
Click to collapse
Only if you have made changes to your system wether it be root like magisk or something else you may have flashed. If you have magisk run the uninstaller from magisk manager and for twrp all you have to do is flash stock boot.img to get rid of it.
Make sure you uninstall root access before getting rid of twrp
As the guys said above me the bootloader shouldn't matter sorry for the misinformation
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.
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?
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
want know if i do Unlock Bootloader i will lose the update or no
No... You will lose nothing
typed through a vantablack POCOPHONE F1 using Tapatalk
tadtadros said:
want know if i do Unlock Bootloader i will lose the update or no
Click to expand...
Click to collapse
U will not lose update and stay on the same version. But you will lose all data and everything on the internal storage
if twrp is installed, do i lose the update feature?
zuhero said:
if twrp is installed, do i lose the update feature?
Click to expand...
Click to collapse
Twrp is a custom recovery only, why do you think the recovery would effect your updates any way if the unlocked bootloder wont..
shadow78 said:
Twrp is a custom recovery only, why do you think the recovery would effect your updates any way if the unlocked bootloder wont..
Click to expand...
Click to collapse
I thought xiaomi worked like samsung, once the knox is tripped, the system otas feature won't work...
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.