So just trying to prepare myself for when I get my phone back from repair that HTC puts 4.3 on there instead of 4.1.2 since Att release is out now.
My understanding 4.3 comes with hboot 1.55 what are my chances of achieving s off with the rum runner if this happens or any other ways
I know if it gets sent back as 4.1.2 a d hboot 1.44 I'm good.
Just curious as to what I'm in for if they do put 4.3 on there
Sent from my HTC One X+ using XDA Premium HD app
I'd like to also find out some information regarding this topic. I had my device swapped because I couldn't take the purple camera any longer.. and the replacement had 4.1.2 installed, but when I booted it and during setup, I let the 4.3 OTA come through and installed the update (not even thinking about the hboot version).. So I now am stock 4.3 w/ hboot 1.55 - I'm assuming at the moment that I cannot really do much until we get 1.55 hboot correct? For the fun of it, I tried running the AT&T 1.26.512 RUU but it failed
OP: not hijacking your thread, just didn't want to create a new thread with the same topic..
No sounds like you have the exact problem I could have
In warranty disclaimer it says phone will be loaded with most recent os released for your carrier.
Now that 4.3 is out I'm afraid HTC will just load that on their
Sucks I had a off before camera problem
Sent from my Nexus 7 using XDA Premium HD app
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Fberry said:
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Click to expand...
Click to collapse
You can use moonshine or revone (which I used) with HBOOT 1.44, however with HBOOT 1.54 you need to use rumrunner but it is not the same unlock as with revone because with rumrunner you actually need to unlock the bootloader via HTCDEV.
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
ac3kill said:
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
Click to expand...
Click to collapse
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
EsJayEs said:
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
Click to expand...
Click to collapse
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
noobsquared said:
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
Click to expand...
Click to collapse
I tried it anyway. Here's the result:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
No matter how many times I've tried it. I followed the directions exactly as stated. The only thing that changed is now I have the "tampered" flag in the bootloader.
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
EsJayEs said:
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
Click to expand...
Click to collapse
there is something new with 4.3, they kinda block the adb. when i was on 4.1.2 the adb "fastboot" command working just fine, but once i ran the ruu and update my htc one to 4.3, now when i type adb devices it show me my device but OFFLINE. so it might be a new hidden menu to activate the adb port again "make it read the device" or maybe we need a new driver "which i doubt"....
Well I saw they have the Att firmware on rum runner site 3.17. Whatever the rest is so we should be fine at getting soff I just have not seen someone say they have since Att stock is is hboot 1.55 but ill figure it out when my pphone get back
Hoping its 1.44 hboot and I can downgrade and unlock bootloader without HTC knowing this time but that would be to easy and I'm sure ill have stock 4.3 1.55 we shall see this week !
Sent from my HTC One X+ using XDA Premium HD app
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
noobsquared said:
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
Click to expand...
Click to collapse
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
EsJayEs said:
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
Click to expand...
Click to collapse
I'm having the same thing.
One time it says offline, the other it says connected.
I've ran rumrunner_m7_3.23.666.1 almost 5 times now with the same result. The only difference is that my HBOOT screen says tempered but I still have S-On and I don't think it's getting anywhere. It does the pouring and restarts the phone quite a few times but I'm guessing it's not having any luck. Maybe rumrunner only supports up to HBOOT 1.54 and since we are HBOOT 1.55, it won't work?
Here is how the process has went the 6th time I believe when I ran it:
==================== rumrunner S-OFF 0.0.3 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
pouring (1).............................
pouring (2)...............................
pouring (3)...............................
pouring (4)...............................
pouring (5)................................
pouring (6)...............................
pouring (7)...............................
pouring (8)...............................
Wait 30 seconds, power on device, run rumrunner again.
Press ENTER to exit
---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------
And here is what my adb says after running that process 6 times:
W:\Downloads\Android\HTCOne\htcone>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT********** device
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
I may have figured it out.
I had version 3.17.502.3 on AT&T HTC One and I've been running rumrunner for .666 version.
I just downloaded rumrunner_m7_3.17.502.3 and about to give it a shot. Will keep everyone posted. Sorry if I annoyed anyone with my dumb post and mistake :silly:
I never got to the pouring part, but I was also apprehensive about using Rumrunner for a different version. I can't remember where I read it on here, but one of the 2.24 users that did it bricked his phone. Or rather it bricked itself during it's first phone call after s-off. No confirmation if it was due to using a different rumrunner than what he had, but I wouldn't want to be the first guy to try. For that, I thank you.
Interesting how the version you used doesn't have all of those test waiting for fastboot and adb.
Thanks for the kind words and motivation EsJayEs
I'll keep everyone posted. Someone has to be the bait or nobody gets the goodies :good:
So, when I ran the right version, it says:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (26/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
I'm guessing because I tried wrong version and now my HBOOT says tempered. Maybe I'll relock bootloader and try to run RUU to go back to stock and start over. Aah, I wish I would have never gone to G2 and stayed with my HTC One that I had working and perfectly setup!
I re-locked the bootloader, installed the latest AT&T RUU, unlocked the bootloader, then ran rumrunner_m7_3.17.501.3 which matches my system version and OS version in HBOOT menu but it seems like it's still not working.
Here is the output after running rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Still don't have my phone sounds like it could be because hboot 1.55
But I don't get why our Att firmware is on rumrunner site if hboot 1.55 don't work because the 3.17 firmware ones with hboot 1.55 and they make it very clear to be stock.
Man I need my phone back I'm ready to start trying
Sent from my HTC One X+ using XDA Premium HD app
That's the exact problem I had time and time again.
Double check you have the right rumrunner for your firmware. Im sure you have.
Don't worry about doing the fastboot bit, you know its all connecting fine.
Boot your phone as normal, on to the phones home screen. Open a command prompt in the same folder as yout ADB link.
Type ADB Devices, and it should find your phone, model number and so on. Leave the window open. Then start rumrunner. It worked for me 1st time then.
Steve
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
As above
Steve
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------
That was not me just copied it from another forum. If I had a pc I would try. Hope it works for you guys.
Sent from my HTC One using XDA Premium 4 mobile app
Related
TL;DR: my phone got stuck in roaming mode, I flashed this without completely thinking it through, now I'm S-on, locked bootloader, and stuck in fastboot.
Is there's any hope in getting at least back to stock?
Did you try the ruu?
Sent from my HTC6435LVW using xda app-developers app
danielhall2689 said:
Did you try the ruu?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The RUU wouldn't work since I was on 2.06 and iirc you can't downgrade with a locked bootloader and/or s-off.
I did manage to fix it (at least I think I did, it's still booting) though. To anyone who made the same stupid mistake I did:
All I did was I took the original zip I flashed (linked in the OP), opened it up and replaced the recovery.img with the latest TWRP. Somehow that managed to flash fine, and from there I just flashed a deodexed stock rom from recovery. I have no idea how this worked but I'm just happy I don't have a ~$350 paperweight.
PROTIP: don't flash at 2 in the morning, kids
Hi everyone!
I have HTC DROID DNA with 1.15.605.4 firmaware. I have carefully read the instructions.
1) Flashed the original zip file download2.06firmware.zip.
2) Make factory reset from fastboot
3) Then turned off fast boot, turned on USB debugging.
4) Start distiller.exe.
All was well until step Moonshine (4). Stopped and stood for a long time on the message "waiting for device". Lasted more than an hour. I noticed that in the process depends on the process manager "adb install dnashellroot.apk". I unplugged the phone. Turned it off completely, turned on and connected to the cable again. The process continued. But in the end issued a message "don't drink and shine". Everything since then, when I did the factory reset - could not turn on WiFi. Moonshine still does not work.
Any idea how can I return the phone to life and make the S-OFF? It now S-ON, TAMPERED, RELOCKED.
Now CID is VZW__001
OP, you should probably link to what you down loaded, not to the actual download. I didn't really need to down load the 2.06 firmware again.
Glad you got it working.
From my S-Off BadSeed DNA
serve nuildrs
The problem is that I wanted to get S-OFF with Moonshine. Now I have a firmware 1.15.605.4, and the boot, hboot_signedbyaa, radio, recovery from the 2.06 version (from official OTA update, from Moonshine thread). However, now I S-ON, RELOCKED (TAMPERED).
I understand that I have no other way except how to use RIFF JTAG?
http://forum.xda-developers.com/showthread.php?p=34329980
try using this or at least the files it comes with. It should have all you need to go to the stock everything
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------
Alexey said:
The problem is that I wanted to get S-OFF with Moonshine. Now I have a firmware 1.15.605.4, and the boot, hboot_signedbyaa, radio, recovery from the 2.06 version (from official OTA update, from Moonshine thread). However, now I S-ON, RELOCKED (TAMPERED).
I understand that I have no other way except how to use RIFF JTAG?
Click to expand...
Click to collapse
Also you can still moonshine
Sent from my HTC6435LVW using xda app-developers app
Unfortunately nothing works. Moonshine does not work.
Result -->
==================== Moonshine S-OFF 0.2 (dlx) ===========================
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 !!
Checking for updates......
Please wait....
..........
Test 1: Rebooting into bootloader
Waiting for fastboot (8/60)
Waiting
Test 2: Booting device
Waiting for ADB (33/60)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/60)
Waiting for ADB (32/60)
Waiting for device
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (1)................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (2)................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (3)................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (4).........................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (5).................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (6).................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (7).........................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (8)................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (9).........................................
Waiting for device
Launching temproot
Sleeping 10 sec
Moonshining (10).........................................
Waiting for device
Launching temproot
Sleeping 10 sec
ERROR: Don't drink and shine!!
Press ENTER to exit
Now i have cid 11111111. Made using JTAG. There are ideas on how to get my phone back to life?
Anybody have other ideas?
shobon said:
The RUU wouldn't work since I was on 2.06 and iirc you can't downgrade with a locked bootloader and/or s-off.
I did manage to fix it (at least I think I did, it's still booting) though. To anyone who made the same stupid mistake I did:
All I did was I took the original zip I flashed (linked in the OP), opened it up and replaced the recovery.img with the latest TWRP. Somehow that managed to flash fine, and from there I just flashed a deodexed stock rom from recovery. I have no idea how this worked but I'm just happy I don't have a ~$350 paperweight.
PROTIP: don't flash at 2 in the morning, kids
Click to expand...
Click to collapse
I am in the EXACT same situation, the problem I have is that I am unable to edit the zip file to insert the twrp recovery in. Every time i try to edit it with winzip for mac or other mac programs it says that the zip is corrupted. WHat did you use to edit the zip file?
---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------
shobon said:
The RUU wouldn't work since I was on 2.06 and iirc you can't downgrade with a locked bootloader and/or s-off.
I did manage to fix it (at least I think I did, it's still booting) though. To anyone who made the same stupid mistake I did:
All I did was I took the original zip I flashed (linked in the OP), opened it up and replaced the recovery.img with the latest TWRP. Somehow that managed to flash fine, and from there I just flashed a deodexed stock rom from recovery. I have no idea how this worked but I'm just happy I don't have a ~$350 paperweight.
PROTIP: don't flash at 2 in the morning, kids
Click to expand...
Click to collapse
Or even better, do you have this edited zip that I could flash? I'm at my wits end now.
doctajay said:
I am in the EXACT same situation, the problem I have is that I am unable to edit the zip file to insert the twrp recovery in. Every time i try to edit it with winzip for mac or other mac programs it says that the zip is corrupted. WHat did you use to edit the zip file?
---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------
Or even better, do you have this edited zip that I could flash? I'm at my wits end now.
Click to expand...
Click to collapse
You do now there is a 2.07 ruu although its in Chinese. But you could flash that and then install recovery if you can't use fastboot to flash one.
After that install a stock 2.06 or 2.07 use moonshine... then install whatever rom you want.
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
All I can tell you is that it worked for me. AT&T Unlocked HBOOT 1.55, firmware 3.17.502.3, ROOTED... just like yours. After I ran rumrunner a prompt appeared on the phone screen that I confirmed with OK and that was it. The phone rebooted several times and ended up with LOCKED HBOOT and S-OFF. I had to unlock again with a new Unlock code from htcdev.
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
Did you do this on windows 8
Did u have to extract the rumrunner zip into a specific folder such as fastboot folder and run it from there?, did u need adb drivers it says if you htcdev unlock the adb doesn't need to be downloaded.
I mean of all else fails where's the exact files /links you used , there's to many variables here can you help any further ?
Why won't my phone keep rebooting past the 2nd fastboot reboot instead just keeps counting.
Sent from my HTC One using xda app-developers app
lojak29 said:
Did you do this on windows 8
Did u have to extract the rumrunner zip into a specific folder such as fastboot folder and run it from there?, did u need adb drivers it says if you htcdev unlock the adb doesn't need to be downloaded.
I mean of all else fails where's the exact files /links you used , there's to many variables here can you help any further ?
Why won't my phone keep rebooting past the 2nd fastboot reboot instead just keeps counting.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes I did this on Win 8. I unzipped the file in a folder on the desktop and ran soju.exe file. I had the ADB drives installed for my previous HTC One X. Didn't download anything extra except for the rumrunner.zip. Make sure you are full stock and rooted. Also you have to uninstall HTC Sync if you have it installed.
lightflier said:
Yes I did this on Win 8. I unzipped the file in a folder on the desktop and ran soju.exe file. I had the ADB drives installed for my previous HTC One X. Didn't download anything extra except for the rumrunner.zip. Make sure you are full stock and rooted. Also you have to uninstall HTC Sync if you have it installed.
Click to expand...
Click to collapse
I'm starting to think I'm experiencing a usb3.0 issue on my gateway which is apparently a huge issue topic under the how to get around soff block thread ..
Windows Usb3.0 on windows 8 doesn't work well with fastboot.
But it seems complicated to change/force Intel usb3.0 drivers which allow fastboot adb to work flawlessly in place of the windows 3.0 usb .
That's the whole issue here I believe.
Sent from my HTC One using xda app-developers app
lojak29 said:
I'm starting to think I'm experiencing a usb3.0 issue on my gateway which is apparently a huge issue topic under the how to get around soff block thread ..
Windows Usb3.0 on windows 8 doesn't work well with fastboot.
But it seems complicated to change/force Intel usb3.0 drivers which allow fastboot adb to work flawlessly in place of the windows 3.0 usb .
That's the whole issue here I believe.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This is exactly what I was going to say Good luck with USB 2
Make sure your adb is up to date and that you have turned off all anti-virus software...
I had issues too but finally got it to work on my ATT One
Sent from my HTC One using Tapatalk
Does anybody have a mirror of rumrunner for 3.17.502.3? Their website is currently down. Thanks guys.
Edit: Site is back up.
lojak29 said:
my HTC one is on 4.3 ota with 1.55 hboot as far as i have read on one thread someone had succesfully soff with rumrunner
It wasnt clear if he was using atat htc One.
I have tried this 20 times and i get stuck with this
it reboots fine once into hboot reboots once into fastboot then locks up at adb reboot
i have all the proper drivers i have adb drivers installed .I have unchecked fastboot in power settings
I also have downloaded the proper rumrunner for my firmware which is os-3.17.502.3
Am i missing something here guys ..is this even possible with the att One on 1.55 hboot with 4.3 android or am i on the wrong track waisting time, this is rediculous
ANY other options to downgrade to get soff from where i stand. I need soff
THIS IS WHAT I GET
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (32/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (13/120)
Waiting
Waiting for ADB (20/120)
Click to expand...
Click to collapse
Did you solve this problem mate? I have the same issue with my one..
mctodd said:
Did you solve this problem mate? I have the same issue with my one..
Click to expand...
Click to collapse
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
make sure you installed latest driver
This is working now I just did mine yesterday. The previous version would lock my phone up while running the tests.
Sent from my HTC One using XDA Premium 4 mobile app
Linux makes life so easy.........
Worked flawless on my One last night. Same firmware as OP:thumbup:
Sent from my HTC One using Tapatalk
I got
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: **** It
........................................................................................................................................................................................................................................................
so am i screwed?
Hboot 1.55 LOCKED S-Off w/ Rumrunner
So, I unlocked my boot loader with HTCDEV. I than used Rumrunner to gain s-off and root. It worked but now it says Tampered "locked" but is S-off. I'd like to unlock my bootloader and if possible without HTCDEV again. I just got the phone set back up. I backed up my apps but I couldn't get TWRP to load through a flashing app or Goomanager. I'm guessing this is because I'm locked. Can anyone help?? Not sure what to do here. Sounds like you guys figured this out but I didn't see the howto..
is it ok to ask what the purpose of s- off is?
I had to be on stock ROM to be able to S-OFF when I tried the other day. I also had to put all the rumrunner files in the same folder as my sdk/adb stuff. Make sure, if your phone prompts you to accept the connection from the PC, to accept.
Is your phone even showing up when you try 'adb devices' ?
Yes, that all worked fine. I ended up installing Clock work through their app.. never could get twrp to work
Sent from my HTCONE using xda app-developers app
pontypool said:
is it ok to ask what the purpose of s- off is?
Click to expand...
Click to collapse
The purpose of S-OFF is so you can change the CID (carrier ID) and a few other things. It is the master access to the phone pretty much. Once you change the CID you can flash stock ROMs (custom roms can be flashed without S-OFF), which allow you to convert your AT&T HTC one to the google play edition or any other edition like the European editions.
I got it to work on my One. I had to try twice. I think it failed the first time because of an SU permission popup or something which I pressed allow but then rumrunner ended without finishing. The second time it worked though.
How did you uninstall the HTC Sync app? I've tried a couple of different ways, but it comes back after I restart the phone.
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!
Hello all, I've just recently recovered my DNA back to stock from a botched ROM install on the 3.06 software. Prior to running the RUU, I used Rumrunner to unlock my bootloader to put CWM on as my recovery. Then I had to re-lock it to run the RUU. Now I'm stuck at re-unlocking it. The HTCdev site is giving me a MID not allowed error and I'm thinking it has something to do with the fact that I used Rumrunner? Call me stupid, the DNA is still relatively new to me. Thank you!!
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
iissmart said:
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Edit: Nevermind, tried a different cable. Hate it when that happens.
Edit 2: Rumrunner must have failed, device still relocked.
Hubblemuffin said:
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Click to expand...
Click to collapse
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
iissmart said:
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
Click to expand...
Click to collapse
I don't even see ADB devices in device manager. Just Android USB Devices.
Hubblemuffin said:
I don't even see ADB devices in device manager. Just Android USB Devices.
Click to expand...
Click to collapse
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
RLGL said:
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
Click to expand...
Click to collapse
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Hı, have you find out a solution to this one ?
I am struggling with a similar situation:
http://forum.xda-developers.com/showthread.php?p=51140962
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
iissmart said:
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
Click to expand...
Click to collapse
Updating the hboot and radio seems a little daunting. Definitely something I want to look in to once I can figure out how to get a ROM on this without calling a mulligan and starting from scratch again.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Adb is universal to all android devices, I highly recommend getting used to it if you plan on rooting future devices, the only thing native to HTC is the S-OFF portion of eMMC
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF? If so issue this command in fastboot:
fastboot oem writecid 22222222
Go to htcdev.com and then it will allow you to unlock the bootloader also make sure you have 8 2's in the command.
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