So i installed and ran weaksause then installed su followed the weaksause guide for firewater
C:\Program Files\Minimal ADB and Fastboot>adb reboot
C:\Program Files\Minimal ADB and Fastboot>adb wait-for-device push C:\Users\XXXXXX\Desktop\firewater /data/local/tmp
3624 KB/s (4519496 bytes in 1.217s)
C:\Program Files\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
Click to expand...
Click to collapse
i get the error run firewater as root su or fu even though root checker says i have root and i even grant su permission to root checker so i know su is working. Im confused any help????
Solved: Skipped the su step after pushing firewater and adb shell. Its important to look at your phone after typing su in adb shell as it will ask you on the phone to grant firewater su. After thast everything went smooth installed a new recovery and about to install a new rom as we speak. Unlocked and s-off :good:
Related
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse
hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps
Thanks! Will try again soon!
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
As far as I remember your supposed to flash 1.34 Rom after changing the version number to 1.33 as the rooting is only possible via 1.34 Rom and not 1.72 Rom .... And you clearly missed that step .... Open desire z wiki and read the psneuter guide ... Follow it word for word .... You will root your phone
Maxymo123 said:
Hello.
I've tried to root my Desire Z. I wanted to achieve only the ROOT not S-off and so on. Just to be able to use some root requiring applications like DSP Manager or Adds free.
1. So I've downloaded and installed Android SDK.
2. Started ADB
3. "adb devices" gave me the proper answer
4. Then I've copied and started psneuter and misc_vesion:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
exit
5. Then I've tried to root the phone:
Ive copied the required files:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
And then from the Terminal Emulator I've entered
/data/local/tmp/root
I've got some messages that the everything is read only so I've tried rage first:
/data/local/tmp/rage
I've got the proper "Forked #### childs" output
and then I've tried the "/data/local/tmp/root" again. But I'm getting the "cannot fork" message.
I'm new in this stuff s please help me. What do I do wrong?
I only want the simple root access I don't want to downgrade my phone and install any custom roms.
Please help.
ps. my "compilation number" is: 1.72.405
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Just out of curiosity, if you only want to root to use some applications and such, why don't you just temp root using visionary and just redo it whenever you restart your phone?
Thanks for the answers guys.
your supposed to flash 1.34 Rom after changing the version number to 1.33
Click to expand...
Click to collapse
hispeedworm - I don't want to downgrade my phone. I don't need it and I don't want to loose whole the settings and apps and start from the beginning just for using some special apps.
mmduluth - I've used the visionary method from this topic while it seemed the easiest one for the beginner. However after taping the "TempRoot Now!" the VISIONary+ seemed to hang. The screen was black for several minutes.
So I've decided it does not work.
Anyway, I'd prefer to have permanent root than a temp one for example for using "autostarts" - which as far as I'm concerned works AFTER rebooting the phone.
So anyone could tell me where is a mistake in what I did?
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Maxymo123 said:
I suppose I've omitted one thing in former trials so I've tried to root it again.
After entering the Terminal Emulator I've run rage:
/data/local/tmp/rage
I've got the Forked #### childs message so everything was ok till then.
Then I've reset terminal --> menu-->reset term
And then I've run the terminal again.
I should get the # sign but what I get is the totally white screen with no possibility to write any command. It's not responding. I can only get out from it by pressing the home button.
So what's going wrong?
Click to expand...
Click to collapse
If you read enough threads/post, at the moment, the only way to gain permaroot is to downgrade your ROM. Unless, somebody finds a way to do it without the need to downgrade.
And, as I understand, using Visionary apps would cause damage to your device. Be careful!
Cheers...
Thank you silverwind. Now it's clear.
So anyone is working on this?
Cheers
I am following these steps
http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/
I typed /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
it then says exploiting device and then goes back to C:\androidsdk\tools and I never get the # command prompt. Looking for advice on what to do next.
Thanks in advance.
Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer
Nipqer said:
Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer
Click to expand...
Click to collapse
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
obas said:
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
Click to expand...
Click to collapse
i also get this following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer
Nipqer said:
That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer
Click to expand...
Click to collapse
I went to that page and got no help . I was wondering if you could look over my steps before I attempt this any further, does this look like it will work.
C:\AndroidSDK\tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
956 KB/s (9796 bytes in 0.010s)
C:\AndroidSDK\tools>adb push misc_version /data/local/tmp/misc_version
1405 KB/s (15837 bytes in 0.011s)
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/fre3vo
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/misc_version
C:\AndroidSDK\tools> /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
---- Also if the above process looks good can my next command be the following
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip ????
Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer
Nipqer said:
Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer
Click to expand...
Click to collapse
Actually everything worked up till this command
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
when I did that it said "file not found" I do believe. So I then tried $ adb push PC10IMG.zip /sdcard/PC10IMG.zip and I got the same error.
I have both the PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip and PC10IMG.zip in the androidsdk\tools folder so this should work right? not sure why I am getting file not found.
Thanks for all you help also I am also there I can feel it
You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer
Nipqer said:
You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer
Click to expand...
Click to collapse
Ok, now I'm confused because this link http://forum.xda-developers.com/showthread.php?t=1178912 has this command under the "downgrade" section.
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
$ adb reboot bootloader
That seems to me they are saying to do adb push from the $ command.
Can someone please help me i want to know if im putting the commands correctly...... okay my adb and all that is in a folder called SDK in my C drive so C:\SDK and i put firewater in there i open a command line and enter what?
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
or would i put
adb reboot <--important!!!!
adb wait-for-device push firewater C:/SDK
adb shell
chmod 755 /C:/SDK
su
C:/SDK/firewater
and also would it be / or \ in the terminal ... if can could someone post the exact commands for what i would have to put thank you so much
C:\SDK>adb wait-for-device push firewater /data/local/tmp
3087 KB/s (4347896 bytes in 1.375s)
C:\SDK>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
[email protected]:/ #
all it shows it doesnt do anything after the last command
You are making it way to complicated. Follow instructions in firewater thread and you will be all set.
dnyoe65 said:
C:\SDK>adb wait-for-device push firewater /data/local/tmp
3087 KB/s (4347896 bytes in 1.375s)
C:\SDK>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
[email protected]:/ #
all it shows it doesnt do anything after the last command
Click to expand...
Click to collapse
scott7044 said:
You are making it way to complicated. Follow instructions in firewater thread and you will be all set.
Click to expand...
Click to collapse
If you're not going to helpful, PLEASE don't even bother in posting
When I got mine S-OFF, I used this set of commands:
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
Type them in exactly as they are above chmod first, then su, then run firewater.
At least, that's what worked for me after trying su then chmod like 50 times with no success.
Hello.
So now we can get root shell on LG Q7
adb push mtk-su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
Any ideas how to setup root access for apps?
Give me link
I can't have a root shell. When I enter /data/local/tmp/mtk-su it just exits adb shell