[Q] Issue with updating firmware - One (M7) Q&A, Help & Troubleshooting

Hello all. First off, great resource here :cyclops:
I am currently trying to update my HTC One (AT&T) so that I can run the 4.3 Google Play Rom (it sticks on boot screen at the moment)
After that I tried to update firmware as seen here http://forum.xda-developers.com/showthread.php?t=2182823
(I am using model PN0712000 and CID CWS__001)
I have downloaded the appropriate file and followed the instructions but get stuck after step 6 "Type: fastboot oem rebootRUU and wait for device to reboot"
When I type the reboot command it boots to a black screen that just says "HTC" and sticks there. And I try to load the firmware it says "cannot load firmware.zip unknown error"
For reference the device is currently running a 4.2.2 rom (ends TBalden) if that matters
Any thoughts?
Thanks!

S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
EDIT: failed to see that you are att... You'll only be able to ruu to the Cingular ruu without s-off. I can't tell which stock firmware you linked as it brought me to some random post in that thread lol
Sent from my One using Tapatalk 2

InflatedTitan said:
S-OFF? Unless you have a legit GE one, you'll have to be s-off to do it.
If you are, you'll need to delete the zip you are trying to flash in fastboot, reboot comp and try a fresh download.
Also id personally say run the command
fastboot oem writecid 11111111
after you have s-off
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Oh I missed that detail. S-On at the moment. Based upon my limited tenure with rooting and my understanding of the potential flops in S-OFF I will probably stay away from anything that requires that (for the time being at least).
Is there some reason that I can install the 4.2.2 Rom but this 4.3 and Bigxie 4.3 both fail? Do they require firmware change? Something else I'm missing? The installer for this ROM is pretty self explanatory. And I am wiping before hand (both in the ROM install and in TWRP).
Same result every time though (never ending HTC screen)
Thanks again

Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2

InflatedTitan said:
Not sure why it won't boot. There should be no extra steps with this phone such as flashing separate boot.img....
Other ROMs flash fine?
S-off does have it warnings and potentials... But the revone s-off method carries and extreemmmeelllyy small chance of being fatal to your phone. I'd usually try to talk someone out of modding if you're not comfortable with it. But revone is a couple adb commands that are pretty newb friendly
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Well I'm 1 for 3 as outlined above. The bigxie_m7_GPe_odexed_tbalden 4.2.2 works fine. The two 4.3 roms do not work... including ARHD and bigxie_m7_GPe_JWR66V_odexed-signed.
Is there an easy way to just "go back to stock" and then try again? The back to stock tutorials all seem a good bit involved.
Edit: Bigxie 4.3 just worked...maybe I'll just stick with that presuming there are no big issues with it?
Are there any big reasons to update the radio? If so can I do after ROM load?
Thanks for all your help btw.

Still wondering why this particular rom won't load. Any other takers? Bigxie still running at the moment.
I bet mike1986. knows!

Related

Guys I need your help

I just got a HTC vivid from a friend .first thing I did is unlock bootloader flash recovery s-off root . Phone is running gb . Here is where I need your help.I try to.flash jb Rom and it would boot. And when I touch screen phone would freeze and reboot.so I restore. What do I have to do to run jellybean ?
Sent from my HTC PH39100 using xda app-developers app
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
ZeRo2o9 said:
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
Click to expand...
Click to collapse
thanks!!
I'm having a similar problem, but i just dont find the right ICS RUU to flash it seems.
I live in austria, have the htc velocity 4g, with 2.3.7 gingerbread.
Bootloader tells me:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0023
eMMC-boot
Feb 1 2012,01:02:37
what i did for now:
i unlocked the bootloader (with htcdev), put on the twrp-recovery (2.4.4.0) (with hasoons-tool) and also tried wcxrecovery.img (for BoRKed)
wiped it clear, installed the cm10 [cm-10-20130310-NIGHTLY-holiday] and gapps / later BoRKed
since i am s-on i ran the "fastboot flash boot boot.img" command.
And the result is the reboot-cycle (cyanogenmod10 - with freezing short after the pin-code / permanently rebooting with BoRKed).
I read through the forums and found out that i need a newer hboot (ICS) to be able to install Jellybean ROMS.
as mentioned before, i think that i should lock my bootload and flash the right ICS RUU like told in the vivid-developers-forum.
i tried out the htc_vivid_att_RUU_3.26.502.56_US.exe but it told me [error130] wrong model, so i couldnt finish the RUU.
the wire-trick for s-off is a little bit scary to me, so i didnt try that for the time being.
so, for the time being i am a little bit out of clues and would be very glad if somebody could help me out with the right version of the RUU i should flash (and where i could get it) or am i completely off track here?
thnx, joe
Don't you flash the boot.IMG before you flash the ROM?
HTC_Vivid said:
Don't you flash the boot.IMG before you flash the ROM?
Click to expand...
Click to collapse
the step-by-step written guide from hasoon2000 (link) tells me to do it after i installed the ROM.
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Click to expand...
Click to collapse
Don't use twrp 2.4.4...
Switch to 2.4.2.0
Sent from my Vivid 4G using Tapatalk 2
oh, but right now i found it just the other way around.... in the
[SUPERGUIDE] ICS-Root-Flash-Stock
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
Click to expand...
Click to collapse
i will give it a try, thanks!
--
edit:
will switch to 2.4.2.0
kernel flash first and then rom (with trwp-2420 recovery) led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Joehittn said:
kernel flash first and then rom with trwp-2420 recovery led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Click to expand...
Click to collapse
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
homeslice976 said:
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
Click to expand...
Click to collapse
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
mainver: (shows nothing...)
CID: VODAP120
i gave the telstra ruu you uploaded (thank you very much) a try, but it also gave me the model-id-error.
do i have to flash the recovery back (where do i find the stock-recovery? in the backup?), i am always using the twrp242-recovery now.
i tried the steps you wrote down with the same result (boot-cycle).
i think i will have to give the "s-off and super CID" as u mentioned before a try and then use the telstra-ruu. i read that this worked out for some guys in germany. i will do this on saturday, i need to be fully concentrated to do that, not next to work...
thank you very much for now!
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
homeslice976 said:
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
yes, always relocked.
first i ran the RUU (telstra) from the gb-2.3.7 screen, now i tried it from fastboot.
same result - error 130 (model-id)
---------- Post added at 01:36 PM ---------- Previous post was at 01:16 PM ----------
XxSHaDoWxSLaYeRxX said:
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I think you mean this thread [Collection] Stock Roms [3/25/13] but i cant find my provider (austria / a1 [telekom]) there. also there has been no OTA ICS launched in austria...
seems that i have to postpone the s-off, cant find the time to do it right now...
i will revive the thread when i finally went through it.
thanks for your help till now.
cyas

