Anybody here successful in using RumRunner on T-MOBILE HTC-ONE? (with 1.55 HBOOT and 3.24 firmware)?
Steps I performed..
1) Unlocked Bootloader (with HTC DEV)
2) Installed Team Win Recovery
3) Installed SUPER SU from Recovery
4) Using T-Mobile 4.3 ROM (from HTC T-MOBILE RUU)
6) Disabled Firewall (Windows 7)
7) Uninstalled Anti-Virus (Microsoft Security Essentials)
8) Installed HTC Sync (for Drivers only - uninstalled right after)
9) Rebooted PC
10) Disabled Lock Screen (no lock screen on HTC ONE)
11) Made sure fastboot was disabled
12) Made sure usb debugging was enabled
13) Made sure "Verify Apps" was unchecked
14) Made sure "Unknown Sources" was checked
15) Told Super SU to automatically grant super user privileges WITHOUT prompting
16) Ran soju in "administrator" console
It does it's thing and reboots several times but it fails with the following
"FATAL: Download updated package at www.rumrunner.us"
I also tried the same thing with the Android HD Revolution ROM (4.3 - ver 31.6) - fails at the same spot (installed via Recovery). I am able to get to www.rumrunner.us without issues and i'm using ver 0.5..
Note: adb Commands Work, fastboot commands all work..
Same sh*t...cant proceed above this point.
Just did it earlier this week. It ran fine for me.
All I did was unlock, root, done. I was on stock T-Mobile 4.3
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
000zui said:
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
Click to expand...
Click to collapse
Just did one just now actually
1) download the universal option
2) unlock bootloader, twrp and root
3) ran on Linux went through perfectly
FWIW, I had no issues doing it with Windows. T-Mobile (PN07130) [previously] bone stock.
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
@SilverSamurai have you tried using Linux? That's what @funks did and it worked for him. See my thread about GPE conversion for a link to his post. I was hboot 1.55 and it worked perfectly for me on Windows 7. Are you sure your antivirus/firewall is disabled completely?
Perhaps there's some kind of firewall built into your router or modem that's messing with rumrunner? If you're using different PCs on the same network with that result, this could be what's going on.
Not an expert at all on this, just throwing stuff out there.
SilverSamurai said:
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
Click to expand...
Click to collapse
Yeah, worked on the international one, hboot 1.55 & win7, don't remember on which fw. Though i had some problems until i uninstalled some Samsung USB drivers..
Related
At the moment I am currently rooted with S-ON and have SOS-M ICS ROM running. I first relocked my 3D and tried running some RUU's to get me back to stock so I could preform the wire trick and had some issues with that here. Then I went ahead unlocking my bootloader and tried MeanROM to try the Wire trick and kept getting the message "Connect device and Install drivers; Press enter to exit". My drivers are installed and have worked before but I will note that everything that requires cmd to either put a program or file on my 3D hasn't worked (getting the device not found message as well) in which I had to do it manually except when I unlocked my bootloader, in which case, everything went fine.
EDIT: I have gotten meanROM v.17 installed and have fixed my driver issue but now it is telling me that Secondary backup has failed. I have turned off all anti-virus but is still getting the problem I know that it says it shouldn't work with custom ROM's but as I have said, the RUU's have all given me errors and will not allow my device back to stock... What do I do
Has anyone had a problem with the windows USB drivers when trying to apply an RUU or an update like RumRunner?
I'm running Windows 8/64 and have been trying to get my EvoLTE to a known "whole" state .. software running 3.17.651.4.710 (rooted/stock as posted elsewhere here), but have been trying to update my radios.
I'd tried returning to a prior version via RUU, but it reports USB driver issues after the first boot when I think it is trying to boot into recovery.
i.e. the phone boots to an HTC logo and stays there until the host times out.
I've tried using RumRunner to get s-off and update the radios that way, but the results are the same.
The USB drivers installed are the ones included with Windroid and otherwise appear to be properly installed (RUU correctly queries the operating version / runrunner reboots the phone to a "ready to receive" mode (presumably through adb).
Any thoughts?
What is your current Hboot & radio version? If you're on the 3.16 update, there is no RUU for either 3.16 or 3.17. Check out my Hboot guide in the top link in my sig-it'll tell you what S-off method to use based on your current Hboot & software version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What is your current Hboot & radio version? If you're on the 3.16 update, there is no RUU for either 3.16 or 3.17. Check out my Hboot guide in the top link in my sig-it'll tell you what S-off method to use based on your current Hboot & software version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Hboot-2.09.0000
Radio-1.12.11.1210
My problem is I'm stuck in some intermediate phase where things like Moonshine and Rumrunner fail after the first adb "boot into receive" command.
satsuke said:
Hboot-2.09.0000
Radio-1.12.11.1210
My problem is I'm stuck in some intermediate phase where things like Moonshine and Rumrunner fail after the first adb "boot into receive" command.
Click to expand...
Click to collapse
Shoot bigdaddy619 a PM. I know he helped somebody find the right drivers for Windows 8 here recently.
You need to use Moonshine, not Rumrunner.
Sent from my HTC EVO 4G LTE
Try this.
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
latest drivers are HERE
ok ,. figured it out
Two things were going on,.
First thing was the adb was essentially broken whenever the phone rebooted without going into the menu and manually selecting "Disk Drive" mode instead of HTC sync .. with all the rebooting I had to reselect this a half dozen times during the process.
The other was a pretty simple problem with moonshine,. the timeout value to return to adb was 60 seconds, too short for the actual boot times.
Rumrunner had timeouts of 120 seconds .. enough time to get through the menus and complete the process.
Hey all,
I have an HTC One running GE on Sense (it's 4.2.2), with Bulletproof. My computer is an HP, running on Win 8.1.
I made the mistake of not formatting on the upgrade from 4.1 and that's taken away like 4 GB of space for me to use. I was trying to reformat so I could get some of that back, but when I put the phone in download mode in CWM, ADB can't find the phone.
Obviously, I can't reformat without having a ROM ready to install.
I've done a number of things to get it to show up in ADB:
a) checked for HTC sync (not present)
b) checked for other drivers in device manager (not present)
c) enabled the install of unsigned drivers (apparently this needed to be done separately in Win 8.1)
d) tried to point the system to the Universal Naked Drivers (the system says no suitable drivers found)
e) enabled USB debugging
Results are the same - ADB is unable to find it. I see the device under device manager, but when I try to have it use the drivers I want, it says it cannot find them.
Is there something I'm doing wrong here?
karankshah said:
Hey all,
I have an HTC One running GE on Sense (it's 4.2.2), with Bulletproof. My computer is an HP, running on Win 8.1.
I made the mistake of not formatting on the upgrade from 4.1 and that's taken away like 4 GB of space for me to use. I was trying to reformat so I could get some of that back, but when I put the phone in download mode in CWM, ADB can't find the phone.
Obviously, I can't reformat without having a ROM ready to install.
I've done a number of things to get it to show up in ADB:
a) checked for HTC sync (not present)
b) checked for other drivers in device manager (not present)
c) enabled the install of unsigned drivers (apparently this needed to be done separately in Win 8.1)
d) tried to point the system to the Universal Naked Drivers (the system says no suitable drivers found)
e) enabled USB debugging
Results are the same - ADB is unable to find it. I see the device under device manager, but when I try to have it use the drivers I want, it says it cannot find them.
Is there something I'm doing wrong here?
Click to expand...
Click to collapse
windows 8.1 and your older hboot do not get along.
do you have access to another pc long enough to get s-off on your phone so you can run a RUU ?
clsA said:
windows 8.1 and your older hboot do not get along.
do you have access to another pc long enough to get s-off on your phone so you can run a RUU ?
Click to expand...
Click to collapse
I do, but if I need to get s-off first I have a few more questions.
1) Do I need to try to run adb when the phone is on the HBOOT screen or when the phone is in CWM/TWRP's sideload option?
2) What method of getting s-off am I going to be able to use from win7/the version of TWRP I'm in?
3) Is there a way to upgrade the HBOOT so it does work better?
4) What is an RUU?
Some of these questions are probably total noob questions, but it's mostly because the current GE+Sense/Bulletproof combination is insanely stable and this is my first HTC phone.
karankshah said:
I do, but if I need to get s-off first I have a few more questions.
1) Do I need to try to run adb when the phone is on the HBOOT screen or when the phone is in CWM/TWRP's sideload option?
2) What method of getting s-off am I going to be able to use from win7/the version of TWRP I'm in?
3) Is there a way to upgrade the HBOOT so it does work better?
4) What is an RUU?
Some of these questions are probably total noob questions, but it's mostly because the current GE+Sense/Bulletproof combination is insanely stable and this is my first HTC phone.
Click to expand...
Click to collapse
1. you run adb when the phone is plugged into the pc and booted up or when the phone is in twrp/cwm .. it doesn't work in bootloader
2.revone we hope or rumrunner maybe
3. hboot is part of the firmware update .. you need s-off first
4. A RUU is a Retail update utility it's how the carrier returns your phone to stock (out of the box condition)
If you looking to just gain back the space lost from the update all you need is a root explorer
and go to /data/media thats your old sdcard - you can delete what you don't want from here
the new sdcard is located at data/media/0
clsA said:
1. you run adb when the phone is plugged into the pc and booted up or when the phone is in twrp/cwm .. it doesn't work in bootloader
2.revone we hope or rumrunner maybe
3. hboot is part of the firmware update .. you need s-off first
4. A RUU is a Retail update utility it's how the carrier returns your phone to stock (out of the box condition)
If you looking to just gain back the space lost from the update all you need is a root explorer
and go to /data/media thats your old sdcard - you can delete what you don't want from here
the new sdcard is located at data/media/0
Click to expand...
Click to collapse
Thanks boss - I ended up running with revone off an old computer and I seem to be up and running for the moment.
Ok
Sent from my HTC One using Tapatalk 4
karankshah said:
Thanks boss - I ended up running with revone off an old computer and I seem to be up and running for the moment.
Click to expand...
Click to collapse
Also if you still want to return to stock now that your s-off
all the files/info you need are here >> http://www.htc1guru.com/downloads
[S-OFF] after the 2014-OTA ... the incredible _has_ been achieved & is fully working
You might not believe me pals, BUT the incredible and unbelievable HAS BEEN achieved!!!
Full radio [S-OFF] ... on a previously [S-ON & LOCKED]
Droid Incredible 4G LTE - with 2014-OTA (ver. 2.19.605.2)
Credits and terms:
This is NOT my own exploit ... but rather accomplished with the guidance from team "FacePalm" (namely: beaups & dr_drache) ... Full testing and 1st run by myself only ... actual [S-OFF] used the "rumrunner universal" exploit ... but needs a prior TEMP-ROOT (i used the " Inc4GUnlockV61-Windows.zip" kit by mdmower available in our Dinc4G-dev section, link added below) .
As usual: While this process shouldn’t be too risky, bricks can happen. None of me or the actual coders will be accountable. => If you are worried, don’t do it. <=
Again a rather simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, it's not my own work ... i just pass the details along, but still DO NOT ... steal, repackage, 1-click, or whatever method described herein ... for the rest: all disclaimers from "rumrunner.us" do apply!!!
TEMP-ROOT (at least) ... is needed, without it the exploit will NOT work!!! (at least no need for supercid :cyclops ... apart from that, both parts (temp-root & actual s-off exploit) work on Linux _and_ Windows *cough*
1) Once you have confirmed you have "Temp-Root" on your 2.19.605.2 fireball:
http://forum.xda-developers.com/showthread.php?t=2214653 ... for the temp-root script (by mdmower)
2) Download the HTC Universal RUMRUNNER (0.5.0) and unzip it in your working directory:
http://rumrunner.us/downloads-2/
3) follow the RUMRUNNER instructions _closely_ as listed at:
http://rumrunner.us/instructions/
4) wait for a ... longer time until ... rumrunner finishes with: "rumrunner done! hope you enjoyed the rum!"
you are now proper: radio [S-OFF] on your 2.19.605.2 fireball
OPTIONAL:
5) flash ENG-hboot 1.15.1111 ... obtainable from DirtyRacun webpage:
http://unlimited.io/fireball.htm
6) flash custom recovery (e.g. TWRP 2.6.3.0h ... the updated KK4.4 capable version from MDMOWER)
http://mdmower.cmphys.com/category/fireball/
(note that the recent 2.6.3.0k-m (currently?) cannot backup/restore "android-secure" anymore, but 2.6.3.0h is also KK4.4-ready & still can do it) ... ... link to TWRP2.6.3.0h in 2nd post
mdmower fixed this issue in TWRP2.6.3.0.n from 2014-03-03
7) reboot ... ENJOY & REJOICE
8) hit the THANKS-button below
:laugh::laugh::laugh: if it helped you (to achieve the unachievable :laugh::laugh::laugh
thanks for reading ........... (thx again to dr_drache & beaups tips and guidance, temp-root script by mdmower & s-off exploit by rumrunner, 1st testing of this combination "me, myself & i" => SUCCESSFUL)
...
6b) linked the "mdmower: TWRP2.6.3.0h" _only_ for convenience as it is currently NOT available from mdmowers site: (_last_ version able to backup the _AndSec-partition_ as well / already KK4.4-capable)
link remoded as this issue was FIXED by mdmower in his recent TWRP2.6.3.0n build from 2014-03-03
spacer ... just in case ^^
Gonna try it this weekend! Thanks!!!!!
I'm going to give it a try tonight. Thanks!!!!!!!!!!
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
kimba99 said:
8) hit the THANKS-button below :laugh::laugh::laugh: if it helped you (to achieve the unachievable) :laugh::laugh::laugh
Click to expand...
Click to collapse
Already s-off, but this is fantastic news for those who are not (yet). Thanks!
Sent from my Fireball using Xparent Blue Tapatalk MegaSuperb Pro
I haven't be able to find Dinc4G_UnlockV61-Windows.zip Any chance someone can point me there?
I think you meant http://forum.xda-developers.com/showthread.php?t=2214653
I just got done with it. I had to run it a couple times. It failed the first time around. But the phone is now s-off
Thanks,
Here you go.
http://forum.xda-developers.com/showthread.php?p=39763697
Sent from my ADR6410LVW using xda app-developers app
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
kimba99 said:
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
Click to expand...
Click to collapse
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
Yes.....that is mdmower's unlock script.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
yeah, right ... seems like i renamed the script after download (quite some while ago), corrected the name in the start-post & ... added a remark about TWRP-2.6.3.0h
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
puhleez said:
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
tj13 said:
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
Click to expand...
Click to collapse
So based on what everybody is saying I actually had temp root since I had the status bar with no lock ring. I guess the issue was with rumrunner then.
I also tried to get an unlock from htcdev but encountered an error 160 invalid MID I think.
Device appears under adb devices.
Thanks for the reply.
Sent from my TouchPad using Tapatalk
USB debug is enabled?
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
Ran temproot, the phone booted to statusbar, no unlock-ring.
Tested sudo ./adb shell and had #: access, able to cd into /data/data etc and list files.
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Thanks
stevey500 said:
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Click to expand...
Click to collapse
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux (most successful ppl here did it on Win, albeit Win8.x _might_ be problematic as well):
Code:
1) 32-bit Linux (Ubuntu is preferred)
•Live CD’s are fine.
•Live USB is fine.
•Native install is fine.
•VM’s are unsupported.
•64-bit Linux may work with 32 bit libraries, but is unsupported.
2) A _working internet_ connection (on your linux system!)
3) USB _debugging enabled_ on your device (in developers options)
4) Fastboot _disabled_ on your device (settings -> battery -> UNcheck “fast boot”)
otherwise ... try on a Win7 machine, only HTC drivers _installed_ (NO HTC-Sync installed, but completely removed/deinstalled!!), NO other phone software installed (Kies, PDAnet etc) ... firewalls / internet security _disabled_, otherwise network filtering could get you stuck ... same restrictions 2), 3) & 4) from linux-rumrunner also apply!
maybe it's your linux firewall that intercepts the needed bits???
good luck
kimba99 said:
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux
maybe it's your linux firewall that intercepts the needed bits???
good luck
Click to expand...
Click to collapse
Thanks for the response!
I ran it in 32 bit ubuntu Linux, all files on my home directory. No firewall, direct connection to ISP. I followed their guide exactly except putting the phone into temp-root before I started.
The rumrunner binary in linux appears to find the phone, reboot to bootloader, finds bootloader, reboots to find ADB... at this point is when I realize rumrunner has removed temp-root as I can see home-screen icons and unlock ring, and later on waiting a few minutes further, rumrunner says no SU and cannot continue.
I will try to run rumrunner binary in windows 7 with only HTC drivers installed, open firewall, boot back up into temp-root and see what it does. :good:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
kimba99 said:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
Click to expand...
Click to collapse
Cool, maybe that is the case then. I'll try windows temp-root & windows rumrunner with HTC drivers as soon as I have a moment to try. Hope it works! This phone is a sluggish borderline unbearable crapper with HTC's stock firmware. I know it's got to be ten folds more tolerable with CM11's latest release for it.
I really appreciate the responses.
I want to install an OTA, but I had rooted it using TWRP and then followed so many procedures in trying to restore to stock that I think my phone's wasted. (It's functioning normally, but I can't help the feeling I've done something untowardly to it).
I have been doing a lot of reading, but I apparently suck since nothing seems to make sense (or that everything seems so disconnected). It appears that what could be one long, detailed post about something is to be found in many different posts, but I understand that since there are so many phones and each one probably needs its own way of being handled. So without complaining any further, I'll just let you know what I've done so far, and hopefully someone is able to tell me what the hell is wrong with me. And my phone.
Here's what I have with me right now:
Device: HTC One SV (Boost mobile) - K2_CL, OS- 4.1.2 (the OTA is 4.2.2)
Tampered, relocked, s-on.
adb is installed
fastboot is installed
android SDK with 4.1.2 and 4.2.2 packages installed
htc toolkit utility is installed
recoverytest.img from androidruu files.
revone
All right, I installed adb, fastboot, an htc utility toolkit, downloaded 3 different img files (one says recoverytest.img, which is from androidruu.com/k2_cl, another one was put here on xda by one of the members, and that was simply recovery.img, and another one called HTC_One_Sv_K2_Ul_boot_signed.img <-- this is probably the wrong file since my bootloader screen says k2_Cl).
Prior to this, a few months ago, my phone was rooted. SuperSU was working fine, and one day somehow I lost the root access when SuperSU upgraded. Tried a few methods to upgrade manually but none worked. Not sure if this is of any importance.
So after installing all those above, I did a variety of commands like revone, fastboot flash recovery.img, fastboot oem lock, fastboot flash boot recovery.img, all based on what was mentioned one one thread or another on the forum and mostly all of them gave me some kind of an error.
So I'm stuck now. My phone does nothing. When I reboot from bootloader, it says in red "this is for development purposes only, blah, blah". When I download the update and try installing it, the phone simply restarts. When I try to do factory reset from the hboot, the phone simply goes back into fastboot menu. My phone apparently doesn't have an RUU, only a recoverytest.img.
Here's where I am and I want to do what next. I jsut installed android sdk, and installed 4.1.2 package (which is the current version on my phone), and I want to update to 4.2.2, which is the latest update for htc one sv on boostmobile (installed the package for that in sdk also).
(A lot of people were also asking for cid, mid and phone model, and I have no clue how to make sure that the .img file is the same as my phone's).
I know I am all over the place, and call me a knucklehead, but I genuinely do not understand a lot of the things that are mentioned on the forums. Every thread mentions a process, and within each process is contained a subprocess which I equally do not know.
Thanks for any help with this!
PS: While I go from fastboot usb to hboot, the screen flickers for a couple seconds an dmessages like "sd checking: no image or bad image" appear for a couple seconds and then I see the hboot menu.
Edit:
Here are some, but not all, of the forums/threads I was trying to follow:
http://forums.androidcentral.com/verizon-droid-dna/287135-revone-s-off-root-method-help.html
http://androidforums.com/one-sv-all...root-without-overwriting-recovery-kernel.html
http://forum.xda-developers.com/showpost.php?p=38018890&postcount=78
http://forum.xda-developers.com/showthread.php?t=2292432
http://forum.xda-developers.com/showthread.php?t=2405050
http://forum.xda-developers.com/showpost.php?p=42371333&postcount=1480
http://forums.androidcentral.com/htc-one-sv/279026-htc-one-sv-ruu.html
http://www.androidfiles.org/?developer=K2_CL
http://forum.xda-developers.com/showpost.php?p=43266179&postcount=6
The way I understand how to do this (in layman terms) is as follows:
1. Restore to stock {by first turning S-Off, then lock the bootloader, and then RUU. I cannot get S-off using revone (revone failed, error code 2 or error code -1); the bootloader is "relocked", and I cannot get to do anything with the RUU (iow I don't know what to do with it)}.
2. Restore to factory settings.
3. Download and install the OTA 4.2.2 update.
You don't need to go S-Off to return to stock, just relocked. Here is the RUU for your phone:
http://goo.gl/0cgV6d
Run as admin. Turn off anti-virus. Have more than 30% battery life. Follow instructions as the program loads and accept whatever.
OTA zip:
http://goo.gl/ckfYQj
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
ravisoni said:
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
Click to expand...
Click to collapse
You're welcome. It is the 4.2.2 update. My understanding is that there is nothing newer. There were reports of a 4.4 update for the Boost variant, but believe it was a mistake, or at least jumping the gun by quite a bit.