Hey Guys. Im looking to unroot yet another HTC One m7. AT&T continues to send me defective devices. This one is a 1.57 Hboot 4M.27.3218.15 radio. I cant find a RUU for this setup. Any help would be greatly appreciated.
sjorge3442 said:
Hey Guys. Im looking to unroot yet another HTC One m7. AT&T continues to send me defective devices. This one is a 1.57 Hboot 4M.27.3218.15 radio. I cant find a RUU for this setup. Any help would be greatly appreciated.
Click to expand...
Click to collapse
radio version is irreverent when searching for a RUU. CID, MID and version-main are the information needed to find one. Best thing is to post your output of "fastboot getvar all' except your imei and serialno. Unfortunately, I don't think there is any AT&T ruu for version on hboot 1.57.
Latest RUU for AT&T (CID: CWS__001 MIDN0712000) is 4.18.502.7 and will require s-off because its a downgrade (hboot 1.56)
alray said:
radio version is irreverent when searching for a RUU. CID, MID and version-main are the information needed to find one. Best thing is to post your output of "fastboot getvar all' except your imei and serialno. Unfortunately, I don't think there is any AT&T ruu for version on hboot 1.57.
Latest RUU for AT&T (CID: CWS__001 MIDN0712000) is 4.18.502.7 and will require s-off because its a downgrade (hboot 1.56)
Click to expand...
Click to collapse
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
sjorge3442 said:
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
Click to expand...
Click to collapse
If you have to send the phone for warranty I will even recommend you to use the 1.26.501.8 RUU (hboot 1.44) so you can remove the tampered flag from bootloader because it might come back if removed on hboot 1.55 and up.
Take a look at nkk71's guide linked in my signature.
sjorge3442 said:
Cool. Never knew that. I will need to S off anyway since that's how to return to stock. I didn't know radio didn't matter. I can flash a 1.56 ruu with no problems?
Click to expand...
Click to collapse
alray said:
If you have to send the phone for warranty I will even recommend you to use the 1.26.501.8 RUU (hboot 1.44) so you can remove the tampered flag from bootloader because it might come back if removed on hboot 1.55 and up.
Take a look at nkk71's guide linked in my signature.
Click to expand...
Click to collapse
I've done this a few times now so I'm no stranger to thing. Last two times I did the 1.56 update, plus I have those files downloaded already. They keep sending me refurbs and each one they send has build quality issues. Its unreal.
sjorge3442 said:
I've done this a few times now so I'm no stranger to thing. Last two times I did the 1.56 update, plus I have those files downloaded already. They keep sending me refurbs and each one they send has build quality issues. Its unreal.
Click to expand...
Click to collapse
Well return it to stock so you can send it for warranty again and ask for an upgrade to another model. Explain that you are not satisfied with this model because you have experienced issues on each replacement units. Might worth a try...
alray said:
Well return it to stock so you can send it for warranty again and ask for an upgrade to another model. Explain that you are not satisfied with this model because you have experienced issues on each replacement units. Might worth a try...
Click to expand...
Click to collapse
Yeah that's the plan. I tried last time, but they swore they would send me a new. box phone this time. However, I ended up with a "like new" phone. This won't be happening again. Hoping for an M8
sjorge3442 said:
Hoping for an M8
Click to expand...
Click to collapse
That is exactly what I had in mind.
Good luck!
Related
I'm running converted GE with 1.54 Google Hboot on my AT&T M7 (S-Off)
in order to go back to stock with the RUU I have to first load the 2.17 firmware Vomer provided in his thread.
If I don't do that I get error 155 when using the RUU.
I lock my bootloader before running it.
What am I missing. I thought S-off and SuperCID bypassed the checks and RUU's just worked.
Thanks for any advice.
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
iElvis said:
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
Click to expand...
Click to collapse
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
gunnyman said:
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
Click to expand...
Click to collapse
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
iElvis said:
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
Click to expand...
Click to collapse
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
gunnyman said:
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
Click to expand...
Click to collapse
You might try sticking with the 2.17 hboot and see if that helps.
iElvis said:
You might try sticking with the 2.17 hboot and see if that helps.
Click to expand...
Click to collapse
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
gunnyman said:
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
Click to expand...
Click to collapse
Must be the GE hboot or perhaps hboot 1.54 from 2.24 in general. I had a AT&T device with the new firmware and hboot 1.54 (from 2.17) I was able to run the RUU with s-off and bootloader still unlocked.
My fear is an ota for the ge would break the ability to downgrade hboot. The 2.17 works because it is the same 1.54
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Rex2369 said:
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Click to expand...
Click to collapse
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
gunnyman said:
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
Click to expand...
Click to collapse
Coming from full GE experience (1.54 hboot, GE recovery and ROM), I had to flash just the 1.44 hboot and relock my bootloader before the Dev RUU worked for me.
Sent from my HTC One using xda premium
So clearly HTC changed something about what S-off means and what you can and can't do with it.
Alright, so my friend has an AT&T One and it had 1.26.502.10 firmware (like mine), but he had some camera issues... He decided to do all the modding (root, s-off, etc...) and upgraded to 4.2.2 firmware 2.24. His camera issues continue, and he plans on returning to 4.1.2 with the available RUU that returns the phone to 1.26.502.12. He is s-off, supercid, unlocked bootloader, rooted, running twrp 2.6.0.1 and is on stock rooted 2.24.401.1 Rom. I thought of just using that RUU to return him to fully stock, but since it has all the mods I'm not really sure if I should take another approach or other steps. Please help me out here, I don't wanna brick his phone (even though he's taking it to be replaced). Thanks in advanced!
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Just run the RUU, as he's S-OFF there should be no issues
jerrycoffman45 said:
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Click to expand...
Click to collapse
Yes, that's the very file I have. Thanks! Will run it now! Thanks for the quick reply!
EddyOS said:
Just run the RUU, as he's S-OFF there should be no issues
Click to expand...
Click to collapse
Will do, thanks for ur quick reply!
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
EddyOS said:
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
Click to expand...
Click to collapse
Hmm, will I get a kind of error during the RUU process that might possibly brick the device or will it warn me before the RUU process starts? Can I and should I just flash the 1.44 RUU from fastboot before starting the RUU? The phone's on 2.24 right now with the modded 1.54 hboot (I know he first has to flash the original, but can/should he flash the 1.44 instead?).
EDIT: As far as I've read till now, the ones having errors were converted to Google Edition with GE hboot and all... I did read about 2 people (one with 2.17 and the other with 2.24 like my friend's phone) both on 1.54 hboot and it worked for both of em. I'm just gonna go ahead and flash the RUU on my friend's phone and hope for the best
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
http://forum.xda-developers.com/showthread.php?p=39588860
No offense but you didn't look very hard. Its in a sticky in the dev thread
Once you s-off (which is ridiculously easy for this device) you can use any RUU. Good luck and enjoy
Sent from my One using Tapatalk 2
Anicane said:
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
Click to expand...
Click to collapse
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
AllAboutTheCore said:
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
Click to expand...
Click to collapse
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Anicane said:
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Click to expand...
Click to collapse
Cool, yes, you are correct, S-Off can be reverted ... It's also worth noting that if you S-Off now, you'd be able to upgrade to Hboot 1.54 and still maintain S-Off. The problem lies with those, like me, who are on the 1.54 Hboot but haven't gone S-Off ... We're now stuck until a solution is available, although I didn't want to go S-Off so it's not really a problem.
If you go S-Off btw you can flash any RUU from any region and change your Cid/Mid, although I can't help you on the whole RUU when S-Off process as I've never run one, nor been S-Off as I previously mentioned lol.
I still can't find which RUU is for my phone, is there anyway to find ? is it via CID or any other way ?
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
EddyOS said:
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
Click to expand...
Click to collapse
It is 1.29.401.16
Anicane said:
It is 1.29.401.16
Click to expand...
Click to collapse
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
EddyOS said:
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
Click to expand...
Click to collapse
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Anicane said:
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Click to expand...
Click to collapse
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
EddyOS said:
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
Click to expand...
Click to collapse
Well, i am thinking of a scenario which i don't know is possible or not, so here it goes. Since i want to be on the safe side, how about i take a nandorid back of the stock, and than if i wanted to returen to stock, simply flash an RUU like 1.29.401.16, and than simply recover the nandroid backup over it, and update if i wanted to ? Is it possible ?
The only problem is that i don't know how to remove the custom recovery when it restore the nandorid back, and update it.
Hello all, I am sort of in a predicament.
First of all, I have an ATT Htc One that had 1.44 Hboot and unlocked, rooted, running Android Revolution HD 22.0 just fine.
On the rom the thread Mike said it was recommended to update firmware, so I did just that.
I headed over to his thread http://forum.xda-developers.com/showthread.php?t=2182823 found the corresponding firmware zip for my device
CWS 001 PN0712000 and flashed it. The firmware being 3.06.1700.10 and now my hboot is 1.54
I am aware that no RUU's will run with 1.54 but is there anyway I can revert back to stock without running a RUU?
Maybe flashing stock rom and stock recovery, relocking and wait for the upcoming OTA due for the ATT htc one?
I would very appreciative for the help.
And I know I should've been more knowing before flashing firmwares, so go on and burn me as much as youd like but id still like some help.
I just assumed since the rom developer insisted it was for the better that there would be a way out of it, which is my bad.
thank you
savatore410 said:
Hello all, I am sort of in a predicament.
First of all, I have an ATT Htc One that had 1.44 Hboot and unlocked, rooted, running Android Revolution HD 22.0 just fine.
On the rom the thread Mike said it was recommended to update firmware, so I did just that.
I headed over to his thread http://forum.xda-developers.com/showthread.php?t=2182823 found the corresponding firmware zip for my device
CWS 001 PN0712000 and flashed it. The firmware being 3.06.1700.10 and now my hboot is 1.54
I am aware that no RUU's will run with 1.54 but is there anyway I can revert back to stock without running a RUU?
Maybe flashing stock rom and stock recovery, relocking and wait for the upcoming OTA due for the ATT htc one?
I would very appreciative for the help.
And I know I should've been more knowing before flashing firmwares, so go on and burn me as much as youd like but id still like some help.
I just assumed since the rom developer insisted it was for the better that there would be a way out of it, which is my bad.
thank you
Click to expand...
Click to collapse
this guide should do it
http://forum.xda-developers.com/showthread.php?t=2394155
clsA said:
this guide should do it
http://forum.xda-developers.com/showthread.php?t=2394155
Click to expand...
Click to collapse
thank you so much!
I'll give it a shot now.
clsA said:
this guide should do it
http://forum.xda-developers.com/showthread.php?t=2394155
Click to expand...
Click to collapse
I don't think this will work since I am S on :/
Same Issue As @savatore410
savatore410 said:
I don't think this will work since I am S on :/
Click to expand...
Click to collapse
I'm in your same boat. Did you ever figure this out? I have an ATT HTC One m7 model PN0712000 with CID CWS__001. My HBOOT is 1.57. Is there a way to get back to STOCK?
consequense said:
I'm in your same boat. Did you ever figure this out? I have an ATT HTC One m7 model PN0712000 with CID CWS__001. My HBOOT is 1.57. Is there a way to get back to STOCK?
Click to expand...
Click to collapse
Wow this is a year old thread
try this modern superguide >> http://forum.xda-developers.com/showthread.php?t=2541082
Hey all,
I'm trying to get my phone back to my carrier's stock but I'm running into some issues.
I can't use a RUU because I have one of the "Whelp" non-s-off phones. Most guides on here as well require you to have s-off to do.
Any idea's on how to bring a S-ON'd phone back to stock?
Thanks,
Basttrax
Basttrax said:
Hey all,
I'm trying to get my phone back to my carrier's stock but I'm running into some issues.
I can't use a RUU because I have one of the "Whelp" non-s-off phones. Most guides on here as well require you to have s-off to do.
Any idea's on how to bring a S-ON'd phone back to stock?
Thanks,
Basttrax
Click to expand...
Click to collapse
you can still use a RUU if it's the same version of your current software or newer
clsA said:
you can still use a RUU if it's the same version of your current software or newer
Click to expand...
Click to collapse
I'm getting to the point with the RUU that the screen goes to the black HTC screen. Then I get a "HTC_Fastboot.exe has crashed" error.
Basttrax said:
I'm getting to the point with the RUU that the screen goes to the black HTC screen. Then I get a "HTC_Fastboot.exe has crashed" error.
Click to expand...
Click to collapse
yeah sorry if your on the 4.x.xx.x software your going to need an older RUU and S-off. The 4.x.xx RUU have had this problem for many users and I have never seen a fix /workaround
clsA said:
yeah sorry if your on the 4.x.xx.x software your going to need an older RUU and S-off. The 4.x.xx RUU have had this problem for many users and I have never seen a fix /workaround
Click to expand...
Click to collapse
Unfortunately I have one of the HTC One's that you can't s-off
Basttrax said:
Unfortunately I have one of the HTC One's that you can't s-off
Click to expand...
Click to collapse
whats your fastboot getvar all
can you do a Guru Reset ?