I'm kinda new to IncS, cause I had Desire untill a few days ago and I have a lot of experience with this things on it.
So what's my point, I'm about to unlock bootloader over htcdev cause I have ICS sense 3.6 (www_asia_hk build 4.10.708.1 with 2.02 hboot so htcdev is the only option as I could find), and my question is will I be able to get it back to factory state (with LOCKED sign) with ruu if I have to get the phone back to the seller for waranty purpose?
Don't jump on me, I tried the search but all the answers I could find were incomplete.
Thanks in adwance.
nlooooo said:
I'm kinda new to IncS, cause I had Desire untill a few days ago and I have a lot of experience with this things on it.
So what's my point, I'm about to unlock bootloader over htcdev cause I have ICS sense 3.6 (www_asia_hk build 4.10.708.1 with 2.02 hboot so htcdev is the only option as I could find), and my question is will I be able to get it back to factory state (with LOCKED sign) with ruu if I have to get the phone back to the seller for waranty purpose?
Don't jump on me, I tried the search but all the answers I could find were incomplete.
Thanks in adwance.
Click to expand...
Click to collapse
You will be able to RELOCK the bootloader, but as long as you have a RUU that has unlockable bootloader in it installed, there will always be a tell-tale sign because the HBOOT screen will show "RELOCKED" instead of "LOCKED".
Also, part of the unlocking procedure at HTCDEV.com requires that you acknowledge that this process 'could void your warranty' and HTC will have a record that you unlocked the bootloader.
I don't worry about HTC cause I got sellers warranty, so repair won't be performed by the HTC service.
And one more question, so if I run ruu over relocked bootloader I won't get LOCKED sign again?
Edit:
After I unlock bootloader, if I do a downgrade to older hboot and s-off it via revolutionary, is there a way for getting back to factory state?
nlooooo said:
I don't worry about HTC cause I got sellers warranty, so repair won't be performed by the HTC service.
And one more question, so if I run ruu over relocked bootloader I won't get LOCKED sign again?
Edit:
After I unlock bootloader, if I do a downgrade to older hboot and s-off it via revolutionary, is there a way for getting back to factory state?
Click to expand...
Click to collapse
Yes, if you use the downgrade procedure, then you could flash a Gingerbread 2.3.3/Sense 2.1 RUU then HBOOT would not show a lock status as long as you left it on that ROM.
If you flash any RUU starting with GB 2.3.5/Sense 3.0 and above, then the HBOOT screen will always show RELOCKED on the HBOOT screen. This will also occur if you take an OTA update for the GB 2.3.5/Sense 3.0.
Related
Can I debrand my phone without s-off or without unlocking my bootloader or can I relock bootloader so it says "locked" and no "tampered"/""relocked"/"unlocked" because i want to still have my warranty.
adammo666 said:
Can I debrand my phone without s-off or without unlocking my bootloader or can I relock bootloader so it says "locked" and no "tampered"/""relocked"/"unlocked" because i want to still have my warranty.
Click to expand...
Click to collapse
I'm assuming you have a carrier branded device so without unlocking the bootloader you are stuck with your carrier rom..... there's not much else you can do.
Without unlocking the bootloader, you can't really do anything to your phone.
You can relock the bootloader so it says "locked" but you need s-off.
You could always unlock the bootloader, get s-off, change what you want, relock to "locked", and then back to s-on.
Just be really reeeeeaaaaaaaallly~ careful not to brick your device when tampering with s-off. Don't go back to s-on with modified/unsigned hboot, etc.
OP can't S-OFF. 1.54 HBOOT and S-ON.
http://forum.xda-developers.com/showthread.php?t=2387163
Pretty much screwed for now.
cee43ja1 said:
OP can't S-OFF. 1.54 HBOOT and S-ON.
http://forum.xda-developers.com/showthread.php?t=2387163
Pretty much screwed for now.
Click to expand...
Click to collapse
Im gonna post a follow up on this one, as I am in the same boat. Have unfortunately bought a One with a very weak wifi antenna, and suffer from dropouts and short distance. I bought this one yesterday, but I have already rooted to get my titanium backups back.
Is there any ETA for S-OFF on Hboot 1.54? Im not asking for a specific eta, but will it take days, weeks or months before they will break it? Just asking out of curiousity, I'll guess ill have to wait anyway.
Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Clivectmob said:
Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 Check this guide out
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Clivectmob said:
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Click to expand...
Click to collapse
Run a stock ROM like found in mike1986's thread, install the stock recovery and relock your bootloader ... That's all you can do at the moment because you can't go S-Off on Hboot 1.54 so the tampered flag will have to stay until you can.
Read through this, http://forum.xda-developers.com/showthread.php?t=2265618 .. there's everything there that you need to return to stock and receive OTA updates while being S-On. The only time you'll have an issue is if you can't go S-Off to remove the tampered flag and change it from relocked to locked, only an issue if you need to return it under warranty for anything that's happened as a result of you unlocking the bootloader and flashing stuff.
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Clivectmob said:
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Click to expand...
Click to collapse
According to the guy I spoke to at HTC when I sent mine back the other day, it shouldn't. He said they should only refuse to cover repair under warranty if the fault is caused by something you've done, i.e, flashing stuff or deliberate damge or something. Unfortunately that's the risk you take if you need to return it, unless there's a method to change the flag by being S-Off you just have to either not risk it and wait until you can go S-Off and be sure to remove all traces of messing, or you return it and hope for the best lol
Well, I don't need to get it fixed or anything. Just had me play and wanna return it back to normal. I have done as I said I would in the first post and applied a small application update from HTC, so it appears to have worked. As expected, I have Re-locked and Tampered displayed. Will Just wait for S-off to emerge and deal with it then. Thanks for all the replies.
Well, I'm usually able to dig myself out of messes I get myself into but this one has had me hunting a few hours. Here's the run-down.
1) S-OFF with 1.44 a while ago, rooted and unlocked bootloader
2) Got camera problem, would like to return phone to stock for warranty
3) Flashed a stock RUU, went fine. Stock recovery and bootloader work fine, hboot was upgraded to 1.55 (my mistake, should have noticed this)
4) Got sidetracked when trying to lock the bootloader and entered fastboot oem lock
So now I have a 're-locked' bootloader on 1.55 with S-OFF. I don't want to unlock through HTCDev, I can't use revone to unlock because I'm on 1.55, and I don't have a custom recovery, and can't flash one because I'm relocked.
Any ideas how I can unlock the bootloader here (or downgrade hboot, I have the zip but can't flash it)? I can probably handle the rest myself, after I smack myself over the head a few times.
The goal here is to have the bootloader 'LOCKED', and I'll then take my chances with S-ON, with the latest firmware but a downgraded (1.44) bootloader before handing it over for warranty purposes.
OK, it looks as though I can patch hboot files OK. Will take a look around for a patched one.
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
SaHiLzZ said:
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
Click to expand...
Click to collapse
Sorted, thanks. Found an older ROM that flashed fine with supercid. Think I'll keep S-OFF and just lock the bootloader. With this being a likely hardware issue I'm hoping I'll be fine with just that.
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
blitzzkrieg said:
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
Click to expand...
Click to collapse
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
alray said:
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
Click to expand...
Click to collapse
I can't unlock bootloader back, flashing unlock_code.bin and allow prompt from phone, it goes to update screen, 2 minutes later i get red triangle screen. I have to unlock my bootloader without unlock_code but my hboot 1.57. So i think my device is dead
Try generating another unlock bin
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
stovie_steve said:
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
From my own experiencea friend sent it in with an unlocked boot loader and they repaired it. But they may have just been lucky.
I wouldn't return to s on on any bootloader later than 1.54, as when you do the writesecureflag command the phone will display a TAMPER DETECTED message and then you're back to square one
Best thing to do would be achieve s off using sunshine
Downgrade hboot to earlier version e.g. 1.44
flash an earlier RUU
Use revone to reset the status of the bootloader to LOCKED, ensure tamper message is not there
Then, if you really must, run the writesecureflag command. That's how I've done it before, and after hboot 1.54 you will def get the tamper detected message
I always leave my phone s off tho
stovie_steve said:
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
nurogo said:
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
Click to expand...
Click to collapse
At this point, how can i solve my problem?
Can anybody help me?
nurogo said:
At this point, how can i solve my problem?
Can anybody help me?
Click to expand...
Click to collapse
you need s-off so you can downgrade using a ruu, lock the bootloader and turn back s-on.
Try sunshine s-off and then follow nkk71's guide linke in my signature.