Related
I attempted to flash my UK Vodafone HTC One as I wanted Android Revolutiion HD ROM on my phone, i've sort of got half way and i'm not sure how to continue (or if I should)
So i've unlocked the bootloader, and flashed the clockwork recovery so my phone now says *TAMPERED*
It is still S-On and is on HBOOT 1.54 - having read around this cannot be done, right?
Also, one other quick question. If I ever wanted to go back to complete stock, how can I do this? I can't seem to find the RUU for my phone, and how would I remove *TAMPERED*
Here is my radio version: 4A.17.3250.14
ANY HELP IS MUCH APPRECIATED GUYS! I've rooted other HTC's before but not the One yet
You can't go S-Off on 1.54
You could just flash the stock rom and stock recovery, which has the same result as an RUU/
Tampered is removed when you lock, but you can't remove -relocked- without S-Off
Thanks for your reply.
So what you're saying is in the situation I am in at the moment, I can't flash the ARHD ROM to my phone without being S-OFF first?
It's basically just a waiting game for S-OFF to become available for 1.54 and then I could just flash the stock ROM and recovery and then S-OFF to remove the TAMPERED or RELOCKED.
This will be just incase id ever need to send the phone off to Vodafone for whatever reason
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.
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
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.
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Seanie280672 said:
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Click to expand...
Click to collapse
Great, thanks! I will flash the original firmware in a sec, but the most recent RUU I can find is this one: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
And I am not sure if that is also based on hboot 1.57 and because of that, if I am able to flash this RUU. Currently I am downloading it but the download speed is terrible, I will report back after I tried.
Or are you saying that I can flash the stock firmware 5.xx.401.xx on top of the current 6.xx firmware? I thought that wouldn't be possible because I'm currently on a higher firmware version but I'll give it a shot!
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Seanie280672 said:
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Click to expand...
Click to collapse
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
WiiiLDFARMER said:
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
Click to expand...
Click to collapse
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Once it's finished, boot the phone once and then back into bootloader and check the hboot version, if it is lower than the version you have on there now then you'll know you have stock hboot and should be safe to s-on, however like I said before, make sure your locked and tampered has gone before setting s-on (not sure if s-on is required for warranty)
Seanie280672 said:
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Click to expand...
Click to collapse
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
WiiiLDFARMER said:
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
Click to expand...
Click to collapse
Unfortunately I don't know that, there's been some reports it comes back after you s-on not after the ruu, I think it's HTC 's way of catching you out, others say it's been fine, are you sending it to HTC or your operator ?
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
However , if you've had s-off with that phone before, chances are you'll get it again, you'll just have to do whatever you did before to get it, then go back to stock again, and send it s-off.
WiiiLDFARMER said:
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
Click to expand...
Click to collapse
Try this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
It worked for me, returned full stock!