Restoring HTC ONE to Stock (Vodafone UK)

I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
robot1000 said:
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
Click to expand...
Click to collapse
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
gee2012 said:
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
robot1000 said:
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
Click to expand...
Click to collapse
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik. You can`t do anything with the OTA atm, not even flash a Vodafone CWM recovery i`am afraid.
gee2012 said:
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik.
Click to expand...
Click to collapse
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
robot1000 said:
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
Click to expand...
Click to collapse
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
gee2012 said:
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
Click to expand...
Click to collapse
I've just gone into Bootloader and it's showing Hboot as 1.44.0000 !!
Would you mind giving me a brief outline on what I should be doing to get my phone back to vodafone stock?y
Many Thanks
Would flashing the Vodafone OTA zip file in recovery be safe or do I need to S-Off the device?
Please can someone advise
Thanks
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
robot1000 said:
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
Click to expand...
Click to collapse
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
rider5512 said:
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
Click to expand...
Click to collapse
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
robot1000 said:
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
Click to expand...
Click to collapse
Ok... you need to change that ID in the phone.
Reboot the phone to bootloader then fastboot and connect to pc then from your ADB directory on PC issue the command "fastboot oem writecid HTC__001" this will then give you the right ID for the RUU.
Note it's HTC__001.... 2 underscores !

Issues getting root back after update. Soff

I just took the sprint update, and I am soft but locked. Originally used revone but can't unlock after update.
I am still soff what are my options. All I want to do is reinstall su.
Anyone?
htc dev
This is why we NEVER take an OTA HTC makes it harder and harder for us to modify our devices with every update
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
tws101 said:
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
Click to expand...
Click to collapse
HTC Dev unlock will allow you to flash a recovery, root, and install a custom rom if you so choose. Realize however that most custom roms are based on 1.29 and will likely have camera and wifi issues with the new firmware.
If you're S-OFF, you can RUU back to 1.29 and be a-okay, provided that the Sprint OTA does nothing beneficial that you need. If you're not S-OFF, it is possible to S-OFF via revone 0.21 and ADB. Most will tell you that it cannot be done but I managed it with little effort. Just don't try using it with a terminal app on the device, it probably won't work. ADB shell + revone will S-OFF someone locked on 1.31.x.
Personal experience, the 1.31 firmware and update made my cell reception weak as hell and wifi unusable at times even when I had full signal. It apparently activated HD voice, but I haven't noticed. That's what prompted me to S-OFF 1.31 and downgrade with a RUU.
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
tws101 said:
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
Click to expand...
Click to collapse
Long as you're S-OFF, you should be able to flash a 1.29 RUU (like I did) and downgrade. If you dev unlock, you can flash a recovery from fastboot and install supersu from there. There's a supersu flashable zip here:http://download.chainfire.eu/315/
So flash this http://forum.xda-developers.com/showthread.php?t=2250904
Then revone will grant me unlock again then I can use twrp to flash su again?
Correct?
I flashed that RUU and still had S-OFF. Even if you, for whatever reason, lose S-OFF - just HTC Dev unlock. You can flash a recovery, install supersu, and be about your day without ever touching S-OFF.
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
tws101 said:
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
Click to expand...
Click to collapse
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
sshede said:
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
Click to expand...
Click to collapse
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
My understanding is that with a locked bootloader, you're still going to be locked out of changing boot-time code (given that the entire purpose of a locked bootloader is to prevent modifications to onboard software that could compromise secure information), unless you're using a runtime exploit (which is generally for rooting only, and I don't know that there are any such exploits for the Sprint One).
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
krazyflipj said:
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
That was the very first thing I tried.
After updating via OTA i ran revone with -u and got segment fault. Based on the revone thread it will no longer work once you take that OTA. Everyone is getting the segment fault after OTA.
I figured with an update.zip and using fastboot flash update.zip If the update putting an Android-info.txt file might work. I know fastboot flash recovery rec.img fails.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
Okay, now I understand a bit better. Why not just take the 11 minutes required to back up whats on the phone, then HTC dev unlock?
Just to update everyone Indirect helped me solve this issue.
1. Create txt file named android-info.txt
Data in file 4 lines
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
2. Get recovery of your choice and rename it recovery.img
3. Zip files up into zip file name of zip does not matter
4. Run the following fastboot commands
fastboot oem rebootRUU
fastboot flash zip nameofzipfile.zip
fastboot reboot
You now have a recovery of your choice on a LOCKED S-OFF system and can re-flash superuser.
Thank to Indirect!!!

[SOLVED] Some questions about S-OFF and RUU

Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...

[Q] using RUU on HTC One M8 HK

I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)
Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app
It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8
you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on
Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?
neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.
Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup:

Categories

Resources