[Q] WIped Stock Rom - Now Stuck ! - Sprint HTC One (M7)

Hello ~
Hoping for some help...
I did the OTA 4.06.651.4 recently and wiped my rom from recovery. Using an old RUU to revert to 3.04.651.2 won't work unless I am S-off, which I have had no luck doing using various methods (rumrunner, revone), I suspect this is because I have hboot 1.56.
I can't get my internal storage to USB PC mount using TWRP 2.6.3.0 -2.6.3.4, otherwise I would flash a custom rom, or use crushalot's guru recovery.
My unit is unlocked, s-on, hboot 1.56, TWRP 2.6.3.4, most recent firmware, no rom.
Any recovery suggestions would be welcome as I am at the end of my rope!!
:fingers-crossed:

Look HERE
BTW twrp 2.6.3.0 is the latest version for Sprint
Once you are up and running use Firewater to s-off there is a link to it in the thread

I was able to make my phone usable again and learned a lot in the process .
Thanks again for your quick response!

Albinado said:
I was able to make my phone usable again and learned a lot in the process .
Thanks again for your quick response!
Click to expand...
Click to collapse
No worries enjoy
Now S-OFF so you won't have to go through that again if things get messed up again.

Related

[Q] Want to restore TELUS unit to as stock as possible

Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
WorldIRC said:
Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
Click to expand...
Click to collapse
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
crushalot said:
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
Click to expand...
Click to collapse
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
WorldIRC said:
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
Click to expand...
Click to collapse
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
crushalot said:
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
Click to expand...
Click to collapse
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
WorldIRC said:
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
Click to expand...
Click to collapse
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Awesome -- I'll be trying this once my replacement unit has arrived. I'll let you know how everything works out.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Not sure why I'm having so much difficulty with this.
I've restored the 1.44 HBOOT referenced above.
I've restored the stock TELUS ROM via TWRP referenced above.
I can boot into the phone, but I have no touch-screen response now. Also, that TWRP backup did not include the stock recovery and I'm not sure which one I should push.
Tried flashing: http://forum.xda-developers.com/showpost.php?p=41953560&postcount=32 and now I have a red triangle recovery.....
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
crushalot said:
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
Click to expand...
Click to collapse
That site needs a "decryption key"?
WorldIRC said:
That site needs a "decryption key"?
Click to expand...
Click to collapse
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
crushalot said:
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
Click to expand...
Click to collapse
How am I flashing this?
WorldIRC said:
How am I flashing this?
Click to expand...
Click to collapse
Same way as the firmware zip's. You use the same guide from post 1.
crushalot said:
Same way as the firmware zip's. You use the same guide from post 1.
Click to expand...
Click to collapse
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
WorldIRC said:
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
Click to expand...
Click to collapse
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Will give it a shot later today and let you know!
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
WorldIRC said:
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
Click to expand...
Click to collapse
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
crushalot said:
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
Click to expand...
Click to collapse
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
WorldIRC said:
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
Click to expand...
Click to collapse
I had one phone that gave me trouble with revone. I tried it like 20 times and nothing was working. Then I ran all the commands in a terminal window on the phone rather than adb shell and it worked. Can you try that?
There are also some other good tips in the revone thread, but I forget them all and will have to read it again.
It wouldn't have been the recovery as that for sure was the stock recovery. Did you download the stock nandroid or did you make it yourself?

[Q] Downgrading Stock and Recovery touch unresponsive.. Please help!

