Hi guys, I have the 02 UK version of the HTC ONE X+
I install custom rom and now not finding any that work 100percent I am trying to get back to stock
Found several RUU files one specific for 02 and when running the RUU it says sending and then error message pops up on the program and the phone reboots.
Any ideas? And it doesnt have to be an 02 ruu just one that works.
My info is
Unlocked
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-None
MICROP-None
RADIO-3.1204.168.32
Thanks
you must relock bootloader to execute the latest RUU
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
Hi Yeah I have had it relocked and tried executing the RUU but still no luck.
i have the exact same issue. reason is, last time i used the RUU to get back to stock rom, i used the phone on stock rom for a while and updated my phone to the latest build which updated the HBoot to version 3.5.000 but the currently available RUUs are not compatible with the HBOOT v3.5 so we have to wait for the new RUUs
problem for me is that i have sold the phone and didnt want to send the phone out with a custom rom but time is running out im afraid.
mjenabi2 said:
i have the exact same issue. reason is, last time i used the RUU to get back to stock rom, i used the phone on stock rom for a while and updated my phone to the latest build which updated the HBoot to version 3.5.000 but the currently available RUUs are not compatible with the HBOOT v3.5 so we have to wait for the new RUUs
problem for me is that i have sold the phone and didnt want to send the phone out with a custom rom but time is running out im afraid.
Click to expand...
Click to collapse
So I have to wait for newer RUU to come out for my HBOOT. Thats not too bad if thats all it is.
I have the exact same problem with my O2 UK One +, does anyone have any idea on when these new RUU's will be available? is it possible to downgrade the HBOOT to an older version that will allow the current RUU's to work?
what about ADB sideloading a flashable .zip of the stock firmware? would that work (if we have a flashable zip) or would it kick back an error?
Thanks.
downgrade hboot works only at S-OFF state
OK, is that possible on this phone? it was on my old HTC Magic, although it was hard work!!!!!
no S-OFF at this time for tegra3
Ok, not looking good then, so is there no way for me to get back to a stock rom now? very tempted to recycle the phone and get another one.....
moon-unit said:
I have the exact same problem with my O2 UK One +, does anyone have any idea on when these new RUU's will be available? is it possible to downgrade the HBOOT to an older version that will allow the current RUU's to work?
what about ADB sideloading a flashable .zip of the stock firmware? would that work (if we have a flashable zip) or would it kick back an error?
Thanks.
Click to expand...
Click to collapse
i have a solution for you.
i have a nandroid back up of my phone, you'd need to flash the boot.img in that and then use clockmod recovery to restore the phone to that nandroid and after that flash a stock recovery, relock the bootloader then use OTA updater on the phone to get it uptodate.
it takes a lot more work than just using the RUU, but they arent available right now, so that's what i did because i sold my phone so wanted it to be back to its original state for the new owner
i have the exact phone, mine was locked to O2 as well. i bet you bought it off that guy on ebay for £400?
pm me if you are interested and i will upload the stuff for you.
Found my backup..
here we go...
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
sweet jebus... so simple, yet I didn't think of that! (I'm pretty new to this whole ROM flashing thing...)
Thanks for that simple suggestion!
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
I accidentally missed a step when flashing a custom ROM onto my HOX+, and now it hangs at the HTC quietly brilliant screen every time. I know that all I need to do is re-lock the bootloader and use the most recent RUU, but I cannot get my computer to detect my phone to re-lock the bootloader. Is there another way to re-lock the bootloader? If not, what should I do?
mjenabi2 said:
i have a solution for you.
i have a nandroid back up of my phone, you'd need to flash the boot.img in that and then use clockmod recovery to restore the phone to that nandroid and after that flash a stock recovery, relock the bootloader then use OTA updater on the phone to get it uptodate.
it takes a lot more work than just using the RUU, but they arent available right now, so that's what i did because i sold my phone so wanted it to be back to its original state for the new owner
i have the exact phone, mine was locked to O2 as well. i bet you bought it off that guy on ebay for £400?
pm me if you are interested and i will upload the stuff for you.
Click to expand...
Click to collapse
Kool can you send me your back up?
Mjenabi2 can u please share the backup of your phone if is possible.
Thanks a lot
Htc one x plus
So i have a relocked HTC one X+ and i need to know the RUU that i need..
ENCRC2B_U PVT SHIP S-OFF RL
RADIO 3.1204.171.33
I'm selling my One X+ and need to return it to stock. I had a search of the forums but most info seemed to be out of date...
I have the latest firmware 1.17.401.3 and my HBOOT is 1.35.0000. I'm not sure if the fact I'm on 1.17.401.3 will cause a problem? There only seems to be RUU's available for 1.17.401.1. - does the fact my HBOOT doesn't seem to be up to date mean I can still go back?
I have installed a custom recovery along with a ROM so I'm guessing I need to find the stock recovery, relock the bootloader and then use the correct RUU? Does the RUU take care of the boot.img or do I need to reflash the stock one too?
I'm in the UK and the phone was originally sim free so no network stuff.
I have a basic grasp of what I need to do but if anyone could confirm the best order to do stuff that would be really helpful, don't want to brick it!
Thanks
thunderstorm654 said:
I'm selling my One X+ and need to return it to stock. I had a search of the forums but most info seemed to be out of date...
I have the latest firmware 1.17.401.3 and my HBOOT is 1.35.0000. I'm not sure if the fact I'm on 1.17.401.3 will cause a problem? There only seems to be RUU's available for 1.17.401.1. - does the fact my HBOOT doesn't seem to be up to date mean I can still go back?
I have installed a custom recovery along with a ROM so I'm guessing I need to find the stock recovery, relock the bootloader and then use the correct RUU? Does the RUU take care of the boot.img or do I need to reflash the stock one too?
I'm in the UK and the phone was originally sim free so no network stuff.
I have a basic grasp of what I need to do but if anyone could confirm the best order to do stuff that would be really helpful, don't want to brick it!
Thanks
Click to expand...
Click to collapse
are you sure youre on hboot 1.35? If youre on latest firmware 1.17.401.3 you should have hboot 1.40. At the moment there is no 1.17.401.3 Ruu available and noone knows if it will ever be or when it will be. But if youre on 1.17.401.3 right now you dont have to flash a ruu to get back to stock. You can flash the 1.17.401.1 recovery via fastboot and then relock youre bootloader via fastboot command. Your bootloader will never be locked as it was fresh out of the box if you had unlocked it, it only wiil be relocked.
Or are you one a custom rom right now? then you have to restore the backup of youre stock rom, which you hopefully have done before flashing. i tried the 1.17.401.1 ruu to get back to stock a few days after ive updated to 1.17.401.3 but i was on hboot 1.40 and the ruu wont work because downgradeing isnt possible with s-on. but if youre on hboot 1.35 you cann give it a try, no idea about it.
Bambule ahoi said:
are you sure youre on hboot 1.35? If youre on latest firmware 1.17.401.3 you should have hboot 1.40. At the moment there is no 1.17.401.3 Ruu available and noone knows if it will ever be or when it will be. But if youre on 1.17.401.3 right now you dont have to flash a ruu to get back to stock. You can flash the 1.17.401.1 recovery via fastboot and then relock youre bootloader via fastboot command. Your bootloader will never be locked as it was fresh out of the box if you had unlocked it, it only wiil be relocked.
Or are you one a custom rom right now? then you have to restore the backup of youre stock rom, which you hopefully have done before flashing. i tried the 1.17.401.1 ruu to get back to stock a few days after ive updated to 1.17.401.3 but i was on hboot 1.40 and the ruu wont work because downgradeing isnt possible with s-on. but if youre on hboot 1.35 you cann give it a try, no idea about it.
Click to expand...
Click to collapse
I know I don't get how the HBOOT hasn't changed, but that's definitely what it says in the bootloader, and the firmware I got from about in settings. Weird. I'm using the InsertCoin ROM, latest version.
I did do a stock backup in december, so I'll try that tonight and see what happens- thanks.
thunderstorm654 said:
I know I don't get how the HBOOT hasn't changed, but that's definitely what it says in the bootloader, and the firmware I got from about in settings. Weird. I'm using the InsertCoin ROM, latest version.
I did do a stock backup in december, so I'll try that tonight and see what happens- thanks.
Click to expand...
Click to collapse
ah you are on insert coin thats why you see the firmware 1.17.401.3 because insert coin is based on the latest puplished software by htc and that is the 1.17.401.3 but this is only the rom your system as itselfs isnt on 1.17.401.3 because that would have happened only if you would have updated your stockrom via the OTA Update of 1.17.401.3 and only this will update your hboot to 1.40. So what I wanted to say is that your system and your hboot is still on 1.17.401.1 so you can try to use the ruu which includes everything boot and recovery or just restore your backup and flash the boot.img, the recovery and relock your bootloader and your done
I tryed all that a few days ago because im gonna sell mine too
and iwas on 1.40 and hat no backup that was a pain in the ass luckely someone on xda shared his nandroid backup of 1.17.401.3 with me
Bambule ahoi said:
ah you are on insert coin thats why you see the firmware 1.17.401.3 because insert coin is based on the latest puplished software by htc and that is the 1.17.401.3 but this is only the rom your system as itselfs isnt on 1.17.401.3 because that would have happened only if you would have updated your stockrom via the OTA Update of 1.17.401.3 and only this will update your hboot to 1.40. So what I wanted to say is that your system and your hboot is still on 1.17.401.1 so you can try to use the ruu which includes everything boot and recovery or just restore your backup and flash the boot.img, the recovery and relock your bootloader and your done
I tryed all that a few days ago because im gonna sell mine too
and iwas on 1.40 and hat no backup that was a pain in the ass luckely someone on xda shared his nandroid backup of 1.17.401.3 with me
Click to expand...
Click to collapse
Thanks, I think I remember reading your posts in the firmware thread, the nandroid backup sounds familiar!
Cool, I'll grab the RUU - do you just relock the bootloader then run it?
I picked up a Nexus 4 instead- I'm just fed up with HTC at the moment!
thunderstorm654 said:
Thanks, I think I remember reading your posts in the firmware thread, the nandroid backup sounds familiar!
Cool, I'll grab the RUU - do you just relock the bootloader then run it?
I picked up a Nexus 4 instead- I'm just fed up with HTC at the moment!
Click to expand...
Click to collapse
yes at first relock your bootloader and then follow the instructions of the ruu setup
Im not selling acctually i trade it for a samsung galaxy note 2 today after work, luckely work today is relaxed so that i can hang around on xda all day
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Hello all,
I usually don't like posting new threads as you can find all you need by searching, but I believe I have a particular situation.
I rooted my phone a while ago using the appropriate methods and then flashed this rom: http://forum.xda-developers.com/showthread.php?t=2440315
I didn't recognize until now, as I am trying to return to stock rom and stuff in order to clean install the new official AT&T update, that this rom somehow also updated my firmware to 3.10.502.2 but I am not S-Off. I didn't/don't know how it upgraded my firmware to this w/o being S-Off but it is. So I have read that if I try and install any other stock rom than my touch screen won't work. And in order for that to work, I think I'll have to gain S-Off and then flash an earlier firmware then flash a rom, but I don't really want to be S-Off for this phone.
Also another stupid mistake I did was not create a nandroid backup of my stock everything before flashing
So in order to accomplish my goal I believe my 2 options are to either gain S-Off, flash an ealier firmware (like 1.26.502.12) and then flash a stock rom or I saw a link that had a stock nandroid backup: http://forum.xda-developers.com/showthread.php?t=2272893
that I can maybe use to restore but will this restore my firmware too?
Any help would be appreciated
Download the 3.17.502.3 RUU and update that way. Backup your data, the RUU method wipes internal storage.
cschmitt said:
Download the 3.17.502.3 RUU and update that way. Backup your data, the RUU method wipes internal storage.
Click to expand...
Click to collapse
Sorry it took me so long to respond but thank you for the help. I appreciate it
Can I still update that way even though I'm still S-On?
spacely8 said:
Sorry it took me so long to respond but thank you for the help. I appreciate it
Can I still update that way even though I'm still S-On?
Click to expand...
Click to collapse
Yes, RUU updating is meant to be done with S-ON.
Hi, I recently returned my phone to stock recovery and OS for OTA update. However I am not sure that I got the proper version for my phone .
My phone works very well except the service hangs low sometimes or fluctuates. I am wondering if this could be due to a version problem. If I have the wrong version recovery for my phone would it be bricked? Or is this possibly a characteristic? Btw I was a fool and never backed up my phone so the recovery and and OS had to be downloaded. The reason I am unsure as to whether I may have the wrong versions is due to the problem where fastboot can't get the software version from the phone. Just blank. So I matched what I could. I believe it was csw_001 or something like that.
Any advice is appreciated.
You need stock recovery and stock for 1.58.502.1
This is the software version I Have . How do I check the recovery version?
Bump
Lancaster84 said:
So I matched what I could. I believe it was csw_001 or something like that.
Click to expand...
Click to collapse
CSW__001 is the correct CID for AT&T. You seem unsure which nandroid you used; if you don't know what you used, how are we supposed to help you?
Did you install the 1.12 or 1.58 nandroid? Do you know what you were on before?
What radio baseband is the phone (listed in bootloader)?
Are you s-on or s-off?
You can try the following AT&T-specific backup thread, which is new and quite handy: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
Or you can try the RUU at the bottom of the following page: http://www.htc.com/us/support/htc-one-m8-att/news/
Some folks were complaining a couple weeks back, that the RUU download would stall out before completed. So hopefully this has been fixed by HTC.
Please don't make multiple threads asking the same question. I'm trying to help you in your other thread.
Also, questions/help threads belong in Q&A.
redpoint73 said:
Please don't make multiple threads asking the same question.
Click to expand...
Click to collapse
@Lancaster84 Please adhere to the advice offered above.
Sorry for the trouble. I will gather the info and will not make duplicate threads.
redpoint73 said:
CSW__001 is the correct CID for AT&T. You seem unsure which nandroid you used; if you don't know what you used, how are we supposed to help you?
Did you install the 1.12 or 1.58 nandroid? Do you know what you were on before?
What radio baseband is the phone (listed in bootloader)?
Are you s-on or s-off?
You can try the following AT&T-specific backup thread, which is new and quite handy: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
Or you can try the RUU at the bottom of the following page: http://www.htc.com/us/support/htc-one-m8-att/news/
Some folks were complaining a couple weeks back, that the RUU download would stall out before completed. So hopefully this has been fixed by HTC.
Click to expand...
Click to collapse
My Device is S-ON
Radio is 1.16.21331931.LA11G
OS 1.58.502.1
Open DSP v38.2.2-00542-M8974.0311
I am Pretty sure i used 1.12 recovery.
i did OTA as soon as i could.
I also just got this IMAGE CRC info from recovery.
rpm: 0xDDD2F5E
sbl1: 0x8891E08E
sbl2: 0x0
sbl3: 0x0
tz: 0x5CB2F1E8
radio: 0x4515FA72
hboot: 0xDEAFD0D8
boot: 0x2FE45494
recovery: 0x53283B2E
system: 0xE5EBE975
Also could you please explain how the radio Image works?
Could it have been changed if i used the wrong recovery?
Regards,
Lancaster84 said:
Also could you please explain how the radio Image works?
Could it have been changed if i used the wrong recovery?
Click to expand...
Click to collapse
If you only installed a nandroid and stock recovery, the radio partition was not modified.
Also, you can't flash a radio with a different CID with S-on, anyway.
I would recommend you relock the bootloader, RUU and start over again, if the intent is to be stock. Its the more reliable way to return to stock, anyway.
Either use my link to the RUU above, or you can also use the bootable RUU (especially if the official HTC download is still broken):
http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Although the concept of returning to stock after unlocking the bootloader, custom recovery etc. just to accept the AT&T OTA (which is not even rolling out yet) is pretty questionable. You understand there have been custom Sense ROMs for weeks now based on the international and Dev Edition Android 4.4.3?
Or are you hoping the OTA will be soon, so you can upgrade the firmware and avoid paying for sunshine S-off?