Serious Rooting problem!! - Droid X General

I am no noob when it comes to rooting- I've had my D1 and Incredible both rooted manually.
However, I'm having some serious problems rooting the DroidX...
I have all the drivers and ADB software installed. This is the 3rd computer i've tried this on and i've been receiving the same errors.
Droid X
Froyo 2.2
1) when i try to adb push exploid to /sqlite_stmt_journals/exploid - i received an error message that says that there is no such file or directory.
instead i adb pushed exploid to /data/local/tmp - and went on from there.
2) I'm able to run ./exploid and even get to the rootshell- but then when i try to cp /sdcard/Superuser.apk /system/app/Superuser.apk - an error occurs that says /sdcard/Superuser.apk is a directory (not copied)
3) I also tried running the 1-click root for the DX - and it fails every time.
I'm completely stuck. Any ideas?

The Answer
To problems one: Where are you getting your information on how to root the X?
To problem two: Did you remember to mount the system to read-write (rw)? And to problem three: Try using this instead, if your on the official OTA of 2.2 FroYo, GO HERE!!!
The link above is what you need and it is the first post on the page.
Good Luck
-Cameron
*edit*
Apparently I'm not allowed to post links...
rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
*end*

got it
yeah i forgot to mount the system- started getting "read-only" errors- the rooting instructions that i was reading seemed to have left that out... :-/

Related

[Q] Rooted w/ Unrevoked, .apk files still read-only