So friends, Need help on this.
Got a new HTC ONE. updated ota to 2.24 / 4.2.2
hboot 1.54 - son
unlocked the bootloader
now the issue is, cwm touch and twrp touch don't work at all. the touch is absolutely unresponsive in recovery mode.
tried through normal cwm which works fine, but installing a custom rom with aroma gives the same issue.
Have been trying to downgrade to stock 1.29 so that i can go back to hboot 1.44 after relocking the device but it says bootloader signature failed.
any help or advice on either how to downgrade to hboot 1.44 or make the recovery responsive again.
please help, thank you!
androidindian said:
So friends, Need help on this.
Got a new HTC ONE. updated ota to 2.24 / 4.2.2
hboot 1.54 - son
unlocked the bootloader
now the issue is, cwm touch and twrp touch don't work at all. the touch is absolutely unresponsive in recovery mode.
tried through normal cwm which works fine, but installing a custom rom with aroma gives the same issue.
Have been trying to downgrade to stock 1.29 so that i can go back to hboot 1.44 after relocking the device but it says bootloader signature failed.
any help or advice on either how to downgrade to hboot 1.44 or make the recovery responsive again.
please help, thank you!
Click to expand...
Click to collapse
make sure your TWRP version matches your Firmware and Android Version
androidindian said:
So friends, Need help on this.
Got a new HTC ONE. updated ota to 2.24 / 4.2.2
hboot 1.54 - son
unlocked the bootloader
now the issue is, cwm touch and twrp touch don't work at all. the touch is absolutely unresponsive in recovery mode.
tried through normal cwm which works fine, but installing a custom rom with aroma gives the same issue.
Have been trying to downgrade to stock 1.29 so that i can go back to hboot 1.44 after relocking the device but it says bootloader signature failed.
any help or advice on either how to downgrade to hboot 1.44 or make the recovery responsive again.
please help, thank you!
Click to expand...
Click to collapse
You can't downgrade your Hboot when you're S-On ... I'm not even sure if you can when you're S-Off. The problem is not what OS or Hboot you are on, it's the version of TWRP or CWM. What version have you installed? You need the latest version in order for it work as touch drivers were updated in the latest firmware. You have the same OS and Hboot as me and touch works fine in the latest version ... Make sure you have this version installed http://forum.xda-developers.com/showthread.php?t=2173870
Everything works fine on that as I have the same OS and Hboot as you.
AllAboutTheCore said:
You can't downgrade your Hboot when you're S-On ... I'm not even sure if you can when you're S-Off.
Click to expand...
Click to collapse
You can, I done it one day when I was feeling brave
(s-off, obviously..)
Sent from my HTC One using xda premium
redbull123 said:
You can, I done it one day when I was feeling brave
(s-off, obviously..)
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
how you can downgrade hboot to 1.44 with s on ?
Android Benutzer said:
how you can downgrade hboot to 1.44 with s on ?
Click to expand...
Click to collapse
you can't

[Q] update issue

Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
dirtrider129 said:
Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
Click to expand...
Click to collapse
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
update issue
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
dirtrider129 said:
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
Click to expand...
Click to collapse
alray said:
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
Click to expand...
Click to collapse
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
dirtrider129 said:
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.
update question
[/Quote]better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.[/QUOTE]
After lots and lots of research into this before doing I've decided to go with viperone custom Rom, if I understand it right I won't have to mess with s-off for this,please correct me if I'm wrong. But I have found some conflicting instructions, I read somewhere that I will have to copy the boot.img from the Rom and flash it before flashing the Rom then others without that step, so I'm confused, I wanna male sure I do this right the first time. Also are there any files that I need to have updated before flashing a 4.4 sense 6 custom Rom or will it all be included in the Rom?
Thank you
Dirtrider
Hi there
Been a long time since I've posted and hope I'm in the right place. Did a search for my question and wound up here.
My phone is stock and s-on, I haven't done anything to it, it's exactly the same as when it came out the box, but I haven't been able to update the software in settings>about>software updates for a while now, it just keeps coming back with download unsuccessful. Any ideas how I can sort this, or do it another way?
Thanks in advance
Sent from my HTC One using XDA Free mobile app

[Q] flashing rom s-on

I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
dirtrider129 said:
I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
Click to expand...
Click to collapse
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
clsA said:
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
Click to expand...
Click to collapse
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
dirtrider129 said:
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
Click to expand...
Click to collapse
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Oh ok, now I understand. Thanks
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Once I flash the RUU zip, will I lose root also?
dirtrider129 said:
Once I flash the RUU zip, will I lose root also?
Click to expand...
Click to collapse
of course you'll have to re-flash recovery and root again
revone failing
clsA said:
of course you'll have to re-flash recovery and root again
Click to expand...
Click to collapse
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
dirtrider129 said:
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
Click to expand...
Click to collapse
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
coolshritz said:
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
Click to expand...
Click to collapse
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
dirtrider129 said:
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
Click to expand...
Click to collapse
It is not mandatory to S-Off to flash a rom. Your rom will anyway work in a good way.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
dirtrider129 said:
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
Click to expand...
Click to collapse
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
clsA said:
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
Click to expand...
Click to collapse
Do you think firewater will work with viper+Elemental X kernel? If I used the same guide as with ARHD. I tried to s-off with revone by flashing a 4.2.2 viper Rom but I lost all signal and service, so I restored my backup. Also I was wondering since I'm running the 3.17 ruu to update radio and stuff , should I use the 4.18 ruu since its newer? Thanks again for all the help.
UPDATE: Well ran firewater since coudnt get revone to work , took all of like 45 seconds and it said device is s-off. Couldn't believe it after all the trouble I've had.Awesome!

