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...
Related
I have an HTC One Developer Edition (64GB) and it comes with a factory unlocked bootloader.
I flashed some recovery images, new kernels, etc, but I'd like to go back to the factory image with the factory unlocked bootloader.
I've tried using the HTC RUU file and it doesn't work unless you "fastboot oem lock", which I did, and it successfully restored the factory image but now the bootloader is "RELOCKED".
I can unlock using HTCDev.com but it erases a bunch of applications and it's no longer the factory developer edition image...
Can anybody help me?
sofakng said:
I have an HTC One Developer Edition (64GB) and it comes with a factory unlocked bootloader.
I flashed some recovery images, new kernels, etc, but I'd like to go back to the factory image with the factory unlocked bootloader.
I've tried using the HTC RUU file and it doesn't work unless you "fastboot oem lock", which I did, and it successfully restored the factory image but now the bootloader is "RELOCKED".
I can unlock using HTCDev.com but it erases a bunch of applications and it's no longer the factory developer edition image...
Can anybody help me?
Click to expand...
Click to collapse
Unlock it via HTCDev and flash back the data partition from my NANDROID, see my signature.
The issue is that unlocking the bootloader wipes the data partition, which has those apps. That's why they are missing. The NANDROID will fully restore your Dev Edition to the factory state.
Thanks for the information...
However, the NANDROID backup requires a custom recovery image, right?
I'm trying to reset everything (recovery image, boot image, data image, etc) back to factory and have the bootloader unlocked (and not say TAMPERED, etc).
Yes. You can fastboot a recovery without installing it but it will say tampered anyways.
Can I restore everything to stock and remove the tampered warning?
sofakng said:
Can I restore everything to stock and remove the tampered warning?
Click to expand...
Click to collapse
Yes, relock your bootloader, install the RUU. Then TAMPERED is gone but bootloader is locked. Unlock with HTCDev. I'd rather go with TAMPERED than with locked bootloader and the hassle with HTCDev.
Hmmm, maybe I'm doing something wrong.
I've relocked the bootloader and installed the RUU but it still says tampered. What can I be doing wrong?
I wish HTC had an RUU that resets the developer edition to factory unlocked (instead of requiring me to use HTCDev to unlock it again...)
You only need to worry about it saying tampered if you send it in for repair. Which you would flash back to stock anyway.
You don't see tampered when booting, so who cares!
Yeah, sorry... I'm new to Android and just trying to learn how to completely reset the phone.
Also, I'm wondering why the tampered warning is even displayed on the developer edition because isn't the entire purpose of this version to replace the different system images, etc?
sofakng said:
Also, I'm wondering why the tampered warning is even displayed on the developer edition because isn't the entire purpose of this version to replace the different system images, etc?
Click to expand...
Click to collapse
Because it's still the same hboot/bootloader but just sold pre-unlocked by HTC.
Ok, so just to clarify then, I can't really go back to factory unlocked (without the tampered warning), but it doesn't really matter...?
sofakng said:
Thanks for the information...
However, the NANDROID backup requires a custom recovery image, right?
I'm trying to reset everything (recovery image, boot image, data image, etc) back to factory and have the bootloader unlocked (and not say TAMPERED, etc).
Click to expand...
Click to collapse
You should use Helium aka Carbon for your backups in case you cannot root again. It don't require root.
Sent from Galaxy S 3 i747M 32gb
I need to send my dev edition back to get an exchange. I have used the RUU, to get rid of the tampered, but now it says relocked... Will that be a problem?
schn1tt3r said:
I need to send my dev edition back to get an exchange. I have used the RUU, to get rid of the tampered, but now it says relocked... Will that be a problem?
Click to expand...
Click to collapse
hey
did u manage to get back it to stock ?? without the tampered? and get it repaired by HTC? after flashing the RUU?
if so hw?
please some links
Thank You
e1forall said:
hey
did u manage to get back it to stock ?? without the tampered? and get it repaired by HTC? after flashing the RUU?
if so hw?
please some links
Thank You
Click to expand...
Click to collapse
I used command prompt Android ADB to run the RUU. Tampered label went away, but "relocked" was shown instead of "unlocked" and I sent it back just like that no problem.
schn1tt3r said:
I used command prompt Android ADB to run the RUU. Tampered label went away, but "relocked" was shown instead of "unlocked" and I sent it back just like that no problem.
Click to expand...
Click to collapse
is there no way to get back to factory state ?? still?
e1forall said:
is there no way to get back to factory state ?? still?
Click to expand...
Click to collapse
What do you mean? Its easy, HTCdev website provide the RUU file which is basically a one click solution.
schn1tt3r said:
What do you mean? Its easy, HTCdev website provide the RUU file which is basically a one click solution.
Click to expand...
Click to collapse
yeah factory state for the Dev edition i mean stock firmware . without tampered. and bootloader unlocked
e1forall said:
yeah factory state for the Dev edition i mean stock firmware . without tampered. and bootloader unlocked
Click to expand...
Click to collapse
I saved an email an HTC support guy sent me for the Developer One Edition.
The only file you need is an RUU.exe you can download from HTCdev.com click "developer" and download somewhere there. If you bought your developer edition in USA like I did, your filename should be RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe
Get that file and follow the instructions:
The easiest way to do that is to put the device into Fastboot Mode:
1. Boot the device into bootloader (Disable Fastboot, Power off device, Press + hold volume down and power on)
2. Navigate to Fastboot using the volume buttons. Select with power
3. Connect device to PC. “Fastboot” should change to say “Fastboot USB”
4. Execute the RUU (Rom Update Utility)
You can also do it using HTC Sync Manager. I will provide you with the instructions.
1. Download and install HTC Sync Manager from http://www.htc.com/www/software/htc-sync-manager/
2. Once it is installed proceed with step three.
3. Power down the phone
4. Power on the phone by holding volume down + power
5. Fastboot is already highlighted by default, tap power to go into it and plug the phone into the computer.
a. Note: If all drivers installed properly, you should see a change on the screen that says “fastboot usb” in red.
6. Run the RUU that was downloaded from the website and follow the on-screen directions.
a. Note: If done correctly, the screen on the phone will change to solid black and say “HTC” in grey letters and proceed to flash the phone
Click to expand...
Click to collapse
That should remove the "tampered" from hboot and will set your bootloader to "relocked" even though phone ships as unlocked. If you want to do this just for warranty, then you can argue the "relocked" happened from their official RUU and therefore still covered under warranty.
EDIT: There is a guide in xda stickied dont know how you did not see it: http://forum.xda-developers.com/showthread.php?t=2358738
schn1tt3r said:
I saved an email an HTC support guy sent me for the Developer One Edition.
The only file you need is an RUU.exe you can download from HTCdev.com click "developer" and download somewhere there. If you bought your developer edition in USA like I did, your filename should be RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe
Get that file and follow the instructions:
That should remove the "tampered" from hboot and will set your bootloader to "relocked" even though phone ships as unlocked. If you want to do this just for warranty, then you can argue the "relocked" happened from their official RUU and therefore still covered under warranty.
EDIT: There is a guide in xda stickied dont know how you did not see it: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
hello
i have seen the guide
I am in India
So the warranty is not covered in India for the Dev Edition
But i wanted to go stock with bootloader unlocked without tampered
so the question
Hello, I am returning my Moto X back to motorola and had a few questions. I have the Tmo US xt1053 model that i've updated to 4.4.2, unlocked the bootloader, flashed twrp and rooted. I want to return it to stock but there are no factory firmware images for the Tmobile US 4.4.2 and I would like to avoid bricking my phone. I was going to return to the stock recovery and then just factory reset it from the privacy menu but I am afraid to flash the stock recovery for fear of bricking it.
So my question is, can I flash the stock recovery found here: http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ ? I can't seem to figure out if there are different recovery versions like there is bootloader versions and if I don't flash the correct one I'll brick something.
I know the bootloader was updated with 4.4.2 so I can't return to 4.4 but if I flash that stock recovery can I just use the factory restore option in the stock rom to remove all my data and root? I know the bootloader will still be unlocked but I highly doubt they will notice that since they never seem to check the bootloader unless its obviously unlocked.
Are you slow???
Turn your phone off then turn it back on and explain to me how you expect them not to notice your bootloader is unlocked?
Even if you used a different boot image to hide the warning, it shows that you're bootloader is unlocked in fastboot. I wouldn't bother hoping they don't notice, I'd hope they don't care.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Did you read at all when you unlocked the bootloeader? Your warranty is voided. They do not need to have physical contact with your phone at all to determine it's voided.
Just for xt1053, you can downgrade firmware from 4.4.2 to 4.4, but just for this specific case, it doesn't mean it won't brick for other version.
SymbioticGenius said:
Are you slow???
Turn your phone off then turn it back on and explain to me how you expect them not to notice your bootloader is unlocked?
Even if you used a different boot image to hide the warning, it shows that you're bootloader is unlocked in fastboot. I wouldn't bother hoping they don't notice, I'd hope they don't care.
Click to expand...
Click to collapse
Fastboot OEM lock
Problem solved?
eksasol said:
Just for xt1053, you can downgrade firmware from 4.4.2 to 4.4, but just for this specific case, it doesn't mean it won't brick for other version.
Click to expand...
Click to collapse
I hope you didn't flash the bootloader for 4.4, if you did... enjoy your new paperweight
mastarifla said:
Fastboot OEM lock
Problem solved
Click to expand...
Click to collapse
Relocking the bootloader and never locking the bootloader are completely different things. Good luck with that.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
Relocking the bootloader and never locking the bootloader are completely different things. Good luck with that.
Click to expand...
Click to collapse
Turns out Motorola uses the QFuse system. While the bootloader will look perfectly "stock"/locked to you, Moto will be able to see that the secure boot fuse was blown, thus, re-locking your bootloader is effectively pointless.
mastarifla said:
Fastboot OEM lock
Problem solved?
I hope you didn't flash the bootloader for 4.4, if you did... enjoy your new paperweight
Click to expand...
Click to collapse
It doesn't let you downgrade it regardless, so doesn't matter.
Also fastboot oem lock only work for developer version, and you have to go through the "fastboot oem lock begin" process: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I don't think you can relock the regular version.
eksasol said:
It doesn't let you downgrade it regardless, so doesn't matter.
Also fastboot oem lock only work for developer version, and you have to go through the "fastboot oem lock begin" process: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I don't think you can relock the regular version.
Click to expand...
Click to collapse
...Unless if you manually flash the files, in which the problem occurs
T-Mobile version is the same as the Dev, maybe the AT&T version is different
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
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
test84 said:
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
Click to expand...
Click to collapse
First, questions need to go in the Nexus 6 Q&A, Help & Troubleshooting Thread, not the General thread. Second, the steps to lock the bootloader have not changed. It's done from the bootloader with fastboot and the command "fastboot oem lock". It shouldn't matter what recovery you have.
Re-locking needs stock recovery(maybe full stock; boot, recovery, system) if you try to re-lock your boot loader without stock recovery you might hardbrick your phone. So just backup your apps and files, flash a stock image from google and re-lock your boot loader with "fastboot oem lock". Which probably needs wiping your phone.
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
dahawthorne said:
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
Click to expand...
Click to collapse
this right here...there is really no reason to ever re lock your bootloader
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
2. No, they don't. Bootloader is on a completly different layer.
test84 said:
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
Click to expand...
Click to collapse
I feel your concerns. I think the safest bet is to watch where you download apps and content from. And make sure "unknown sources" is turned off. That should minimize your potential for problems. I think the main thing is watching where you get apps from.
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.