Related
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
LifeAsADroid said:
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
Click to expand...
Click to collapse
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
LifeAsADroid said:
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
Click to expand...
Click to collapse
once the bootloader is unlocked, it cant be locked back.
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
LifeAsADroid said:
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
Click to expand...
Click to collapse
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
RikRong said:
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
Click to expand...
Click to collapse
peladoro said:
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
Click to expand...
Click to collapse
Yes, but you won't be able to unlock if you're system version is newer than May.
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
RikRong said:
Yes, but you won't be able to unlock if you're system version is newer than May.
Click to expand...
Click to collapse
peladoro said:
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
Click to expand...
Click to collapse
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
hehe...ok thanks again!!!
RikRong said:
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
Click to expand...
Click to collapse
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Hello
Please can you explain step by step how to install a cwm ? (i just unlock the bootloader)
Do i have to root the phone to do that ?
Thank you
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.
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
Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.
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.