Here is the commands I used:
cd\
cd androidsdk\tools
adb push try3.dat /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su.dat > /system/bin/su1
cat /sdcard/su.dat > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo “#!/system/bin/sh
/data/local/try3.dat /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real” > /system/bin/playlogo
exit
exit
exit
adb install Superuser.apk
adb shell reboot
It said Superuser.apk installed successful. When I tried to reboot it said permission denied.
Here is the CMD pasted. Please help me I have no idea what I am doing wrong.
C:\AndroidSDK>cd\
C:\>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd\
C:\>cd androidsdk\
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ exit
exit
C:\AndroidSDK>adb devices
List of devices attached
SGH-T939 device
C:\AndroidSDK>adb shell
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit
Related
hi guys,i'm working for make a rom kitchen for our sg3 those days
it's 40% done,but i have some troubles
i can't root via this script,can you help me?
this is my code:
Code:
adb push .\root\rageagainstthecage /data/local/tmp/rageagainstthecage
adb push .\root\Superuser.apk /data/local/tmp/Superuser.apk
adb push .\root\su /data/local/tmp/su
adb push .\root\busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/rageagainstthecage
adb shell "/data/local/tmp/rageagainstthecage"
adb kill-server
adb start-server
adb -d shell "mount -o remount,rw /dev/block/stl9 /system"
adb push .\root\su /system/bin/su
adb push .\root\busybox /system/bin/busybox
adb push .\root\sqlite3 /system/bin/sqlite3
adb push .\root\Superuser.apk /system/app/
adb shell "/system/bin"
adb -d shell "chmod 4755 su"
adb -d shell "chmod 4755 busybox"
adb -d shell "chmod 4755 sqlite3"
maybe it's complicate, i tried many times to mod it,but no result.
i run it ，it goes to
adb -d shell "mount -o remount,rw /dev/block/stl9 /system"
this line ，says ‘mount ：operation not permitted ’
and it still $ instead of #
i do not know where the problem is ...
plz help me
hi pls their are two tutorials on this subject pls ask ur question in one of the threads
CLOSED
and my base version is ZHJPF
i think u need to su to remount system as rw.
Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Download the htc flyer 16/32gb file and use that one. After you run the Run_ME_fre3vo_Root.bat File go to terminal and type su then hit enter.
You will get the notice that terminal has been granted superuser permission and you will be all set. Download titanium backup and install it .But remember everytime you reboot you will have to run the .bat again.
Thanks to Eugene373 for creating this tool. And thanks to #Teamwin
Htc Evo 4g rooted s-off cyanogenmod 7
Htc Flyer 16gb wifi rooted s-off Flyhigh rom
If i helped in anyway feel free to hit the thanks button
Or just use z4root. That's what I did on my Next6 while dumping the stock image.
By chance could I get a copy of the Next7's stock image?
temp root
tried z4root, i had no luck with gingerbread.
temp root
here is the system dump for nextbook7p
http://www.multiupload.com/6BY8BVS5BJ
Ok i followed the steps on there but im kinda confused on hoqw you managed to get it to work. The next book 7p always shows as a mountable disk when connected to my computer. On the link it says u need to change it to charge only. I tried ignoring that because the nexbook 7p cant charge via usb. But when i click run_me_fr3vo_root the terminal opens and it says wait-for-devices and thats all. So would u kind giving a more detailed explanation? Id aporeciate it alot cause ive been wanting to root this thing foreverrrrr (3 months lol)
krisf29 said:
Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Click to expand...
Click to collapse
This method did not work with my NextBook 7:
Code:
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb push fre3vo /data/local/tmp
3188 KB/s (9796 bytes in 0.003s)
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /data/local/tmp/fre3vo
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sleep 5
C:\RW_HTC_Flyer(1)>adb remount
remount failed: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /data
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell rm -r /vendor
rm failed for /vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor
mkdir failed for /system/vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor/bin
mkdir failed for /system/vendor/bin, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor
Unable to chmod /system/vendor: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor/bin
Unable to chmod /system/vendor/bin: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\RW_HTC_Flyer(1)>adb push sqlite3 /system/vendor/bin
failed to copy 'sqlite3' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push libext4_utils.so /system/lib
failed to copy 'libext4_utils.so' to '/system/lib/libext4_utils.so': Read-only f
ile system
C:\RW_HTC_Flyer(1)>adb push libfuse.so /system/lib
failed to copy 'libfuse.so' to '/system/lib/libfuse.so': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 655 /system/lib/libext4_utils.so
Unable to chmod /system/lib/libext4_utils.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 000 /system/lib/libfuse.so
Unable to chmod /system/lib/libfuse.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb push default.prop /default.prop
failed to copy 'default.prop' to '/default.prop': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.rc /init.rc
failed to copy 'init.rc' to '/init.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.flyer.rc /init.flyer.rc
failed to copy 'init.flyer.rc' to '/init.flyer.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /default.prop
Unable to chmod /default.prop: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.rc
Unable to chmod /init.rc: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.flyer.rc
Unable to chmod /init.flyer.rc: No such file or directory
C:\RW_HTC_Flyer(1)>adb push fixit /system/vendor/bin
failed to copy 'fixit' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push su /sbin
failed to copy 'su' to '/sbin/su': Permission denied
C:\RW_HTC_Flyer(1)>adb push su /system/vendor/bin
failed to copy 'su' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push busybox /system/vendor/bin
failed to copy 'busybox' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin
Unable to chmod /sbin: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin/su
Unable to chmod /sbin/su: Permission denied
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/su
Unable to chmod /system/vendor/bin/su: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/fixit
Unable to chmod /system/vendor/bin/fixit: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/busybox
Unable to chmod /system/vendor/bin/busybox: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /system/vendor/bin/sqlite3
Unable to chmod /system/vendor/bin/sqlite3: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell /system/vendor/bin/busybox --install -s /system/ven
dor/bin
/system/vendor/bin/busybox: not found
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/ls
rm failed for /system/vendor/bin/ls, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/reboot
rm failed for /system/vendor/bin/reboot, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chmod
rm failed for /system/vendor/bin/chmod, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chown
rm failed for /system/vendor/bin/chown, No such file or directory
C:\RW_HTC_Flyer(1)>adb install Superuser.apk
5818 KB/s (196640 bytes in 0.033s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb install androidterm.apk
6039 KB/s (92780 bytes in 0.015s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb shell ln -s /system/vendor /vendor
link failed File exists
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sync
C:\RW_HTC_Flyer(1)>pause
Press any key to continue . . .
Same here. I tried all of the methods that I could come across on the web with no luck. You would think that it would be a way to root the original factory rom and just flash the device with the rooted rom. That seems to be the only way.
pls help me to get it rooted
i tried Zroot and gingerbreak without sucess
after i tried superoneclick
without sucess
i have a bextbook next8P
pls help
Hi,
I found a nice exploit for Xperia which works fine for Nexus one too ( the DooMLoRD exploit ).
I modified the script to flash the recovery without unlocking the bootloader, so you can flash the rom you like
The exploit works fine on Nexus one 2.3.4 GRJ22 with stock rom and locked bootloader, if you don't have a nexus one:
- remplace files/recovery.img with the right one!
- modify the line in script with the right system partition path.
here's the linux script to do the trick :
2shared.com/file/4uu5h2NH/zergRush_automated_Linux_roott.html
i'm sure someone will port it to windows
NB : backup data, and apps, when you flash a new rom, all data are deleted ( except SD Card).
Automatic installation using the script :
tar -xjvf zergRush_automated_Linux_root.tar.bz2
cd zergRush_automated_Linux_root/
chmod a+x runme-linux
sudo ./runme-linux
Manual installation :
tar -xjvf zergRush_automated_Linux_root.tar.bz2
cd zergRush_automated_Linux_root/
./files/adb kill-server
./files/adb wait-for-device
./files/adb shell rm -r /data/local/tmp
./files/adb shell mkdir /data/local/tmp
./files/adb push ./files/zergRush /data/local/tmp/
./files/adb shell chmod 755 /data/local/tmp/zergRush
./files/adb shell /data/local/tmp/zergRush
./files/adb wait-for-device
./files/adb push ./files/busybox /data/local/tmp
./files/adb shell chmod 755 /data/local/tmp/busybox
./files/adb shell /data/local/tmp/busybox mount -o remount,rw /system
./files/adb push files/busybox /system/xbin
./files/adb shell chown root.shell /system/xbin/busybox
./files/adb shell chmod 04755 /system/xbin/busybox
./files/adb shell /system/xbin/busybox --install -s /system/xbin
./files/adb shell rm -r /data/local/tmp/busybox
./files/adb push ./files/su /system/bin/su
./files/adb shell chown root.shell /system/bin/su
./files/adb shell chmod 06755 /system/bin/su
./files/adb shell rm /system/xbin/su
./files/adb shell ln -s /system/bin/su /system/bin/su
./files/adb push files/Superuser.apk /system/app/
./files/adb shell rm -r /data/local/tmp
./files/adb push files/flash_image /data/flash_image
./files/adb shell chmod 755 /data/flash_image
./files/adb push files/recovery.img /data/recovery.img
./files/adb shell /data/flash_image recovery /data/recovery.img
./files/adb shell rm /data/flash_image
./files/adb reboot recovery
In less than a minute, your phone will reboot to amonRA recovery, flash the rom you want, and Enjoy!
Hi sparkym3,
I'm not able to reply your post "[ROOT] TPSparkyRoot - ICS' so I created a new post here.
I had successfully rooted my Star N8000 phone using the below script with busybox, Superuser and RootExplorer installed.
Root
====
echo off
cls
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo Rebooting (1/3) - Continue once device finishes rebooting
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo Rebooting (2/3) - Continue once device finishes rebooting
pause
adb shell id
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
pause
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
adb push RootExplorer.apk /system/app/RootExplorer.apk
adb shell chown 0.0 /system/app/RootExplorer.apk
adb shell chmod 0644 /system/app/RootExplorer.apk
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo Rebooting (3/3) - You should now be Rooted
pause
echo on
***My question is if I want to unroot my Star N8000 phone, I will need to remove the su, busybox, Superuser and RootExplorer from my phone system.
So, the new script should as below. Please help to verify and let me know whether this is correct.
Thanks in advance.
UNRoot
======
echo off
cls
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo Rebooting (1/3) - Continue once device finishes rebooting
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo Rebooting (2/3) - Continue once device finishes rebooting
pause
adb shell id
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
pause
adb remount
adb shell rm /system/xbin/su
adb shell rm /system/xbin/busybox
adb shell rm /system/xbin/Superuser.apk
adb shell rm /system/xbin/RootExplorer.apk
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo Rebooting (3/3) - You should now be UNRooted
pause
echo on
rayxware said:
Hi sparkym3,
I'm not able to reply your post "[ROOT] TPSparkyRoot - ICS' so I created a new post here.
I had successfully rooted my Star N8000 phone using the below script with busybox, Superuser and RootExplorer installed.
Root
====
echo off
cls
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo Rebooting (1/3) - Continue once device finishes rebooting
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo Rebooting (2/3) - Continue once device finishes rebooting
pause
adb shell id
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
pause
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
adb push RootExplorer.apk /system/app/RootExplorer.apk
adb shell chown 0.0 /system/app/RootExplorer.apk
adb shell chmod 0644 /system/app/RootExplorer.apk
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo Rebooting (3/3) - You should now be Rooted
pause
echo on
***My question is if I want to unroot my Star N8000 phone, I will need to remove the su, busybox, Superuser and RootExplorer from my phone system.
So, the new script should as below. Please help to verify and let me know whether this is correct.
Thanks in advance.
UNRoot
======
echo off
cls
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo Rebooting (1/3) - Continue once device finishes rebooting
pause
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo Rebooting (2/3) - Continue once device finishes rebooting
pause
adb shell id
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
pause
adb remount
adb shell rm /system/xbin/su
adb shell rm /system/xbin/busybox
adb shell rm /system/xbin/Superuser.apk
adb shell rm /system/xbin/RootExplorer.apk
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo Rebooting (3/3) - You should now be UNRooted
pause
echo on
Click to expand...
Click to collapse
This is doing way to much extra while unrooting. Since you would already have root by this point, you can just call su to do all the removes and then remove su last. This can be done from adb or any root file explorer like es file explorer (which will also allow you to mount the file system).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
HOW TO DUMP SAMSUNG FACORY ROM USING ADB
MUST BE ROOTED WITH BUSYBOX INSTALLED
1. You must have Android SDK https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
2. Your Devices USB Driver package installed
3. USB DEBUGGING On Your device needs to be Enabled. go to settings > about device> and tap Build Number 5 times and you will see you are now a developer. go back to settings Select Devloper options> usb debugging.
4. After you install busybox to your device. Use Root browser on your device and go to Data>local and long press on busybox to change the permisions select all of them.
Now we are Ready to start
C:\android\platform-tools>adb devices
List of devices attached
42007ffad33453a9 device
C:\android\platform-tools>adb shell
[email protected]:/ $ cd /sdcard OR
[email protected]:/ $ cd /storage/2082-08E3 < What my ext sdcard is named yours maybe different
1|[email protected]:/sdcard $ su
[email protected]:/storage/emulated/0 # chmod 755 /data/local/busybox
THEN
/data/local/busybox tar cvf Samsung.tar /system <
tar: removing leading '/' from member names
HERE'S A COPY OF MINE JUST INCASE YOUR HAVING PROBLEMS
C:\android\platform-tools>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ chmod 755 /data/local/busybox
chmod: chmod '/data/local/busybox' to 100755: Permission denied
1|[email protected]:/sdcard $ chmod 755 /data/local/busybox
chmod: chmod '/data/local/busybox' to 100755: Permission denied
1|[email protected]:/sdcard $ su
[email protected]:/storage/emulated/0 # chmod 755 /data/local/busybox
/data/local/busybox tar cvf Samsung.tar /system <
tar: removing leading '/' from member names