Database Develop

[Q] How do I factory reset my HTC Developer Edition but keep unlocked bootloader?

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

Stuck trying to get back to unlock/root

I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader

yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)

Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.

Upgrading rooted stock ROM to new stock OTA

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...

Help - OTA Update gave me a brick

Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!

brockwitting said:
Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!
Click to expand...
Click to collapse
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.

You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.

brockwitting said:
You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.
Click to expand...
Click to collapse
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241

kal250 said:
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241
Click to expand...
Click to collapse
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?

mrmazak said:
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?
Click to expand...
Click to collapse
Yes.... See what happens when you loose your R1, I'm out of touch lol.... I do miss the phone.....

mrmazak said:
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.
Click to expand...
Click to collapse
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?

kfn said:
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?
Click to expand...
Click to collapse
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly

mrmazak said:
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly
Click to expand...
Click to collapse
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled back booloader, installed 6.1 from ColtonDRG site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this

kfn said:
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled booloader, installed 6.1 from Coltron site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this
Click to expand...
Click to collapse
This will brick your phone, if you are not careful, and also if you are carefull. You can browse for help in encryption with unlocked bootloader before doing this, I'm sure there is a solution.
If you replace Seccfg.bin and Secro.bin from a backup from before unlocking bootloader you should be set to locked but I do not know of your phone will boot. You will be doing g that at your own risk.
But if you download the repair solution under the hidden tag(click to show content) in the roll back thread.
In that file it will restore you to 6.1 and it will be locked bootloader. I do not know about keeping v7 and relocked

Bricked, no clue what to do

I'm lost. I was trying to update my bootloader, and I saw a guide somewhere but lost it. I looked for it again, and I didn't find the same, but I saw different instructions. It said to update via RUU. I was using an older CM build with hboot 3.18, and I used the RUU after relocking my bootloader. It erased all the data on the phone, and then gave me error 158, which I could only find cited on a HTC One X thread. I used the RUU given in the forums here. It was non-HK. I didn't have a backup (because my stupid ass decided to not backup my phone .-.) and I am now bricked essentially. I cannot install anything. I tried to unlock, but I can't. It gives me no response other than that it fails. I have the original key too, I just don't know what to do. So, tell me if this sounds reasonable.
1. Make a new HTCdev account since I'm missing my old one.
2. Unlock via the same process.
3. Reinstall TWRP.
4. Find the old CM build I had.
5. Live with my old bootloader.
Because I have nothing I can do. If that RUU didn't work, I don't know what will. Sunshine is retarded and I'm not spending $25 for it to update the bootloader with S-OFF.
TL;DR: S-ON relocked bootloader on a phone that's wiped. Stuck with no recovery/data/anything after a failed RUU install since it decided to wipe my data instead of making sure it could even install first.