Database Info

Samsung Behold 2 Rooting

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

Superuser 2.3

Anyone manage to install it successfully without losing root. If so, how?

No, same problem, pushed the 2.3 apk to apps, after that not in launcher anymore and root completely gone.
Messed around for 2 hours now with X10root.apk, the runme batch file and at last manually. Don't know which method actually did it, but after final reboot I got rooted again and Superuser was visible again in Launcher.
I think the Donut Version of Superuser 2.3 is a fail, got 2.2 now, I think from Angelos pack but not sure.

Yeah, that's my experience too. The root .apk fixed it up for me again.

I've heard that the superuser 2.3 asks for permission for everything on the phone, is that correct?

Why would one need to upgrade to what most have using the root method? I see no reason to change whats already working fine and giving root. People never realise that newer versions dont always mean better!!!!!!!!!!!!!

Works a treat
You have to remove the old Superuser.apk from /system/app/
Then add the latest Superuser.apk along with the "su" supplied using adb:
Code:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push apps\Superuser.apk /sdcard/Superuser.apk
@adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
@adb shell chmod 644 /system/app/Superuser.apk
@adb push bin\su /sdcard/su
@adb shell dd if=/sdcard/su of=/system/bin/su
@adb shell chmod 4755 /system/bin/su
@adb shell rm /sdcard/su
@adb shell rm /sdcard/Superuser.apk

MarylandCookie said:
Works a treat
You have to remove the old Superuser.apk from /system/app/
Then add the latest Superuser.apk along with the "su" supplied using adb:
Code:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push apps\Superuser.apk /sdcard/Superuser.apk
@adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
@adb shell chmod 644 /system/app/Superuser.apk
@adb push bin\su /sdcard/su
@adb shell dd if=/sdcard/su of=/system/bin/su
@adb shell chmod 4755 /system/bin/su
@adb shell rm /sdcard/su
@adb shell rm /sdcard/Superuser.apk
Click to expand...
Click to collapse
Thanks mate!

Force closes on mine on opening the app.. Though works when pop up appears for permision..

realunited123 said:
Force closes on mine on opening the app.. Though works when pop up appears for permision..
Click to expand...
Click to collapse
This also happens on my phone.

Did the same for me. Rebooted, it was fine (did it on both my x10 and nexus).
Removing the old superuser app and pushing the new one works. Thanks guys.

Can i use a terminal / file manager on X10 to copy the apk and sh binary (ofcourse after mounting rw) ?
Or i have to use "dd"?

What are the new features found in the Superuser 2.3?

2.3.1 is out and works no more FC....

yup! works fine now

MarylandCookie said:
Works a treat
You have to remove the old Superuser.apk from /system/app/
Then add the latest Superuser.apk along with the "su" supplied using adb:
Code:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push apps\Superuser.apk /sdcard/Superuser.apk
@adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
@adb shell chmod 644 /system/app/Superuser.apk
@adb push bin\su /sdcard/su
@adb shell dd if=/sdcard/su of=/system/bin/su
@adb shell chmod 4755 /system/bin/su
@adb shell rm /sdcard/su
@adb shell rm /sdcard/Superuser.apk
Click to expand...
Click to collapse
Could you please tell me how to do this?
Do i have just to open my sdk on my pc and insert the comand you wrote?
I'm tryng to understand how to remove superuser from the phone because i have a X10 and X10mini, and i've a problem with the second phone and this apk.
When i downloaded from the market a new version (2.3.6.1) of this programm, all went fine with my X10.
With X10 mini, when i try to download from market superuser, i can finish to downloading this apk, but phone dosen't install it.
A messagge appear sayng the package is not signed.
So maybe i thought it could depends from older version that's installed on X10 mini. Am i doing right removing the old version for installing new one? Or mine is another kind of issue?
And in general, is this still the right method (and the only one) to remove superuser.apk from Xperia phones?
Thanks

thank you!

I am a G3's user
MarylandCookie said:
Works a treat
You have to remove the old Superuser.apk from /system/app/
Then add the latest Superuser.apk along with the "su" supplied using adb:
Code:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push apps\Superuser.apk /sdcard/Superuser.apk
@adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
@adb shell chmod 644 /system/app/Superuser.apk
@adb push bin\su /sdcard/su
@adb shell dd if=/sdcard/su of=/system/bin/su
@adb shell chmod 4755 /system/bin/su
@adb shell rm /sdcard/su
@adb shell rm /sdcard/Superuser.apk
Click to expand...
Click to collapse
I can see the new superuser in the phone,but it can't work.I use g3,can you help me?
thanks!

