So I unlocked(htcdev) and rooted(twrp) and now I wounder if I should re-lock for security? I read that the boot-loader could have an authorized os list. Since both the system and recovery are os's would a re-lock put twrp out of control?
Thanks
I'd like to know this also. Fortunately relocking seems to be easy.
micnolmad said:
So I unlocked(htcdev) and rooted(twrp) and now I wounder if I should re-lock for security? I read that the boot-loader could have an authorized os list. Since both the system and recovery are os's would a re-lock put twrp out of control?
Thanks
Click to expand...
Click to collapse
Musicbee said:
I'd like to know this also. Fortunately relocking seems to be easy.
Click to expand...
Click to collapse
Never relock with custom roms or custom recovery still installed on your phone, this will result in bootloop.
Only way to stop this bootloop will be to unlock again but unlocking the bootloader require the stock recovery to be installed.
So with custom recovery installed and bootloader relocked = bootloop = can't unlock again. You'll have to reflash the whole firmware in ruu mode to get back the stock recovery over the custom one and then you'll be able to re-unlock to stop the bootloop.
So short answer, don't relock when not 100% stock
Ich, thanks! Glad I asked first instead of taking the chance..
Sent from my HTC One using XDA Free mobile app
Related
I'm a bit curious why my bootloader shows "TAMPERED" after flashing TWRP custom recovery.
I have the HTC One developer edition so I thought this kind of stuff (i.e. flashing custom recovery images) was OK?
sofakng said:
I'm a bit curious why my bootloader shows "TAMPERED" after flashing TWRP custom recovery.
I have the HTC One developer edition so I thought this kind of stuff (i.e. flashing custom recovery images) was OK?
Click to expand...
Click to collapse
Don't know for sure, but I thought this message showed up after I unlocked the bootloader on my consumer HTC One.
appelflap said:
Don't know for sure, but I thought this message showed up after I unlocked the bootloader on my consumer HTC One.
Click to expand...
Click to collapse
Yeah, I thought that was a warning for consumers who unlocked their bootloaders but I thought a developer edition wouldn't have this because it's meant to be fooled around with, etc.
Didn't show up until I rooted.
sofakng said:
I'm a bit curious why my bootloader shows "TAMPERED" after flashing TWRP custom recovery.
I have the HTC One developer edition so I thought this kind of stuff (i.e. flashing custom recovery images) was OK?
Click to expand...
Click to collapse
It shows tampered for when you change your boot.img.
I'm pretty sure the tampered message happens when you flash any recovery other than stock.
Not a big deal unless you need to return your phone in which you flash stock recovery and relock.
Sent from my HTC One using Tapatalk 2
Marcismo55 said:
I'm pretty sure the tampered message happens when you flash any recovery other than stock.
Not a big deal unless you need to return your phone in which you flash stock recovery and relock.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
How do you flash stock recovery? After I do this, will it AUTOMATICALLY relock?
Thanks
It even shows TAMPERED when you fastboot anything. You don't even need to flash anything, a
fastboot boot recovery.img
is enough to tamper with the boot loader. Was disappointed at first but that won't void your warranty anyways and once we got S-Off we are done with it.
Becool0130 said:
How do you flash stock recovery? After I do this, will it AUTOMATICALLY relock?
Thanks
Click to expand...
Click to collapse
You flash the stock recovery just as you would TWRP/CWM using fastboot. No, you would have to manually relock your device (using HTCdev) as flashing the stock recovery will not automatically lock the device.
Thanks for the information everybody.
Does the tampered warning cause any other problems?
sofakng said:
I'm a bit curious why my bootloader shows "TAMPERED" after flashing TWRP custom recovery.
I have the HTC One developer edition so I thought this kind of stuff (i.e. flashing custom recovery images) was OK?
Click to expand...
Click to collapse
Wouldn't the answered be, because you did tampered with it?
Sent from my HTC One using xda app-developers app
Yeah, I understand. I actually rooted the phone for something but now I realized I didn't actually need to.
If I wanted to completely restore the phone back to factory condition, how can I do that?
I still want to keep the factory unlocked bootloader of course... (since it's the developer edition)
My gf has HTC One with latest stock T-Mobile US ROM, unlocked bootloader, is rooted, and has TWRP. T-Mobile is about to release an OTA (source), and I am wondering how to go about installing it. AFAIK, stock recovery is required, AND the bootloader needs to be locked again. If this is the case, re-rooting will require unlocking the bootloader and thus doing factory reset? Is there a simpler way to do this?
Stock recovery and preinstalled apps needed
Bootloader locked not needed
There are many posts written about this read them first
c00ller said:
My gf has HTC One with latest stock T-Mobile US ROM, unlocked bootloader, is rooted, and has TWRP. T-Mobile is about to release an OTA (source), and I am wondering how to go about installing it. AFAIK, stock recovery is required, AND the bootloader needs to be locked again. If this is the case, re-rooting will require unlocking the bootloader and thus doing factory reset? Is there a simpler way to do this?
Click to expand...
Click to collapse
relock your bootloader
fastboot oem lock
and run this RUU
http://www.htc.com/us/support/htc-one-t-mobile/news/
instructions / Download are at the bottom of the page
Everything on the Phone will be lost ..Backup to your PC and google first !
yatindroid said:
Stock recovery and preinstalled apps needed
Bootloader locked not needed
Click to expand...
Click to collapse
FYI I have actually tried running an RUU on unlocked bootloader with stock recovery, kept failing until I relocked the bootloader...
hello guys ) i just wanna ask if its possible to flash android m with nexus root toolkit or no ??
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
jj14 said:
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
Click to expand...
Click to collapse
thank you for the fast reply
Yes I followed those steps and flashed it perfectly.
BossJ said:
Yes I followed those steps and flashed it perfectly.
Click to expand...
Click to collapse
yeah same here, everything went more then well.
Should I relock the bootloader after flashing M ?
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
NOOO!!!!
To many folks have encountered an issue that soft-bricked their device afterwards.
You will still receive OTA with an unlocked bootloader.
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
stricker said:
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
Click to expand...
Click to collapse
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
danarama said:
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
Click to expand...
Click to collapse
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
danarama said:
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
Click to expand...
Click to collapse
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you like.
Hello
i have to sell my device so i want to get it to stock again.
My current Setup:
Bootloader Unlocked, Stock Recovery, Rooted with Magisk, Stock ROM 9.0.0.283
What are the Steps to go Back to Stock and wipe everything?
Ive read that if the bootloader relock again it is not able to unlock the second time? Is this correct? I want to get the Unlock Code to the person who buy it but if its real, he cant use the code anymore..
anyway is it possible to do the job with the Stock E-Recovery in the current state of my phone? Without bootloader Relocked? Or is it necessary to relock the bootloader again?
Thank you very much
blackst225 said:
Hello
i have to sell my device so i want to get it to stock again.
My current Setup:
Bootloader Unlocked, Stock Recovery, Rooted with Magisk, Stock ROM 9.0.0.283
What are the Steps to go Back to Stock and wipe everything?
Ive read that if the bootloader relock again it is not able to unlock the second time? Is this correct? I want to get the Unlock Code to the person who buy it but if its real, he cant use the code anymore..
anyway is it possible to do the job with the Stock E-Recovery in the current state of my phone? Without bootloader Relocked? Or is it necessary to relock the bootloader again?
Thank you very much
Click to expand...
Click to collapse
Ask the buyer if they want it locked. Personally it wouldn't be worth my time if it couldn't be unlocked again. Better to check first..
If you want to lock (not relock) bl justdownload your adequate firmware from androidhost.ru and flash fw using Usb-otg method.
You can unlock/lock your bl using unlock code anytime you want (provided you haven't changed your mainboard in the meantime).
forever_lol said:
If you want to lock (not relock) bl justdownload your adequate firmware from androidhost.ru and flash fw using Usb-otg method.
You can unlock/lock your bl using unlock code anytime you want (provided you haven't changed your mainboard in the meantime).
Click to expand...
Click to collapse
Hi is it possible to do the following..
Adb relock bootloader in my current state?
In my opinion the relock of the bootloader restore system to default over the erecovery or is this wrong?
Many thanks
blackst225 said:
Hi is it possible to do the following..
Adb relock bootloader in my current state?
In my opinion the relock of the bootloader restore system to default over the erecovery or is this wrong?
Many thanks
Click to expand...
Click to collapse
I thought you wanted to go back to stock. I've already gave you solution to bring back all the way stock.
I m not sure if it's even possible to re-lock bootloader using fastboot when you're on pie.
Bootloader status re-locked still means your warranty is void.
forever_lol said:
I thought you wanted to go back to stock. I've already gave you solution to bring back all the way stock.
I m not sure if it's even possible to re-lock bootloader using fastboot when you're on pie.
Bootloader status re-locked still means your warranty is void.
Click to expand...
Click to collapse
Hey I've tried this otg method but without success
If I try it with the dload folder option and try to force flash the emui updater throws an error.
Even with the dialer code method.. same..
I'm not able to get it to stock.
I've tried the Huawei suite on PC and phone in fastboot mode..same..massage this phone can't be reset or so..
What can I do next?
Current state, halfway working phone that's boot into os 2 times from 10 reboots.
Yeah the title says it all. Just wondering if that's possible or not since I'm not sure if I'd have to wait for a week for my phone to be unlocked, while I could get the job done in no time.
If unlocking the bootloader is required, then would force unlocking it using mtkclient work (triggers bootloop, haven't tried to relock it and see if it fixes it)? Or will it only work through official bootloader unlocking?
No, you need to unlock the bootloader in order to flash a recovery over the stock one
zSyntex said:
No, you need to unlock the bootloader in order to flash a recovery over the stock one
Click to expand...
Click to collapse
Oh, alright then. Thanks. But can I just force unlock it or is official unlocking required?
YLTN said:
Oh, alright then. Thanks. But can I just force unlock it or is official unlocking required?
Click to expand...
Click to collapse
You need to unlock first, since locked bootloader will block any flash over system partitions
zSyntex said:
You need to unlock first, since locked bootloader will block any flash over system partitions
Click to expand...
Click to collapse
I meant if I should unlock it using the official method, or using the mtkclient method?