I had s-off and unlocked bootloader by revone, but decided to make it stock to claim warranty.
Since Australia doesnt have RUU, I used European RUU since 1.29.XXX are same then I used my own nandroid backup to have Australian rom.
I tried to update with OTA, but it just rebooted to bootloader and gave me TAMPERED..
So I used revone again to s-off and unlock bootloader then removed TAMPERED.
I locked bootloader and s-on again, but needed to flash radio.img to have matching baseband.
Therefore I re unlock and s-off to have CWM, however this time wasnt easy to achieve s-off, so I tried to factory reset before I try revone again.
But once again rebooted into bootloader and another TAMPERED..
I managed to remove TAMPERED, but what is wrong with my phone?
I can not OTA update 4.2.2 to have Australian rom and Australian firmware.zip..
I can not factory reset with 4.1.2 Australian rom and European firmware.zip
I can take my phone as 4.1.2 with s-on locked to service center, but what if they factory reset the phone and TAMPERED appears?
How big is stock recovery for 4.1.2? I bet 4.1.2 and 4.2.2 are same but the one I used was 9.4mb
Related
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.
i have the htc one, unbranded htc_001 firmware 1.29.401.13.. ive unlocked the bootloader and reinstalled firmware and recovery and relocked bootloader..yet it still shows tampered, so how do i go about returning it to complete stock with tampered gone, can i install this ruu-m7-ul-jb-50-htc-europe-1284017-radio-4a13323127-1031113105-release-310878-signedexe/ and then let it ota update to 1.29.401.13 all help welcome
That will either work, or fail and make no changes. No in between, no risk of damage.
Hoping you guys can help me
I s offed my phone using rumrunner, downgraded my hboot to 1.44 and restored my 1.29.206.7 O2 stock nandroid backup. I ran revone, locked the bootloader, removed tampered and updated to the latest 3.62.206.1 firmware. I need to send the phone back for repair so I did fastboot oem writesecureflag 3. I rebooted the phone and on first reboot the phone boot to the lock screen, froze and then reboot. This kept happening until a factory reset, after which the bootloader read as tampered and locked
My bootloader was 1.55 and not a modified hboot as I had come from hboot 1.44, although I don't think this hboot was for my model id or cid (I changed the android.info file to flash it)
How do I safely go to s-on for repairs? Or should I leave it as s off and locked bootloader. I'm sending it to o2 rather than HTC
I'd like to revert my Rogers HTC One back to out-of-the-box stock for warranty reasons, I'm currently S-OFF, bootloader unlocked (tampered flag removed), hboot 1.56, latest firmware 4.06. I need to go back to a locked bootloader with S-ON but there is no Rogers RUU in existence (I've read that if I S-OFF using another RUU I will brick my phone, not what I want). Is there a possibility to revert to stock or am I screwed without an RUU?
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Your good
Ali812 said:
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Click to expand...
Click to collapse
If you have changed your CID back to your carrier specific code you should be OK.
However, with the 4.4 update, there have been a few issues with the Bootloader not unlocking again, if you are sending your phone back under warranty for repair or replacement then your good to S-On, if you just want to set S-on for the hell of it (like me) I would hold fire for now.
Its will be your only remaining access to unlock the phone in one way or another.
Ali812 said:
I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
Click to expand...
Click to collapse
Like I said, no bricks involved, but read below too.
zeushacker said:
if you are sending your phone back under warranty for repair or replacement then your good to S-On
Click to expand...
Click to collapse
if he tries to go s-off to s-on on hboot 1.55, then there is a high probability, that after a few reboots "tamper detected - rebooting" -> and the TAMPERED sign is back.
I wrote the guide in a specific order 1, then 2, then 3, etc, because of that reason.
If the OP wants to give it a shot, he can go ahead, maybe the "tamper detected" won't happen; if it does, he will have to s-off using rumrunner, and start the procedure again.
s-on is not needed on waranty, there are always some devices shiped from factory with s-off. my advice is to keep s-off.