I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....
whitetiger_0603 said:
I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....
Click to expand...
Click to collapse
Unlock ur bootloader. Gain S-OFF nd root access
then flash then zip from this link: http://www.htc1guru.com/guides/guru-bootloader-reset/
from TWRP/CWM. It will be an Aroma installer for removing the tampered logo and locking the bootloader
Here, choose Remove Tampered and lock ur bootloader(DON'T RELOCK. CHOOSE LOCK BOOTLOADER. then proceed to flash the RUU
whitetiger_0603 said:
I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....
Click to expand...
Click to collapse
I'll highly suggest you read nkk71's guide linked in my signature. Don't forget that if you turn s-on on hboot 1.55, the tampered flag will come back after a few reboot so make sure you go back s-on on hboot 1.44 or 1.54. Anyway, its all explained in that guide
alray said:
I'll highly suggest you read nkk71's guide linked in my signature. Don't forget that if you turn s-on on hboot 1.55, the tampered flag will come back after a few reboot so make sure you go back s-on on hboot 1.44 or 1.54. Anyway, its all explained in that guide
Click to expand...
Click to collapse
raghav kapur said:
Unlock ur bootloader. Gain S-OFF nd root access
then flash then zip from this link: http://www.htc1guru.com/guides/guru-bootloader-reset/
from TWRP/CWM. It will be an Aroma installer for removing the tampered logo and locking the bootloader
Here, choose Remove Tampered and lock ur bootloader(DON'T RELOCK. CHOOSE LOCK BOOTLOADER. then proceed to flash the RUU
Click to expand...
Click to collapse
Thank you both. Alray, I looked through that thread last night before finally asking forh lep, but it seemed confusing as to what i needed exactly. I'll go through it again, maybe it was just late night brain fuzzies that made it look confusing to me. Raghav, I saw that as well, and will give it a shot. I appreciate you both responding.
I triple checked my hboot, and it's 1.44. I never changed it. Guess I'll check in if i have any more questions or have fixed the issue. Thanks again.
whitetiger_0603 said:
Thank you both. Alray, I looked through that thread last night before finally asking forh lep, but it seemed confusing as to what i needed exactly. I'll go through it again, maybe it was just late night brain fuzzies that made it look confusing to me. Raghav, I saw that as well, and will give it a shot. I appreciate you both responding.
I triple checked my hboot, and it's 1.44. I never changed it. Guess I'll check in if i have any more questions or have fixed the issue. Thanks again.
Click to expand...
Click to collapse
post a "fastboot getvar all" (excluding IMEI and s/n) and let me know which parts are confusing or need further explanation.
please note the guide was written (and rewritten) with in a certain sequence to avoid potential problems; if you have questions as to "why do this at that point" or other questions, feel free to ask
Ok, so in the order you guys gave me, I:
Unlocked bootloader via HTC-Dev..again...
I still had root access so I flashed CWMT
Regained S-off with the Toolkit
Flashed the zip you all provided, in recovery to "lock bootloader' and remove tampered
Tried using the toolkit again to flash the RUU. That failed so I manually ran ADB to do it.
It went through the whole process then at the end, says "FAILED (unknown status code). The RUU mode screen seems to be done. I know the green status bar never finishes completely, but I'm concerned with that failed message in cmd. Should i reboot to see what happens?
Edit: It looks like it worked. So, assuming I no longer have root access, cause if I remember correctly the RUU removes it, how do I go back to S-on, without the tampered popping up again?
whitetiger_0603 said:
Ok, so in the order you guys gave me, I:
Unlocked bootloader via HTC-Dev..again...
I still had root access so I flashed CWMT
Regained S-off with the Toolkit
Flashed the zip you all provided, in recovery to "lock bootloader' and remove tampered
Tried using the toolkit again to flash the RUU. That failed so I manually ran ADB to do it.
It went through the whole process then at the end, says "FAILED (unknown status code). The RUU mode screen seems to be done. I know the green status bar never finishes completely, but I'm concerned with that failed message in cmd. Should i reboot to see what happens?
Click to expand...
Click to collapse
stop using that toolkit and do it by yourself, best way to know what is going wrong....
What ruu did you used? Also if you are using a ruu.zip you have to flash it with fastboot in ruu mode not with adb.
You should go read and follow post #3 of nkk's guide.
EDIT: you still haven't posted your ''fastboot getvar all'' as @nkk71 asked for earlier.
alray said:
stop using that toolkit and do it by yourself, best way to know what is going wrong....
What ruu did you used? Also if you are using a ruu.zip you have to flash it with fastboot in ruu mode not with adb.
You should go read and follow post #3 of nkk's guide.
Click to expand...
Click to collapse
Noted, I think the toolkit is what keeps having the tampered pop up anyhow...
Guess I should have been more detailed. Rebooted into bootloader, then to RUU mode. Ran adb cmd to flash RUU. I know I have the correct file for that.
Double checked the guide you referenced... it seems to cluttered to me... but I found the part I need. Giving it a shot now.
Yup..that did it. I remember using that cmd line in the beginning but i didn't know that was for S-on, rather just for tampered. Just factory reset my phone now. Thank you again.
Edit: didn't post the getvar, as i thought it was only requested if i came up with another issue. My mistake. Thank you all again.
alray said:
stop using that toolkit and do it by yourself, best way to know what is going wrong....
Click to expand...
Click to collapse
+8
stop using toolkits
whitetiger_0603 said:
it seems to cluttered to me... but I found the part I need.
Click to expand...
Click to collapse
cluttered :crying::crying:
i knew this was gonna happen :crying::crying:
suggestions are welcome
nkk71 said:
+8
stop using toolkits
cluttered :crying::crying:
i knew this was gonna happen :crying::crying:
suggestions are welcome
Click to expand...
Click to collapse
Lol, I'm sorry... you're guid is very comprehensive. No lie there. I personally, just couldn't get around through it. It may just have been me. I just thought it could ahve been more organized. But hey, no big. I found what I needed and I appreciate it.:laugh:
whitetiger_0603 said:
Lol, I'm sorry... you're guid is very comprehensive. No lie there. I personally, just couldn't get around through it. It may just have been me. I just thought it could ahve been more organized. But hey, no big. I found what I needed and I appreciate it.:laugh:
Click to expand...
Click to collapse
Which parts did you find unorganized, I always appreciate constructive criticism :cyclops:
Related
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Squeaky369 said:
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Click to expand...
Click to collapse
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
ess.boyer said:
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
Click to expand...
Click to collapse
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Or whatever...
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Squeaky369 said:
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Click to expand...
Click to collapse
Amen to that!
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Click to expand...
Click to collapse
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
http://forum.xda-developers.com/showthread.php?t=1416836
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
ess.boyer said:
Amen to that!
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
Click to expand...
Click to collapse
Ripped the original HBOOT out of the RUU that I had from HTC.
When I try and flash though I get this:
---------------------------------------------------------------------------------------------------------
C:\Android>fastboot flash hboot hboot.nb0
sending 'hboot' (1023 KB)... OKAY [ 0.297s]
writing 'hboot'... FAILED (remote: not allowed)
finished. total time: 0.614s
---------------------------------------------------------------------------------------------------------
I don't need to be S-OFF to flash the HBOOT do I? I unlocked the bootloader again, so that is not what is causing the issue.
Brand New said:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
That's the first thread I went through when starting this
I have actually been looking for the PH39IMG.zip file for At&t because that's how I used to do this...
But the file in that link isn't there anymore. It seems that every search I do and find where someone has posted it, it's been removed because of copyright infringement or some other stupid political BS.
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Ha! Rocking! Glad you're back up and running.
Squeaky369 said:
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Click to expand...
Click to collapse
I am having the exact same issue. Any chance you could share that PH39IMG.zip you made or explain how you did it?
I'll be putting the links up for the PH39IMG.zip in the next hour or so
---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------
For both AT&T and Rogers Ripped straight from the RUU
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
[SOLVED]
Fully stock and downgraded to H-Boot 1.44 Android 4.1.2
Thanks to @nkk71
mctodd said:
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
Click to expand...
Click to collapse
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
blakphoenix said:
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
Click to expand...
Click to collapse
Thanks for the reply, but mostly in youtube where out of date..
mctodd said:
Thanks for the reply, but mostly in youtube where out of date..
Click to expand...
Click to collapse
mctodd said:
Hi nkk71, I know it's a bit annoying to have someone bothering you but seems like your the one the good guys that can patiently help some one frustrated on going back to stock (like brand new). I am having a problem on going back to stock. Here is my spec on Bootloader mode.
M7_U Htc One model
Hboot-1.54.0000
Radio-4A.17.3250.14
OpebDSP-v31.120.272.0617
OS-2.24.707.3
EMMC-boot
HTC_044
One of my problem also is i rooted it with mac and there is no unrooting instructions for mac.. Pls help if you have any idea, i just have to send it back to repair. Thanks.
P. S i am willing to pay via paypal if necessary
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
nkk71 said:
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
Click to expand...
Click to collapse
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
No worries, do it later, as I'm not on s computer either for the time being. I'll be on again later, but only for an hour or two, so it might have to wait till tomorrow anyway.
Sent from my HTC One using Tapatalk
This your firmware ? 2.24.707.3
Do you have a nandroid backup of it ?
What does it say on your bootloader ?
also, on a mac you will need to type the following before any command:
./
so ./adb devices
./fastboot devices
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Thanks for yours patient on making this replies and research man.. i really do appreciate it.
Heres the screen shot that you requested earlier.
I am a bit confused with this OS-2.24.707.3 and build number 2.24.401.8 Which one is really my ROm version?? Any idea?
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
mctodd said:
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
Click to expand...
Click to collapse
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
nkk71 said:
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks alot man.. Your such a help..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, is it possible to flash the ruu that you linked above to back to stock so i'll be able to run rumrunner S-off.. Cuz i tried in ARHD 13.1 didnt work after 8 pouring it says "please wait 30 seconds and run rumrunner again,press enter to exit" I had multiple attempts already and never worked..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
mctodd said:
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
Click to expand...
Click to collapse
I'll get back to u in an hour or two...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
At number 4. Did mean that i have to manually downgrade or it is automatic??
mctodd said:
At number 4. Did mean that i have to manually downgrade or it is automatic??
Click to expand...
Click to collapse
It's automatic. If there's an error let me know
Keep S-Off !!
nkk71 said:
It's automatic. If there's an error let me know
Keep S-Off !!
Click to expand...
Click to collapse
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
mctodd said:
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
Click to expand...
Click to collapse
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
nkk71 said:
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
Click to expand...
Click to collapse
Once it succeeded it is ready for service repair to claim warranty? Thanks
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
kikinhorap said:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
Click to expand...
Click to collapse
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Answer
attanasi0 said:
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Click to expand...
Click to collapse
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
kikinhorap said:
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
Click to expand...
Click to collapse
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
A
attanasi0 said:
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
Click to expand...
Click to collapse
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
kikinhorap said:
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
Click to expand...
Click to collapse
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
nkk71 said:
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
Click to expand...
Click to collapse
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
kikinhorap said:
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
Click to expand...
Click to collapse
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
nkk71 said:
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
Click to expand...
Click to collapse
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
kikinhorap said:
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
Click to expand...
Click to collapse
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
nkk71 said:
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
Click to expand...
Click to collapse
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
kikinhorap said:
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
Click to expand...
Click to collapse
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
nkk71 said:
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
Click to expand...
Click to collapse
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
kikinhorap said:
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
Click to expand...
Click to collapse
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
nkk71 said:
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
Click to expand...
Click to collapse
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
kikinhorap said:
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Click to expand...
Click to collapse
Excellent :good:
kikinhorap said:
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
Click to expand...
Click to collapse
That's normal, dont worry about it.
kikinhorap said:
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
Click to expand...
Click to collapse
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
nkk71 said:
Excellent :good:
That's normal, dont worry about it.
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
Click to expand...
Click to collapse
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
kikinhorap said:
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
Click to expand...
Click to collapse
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
nkk71 said:
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
Click to expand...
Click to collapse
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
kikinhorap said:
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
Click to expand...
Click to collapse
You should have LOCKED it before running the RUU, because that's what made you loose root.
So before proceeding, can you give me an update of your status:
bootloader: locked/relocked/unlocked?
tampered?
ROM?
"fastboot getvar all" (remove IMEI and s/n)
Hello all, you've all been very helpful since I got my Htc One.
However, I have to return it tomorrow, and am quite worried. I relocked the bootloader, and turned S-OFF to S-ON, however, it says TAMPERED. I fear they won't take it back since it says tampered...
And I see no way to remove tampered while S is ON. Is there a way? I have to return it tomorrow, and am very worried. I try to flash the factory RUU but it ALWAYS returns an error. I tried using the all-in-one hasoon tool, and it won't flash the zip either. I am not sure how to return it to factory and remove the tampered.
Any help would be grateful. This will be my final topic.
A) Why put it back to S-On? There's no need for that. Take it back to stock, but leave it S-Off.
B) Nope. You have to have S-Off in order to remove the tampered flag.
RossLH said:
A) Why put it back to S-On? There's no need for that. Take it back to stock, but leave it S-Off.
B) Nope. You have to have S-Off in order to remove the tampered flag.
Click to expand...
Click to collapse
But by default my friend doesn't it come as S-ON? That's why I'd be worried they wouldn't accept it.
No matter what, when I try to flash the factory RUU, it says Error 155. It will never complete.
ThomasZRedFox said:
But by default my friend doesn't it come as S-ON? That's why I'd be worried they wouldn't accept it.
No matter what, when I try to flash the factory RUU, it says Error 155. It will never complete.
Click to expand...
Click to collapse
Most of them do, some of them don't. Just tell them it came that way, they have no way of contesting it.
You're not going to be able to flash the factory RUU, unless you're upgrading to a newer version, I believe. You need S-Off to do what you're trying to do.
RossLH said:
Most of them do, some of them don't. Just tell them it came that way, they have no way of contesting it.
You're not going to be able to flash the factory RUU, unless you're upgrading to a newer version, I believe. You need S-Off to do what you're trying to do.
Click to expand...
Click to collapse
Thank you for not ignoring me, I have never been so anxiety ridden trying to accomplish something! I am up against time.
I am running rumrunner to re S-OFF. Once that is done, to flash a factory RUU, I won't be able to use the exe you say? Will I be able to load it via hasoon then, the zip instead of the exe? Thank you so much. I truly actually appreciate it big time.
ThomasZRedFox said:
Thank you for not ignoring me, I have never been so anxiety ridden trying to accomplish something! I am up against time.
I am running rumrunner to re S-OFF. Once that is done, to flash a factory RUU, I won't be able to use the exe you say? Will I be able to load it via hasoon then, the zip instead of the exe? Thank you so much. I truly actually appreciate it big time.
Click to expand...
Click to collapse
I've never personally used the exe, I find it more reliable to flash the zip manually through adb. But once you have S-Off, you should be able to do it with whichever method you prefer.
That said, I don't know that flashing the RUU will turn the tampered flag off. You might have to do that using this method or revone.
Once you have signed software on the phone, tampered should go away. The RUU should work.