I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.
going through the same exact thing. I have a fresh verizon device and i checked to make sure everything matched up. and they do. Firmware, HBOOT, RADIO, everything.
I get to chugging and then bam..sorry this wont work on your phone etc. Whats also funny is this phone has a brighter clearer display and has a weird serial id. seomthing like FFA something when my original is HT something. Ive also factory reset 12 times.
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated
jtbndy said:
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated
Click to expand...
Click to collapse
My phone yields the identical information.. Rooted soff'd and all custom romd up time and time again.
Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
S1L3nTShaDoWz said:
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
Click to expand...
Click to collapse
I just exchanged phones with HTC and was still able to use Firewater
Sent from my HTC6525LVW using XDA Premium HD app
jtbndy said:
I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.
Click to expand...
Click to collapse
Did you follow the instructions here to the letter? http://firewater-soff.com/instructions/
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
berndblb said:
Did you follow the instructions here to the letter?
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
Click to expand...
Click to collapse
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
jtbndy said:
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
Click to expand...
Click to collapse
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
Tigerstown said:
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
Click to expand...
Click to collapse
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
jtbndy said:
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
Click to expand...
Click to collapse
Fastboot turned off?
Sent from my HTC6525LVW using XDA Premium HD app
Fastboot has been off every attempt.
jtbndy said:
Fastboot has been off every attempt.
Click to expand...
Click to collapse
backup your phone and then do a factory reset then do the process all over again? This might be the way to go. ONce you are back up, install weaksauce then supersu from play store. then go ahead and try the firewater. If no go, then try sunshine but I know its $25 but its easier to use than using firewater.
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters
EKnofsky said:
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters?
Click to expand...
Click to collapse
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app
lucky_strike33 said:
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.
EKnofsky said:
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.
Click to expand...
Click to collapse
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app
lucky_strike33 said:
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
EKnofsky said:
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
Click to expand...
Click to collapse
After it says your phone can be s off and unlocked. Then takes you to PayPal to pay
Sent from my HTC6525LVW using XDA Premium HD app
Related
Disclaimer: This is not one-click. However, it IS relatively short and straightforward, and does not require you to downgrade.
Credits: The 743C exploit, and ChainsDD for Superuser.
You need:
Android SDK installed and working.
The zip attached to this post.
If you're still on Cupcake (Android 1.5) you'll need su and Superuser from http://bit.ly/su2361cd
So, let's get down to business.
Unzip the attached file into your /android-sdk/tools/ directory, it'll make your life (and ours) easier.
Open up your command line, change to the SDK tools directory, and enter these commands:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
Now execute the exploit:
Code:
adb shell
/data/local/tmp/rageagainstthecage-arm5.bin
Wait for the exploit to finish.
Code:
exit
If it doesn't exit cleanly, chances are it worked, just close your terminal or command prompt and open a new one.
Test that it worked:
Code:
adb kill-server
adb start-server
adb shell
If you see a $, it DID NOT work, execute the exploit again. (Step 3)
If you see a #, it WORKED, continue:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb install Superuser.apk
You may need to ctrl-c once it says Success!
Next time you 'su' in adb shell, make sure to click Allow in Superuser!
You may instead install Superuser from the Market if you wish.
Clean up the exploit:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
If you ever do a "Factory Reset", Superuser will go away, but you DO NOT lose root. Just reinstall Superuser.
What next? The choice is yours! Remove stock apps, get some good 'ol WiFi tethering, or flash something different!
*NOTE*
The above steps DO NOT put a recovery on your phone, though it is VERY EASY.
Once you're rooted, install ROM Manager by Koushik Dutta from the Market. Open it up, click "Flash ClockworkMod Recovery".
Select your model (Hero CDMA), and hit Allow when the Superuser Prompt shows up.
*NOTE*
The above steps DO NOT install Busybox on your phone.
Simply install Busybox from Stephen (Stericson), available on the market.
Start the app and click Allow when prompted by Superuser.
How To Uninstall
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
rm /system/xbin/su
rm /etc/passwd
rm /etc/group
Uninstall Superuser.apk then reboot, and you're set!
tehdarkknight said:
Disclaimer: This is not one-click. However, it IS relatively short and straightforward.
Credits: The 743C exploit, and ChainsDD for Superuser.
You need:
Android SDK installed and working.
The zip attached to this post.
So, let's get down to business.
Unzip the attached file into your /android-sdk/tools/ directory, it'll make your life (and ours) easier.
Open up your command line, change to the SDK tools directory, and enter these commands:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
Now execute the exploit:
Code:
adb shell
/data/local/tmp/rageagainstthecage-arm5.bin
Wait for the exploit to finish.
Code:
exit
If it doesn't exit cleanly, chances are it worked, just close your terminal or command prompt and open a new one.
Test that it worked:
Code:
adb kill-server
adb start-server
adb shell
If you see a $, it DID NOT work, execute the exploit again. (Step 3)
If you see a #, it WORKED, continue:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb install Superuser.apk
You may need to ctrl-c once it says Success!
Next time you 'su' in adb shell, make sure to click Allow in Superuser!
That's it!
I won't give directions on installing a recovery or flashing another rom, there are plenty of threads detailing how to do so.
Click to expand...
Click to collapse
Pretty straightforward. This will probably help a lot of newer hero owners, because amazingly, people are still buying them every day!
If I get a chance to test it out, I will.
Nice job. Should be stickied so people don't run around searching through all the old rooting threads which aren't as compatible with the newer RUU versions.
Worked nicely on a refurb Hero that Sprint sent due to the dust problem.
Thanks!
Works great for me
Why am I having trouble doing this? I was able to do it on one Hero though not after many retries, but not on another.
tehdarkknight said:
Disclaimer: This is not one-click. However, it IS relatively short and straightforward, and does not require you to downgrade.
Credits: The 743C exploit, and ChainsDD for Superuser.
Click to expand...
Click to collapse
Great! I can't live without WiFi tethering my iPad which is why I haven't done the 2.31.651.7 HTC OTA update at all.
So, I take it that this exploit will root the Official RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe file then too? I ask because I really don't like to do 'update patches'. I prefer to flash and start fresh so I'm planning on flashing the RUU and then doing this root exploit. Yes, No???
DaWeav said:
Great! I can't live without WiFi tethering my iPad which is why I haven't done the 2.31.651.7 HTC OTA update at all.
So, I take it that this exploit will root the Official RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe file then too? I ask because I really don't like to do 'update patches'. I prefer to flash and start fresh so I'm planning on flashing the RUU and then doing this root exploit. Yes, No???
Click to expand...
Click to collapse
I tested it with the very same RUU, it works.
tehdarkknight said:
I tested it with the very same RUU, it works.
Click to expand...
Click to collapse
SUPER!
Because when I saw this post, I tried to download the latest OTA patch, but my phone just responds 'Your phone is up to date. There are no updates available for your phone'. Strange, because I'm on 2.27.651.6 and the OTAcerts.ZIP is in tact.
Oh well, FEAR NOT, because after I get back from the store this morning, then get the TV tuned to the split screen with football on one and the baseball playoffs on the other, and get Leo Laporte's TechGuy radio show screaming...it'll be the perfect time to flash my phone to factory fresh.
Thanks.
Works perfectly on latest and "greatest" stock ROM... excellent
DaWeav said:
SUPER!
Because when I saw this post, I tried to download the latest OTA patch, but my phone just responds 'Your phone is up to date. There are no updates available for your phone'. Strange, because I'm on 2.27.651.6 and the OTAcerts.ZIP is in tact.
Click to expand...
Click to collapse
Same thing happened to me, that's why I tested this method with the RUU
What are the advantages to ruu'ing to. 7 and rooting again? I rooted my .5 hero and have had no problems....is there something significant that makes the extra work worth it?
Sent from my HERO200 using XDA App
tehdarkknight said:
Same thing happened to me, that's why I tested this method with the RUU
Click to expand...
Click to collapse
Well, I just did the RUU, then did this root, then loaded WiFi Tether, and I'm back in business with my iPad tethering.
Vandelay007 said:
What are the advantages to ruu'ing to. 7 and rooting again? I rooted my .5 hero and have had no problems....is there something significant that makes the extra work worth it?
Click to expand...
Click to collapse
One reason is that when I tried to download the latest OTA update today, I could not. And another reason is before I RUU'd, I had less than 50MB of available memory, but now I have 96MB available with all of my programs loaded again. So for me, it just seems more and more that Android (or HTC Sense) is like Windows boxes since it seems I have to reload the Android OS every now and then to clean things out.
Vandelay007 said:
What are the advantages to ruu'ing to. 7 and rooting again? I rooted my .5 hero and have had no problems....is there something significant that makes the extra work worth it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Well, if you're using Sprint's official stock .5 rom, with no tweaks applied, you gain the advantage of having an up-to-date rom with the latest bugfixes from Sprint, plus I would say my root method is less invasive and more transparent than other root methods. My personal opinion is that it feels like a root method that can't be abused easily.
SuperOneClick
But I don't need storage space with firerats custom mtd partition....I have over 200mb free with over 50 apps and zero of them on m SD card
Sent from my HERO200 using XDA App
this isnt working.... I can't get passed step 3... my phones just restarts, and then i can't get any further than that.
devonkosa said:
this isnt working.... I can't get passed step 3... my phones just restarts, and then i can't get any further than that.
Click to expand...
Click to collapse
Give us some info. What's your ROM version?
aosp said:
SuperOneClick
Click to expand...
Click to collapse
Is SuperOneClick the same method of rooting?
chiill said:
Is SuperOneClick the same method of rooting?
Click to expand...
Click to collapse
Yes it is....
Ok guyz, I'm going to help yall out !!!!
Look at this and this works I just did it.... any questions pm me then I will post up on here....
http://forum.xda-developers.com/showthread.php?t=803682
This is for rooting your hero and other android devices, even at .7 on the Hero.... I just did this and I laughed at out quick and easy this was... Just make sure you are charge only, and you unzip the downloaded file,.. then open up the SuperOneClickv1.3-ShortFuse.zip on your computer somewhere and open up the SuperOneClick program, and bam you are done....
http://forum.xda-developers.com/atta...5&d=1286657043
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
u need to use search button... its a yellow thing up
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi, you might wanna try to flash this ROM to get back to old Hboot
http://www.4shared.com/file/bAebAgjC/RUU_Saga_HTC_Europe_1284011_Ra.html
It may or may not work on your s-on device but worth to try.
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually
Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
People like this annoy me. As the OP already stated, he can't downgrade with s-on. Just because YOU did, doesn't mean he can. His stock RUU is too new (1.47) and there is no exploit to get temp root yet for this RUU, so downgrading is not possible.
Agreed, he should use the search function, there are about 3 threads of people trying to s-off their 1.47 device. But in his defence, all 3 of those threads are filled with morons like yourself telling people they can do it. Newsflash, you can't.... yet
I'm waiting to :-(
Hope it will no take very long time ahah
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi Evilier.
I just have few questions regarding to your phone, since its one of the "new" software, do you have the Wi-Fi Death Grip? More info can be found here.
And can you tell me which of the v1.47 do you have? Which country I mean.
Well this is going to be a stretch, since you're on the "new" phones software version, can you update/RUU to the latest (RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed)? Then double check if you still have the so could Wi-Fi Death Grip. Thanks a lot.
+ 1 for a method to unlock/root the "new " firmware. Please devs do your magic
Sent from my HTC Desire S using XDA App
davidreece said:
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually
Click to expand...
Click to collapse
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?
jakmor said:
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?
Click to expand...
Click to collapse
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
This part got me all excited in the pants a little. I tried it, but the fre3vo script is hanging at "Frame Buffer handle: 4" for about 5 minutes now.
I will try factory reset on my 1.47 RUU and try once more.
@davidreece: can you confirm what RUU version you had when this worked for you?
davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?
vankox said:
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?
Click to expand...
Click to collapse
You appear to be doing exactly the correct thing...just be patient...(although I admit it does say a few minutes).
See this refined guide....http://forum.xda-developers.com/showpost.php?p=16104882&postcount=16
I'd be tempted to reboot the phone and start at the beginning again, (although the first two steps may well error as the files will be already there - ignore that and proceed).
first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..
ratss123 said:
first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..
Click to expand...
Click to collapse
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?
ben_pyett said:
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?
Click to expand...
Click to collapse
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!
Worked like a charm now s- off again running pre rooted 1.47.401 European Rom many thanks
Sent from my HTC Desire S using XDA App
ratss123 said:
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!
Click to expand...
Click to collapse
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?
ben_pyett said:
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?
Click to expand...
Click to collapse
no sadly i don't, tried to run it also on another pc but it's the same.. there is also another thing, few days ago i tried to run the .exe hoping that it would downgrade, later i found out that i've got hboot 92 so i waited for a new method.. When i tried I didn't get any error message, just thath obviusy it couldn't downgrade... today i tried again and I keep gettint low battery....
I have a Droid Razr Maxx HD and I ran the motochopper and it went through perfectly. Well, the first time it said failure because I already had superuser.apk, but then the second time I uninstalled SuperSU and cleared data for superuser and that time it went through without a hitch. But I'm not rooted and I don't know why.
I tried master resetting twice and I cleared the cache partition as well, but no luck. I can't seem to root my Razr Maxx HD since going to 4.1.2. Any ideas?
heather1209 said:
I have a Droid Razr Maxx HD and I ran the motochopper and it went through perfectly. Well, the first time it said failure because I already had superuser.apk, but then the second time I uninstalled SuperSU and cleared data for superuser and that time it went through without a hitch. But I'm not rooted and I don't know why.
I tried master resetting twice and I cleared the cache partition as well, but no luck. I can't seem to root my Razr Maxx HD since going to 4.1.2. Any ideas?
Click to expand...
Click to collapse
Hi Heather,
So you are trying to root using the motochopper utility released within the past couple of days, and it won't let you root? After completing a root, Have you opened SuperSU and tried downloading the new su binary before doing anything else?
Mr.Parkinson said:
Hi Heather,
So you are trying to root using the motochopper utility released within the past couple of days, and it won't let you root? After completing a root, Have you opened SuperSU and tried downloading the new su binary before doing anything else?
Click to expand...
Click to collapse
Thanks for the reply! Yes, I tried with the new motochopper and it seems to work, at least based on the command prompt, but when the phone restarts, I do not have root. I opened SuperSU to download the new su binary and it says that SuperSU has been denied superuser permissions.
Alright Heather,
Here is what I want you to do.
I want you to move the motochopper utility into an easily accessible location, such as desktop, and (if you're running Windows), I want you to go through the following steps:
0) Make sure your phone is plugged in, with the latest Motorola Drivers installed, and with USB Debugging enabled.
1) Open command prompt as administrator
2) Type the following command (w/o quotes)
Windows 8/7/Vista: "cd \users\[account name]\desktop\motochopper"
Windows XP: "cd \documents and settings\[account name]\desktop\motochopper"
3) Type the following commands (w/o quotes)
Windows 8/7/Vista/XP:
"adb kill-server"
"adb wait-for-device"
"adb push pwn /data/local/tmp/pwn"
"adb shell chmod 755 /data/local/tmp/pwn"
"adb push su /data/local/tmp/su"
"adb push busybox /data/local/tmp/busybox"
"adb install Superuser.apk"
"adb shell /data/local/tmp/pwn"
"adb shell rm /data/local/tmp/pwn"
"adb shell rm /data/local/tmp/su"
"adb shell rm /data/local/tmp/busybox"
"adb reboot"
"adb kill-server"
All that is doing, is just manually doing the root exploit, as opposed to having the batch file do it.
Try this, and if it doesn't work, send me a PM. Good luck!
Very Similiar Issue
Mr.Parkinson said:
Alright Heather,
Here is what I want you to do.
I want you to move the motochopper utility into an easily accessible location, such as desktop, and (if you're running Windows), I want you to go through the following steps:
0) Make sure your phone is plugged in, with the latest Motorola Drivers installed, and with USB Debugging enabled.
1) Open command prompt as administrator
2) Type the following command (w/o quotes)
Windows 8/7/Vista: "cd \users\[account name]\desktop\motochopper"
Windows XP: "cd \documents and settings\[account name]\desktop\motochopper"
3) Type the following commands (w/o quotes)
Windows 8/7/Vista/XP:
"adb kill-server"
"adb wait-for-device"
"adb push pwn /data/local/tmp/pwn"
"adb shell chmod 755 /data/local/tmp/pwn"
"adb push su /data/local/tmp/su"
"adb push busybox /data/local/tmp/busybox"
"adb install Superuser.apk"
"adb shell /data/local/tmp/pwn"
"adb shell rm /data/local/tmp/pwn"
"adb shell rm /data/local/tmp/su"
"adb shell rm /data/local/tmp/busybox"
"adb reboot"
"adb kill-server"
All that is doing, is just manually doing the root exploit, as opposed to having the batch file do it.
Try this, and if it doesn't work, send me a PM. Good luck!
Click to expand...
Click to collapse
I'm having a very similar issue like this. My phone was rooted, then my software updated to 4.1.2 and now I'm no longer rooted. But the SuperSU is still on my phone. When I try to run it, I got the same thing Heather did. "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I did try rooting the phone again with motochopper, but when I do it says it failed because superuser.apk already exists and of course I can delete it. Is there any work around to fix this?
Chris
heather1209 said:
I have a Droid Razr Maxx HD and I ran the motochopper and it went through perfectly. Well, the first time it said failure because I already had superuser.apk, but then the second time I uninstalled SuperSU and cleared data for superuser and that time it went through without a hitch. But I'm not rooted and I don't know why.
I tried master resetting twice and I cleared the cache partition as well, but no luck. I can't seem to root my Razr Maxx HD since going to 4.1.2. Any ideas?
Click to expand...
Click to collapse
I just switched from the S3 to the MAXX HD and motochopper had no issues rooting.
courtct said:
I'm having a very similar issue like this. My phone was rooted, then my software updated to 4.1.2 and now I'm no longer rooted. But the SuperSU is still on my phone. When I try to run it, I got the same thing Heather did. "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I did try rooting the phone again with motochopper, but when I do it says it failed because superuser.apk already exists and of course I can delete it. Is there any work around to fix this?
Chris
Click to expand...
Click to collapse
Whats up Chris,
My utility is available for download, and it can fix your little problem. You will need to reflash your ROM, and reroot. Just use my utility, which I have linked in my Signature! If you want to keep userdata, while in the flashing process, when it asks if you want to erase userdata, just say no.
Cheers!
Mr.Parkinson said:
Whats up Chris,
My utility is available for download, and it can fix your little problem. You will need to reflash your ROM, and reroot. Just use my utility, which I have linked in my Signature! If you want to keep userdata, while in the flashing process, when it asks if you want to erase userdata, just say no.
Cheers!
Click to expand...
Click to collapse
May I ask 1 more question. What exactly does reflashing the ROM mean? In your utility, is that #1 in the deluxe version or is that something I need to do on the device itself prior to rerooting the phone? Just want to make sure I understand exactly which option I should be choosing for that. Thanks again for all your help!
Hi again Chris,
Sorry for not being more specific the first time, but yes, choice number 1 in the main menu, and then there will be a subsection after that, where selecting 1 again would be your best bet. It provides instructions on how to load into fast boot, but I can give them to you here!
1) Power off your phone.
2) Hold down the Volume Down and Volume Up while holding down the Power button.
3) Eventually, a menu will appear, and you can let go of the buttons.
4) When this menu appears, press Volume down to scroll until you reach an option titled AP Fast boot, and press volume up to select.
5) Once you reach the AP fast boot section, just use the utility's built in features to reflash the ROM!
Good Luck Mate!
Sent from my DROID RAZR HD using xda app-developers app
courtct said:
May I ask 1 more question. What exactly does reflashing the ROM mean? In your utility, is that #1 in the deluxe version or is that something I need to do on the device itself prior to rerooting the phone? Just want to make sure I understand exactly which option I should be choosing for that. Thanks again for all your help!
Click to expand...
Click to collapse
I wasn't being very specific in my previous post either.
Reflashing your ROM, means that you are basically just reinstalling the Operating System from scratch. In most cases, it will erase all the data on the phone in the process. By using my utility, Which you launch on your computer and run while the phone is plugged in with USB Debugging on, it will simplify the whole process for you, and makes it optional, but recommended to delete you user data. You will need to do this before you reroot your phone I'm afraid, but its an easy enough thing to do.
If you have any more questions, don't hesitate to ask.
Cheers!
I sort of can't believe this thread is from today. I have followed all of these instructions as I have had the same problems. When I try to use your utility to reflash my stock 4.1.2, it sends the files "OKAY" but fails to write, saying "no such partition". Can you shed any light on what might be wrong with my phone based on that?
EDIT: Compared to the version here http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html that seems to work fine, you try to flash some extra files (slb1 sbl2 etc) that it seems not to like and aborts the process. I tried flashing everything but those but it gives me an error as well. Not sure how to get my root back but I have put a lot of effort at this point
Mr.Parkinson said:
I wasn't being very specific in my previous post either.
Reflashing your ROM, means that you are basically just reinstalling the Operating System from scratch. In most cases, it will erase all the data on the phone in the process. By using my utility, Which you launch on your computer and run while the phone is plugged in with USB Debugging on, it will simplify the whole process for you, and makes it optional, but recommended to delete you user data. You will need to do this before you reroot your phone I'm afraid, but its an easy enough thing to do.
If you have any more questions, don't hesitate to ask.
Cheers!
Click to expand...
Click to collapse
Is there a way to get the utility another way? I have tried downloading it multiple times. Either the download just freezes at a certain % or it gets to 100% and nothing happens. My internet connection is fine though, so I am thinking it may have something to do with the site.
Hi,
The way mega works is different from a traditional download, where once it reaches 100%, it starts to "dump" the file, would probably be the best way to put it. It works great on the latest version of chrome, so I'm not sure what kind of trouble you're having...
Sent from my DROID RAZR HD using xda app-developers app
I havent read this whole thread but I had root on my Razr Maxx HD, then lost it and got it back using this thread
http://forum.xda-developers.com/showthread.php?t=2228613&page=22
I followed this guy's script and it fixed my root issue: http://forum.xda-developers.com/showpost.php?p=40426016&postcount=214
Root not working
I've tried this one 2 different win 7 64 phones and get the following when running the run.bat
Press enter to root phone
press any key
(pressed enter)
waiting for device
daemon not running, starting
daemon started
device found
pushing exploit
4017 KB/s <1283460 bytes in 0.312s>
Pushing root tools
3828 KB/s >366952 bytes in 0.093s>
3653 KB/s <1867568 bytes in 0.499s>
3000 KB/s >1578585 bytes in 0.405s>
pkg: /data/local/tmp/Superuser.apk
Success
Rooting phone
This may take a few minutes
Failure
Cleaning up
Exploit complete. Press enter to reboot and exit
Press any key to continue...
/////////////////////////////
When I check the phone Superuser is installed, but won't work (b/c root was unsuccessful is my assumption). Any ideas?
UnlikelyKiller said:
I've tried this one 2 different win 7 64 phones and get the following when running the run.bat
Press enter to root phone
press any key
(pressed enter)
waiting for device
daemon not running, starting
daemon started
device found
pushing exploit
4017 KB/s <1283460 bytes in 0.312s>
Pushing root tools
3828 KB/s >366952 bytes in 0.093s>
3653 KB/s <1867568 bytes in 0.499s>
3000 KB/s >1578585 bytes in 0.405s>
pkg: /data/local/tmp/Superuser.apk
Success
Rooting phone
This may take a few minutes
Failure
Cleaning up
Exploit complete. Press enter to reboot and exit
Press any key to continue...
/////////////////////////////
When I check the phone Superuser is installed, but won't work (b/c root was unsuccessful is my assumption). Any ideas?
Click to expand...
Click to collapse
same problem, any ideas?
i had the same issue.. i used motochopper and my phone was like "half rooted" only 2 app were given root accesss, i think the issue is the superuser app that comes with motochopper. i downloaded supersu from the playstore, it asked me to delete the other superuser app.. i did.. and now everything works fine.
Same Problem Droid Razr M
I am having the same problem but mine says that there is already the superuser.apk and after it says that it says failure. I'm new to rooting and want to root very badly.
rodmc123 said:
i had the same issue.. i used motochopper and my phone was like "half rooted" only 2 app were given root accesss, i think the issue is the superuser app that comes with motochopper. i downloaded supersu from the playstore, it asked me to delete the other superuser app.. i did.. and now everything works fine.
Click to expand...
Click to collapse
Same here. Uninstall super user and then go to the play store and install the superuser app with a "pound" sign as its icon
Sent from my DROID RAZR HD
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4
shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2
buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:
i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Been following the instructions to s-off with firewater but coming up with problems. First after reboot, after a little while on the phone it says "Root failed" however after sometime using root checker it says that I have root access. I get shell and su to work. But when I "/data/local/tmp/firewater" I don't get the term or condition screen on command prompt, it's just at "/[email protected]_m8wl:/ #"
Any ideas?
same here:
C:\>adb devices
List of devices attached
FA43ASFxxxxx device (edited for paranoia)
C:\>adb reboot
C:\>adb wait-for-device push firewater /data/local/tmp
895 KB/s (4519496 bytes in 4.929s)
C:\>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8wl:/ #
Also my device goes offline after pushing firewater to the device. I uncheck and check debugging but device still shows offline. Eventually it finally goes back online but still can't get the terms to come up when trying to use Firewater.
I"m having the same issue. Checked my version numbers and they all match. Firewater does nothing, no terms, no confirmation, nothing.
Same problem
I've tried uninstalling weak sauce and supersu, used other superuser apps (but that's not the issue, I clearly have root), and tried switching the position of the "su" command when attempting to run firewater. The prompt for the script to say yes to just does not pop up. Brand new M8 today. Everything on the bootloader screen seems to match a few photos I've seen of other vzw phones which were granted s-off.
Maybe the last firewater script is bad? I don't know the last date of update for it.
Same Thing
Yep,
Having the exact same issue. Brand new M8 a few days ago. I'm no stranger to adb, have tried multiple computers, multiple factory resets, and every combination of commands.
Firewater won't even try to run... Any ideas?
Electro900k said:
Yep,
Having the exact same issue. Brand new M8 a few days ago. I'm no stranger to adb, have tried multiple computers, multiple factory resets, and every combination of commands.
Firewater won't even try to run... Any ideas?
Click to expand...
Click to collapse
I ended up having to go from my Mac to my Windows machine then it worked. That shouldn't matter, but it was also suggested to me to redownloaded the tool.
Fixed, don't use Chrome to download.
I just got it, gave up on Chrome and redownloaded from firewater site with (the dreaded) Internet Explorer. Replaced the file, script ran as it should.
titanshadow said:
I ended up having to go from my Mac to my Windows machine then it worked. That shouldn't matter, but it was also suggested to me to redownloaded the tool.
Click to expand...
Click to collapse
Did you follow the steps exactly as under the WeakSauce method?
adb reboot <--important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
I'm tried using a VM (usually doesn't work anyway). ADB through my mac, now I'm using 7x64. Still no luck. Have replaced the firewater script twice just in case. I'm downloading the android sdk and reinstalling now trying to figure this out.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Electro900k said:
I just got it, gave up on Chrome and re-downloaded from firewater site with (the dreaded) Internet Explorer. Replaced the file, script ran as it should.
Click to expand...
Click to collapse
Right when I posted my last, I saw that. Either it was a corrupted dl using Firefox on mac, or it was my SDK. Either way I followed the instructions verbatim in the order given, replaced the sdk and downloaded using IE. It's currently chugging. Hopefully this thread helps out others. Thank you!
That is unbelievable! Haha. Used IE instead of Chrome too and it worked.
I guess IE is good for ONE thing. Worked for me.
Verizon HTC One (M8)
It took me 5 tries to get Firewater to take.
Sent from my HTC6525LVW using Tapatalk