Quote:
Originally Posted by bilfdoffle
Great guide. I'm all rooted now, only problem is I can't boot into recovery mode - It' gets stuck at the icon with the exclamation point. Normal boot works fine. I have superuser priveleges (checked by typing su into terminal).
the ./rage command didnt' work the first time, but worked fine the second time. I also accidentally pushed the rage.bin to /data/local/tmp\ , so now theres a tmp\ directory (in addition to the normal tmp directory). Found a forum with a few other people having similar problems, but no solution that worked.
I started with verizon froyo.
Was hoping to load a custom rom - Any ideas?
|
you need to flash a custom recovery. Rom Manager will do it for you.
Quote:
Originally Posted by RDKamikaze
Technically after installing the ADB and such, couldn't you just make a batch file to do the work for you?
Example (has pauses and confirmations in noted places from original tut):
Code:
@echo off
echo If any part of this batch file fails or goes against comments listed, log where you are and exit the batch file immediately.
pause
cd C:\android-sdk-windows\tools
adb devices
echo This should list a device as a long number under list of devices. If it doesnt something is wrong.
pause
adb push c:\droidroot\rageagainstthecage-arm5.bin /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
echo This next step can take a minute, just let it go until you are returned to your adb tools folder.
pause
./rageagainstthecage-arm5.bin
pause
adb devices
adb shell
echo You should now see a # instead of a $
pause
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
exit
adb push c:\droidroot\Superuser.apk /system/app
adb push c:\droidroot\su /system/bin
adb push c:\droidroot\busybox /system/bin
adb shell
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
echo Note if you are on a build earlier than froyo this next step will fail. That is fine and expected.
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.disabled
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
rm /data/local/tmp/rageagainstthecage-arm5.bin
echo I would suggest rebooting your phone but its not required.
pause
exit
EDIT: If you guys like this idea then I can make a command-based yes/no style batch file (prettier version) or even a VBscript that does all the work and just asks simple prompts (such as continue? Y/N, directory for ADB, etc.). What do you all think? Yeah? Rooting made a shade easier? 
EDIT#2: Why is step #15 exit? Won't that just close cmd?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
a batch file would be great. would eliminate the possibility for mistyped commands.
Step 15 is exit to get out of abd shell and back to the regular command prompt. You cant adb push when in shell.
edit: The only possible issue I see with this would be step 5. If someone has adb in a different directory this wouldnt work.
edit again: nm I noticed you covered that