1 Attachment(s)
Complete How-To Root, Busybox, Flash/Recovery, Framework-res.apk, custom boot ani...
An excellent post has been written on how to use ADB. I recommend people follow that post before attempting my methods.
http://www.droidforums.net/forum/dro...s-options.html
Hello,
I document everything I do and thought I would share the information I have compiled with you all. I have not written these individualy, but rather have used everyones advice in various forums to create a one stop shop tutorial. I cannot remember everyone I have gotten these from, so instead of issuing credit to everyone individually; I will just relinquish credit for myself. :D Enjoy!
- Improve Call Audio Quality
• Dial ##7764726 (##PROGRAM) and act as if you were going to call that number.
• Enter 000000 for the SPC Password and then tap Verify
• Tap on "04 Vocode"
• Tap on EVRC-B than Apply
• The phone should automatically reset a few seconds afterward. If not, power cycle the phone
• Explanation - This changes how the phone compresses and decompressed the call audio which improves the quality.
- Safe Mode
• With the phone off, slide open the keyboard open
• Press and hold the Power+Menu button (on the keyboard)
• Continue to hold until the "Droid Eye" comes up and you feel the phone vibrate
• Phone should start up and say "Safe Mode" in the bottom left-hand corner
• Explanation - This starts only the core Android processes. This is best used for diagnosing if a 3rd party application is causing your phone to malfunction or if you cannot uninstall if when in regular mode.
• TRY THIS FIRST if you are having any problems with your phone acting up, especially with the built-in Android apps (example - Messaging app is crashing. Boot in Safe Mode. If app doesn't crash when doing what you were doing in regular mode, it's most likely going to be a 3rd party app with access to messaging that is causing a problem.)
• BE AWARE that after coming out of Safe Mode, 3rd party widgets might not display properly on the home screen. Press and hold on the widget and drag it down into the trash can, then readd it to the home screen. This will fix the "problem loading widget" error.
________________________________________
Hax
Root (2.0.1 only)
1 - Download the droid-super_user.zip file from: http://alldroid.org/download/file.php?id=659
(md5sum cf653352967253e99d967498ffd9ce69). Do not extract.
2 - Rename the file to "update.zip".
3 - Plug your Droid into your computer via USB. On the Droid go to the Notifications bar and select "USB Connected" then press "Mount".
4 - Once the device is mounted, the SD card will show as a removable device on your computer
5 - Put the "update.zip" file you just renamed into the Root (top) directory of your SD Card.
6 - Unmount the device from your computer, and turn the Droid off.
7 - Hold down the "X" key on the physical keyboard and while doing so press the power button. Hold both of them down until you see a Triangle with an !.
8 - Press the Vol+ and the Camera button together until you get a menu.
9 - Using the D-pad on the physical keyboard, select the option to update with the update.zip file.
10 - This should take a little bit. Once it's done select the option to reboot the phone.
BusyBox
download busybox binary to your adb tools directory
http://www.alldroid.org/download/file.php?id=709
cd to your adb tools directory
adb push busybox /data/local/busybox
adb shell
su
cd /data/local
chmod 755 busybox
./busybox
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mkdir /system/xbin
/data/local/busybox cp /data/local/busybox /system/xbin
/data/local/busybox cp /data/local/busybox /system/bin
cd /system/xbin
busybox --install .
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
reboot
Flash/Recovery image
::NOTE: This is not important atm, since there aren't any roms for us to install. However, once roms start comming out this will be how we get them on the phone. Additionally, I have left my link at 0.08 for stabilty reasons.
Flash Image- http://cyanogen-files.carneeki.net/flash_image.zip
Recovery image-SP Recovery Image with nandroid! | Sholes
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
sync
mount -o remount,r -t yaffs2 /dev/block/mtdblock4 /system
/system/bin/flash_image recovery /sdcard/use the recovery ROM in your sdcard
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.old
sync
mount -o remount,r -t yaffs2 /dev/block/mtdblock4 /system
Disable default Verizon crap
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/app
mv Email.apk Email.bak
mv VVMStub.apk VVMStub.bak
mv com.amazon.mp3.apk com.amazon.mp3.bak
mv CorpCal.apk CorpCal.bak
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
reboot
Change Framework-res.apk
Use your desired framework-res.apk. I have not provided one.
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
mv /system/framework/framework-res.apk /system/framework/framework-res.bak
cd sdcard
busybox cp -R framework-res.apk /system/framework/
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
reboot
Custom Boot Animation ROOT IS NOT REQUIRED!!!
Download desired bootanimation.zip to your adb tools directory.
Code:
adb push bootanimation.zip /data/local
http://img709.imageshack.us/img709/6067/fkaple.gif
Attachment 714
::EDIT:: All scripts have been changed to reflect that the correct system partition is mtdblock4. mtdblock3 is often misqouted as the system partition and this is why.
Quote:
Originally Posted by [EMAIL="humancyborg@alldroid"
humancyborg@alldroid[/EMAIL]]
Simply do "cat /proc/mtd" and it will print a list of mtd's available and in what order, starting with mtdblock0. mtdblock3 was the system partition for the HTC devices which is probably where you copy pasted it from in the first place.
The reason it still works 'flawlessly' is that the command you are typing simply remounts /system ignoring the dev/block part. Please make sure you get this right, as if you tried to mount the wrong block in recovery for example (where /system isn't already mounted) you will do some serious damage. Again, note that the mtd's are different when you boot into recovery and a cat /proc/mtd will tell you the correct order (mtdblock6 is system in recovery).
