Related
For anyone having issues with running this in linux.
I used zikronix guide and modified it for use in a linux support thread. The original thread can be found here:
http://forum.xda-developers.com/showthread.php?t=829045
This is my setup:
-I made sure to show my .bashrc profile and path to my tools folder if you needed help getting that setup as well... If not please ignore.
Code:
[email protected]:~$ cat .bashrc | grep adb
alias start-adb='sudo /usr/local/android-sdk/tools/./adb start-server'
alias kill-adb='sudo /usr/local/android-sdk/tools/./adb kill-server'
[email protected]:~$ cat .bashrc | grep android-sdk
export PATH="/usr/local/android-sdk/tools/:${PATH}"
[email protected]:~$ $PATH
bash: /usr/local/android-sdk/tools/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
Download: http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
Download (Mirror): http://sdx-downloads.com/EVO/devs/jerdog/fixes/hboot202-s_off-V6.2.zip
Now This might make things easier.
-I have this so that you are in the same enviroment that i was in so that the paths will be the same.
Code:
wget http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
mkdir Evo-root
mv hboot202-s_off-V6.2.zip
cd Evo-root
unzip hboot202-s_off-V6.2.zip
- This step I just made sure that adb devices showed my device. If not get it working.
- Once adb devices showed my device properly, I simply ran the following commands.
Code:
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
adb push root/amon_ra.img /sdcard/
- Then this is just changing permissions. Pretty straight forward.
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
- Running the script. Should kick you out of adb... If not after 5 min kill the adb server and restart.
Code:
adb shell
./data/local/tmp/rageagainstthecage
- Now you should see a "#", if you do proceed. If not then run the script above again till it works.
Code:
adb shell
- If you saw that "#" run this. This can only be ran as root "#" means root.
Code:
./data/local/flash_image misc /sdcard/mtd-eng.img
Now you are going to want to reboot into the bootloader. Make sure once you do that you selet bootloader and let the PC36IMG.zip load.
Code:
reboot bootloader
After that is done reboot into the new rooted rom. Then make sure adb works again. Then run the following commands. Make sure you terminal is in the same directory this entire time there is no reason to leave the direcory we went into earlier "cd Evo-root" You directory should always be Evo-root. Thanks. The part that I found out was the second command where the entire recovery/ needed the permissions changed to be executable. As you saw in my post on that forum board.
- This will remove the PC36IMG.zip to a different name so that the bootloader won't get confused again. Then the second commands makes the directory executable recursivly. Then the third will reboot you into recovery.
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-ENG.zip
chmod -R +x recovery/
adb reboot recovery
- Now this is going to be done at the recovery screen. As long as you followed the steps above it will work fine. Should only take you about 20 mins to root this phone. Though it took me about 2 hours since no one else has been rooting using linux. I am thinking about writing a script that will root everything and alls you have to do is follow a terminal guide.... But ill see.
- Just run these commands that will allow you to flash the unrevoked-forever.zip. Once you follow the onscreen instructions of the unrevoked-forever.zip you will be able to reboot into the recovery and see the S-Off. Once that is done reboot into the rom, now we need to flash a custom recovery!
Code:
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
- Again make sure your terminal was never closed and in the same folder. Then simply run these commands to flash the Amon_ra recovery. Since it has wimax capabilities I prefer it.
Code:
adb push root/flash_image /data/local/
adb shell
chmod 0755 /data/local/flash_image
./data/local/flash_image recovery /sdcard/amon_ra.img
reboot recovery
Now you should see the custom recovery and you should be able to flash any rom you desire!
reserved for later use
i see that they are same commands as the pc.., so would this also work with PC?
nickespi said:
i see that they are same commands as the pc.., so would this also work with PC?
Click to expand...
Click to collapse
I am guessing your talking about windows? Sure make sure adb is in your path. Though there are steps in here that are only for linux.
95% success
Well I want to thank you for this thread
It has worked for me I have root I have NAND unlocked
I can flash ROMs
The only issue I have is my radio/baseband and PRI version have been lowered
I have not been able to get thise back where they whould with either update or by using teh wimax.ADDRESS.tree.xml fix (there is no file with that)
If you have any ideas how to fix this would be much appreciated
I am unable to get higher tahn baseband 1.36.00.04.02 in ant rom
when I got teh phone it was 2.15.00.xx.xx
any help would be appreciated
100% Success
THANK YOU
My Evo
Hardware 004
Build 3.30
Hboot 2.02
Baseband 2.15.xx.xx
is now sucessfully rooted.
I did have some problems after being able to flash ROMs of not haveing PRI and Baseband updated.
On thread #787756 there are downloads that can be flashed to fix this problem if anyone else is in that boat.
zikronix sent me there for the fix...I believe he is adding it to the main thread but if it isn't there yet I wanted to add it now for anyone in my boat.
Again this method works and there is success.
Happy rooting
Hey thanx for this Linux guide. Does this steps work with the update 12.25.10 on the windows thread?
Will you update this guide?
Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.
I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash
gee one said:
I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash
Click to expand...
Click to collapse
thanks for the reply, but I was asking if after I've done that I could flash the boot img with CWM? I've heard that nvflash doesn't work on B70 transformers.
Sent from my HTC Vision using Tapatalk
Yup, in step 6, you would zip it up and flash it via cwm.
pm sent!!!
perquisitor_omnia said:
Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.
Click to expand...
Click to collapse
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system
gls9 said:
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system
Click to expand...
Click to collapse
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.
perquisitor_omnia said:
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.
Click to expand...
Click to collapse
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]
gls9 said:
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]
Click to expand...
Click to collapse
Thats what I am doing at the moment, but it is annoying to have to stage all files to /data/local or /sdcard before copying files to /system from the tablet, when it is much easier to do
$ adb push <file> /system/
from the host computer. Anyway, if I make a insecure bootloader for my tablet that can be flashed from the recovery, I'll post it here as it might be useful to other people in my position.
I've got an insecure boot.img from the US 8.6.5.21 firmware if anyone is interested. It's just the boot in a zip file.
Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.
sidneyk said:
Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.
Click to expand...
Click to collapse
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk
Are you trying this in recovery or under the normal system? Try it under both.
sent from my transformer
I'm trying under the normal system, I will try under recovery when I get access to my desktop.
Sent from my Transformer TF101 using Tapatalk
OK, how about some testing:
from your PC:
adb version
adb shell grep secure /default.prop (or adb shell getprop ro.secure)
This will check your adb version and also see if your ro.secure flag is set.
I tested 'adb remount' and it worked as intended. I'm on adb version 1.0.29 with ro.secure=0.
Also, the recovery ramdisk has it's own default.prop and ro.secure flag, so these can actually be set independantly, but I think you would notice it immediately if recovery wasn't insecure.
Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?
perquisitor_omnia said:
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I am familiar with errors kind of like this from Mac OS, dunno if it applies here but you might try repairing permissions from CWM. I have fund that quite a lot of ROMs do not have correct permissions set.
Cheers!
-M
Xda member since 2007
perquisitor_omnia said:
Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?
Click to expand...
Click to collapse
Yeah, that would cause the issues. Not sure how to fix it, but some ideas:
1) flash an insecure boot.img via cwm
2) use the staging partition to flash a boot.img/blob
3) ???
I finally used the SBK detect tool, my B70 has a nvflashable firmware, so I will pull the boot loader with nvflash and make it insecure that way.
Sent from my HTC Vision using Tapatalk
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?
Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU
I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium
nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it
http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805
It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU
Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!
Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU
How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.
Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse
Hi! I wouldl ike to restore my phone from being S-off, custom recovery, and a custom rom. Can anyone please guide me through the steps ? (I just need to know what I have to do I know my way around android devices just not that used with HTC. Should I flash a stock rom, flash stock recovery, then s-off ?)
Thanks
You should read the threads in dev section carefully before proceding, but the short version should be like this:
1. copy "misc_version" to android sdk / adb folder
2. cmd: adb push misc_version /data/local/tmp
3. set older software version with misc_version to flash a older RUU File
cmd: adb shell /data/local/tmp/misc_version -s 1.27.405.6
4. copy original hboot.img (0.98.00...) to root of microSD card.
5. open cmd :
cd/
cd android-sdk-windows
cd platform-tools
adb devices
adb shell mount /sdcard
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
6. restart to bootloader
7. enter fastboot
8. run RUU
THIS IS NOT A HOWTO, check yourself if this is the right way for you!!!
Or check this thread: http://forum.xda-developers.com/showthread.php?t=1187231
Maybe it's the simple way...
hello i have my device SM A202F ANDROID 11 so i tried to root it but not working i have tried with kingroot ADB and Odin to flash twrp but not works if someone have the file to root it please share it thx
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
jwoegerbauer said:
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
Click to expand...
Click to collapse
am i undesrstand i have unlocked the bootloader but can you make a video about abd push i dont understand