I am wondering if I should root my new device, but I'd like to keep the security benefits too (and SafetyNet might need locked bootloader in the near future), so I would only do it if relocking is possible. Has anyone tried to relock the bootloader after patching with Magisk and signing the boot.img?
geiszla said:
I am wondering if I should root my new device, but I'd like to keep the security benefits too (and SafetyNet might need locked bootloader in the near future), so I would only do it if relocking is possible. Has anyone tried to relock the bootloader after patching with Magisk and signing the boot.img?
Click to expand...
Click to collapse
Don't ever do that u loose fingerprint or u end up in a bootloop because of the persist partition and the bootloader whats getting corrupt. Only when you are on a normal or stock firmware u can lock your bootloader without issues.
mastersjef said:
Don't ever do that u loose fingerprint or u end up in a bootloop because of the persist partition and the bootloader whats getting corrupt. Only when you are on a normal or stock firmware u can lock your bootloader without issues.
Click to expand...
Click to collapse
I wouldn't change any other partition except replace the boot.img, but I would sign that one too. What do you mean by bootloader getting corrupt?
geiszla said:
I wouldn't change any other partition except replace the boot.img, but I would sign that one too. What do you mean by bootloader getting corrupt?
Click to expand...
Click to collapse
Because the relock locks the bootloader and the bootloader is patched how you wanna do that?
mastersjef said:
Because the relock locks the bootloader and the bootloader is patched how you wanna do that?
Click to expand...
Click to collapse
The bootloader is not patched, it's just unlocked than locked. When it's unlocked, it doesn't check the signatures of the loaded components, when it's locked, it does. It won't boot if any of the system components is not signed, but I can sign the changed boot image and then it should boot just fine. At least in theory... I've seen a few people who's done it even with custom ROM and recovery, but I haven't done it before and don't know if it would work with the OP8.
I know it also depends on the signature verification method used by the bootloader and I think OnePlus devices use AVB, but not sure about that either and don't want to brick my brand new device
geiszla said:
I wouldn't change any other partition except replace the boot.img, but I would sign that one too. What do you mean by bootloader getting corrupt?
Click to expand...
Click to collapse
How do you sign the boot.img?
rossrosh007 said:
How do you sign the boot.img?
Click to expand...
Click to collapse
I too would like to know more about this.
It would be nice to be able to run your own boot image and re-lock the bootloader.
Related
Is there any way to root the Oneplus without unlocking the bootloader and wiping the device?
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
stone1269 said:
Is there any way to root the Oneplus without unlocking the bootloader and wiping the device?
Click to expand...
Click to collapse
yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.
---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------
zephiK said:
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Click to expand...
Click to collapse
thats a terrible analogy. thats like saying "ill bulldoze this whole wall and then ill never need to unlock my door!"
zephiK said:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
Click to expand...
Click to collapse
I want to avoid unlocking the bootloader simply because I have everything set up on the phone the way I like, and do not want to wipe it. I know I should have rooted it before installing anything, but nothing I can do about that now....
The Jack of Clubs said:
yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------
Thanks for the suggestion! I will give it a try.
The Jack of Clubs said:
yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty."
Click to expand...
Click to collapse
I'm a bit lost here....
To root the phone with locked bootloader, man has to have an "exploit"...which is not discovered (yet) for OPO.
And now you are saying that the exploit and hence an unlocked bootloader is not needed and we can just push SuperSU into system via adb....
Please elaborate how it's possible?????
RalphLauren said:
I'm a bit lost here....
To root the phone with locked bootloader, man has to have an "exploit"...which is not discovered (yet) for OPO.
And now you are saying that the exploit and hence an unlocked bootloader is not needed and we can just push SuperSU into system via adb....
Please elaborate how it's possible?????
Click to expand...
Click to collapse
What he said. The OPO does not need a "exploit" to root the phone with a locked bootloader because you can unlock it simply by typing a command.
You can't flash SuperSU without having access to a custom recovery such as TWRP/CWR which requires a unlocked bootloader.
zephiK said:
What he said. The OPO does not need a "exploit" to root the phone with a locked bootloader because you can unlock it simply by typing a command.
Click to expand...
Click to collapse
I think you mixing the things up.... I'm NOT talking that a man needs to have an exploit in order to unlock bootloader.
I'm wondering if OPO system (or better to say CM) designed in a such way that it can be indeed rooted without exploit and with still locked bootloader by simply pushing SuperSU.
That what I want to hear from @The Jack of Clubs.
zephiK said:
You can't flash SuperSU without having access to a custom recovery such as TWRP/CWR which requires a unlocked bootloader.
Click to expand...
Click to collapse
Of course you can by simply booting into whatever recovery in adb. I do not need a custom recovery and never install it.
RalphLauren said:
I think you mixing the things up.... I'm NOT talking that a man needs to have an exploit in order to unlock bootloader.
I'm wondering if OPO system (or better to say CM) designed in a such way that it can be indeed rooted without exploit and with still locked bootloader by simply pushing SuperSU.
That what I want to hear from @The Jack of Clubs.
Of course you can by simply booting into whatever recovery in adb. I do not need a custom recovery and never install it.
Click to expand...
Click to collapse
No you cannot root the phone without a exploit with a locked bootloader. If that was the case, then the OPO would not be Google certified for Google Apps.
Still need a unlocked bootloader.
zephiK said:
No you cannot root the phone without a exploit with a locked bootloader. If that was the case, then the OPO would not be Google certified for Google Apps.
Still need a unlocked bootloader.
Click to expand...
Click to collapse
That's exactly what I was reading and thinking for years.
But somehow, @The Jack of Clubs got probably a different idea (referring to his post #3 : "yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.")
That's why I got so exited and anxious to hear some explanation and elaboration from him!
You do not need to unlock the bootloader to root. The locked bootloader only protects the kernel and recovery partitions. Do not run "fastboot oem unlock" and do not run "fastboot flash recovery recovery.img". Instead just run "fastboot boot recovery.img" and flash the supersu zip from there. I've done this already. I know because I'm writing this on my rooted and bootloader locked oneplus.
Sent from my One using XDA Premium 4 mobile app
The Jack of Clubs said:
You do not need to unlock the bootloader to root. The locked bootloader only protects the kernel and recovery partitions. Do not run "fastboot oem unlock" and do not run "fastboot flash recovery recovery.img". Instead just run "fastboot boot recovery.img" and flash the supersu zip from there. I've done this already. I know because I'm writing this on my rooted and bootloader locked oneplus.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for some enlightening
I know about the recovery trick, always was doing this way and never bother with the custom one.
But the information about the rooting in a such way comes to the big surprise!
Well in this case I just hope it's not a flaw in CM build and it will stay this way and won't be fixed in next OTAs
The Jack of Clubs said:
You do not need to unlock the bootloader to root. The locked bootloader only protects the kernel and recovery partitions. Do not run "fastboot oem unlock" and do not run "fastboot flash recovery recovery.img". Instead just run "fastboot boot recovery.img" and flash the supersu zip from there. I've done this already. I know because I'm writing this on my rooted and bootloader locked oneplus.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did this... It works. Installed SuperSU using this method, I"m running Titanium Backup Pro, which requires root.
having read and write access in an alternate environment and being able to load a kernel in untrusted space kind of negates the point of the locked bootloader. which is why on something like a nexus 5, you have to unlock to root. its a security measure to block alternative access and destroying data when tampered. the international/cyanogenmod version of the phone may be running a different version of the bootloader that is on the chinese/coloros phone. you do see a cyanogenmod logo when booting into fastboot. so cyanogen may have an alternative fastboot that gives you access like this so you can mod you phone.
as far as root goes, theres two parts, the su binary which has to be copied to the system partition, and the app that gives root permissions to apps (a sudo app). you can install supersu from the playstore https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en but it doesnt do anything without the su binary. so when you are in recovery, which gives you full write access to the system partition, you flash the superuser zip, which copies the su binary to the system partition.
The Jack of Clubs said:
yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.
Click to expand...
Click to collapse
I can confirm that this method definitely works. My Oneplus is rooted, I never had to unlock the bootloader and my data is safe. Thank you!
I really think that this thread has to go to the General from Q&A and has become sticky.
Also these findings has to be communicated to @Chromium in order to enhance his Guide
This method works, I can confirm also.
Fastboot boot recovery.img
then install the su.zip file
MAKE SURE YOU BACKUP WHILE YOU ARE IN TWRP!!
The Jack of Clubs said:
You do not need to unlock the bootloader to root. The locked bootloader only protects the kernel and recovery partitions. Do not run "fastboot oem unlock" and do not run "fastboot flash recovery recovery.img". Instead just run "fastboot boot recovery.img" and flash the supersu zip from there. I've done this already. I know because I'm writing this on my rooted and bootloader locked oneplus.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Works perfectly. Thanks!
Can you explain little more for a dummie @The Jack of Clubs
Thanks
Isn't that we are able to lock the bootloader on OPO after we unlocked it ?
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
Hi all,
So I read people are now able to backup TA partition (DRM Keys) before Unlocking the Bootloader.
Keep in mind my aim for instance here is to install BBS (Better Battery Stats app) onto the system partition for full battery stats.
Now my question is can the below tasks be achieved in this order.:
1. Downgrade to an exploitable Firmware (MM?)
2. Backup TA partition
3. UL BL (Unlock Bootloader)
4. Root device
5. Install BetterBatteryStats onto System partition.
6. Unroot device
8. L BL (Lock Bootloader)
9. Restore TA partition.
And where in this list would be best to upgrade to Nougat.
I believe I achieved something similar on my z5c, but it's been a while now since I've wanted to root. But given the recent TA exploits I'm thinking it's time to geek again.
I believe if we can define the above process explicitly, many people would be happy.
As much information, direction, insight, instructions on all of the points above would be greatly appreciated by and for my.fellow XZ'ers :fingers-crossed:
I'm also curious on how to unlock, root and restore
I know it was possible to be rooted with locked bootloader on Z3 but have not seen how to on the XZ yet
Sonic Dash said:
I'm also curious on how to unlock, root and restore
I know it was possible to be rooted with locked bootloader on Z3 but have not seen how to on the XZ yet
Click to expand...
Click to collapse
Its not possible to have root on a locked bootloader on the XZ.
dillalade said:
Hi all,
Keep in mind my aim for instance here is to install BBS (Better Battery Stats app) onto the system partition for full battery stats.
And where in this list would be best to upgrade to Nougat.
Click to expand...
Click to collapse
Try this
Downgrade to MM
Backup TA
Upgrade to Nougat
Unlock bootloader and root
Install BBS
Remove root and relock bootloader
I have no guarantee it will work though and the DM-verity would probably lead to a bootloop or a non booting device. Be sure you know how to get out of this before you proceed.
gregbradley said:
Its not possible to have root on a locked bootloader on the XZ.
Click to expand...
Click to collapse
What's the reason for this?
Doesn't the Z3 have similar protection as the XZ?
Sonic Dash said:
What's the reason for this?
Doesn't the Z3 have similar protection as the XZ?
Click to expand...
Click to collapse
No, the XZ has verified boot security (DM-verity). The bootloader will not allow a non signed kernel to boot. Stock kernels will not allow a modified system to boot. Hence you need to unlock the boot for the phone to boot if you change the system partition by just one bit....
gregbradley said:
No, the XZ has verified boot security (DM-verity). The bootloader will not allow a non signed kernel to boot. Stock kernels will not allow a modified system to boot. Hence you need to unlock the boot for the phone to boot if you change the system partition by just one bit....
Click to expand...
Click to collapse
Okay that makes sense, so with it being unlocked is there any way to hide the device unlocked screen at boot?
Im sure I also have seen talks about DRM keys being flashed in and being possible to use with unlocked bootloaderers did anything ever come of that?
Sonic Dash said:
Okay that makes sense, so with it being unlocked is there any way to hide the device unlocked screen at boot?
Im sure I also have seen talks about DRM keys being flashed in and being possible to use with unlocked bootloaderers did anything ever come of that?
Click to expand...
Click to collapse
I do not know any way of hiding the screen. Also, the DRM fix that is used with an unlocked bootlader is not a full restore of the keys. DRM functionality is restores and to my knowledge it is not 100% the same as restoring the TA partition fully.
gregbradley said:
I do not know any way of hiding the screen. Also, the DRM fix that is used with an unlocked bootlader is not a full restore of the keys. DRM functionality is restores and to my knowledge it is not 100% the same as restoring the TA partition fully.
Click to expand...
Click to collapse
After some research it seems like this warning is stored in the logo.
I found a post from a few months back with a guide on how to remove it for the Moto G4
Maybe its the same for our XZ?
Sonic Dash said:
After some research it seems like this warning is stored in the logo.
I found a post from a few months back with a guide on how to remove it for the Moto G4
Maybe its the same for our XZ?
Click to expand...
Click to collapse
Yes, this can be changed in the kernel from what I remember.
gregbradley said:
Its not possible to have root on a locked bootloader on the XZ.
Try thisDowngrade to MM
Upgrade to Nougat
Install BBS
Remove root and relock bootloader
I have no guarantee it will work though and the DM-verity would probably lead to a bootloop or a non booting device. Be sure you know how to get out of this before you proceed.
Click to expand...
Click to collapse
Not sure I follow your procedure, seems redundant, I assume you've missed out a few steps there by accident.
But thanks anyway.
However, if the DM verity you mention does what it should then I guess by editing the system partition as I proposed and then relocking would cause a bootloop.
I hope there is a way and perhaps others can share more insight.
dillalade said:
Not sure I follow your procedure, seems redundant, I assume you've missed out a few steps there by accident.
But thanks anyway.
However, if the DM verity you mention does what it should then I guess by editing the system partition as I proposed and then relocking would cause a bootloop.
I hope there is a way and perhaps others can share more insight.
Click to expand...
Click to collapse
Your quote has missed some of the steps I mentioned...
•Downgrade to MM
•Backup TA
•Upgrade to Nougat
•Unlock bootloader and root
•Install BBS
•Remove root and relock bootloader
But yes, I presume a bootloop will result from it
dillalade said:
Hi all,
So I read people are now able to backup TA partition (DRM Keys) before Unlocking the Bootloader.
Keep in mind my aim for instance here is to install BBS (Better Battery Stats app) onto the system partition for full battery stats.
Now my question is can the below tasks be achieved in this order.:
1. Downgrade to an exploitable Firmware (MM?)
2. Backup TA partition
3. UL BL (Unlock Bootloader)
4. Root device
5. Install BetterBatteryStats onto System partition.
6. Unroot device
8. L BL (Lock Bootloader)
9. Restore TA partition.
And where in this list would be best to upgrade to Nougat.
I believe I achieved something similar on my z5c, but it's been a while now since I've wanted to root. But given the recent TA exploits I'm thinking it's time to geek again.
I believe if we can define the above process explicitly, many people would be happy.
As much information, direction, insight, instructions on all of the points above would be greatly appreciated by and for my.fellow XZ'ers :fingers-crossed:
Click to expand...
Click to collapse
It won't work! As @gregbradley said, dm-verity does not allow unsigned partitions (eg modified /system) to be loaded, and the procedure you wanna try will result in a bootloop for sure!
Now that we have a specific tool to perform backup of TA partition, "safe" root came true. So why not to do that?
You can always restore your original TA.img and flash full stock firmware, which will give you a locked device like the never-unlocked one!
Anyway... try it at your own risk!
gregbradley said:
Yes, this can be changed in the kernel from what I remember.
Click to expand...
Click to collapse
So who would be best to contact in regards to making this? @AndroPlus perhaps?
How to convert ta.img to file ta.zip flash twrp
s-6182 said:
How to convert ta.img to file ta.zip flash twrp
Click to expand...
Click to collapse
Just realised, you won't need to convert anything!
In TWRP, select - Install Image (under Install button on the home menu) and locate the TA.img from there.
Apparently, you might not need to flash stock firmware afterwards, but I would do that if I were you just to make sure everything works cleanly!
gregbradley said:
No, the XZ has verified boot security (DM-verity). The bootloader will not allow a non signed kernel to boot. Stock kernels will not allow a modified system to boot. Hence you need to unlock the boot for the phone to boot if you change the system partition by just one bit....
Click to expand...
Click to collapse
Why did Sony do that?
I just dont want to see ads in games and apps.
For these, root was enough. At least my old Z3 phone.
I do not want to open the unlock bootloader, because the device may have serious performance degradation especially on the camera, right?!
Is it possible in the near future to make root without unlock bootloader ?
P.S.: If I knew that, I would not buy XZ.
please stop the discussion on SONY's security measures here
FerhaDo said:
I do not want to open the unlock bootloader, because the device may have serious performance degradation especially on the camera, right?!
Is it possible in the near future to make root without unlock bootloader ?
Click to expand...
Click to collapse
This has been beaten to death in the post Z3 devices fora.
You can read A LOT about in e.g. the Z5 section.
Authorative Guide:
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
I wanted to switch to Lineage with MicroG so I unlocked my bootloader(was on Open beta 3), flashed Lineage recovery and tried out Lineage. Somehow being unsatisfied, I wanted to move back to stock and found the Android 10 fastboot rom and instructions from this thread I am back on stock now. However my bootloader is still unlocked. I tried to lock it using fastboot OEM lock but then I ended up not able to boot at all. Has anyone managed to relock bootloader and can you share the way to do it?
yeshwanthvshenoy said:
I wanted to switch to Lineage with MicroG so I unlocked my bootloader(was on Open beta 3), flashed Lineage recovery and tried out Lineage. Somehow being unsatisfied, I wanted to move back to stock and found the Android 10 fastboot rom and instructions from this thread I am back on stock now. However my bootloader is still unlocked. I tried to lock it using fastboot OEM lock but then I ended up not able to boot at all. Has anyone managed to relock bootloader and can you share the way to do it?
Click to expand...
Click to collapse
Why do you want to lock your bootloader?
There are many reasons for unlocking but I do not see any for "re-locking" the bootloader
You sure you have no modifications applied at all? As soon as the boot / system partition is being detected as tampered the device won't boot. I can imagine there is some information on persist whichmight be used for comparison and as you are using a file to go back to Android 10 from XDA it might throw this error? Just guessing though
TheSSJ said:
You sure you have no modifications applied at all? As soon as the boot / system partition is being detected as tampered the device won't boot. I can imagine there is some information on persist whichmight be used for comparison and as you are using a file to go back to Android 10 from XDA it might throw this error? Just guessing though
Click to expand...
Click to collapse
I am not sure what exactly is causing this. This is why I created this thread to see if someone who has locked it again can reply or something or I can get some hints from someone.
It_ler said:
Why do you want to lock your bootloader?
There are many reasons for unlocking but I do not see any for "re-locking" the bootloader
Click to expand...
Click to collapse
People have preferences. Whilst for you it may not seem valid or no reasons, I do have bro.
using OnePlus 9 5g from tmobile and looking to convert to internation.anyone had any issues or tips to make sure I don't mess up?
So I come from the OnePlus 9 Pro forum, but the tips are identical because pretty much the same phone except for a few differences.
1. DO NOT FLASH BOOTLOADER
I can't stress this enough, flashing the bootloader will render the MSM tool that OnePlus provides for you USELESS! I figured this out the hard way!
2. Make a full device backup, if you're rooted already use Partitions backup and restore available on the Play Store
3. Keep OEM UNLOCKING ON THE WHOLE TIME! Don't turn it off until and unless you return to complete stock using a MSM tool! Also, keep your bootloader unlocked please.
4. Don't trust random "conversion" folders that flash everything at once without looking at the files, ESPECIALLY not without looking at the .bat file(s) such as a flashall.bat.
Sounds too risky. It's not so simple anymore .
Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
What if I don't want root, just international version
I am interested to switch from T-Mobile variant to international as well.
Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Do you have magiskhide enabled?
inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Im showing to be passing. There was a magisk issue a week ago or so that cause it to fail but it was updated.
Playstore shows "Device is certified"
I really want international myself. This battery is complete garbage and tmo likes to drag their feet on an update the international got to fix the battery issue weeks ago
jfsat said:
Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.
Click to expand...
Click to collapse
@jfsat If you just want root, patching the boot.img with magisk should be good enough. Just don't forget to keep OEM unlocking checked and keep the unlock code just in case. Also, don't relock until you have flashed stock boot.img.
Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
It literally does not matter, but I would recommend flashing the boot.img instead because I don't know what the Direct Install method does to your phone's firmware. Flashing the boot.img works great, it only touches your boot partition and if you have the stock boot you can just flash it back and relock it, no problem. Direct Install could potentially change something else though it looks like it could be fine, but YMMV.
inspron said:
I am interested to switch from T-Mobile variant to international as well.
Click to expand...
Click to collapse
I know how to do it, you need to extract payload.bin from the EU OTA and flash all the partitions, find a tutorial online. Just make sure to make a full backup using Partitions backup and restore on the play store or manually dump partitions from your phone. You don't need userdata, it's too big and probably incompatible with the region change, just a side note that flashing partitions in the super partition (system, vendor, product, system_ext, odm, etc.) requires you to be in fastbootd, so use fastboot reboot fastboot to do so. Other than that, make sure there's an MSM tool available, you can check with OnePlus support.