instigator008 said:
Anyone manage to install it successfully without losing root. If so, how?
Click to expand...
Click to collapse
Market updated me to 2.3.6.1, Titanium still runs, so still rooted.

need help to make a rom kitchen for sg3

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.

Android 2.2/2.3 stock,Flash recovery without unlocking bootloader (GRJ22 Nexus One)

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!

[Q] adb push- why am I getting permission denied?

phone: LG esteem ms910
Rooted: Yes
I'm trying to adb push a .apk file into my phones /system/app folder. These are the steps I am taking in trying to do this, but I am getting a permission denied response at the "adb push" part. Oh and my phone is under the "internet connection" setting. The other two (mass storage, charge only) wont let my phone enter debugging mode.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push C:\Myfile.apk /system/app
Also when I enter the "mount -o remount,rw /dev/block/stl9 /system" command, It pops up twice but without the # symbol, not sure if there is an error there but it ends up looking like this:
Code:
C:\Android\android-sdk\platform-tool>adb shell
$ su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
C:\Android\android-sdk\platform-tool>

I think you would want it to be on charge only, as the other options are utilizing the USB while charge only does not. That is how my setup functions... I did have the permission denied error before when I was using Ubuntu 10.04. Are you sure you have an up to date version of JDK? And the USB rules?

your command should be
adb push C:\Myfile.apk /system/app/myfile.apk
you have also to run adb as root or enable rw for /system/app
Basically:
______________________________________________
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
exit
exit
adb push C:\Myfile.apk /system/app/myfile.apk
________________________________________________
should do the job

@imheroldman- I tried leaving it on charge only, but the devices wasnt found when I ran the adb devices command, and yes the JDK is the latest.
@djodjoni -Hey I tried your suggestions and it worked.
Thanks to the both of you for helping.

FWIW, I got permission denied errors when I tried to push busybox via adb. I just downloaded a busybox .zip and flashed it via TWRP, it seems to have worked, and the busybox app recognizes it as installed.

I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why

kavinzhao said:
I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why
Click to expand...
Click to collapse
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard

ИΘΘK¡€ said:
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard
Click to expand...
Click to collapse
Thanks. I was using the recovery to receive before this. I think that should save me some time.

hello, I am having same problem, can you please help me out?
[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/temp
adb push C:\firewater /data/local/temp
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/
adb push C:\firewater /data/local/
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/l
adb push C:\firewater /data/l
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/data/local # cd ..
cd ..
[email protected]_himaulatt:/data # cd ..
cd ..
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb push C:\firewater /data/local/temp
failed to copy 'C:\firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb shell
[email protected]_himaulatt:/ $ su
su
[email protected]_himaulatt:/ # mount -o rw,remount rootfs/
mount -o rw,remount rootfs/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_himaulatt:/ # mount -o rw,remount rootfs /
mount -o rw,remount rootfs /
[email protected]_himaulatt:/ # chmod 777 /sdcard
chmod 777 /sdcard
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>

Make sure you have phone detected and correct drivers and adb installed.
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the phone. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe
once you have moved the apk to the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push myfile.apk /system/app/
adb shell chmod 644 /system/app/myfile.apk
adb reboot[/FONT]
adb remount mounts the phone as read write so you can write thru adb, it will be automatically unmounted when phone disconnected or rebooted
assuming your APK you want moved is called "myfile.apk"
adb push file_myfile.apk /system/app/ this command moves the "myfile.apk" (the apk you want moved) to the /system/app/ directory on your phone
adb shell chmod 644 /system/app/myfile.apk this command sets the correct file permissions for APKs
adb reboot this reboots the phone so that the new apk can be detected
Good luck

hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.

opalescent said:
hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.
Click to expand...
Click to collapse
sounds like you possibly do not have proper permission for the user you are logged into your computers operating system with. make sure you have the proper permissions and rights to access the folders you are trying to access. For a quick fix you can try loging into the system using the root user or administrator of the system that you are using and then try the adb commands. and you can just do a quick su switch from the Computer OS's konsole/terminal.

XeoNoX said:
First you need to make sure the apk you want to push is in the same directory as adb.exe
Click to expand...
Click to collapse
OMG thanks, mine wasn't working because something as simple as that!