Related
Do you currently have a bootloader that is S-OFF (thanks to LazyPanda/DirtyRacun)?
Do you need to take your phone into Sprint for repairs, and want to set it to S-ON again?
This guide will show you EXACTLY how to go from S-OFF to S-ON again. Not only that,
but it will be like you just got your phone brand new from Sprint again, ***LOCKED*** and S-ON.
This sure looks like a lot of steps, but it's not really. I've just detailed everything out
so there is no confusion.
This process wipes your phone completely including internal storage (internal sdcard).
It does NOT wipe your external sdcard (the one you physically put in the device).
Requirements
Download one of the following bullet points:
1.13.651.1 RUU - MIRROR (Windows ONLY) - af533d16d6131c7bbd4ef281441cc096
PJ75IMG.zip (External Sdcard Required) - a429f8150560433c264887e3d85ba368
And also download the RegawMOD S-ON Writer Utility (Windows ONLY - SOURCE) - 05d6800bd66f7a9150f64fd203230ccf
Steps
This guide assumes that you have either the HTC drivers from my rooter
or LazyPanda S-OFF installed (since you used them to gain S-OFF/root).
Charge you battery to above 50% (preferably fully charged)
Make sure your phone is connected to the computer and make sure Settings > Developer options > USB debugging is checked on your device.
If you would like to skip making a nandroid backup, skip now to Step #10 if you downloaded the RUU, or Step #11 for the PJ75IMG.zip
Reboot to recovery. If you don't know how to do that, download my RegawMOD Rebooter and use that.
Press "Mount" and make sure the following are checked on
Unmount Cache
Unmount SDCard
Unmount Internal
Using external SDCard (this is vital, because the following process wipes your internal sdcard)
Press the back button to get to the main menu.
Press "Backup" and swipe the slider to the right to begin your nandroid backup.
Once complete, press "Back" to go to the main menu.
Press "Reboot" then "System" to reboot back into Android.
If you'd like to backup the nandroid to your computer, do that now by mounting your sdcard to your computer and copying it over.
If you downloaded the PJ75IMG.zip instead of the RUU, skip to Step #11 NOW
Now it's time to run the RUU on your computer. Double click on the exe to run. The following tells you what to do on each screen of the RUU
Check the box next to "I understand the caution indicated above and have reviewed the ReadMe." then click "Next"
Check the box next to "I have completed the steps indicated above" then click "Next"
Click "Update"
Click "Next"
Click "Next". The RUU will begin to update your phone
This process will take ~10 minutes and sometimes up to 20. Be patient!
Click "Finish" when it completes. Once complete, your phone will begin to boot into Android.
Now skip to Step #17
Copy the PJ75IMG.zip you downloaded onto your external SDCard. You can either:
Select Disk Drive mode instead of Charge Only from your device's drop down menu. Then select Charge Only again once it's done copying.
Remove your sdcard and put it in a card reader in your computer (put it back in the phone after)
(Advanced) Run the command 'adb push PJ75IMG.zip /sdcard/ext_sd/'
Power your device completely off. (We are preparing to boot into the bootloader)
Hold Volume-Down and Power until it boots into the bootloader.
This make take a few tries to get into the bootloader, it's finiky.
The 3 button LED's will flash a few times, this is normal.
The "Enable Fastboot" option in Settings > Power has nothing to do with booting into the bootloader (even though many think it does)
The PJ75IMG.zip will automatically start being read. This takes a LONG time (up to 20 minutes depending on sdcard speed).
When it asks you if you want to flash, press Volume-Up to accept. This will also take up to 20 minutes to flash.
Your device may reboot a few times as well, this is normal. The only downside is that it has to reload the PJ75IMG.zip again. Again, normal.
When it's completely finished flashing and prompts you, press the Power button to reboot the device.
Once it's fully booted, skip all of the setup details by pressing "Next"/"Skip" and enable USB Debugging (See Step #2).
You can sign in to things if you want, just for time sake I say to skip it here.
Go into Settings > Developer options and check USB debugging (make sure it's on)
Now it's time to run the RegawMOD S-ON Writer Utility you downloaded to your computer earlier
After double clicking the exe, you will be asked if you want to run the utility. Type either y or Y and hit enter to accept.
It will run automatically and tell you what it's doing along the way.
If there are any errors, it will tell you as well.
You may get an extra reboot after it writes S-ON, it's normal.
You may get the Hands-Free-Activation pop up as well, that's normal as well.
If the RegawMOD S-ON Writer Utility runs all the way through without errors, you are now fully stock! Congrats!
You now have S-ON and ***LOCKED*** on your bootloader and there is no way to prove that it wasn't!
Post any questions here, or join me in #RegawMOD on irc.freenode.net - WEBCHAT
Consider donating to me to support my work. It is much appreciated and respected by myself.
If not, please hit the "Thanks" button on this post! That also helps me out. OR you can do a tasteful combination of both
Reserved....
regaw_leinad said:
Reserved....
Click to expand...
Click to collapse
Awesome. Thanks for this, I have no doubt people will find it highly useful (though I hope I never need to use it!)
Just to let everyone know, I tested this whole process 6 times (including lazypanda s-off again). Trust me, this guide took a LONG time to write up correctly. Let me know if there are any huge mistakes, it's 5am here and I stayed up all night getting this ready for everyone and I'm pretty tired.
anYONE gUIDE hUH? Man your like the KING with kinds it seems? Some one will def find this useful. WIth they would set these as Sticky's. Hate to see this get lost in the Board. Good stuff man!!
Great job regaw! This is the last piece of the puzzle.
We'll get it stickied over at AF.
@Everyone: Throw this man a fist full of dollars please. Let's give back what he's put in!
Sent from my EVO using xda app-developers app
Granite1 said:
Great job regaw! This is the last piece of the puzzle
@Everyone: Throw this man a fist full of dollars please. Let's give back what he's put in!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
^^^^^^^^^^THIS^^^^^^^^^^^^^^^
Sent from my EVO using xda premium
Any very detail guide like this to get S-off from stock ROM that has been rooted?
Do you need to relock the bootloader before running the RUU?
I wish I had extra cash laying around so I could donate but I really appreciate this. Unfortunately, I already need it; I cracked my screen =(
SPreston2001 said:
Do you need to relock the bootloader before running the RUU?
Click to expand...
Click to collapse
You cannot run an RUU unless you have relocked your bootloader.
---------- Post added at 11:20 AM ---------- Previous post was at 11:16 AM ----------
Also, to the OP, your have your links backwards, the link to the RUU is actually for the PJ75IMG and the link to the PJ75IMG is actually for the RUU
Whoa you are fast!
I was going to say the same thing about the links..
DNarsingh said:
You cannot run an RUU unless you have relocked your bootloader.
Click to expand...
Click to collapse
So just to be sure...if we are using the modded HBOOT 1.12.1111 do we need to revert to 1.12.0000 first before relocking?
-Apollo- said:
So just to be sure...if we are using the modded HBOOT 1.12.1111 do we need to revert to 1.12.0000 first before relocking?
Click to expand...
Click to collapse
Running the RUU reverts you to the stock HBOOT, which you cannot do without relocking your bootloader first.
DNarsingh said:
Running the RUU reverts you to the stock HBOOT, which you cannot do without relocking your bootloader first.
Click to expand...
Click to collapse
Ok, thanks! Just wanted to be sure there were no ill-effects from locking on modded version.
If you try to re-lock the bootloader BEFORE flashing back to a stock hboot you will PERMANENTLY brick your phone. Just do everything in the order the OP has it. I relocked following this post exactly and it worked just fine.
xhaui said:
If you try to re-lock the bootloader BEFORE flashing back to a stock hboot you will PERMANENTLY brick your phone. Just do everything in the order the OP has it. I relocked following this post exactly and it worked just fine.
Click to expand...
Click to collapse
I was under the impression that an RUU could not be ran unless your bootloader was locked. That's how it was was my HTC Jetstream and I believe I have read that within these forums a few times as well. Please correct me if I am wrong though.
---------- Post added at 12:24 PM ---------- Previous post was at 12:04 PM ----------
DNarsingh said:
I was under the impression that an RUU could not be ran unless your bootloader was locked. That's how it was was my HTC Jetstream and I believe I have read that within these forums a few times as well. Please correct me if I am wrong though.
Click to expand...
Click to collapse
EDIT: Actually, never mind. You are right, I guess that since LazyPanda changes it to just ---LazyPanda--- instead of ***Locked***, you wouldn't need to relock before running the RUU since it technically isn't considered unlocked anymore.
thread stuck
il Duce said:
thread stuck
Click to expand...
Click to collapse
We love you Duce....thanks brotha!!.How ya been
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
xhaui said:
I wish I had extra cash laying around so I could donate but I really appreciate this. Unfortunately, I already need it; I cracked my screen =(
Click to expand...
Click to collapse
OMG come hand LOL. Really? Man i feel bad for ya. Hasnt been a good week for ya huh? im right there with ya pal!!>.
DNarsingh said:
I was under the impression that an RUU could not be ran unless your bootloader was locked. That's how it was was my HTC Jetstream and I believe I have read that within these forums a few times as well. Please correct me if I am wrong though.
Click to expand...
Click to collapse
Thats what I always thought. Anyway we can get some clarification on this? I tried to run the ruu before relocking the bootloader and it gave me a error message. I cracked my screen and needed to take my phone back to Best Buy but just decided to flash the stock rooted rom after it gave me the error message.
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
So just trying to prepare myself for when I get my phone back from repair that HTC puts 4.3 on there instead of 4.1.2 since Att release is out now.
My understanding 4.3 comes with hboot 1.55 what are my chances of achieving s off with the rum runner if this happens or any other ways
I know if it gets sent back as 4.1.2 a d hboot 1.44 I'm good.
Just curious as to what I'm in for if they do put 4.3 on there
Sent from my HTC One X+ using XDA Premium HD app
I'd like to also find out some information regarding this topic. I had my device swapped because I couldn't take the purple camera any longer.. and the replacement had 4.1.2 installed, but when I booted it and during setup, I let the 4.3 OTA come through and installed the update (not even thinking about the hboot version).. So I now am stock 4.3 w/ hboot 1.55 - I'm assuming at the moment that I cannot really do much until we get 1.55 hboot correct? For the fun of it, I tried running the AT&T 1.26.512 RUU but it failed
OP: not hijacking your thread, just didn't want to create a new thread with the same topic..
No sounds like you have the exact problem I could have
In warranty disclaimer it says phone will be loaded with most recent os released for your carrier.
Now that 4.3 is out I'm afraid HTC will just load that on their
Sucks I had a off before camera problem
Sent from my Nexus 7 using XDA Premium HD app
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Fberry said:
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Click to expand...
Click to collapse
You can use moonshine or revone (which I used) with HBOOT 1.44, however with HBOOT 1.54 you need to use rumrunner but it is not the same unlock as with revone because with rumrunner you actually need to unlock the bootloader via HTCDEV.
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
ac3kill said:
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
Click to expand...
Click to collapse
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
EsJayEs said:
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
Click to expand...
Click to collapse
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
noobsquared said:
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
Click to expand...
Click to collapse
I tried it anyway. Here's the result:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
No matter how many times I've tried it. I followed the directions exactly as stated. The only thing that changed is now I have the "tampered" flag in the bootloader.
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
EsJayEs said:
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
Click to expand...
Click to collapse
there is something new with 4.3, they kinda block the adb. when i was on 4.1.2 the adb "fastboot" command working just fine, but once i ran the ruu and update my htc one to 4.3, now when i type adb devices it show me my device but OFFLINE. so it might be a new hidden menu to activate the adb port again "make it read the device" or maybe we need a new driver "which i doubt"....
Well I saw they have the Att firmware on rum runner site 3.17. Whatever the rest is so we should be fine at getting soff I just have not seen someone say they have since Att stock is is hboot 1.55 but ill figure it out when my pphone get back
Hoping its 1.44 hboot and I can downgrade and unlock bootloader without HTC knowing this time but that would be to easy and I'm sure ill have stock 4.3 1.55 we shall see this week !
Sent from my HTC One X+ using XDA Premium HD app
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
noobsquared said:
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
Click to expand...
Click to collapse
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
EsJayEs said:
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
Click to expand...
Click to collapse
I'm having the same thing.
One time it says offline, the other it says connected.
I've ran rumrunner_m7_3.23.666.1 almost 5 times now with the same result. The only difference is that my HBOOT screen says tempered but I still have S-On and I don't think it's getting anywhere. It does the pouring and restarts the phone quite a few times but I'm guessing it's not having any luck. Maybe rumrunner only supports up to HBOOT 1.54 and since we are HBOOT 1.55, it won't work?
Here is how the process has went the 6th time I believe when I ran it:
==================== rumrunner S-OFF 0.0.3 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
pouring (1).............................
pouring (2)...............................
pouring (3)...............................
pouring (4)...............................
pouring (5)................................
pouring (6)...............................
pouring (7)...............................
pouring (8)...............................
Wait 30 seconds, power on device, run rumrunner again.
Press ENTER to exit
---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------
And here is what my adb says after running that process 6 times:
W:\Downloads\Android\HTCOne\htcone>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT********** device
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
I may have figured it out.
I had version 3.17.502.3 on AT&T HTC One and I've been running rumrunner for .666 version.
I just downloaded rumrunner_m7_3.17.502.3 and about to give it a shot. Will keep everyone posted. Sorry if I annoyed anyone with my dumb post and mistake :silly:
I never got to the pouring part, but I was also apprehensive about using Rumrunner for a different version. I can't remember where I read it on here, but one of the 2.24 users that did it bricked his phone. Or rather it bricked itself during it's first phone call after s-off. No confirmation if it was due to using a different rumrunner than what he had, but I wouldn't want to be the first guy to try. For that, I thank you.
Interesting how the version you used doesn't have all of those test waiting for fastboot and adb.
Thanks for the kind words and motivation EsJayEs
I'll keep everyone posted. Someone has to be the bait or nobody gets the goodies :good:
So, when I ran the right version, it says:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (26/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
I'm guessing because I tried wrong version and now my HBOOT says tempered. Maybe I'll relock bootloader and try to run RUU to go back to stock and start over. Aah, I wish I would have never gone to G2 and stayed with my HTC One that I had working and perfectly setup!
I re-locked the bootloader, installed the latest AT&T RUU, unlocked the bootloader, then ran rumrunner_m7_3.17.501.3 which matches my system version and OS version in HBOOT menu but it seems like it's still not working.
Here is the output after running rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Still don't have my phone sounds like it could be because hboot 1.55
But I don't get why our Att firmware is on rumrunner site if hboot 1.55 don't work because the 3.17 firmware ones with hboot 1.55 and they make it very clear to be stock.
Man I need my phone back I'm ready to start trying
Sent from my HTC One X+ using XDA Premium HD app
That's the exact problem I had time and time again.
Double check you have the right rumrunner for your firmware. Im sure you have.
Don't worry about doing the fastboot bit, you know its all connecting fine.
Boot your phone as normal, on to the phones home screen. Open a command prompt in the same folder as yout ADB link.
Type ADB Devices, and it should find your phone, model number and so on. Leave the window open. Then start rumrunner. It worked for me 1st time then.
Steve
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
As above
Steve
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------
That was not me just copied it from another forum. If I had a pc I would try. Hope it works for you guys.
Sent from my HTC One using XDA Premium 4 mobile app
While rooting / SOFFing my One Max, I had to look all around to find all the parts. I wanted to create a guide so other people could get it faster / easier than I could .
This is for the Sprint HTC One Max, not sure how other devices will react. rumrunner is for more than just the Sprint version though.
I TAKE NO CREDIT. IM JUST PUTTING A GUIDE TOGETHER. ALL CREDIT GOES TO PEOPLE WHOM MADE THIS HAPPEN.
Credit: (In no order) Please donate to them! They deserve it.
rumrunner: SOFF program.
scotty1223: Unlocking/removing tampered flag
Flyhalf205: Custom recoveries
carl1961: Unsecure kernel
HTC for an awesome phone
If I forgot anyone, let me know! Everyone that made this happen is awesome!
DISCLAIMER: IT IS NOT MY FAULT IF YOUR PHONE YELLS AT YOU AND RUNS AWAY BECAUSE YOU DID SOMETHING WRONG.
Step One: Unlock your bootloader at htcdev.com. Create an account and follow their instructions. When it asks you for your device put "all other support devices"
Step Two: Make sure your ADB/Fastboot prompts are working. Here's how we check that:
a. Make sure USB debugging is on.
b. Plug in your phone, then open your adb prompt.
c. Issue the command adb devices. If your serial number is shown, adb is working.
d. While still in the adb prompt, issue the command adb reboot bootloader. Your phone will reboot in to your bootloader
e. Now issue the command fastboot devices. If your serial number is shown, fastboot is working.
f. Reboot your device so it's on and fully boot up. It's time to get set up!
Step Three, Getting all the files needed on your craptop. (Computer, just kidding)
a. Download your choice of recovery from flyhalf205's thread (TWRP didn't play nice with my phone, so I used CWM, but your results my vary).
CWM: http://forum.xda-developers.com/showthread.php?t=2498749
TWRP: http://forum.xda-developers.com/showthread.php?t=2498746
b.Then download this superuser.zip. :http://www.mediafire.com/download/v27kh5nkpo3nfum/superuser.zip Place it on your phone somewhere.
c. Then download rumrunner from beaups' thread: http://forum.xda-developers.com/showthread.php?t=2525375
d. Then download carl1961's unsecure kernel : http://www.mediafire.com/download/rrfelsllgomrpix/Sprint_One_Max_1.16.651.4_Unsecure_kernel.zip
Step Four: Lets do this thing!
a. First, we flash a custom recovery. Place the recovery you downloaded from flyhalf205 into the same directory as your adb/fastboot stuff.
b. Plug in your phone, issue the command adb devices just to make sure there is a connection. (can never be too careful now.)
c. If all is good and a serial number is shown, issue the command adb reboot bootloader.
d. You should see a string of words on your phone's bootloader saying "fastboot usb". Issue the command fastboot flash recovery "NAME OF RECOVERYFILEHERE".img. If all goes well. You now have a custom recovery, woop!
BOOT INTO THE RECOVERY AND MAKE A NAND. NOT OPTIONAL.
While in recovery, go ahead and flash the superuser.zip as you would do any other zip.
e. Now open the kernel and extract the boot.img file, place it in the adb/fastboot place.
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand .
HOW-TO Re-enable your fingerprint scanner!
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
a. Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
b. Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
I'll help if I can. Have fun everyone!
If I can recommend rumrunner first **for Verizon versions** which soff, unlocks bootloader (vice htcdev) , installs unsecure kernel and roots. Htcdev unlock voids warranties for some carriers. Then install recovery of choice.
Lastly I would insert a line to remind everyone to donate to the devs for countless hours put in.
EDITED for versions
Any issues with fingerprint scanner
Thanks PUNK9 for putting this guide together!! Thanks to the devs for their hard work!!
I've had my One Max for 2 weeks and I must root it!!!
I read that unlocking the One Max caused issues with the fingerprint scanner. Is this your experience?
Also, I am a fan of TWRP. What issues did you expereince that caused you to go to CWM.
Thanks,
Gary
Jiggity Janx said:
If I can recommend rumrunner first **for International and Verizon versions** which soff, unlocks bootloader (vice htcdev) , installs insecure kernel and roots. Htcdev unlock voids warranties for some carriers. Then install recovery of choice.
Lastly I would insert a line to remind everyone to donate to the devs for countless hours put in.
Click to expand...
Click to collapse
Do I need unlock the bootloader via HTCDev and flash insecure kernel after S-OFF in order to get root on VZW One Max ?
GaryJohnSr said:
Thanks PUNK9 for putting this guide together!! Thanks to the devs for their hard work!!
I've had my One Max for 2 weeks and I must root it!!!
I read that unlocking the One Max caused issues with the fingerprint scanner. Is this your experience?
Also, I am a fan of TWRP. What issues did you expereince that caused you to go to CWM.
Thanks,
Gary
Click to expand...
Click to collapse
TWRP would go on the "swipe to unlock" screen I wasn't able to swipe it. So I used the classic version of CWM.
Also yes, unlocking the bootloader stops the fingerprint scanner from working. Here is how you get it back working (Which i'll update the OP for)
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
Have fun!
androitri said:
Do I need unlock the bootloader via HTCDev and flash insecure kernel after S-OFF in order to get root on VZW One Max ?
Click to expand...
Click to collapse
No to htcdev. Rumrunner does all of that for the verizon version EDITED OUT
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version and I *believe* it does all that for all versions.
Click to expand...
Click to collapse
anyone use rumrunner and the boot image he attaches with a sprint phone?
---------- Post added at 12:59 PM ---------- Previous post was at 12:18 PM ----------
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version and I *believe* it does all that for all versions.
Click to expand...
Click to collapse
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
from rumrunner prereq's.
What is considered a device blocked by htcdev?
Having some work issues lately... as in I may not have work in the next week or two. Removing some of the things I have posted recently because I just was not thinking clearly. My apologies.
Jiggity Janx said:
Having some work issues lately... as in I may not have work in the next week or two. Removing some of the things I have posted recently because I just was not thinking clearly. My apologies.
Click to expand...
Click to collapse
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
i haveflashed Then download carl1961's unsecure kernel, and i have supersu installed provided by above link. bootloader unlocked by HTCDEV. Same output, constantly.
I receive this for a rumrunner output, what am i doing wrong???
Never getting any popups to give ADB root access, no popups for any escalation.
Starting from usb debugging mode android OS up.
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (38/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (32/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
---------- Post added at 04:08 PM ---------- Previous post was at 03:12 PM ----------
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version EDITED OUT
Click to expand...
Click to collapse
DeadPhoenix said:
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
Click to expand...
Click to collapse
From rumrunner instructions -
Prerequisites
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.
Finger print
Punk9 said:
TWRP would go on the "swipe to unlock" screen I wasn't able to swipe it. So I used the classic version of CWM.
Also yes, unlocking the bootloader stops the fingerprint scanner from working. Here is how you get it back working (Which i'll update the OP for)
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
Have fun!
Click to expand...
Click to collapse
Finally done and S-OFF. How do I go 'bout fingerprint again???
I was unable to use htcdev.com to unlock the bootloader. I am with Verizon, perhaps thats the issue, not sure. The error I received
Error Code: 160.
Error Reason: MID Not Allowed
Tried using rumrunner and of course that failed due to the fact the bootloader is still locked and there is no unsecure kernel.
Am I missing something?
Punk9 said:
While rooting / SOFFing my One Max, I had to look all around to find all the parts. I wanted to create a guide so other people could get it faster / easier than I could .
This is for the Sprint HTC One Max, not sure how other devices will react. rumrunner is for more than just the Sprint version though.
I TAKE NO CREDIT. IM JUST PUTTING A GUIDE TOGETHER. ALL CREDIT GOES TO PEOPLE WHOM MADE THIS HAPPEN.
Credit: (In no order) Please donate to them! They deserve it.
rumrunner: SOFF program.
scotty1223: Unlocking/removing tampered flag
Flyhalf205: Custom recoveries
carl1961: Unsecure kernel
HTC for an awesome phone
If I forgot anyone, let me know! Everyone that made this happen is awesome!
DISCLAIMER: IT IS NOT MY FAULT IF YOUR PHONE YELLS AT YOU AND RUNS AWAY BECAUSE YOU DID SOMETHING WRONG.
Step One: Unlock your bootloader at htcdev.com. Create an account and follow their instructions. When it asks you for your device put "all other support devices"
Step Two: Make sure your ADB/Fastboot prompts are working. Here's how we check that:
a. Make sure USB debugging is on.
b. Plug in your phone, then open your adb prompt.
c. Issue the command adb devices. If your serial number is shown, adb is working.
d. While still in the adb prompt, issue the command adb reboot bootloader. Your phone will reboot in to your bootloader
e. Now issue the command fastboot devices. If your serial number is shown, fastboot is working.
f. Reboot your device so it's on and fully boot up. It's time to get set up!
Step Three, Getting all the files needed on your craptop. (Computer, just kidding)
a. Download your choice of recovery from flyhalf205's thread (TWRP didn't play nice with my phone, so I used CWM, but your results my vary).
CWM: http://forum.xda-developers.com/showthread.php?t=2498749
TWRP: http://forum.xda-developers.com/showthread.php?t=2498746
b.Then download this superuser.zip. :http://www.mediafire.com/download/v27kh5nkpo3nfum/superuser.zip Place it on your phone somewhere.
c. Then download rumrunner from beaups' thread: http://forum.xda-developers.com/showthread.php?t=2525375
d. Then download carl1961's unsecure kernel : http://www.mediafire.com/download/rrfelsllgomrpix/Sprint_One_Max_1.16.651.4_Unsecure_kernel.zip
Step Four: Lets do this thing!
a. First, we flash a custom recovery. Place the recovery you downloaded from flyhalf205 into the same directory as your adb/fastboot stuff.
b. Plug in your phone, issue the command adb devices just to make sure there is a connection. (can never be too careful now.)
c. If all is good and a serial number is shown, issue the command adb reboot bootloader.
d. You should see a string of words on your phone's bootloader saying "fastboot usb". Issue the command fastboot flash recovery "NAME OF RECOVERYFILEHERE".img. If all goes well. You now have a custom recovery, woop!
BOOT INTO THE RECOVERY AND MAKE A NAND. NOT OPTIONAL.
While in recovery, go ahead and flash the superuser.zip as you would do any other zip.
e. Now open the kernel and extract the boot.img file, place it in the adb/fastboot place.
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand .
HOW-TO Re-enable your fingerprint scanner!
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
a. Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
b. Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
I'll help if I can. Have fun everyone!
Click to expand...
Click to collapse
If this helps anyone out there. I think unplugging device from USB while rumrunner states it is "Waiting for adb" is probably a good idea. Then plug it back in once the device is fully booted and off the security screen.
This was found on a post somewhere on these forums. Guess its worth a try, i will let everyone know the results!
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
luv2ride said:
I was unable to use htcdev.com to unlock the bootloader. I am with Verizon, perhaps thats the issue, not sure. The error I received
Error Code: 160.
Error Reason: MID Not Allowed
Tried using rumrunner and of course that failed due to the fact the bootloader is still locked and there is no unsecure kernel.
Am I missing something?
Click to expand...
Click to collapse
Read second post of this thread
Jiggity Janx said:
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Read second post of this thread
Click to expand...
Click to collapse
I will try that!!!! thanks for the response!!!!
I went back and did some research. Found the correct version of RumRunner & completed the process. I was using the "universal" version.
Jiggity Janx said:
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Read second post of this thread
Click to expand...
Click to collapse
Finished flashing the unsecure kernel and locked the bootloader. Now I'm unable to turn on wifi, I slide the tab and it grays out without turning on. Anyone have an idea on this one?
luv2ride said:
Finished flashing the unsecure kernel and locked the bootloader. Now I'm unable to turn on wifi, I slide the tab and it grays out without turning on. Anyone have an idea on this one?
Click to expand...
Click to collapse
As my second post says rumrunner does EVERYHTING for verizon versions. You have now flashed something non verizon to your phone (kernel) so likely it will have prpblems . You are lucky you are not screwed permanently. However you may have to wait until a dev creates a flashable verizon unsecure kernel. Im not sure what direction to tell you to go...
same issue
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (47/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
when out of developer mode it is not detected by OS which is strange, HTC Sync picks it up when i reinstalled it attempting to get drivers to make it be detected. What is this issue about? simply PC drivers?
---------- Post added at 07:12 PM ---------- Previous post was at 06:49 PM ----------
just tried from linux - same exact error.
any ideas?
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
logikzzz said:
same issue
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (47/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
when out of developer mode it is not detected by OS which is strange, HTC Sync picks it up when i reinstalled it attempting to get drivers to make it be detected. What is this issue about? simply PC drivers?
---------- Post added at 07:12 PM ---------- Previous post was at 06:49 PM ----------
just tried from linux - same exact error.
any ideas?
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Click to expand...
Click to collapse
omg, ive been running wrong one. should be using universal... lol this will work now i bet
---------- Post added at 07:53 PM ---------- Previous post was at 07:18 PM ----------
s-off wow i feel dumb
DeadPhoenix said:
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
Click to expand...
Click to collapse
install 32-bit curl libs and ur all set!
Hey everyone. After 22 logged hours of work on this phone and looking everywhere on XDA and AndroidForums I could really use some help guys. :crying: Since I cannot post links, please bear with my references.
HTC Evo 3D Shooter s-on hboot 1.58.0000 | device:HT17JHX02410 cid:SPCS_001 [sprint] mainver:2.95.651.6
Current status: stock rom successfully reloaded, relocked w/ security warning, stock rom stopped loading after relock. I can access 4ext as well as make commands from adb.
My goal is to flash PACMAN v 23.0.0 rom to my phone. I believe pacman uses Android 4.3. I tried flashing with 4ext, cwm, and twrp. As I recall the problem was an "error 7" across the board. Trying to solve this has lead me down the rabbit hole. I'm not even sure I'm on the right track anymore. I tried deleting the "assert getprop" lines from the beginning of the updater-script file as suggested by several users here, but that lead only to abortions. It may have something to do with 7zip asking whether to overwrite already existing files during extraction? I'm currently trying to return the phone to stock condition so I can downgrade to hboot 1.4 and get s-off, thus allowing me to flash PACMAN. This method was obtained from Unknownforce, Closeone, and RamJet73 all found on XDA.
Returning the phone to stock [in order to brick it via Unknownforce] has been a hassle because every tutorial requires that I lock the phone and then run the RUU update utility. I have tried several versions of this utility and they all drop the connection to my phone after restarting bootloader with an Error 170 [or 171]. There are several reasons for this error and one possible reason is that the software is incompatible. I think this is due to my mainver being 2.95 as opposed to 2.89 or lower. This is why I needed to find a .zip for the stock rom that would work, flash SetMainVersionLow, flash the rom zip, and then lock, bringing me to where I am now, which is a phone that will boot to bootloader and nothing more. This final method with setmainversionlow was obtained from remanifest on AndroidForums.com and I began using it because they mentioned something about 2.95 compatibility or something.
I can still lock/unlock the phone easily and flash any rom i wish, providing it is compatible. Where have I gone wrong? Is the PACMAN rom worth all of this!?
Thanks, all help is greatly appreciated.
-a
Update progress...
i can no longer get a recovery to load [4ext, twrp, cwm] and i think this is because i used a wonky verson of CWM. some have said CWM and htc 3vo don't play nicely together. all i have now is bootloader and adb. no rom loads either, just white screen with green HTC logo until battery dies. recovery programs flash successfully from adb but do not start.
my mainver has been reset to 1.00.000.0 and phone is relocked so i was trying to forget about the recovery and run a RUU. according to RamJet these are the two required items for running RUU. i've tried a 1.13 version as well as a 2.89 version. both of them act the same way as before -- immediately after the phone comes back and the program reads "erase user data" for one second, it fails and give me a 171 error.
please help. i'm a noob but i've looked EVERYWHERE for answers to these problems. if you have links to solutions i would appreciate that as well but i'd put money down that i've been there before.
i will never accept an OTA update again! all i need is hboot 1.4 and i'll be golden! how frustrating
Did you unlock again before trying to flash a recovery?
AFAIK there is no ruu that'll work for your phone until you get s off.
Sent from my Evo 3D CDMA using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------
Short story
You need to get recovery
Then you need to flash a ROM that works on 1.58 or 1.4/1.50 and then you can get s off and downgrade your hboot and flash pac
This is more updated
http://forum.xda-developers.com/showthread.php?t=2539241
Sent from my Evo 3D CDMA using xda app-developers app
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
hanger-on said:
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
Click to expand...
Click to collapse
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
This is what I did, alternatively there's this thread with alternate methods (more designed for windows I think).
Normal disclaimer: This is (to the best of my recent memory) what I did after mucking up my E3D. Follow at your own risk, my memory, your phone, or anything else could be faulty and you could permanently brick your phone trying the following steps.
Assuming you're CMDA and S-ON still:
If you need to fix your hboot/etc download the latest (2.89) PG86IMG.zip
Download the 1.13 PG86IMG.zip
Download SetMainVersionLow.zip (I think you already have that).
Make sure you have adb and fastboot installed and working.
Make sure you're at a stable hboot with a custom recovery.
If not flash the 2.89 RUU (see flashing RUU below).
Reunlock and apply custom recovery if needed.
Run SetMainVersionLOW.zip from a custom recovery.
Before downgrading your hboot you should be (hboot 1.89, custom recovery, "fastboot getvar mainver" = 1.00.0000)
Downgrade your hboot to 1.4.something (Possibly like this)
Flash the 1.13 RUU to get a bootable system
Optionally, Revolutionary to get Revolutionary S-OFF
Optionally (CDMA ONLY), if you got S-OFF you may update the radio (the 1.13 RUU downgraded the radio too). I used the 1.06 version, the 1.09 may work as well but IIRC it was a VM leak so I just stuck with what I think is the latest Sprint image.
From here you should be able to install whatever recovery and ROM (As well as any other partition like radio, hboot, etc) that you like. Good luck.
Flashing RUU
Either use the windows exe (requires windows and a phone that boots correctly), or:
get to your fastboot/bootloader (vol down + power or "adb reboot bootloader")
fastboot oem rebootRUU
fastboot flash zip RUUFile.zip
fastboot reboot (back to bootloader if you want to).
OR
Put the zip on the root directory of the sdcard
Make sure it's named PG86IMG.zip (CaSe sEnSiTiVe)
reboot to a locked/relocked bootloader and apply the zip
Lots of credit to all the devs that made the tools, without whom I'd have been stuck on boring, outdated stock roms.
These steps collected from various xda posts and pieced together for my particular situation, including but not limited to:
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1889438
http://forum.xda-developers.com/showthread.php?t=1193101
http://forum.xda-developers.com/showthread.php?t=2074181
http://forum.xda-developers.com/showthread.php?t=1447839
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1653777
These guides should provide more background on why/how to do certain steps, as long as being better formatted and complete.
Thanks and Thanks
btharper said:
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
Click to expand...
Click to collapse
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
hanger-on said:
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
Click to expand...
Click to collapse
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
310 26345564
btharper said:
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
Click to expand...
Click to collapse
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
hanger-on said:
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
Click to expand...
Click to collapse
What were the last few steps you had done? The only time my hboot didn't come on was when I had my case on slightly off and the buttons didn't hold down correctly (try reseating your case as a last resort and make sure you can feel the buttons being pressed), at one point during the process you have to intentionally brick your phone as noted to corrupt the hboot, as long as you're S-ON it's okay and there are plenty of warnings that you must be S-ON, and one point right after recovering from that step where it's noted that you have to give it some time (I eventually just went to bed for the night because it wasn't working and I wasn't lucid enough to get it anywhere else). So probably just try pulling/replacing the battery and booting up hboot again and hopefully it works. If the red charging light is solid and dimly illuminated when plugged in then the hboot is corrupt and you can proceed to that part of the guide anyway http://forum.xda-developers.com/showthread.php?t=1547695
As well, adb only works when booted to recovery or once the normal system is booted, fastboot only works during hboot or right after rebootRUU (which is actually a part of the hboot, at least on the shooter), and emmc_recovery (used during hboot downgrade)/ultimate recovery tool should work and be able to unbrick the phone. Failing that are you on windows or linux? (revolutionary and some of the hboot downgrade steps require or work best on linux, there's a livedisc (bootable CD/USB stick that won't reset anything on your computer) you can use for the process made by closeone for the hboot downgrade process but you can use for the full process I would think (I did the whole thing on linux since that's my OS of choice) http://forum.xda-developers.com/showthread.php?t=1563342
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
hanger-on said:
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
Click to expand...
Click to collapse
Good luck with it, my advice is lots of nandoid backups and make sure you've got all the tools you need ready. The whole process can be done with linux tools (including the RUU flash). Feel free to let me know if you have any more questions.
Any luck?
Any luck on the new phone?
btharper said:
Any luck on the new phone?
Click to expand...
Click to collapse
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
hanger-on said:
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
Click to expand...
Click to collapse
If you pay all the fees/fines you can keep the phone. If not the esn will be marked as bad and it wont work on sprint.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Oh. Thanks for the heads up.