I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
BR3W CITY said:
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
Click to expand...
Click to collapse
To test that you are infact rooted, please do the following:
1. Open command prompt/shell
2. cd into your AndroidSDK directory
3. Issue the command:: adb shell (if you see the # mark, then you are rooted -- otherwise type, su.)
To answer your questions:
1. When your phone says its "read-only file system"; this means that you need to issue the adb remount command; this will remount the system as RW (read/write), at which point you can go on deleting any apps you no longer want.
2. If you still have S-ON, that means you did not run the Unrevoked FOREVER file. You've only ran the Unrevoked 3 file. Notice when going to the Unrevoked site, that there are two different downloads.
3. Clockworkmod/superuser will exist because you are rooted and the process was successful.
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
n/m, didn't read previous post properly
BR3W CITY said:
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
Click to expand...
Click to collapse
What kind of phone? Some phones won't reliably mount the system partition read-write while running in normal mode. You should be able to do it from the clockwork recovery system though.
htc desire on 2.1, from USCC. I have not yet tried to do it from clockwork yet. I will try that later
Thanks!
Thanks for the help, putting her into ClockwordMod and using it to Mount /system solved the problem. Stock crap is gone yay!

I have Unknown Sources Enabled now

This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
Earlier today, I wrote instructions on how to root the flipside. Now, I have Unknown Sources enabled. Here's how you can do it.
First, if you don't have root, follow these directions:
http://forum.xda-developers.com/showpost.php?p=9702394&postcount=4
Next, you will need to run a script, but for the script to work you will need to install busybox to your rooted flipside. You can either get it from the market, or download it somewhere on the web. I tried installing it from the market, but it just timed out on download for some reason.
Once you have busybox, you have an environment ready for enabling Unknown Sources. Lets do it:
Latest version installs busybox for you]
I have not tested it, so you may still need to tell it to install, but it installs the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
run_second.sh
i get errors when i attempt to run your run_second
though for the life of me... i can't figure out what's wrong with it?
What error do you get?
on all 4 of the cp commands... i get a return of
cp: (destination directory): Invalid argument
EDIT: tried the run.sh script... got an invalid file/folder error on the mount... on one of the cp's... and on the chmod of the same
EDIT: i manually edited the 2 files in the system directory using notepad++ and droid explorer...
couldn't find the 2 databases anywhere on the phone? hidden?
Odd. I did this:
Code:
ls /data/data/com.motorola.android.providers.settings/databases
and I get this back:
Code:
settings.db
The only time I cannot do that is if I don't have super user.
DOH! just realized the issue. once you type "SU", go to your phone, and tell it to allow application "unknown" super user.
Forgot about that part.
well... here's one for you then... i have nothing in my /data/ directory...
never did...
EDIT: wait... droid explorer lied to me... now if i could just get into that file... i could hard change them without having to deal with all the scripting
script typo
Thanks for the script. I have managed to enable it by following your script.
However there are a few typo in your script that caused errors. I have corrected them. You may check attached script.
jonsjava said:
What error do you get?
Click to expand...
Click to collapse
I get an error when I exicute run.sh
: No such file or directory
monho said:
I get an error when I exicute run.sh
: No such file or directory
Click to expand...
Click to collapse
Did you install busybox? Please, run through what you have done so far. My goal is to get a comprehensive how-to together, and any and all input I can get will assist me to that end.
i'm getting read only file errors on the script now... i assume some file attributes need adjusting... not sure how to do that...
Did you remount /system/ in rw mode, as mentioned in the walkthrough? /system is read only by default, but part of my how-to explains how to re-mount it in read/write
all 5 chmod statements return no file found....
EDIT: even reboot is no found
that sounds like you don't have super user, or busybox isn't installed.
i have super user access... i used z4root... this also installs busybox... or so i'm told...
rignfool said:
i have super user access... i used z4root... this also installs busybox... or so i'm told...
Click to expand...
Click to collapse
That does not install busybox. As stated in my how-to, you will need to either download busybox from the market, or get it from the web.
I know it says it does, but I didn't have busybox features until I installed it manually myself.
root explorer FTW
so... after using root explorer to manually edit the mkitso files... and copy the databases from the /ab/ directory....
i made it work...
Hallo there. Please I would appreciate if you can help me. When you say:
1.Look for the one that says "/system". Mine says "/dev/block/mtdblock7"
- Mine says the same too, is that right? Could it be different? Why sould we care where it says 'system'?
2.'type this in (changing the /dev/ as needed)':
-When you say 'as needed' that means changing the /dev/ is not neccesary? What does ir depends? If it's neccesary, what should I type instead of /dev/?
3. 'Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock7 /system'
-Must that line be typed exactly as it's shown? I've done so and after running the commands:
cd /sdcard/
sh run.sh
-This error message appears:
No such file or directory
I've rooted with z4. I've already installed BusyBox from the market, altought I can see it's not an app that appears like the others: I've just got an Icon named 'busyBox Installer' and after all it says 'busybox is successfully installed'.
Please excuse my bad english and thank you very much in advance for your help
1. I wrote it that way just in case it was different anywhere else. It shouldn't be.
2. when I said "change /dev/..." It was in reference to 1. above
If /system is /dev/block/mtdblock7 as listed, you don't need to change it.
If /system is /dev/block/mtdblock21 (example), you would need to change my command to read:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock21 /system
That's what I mean when I said change /dev as needed. Seeing how yours is the same as mine, that is not necessary.
3. the command to mount /system will not affect the sdcard. Make sure the /sdcard isn't mounted on your computer. In windows, look in "My Computer", or your languages equivelant, and if you see the phone there, right click and tell it to unmount. Wait a few seconds for the phone to access the SD card, and try again.
so, I too have problems running run.sh
I tried both the one in the original post and the typo fix in the other post. Both didn't work. I get file not found errors.
Yeah, I have z4root done and busybox installed no problem.
For some reason it's not seeing the files when I run run.sh.
Here's a copy paste just to prove what I am seeing:
Unable to chmod /system/etc/motorola/com.android.providers.settings/secure.mkitso
: No such file or directory
Unable to chmod /system/etc/motorola/com.android.providers.settings/system.mkitso
: No such file or directory
I verified that my sdcard has /ab/ folder copied over, and all the subfolders and files from the original archive are moved over.
What gives?

G2 Rooting Problem

