[Q] Rumrunner, wait 30 sec, run rumrunner again - HTC One Max

So, im stuck at the phase where rumrunner kept pouring shots and after 7 tries it stated to run it again. i know it said it doenst work on all custom rom, and i running stock rooted rom ( does that mean its custom rom?). is that the reason rumrunner wont run for my sprint htc one max phone?
i tried firewater and it also didnt S-off my phone.
im running android 4.4.2 with hboot 2.49
tampered unlocked and custom rooted stock rom.

HtcEvo4gLTE said:
So, im stuck at the phase where rumrunner kept pouring shots and after 7 tries it stated to run it again. i know it said it doenst work on all custom rom, and i running stock rooted rom ( does that mean its custom rom?). is that the reason rumrunner wont run for my sprint htc one max phone?
i tried firewater and it also didnt S-off my phone.
im running android 4.4.2 with hboot 2.49
tampered unlocked and custom rooted stock rom.
Click to expand...
Click to collapse
Rumrunner won't work with hboot 2.49 ..
u must use firewater only for s-off now
what step of firewater do you have problem?

blue8 said:
Rumrunner won't work with hboot 2.49 ..
u must use firewater only for s-off now
what step of firewater do you have problem?
Click to expand...
Click to collapse
i tried firewater. it doesnt work. i use the first step stock rooted rom. so i dont need temp root. but it didnt s-off my phone.
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
The first bottle is open
chugging.....
[email protected]:/#
it just stop from there.

HtcEvo4gLTE said:
i tried firewater. it doesnt work. i use the first step stock rooted rom. so i dont need temp root. but it didnt s-off my phone.
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
The first bottle is open
chugging.....
[email protected]:/#
it just stop from there.
Click to expand...
Click to collapse
Did you try different HTC driver?
Check these post
Code:
http://forum.xda-developers.com/showpost.php?p=52770187&postcount=12
Code:
http://forum.xda-developers.com/showpost.php?p=52777681&postcount=14

blue8 said:
Did you try different HTC driver?
Check these post
Code:
http://forum.xda-developers.com/showpost.php?p=52770187&postcount=12
Code:
http://forum.xda-developers.com/showpost.php?p=52777681&postcount=14
Click to expand...
Click to collapse
i did. still didnt work. i was reading about that too. people claim to got it working with older driver.

*cry*

Related

HTCDEV method not working on my Evo 3D GSM

One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Post in q&a not development !
crossmanbx said:
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Click to expand...
Click to collapse
HTCDev unlock method doesn't work on phones with replaced motherboards. You're out of luck, sorry.
it's called bad blocks. nothing you can do about it ...
Can't you use juopunutbear and do the wire trick?
00mpollard said:
Can't you use juopunutbear and do the wire trick?
Click to expand...
Click to collapse
I think it's a good idea to try the juopunutbear, but i need to have temp root at least.
And all temp root i find are made for Gingerbread.
Does anyone know a temp root method for ICS ?
Thank you
Questions and non-development related should be posted in the appropriate sections. This thread is not dev related, so I'm moving it.
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
crossmanbx said:
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
Click to expand...
Click to collapse
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
kgs1992 said:
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
Click to expand...
Click to collapse
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
ramjet73 said:
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
Click to expand...
Click to collapse
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Click to expand...
Click to collapse
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
ramjet73 said:
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
Click to expand...
Click to collapse
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
kgs1992 said:
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
Click to expand...
Click to collapse
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
ramjet73 said:
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
Click to expand...
Click to collapse
Yes, that's right, it doesn't matter.
That is basically the TPSparkyRoot exploit, but I've modified it slightly.
Hope it does work.
If it doesn't, whoever tries it, please post the error message.
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
Click to expand...
Click to collapse
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
johnmarshton said:
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
Click to expand...
Click to collapse
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
kgs1992 said:
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
Click to expand...
Click to collapse
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
johnmarshton said:
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
Click to expand...
Click to collapse
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
kgs1992 said:
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
Click to expand...
Click to collapse
Could he push an "su" binary to the system partition while he has temp root?
ramjet73

