oh, and I do delete the error log each time I try.
saw the post regarding that and have done it each time.
saw the post regarding that and have done it each time.
i am doing pretty good until i get to Install /sdcard/update.zip
the error code i get is
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E: can't mount sdcard.update.zip
installation aborted
i have read through your fei, and faq. i have selected all the correct settings i have uninstalled and replaced the update.zip file (via drag and drop cant understand the adb yet) several times. please help --jp
@travelingp: I have been following this thread and there have been just a few with your problem. <snip>
Another solution would be to manually install su, busybox, and superuser.apk but that pretty much requires adb shell to be installed and working on your computer. I have sent MotoCache1 a pm about that final method of finishing off the rooting for those with your problem.
Now, I gotta go through my notes <snip>
Well, MotoCache1 never did answer my pm, I don't blame him, he's probably getting a ton of them these days with all the coOl things he's done, but I still wanted to post the 'manual' solution. As I posted previously, you need to have adb (Android SDK) installed and working on your system. I will not go into those details here, but a quick google search will get you all the info you need to do so.
That being said, this info and the way I may post it is probably not geared towards total n00bs, so please be aware of that fact. If you do not understand some of my steps, more research will help you to gain said understanding.
Alright. The condition of your phone needs to be such that it is currenty booted into the SPRecovery menu. If not, follow the guide until you are there.
Now, on your computer, go ahead and extract the "MotoCache1_Complete_Root_v1.1-update.zip" file. Once extracted and you're in it's main folder, you will see three more folders, the only one we're concerned with is the "system" folder. Now within that folder, you'll see three more folders (pay attention as it will start to make a ton of sense later), "app", "bin" and "xbin". What you need to do is take _only_ the files contained _within_ each of these folders and put them into your android 'tools' folder (i.e. for a PC, the same place that adb.exe resides). Do NOT copy the folders. To be more specific, you will be copying files named 'Superuser.apk', 'su', and 'busybox'. Hope that's clear enough.
Now, let's plug your phone into your computer and then on a windows box open a command prompt. On a linux box open your terminal. Do a test by typing "adb devices". If you get a number, you're golden. If you get a message saying "device not found" STOP!! You don't have adb setup properly and you'll need to go back and get it right. Now for the rest.
On the phone, within the SPRecovery menu, go to 'mount options', then select 'Mount system' (it's the top one). Now the rest is a bunch of commands (these are VERY specific as to capitalization, spacing, and punctuation, pay close attention):
Code:adb shell mkdir /system/xbin exit adb push Superuser.apk /system/app adb push su /system/bin adb push busybox /system/xbin adb shell chmod 6755 /system/bin/su cd /system/xbin chmod 755 busybox busybox --install . sync mv /system/recovery-from-boot.p /system/recovery-from-boot.p.not exit
You can now close your command prompt (or terminal on Linux). Now select "Unmount system" within the SPRecovery menu, then using the power button go back until you get the reboot phone option and do so. Oh yeah, you can now unplug your phone from your computer as well.
You won't notice much difference, as in MotoCache1's OP, look for the signs that you're rooted, you should be . . .
Oh yeah, now that you've got the rooting process done, time to look into what's wrong with your sd card.
good luck
rebooted the computer twice, still no luck. I gave RSD Lite 5 minutes each time to pickup my deviceAre you still using the ERIS?
EDIT: My bad, I see in you are now on the DROID. haha
If you're running as an admin, then that is strange. I'd say give the tried and true "reboot your computer" a shot.