Database Users

{Behold 2 }[How-to] Root for App's working with Persistent root

First off, I want to say thanks to Kam187 & the Creators of asroot
Okay, Below is the Method I used for getting Root working for my app's.
Even though Shell is running as Root, any Call's made to su trigger's the white List Superuser.apk, So don't think your phone is wide open. G1's & MT3G Setup's are the same regard sh.
I'm not sure is the apk is counted as warez or not, if so I hope a Mod will remove the link to the Apk or let me know to Remove it...
Okay, File's Need to complete the Task is....
Try3 Placed in C:\SDK\tools> found here > File's attached below
SU for /system/bin found here > File's attached below
Superuser app control for our App's found Here > File's attached below
Next, Mount the SDCARD and place the SU file in the root of the sdcard like so ( /sdcard ). This is Important!!!
From here we do the Following.. ( Kam187 script the I edited ).
adb push try3 /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 > /system/bin/su1
cat /sdcard/su > /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 /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
Click to expand...
Click to collapse
Once Done, place the Superuser.apk in your SDK tools Directory.
Mine happens to look like this
C:\SDK\tools>
Click to expand...
Click to collapse
Once you have that Copied over, Open a Command prompt and CD to your sdk\tools directory and type the following.
adb install Superuser.apk
Click to expand...
Click to collapse
Once done, do a reboot of the Phone, Once boot up is complete open a Command Prompt ( or app that needs Root ).
For Command Prompt, type:
adb shell
Click to expand...
Click to collapse
su
Click to expand...
Click to collapse
If done correctly you will now see the deny or allow prompt on the Phone, or just open any app that needs root & you will see the same window.
Here's some Picture of it working
SU working with SU apk on Twitpic & SU working with SU apk on Twitpic

Root Froyo 318

I have upgraded from 309 to 318.......wanting to root it using z4root and universal androot but both apps dont work for this 318 version.....
does anyone have any clues to what i can do? please advise, thanks

Please Do Not Post the Same Question in 2 Forums i will Lock this one as i have answered the other one

Quoted from fards' thread: http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage
Been rooting this way since day 1 -- if you aren't the type in command prompt, you can also just copy and paste the command lines exactly~
GET ECLAIR/FROYO version of Superuser.apk and su
from http://forum.xda-developers.com/showthread.php?t=682828 extract the two files to the directory you're working from..
GET rageagainstthecage from
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
extract the rageagainstthecage-arm5.bin to the same directory you're working from
open a terminal/command line
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 700 /data/local/tmp/rageagainstthecage
adb shell chmod 700 /data/local/tmp/busybox
adb shell
cd /data/local/tmp
./rageagainstthecage
******this will kill adb server but manually kill it anyway and restart it ******
adb kill-server
adb start-server
* daemon not running. starting it now *
* daemon started successfully *
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
**********Follow the following steps to install Superuser.apk, busybox,su ****************
cd /data/local/tmp
./busybox cp busybox /system/bin/
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app/
busybox cp su /system/bin/
chmod 4755 /system/bin/su
exit
exit
then reboot streak
************to remount filesystem as readonly,*************
adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock6 /system
# exit
exit
Click to expand...
Click to collapse

installing su complete but nothing! 2.3.3 9023

hello
After unlocking the bootloader then installing the recovery image
then from the recovery image
i install this file from sdcard su-2.3.6.1-ef-signed.zip
everything run smoothly and i get installation completed
but then when i boot to the device, the Rom Manager tells that there is no su into /system/bin
how to install su correctly ?
i'm on ubuntu with Nexus S 9023
thank you

even market enabler app tell "we got a problem Huston" that means no root applied
i've mounted the /system from recovery mode but nothing seem to activate the su
help please

Do you have /system/app/Superuser.apk ? Otherwise I would try to flash the zip again from recovery.

no doing /adb shell ls /system/app/
i can't find the Superuser.apk there
even i tried to flash the zip files 3 times
and removed the superuser then installed it from market
still not su

solved
ok, now i fixed this problem
extract the (su and Superuser.apk) from su-2.3.6.1-ef-signed.zip to /sdcard
Code:
./adb reboot bootloader
then choose recovery mode
then
Code:
./adb shell
Code:
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su

[TUTORIAL]How to manual root official 2.3

I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.

I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?

Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800

SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?

dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly

don't work.

try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7

Manual method of adbd Insecure

This method is similar to Chainfire's adbd Insecure, I tried Chainfire method, adb wireless didn't work for me, so I made my own, I needed to use adb wireless on some devices.
I made this adbd for my BLU Studio 5.0 C Cell phone, but I am sure it will work for other arm devices.
Anyway long story short, you need a rooted device, you push a script and an adbd file to /system/xbin then you add a line to /etc/install-recovery.sh to load the script each boot.
To install download replace_adbd.zip
extract zip place all three files on sdcard, and use rooted file manager to copy them to to their correct places, or use adb.
adb shell
mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell
chmod 755 /system/xbin/adbd
chmod 755 /system/xbin/adbd-Insecure
chmod 755 /system/etc/install-recovery.sh
reboot
Or use file manager like ES File Explorer File Manager to copy files from sdcard to correct place and set permission then reboot.
https://www.androidfilehost.com/?fid=24052804347763661
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.persist.partition.support=no
[email protected] STUDIO 5.0 C:/ #
credits
@carliv for CarlivScreenshot
http://forum.xda-developers.com/android/development/tool-carlivscreenshot-screenshots-t3075992
@Chainfire for the ideal of making adbd insecure
http://forum.xda-developers.com/showthread.php?t=1687590

Download link didn't sync correctly, file was corrupt first link, I have now changed the link, this one should now work correctly.

Thanks, I will test on my device and report back. I've always wanted some manual way instead of using the app.

@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.

bovirus said:
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
Click to expand...
Click to collapse
Yes, one can use the adbd binary from adb insecure 2.0.apk.
There isn't any version number to check, we both just build the adbd binary from source, mine was built from CM 12.1 source, not sure about chainfire's.
Chainfire's may have used AOSP source.
Yes one can create a Windows batch file, to execute the adb commands, or create a flashable zip, provided the devices has a custom recovery.
Sent from my Venue 8 3830 using Tapatalk