Bootloader relock breaking my boot - OnePlus Nord Questions & Answers

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.

Related

[Q] Trying to root on 33R to no avail

Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
zephiK said:
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
Click to expand...
Click to collapse
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Yeah, I'm in the same boat as you. Unfortunately after all my reading, it seems impossible as CM did it as a preventative measure to secure your data.
I'm going to do a back up of everything and then a reflash to 25R where battery life was best, then unlock and reboot.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Well thats the whole point, the OnePlus One is a very developer friendly phone indeed. Thats why you get the "keys" to unlock the phone with a simple command instead of using a exploit to flash a custom recovery.
On 25R bootloader, it was possible but as of now there isn't a way to root without unlocking the bootloader. You can read the thread here, http://forum.xda-developers.com/oneplus-one/help/root-unlocking-bootloader-t2820628
This is why when people just now get a phone that has the ability to fastboot oem unlock, I suggest them to unlock their bootloaders as the first thing to do.
Backup all of your data and move forward. Best of luck.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
if you truly want to restore everything there are apps that will zip up all your data and you can flash in one session after wiping your phone. If you are reloading the exact same software it should not be an issue. check google and playstore for such apps like app2zip
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
therightperson_630 said:
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
Click to expand...
Click to collapse
oh yea my bad I forgot about the root part. I usually root right away so my bad..
Sorry, but the only way is to unlock the bootloader. You could use Helium backup, also some Apps themselves have great backup functionality.
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
timmaaa said:
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
Click to expand...
Click to collapse
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
therightperson_630 said:
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
Click to expand...
Click to collapse
The difference between having a locked and unlocked bootloader is simply flashing custom recoveries or radios/etc. Theres no harm in doing leaving your bootloader unlocked.
The bootloader has to be locked out of the box, I believe its one of the criterias needed to be fulfilled in order to be approved for Google Apps (Play Store,etc). Also, it doesn't make sense to have a bootloader unlocked for average users.
Just unlock the bootloader and learn from your lesson.... either that or stick with stock ROM without root. Yeah it'll set you back because you'll have to redo your phone apps/settings but on the bright side you won't have to do it again because ur bootloader is already unlocked.
You need your bootloader unlocked to obtain root. See http://forum.xda-developers.com/showthread.php?t=2788632 on instructions on how to do so if you're unfamiliar. After once its unlocked, fastboot flash a custom recovery and flash supersu.
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
therightperson_630 said:
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
Click to expand...
Click to collapse
Thats because the G1 had a locked bootloader and the only way to flash a custom recovery was to gain a exploit to push a custom recovery. For the OnePlus/Nexus/HTC, we don't need a exploit because we have the ability to unlock our bootloaders. Think of it as Apple's iOS, in order to gain jailbreak you need a exploit to jailbreak your phone which can take a long time for it to happen. Whereas, on Nexus/OnePlus/HTC, we can simply just obtain access to do changes to the phone without having to wait for a exploit.
You keep mentioning average user but a average user wouldn't be attempting to obtain root access for their phone. The average user would just be using his/her phone as a phone and not tinkering with the deeper innings of the Operating System and if the average user wants to tinker with the deeper innings then they should really do their research and learn. There are a lot of good guides on XDA.
Couldn't agree more. There is no need for any exploit with this phone because you've been handed the keys.
Transmitted via Bacon
therightperson_630 said:
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Click to expand...
Click to collapse
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
ondoy1943 said:
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
But then again,
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to fastboot oem unlock command.
Click to expand...
Click to collapse
A little off topic but I unlock my boot loader and root as soon as I get the phone so I don't have to loose anything.
zephiK said:
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
Click to expand...
Click to collapse
that's what you think, but in my case i was able to unlock the bootloader using the mod, hence rooting was a matter of course. the casual "fastboot oem unlock" command was not effective with my device. so.....
edit: then again, i unlocked the bootloader and rooted my phone while it was still at 30O firmware. i have no idea if the 33R firmware's bootloader is different from that of the 30O or not, that will render the mod ineffective.
It's fine, problem solved, went through the gruelling task of trying to back everything up without root = 40gb of stuff..
Already tried the tamper bit mod...it was stated in the first post (tamper bit mod) and the command screenshot was one of the steps when trying to boot the recovery, it still wouldn't boot because the bootloader wasn't unlocked..so, useless in my case.
Still lost some stuff but I got most of it back. I didn't have this problem on my xperia SP when unlocking the bootloader..if I remember correctly you could root, get recovery and custom rom all without unlocking bootloader. Unlocking the bootloader didn't erase the internal sd either..sure it might have been through an exploit rather than the proper way, but tbh I think I'd rather have that.
I'm not liking this "you've been given the keys" analogy...It's more like you've already settled into your new house and you're given the keys to unlock the front door when you're already inside...it's hassle more than anything.

[Q] Error message while installing android lollipop on Nexus 5

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.

Opo help no bootloader and recovery gone