Hey all,
I would like to know, what I might have done wrong in the rooting process. I used
This Tutorial hxxp://g2hacks.com/g2-hacks/how-to-root-g2-phone/
I made it to step #18 and was stopped by this error:
Code:
/data/local/tmp/root: data/local/tmp/busybox: not found
/data/local/tmp/root: data/local/tmp/busybox: not found
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Ideas?
Thanks,
Danny
Here is a screenshot of what I pushed to the phone:
hxxp://i.imgur.com/No1id.jpg
You have a typo in your push command for busybox (you renamed it to root instead, which then got overwritten when you pushed root). Just push busybox again.
How do I back out and enter that push command again?
What would I type?
I'm a total novice.
On your comp, just type the command again:
Code:
adb push G2TempRoot/busybox /data/local/tmp/busybox
Then on your phone, in Terminal, just run the root command again:
Code:
/data/local/tmp/root
It should complete this time.
I made a mess. Check it:
hxxp://i.imgur.com/y3NRW.jpg
You are still in the adb shell (basically creates a terminal on your phone that you can interact with on your computer).
Type "exit" to leave the shell. This will return you to the regular command prompt (instead of the $). Then try the push command again.
So now the phone terminal gives me this:
Code:
/data/local/tmp/busybox: permission denied
Oh sorry, forgot you needed to set permissions on the file. Run this command again from your computer:
Code:
adb shell chmod 0755 /data/local/tmp/*
Then it should all work fine.
The errors are getting shorter
Now I get this:
Code:
mkdir failed for /system/xbin, File exists
This error doesn't matter (it's really more of a warning in this case) and is actually expected.
You should actually be rooted if you didn't see anything else.
AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?
Danny.B said:
AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?
Click to expand...
Click to collapse
Congrats! And there are a few threads about this that you can read through (just search for them). If you like HTC Sense (the interface HTC adds to a lot of their phones---basically lots nice visuals and extra polish to things), you can try Virtuous. If you like the stock look that the G2 comes with, there is a stock DEODEX rom out there. By de-odexing the rom, you can do things like customize the framework (e.g., customize the status bar icons/colors or add a battery percentage to it). Lots of people here (myself included), use CyanogenMod. It's close to stock but with lots of tweaks/extras (it's based on the Android Open Source Project or AOSP). It's also nice because it has frequent updates and constant development (they recently started pushing test builds that are based on Gingerbread---the new Android update only available on Nexus S).
Now that you are rooted though, it's easy enough to install Rom Manager and test them all out. Be sure to create a backup first as well.
ROM Manager installed. I'm backed up.
Thanks again for your help.
i cant flash the engineering hboot keep getting error md5sum : not found Verification of hboot-eng.img failed i re-download the files, re-extracted them to my SD card, and ran the flash_hboot script 3x still nothing plz help but im rooted and backed up
Did not want to create a new thread so I'm posting it here.
First off, I haven't tried rooting any of my phones previously so I'm obviously making a mistake somewhere.Hope someone here can help me out.
I installed visionary+ r14 but it just blacked out the screen with a heading.I've read elsewhere that it has all to do with the new firmware updates.My update for the DZ seems to be country a specific one and came out a couple of weeks back.
Anyway,
I tried this visionary method a few times but the phone just hung and I had to go to the homescreen and uninstall Visionary and reboot to get the phone to run smoothly again.
Then I read another way of rooting the thing and it took me here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
After a couple of tries I was able to push the files to the DZ but got stuck at this command:
adb shell chmod 0755 /data/local/tmp/*
The error it gives me is:
Unable to chmod /data/local/tmp/sqlite3: operation not permitted
Strange thing is, yesterday at the same point it gave me the same error but it was 'busybox' instead of sqlite3 and right before that it was something else.Which should mean that those earlier commands were run successfully by the terminal.
P.S. Debugging mode is on.Visionary is uninstalled. followed all the steps mentioned in the guide.
Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.
mohitanfield said:
Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.
Click to expand...
Click to collapse
It looks like you are trying to root a DZ with a firmeware version >= 1.72.
If yes to have to downgrade it to 1.34 first.
See either the instructions here: http://forum.xda-developers.com/showthread.php?t=905261 or the more comprehensive at http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
But if your CID is other then the ones stated in the the first thread you need a goldcard to downgrade first, which is also described in the first thread.
have fun - Guhl
Thanks a lot for your reply and as is the case, my phones CID is HTC_38 which does not seem to be downgradable without a gold card.
I read the procedure and although its well explained, it will take a bit of time.
Will try it sometime soon hopefully, although I wish someone would just make a simple rooting app for the newer versions!
It took us month without sleep to create the existing rooting tools. So I do not see any simple rooting tools on the horizon

- exec '/system/bin/sh' failed: No such file or directory (2) -

I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
rydinsmoothx said:
I am running the cm7 rom but last night I installed busybox and ran the v6 supercharger script. Now my wifi no longer works. I tried to install the new version of cm7 but I get this error when i try to access dab shell.
adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is it possible to fix this? if not what is the easiest way to return to stock and start over. Thank you.
Click to expand...
Click to collapse
Not gonna happen unless you can get into recovery or have the special usb cable to throw your device into fastboot (search the unbricking thread for more information on that). If you get lucky and can fix it + revert to stock, I would not install cm7 again until doing so is more noob friendly and forgiving.
The issues people are having with installing cm7 and severely screwing up their kindle are pretty epidemic due to the issues with recovery for those that don't prepare ahead of time for the possibility of disaster. The maintainer should really either close it out for now to the public or make the disclaimer much larger.
I have the same error. This is end. Only Factory Cable can help you but even with this cable I'm not sure what you can restore it.
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
rydinsmoothx said:
i can still operate the kindle fire. I'm looking in /system/bin folder and it appears i am missing the sh file. if i replace it can i gain dab shell access again? if this is possible where can i get the sh file?
Click to expand...
Click to collapse
Operate how? Also, please don't double post in 2 threads.
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
rydinsmoothx said:
My bad . It boots into cm7. I'm missing the sh file for some reason. Wifi also stopped working and Some apps don't work. This Happened after i used v6 supercharger. My goal is to go back to stock but I can't access adb shell.
Click to expand...
Click to collapse
Could be a bit more explicit. Boots as in "yay, i see a logo and can't use my device beyond a paperweight that displays the cm7 logo" or boots as in "yay, i can use my device like normal and it's not bricked or malfunctioning"
Anyways, if you actually have root privileges and can mount system in read/write, get the sh binary out of the CM7 download by unzipping it or whatever and copy it over, making sure to match the owner/group and permissions that the other things in the /system/bin directory have. Since I'm guessing you're not command line savvy, I recommend doing this in root explorer or buying it if you do not have it.
Also, many of us do not own kindles and a larger % are also not running cm7 on their kindle so saying "i ran some random script that I won't say what it does and where I found it" does not help your situation either as far as getting a helpful answer.
Can you type ADB DEVICES at your command line and get a device? What about fastboot? Can you get devices to show there while at the command line?If yes, I am sure you can flash the CWM recovery to get ADB, then follow the steps to get back to stock...Dont blame me though if it doesnt work
I got the script script from someone in the cm7 thread, its supposed to opitimize the ram usage thus making the rom more smooth. He said it worked for him so I gave it a shot. I think it unrooted my kindle because I can't gain root access with root explorer. My devices shows up in adb devices but since I can't use adb shell I can't enable the fast boot.

Very Hard Time Rooting

Ok let me start off by saying i totally understand the importance of doing research on here to finding the answer but i have had no luck. Recently just got a T-Mobile LG G2 4.2.2. Trying to root using the one click root process (root windows batch). Halfway through i get a...
Mounting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su/ to '/system/xbin/su' : Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superusuer
So it just installs superuser but i know im not fully rooted. Ive searched for a fix and seen similar problems but they were for HTC phones and i know the process is different. I would greatly appreciate any help.
Run as administrator and make sure you have the most up-to-date one click root
datechnerd said:
Run as administrator and make sure you have the most up-to-date one click root
Click to expand...
Click to collapse
Running as admin closes the exe. and the one click root is the most recent
I assume ioroot16 then?
try the manual method here http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Day 2 and im still getting the same error message. Uninstalled ADB drivers and reinstalled. Tried IORoot 15 and 16. Also tried to manually push adb on my pc but it runs then quits. I've tried to research this for hours now and still no luck Does anyone have a proper work around for TMo version? Process seems very easy but for some reason i can not get passed this
davewave91 said:
Day 2 and im still getting the same error message. Uninstalled ADB drivers and reinstalled. Tried IORoot 15 and 16. Also tried to manually push adb on my pc but it runs then quits. I've tried to research this for hours now and still no luck Does anyone have a proper work around for TMo version? Process seems very easy but for some reason i can not get passed this
Click to expand...
Click to collapse
Not sure what steps you are following, but xda is pretty much in agreement that this thread is the best one to follow the steps to gain root without complications
http://forum.xda-developers.com/showthread.php?t=2448887
thats the thread that i have been researching. I've followed every step. the only complication that comes is at the end to finally attempt root process and mount. thats when i get the error messages that i listed above

Categories

Resources