Database Users

is this the right way to root?

adb devices
adb push asroot2 /data/local
adb shell chmood 0755 /data/local/asroot2
adb shell
$ /data/local/asroot /system/bin/sh
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero)
$ cd /system/bin
$cat sh > su
$ chmod 4775 su (or 4755?)
$exit
adb push recovery-RA-heroc-v1.2.3.img
adb shell
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home?
is this how to do it? help please

Code:
adb devices
adb push asroot2 /data/local
adb push recovery-RA-heroc-v1.2.3.img /data/local
adb shell
Code:
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system
cd /system/bin
cat sh > su
chmod 4755 su
flash_image recovery /data/local/recovery-RA-heroc-v1.2.3.img
reboot recovery
corrected some stuff for ya make sure asroot2 and recovery-RA-heroc-v1.2.3.img is in same directory as adb.exe
and that's good to go
UPDATE: no longer requires a sd card to root + recovery image + made copy/pasteable

fullgrown said:
adb devices
adb push asroot2 /data/local
adb shell chmood 0755 /data/local/asroot2
adb shell
$ /data/local/asroot /system/bin/sh
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero)
$ cd /system/bin
$cat sh > su
$ chmod 4775 su (or 4755?)
$exit
adb push recovery-RA-heroc-v1.2.3.img
adb shell
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home?
is this how to do it? help please
Click to expand...
Click to collapse
Up to the exit is the rooting part, yes. After that you can shell in and type "su" and have root access.
The rest of it is installing a custom recovery image.

thank you!!! now i'm rooted!!!

[Q] Root 2.2 318 without ADBshell

Hi,
a pin of my USB connector is broken so I cannot get a USB data connection to a PC (but charging still works ...).
How can I root the official 318 build of froyo ? More specifically, in the new build, there doesn't seem to be any mounted filesystem on which one can copy RATC to run it.
Any hint welcome.

Have you already tried superoneclick, androot, or z4root? If so, then maybe try the below.
I don't know if this will work but you can try fard's instructions to root manually and use "Terminal Emulator" from Market instead of ADB SHELL, but i don't know what will happen when you run rageinthecage~ You will need to change the instruction a bit for your case.
http://forum.xda-developers.com/showthread.php?t=844966&highlight=rageagainstthecage
Instructions:
1. Copy all the needed files (from fards thread) into the SDCARD.
2. run Terminal Emulator
3. cd /sdcard/
4. busybox cp rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
5. busybox cp Superuser.apk /data/local/tmp/Superuser.apk
6. busybox cp su /data/local/tmp/su
7. busybox cp busybox /data/local/tmp/busybox
8. chmod 700 /data/local/tmp/rageagainstthecage
9. chmod 700 /data/local/tmp/busybox
10. cd /data/local/tmp
11. ./rageagainstthecage
12. Reset Terminal
13. Start Terminal Emulator again
14. mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
15. follow the rest of the instructions below "mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system "
In case you can't find it in the thread, here is the original post by fards:
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

Well...
yes, I have tried all that.
The main problem with the last option (i.e. CLI) is that the directory /data/local/tmp/ is not user writable (actually /data permissions are 751). So I was in search of a another directory (in an executable partition) where I can copy rageagainstthecage-arm5.bin.
Finally found it : "find" was my friend. /firstboot/sqlite/jackpal.androidterm/ is owned by my user (ID 10123)! It's the only one I found in all the filesystems!
Note that "find" is available through /system/bin/busybox_1P8P1. Btw /firstboot/sqlite/jackpal.androidterm/ seems to be linked to the terminal process.
Ran rageagainstthecage-arm5.bin various times to no avail ! It didn't give me root!

[Guide] Rooting Fascinate and Installing CWM using a MAC

So I posted a question yesterday to see if anyone could instruct me on how to root my phone using a MAC, no PC AT ALL. And then install CWM w/o having to use ODIN, b/c I do not have a PC. Well after some researching on my own I found out how and here is how I did it.
To root: Follow this thread (it requires using adb commands)
http://forum.androidcentral.com/ver...s/34188-rooting-using-mac-video-tutorial.html
To install CWM reference this thread, but here are the steps. You must download and install ROM Manager from market and also download zimage file. This also requires adb commands.
http://forum.xda-developers.com/showthread.php?t=804248
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redbend_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
I know this is vague, but if you know what you are doing and reference the threads you should have no problem. Let me know if you have any questions.

Official update to 1.82.405.1 stock ROM (from 1.72..) and root

Hi there,
I tried if it is possible root on stock ROM 1.82.405.1 on HTC Desire Z. YES, we can!
This is a little "how to" with all previous roots and updates from "1.34.." to actual 1.82.405.1 stock ROM:
Permanent root on HTC ESIRE Z using linux
Software No. 1.34...
Necessary files:
adb (Android SDK)
gfree_02
psneuter
Terminal emulator (Android)
Optional files:
gfree_verify
Settings on Phone:
Menu-Settings-Applications-Development-USB debugging [yop]
USB connected to PC – only charge (card not mounted to PC)
Procedure on PC:
Check your device is properly conneted:
$ ./adb devices
It has to be like this : SH0BFRT00451 device
Than continue:
$ ./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/*
On Android:
Launch Terminal Emulator
$ /data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Procedure on PC:
$ ./adb push gfree /data/local
On Android:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
# /data/local/tmp/root
# sync
there can be some errors with directory create – it is ok.
update to 1.72 via system and do following again:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
Superusere error is patchable by this:
http://forum.xda-developers.com/showthread.php?t=886999
check /sys/devices/system/cpu/cpu0/cpufreq/current_scaling_freq​

But do we need to be already on 1.82++ or do we need to downgrade to 1.34++ because I don't really understand what we have to do!
PS: really really thank you!!!!! (all other root methods failed for me, so fingers crossed that this one will work!)

You need to have S-OFF; if you don't you need to go to 1.34 to get it, then upgrade back up the chain...

oh, thanks... I guess I'll have to downgrade then, wouldn't I

I guess so, but should only have to do it once...
Sent from my HTC Vision using XDA App

I rooted my 1.72 device a while ago with this tut: http://forum.xda-developers.com/showthread.php?t=905261
Should I be fine by just executing the latest part off this tut?
Code:
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....

I got error:
E:signature verification failed
I'm using clockwork recovery 2.5.1.3. I think that's the reason, anyone got a fix for this?

hi, I have desire Z with bootloader 1.82.405.1 , from which stage should I start the rooting process?

Rooting with busybox can brick with this method?

I am trying to Root the new Arc but I don't want to brick it in any way.
Someone posted this method and I want to know if there are any risk:
push the busybox binary to /data/local/tmp/:
adb push busybox /data/local/tmp/
change permission to execute:
adb shell "chmod 755 /data/local/tmp/busybox"
then enter adb shell and type following commands:
cd /data/local/tmp/
mount -o remount,rw -t yaffs2 `mount | busybox grep /system| busybox awk '{print $1}'` /system