Related
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.
EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does
EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.
gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread
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.
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.
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.
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.