Related
check last page for latest situation status.
a bad download, maybe? you try redownloading the files?
Right-click on the file you downloaded and extract it to your desktop or somewhere else you can find it. Then go to the file you extracted, right-click on it and select to run as administrator. Also make sure you're connected to a USB 2.0 port.
Sent from my EVO using XDA Premium 4 mobile app
Yeah, I tried a new download, and still the same outcome.
That didn't work. Some results.
Would it matter that the linux folder has an extra file the Windows file doesnt. (Moonshiner.sh)
redm1st said:
Would it matter that the linux folder has an extra file the Windows file doesnt. (Moonshiner.sh)
Click to expand...
Click to collapse
Are you running it on Linux or Windows?
Did you download the correct format?
I'm running the windows version. And yes its the right version. I dropped the sh. File Into my windows moonshine folder and I got all the way to test 3. But hit a battery to low error. So I'm a charge it and try again. Maybe it may work. Not sure yet.
redm1st said:
I'm running the windows version. And yes its the right version. I dropped the sh. File Into my windows moonshine folder and I got all the way to test 3. But hit a battery to low error. So I'm a charge it and try again. Maybe it may work. Not sure yet.
Click to expand...
Click to collapse
Good luck
Pm if you have any questions
Thanks. Will do. :thumbup:
bigdaddy619 said:
Good luck
Pm if you have any questions
Click to expand...
Click to collapse
Got this far, then it just stopped.
redm1st said:
Got this far, then it just stopped.
Click to expand...
Click to collapse
I think folks are fixing that by rebooting manually.
bigdaddy619 said:
I think folks are fixing that by rebooting manually.
Click to expand...
Click to collapse
Yeah, just rebooted to bootloader. And it says s-off moonshine. So I guess its done..
Thanks for your assistance. :thumbup:
redm1st said:
Yeah, just rebooted to bootloader. And it says s-off moonshine. So I guess its done..
Thanks for your assistance. :thumbup:
Click to expand...
Click to collapse
NP if you see the hands free activation start when you reboot let it do it's thing
A side effect of S-OFF is you can't make or receive calls or texts
bigdaddy619 said:
NP if you see the hands free activation start when you reboot let it do it's thing
A side effect of S-OFF is you can't make or receive calls or texts
Click to expand...
Click to collapse
Yeah it did that during moonshining 2 phase.
CANT s-off for 3.17.651.4
==================== Moonshine S-OFF 0.2.1 (shine) ===========================
Moonshine 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 Moonshine 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 moonshine] ----
(2) Realize that moonshine 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 moonshine S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Reading model id....[PJ7510000]
Test 2: Booting device
Waiting for ADB (41/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
......................
(Dots go on forever)
redm1st said:
==================== Moonshine S-OFF 0.2.1 (shine) ===========================
Moonshine 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 Moonshine 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 moonshine] ----
(2) Realize that moonshine 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 moonshine S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Reading model id....[PJ7510000]
Test 2: Booting device
Waiting for ADB (41/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
......................
(Dots go on forever)
Click to expand...
Click to collapse
Use the newest Universal version 0.5.0 and read the instructions it will tell you why you are getting endless .................
BD619 said:
Use the newest Universal version 0.5.0 and read the instructions it will tell you why you are getting endless .................
Click to expand...
Click to collapse
Tried rumrunner 5.0 and got this. (downloaded a fresh download, and still a no go)
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (52/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Use a stock rooted rom like Captian_Throwbacks rom
Make sure your Superuser/SuperSU binaries are up to date
Keep the screen awake it may ask you to grant superuser rights
Make sure all your security programs are disabled or deleted and your firewall is turned off
BD619 said:
Use a stock rooted rom like Captian_Throwbacks rom
Make sure your Superuser/SuperSU binaries are up to date
Keep the screen awake it may ask you to grant superuser rights
Make sure all your security programs are disabled or deleted and your firewall is turned off
Click to expand...
Click to collapse
Phone's being stubborn, that's still a no go.
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!
I have a HTC one 32GB and it's currently s-on with tampered showing and unlocked showing . My hboot is 1.56.0000. Need to return to stock since att sending me overnight a replacement...i have stupid purple camera really bad.
Sent from my KFSOWI using Tapatalk
This should be the right one, double check your version. http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
EDIT: have you ever flashed an ruu before?
Sent from my HTC One using XDA Premium 4 mobile app
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
bigfdaddy2 said:
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
i got adb to work i had 2 change roms... how do i go about relocking myphone so i can run the ruu
Got my phone relocked know gonna run the ruu
Sent from my KFSOWI using Tapatalk
If you take the phone back to an ATT store for an exchange or to have them fix it, you don't have to return it to stock. they don't check and they don't care. The only time you need to return it to stock is if you are having to send it back to HTC. If at all possible deal with ATT as they will most of the time just hand you a new one while HTC will give you a refurb. You won't get your original back from HTC.
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
bigfdaddy2 said:
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
Click to expand...
Click to collapse
As it is showing your device ID in fastboot mode, your phone is properly connected in fastboot mode. Does the screen say FASTBOOT USB? If yes, you can run RUU.exe file.
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Stock kernel blocks this...
bigfdaddy2 said:
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Which kernal do I need then I tried with bullet I believe the name was
Sent from my KFSOWI using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
He could but these prop settings mess things up
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.metropcs.ui=0
GalaxyUser50 said:
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I've gotten to accept root through adb and am trying to use Firewater to s-off my new one and it just fails every time .... Can't seem to find a how to or step by step on it like the older hboots have ...I got 1.56 of course lol ...
Sent from my HTC One using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
bigfdaddy2 said:
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
Click to expand...
Click to collapse
Wonders_Never_Cease said:
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
Click to expand...
Click to collapse
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
bigfdaddy2 said:
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
Click to expand...
Click to collapse
sync is gone adb works ,fastboot works,latest drivers....
C:\Users\ace\Desktop\htc 1 toolkit>adb reboot
C:\Users\ace\Desktop\htc 1 toolkit>adb wait-for-device push firewater /data/loca
l/tmp
protocol failure
C:\Users\ace\Desktop\htc 1 toolkit>adb push firewater /data/local/tmp
2532 KB/s (4519496 bytes in 1.743s)
C:\Users\ace\Desktop\htc 1 toolkit>adb shell
[email protected]:/ # su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.5.15 ===========================
firewater 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 firewater 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.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]:/ #
C:\Users\ace\Desktop\htc 1 toolkit>
==================== rumrunner S-OFF 0.7.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 (50/120)
Waiting
Test 2: Booting device
Waiting for ADB (25/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (5/120)
Waiting for ADB (24/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Please Help Me What Does Mean
My HTC DESIRE X DETAILS
ANDROID VERSION-4.04
ROM 1.18.401.1.zip its not rooted but i flashed latest Supersu and its now rooted
kernel [email protected]#SMP PREEMPT
BASEDVERSION-10.18.40.05U_.09.45.201
BUILDNUMBER-1.18.401.1CL28557 RELEASE- KEYS
Rmyaseen said:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
Click to expand...
Click to collapse
As it said ... flash an insecure kernel. The stock kernel/boot.img won't work.
As your ROM is an ICS, make sure to flash only ICS boot.img
ckpv5 said:
As it said ... flash an insecure kernel. The stock kernel/boot.img won't work.
As your ROM is an ICS, make sure to flash only ICS boot.img
Click to expand...
Click to collapse
ok bro
thnx a lot i did it plz tel me any stable jb rom for our desire x plz
Hi
Rumrunner works with my Desire X
I haved hboot 1.25.02
Andorid 4.1
Custom ROM 1.10.401.4 or 2.20.401.4 (I´m not sure)
I don´t know what´s can happen with lower hboot version or Adroid, you could brick your phone.
For sure your Desire x must be rooted and custom ROM.
Rmyaseen said:
thnx a lot i did it plz tel me any stable jb rom for our desire x plz
Click to expand...
Click to collapse
If you mean really stable, try any of the Sense ROMs, there are all pretty stable (the Sense 4 ones are most stable). If you want to have CM, you can try that as well, but it isn't stable yet and currently being worked on, so I would wait for that (you can always try one of the custom ROMs based on CM (PA, AOKP or MIUI) of you want, but do it on your own risk...)
When you start rumrunner should allow rights superSU, when I dismissed them automatically so ask them to always ... Sorry for my bad english :/
Sent from my Desire X using XDA Free mobile app
I tried to do Firewater, cant because I tried to do adb reboot, gave me a error. Looked up adb devices, says there is no devices. USB debugging is ON. I updated my drivers, nothing. Am I missing something? I even adb kill-server and adb start-server, made no difference.
I wouldnt mind purchasing SunShine, but would like to see if I can get this to work. SunShine says it will work, but I have to pay $25, so obviuosly, if I can get the free version of firewater to work, that would be great.
**Edit** now it gets stuck when I try pushing the file.
**Edit** I just moved the file over to the directory manually, used SU to chomd the file for 755 in a terminal emulator, bypassing the need for abd, then ran the file in a emulator. Firewater will not work for my device. It did run normally however, it just says the "welp, this sucks, firewater will not work for your device". Time for SunShine when I get the money since its pre-install scan said its compatable.
Do you have fastboot disabled as well?
Did you get it to work or not?
jball said:
Did you get it to work or not?
Click to expand...
Click to collapse
No, I need SunShine sadly. I will get it when I have the time, right now I gotta goto work, been trying to get FireWater to work for 2 hours now.
Wonders_Never_Cease said:
Do you have fastboot disabled as well?
Click to expand...
Click to collapse
In the battery manager? Yeah, I turned that off. I can see my device momentairily, then when I go to push a file over to my device, it just freezes. I left it to see if it took awhile, gave up after 5 minutes (shouldnt take that long for a 5MB file...) and then did adb devices to find out that it dissapeared from the list while trying to trasnfer.
I am the biggest idiot ever, I thought adb had to be run in fastboot usb for some reason. DERP...
I lost a lot of sleep trying firewater man so I straight up recommend as if you don't already know to just bit down and feel great after using Sunshine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------
LightningKitsune said:
I am the biggest idiot ever, I thought adb had to be run in fastboot usb for some reason. DERP...
Click to expand...
Click to collapse
It's all good.you figured it out
jball said:
I lost a lot of sleep trying firewater man so I straight up recommend as if you don't already know to just bit down and feel great after using Sunshine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------
It's all good.you figured it out
Click to expand...
Click to collapse
Yeah, but to no avail, same output as before. Ill buy SunShine when I get back from work:
==================== firewater S-OFF 8.0.11.09 ===========================
firewater 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 firewater 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.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
Yes for days and multiple
ROM/kernel combos and that's all I got.it states clearly man over and over .I forget after all why you want S-off for(was it to convert to GPE?)
LightningKitsune said:
I am the biggest idiot ever, I thought adb had to be run in fastboot usb for some reason. DERP...
Click to expand...
Click to collapse
adb should work whether you are in fastboot mode or not. adb should work in any condition, as long as the phone is powered on (in OS, bootloader, recovery, fastboot).
jball said:
Yes for days and multiple
ROM/kernel combos and that's all I got.it states clearly man over and over .I forget after all why you want S-off for(was it to convert to GPE?)
Click to expand...
Click to collapse
SkyDragon rom. Says you can do it s-on, but I assume it's only for GPE M8's (or at least att converted over to GPE) because 4.4.4 is a must. I'm on 4.4.2, so I have to use the S-off method unless there is a 4.4.4 RUU for att devices.
Well there's a RUU for GPE 4.4.4...it's 2.12.1700.1 hosted on graffixnyc.com....it's best to s-off, if you have 25 bucks just use sunshine.
LightningKitsune said:
SkyDragon rom. Says you can do it s-on, but I assume it's only for GPE M8's (or at least att converted over to GPE) because 4.4.4 is a must. I'm on 4.4.2, so I have to use the S-off method unless there is a 4.4.4 RUU for att devices.
Click to expand...
Click to collapse
I did the full GPE conversion just the other day and it involved the 4.4.3 ruu so I could accept the official OTA ,
Took the OTA on my (at&t) HTC ONE M8
Keep in mind I followed to the letter all steps including changing "cid" and "mid"
---------- Post added at 03:25 AM ---------- Previous post was at 03:07 AM ----------
I'm on 4.4.2, so I have to use the S-off method unless there is a 4.4.4 RUU for att devices.[/QUOTE]
Choose the 4.4.4 file but it's still a must to have S-off cause you want to have matching "cid" "mid"
http://www.graffixnyc.com/m8.php