Hi all. i tryed S-off from my htc desire x. Bootloader unlocked custom rom and kernel. When i try rumrunner FATAL: Download updated package at rumrunner and firewather same not working. Hboot.1.25.0002 Radio 1.15.40.04. I tried to use universal rumrunner not working. I now have seven vibrations. Any idea?
turboflashing said:
Hi all. i tryed S-off from my htc desire x. Bootloader unlocked custom rom and kernel. When i try rumrunner FATAL: Download updated package at rumrunner and firewather same not working. Hboot.1.25.0002 Radio 1.15.40.04. I tried to use universal rumrunner not working. I now have seven vibrations. Any idea?
Click to expand...
Click to collapse
You need to run the device specific latest package from rumrunner.us.
dansou901 said:
You need to run the device specific latest package from rumrunner.us.
Click to expand...
Click to collapse
Where i can download?
Here: http://rumrunner.us/downloads-2/
Just go down the site and pick the HTC Desire X one.
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
HTC Desire X (proto/protou) Windows MANY rumrunner_proto_0.7.1.zip - 21.4 MB
and
Windows 0.5.0 rumrunner_HTC_0.5.0.zip - 20.2 MB
Same error.....
ANY IDEAS?
.1. No Antyvirus and firewall
2. New windows 7 pro 32 updated
3. my rom JB Desire X STOCK ROM 2.20.401.6 Jelly Bean Sense 4+
i'm getting the same error:
Code:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (14/120)
Waiting
Test 2: Booting device
Waiting for ADB (82/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (14/120)
FATAL: Download updated package at www.rumrunner.us
i already s-offed my phone once (and s-on'd it again) some time ago, i followed the instructions on romrunner.us, no idea where this error comes from.
edit: same with deodexed stock rom 2.20.401.6
tried different kernels, too. still no luck.
probably romrunner has disabled servers. I flash new stock boot Jb and
the problem is the same
and when they turn on? and what to do now? need to ask the developer to include the server.
realCyphox said:
i'm getting the same error:
Code:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (14/120)
Waiting
Test 2: Booting device
Waiting for ADB (82/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (14/120)
FATAL: Download updated package at www.rumrunner.us
i already s-offed my phone once (and s-on'd it again) some time ago, i followed the instructions on romrunner.us, no idea where this error comes from.
edit: same with deodexed stock rom 2.20.401.6
tried different kernels, too. still no luck.
Click to expand...
Click to collapse
I have same problem, different roms/kernels etc. Mine gets stuck here.
==================== 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 wo
(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 (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (48/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
I have the same problem, please help
Help?
Anyone? Any sugestions? I need to unlock my desire x...
Disable your AV and firewall, reboot and try run it with administrator permission.
IulianV4 said:
Anyone? Any sugestions? I need to unlock my desire x...
Click to expand...
Click to collapse
I do not use antivirus. closed all running apps, restarted windows, etc, tried everything. maybe is something about the phone? about rumrunner?
It's not rumrunner, it's either something with firewall, network or internet security. What ROM, kernel and hboot are you on ?
nightwalkerkg said:
It's not rumrunner, it's either something with firewall, network or internet security. What ROM, kernel and hboot are you on ?
Click to expand...
Click to collapse
how can you be so sure about that? i already s-offed my phone once (on win7, same system) and now on win8 it doesnt work anymore.
no av, firewall disabled, network configuration the very same as before.
i tried it on different roms and kernel, even on stock rom, always the same error.
tried it on a winxp netbook, too. same.
and as there are more and more people experiencing this "fatal error: download update blabla yada"-error, i very tend to believe that the problems is on rumrunners side somehow.
realCyphox said:
how can you be so sure about that? i already s-offed my phone once (on win7, same system) and now on win8 it doesnt work anymore.
no av, firewall disabled, network configuration the very same as before.
i tried it on different roms and kernel, even on stock rom, always the same error.
tried it on a winxp netbook, too. same.
and as there are more and more people experiencing this "fatal error: download update blabla yada"-error, i very tend to believe that the problems is on rumrunners side somehow.
Click to expand...
Click to collapse
Because the other devices had a same problem and got fixed by av/firewall disable. I recommend you to download Ubuntu, make a live cd and try with it.
Does ADB USB drivers work Windows 8? I though it didn't worked
Do as nightwalker said, and if you're not on stock Rom and kernel, go back to it.
albru123 said:
Does ADB USB drivers work Windows 8? I though it didn't worked
Do as nightwalker said, and if you're not on stock Rom and kernel, go back to it.
Click to expand...
Click to collapse
tried different roms, different kernels. went back to stock rom odexed, deodexed, all have the same result, same ****ing error...
albru123 said:
Does ADB USB drivers work Windows 8? I though it didn't worked
Click to expand...
Click to collapse
well, you are wrong!!
albru123 said:
Do as nightwalker said, and if you're not on stock Rom and kernel, go back to it.
Click to expand...
Click to collapse
tried with ubuntu 32bit, guess what happened?
maybe i should change my isp or move to a different country or planet to get rumrunner working again
or maybe some people should finally consider the possibility that some server-sided response from rummrunner doesnt work.
realCyphox said:
well, you are wrong!!
tried with ubuntu 32bit, guess what happened?
maybe i should change my isp or move to a different country or planet to get rumrunner working again
or maybe some people should finally consider the possibility that some server-sided response from rummrunner doesnt work.
Click to expand...
Click to collapse
Yeah,i heard Venus has a nice 1Gbps plan,and it's cheap. ( HA! In your face Google! )
If that is the case then you do this :
1. Go to webchat.freenode.net. ( Or you can use your own IRC client)
2. Join the #rumrunners channel.
3. Tell Beaups that he is d*** for not fixing it. ( He is not really a D, he is a great guy. xP )
4. Profit! ( Or get a ban from the channel. )
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.
[S-OFF] after the 2014-OTA ... the incredible _has_ been achieved & is fully working
You might not believe me pals, BUT the incredible and unbelievable HAS BEEN achieved!!!
Full radio [S-OFF] ... on a previously [S-ON & LOCKED]
Droid Incredible 4G LTE - with 2014-OTA (ver. 2.19.605.2)
Credits and terms:
This is NOT my own exploit ... but rather accomplished with the guidance from team "FacePalm" (namely: beaups & dr_drache) ... Full testing and 1st run by myself only ... actual [S-OFF] used the "rumrunner universal" exploit ... but needs a prior TEMP-ROOT (i used the " Inc4GUnlockV61-Windows.zip" kit by mdmower available in our Dinc4G-dev section, link added below) .
As usual: While this process shouldn’t be too risky, bricks can happen. None of me or the actual coders will be accountable. => If you are worried, don’t do it. <=
Again a rather simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, it's not my own work ... i just pass the details along, but still DO NOT ... steal, repackage, 1-click, or whatever method described herein ... for the rest: all disclaimers from "rumrunner.us" do apply!!!
TEMP-ROOT (at least) ... is needed, without it the exploit will NOT work!!! (at least no need for supercid :cyclops ... apart from that, both parts (temp-root & actual s-off exploit) work on Linux _and_ Windows *cough*
1) Once you have confirmed you have "Temp-Root" on your 2.19.605.2 fireball:
http://forum.xda-developers.com/showthread.php?t=2214653 ... for the temp-root script (by mdmower)
2) Download the HTC Universal RUMRUNNER (0.5.0) and unzip it in your working directory:
http://rumrunner.us/downloads-2/
3) follow the RUMRUNNER instructions _closely_ as listed at:
http://rumrunner.us/instructions/
4) wait for a ... longer time until ... rumrunner finishes with: "rumrunner done! hope you enjoyed the rum!"
you are now proper: radio [S-OFF] on your 2.19.605.2 fireball
OPTIONAL:
5) flash ENG-hboot 1.15.1111 ... obtainable from DirtyRacun webpage:
http://unlimited.io/fireball.htm
6) flash custom recovery (e.g. TWRP 2.6.3.0h ... the updated KK4.4 capable version from MDMOWER)
http://mdmower.cmphys.com/category/fireball/
(note that the recent 2.6.3.0k-m (currently?) cannot backup/restore "android-secure" anymore, but 2.6.3.0h is also KK4.4-ready & still can do it) ... ... link to TWRP2.6.3.0h in 2nd post
mdmower fixed this issue in TWRP2.6.3.0.n from 2014-03-03
7) reboot ... ENJOY & REJOICE
8) hit the THANKS-button below
:laugh::laugh::laugh: if it helped you (to achieve the unachievable :laugh::laugh::laugh
thanks for reading ........... (thx again to dr_drache & beaups tips and guidance, temp-root script by mdmower & s-off exploit by rumrunner, 1st testing of this combination "me, myself & i" => SUCCESSFUL)
...
6b) linked the "mdmower: TWRP2.6.3.0h" _only_ for convenience as it is currently NOT available from mdmowers site: (_last_ version able to backup the _AndSec-partition_ as well / already KK4.4-capable)
link remoded as this issue was FIXED by mdmower in his recent TWRP2.6.3.0n build from 2014-03-03
spacer ... just in case ^^
Gonna try it this weekend! Thanks!!!!!
I'm going to give it a try tonight. Thanks!!!!!!!!!!
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
kimba99 said:
8) hit the THANKS-button below :laugh::laugh::laugh: if it helped you (to achieve the unachievable) :laugh::laugh::laugh
Click to expand...
Click to collapse
Already s-off, but this is fantastic news for those who are not (yet). Thanks!
Sent from my Fireball using Xparent Blue Tapatalk MegaSuperb Pro
I haven't be able to find Dinc4G_UnlockV61-Windows.zip Any chance someone can point me there?
I think you meant http://forum.xda-developers.com/showthread.php?t=2214653
I just got done with it. I had to run it a couple times. It failed the first time around. But the phone is now s-off
Thanks,
Here you go.
http://forum.xda-developers.com/showthread.php?p=39763697
Sent from my ADR6410LVW using xda app-developers app
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
kimba99 said:
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
Click to expand...
Click to collapse
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
Yes.....that is mdmower's unlock script.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
yeah, right ... seems like i renamed the script after download (quite some while ago), corrected the name in the start-post & ... added a remark about TWRP-2.6.3.0h
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
puhleez said:
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
tj13 said:
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
Click to expand...
Click to collapse
So based on what everybody is saying I actually had temp root since I had the status bar with no lock ring. I guess the issue was with rumrunner then.
I also tried to get an unlock from htcdev but encountered an error 160 invalid MID I think.
Device appears under adb devices.
Thanks for the reply.
Sent from my TouchPad using Tapatalk
USB debug is enabled?
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
Ran temproot, the phone booted to statusbar, no unlock-ring.
Tested sudo ./adb shell and had #: access, able to cd into /data/data etc and list files.
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Thanks
stevey500 said:
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Click to expand...
Click to collapse
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux (most successful ppl here did it on Win, albeit Win8.x _might_ be problematic as well):
Code:
1) 32-bit Linux (Ubuntu is preferred)
•Live CD’s are fine.
•Live USB is fine.
•Native install is fine.
•VM’s are unsupported.
•64-bit Linux may work with 32 bit libraries, but is unsupported.
2) A _working internet_ connection (on your linux system!)
3) USB _debugging enabled_ on your device (in developers options)
4) Fastboot _disabled_ on your device (settings -> battery -> UNcheck “fast boot”)
otherwise ... try on a Win7 machine, only HTC drivers _installed_ (NO HTC-Sync installed, but completely removed/deinstalled!!), NO other phone software installed (Kies, PDAnet etc) ... firewalls / internet security _disabled_, otherwise network filtering could get you stuck ... same restrictions 2), 3) & 4) from linux-rumrunner also apply!
maybe it's your linux firewall that intercepts the needed bits???
good luck
kimba99 said:
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux
maybe it's your linux firewall that intercepts the needed bits???
good luck
Click to expand...
Click to collapse
Thanks for the response!
I ran it in 32 bit ubuntu Linux, all files on my home directory. No firewall, direct connection to ISP. I followed their guide exactly except putting the phone into temp-root before I started.
The rumrunner binary in linux appears to find the phone, reboot to bootloader, finds bootloader, reboots to find ADB... at this point is when I realize rumrunner has removed temp-root as I can see home-screen icons and unlock ring, and later on waiting a few minutes further, rumrunner says no SU and cannot continue.
I will try to run rumrunner binary in windows 7 with only HTC drivers installed, open firewall, boot back up into temp-root and see what it does. :good:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
kimba99 said:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
Click to expand...
Click to collapse
Cool, maybe that is the case then. I'll try windows temp-root & windows rumrunner with HTC drivers as soon as I have a moment to try. Hope it works! This phone is a sluggish borderline unbearable crapper with HTC's stock firmware. I know it's got to be ten folds more tolerable with CM11's latest release for it.
I really appreciate the responses.
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
nzgx beast said:
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
Click to expand...
Click to collapse
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
therreid said:
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
Click to expand...
Click to collapse
Also verify the build version that is currently on your phone. I would assume you have the latest OTA (2.19), if so, then therreid is spot on. If you're earlier, then you have a few additional options, but it might be easiest for you to install the OTA and follow those instructions.
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Still dont understand.-.
I've read them but like my drivers apparently aren't installed, my phone isn't recognized on my computer, and this is all confusing lol. Do any of you know where to find like a video to help me
Here are the drivers:
http://forum.xda-developers.com/showthread.php?t=2089508
Okay...
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
okay so what exactly is s-off? and what do drivers do and how do i know which to get? and how to temp root?
kimba99 said:
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Click to expand...
Click to collapse
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
kimba99 said:
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
Click to expand...
Click to collapse
OK, thought that if reboot took place, temp-root was lost. So, when I ran rumrunner, it would just timeout and fail. I'll try to get the exact details later.
Anyway, thanks for your reply. May try again today using Windows to see if it works any differently.
EDIT: here's what happened under Windows.
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (12/120)
Waiting
Test 2: Booting device
Waiting for ADB (20/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (29/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
just saw above, that you guys referenced the __hasoon2000's all-in-one toolkit__ ... as for root (well, better said: [s-off]) in the "[s-off] after 2014-ota" thread, i wrote to use mdmovers script-kit! ... the hasoon2000 kit might be outdated (in terms of temp-root) ... i didn't check the details, but for clarity, please do AS IT'S WRITTEN down ... do not deviate from the (fairly easy) route given in that thread!
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
I was finally able to get the method oiutlined by kimba99 to work using Linux, but you are correct, the initial adb & fastboot connection tests cause the phone to lose the temp-root and go back to my normal lock screen with ring and icons(in a usable state).
I know i sound conflicted but i tested it several times.
Here is the weirdness.
What finally got it to work was "attempting" using my win8 system. The win8 failed due to windows losing the device. I used drivers from HTC and then used drivers from the link provided. While rumrunner ran I would get a pop-up saying an unrecognized device was plugged in and then rumrunner would timeout being it could no longer talk to the phone. After 3 failed attempts on windows it got late so I rebooted my laptop into Ubuntu so i could use rumrunner to remove the temp-root and make it usable again as it had done 5 previous times.
Suddenly rumrunner was able to go past the root checks. The only difference than before is that while trying on windows my device went from LOCKED to TAMPERED to TAMPERED LOCKED.
Anyways, everything worked as after that just as advertised.
]
Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
stifer said:
Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
Click to expand...
Click to collapse
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
RLGL said:
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
Click to expand...
Click to collapse
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
stifer said:
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
Click to expand...
Click to collapse
tried firewater?
RLGL said:
tried firewater?
Click to expand...
Click to collapse
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
stifer said:
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
Click to expand...
Click to collapse
it took 30 seconds to find the following using the search function:
Default [Guide] Firewater S-Off
Disclaimer
License: Firewater S-Off is the result of many hours of hard work by beaups and fuses. The firewater binaries you download may not be shared, rehosted, bat’d, integrated into a one-click, repackaged, hotlinked, or otherwise distributed or reused. The source code and methods in firewater are closed and private.
Temproot is a hack-up build of android_run_root_shell which appears to be a work of hikezoe and fi01. Original source can be downloaded HERE, our modified mess will be made available on this website soon.
This software is provided free of charge for personal non-commercial use. For commercial use or redistribution a WRITTEN agreement with the authors is required.
Support: support for firewater s-off is available at #firewater on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Official website: http://firewater-soff.com/
Welcome to Firewater
What firewater can do for you:
S-Off your HTC device
Unlock yout bootloader
There are two methods which can be used to achieve S-Off:
Method n.1: to be used with and HTCDev unlocked/rooted device;
Method n.2: temp-root method, to be used if you don't want to unlock your device through HTCDev (it may not work with all devices);
Prerequisites
Working adb on your PC (Windows, Linux, OSX, etc. are all supported);
HTC drivers installed and working
HTC sync removed (not closed - REMOVED)
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
A working internet connection on your device (Wifi, 3G, 4G, etc. are all supported). There is no way around this requirement, don’t ask;
USB debugging enabled on your device;
Your device must be HTCDEV unlocked/rooted or have a working temproot. A temproot that works with many modern (not all) HTC devices is provided below;
Do not attempt to run firewater from a terminal emulator on your device. You MUST use adb along with a PC;
A supported device. Firewater *should* work with most modern QUALCOMM based HTC devices, including (but not limited to) the HTC One, HTC Droid DNA, HTC One S, HTC One Max and many others.
Instructions: method n.1 (normal, rooted device method)
Once you confirm you meet the above pre-requisites, it’s time to get started.
Ensure device is booted to android with usb debugging enabled
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download Firewater Search the download from the official site;
Push, prepare and execute Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Instructions: method n.2 (temp-root method)
This method may allow firewater to work on a fully stock/HTCDev locked device. This method is being provided as a convenience. Do NOT seek support if this temproot does not work for you.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download firewater Search the download from the official site;
Download temproot Search the download from the official site;
Push, prepare and execute temproot and Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Donate
Donate to Firewater developers
Donate to me (if you appreciate the guide; thank you!)
Thanks for that. I did try that, and now it says '' Tampered'' and ''Relocked'' and ''S-ON''. I don't understand why this is happening.
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Icyman said:
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Click to expand...
Click to collapse
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
stifer said:
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
Click to expand...
Click to collapse
Did you use the unlock bin from HTC?
Icyman said:
Did you use the unlock bin from HTC?
Click to expand...
Click to collapse
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
stifer said:
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
Click to expand...
Click to collapse
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Icyman said:
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Click to expand...
Click to collapse
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
stifer said:
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
Click to expand...
Click to collapse
I never used weaksauce on DNA. Maybe that's the problem.
Icyman said:
I never used weaksauce on DNA. Maybe that's the problem.
Click to expand...
Click to collapse
That's the only way I can apply temproot and then firewater, I can't find the original temproot file anywhere and I thought that weaksauce is the updated version of the temproot file. If you could send me the temproot file somehow that would be great,-just to see if it could work...
Any further advice guys? Please?!!! I've got this phone but the outdated software makes it useless.
==================== 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