I was trying to upgrade my opo and I found my bootloader was locked but to unlock it I needed a recovery installed and somehow it had dissapeared. Please help asap
tom_clegg said:
I was trying to upgrade my opo and I found my bootloader was locked but to unlock it I needed a recovery installed and somehow it had dissapeared. Please help asap
Click to expand...
Click to collapse
None of that makes sense. You don't need a recovery to unlock your bootloader. Your bootloader can't disappear either. Look, you're going to have to provide a lot more information if you expect anybody to be able to help you. We need details, lots of them. We need to know exactly what you did to the device, we need to know exactly what the device can and can't do now. You need to explain everything with as much information as possible, because honestly, with the information you've given so far nobody can help at all.
Heisenberg said:
None of that makes sense. You don't need a recovery to unlock your bootloader. Your bootloader can't disappear either. Look, you're going to have to provide a lot more information if you expect anybody to be able to help you. We need details, lots of them. We need to know exactly what you did to the device, we need to know exactly what the device can and can't do now. You need to explain everything with as much information as possible, because honestly, with the information you've given so far nobody can help at all.
Click to expand...
Click to collapse
Ok well..
I was recently trying to flash the new oxygen OS onto my oneplus, but when i was trying to flash a custon recovery to do so like TWRP, it said bootloader needed to be unlocked, I did what was needed but my phone wouldnt boot into the stock recovery (or recovery of any form) and just stayed at the boot screen. This made me unable to unlock my bootloader so i am basically stuck on the current version of Android and cannot upgrade or flash.
tom_clegg said:
Ok well..
I was recently trying to flash the new oxygen OS onto my oneplus, but when i was trying to flash a custon recovery to do so like TWRP, it said bootloader needed to be unlocked, I did what was needed but my phone wouldnt boot into the stock recovery (or recovery of any form) and just stayed at the boot screen. This made me unable to unlock my bootloader so i am basically stuck on the current version of Android and cannot upgrade or flash.
Click to expand...
Click to collapse
That still doesn't make sense. Where did you read that you need to boot into recovery in order to unlock your bootloader? That isn't true. You use fastboot to unlock your bootloader, not recovery. Have a look at my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

Relock bootloader

Can I relock bootloader, and flash completely stock if I need?
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
suzook said:
Can I relock bootloader, and flash completely stock if I need?
Click to expand...
Click to collapse
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Bradl79 said:
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
Click to expand...
Click to collapse
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Bradl79 said:
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
Click to expand...
Click to collapse
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
intruda119 said:
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Click to expand...
Click to collapse
Ah, got it. That sucks. :'( Thanks!
effmsee said:
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
Ah, got it. That sucks. :'( Thanks!
Click to expand...
Click to collapse
if all else fails we do have an unbrick tool, but from what i have read, u can no longer sideload with ur bootloader locked and there is not install from internal storage from stock recovery
I learned the hard way. Soft brick in the first hour of ownership.i thought I really broke something until eventually a few others reported on it. B
Op I would wait
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
BoboBrazil said:
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
Click to expand...
Click to collapse
Certain I did something wrong. But I tried the same thing initially and would bootloop to recovery after factory reset. Wasn't a biggie learned about the new a/b system in the process
Somewhat related question:
If you relock the bootloader, does Widevine go back to L1?
One user reported no. Is it really a permanent change of the Widevine status to unlock it?
I might be able to deal with 480p netflix, but if I sell this phone someday it sucks for the next owner.
No worry just try mega unbrick guide used it to relock bootloader and flash stock hydrogen os it can recover your device from even hardbrick I tested it for safety it works like charm so I recommend you that
Can anyone who has unlocked and re-locked their bootloader check their Widevine status in DRM info?
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
noppoer2 said:
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
Click to expand...
Click to collapse
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
kailashnj said:
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
Click to expand...
Click to collapse
Reinstall your rom ( i believe 5.1.6 ) to get rid of TWRP & root
Factory reset
Then on fastboot " fastboot oem lock"
Data & internal storage will be wiped
Which means post following the steps origins bootloader will be locked and I will not get the warning again right at the start of the phone
All you can do is try but first make a Nandroid just in case this falls through
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
thealexwu said:
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
Click to expand...
Click to collapse
Lock as you unlocked in cmd by typing lock instead of unlock. It will make a wipe, so I recommend make backup before.

Question Flash P6a stock?

Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
Click to expand...
Click to collapse
There is no TWRP for this device. To get back to stock and re-lock your bootloader you can try Android Flash Tool or Pixel Flasher.
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock?
Click to expand...
Click to collapse
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Did you erase the GrapheneOS Android Verified Boot key before you went back to stock?
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
At the bottom of the articel is described how to erase the key.
WoKoschekk said:
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Click to expand...
Click to collapse
I starts to boot, then it goes to white Google screen and stays there until I force it to reboot.
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
LankiCat said:
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
Click to expand...
Click to collapse
It's described on that page. Just do what the say and all is fine.
It's just one fastboot command. Thereis no reason to find a workaround or sth.
WoKoschekk said:
It's described on that page. Just do what the say and all is fine.
Click to expand...
Click to collapse
I really appreaciate the help, but, the page says: Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it. Since I have already flashed the factory stock image I want to be sure that will work and not cause more problems. It takes a really long time to flash stock with all the setup, updates, restore, and re-loading apps to get back where i need to be. Thanks again for you input.
LankiCat said:
Since I have already flashed the factory stock image
Click to expand...
Click to collapse
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
WoKoschekk said:
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
Click to expand...
Click to collapse
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
LankiCat said:
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
Click to expand...
Click to collapse
Then run fastboot flashing lock
WoKoschekk said:
Then run fastboot flashing lock
Click to expand...
Click to collapse
yeah, tried that too. I'm going to have to wait until this weekend when I can afford some downtime on my phone.

Categories

Resources