Unique DNA issue (also trying to S-OFF)

Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
hurrrtin said:
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
Click to expand...
Click to collapse
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
PhantomApollyon said:
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
Click to expand...
Click to collapse
fastboot oem writecid xxxxxxxxx if you have issues with revone, try typing "su" before ./revone -p in shell so it runs as root (if you have root obviously)
Also omitting the "-p" switch might help.
fr4nk1yn said:
Also omitting the "-p" switch might help.
Click to expand...
Click to collapse
Even though this is marked solved in the op, im going to leave this tidbit here as it most likely would have applied here.
adb install dnashellroot.apk
[16:40] <@beaups> then
[16:40] <@beaups> adb shell
[16:40] <@beaups> am start -n c.fyf/.MainActivity
[16:41] <@beaups> wait 10 seconds, then
[16:41] <@beaups> /dev/sh
[16:41] <@beaups> let me know if $ turns into #
[16:41] <maxiixam> k
[16:42] <maxiixam> hah, helps if im not in fastboot =P
[16:43] <@beaups> indeed
[16:43] <maxiixam> don't worry this aint my first rodeo
[16:43] <@beaups> says the guy who went s-on...
[16:44] <Nick> lmfao
[16:44] <maxiixam> every dog has his day.
[16:44] <maxiixam> also next, we got #
[16:45] <@beaups> cool
[16:45] <@beaups> echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
[16:45] <@beaups> ^copy/paste that
[16:45] <@beaups> do NOT screw it up
[16:45] <maxiixam> done
[16:46] <@beaups> ok
[16:46] <@beaups> exit
[16:46] <@beaups> exit
[16:46] <@beaups> adb reboot bootloader
[16:46] <@beaups> fastboot getvar cid
[16:46] == Bowsakirby [[email protected]/web/freenode/ip.69.92.52.209] has quit [Ping timeout: 250 seconds]
[16:46] <maxiixam> all 2222222's just procede to htcdev?
[16:47] <@beaups> yep
[16:47] <@beaups> then use facepalm for s-off
Run this from an elevated cmd prompt where you have un zipped moonshine.
*I am not responsible for what may happen to your phone*

[s-off]Firewater S-OFF

