Upgraded to ICS 4.0.4 following Jim's instruction. Got stuck on the rooting step. In windows, the driver could be installed without USB debug turned on. And I can see the phone is mounted. Only when I turned on usb debugging, the driver couldn't not be installed properly and rooting script would freeze at damon started (something like that)
Tried it under Mac too. The phone can't even be recognized. Tried factory reset/reinstall newest driver/reboot millions of times, it just didn't help. The phone still can be seen using adb devices command. But I got the following errors while running the rooting script:
Unable to chmod /data/local/12m/debugfs^M: No such file or directory
Unable to chmod /data/local/12m/su^M: No such file or directory
Unable to chmod /data/local/12m/cmds^M: No such file or directory
failed on '/data/local/12m/batch' - No such file or directory
...
I can still log on to my phone by adb -s command and it turned out I don't have permission to write or list all the phone folders including data. No wonder. There is noway of changing the permission with chmod either since sudo does not work.
I came very close to fxz back to 2.3.6 because of the frustration, but still wanted to give it a final shot. Does anyone have any idea how to get my phone rooted in this case?
Also, not a good idea to re-post in another sub forum, even if it belongs here. Better to have a mod move it. Please re-read the forum's rules that you can find in this thread, along with some good advice for you as a New Member...
http://forum.xda-developers.com/showthread.php?t=1857631
[GUIDE] How To Be A New Member, Not A NØØB
Sent from my fingers to your peepers
This needs to be posted in the thread for the utility you're having issues with. So the developer can help you you. He won't see it here. Have a mod merge you thread into the proper thread and delete this please.
http://forum.xda-developers.com/showthread.php?t=1779968
Sent from my SAMSUNG-SGH-I727 using xda premium
Related
Hey guys. This is my first Android phone, and I'm trying to get ready to root it. I read the steps by toast in thread 690762 (it won't let me post a link due to "new member restrictions") but can't figure out how to do the adb shell commands. I have downloaded the Google SDK, and also eclipse, and am just utterly confused now. I've never really approached a project like this. Any help would be much appreciated.
yeah i had trouble setting it up also. what os are you using, by the way, some people might give u hell about posting this here.
Windows 7. First time posting in these forums, so I apologize in advance to anyone who may be annoyed with me for posting this here, admins may feel free to move this post to a more appropriate section.
in command prompt type
cd/
cd c:/android-sdk/tools
Sent from my Hero CDMA using the XDA mobile application powered by Tapatalk
appreciate the help guys finally got it to work by manully putting adb.exe, adbwinapi.dll, and adbwinusbapi.dll in my windows/system32 folder. took me about 6 hours of googling
thats from my post from a couple days ago, its prolly something with the drivers not being recognized, goto your sdk folder then the tools folder and look for the files and copy and move them to your windows/system32 folder and see if that works. also remember to use administrative access when trying to flash the recovery or really anything. i set mine up to automatically run adb.exe in administrative mode
That did the trick, now stuck on sprint loading animation after flashing stock rooted evo ota update and updated radio image.
Correction: All issues fixed, thanks for your help guys. My EVO is now rooted and running the stock ROM that is rooted with an updated radio.
I have searched google far and wide, found a few cases of similar issues but haven't found a solution yet. Got my T-mobile g2 /DZ about 2 months ago, love the hardware and the form factor, but I cannot stand stock froyo. First of all:
Phone build/firmware (?) number is: 1.22.531.8
Release keys: cl277427
I initially tried rooting the phone with visionary r14, which gave me a temp root, then rebooted when I tried perm-root. Ever since then, the program hangs when trying to even temp root (I have tried visionary r11,12,13, and 14, as well as uninstalling and reinstalling countless times [not to mention downloading from different sources]).
After a bit of searching, decided to try rage method - again it didnt work (terminal emulator > /data/local/tmp/rage - permission denied) no matter how many times I tried it.
Tried rage method with gfree (both .02 and .04), which is where I had the most success. I managed to get s-off, but still no superuser access. The problem occurs when I enter the code /data/local/tmp/root
described in this page: http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF where it tells you how to 'lock in' the root.
After entering the '/data/local/tmp/root' code, I get an error message that reads something like:
mkdir failed for /system/xbin/, File exists
cp: can't stat `/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
I have checked, double-checked, and triple-checked that I have pushed busybox etc correctly, and they definitely write to the folder as I am not getting any error messages in CMD.
I would greatly appreciate anyone who can give me a straight answer as to what to look for (somebody said you can't have a file/folder on SD card called 'su' so I have checked that). This is driving me crazy - I bought the G2 thinking froyo would be so much better than Symbian/Motoblur, but I am really disappointed. Even Launcherpro etc are pretty lame compared to some of the custom roms out there.
Please help me!
Alternatively, seeing as I have s-off, any way to flash a rom without superuser? Sorry for the noob question
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
fajarep said:
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
Click to expand...
Click to collapse
Can you give me a bit more detail? About to try and flash a pre-rooted modaco rom. Will probably have to wipe the phone so if it doesnt work I will try gfree again on the wiped phone
Bumping bump
Anybody?...
Still needing help on this
Hello Everyone,
I have supposedly rooted my new Galaxy Nexus (CDMA) phone. All the apps that request root on the phone are able to get access to it, also if I use "adb shell" and then use the "su" command to switch to root it will grant me access, albeit without ever prompting me on the phone. However when I try to use the "adb root" command from the terminal window it gives me an error of "adbd cannot run as root in production builds".
I need this function to work, but cannot seem to find my way around it. I am not the only one I know who has seen this, but we cannot seem to figure it out. I was hoping to get some suggestions? Any thoughts?
No luck it looks like...will this bumb it?
Why do you need the command "adb root" ?
Mostly for grabbing logs via the logcat command.
Sent from my GNex,
-Originalme8
Why not "adb logcat" ?
Still don't understand why you need the specific "adb root" command.
Does it really matter what my reasons are? Maybe I am worried that there is a problem with my such controller? I just want to know why this command isn't working. If your not going to help, please don't post hand waste my time.
Sent from my GNex,
-Originalme8
you could use adb logcat as mentioned above
http://forum.xda-developers.com/showthread.php?t=833756
forum search, it's magic.
and yes, reasons matter.
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
So you are saying the link i posted, does not contain the answer to your question, although it states what causes the error message and how it can be fixed?
Originalme8 said:
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
Click to expand...
Click to collapse
So you have a "recognized developer" trying to help you out and posting a link to the problem and the fix, and that is how you respond? Good luck on XDA buddy.
Oh, and don't worry, I will hit their thanks button for you.
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Your Kernel is likely stock kernel and will not allow this change if you don't have USB Debugging option available within your ROM.
If you have this option, then enable it. It is possible that you have half root - Unlocked boot loader, but Kernel is from a stock ROM. You can still get shell access. You just won't get it while your System is Mounted if you don't have USB Debugging enabled and you plugged into Windows while your System is running. So Reboot into Recovery, and then go into your ADB Directory and type
adb start-server
adb devices (see if it lists the connected device) if yes then type
adb root (It should say adb is already running as root)
then type
adb shell
you can use the ls command to list all the directories.
cd to change into them. like cd /sdcard then ls and so on.
and cd / to go back.
Look up basic linux shell commands.
and then you can do whatever you want. List of ADB Noob Commands
http://forum.xda-developers.com/showthread.php?t=517874
Hope this helps anyone who got in here from a Google search.
Next time try to be nice to others, and be patient. I spent time trying to help you. As did the other guys. Try to give back.
ocd_amp said:
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Click to expand...
Click to collapse
Terribly sorry for bumping a post this old in advance. I would PM but I am also leaving a reply for people Googling this later on.
I have been searching on how to compile a .prop file for 2 hours now. The most relevant thing I could find online was a tutorial on how to compile my own ROM's but that compiles the whole ROM and seems unrelated to what you said (using Es file manager). Also, I just want to make my Stock rooted ROM debuggable.
Could you direct me to a source or simply explain how I would do that?
Hi Experts,
I am trying to root my phone. I am following below link.
http://forum.xda-developers.com/showthread.php?t=1709424
Below is the error i am getting, i am noob with android. Please help or point me if this is already solved. Thanks for your time.
-------------------------------------------------------------------------
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'magic.sh' to '/data/local/tmp/magic.sh': Permission denied
Unable to chmod /data/local/tmp/magic.sh: No such file or directory
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/system/bin/sh: /data/local/tmp/magic.sh: not found
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
rm failed for /system/app/Superuser.apk, No such file or directory
failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk': Permission denied
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp/magic.sh, No such file or directory
Done! Rebooting...
Press any key to continue . . .
----------------------------------------------------------------------------
Regards,
Pkumar
Do you have USB debugging enabled? Make sure you go into settings>developer options and check to enable debugging. Also make sure your phone is in charge only mode when plugged in. And you'll want to disable fastboot.
Sent from my HTC One X using xda app-developers app
I had the same thing just kept trying moving the date up by two days and it worked for me
Sent from my HTC One XL using xda premium
Hi
I tried updating the date as well, but didn't work. I am following the steps correctly.
USB is debug mode, connected as charge only and disabled fast boot.
Please help.
Thanks
pkumar_s said:
Hi
I tried updating the date as well, but didn't work. I am following the steps correctly.
USB is debug mode, connected as charge only and disabled fast boot.
Please help.
Thanks
Click to expand...
Click to collapse
As per the written instructions in the OP of the root thread, if it doesn't work set your date ahead two days, reboot and try again.
Just keep on trying. When I rooted my phone using this method, it took me 2 tries. Somehow it's different for everyone, but the common thing is that it works for sure. be patient
I was able to root my phone. Thanks for all the replied. I followed step by step guide rather than the one-click one.
Regards,
PKumar
pkumar_s said:
I was able to root my phone. Thanks for all the replied. I followed step by step guide rather than the one-click one.
Regards,
PKumar
Click to expand...
Click to collapse
which step by step guide did you use??
Ok, use the root method in the stickies, in the dev thread ... On the other hand why not do a search for things ? This question has already been answered numerous times.
My "WCX" dominated HTC One X
robertmoore208 said:
Ok, use the root method in the stickies, in the dev thread ... On the other hand why not do a search for things ? This question has already been answered numerous times.
My "WCX" dominated HTC One X
Click to expand...
Click to collapse
first of all in case you did not notice, the question was directed to "pkumar" not you, and second, if you have a problems answering questions that have already been answered, just don't answer. instead of writing crap that took more of your time than if you would have answered my question.
nymikey said:
first of all in case you did not notice, the question was directed to "pkumar" not you, and second, if you have a problems answering questions that have already been answered, just don't answer. instead of writing crap that took more of your time than if you would have answered my question.
Click to expand...
Click to collapse
Hey speed racer .... He asked experts ... I don't see how or why your even talking to me ? And I'm not the only one whom has issues answering already ANSWERED QUESTIONS , XDA DOES !!! mind your own business dude , and I was telling pkumar not you to begin with ...so he avoids a flaming by others in the future
My "WCX" dominated HTC One X
Are we done bickering?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"~Rush
Sent from my HTC One X, using XDA Premium.
Yep, no more out of me ..
My "WCX" dominated HTC One X
mod edit
I am just going to take this down before you brick anyone else's device. What you posted only works for a specific device. Messing around with commands without knowing what your doing almost always leads to a brick.
Where is the tune2fs -j ext4 /dev/block/mmcblk0p1 command and if having any problem jus change the updater script of the Rom and the where ever there is a mention of mounting write mmcblk0p1 in place of that
Additional things u should mention is to use of terminal in windows if ppl have ask installed they should install the required bundles fRom android.com installs the required platforms and then go into platform tools and in a blank space there holding shift there right click and select open cmd here and type adv shell and the required info in the above thread appreciated it work bro nice
Sent from my LG-P920 using xda premium
help me, after i command "reboot" my phone has turned to black screen, i thought it was going to reboot, now i cant even ON my phone,cant even charge and cant even go to bootloader. please help :crying:
Mileading Post
Dude you bricked my phone. Its not turning on after i entered the commands and rebooted the phone (as mentioned by you). What should i do now !
Thread closed
For those of you who who bricked your device I suggest you ask around in your device forums to see if there is any fix around. However, let this be a lesson to you all. Running commands and/or flashing random things to your phone without knowing what you are doing is very dangerous. Best of luck to those of you who bricked your device
Diestarbucks was here!