Hi I basically want to trade in my HTC desire 610 (EU addition) at CEX.
It is currently S-ON, deodexed & modified stock rom with JMZ kernel.
I want to be able to unroot and relock bootloader without signs of tampering as I will get less for it if they find it has been rooted.
I am fine to flash an odexed stock rom (im pretty sure there is one in the dev thread), but does anyone know how to get the bootloader back to its original state, when I have tried with other phones it always says "re-locked" instead of locked and is obvious it has been tampered with.
Any ideas?
W1LD3G30RG3 said:
Hi I basically want to trade in my HTC desire 610 (EU addition) at CEX.
It is currently S-ON, deodexed & modified stock rom with JMZ kernel.
I want to be able to unroot and relock bootloader without signs of tampering as I will get less for it if they find it has been rooted.
I am fine to flash an odexed stock rom (im pretty sure there is one in the dev thread), but does anyone know how to get the bootloader back to its original state, when I have tried with other phones it always says "re-locked" instead of locked and is obvious it has been tampered with.
Any ideas?
Click to expand...
Click to collapse
You can do "fastboot oem lock" to re-lock the bootloader. This will change it from saying "unlocked" to "Locked". However it will still say "Tampered" above it and there is no way to get rid of that once it has been unlocked.
Related
i want to send my phone back to handtec to replace my phone with new one that work fine with no issues like my phone...
and my phone is rooted and unlocked....
there is any easy or noob way to make it fully stock agin?
install a RUU makes all Stock
skdubg said:
install a RUU makes all Stock
Click to expand...
Click to collapse
First you have to use the all in one toolkit to relock your bootloader, then you can run the ruu. Just FYI at the top of Hboot it will now say relocked, not locked. In other words HTC will know you tampered with it.
yes, but a relocked bootloader has nothing to do with warranty (in europe)...
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
For a quick and easy way, just boot into fast boot and cmd "fastboot oem lock"
The only problem with that is that if they DO boot into the bootlaoder, it will say "RELOCKED" instead of "LOCKED"
The longer way, is to S-OFF (find it in the international forum) and then follow instructions there to put the "LOCKED" text back.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
Get S-OFF, I was able to remove TAMPERED and change my UNLOCKED to LOCKED. You can also flash a modded HBoot that will take the red letters away and change the text from S-OFF to S-ON this will allow it to look like you never touched a thing
To get S-OFF I recommend http://forum.xda-developers.com/showthread.php?t=2314582
To mod your HBoot go through the post from here http://forum.xda-developers.com/showthread.php?t=2316726 (to download the HBOOT and here http://forum.xda-developers.com/showthread.php?t=1786498 to download the tool to create the modified HBOOT
But to let you know, I have returned 2 HTC Ones with unlocked bootloaders and AT&T did not say anything. Just flash the stock rom, make sure fastboot in enabled and leave it booted to the set up screen. Above is for if you want to be thorough and make sure you cover all your bases.
I'm trying to get back to full stock (which I am) but on my bootloader it says relocked and I want to get back to locked so I can use my JUMP thing from T-mobile. Any tips on what i should do?
INFINITYandONE said:
I'm trying to get back to full stock (which I am) but on my bootloader it says relocked and I want to get back to locked so I can use my JUMP thing from T-mobile. Any tips on what i should do?
Click to expand...
Click to collapse
Need more info:
What firmware are you on? Are you S-Off? If you are S-Off, what did you use to achieve it?
The easiest way, assuming you want 4.3 fully stock is to use the RUU that tmobile provides.
I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it. I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
My device has S-ON from what I saw on HBOOT, is using the Skydragon custom kernel, and I'm using TWRP custom recovery. I still have the RUU I downloaded from AT&T to return my device to stock 5.0.2 firmware. My question is, shall I just run the RUU and it will all be back to stock? Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have. Could anyone point me in the right direciton? thanks!
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
sarxion said:
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it.
Click to expand...
Click to collapse
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
sarxion said:
I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
Click to expand...
Click to collapse
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
sarxion said:
My question is, shall I just run the RUU and it will all be back to stock?
Click to expand...
Click to collapse
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
sarxion said:
Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
Click to expand...
Click to collapse
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
sarxion said:
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have.
Click to expand...
Click to collapse
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
redpoint73 said:
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
Click to expand...
Click to collapse
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy, or don't apply, such as this one that requires S-OFF http://forum.xda-developers.com/showthread.php?t=2708571
sarxion said:
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Click to expand...
Click to collapse
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
sarxion said:
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy
Click to expand...
Click to collapse
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
redpoint73 said:
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
Click to expand...
Click to collapse
Thank you very much. So I can run the RUU with my M8 on bootloader mode? Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel. (I'll be running the exact same RUU version I ran before installing the custom rom)
sarxion said:
So I can run the RUU with my M8 on bootloader mode?
Click to expand...
Click to collapse
The RUU will run with the phone in bootloader-fastboot mode, yes.
sarxion said:
Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel.
Click to expand...
Click to collapse
That is correct. And in fact, as far as I know, the phone is rendered unable to boot into OS after relocking the bootloader, even if you were on the stock ROM.
OP,
Were you able to go back to stock?