Mod edit: Firewater has been shut down server-side and is no longer supported. Try Sunshine.
It claims to S-off any HTC device that is rooted/unlocked.
*Works with Hboot 2.47
Home
welcome to firewater
what firewater can do for you:
S-OFF Your HTC device
Unlock your bootloader
Prerequisites
Working adb on your PC. Yes, that means OS X, linux, Windows, 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, droid dna, one s, one max, and many others.
Instructions (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 HERE - _http://firewater-soff.com/firewaterdownload-3
Push, Prepare, and Execute firewater:
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 (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 HERE - _http://firewater-soff.com/firewaterdownload-3
Download temproot HERE - _http://firewater-soff.com/temprootdownload
Push, Prepare, and Execute temproot and firewater:
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
_http://firewater-soff.com/instructions/
ps: i am not a member of firewater team
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.
Click to expand...
Click to collapse
For those in HBOOT 2.49, please revert to stock 1.19.xxx ROM and try this - more instructions http://forum.xda-developers.com/showthread.php?t=2765383
LOLZ
worked a treat, many thanks, cheers again
DANIELWHITT said:
worked a treat, many thanks, cheers again
Click to expand...
Click to collapse
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
pradeepvizz said:
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
Click to expand...
Click to collapse
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
DANIELWHITT said:
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
Click to expand...
Click to collapse
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
pradeepvizz said:
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
Click to expand...
Click to collapse
Hboot is 2.47 and int one max t6up
DANIELWHITT said:
Hboot is 2.47 and int one max t6up
Click to expand...
Click to collapse
Thanks!
help
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
It worked!!!
Thanks a lot! It worked like a charm...
Tried rumrunner but without success. Firewater did it in under 30 seconds! Amazing!
I have a German Telekom based One Max with 2.46 hboot (T6UL).
Thanks for your work!
OMG! Thank you so much. i have max one UK hboot 2.47 and this worked in less that 2 mins. now s-off'd
thank you
Tampered message also gone too!
will relock now and see if fingerprint scanner enables.
:laugh:
Edit: re-locked bootloader and now fingerprint scanner works too! also if i unlock, i dont ever get the tampered message again!
thank you so much.
has anyone tested on the HTC One? i dont see a thread there for that but OP says that it should work
Worked like a charm on HTC One (m7ul/International) - ****ing speedy and easy - once I dusted off my adb hahaha.
sns0582 said:
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
Click to expand...
Click to collapse
Use rumrunner on VZW One Max, worked like a charm for me. Fully bone stock when I ran it, worked first try.
Sent from my HTC One Max
thank you
verizon htc one 4.3 hboot 1.55 want temproot
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
sns0582 said:
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
Click to expand...
Click to collapse
is your device must be HTCDEV unlocked?
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
Yes... Your device must be HTCDEV unlocked and rooted.
Worked like a charm on my International One Max, thank you!
im trying to temp root to s off and unlock
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
. If I read correctly it states I need to temp root to s-off , is there a way to HTC dev unlock 4.3 hboot 1.55 on Verizon,

Return to stock

I have a HTC one 32GB and it's currently s-on with tampered showing and unlocked showing . My hboot is 1.56.0000. Need to return to stock since att sending me overnight a replacement...i have stupid purple camera really bad.
Sent from my KFSOWI using Tapatalk
This should be the right one, double check your version. http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
EDIT: have you ever flashed an ruu before?
Sent from my HTC One using XDA Premium 4 mobile app
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
bigfdaddy2 said:
Yes I have currently trying to lock boot loader but says device is offline
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
i got adb to work i had 2 change roms... how do i go about relocking myphone so i can run the ruu
Got my phone relocked know gonna run the ruu
Sent from my KFSOWI using Tapatalk
If you take the phone back to an ATT store for an exchange or to have them fix it, you don't have to return it to stock. they don't check and they don't care. The only time you need to return it to stock is if you are having to send it back to HTC. If at all possible deal with ATT as they will most of the time just hand you a new one while HTC will give you a refurb. You won't get your original back from HTC.
hafizimtiaz said:
Start the phone in fastboot mode and type the following command:
Code:
fastboot devices
What's the output?
Click to expand...
Click to collapse
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
bigfdaddy2 said:
new phone same prblm error device offline while using adb..but run venom adb works but no su when typed in and asked
C:\AndroidSDK>fastboot devices
HT36MW903711 fastboot
C:\AndroidSDK>
Click to expand...
Click to collapse
As it is showing your device ID in fastboot mode, your phone is properly connected in fastboot mode. Does the screen say FASTBOOT USB? If yes, you can run RUU.exe file.
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Stock kernel blocks this...
bigfdaddy2 said:
Yes it does and can run the ruu.... My issue know is how come adb says device offline with stock rooted Rom but with venom Rom it's connected but doesn't grant root when asked to through adb
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Which kernal do I need then I tried with bullet I believe the name was
Sent from my KFSOWI using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
He could but these prop settings mess things up
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.metropcs.ui=0
GalaxyUser50 said:
Doesn't he need USB debugging and accept the computers adb key? That could be why he gets that.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I've gotten to accept root through adb and am trying to use Firewater to s-off my new one and it just fails every time .... Can't seem to find a how to or step by step on it like the older hboots have ...I got 1.56 of course lol ...
Sent from my HTC One using Tapatalk
Wonders_Never_Cease said:
Stock kernel blocks this...
Click to expand...
Click to collapse
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
bigfdaddy2 said:
how do i achieve s-off on hboot 1.56 ive tried rumrunner,firewater,arhd,venom rom
Click to expand...
Click to collapse
Wonders_Never_Cease said:
i think i used firewater for s-off,I unlocked via htc dev and then ran the firewater on numerous htc ones, you do need an unsecured boot image for your device though...root actually isnt needed,is a plus but i didnt root my devices and it worked with just a unsecured boot image I made
Click to expand...
Click to collapse
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
bigfdaddy2 said:
this my current setup: win7 ,htc one m732gb,hboot 1.56.00,rom currently using arhd 31.6.... i am unlocked,rooted,fastboot disabled,no lock...what else am i missing to achieve this ?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
adb/fastboot configured correctly? htc sync removed and latest drivers installed?
Click to expand...
Click to collapse
sync is gone adb works ,fastboot works,latest drivers....
C:\Users\ace\Desktop\htc 1 toolkit>adb reboot
C:\Users\ace\Desktop\htc 1 toolkit>adb wait-for-device push firewater /data/loca
l/tmp
protocol failure
C:\Users\ace\Desktop\htc 1 toolkit>adb push firewater /data/local/tmp
2532 KB/s (4519496 bytes in 1.743s)
C:\Users\ace\Desktop\htc 1 toolkit>adb shell
[email protected]:/ # su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.5.15 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]:/ #
C:\Users\ace\Desktop\htc 1 toolkit>

[Q]How to approach this VZW One Max

Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
ceo4eva said:
Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
Click to expand...
Click to collapse
If you still need help with this, I recently did this on a Verizon One Max, double check the following:
Fastboot mode is off in the power/battery settings
No lock screen security enabled, pattern, pin, face, nothing should be on
Leave the screen on a long timeout, or no timeout for this process, adb may prompt RSA checks you'll need to grant permissions to.
Remove all super user apps, busybox installer apps, supersu, superuser, whatever
Then:
Run weaksauce app
Install supersu from play store or you can adb install the apk if you have the updater zip or apk on your PC
After you have su (# prompt instead of $ after typing su) in adb shell turn off WiFi, leave mobile data on:
adb shell
su
If you see it change to # then proceed, if not, reboot and run weaksauce again, wait for a minute and try the commands again.
Exit adb shell (type exit and hit enter twice)
Push firewater to /data/local/tmp
adb push firewater /data/local/tmp
Set 755 permissions on firewater:
adb shell
su (if not on # prompt, it should still be there)
chmod 755 /data/local/tmp/firewater
Run firewater (still in shell, don't close the terminal or exit from su/#):
/data/local/tmp/firewater
Last time it froze the first time, then the second try it went through on the second bottle. If you see no improvement after 3 minutes hold power for 60 seconds until it reboots the device, then start again from the weaksauce running part.
Hope this helps. I did it over team viewer with another user and this is what finally got it to get it all finished.
Rumrunner doesn't work with verizon 2.49 that I can tell, it'll be weaksauce and firewater.

Categories

Resources