[Q]Back to Stock-Problem

Hi everyone,
I'm trying to get my htc one back to stock, to get the latest ota update (4.4.3), so that I can use the latest venomrom (I think it's 7.0.1 by now).
As far as I understood it, I have to go back to stock to do that, but there were some problems I could not fix.
First my Version is 2.24.206.7 and I can't find any stock recovery for it, I searched the whole internet (that's how it felt), but nothing. I have a backup from my stock rom, that is not the problem.
Second I'm currently S-on, and my hboot is 1.54. I tried to s-off it with firewater, but it did not work.
And I have a custom kernel (ElementalX) installed, is that a problem? If it is, how can I fix it?
I hope someone can help me, and these questions are not already answered somewhere.
Thank you!
umbertoftw said:
Hi everyone,
I'm trying to get my htc one back to stock, to get the latest ota update (4.4.3), so that I can use the latest venomrom (I think it's 7.0.1 by now).
As far as I understood it, I have to go back to stock to do that, but there were some problems I could not fix.
First my Version is 2.24.206.7 and I can't find any stock recovery for it, I searched the whole internet (that's how it felt), but nothing. I have a backup from my stock rom, that is not the problem.
Second I'm currently S-on, and my hboot is 1.54. I tried to s-off it with firewater, but it did not work.
And I have a custom kernel (ElementalX) installed, is that a problem? If it is, how can I fix it?
I hope someone can help me, and these questions are not already answered somewhere.
Thank you!
Click to expand...
Click to collapse
Try to s-off with Rumrunner
after your s-off it's easy to update your firmware and flash ViperOne rom
Thanks for the fast answer!
I wanted to s-off with rumrunner using this guide: http://forum.xda-developers.com/showthread.php?t=2488772
But my firmware is not available, or can I use the universal Rumrunner? I think it does not work with hboot 1.54.
umbertoftw said:
Thanks for the fast answer!
I wanted to s-off with rumrunner using this guide: http://forum.xda-developers.com/showthread.php?t=2488772
But my firmware is not available, or can I use the universal Rumrunner? I think it does not work with hboot 1.54.
Click to expand...
Click to collapse
Yes use the Universal > http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.zip
Ok I tried it with rumrunner universal, but it says: "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!!"
But it is rooted oO any idea?
Thanks
EDIT: I tried it again with my stock rom, but it didn't work either. It said i should flash another kernel, or another rom and retry.
umbertoftw said:
Ok I tried it with rumrunner universal, but it says: "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!!"
But it is rooted oO any idea?
Thanks
EDIT: I tried it again with my stock rom, but it didn't work either. It said i should flash another kernel, or another rom and retry.
Click to expand...
Click to collapse
stock rom plus ElementalX is a good combo
okay, I reinstalled ElementalX (in the right version) as stockish as possible, and after many many reboots, and a few prayers and cries it did WORK!!
Thank you very much
What is the next step, because I don't have any stock recovery for my firmware? or a stock kernel..
EDIT: I was searching for RUU to flash, but the weird thing is, that my CID is O2 germany, and my firmware is O2 UK. What should I flash? There is no exact RUU for my CID, or I did not find it..
I'm really clueless how I could get the latest OTA, I don't find any fitting backup or ruu for my phone..
Or is there any other way to get the OTA's?
umbertoftw said:
I'm really clueless how I could get the latest OTA, I don't find any fitting backup or ruu for my phone..
Or is there any other way to get the OTA's?
Click to expand...
Click to collapse
You now have s-off you can convert your phone to international
you need this
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
use modelid: PN0710000
and simply change your CID to HTC__001
fastboot oem writecid HTC__001
then use this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
or here
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
you should get OTA, then go back to unlocking your bootloader and Rooting as usual

Categories

Resources