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
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.
So just trying to prepare myself for when I get my phone back from repair that HTC puts 4.3 on there instead of 4.1.2 since Att release is out now.
My understanding 4.3 comes with hboot 1.55 what are my chances of achieving s off with the rum runner if this happens or any other ways
I know if it gets sent back as 4.1.2 a d hboot 1.44 I'm good.
Just curious as to what I'm in for if they do put 4.3 on there
Sent from my HTC One X+ using XDA Premium HD app
I'd like to also find out some information regarding this topic. I had my device swapped because I couldn't take the purple camera any longer.. and the replacement had 4.1.2 installed, but when I booted it and during setup, I let the 4.3 OTA come through and installed the update (not even thinking about the hboot version).. So I now am stock 4.3 w/ hboot 1.55 - I'm assuming at the moment that I cannot really do much until we get 1.55 hboot correct? For the fun of it, I tried running the AT&T 1.26.512 RUU but it failed
OP: not hijacking your thread, just didn't want to create a new thread with the same topic..
No sounds like you have the exact problem I could have
In warranty disclaimer it says phone will be loaded with most recent os released for your carrier.
Now that 4.3 is out I'm afraid HTC will just load that on their
Sucks I had a off before camera problem
Sent from my Nexus 7 using XDA Premium HD app
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Fberry said:
Are you saying that if I have 4.12 with Hboot 1.44 that rumrunner will give me s off. The only list I have seen of versions it works for is on the HTC One forum and all of the versions seem to be international or verizon.
Click to expand...
Click to collapse
You can use moonshine or revone (which I used) with HBOOT 1.44, however with HBOOT 1.54 you need to use rumrunner but it is not the same unlock as with revone because with rumrunner you actually need to unlock the bootloader via HTCDEV.
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
ac3kill said:
Ya but Att 4.3 Rom comes with hboot 1.55 is there a way to downgrade to 1.54 and then us rum runner
Sent from my HTC One X+ using XDA Premium HD app
Click to expand...
Click to collapse
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
EsJayEs said:
There is a version now for us AT&T people with 4.3. I'd test it now, but after getting home from work, it's beer:30
http://forum.xda-developers.com/showthread.php?t=2487888
http://rumrunner.us/rumrunner_downloads/rumrunner_m7_3.17.502.3.zip
Click to expand...
Click to collapse
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
noobsquared said:
Not trying to hijack the thread but I just replaced my G2 with HTC One and this HTC One has 4.3.
I have tried every method on this site but I can't get adb to work in order to s-off.
Is anybody else having the issue where when you do adb devices, it says offline?
I turned fastboot off, developer options on, debugging mode on and adb devices on macbook, parallels and windows 8 machine..all say offline in front of the phone id
Click to expand...
Click to collapse
I tried it anyway. Here's the result:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
No matter how many times I've tried it. I followed the directions exactly as stated. The only thing that changed is now I have the "tampered" flag in the bootloader.
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
EsJayEs said:
Also, I'm doing this with a Vista 64-bit machine. I've tried using the "adb devices" command several times before executing soju, but still no luck. I'm running a completely stock phone and the only modification I've done is the HTCdev bootloader unlock. Has anybody had success with Rumrunner for 3.17.502.3 ?
Click to expand...
Click to collapse
there is something new with 4.3, they kinda block the adb. when i was on 4.1.2 the adb "fastboot" command working just fine, but once i ran the ruu and update my htc one to 4.3, now when i type adb devices it show me my device but OFFLINE. so it might be a new hidden menu to activate the adb port again "make it read the device" or maybe we need a new driver "which i doubt"....
Well I saw they have the Att firmware on rum runner site 3.17. Whatever the rest is so we should be fine at getting soff I just have not seen someone say they have since Att stock is is hboot 1.55 but ill figure it out when my pphone get back
Hoping its 1.44 hboot and I can downgrade and unlock bootloader without HTC knowing this time but that would be to easy and I'm sure ill have stock 4.3 1.55 we shall see this week !
Sent from my HTC One X+ using XDA Premium HD app
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
noobsquared said:
So, I unlocked my phone and tried to run the rumrunner with no luck.
Even after bootloader unlock, adb devices still says offline in front of the serial number.
Has anyone figured out why it says offline and how to enable adb mode properly after 4.3 update?
Click to expand...
Click to collapse
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
EsJayEs said:
If I run the adb devices command, it will sometimes say offline. If I run it a second time, it shows it's connected.
---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------
I've also tried flashing the official RUU to my phone for a completely fresh start, and still have no luck.
Click to expand...
Click to collapse
I'm having the same thing.
One time it says offline, the other it says connected.
I've ran rumrunner_m7_3.23.666.1 almost 5 times now with the same result. The only difference is that my HBOOT screen says tempered but I still have S-On and I don't think it's getting anywhere. It does the pouring and restarts the phone quite a few times but I'm guessing it's not having any luck. Maybe rumrunner only supports up to HBOOT 1.54 and since we are HBOOT 1.55, it won't work?
Here is how the process has went the 6th time I believe when I ran it:
==================== rumrunner S-OFF 0.0.3 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
pouring (1).............................
pouring (2)...............................
pouring (3)...............................
pouring (4)...............................
pouring (5)................................
pouring (6)...............................
pouring (7)...............................
pouring (8)...............................
Wait 30 seconds, power on device, run rumrunner again.
Press ENTER to exit
---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------
And here is what my adb says after running that process 6 times:
W:\Downloads\Android\HTCOne\htcone>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT********** device
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
I may have figured it out.
I had version 3.17.502.3 on AT&T HTC One and I've been running rumrunner for .666 version.
I just downloaded rumrunner_m7_3.17.502.3 and about to give it a shot. Will keep everyone posted. Sorry if I annoyed anyone with my dumb post and mistake :silly:
I never got to the pouring part, but I was also apprehensive about using Rumrunner for a different version. I can't remember where I read it on here, but one of the 2.24 users that did it bricked his phone. Or rather it bricked itself during it's first phone call after s-off. No confirmation if it was due to using a different rumrunner than what he had, but I wouldn't want to be the first guy to try. For that, I thank you.
Interesting how the version you used doesn't have all of those test waiting for fastboot and adb.
Thanks for the kind words and motivation EsJayEs
I'll keep everyone posted. Someone has to be the bait or nobody gets the goodies :good:
So, when I ran the right version, it says:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (26/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
I'm guessing because I tried wrong version and now my HBOOT says tempered. Maybe I'll relock bootloader and try to run RUU to go back to stock and start over. Aah, I wish I would have never gone to G2 and stayed with my HTC One that I had working and perfectly setup!
I re-locked the bootloader, installed the latest AT&T RUU, unlocked the bootloader, then ran rumrunner_m7_3.17.501.3 which matches my system version and OS version in HBOOT menu but it seems like it's still not working.
Here is the output after running rumrunner:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Still don't have my phone sounds like it could be because hboot 1.55
But I don't get why our Att firmware is on rumrunner site if hboot 1.55 don't work because the 3.17 firmware ones with hboot 1.55 and they make it very clear to be stock.
Man I need my phone back I'm ready to start trying
Sent from my HTC One X+ using XDA Premium HD app
That's the exact problem I had time and time again.
Double check you have the right rumrunner for your firmware. Im sure you have.
Don't worry about doing the fastboot bit, you know its all connecting fine.
Boot your phone as normal, on to the phones home screen. Open a command prompt in the same folder as yout ADB link.
Type ADB Devices, and it should find your phone, model number and so on. Leave the window open. Then start rumrunner. It worked for me 1st time then.
Steve
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
As above
Steve
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------
That was not me just copied it from another forum. If I had a pc I would try. Hope it works for you guys.
Sent from my HTC One using XDA Premium 4 mobile app
While rooting / SOFFing my One Max, I had to look all around to find all the parts. I wanted to create a guide so other people could get it faster / easier than I could .
This is for the Sprint HTC One Max, not sure how other devices will react. rumrunner is for more than just the Sprint version though.
I TAKE NO CREDIT. IM JUST PUTTING A GUIDE TOGETHER. ALL CREDIT GOES TO PEOPLE WHOM MADE THIS HAPPEN.
Credit: (In no order) Please donate to them! They deserve it.
rumrunner: SOFF program.
scotty1223: Unlocking/removing tampered flag
Flyhalf205: Custom recoveries
carl1961: Unsecure kernel
HTC for an awesome phone
If I forgot anyone, let me know! Everyone that made this happen is awesome!
DISCLAIMER: IT IS NOT MY FAULT IF YOUR PHONE YELLS AT YOU AND RUNS AWAY BECAUSE YOU DID SOMETHING WRONG.
Step One: Unlock your bootloader at htcdev.com. Create an account and follow their instructions. When it asks you for your device put "all other support devices"
Step Two: Make sure your ADB/Fastboot prompts are working. Here's how we check that:
a. Make sure USB debugging is on.
b. Plug in your phone, then open your adb prompt.
c. Issue the command adb devices. If your serial number is shown, adb is working.
d. While still in the adb prompt, issue the command adb reboot bootloader. Your phone will reboot in to your bootloader
e. Now issue the command fastboot devices. If your serial number is shown, fastboot is working.
f. Reboot your device so it's on and fully boot up. It's time to get set up!
Step Three, Getting all the files needed on your craptop. (Computer, just kidding)
a. Download your choice of recovery from flyhalf205's thread (TWRP didn't play nice with my phone, so I used CWM, but your results my vary).
CWM: http://forum.xda-developers.com/showthread.php?t=2498749
TWRP: http://forum.xda-developers.com/showthread.php?t=2498746
b.Then download this superuser.zip. :http://www.mediafire.com/download/v27kh5nkpo3nfum/superuser.zip Place it on your phone somewhere.
c. Then download rumrunner from beaups' thread: http://forum.xda-developers.com/showthread.php?t=2525375
d. Then download carl1961's unsecure kernel : http://www.mediafire.com/download/rrfelsllgomrpix/Sprint_One_Max_1.16.651.4_Unsecure_kernel.zip
Step Four: Lets do this thing!
a. First, we flash a custom recovery. Place the recovery you downloaded from flyhalf205 into the same directory as your adb/fastboot stuff.
b. Plug in your phone, issue the command adb devices just to make sure there is a connection. (can never be too careful now.)
c. If all is good and a serial number is shown, issue the command adb reboot bootloader.
d. You should see a string of words on your phone's bootloader saying "fastboot usb". Issue the command fastboot flash recovery "NAME OF RECOVERYFILEHERE".img. If all goes well. You now have a custom recovery, woop!
BOOT INTO THE RECOVERY AND MAKE A NAND. NOT OPTIONAL.
While in recovery, go ahead and flash the superuser.zip as you would do any other zip.
e. Now open the kernel and extract the boot.img file, place it in the adb/fastboot place.
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand .
HOW-TO Re-enable your fingerprint scanner!
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
a. Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
b. Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
I'll help if I can. Have fun everyone!
If I can recommend rumrunner first **for Verizon versions** which soff, unlocks bootloader (vice htcdev) , installs unsecure kernel and roots. Htcdev unlock voids warranties for some carriers. Then install recovery of choice.
Lastly I would insert a line to remind everyone to donate to the devs for countless hours put in.
EDITED for versions
Any issues with fingerprint scanner
Thanks PUNK9 for putting this guide together!! Thanks to the devs for their hard work!!
I've had my One Max for 2 weeks and I must root it!!!
I read that unlocking the One Max caused issues with the fingerprint scanner. Is this your experience?
Also, I am a fan of TWRP. What issues did you expereince that caused you to go to CWM.
Thanks,
Gary
Jiggity Janx said:
If I can recommend rumrunner first **for International and Verizon versions** which soff, unlocks bootloader (vice htcdev) , installs insecure kernel and roots. Htcdev unlock voids warranties for some carriers. Then install recovery of choice.
Lastly I would insert a line to remind everyone to donate to the devs for countless hours put in.
Click to expand...
Click to collapse
Do I need unlock the bootloader via HTCDev and flash insecure kernel after S-OFF in order to get root on VZW One Max ?
GaryJohnSr said:
Thanks PUNK9 for putting this guide together!! Thanks to the devs for their hard work!!
I've had my One Max for 2 weeks and I must root it!!!
I read that unlocking the One Max caused issues with the fingerprint scanner. Is this your experience?
Also, I am a fan of TWRP. What issues did you expereince that caused you to go to CWM.
Thanks,
Gary
Click to expand...
Click to collapse
TWRP would go on the "swipe to unlock" screen I wasn't able to swipe it. So I used the classic version of CWM.
Also yes, unlocking the bootloader stops the fingerprint scanner from working. Here is how you get it back working (Which i'll update the OP for)
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
Have fun!
androitri said:
Do I need unlock the bootloader via HTCDev and flash insecure kernel after S-OFF in order to get root on VZW One Max ?
Click to expand...
Click to collapse
No to htcdev. Rumrunner does all of that for the verizon version EDITED OUT
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version and I *believe* it does all that for all versions.
Click to expand...
Click to collapse
anyone use rumrunner and the boot image he attaches with a sprint phone?
---------- Post added at 12:59 PM ---------- Previous post was at 12:18 PM ----------
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version and I *believe* it does all that for all versions.
Click to expand...
Click to collapse
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
from rumrunner prereq's.
What is considered a device blocked by htcdev?
Having some work issues lately... as in I may not have work in the next week or two. Removing some of the things I have posted recently because I just was not thinking clearly. My apologies.
Jiggity Janx said:
Having some work issues lately... as in I may not have work in the next week or two. Removing some of the things I have posted recently because I just was not thinking clearly. My apologies.
Click to expand...
Click to collapse
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
i haveflashed Then download carl1961's unsecure kernel, and i have supersu installed provided by above link. bootloader unlocked by HTCDEV. Same output, constantly.
I receive this for a rumrunner output, what am i doing wrong???
Never getting any popups to give ADB root access, no popups for any escalation.
Starting from usb debugging mode android OS up.
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (38/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (32/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
---------- Post added at 04:08 PM ---------- Previous post was at 03:12 PM ----------
Jiggity Janx said:
No to htcdev. Rumrunner does all of that for the verizon version EDITED OUT
Click to expand...
Click to collapse
DeadPhoenix said:
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
Click to expand...
Click to collapse
From rumrunner instructions -
Prerequisites
32-bit Linux (Ubuntu is preferred)
Live CD’s are fine.
Live USB is fine.
Native install is fine.
VM’s are unsupported.
64-bit Linux may work with 32 bit libraries, but is unsupported.
Finger print
Punk9 said:
TWRP would go on the "swipe to unlock" screen I wasn't able to swipe it. So I used the classic version of CWM.
Also yes, unlocking the bootloader stops the fingerprint scanner from working. Here is how you get it back working (Which i'll update the OP for)
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
Have fun!
Click to expand...
Click to collapse
Finally done and S-OFF. How do I go 'bout fingerprint again???
I was unable to use htcdev.com to unlock the bootloader. I am with Verizon, perhaps thats the issue, not sure. The error I received
Error Code: 160.
Error Reason: MID Not Allowed
Tried using rumrunner and of course that failed due to the fact the bootloader is still locked and there is no unsecure kernel.
Am I missing something?
Punk9 said:
While rooting / SOFFing my One Max, I had to look all around to find all the parts. I wanted to create a guide so other people could get it faster / easier than I could .
This is for the Sprint HTC One Max, not sure how other devices will react. rumrunner is for more than just the Sprint version though.
I TAKE NO CREDIT. IM JUST PUTTING A GUIDE TOGETHER. ALL CREDIT GOES TO PEOPLE WHOM MADE THIS HAPPEN.
Credit: (In no order) Please donate to them! They deserve it.
rumrunner: SOFF program.
scotty1223: Unlocking/removing tampered flag
Flyhalf205: Custom recoveries
carl1961: Unsecure kernel
HTC for an awesome phone
If I forgot anyone, let me know! Everyone that made this happen is awesome!
DISCLAIMER: IT IS NOT MY FAULT IF YOUR PHONE YELLS AT YOU AND RUNS AWAY BECAUSE YOU DID SOMETHING WRONG.
Step One: Unlock your bootloader at htcdev.com. Create an account and follow their instructions. When it asks you for your device put "all other support devices"
Step Two: Make sure your ADB/Fastboot prompts are working. Here's how we check that:
a. Make sure USB debugging is on.
b. Plug in your phone, then open your adb prompt.
c. Issue the command adb devices. If your serial number is shown, adb is working.
d. While still in the adb prompt, issue the command adb reboot bootloader. Your phone will reboot in to your bootloader
e. Now issue the command fastboot devices. If your serial number is shown, fastboot is working.
f. Reboot your device so it's on and fully boot up. It's time to get set up!
Step Three, Getting all the files needed on your craptop. (Computer, just kidding)
a. Download your choice of recovery from flyhalf205's thread (TWRP didn't play nice with my phone, so I used CWM, but your results my vary).
CWM: http://forum.xda-developers.com/showthread.php?t=2498749
TWRP: http://forum.xda-developers.com/showthread.php?t=2498746
b.Then download this superuser.zip. :http://www.mediafire.com/download/v27kh5nkpo3nfum/superuser.zip Place it on your phone somewhere.
c. Then download rumrunner from beaups' thread: http://forum.xda-developers.com/showthread.php?t=2525375
d. Then download carl1961's unsecure kernel : http://www.mediafire.com/download/rrfelsllgomrpix/Sprint_One_Max_1.16.651.4_Unsecure_kernel.zip
Step Four: Lets do this thing!
a. First, we flash a custom recovery. Place the recovery you downloaded from flyhalf205 into the same directory as your adb/fastboot stuff.
b. Plug in your phone, issue the command adb devices just to make sure there is a connection. (can never be too careful now.)
c. If all is good and a serial number is shown, issue the command adb reboot bootloader.
d. You should see a string of words on your phone's bootloader saying "fastboot usb". Issue the command fastboot flash recovery "NAME OF RECOVERYFILEHERE".img. If all goes well. You now have a custom recovery, woop!
BOOT INTO THE RECOVERY AND MAKE A NAND. NOT OPTIONAL.
While in recovery, go ahead and flash the superuser.zip as you would do any other zip.
e. Now open the kernel and extract the boot.img file, place it in the adb/fastboot place.
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand .
HOW-TO Re-enable your fingerprint scanner!
You have to relock (after SOFFing it) the bootloader.
All credit goes to scotty1223.
a. Follow this OP to lock your bootloader. : http://forum.xda-developers.com/showthread.php?t=2540004
b. Follow this OP to remove the tampered flag on your bootloader : http://forum.xda-developers.com/showthread.php?t=2540024
I tested all of this on my own Sprint HTC One Max, and it has all worked with no side effects. After relocking and removing the tampered flag my fingerprint reader was 100% working again.
I'll help if I can. Have fun everyone!
Click to expand...
Click to collapse
If this helps anyone out there. I think unplugging device from USB while rumrunner states it is "Waiting for adb" is probably a good idea. Then plug it back in once the device is fully booted and off the security screen.
This was found on a post somewhere on these forums. Guess its worth a try, i will let everyone know the results!
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
luv2ride said:
I was unable to use htcdev.com to unlock the bootloader. I am with Verizon, perhaps thats the issue, not sure. The error I received
Error Code: 160.
Error Reason: MID Not Allowed
Tried using rumrunner and of course that failed due to the fact the bootloader is still locked and there is no unsecure kernel.
Am I missing something?
Click to expand...
Click to collapse
Read second post of this thread
Jiggity Janx said:
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Read second post of this thread
Click to expand...
Click to collapse
I will try that!!!! thanks for the response!!!!
I went back and did some research. Found the correct version of RumRunner & completed the process. I was using the "universal" version.
Jiggity Janx said:
Everyone having issues with rumrunner should make sure they have plugged in their phone into their computer with AND without adb debugging enabled AND in fastboot to make sure all drivers are set up properly before rumrunner.
Having said that beaups himself said the device driver error is normal.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Read second post of this thread
Click to expand...
Click to collapse
Finished flashing the unsecure kernel and locked the bootloader. Now I'm unable to turn on wifi, I slide the tab and it grays out without turning on. Anyone have an idea on this one?
luv2ride said:
Finished flashing the unsecure kernel and locked the bootloader. Now I'm unable to turn on wifi, I slide the tab and it grays out without turning on. Anyone have an idea on this one?
Click to expand...
Click to collapse
As my second post says rumrunner does EVERYHTING for verizon versions. You have now flashed something non verizon to your phone (kernel) so likely it will have prpblems . You are lucky you are not screwed permanently. However you may have to wait until a dev creates a flashable verizon unsecure kernel. Im not sure what direction to tell you to go...
same issue
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (47/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
when out of developer mode it is not detected by OS which is strange, HTC Sync picks it up when i reinstalled it attempting to get drivers to make it be detected. What is this issue about? simply PC drivers?
---------- Post added at 07:12 PM ---------- Previous post was at 06:49 PM ----------
just tried from linux - same exact error.
any ideas?
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
logikzzz said:
same issue
==================== rumrunner S-OFF 0.5.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (47/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Press ENTER to exit
when out of developer mode it is not detected by OS which is strange, HTC Sync picks it up when i reinstalled it attempting to get drivers to make it be detected. What is this issue about? simply PC drivers?
---------- Post added at 07:12 PM ---------- Previous post was at 06:49 PM ----------
just tried from linux - same exact error.
any ideas?
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (59/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try a
gain.
ERROR: run rumrunner again.....
Click to expand...
Click to collapse
omg, ive been running wrong one. should be using universal... lol this will work now i bet
---------- Post added at 07:53 PM ---------- Previous post was at 07:18 PM ----------
s-off wow i feel dumb
DeadPhoenix said:
Did you unlock on Windows or Linux?
I have linux-64 bit ubuntu and I get a error when running ./soju
error while loading shared libraries: libcurl.so.4
Click to expand...
Click to collapse
install 32-bit curl libs and ur all set!
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.
HI Fellow XDA member.
I intially tried everything and failed. So I have decided to factory reset my Verizon HTC one MAX, and
redo the s-off. It finally worked!!!
Here are the exact steps.
Credit to MrT69 for his awesome collection of drivers.
Credit to the Firewater team for the awesome program.
Credit to all the XDA members for their contribution and anyone else I forget.
Here is my software version:
Android 4.4.2, Sense 5.5, Software version 2.16.605.2
HBoot 2.49.000
1. Factory reset your Verizon HTC One Max.
* Press and hold the VOLUME DOWN button, and then press and hold the POWER button.
* Wait for the screen with the three Android images to appear, and then release the POWER and VOLUME DOWN buttons.
* Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button.
2. Go thru the basic setups. Setup Wifi which is require for Firewater to work. Make sure wifi is working.
3. Enable developer Options : Setting - About - Software - More - Tap on Build number 5 times.
* Checked - USB debugging
* unchecked - everything else
4. Goto Security.
* Check - Unkown sources
* Uncheck - Verify apps.
5. Goto Display
* Screen timeout - 1 hour.
6. Download and install Es Explorer ( or any file manager of your choice )
7. download drivers from here
http://forum.xda-developers.com/showthread.php?t=2765383
8. Install the driver in the freshly installed windows 7, x86, sp1.
9. Download Weaksauce from here. Copy into phone thru Windows Explorer
http://forum.xda-developers.com/showthread.php?t=2699091
10. Install using Es Explorer. Click I agree.
10a. Download Firewater from here
http://firewater-soff.com/instructions/
(CRITICAL - Download with Internet Explorer, WILL NOT WORK WITH ANY OTHER BROWSER.)
11. Now Run CMD.exe as Administrator in windows. Make sure adb.exe and firewater is in the same directory.
12. type the followings:
adb devices
*make to to watch the phone screen to give permission to the program.
* make sure you see the device number and device,
* if offline, that means you missed the screen to give permission to the program
adb reboot <–important!!!!
* after reboot, rerun WeakSauce and click I agree to make sure root is working.
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
13. Your Verizon HTC one Max is now S-OFF!!!
Discussion.
I didn't bother to run temproot because there is some script program.
If this works for you, please leave a reply. Thanks.
Mod edit: no need to quote the entire OP....
can you plz tell what to type after 12. ( type the followings
adb devices… its there..
waco2hot33 said:
adb devices… its there..
Click to expand...
Click to collapse
thanks
this have to type all togather plz help
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
---------- Post added at 10:49 PM ---------- Previous post was at 10:04 PM ----------
xda-developers1974 said:
Thanks its work now
Click to expand...
Click to collapse
S-OFF and unlocked now, but Fingerprint scan stop working anyone help Plz
xda-developers1974 said:
S-OFF and unlocked now, but Fingerprint scan stop working anyone help Plz
Click to expand...
Click to collapse
Is your boot loader unlocked
hi
xda-developers1974 said:
S-OFF and unlocked now, but Fingerprint scan stop working anyone help Plz
Click to expand...
Click to collapse
So u got this to work with the new sense 6 update or were u on something else
calculus said:
Download Firewater from here
http://firewater-soff.com/instructions/
(CRITICAL - Download with Internet Explorer, WILL NOT WORK WITH ANY OTHER BROWSER.
Click to expand...
Click to collapse
Not true
---------- Post added at 05:04 AM ---------- Previous post was at 05:04 AM ----------
cj28sc said:
So u got this to work with the new sense 6 update or were u on something else
Click to expand...
Click to collapse
He was on 5.5
thayl0 said:
Not true
---------- Post added at 05:04 AM ---------- Previous post was at 05:04 AM ----------
He was on 5.5
Click to expand...
Click to collapse
Yup.. he knows everything.
Man I really miss not being able to root this bad boy on OTA 6 sense my self… waiting patiently for a root method… !!
NO WAY!
Hey Fellas,
I just picked up a HTC One Max on VZW today.
**** LOCKED ****
T6WL PVT SHIP S-ON RH
HBOOT - 2.49.0000
RADIO - 1.36.60.0520
ON SENSE 6
Am I to understand that I am pretty much screwed on root right now?
rafaelvelasquez2 said:
Hey Fellas,
I just picked up a HTC One Max on VZW today.
**** LOCKED ****
T6WL PVT SHIP S-ON RH
HBOOT - 2.49.0000
RADIO - 1.36.60.0520
ON SENSE 6
Am I to understand that I am pretty much screwed on root right now?
Click to expand...
Click to collapse
Nope you are not. Check out Sunshine. It will take will unlock the bootloader and get you S off. You take care of the rest. I was completely stock on the sense 6 OTA when I found out about and used Sunshine. Sunshine does cost $25 to use, but for me, it was worth it.
Sounds promising. Thanks. I'm googling now.
Sent from my HTC6600LVW using XDA Free mobile app
thafrogggg said:
Nope you are not. Check out Sunshine. It will take will unlock the bootloader and get you S off. You take care of the rest. I was completely stock on the sense 6 OTA when I found out about and used Sunshine. Sunshine does cost $25 to use, but for me, it was worth it.
Click to expand...
Click to collapse
Thanks for the advice. I googled SunShine, paid my $25, ran the app and BOOM!!! Unlocked! S-Off! and Root. All I had to do was fastboot flash the unofficial verizon 2.8.0.0 twrp recovery (that confused me for a few hours as well, I was getting errors with the official), install supersu and update the binaries and that was it. I'm chillin on some cyanogenmod now and loving it.
rafaelvelasquez2 said:
Thanks for the advice. I googled SunShine, paid my $25, ran the app and BOOM!!! Unlocked! S-Off! and Root. All I had to do was fastboot flash the unofficial verizon 2.8.0.0 twrp recovery (that confused me for a few hours as well, I was getting errors with the official), install supersu and update the binaries and that was it. I'm chillin on some cyanogenmod now and loving it.
Click to expand...
Click to collapse
Glad it went easy for you. I have not put a custom rom on mine yet. I am considering it, but doing something stupid and borking a phone is not the same as borking a tablet. The tablet can sit until I can figure out what I did wrong. I cant do that with my main line of communications.
waco2hot33 said:
Man I really miss not being able to root this bad boy on OTA 6 sense my self… waiting patiently for a root method… !!
Click to expand...
Click to collapse
Sunshine might work. Google it. You could flash an older rom if your unlocked.
thayl0 said:
Sunshine might work. Google it. You could flash an older rom if your unlocked.
Click to expand...
Click to collapse
Yeah sunshine worked for me I finally broke down and paid for it ..I'm back in business !!!
rafaelvelasquez2 said:
Thanks for the advice. I googled SunShine, paid my $25, ran the app and BOOM!!! Unlocked! S-Off! and Root. All I had to do was fastboot flash the unofficial verizon 2.8.0.0 twrp recovery (that confused me for a few hours as well, I was getting errors with the official), install supersu and update the binaries and that was it. I'm chillin on some cyanogenmod now and loving it.
Click to expand...
Click to collapse
What does it mean to fastboot flash twrp? Im trying to install a custom rom on my verizon one max but idk how to install a custom recovery. My phone is still locked and i have the sunshine app (havent paid the $25 yet) how do i install the custom recovery?
Xx MOE said:
What does it mean to fastboot flash twrp? Im trying to install a custom rom on my verizon one max but idk how to install a custom recovery. My phone is still locked and i have the sunshine app (havent paid the $25 yet) how do i install the custom recovery?
Click to expand...
Click to collapse
You can't flash anything while you are S-ON, bootloader locked, and you can't unlock the bootloader or get S-OFF without Sunshine. Once you are bootloader unlocked and S-OFF, you flash a custom recovery like TWRP so you can gain root and you can (if you choose) flash a custom ROM or other modifications. For the Verizon One Max, Sunshine is the only alternative.
It sounds like you haven't yet looked at other threads here to learn the difference between booting to bootloader, booting to recovery or booting to system, or what S-ON/S-OFF means, or what adb and fastboot are for. You should know all of those things before you wade in and accidentally brick your One Max.
There aren't a lot of devs still working on the device, but there are lots of threads in this forum and elsewhere on xda that will tell you what you need to know. "Search" is your friend.
It sounds like you haven't yet looked at other threads here to learn the difference between booting to bootloader, booting to recovery or booting to system, or what S-ON/S-OFF means, or what adb and fastboot are for. You should know all of those things before you wade in and accidentally brick your One Max.
There aren't a lot of devs still working on the device, but there are lots of threads in this forum and elsewhere on xda that will tell you what you need to know. "Search" is your friend.[/QUOTE]
I have looked at other threads and understand s-off, boot loader on/off, and stuff. What I don't understand, is how to install the custom recovery. I've seen tutorials for how to install custom recovery on the HTC one m7 but none for the one max. I'm not sure if there's a difference. Most of the threads I've seen simply say that I need sunshine, which I have installed on my phone but I'm trying to gather all the information I need on how to install a custom Rom before pulling the trigger and forking out $25.