I am trying to root my droid and i am getting stuck at this point
here is the time line of events
1. rooted successfully via easy root a really long time ago
2. after an ota update i receive an error when i attempt to reflash the phone or back up the rom anything that requires super user permissions fails saying "permission denied"
here i am now haha
After running RATC, you're not getting root UID (0), and you're staying in adb shell, so it's normal that adb devices command isn't working.
However, the real problem I see here is that RATC isn't working. Are you sure that you're using correct exploit - is RATC working on your FW version? Maybe you have to use psneuter...
sorry could you possibly put that in layman's terms im some what technical but im some what new to android stuff
UPDATE: nvm the above how do i figure the FW version ive looked in the about section of the phone but it doesnt seem to be there whats the best way to obtain the FW version?
I don't own Droid but same principles more or less should be same for all Android phones. So, to simplify it:
Basically, when you execute RATC (rage_against_the_cage) exploit, adb shell should disconnect and you should be thrown back to Windows' CMD prompt and adb shell should get root permissions. But in your case this isn't happening, adb doesn't restart and RATC isn't working.
Can you try with SuperOneClick v.1.6.3?
i was looking at that ill go ahead and try that
still a no go i attached some screen shots
Which Android version have you got? 1.6 or 2.1? Try with psneuter exploit.
i rooted with unRevocked3, on htc. very easy!!!!
Related
Hello I've updated a Xperia Play with the official Update tool by SE, now I have this
Code:
Android version 2.3.3
Kernel 2.6.32.9-perf
I can't use the tools I used for rooting anymore.
I've tried GingerBreak 1.2 and SuperOneClick, but they don't work. Is there any way to root android 2.3.3?
I don't have the same phone as you, but when the G2X had the Gingerbread update SuperOneClick didn't work either... The workaround was to flash CWM and from there flash your own custom ROM that came pre-rooted. Though if you want to keep the stock ROM and root it, I guess you might have to wait for someone to root that..
sorry, whats a CWM? Does flashing require "unlocking" the bootloader? Can that be undone (to not void the warranty when sending the device back)?
Where could I get a 2.3.2 ROM for Xperia Play?
I know this is a guide for my phone but it won't hurt to give it a try since the guide was meant for official gingerbread. Just ignore step one:
http://forum.xda-developers.com/showpost.php?p=15454927&postcount=7
Sent from my LG-P509 using xda premium
Sorry, but that tutorial seems badly written. The author doesnt mention what some lines are.
Allow me to explain:
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf,
Click to expand...
Click to collapse
First adb.exe is not in the top folder, it's in its own folder "ADB".
Okay, you can do it like this instead:
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
ADB\adb devices (after this command you should see your device id)
ADB\adb shell
echo 1 > /data/local/lge_adb.conf,
Click to expand...
Click to collapse
But then theres this comma in the end. Firstly he could just put the code in a [ code ] tag. I assume he put the comma to separate the text, so I didnt write that. I entered the last line in command line and nothing seemed to happen. No error messages either.
Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
Click to expand...
Click to collapse
specifying what he meas by "it" wouldnt hurt, otherwise Im just making assumptions.
And no, it didnt work, I tied toggling USB Debugging with no difference. The superoneclick window is frozen and it's possible I'll break the phone again if I'll stop the process now. Nice...
I have never rooted an android device before and this is my first time. The reason I'm rooting is so I can enable the Virtuous Prime ROM (the guide for Virtuous Prime suggested to use ViperMOD to root first)
[ROOT] [TOOL][Updated 2.22.12]viperMOD PrimeTime v4.5 | Auto Root/Unroot/Busybox/CMW - xda-developers
^I'm following the instructions from the link above word for word. So far I've met the following Criteria:
-Enabled USB Debugging
-Running build 9.4.2.15
-Have "ASUS Android Composite ADB Interface" drivers installed and updated
I downloaded the ViperMOD 4.5 zip and extracted it to my PC. I opened the folder and right clicked on "viperMOD Primer Tool v4.5 - copy.bat". A cmd popped up with several different options; I pressed 1 to root, and pressed enter to skip the following two prompts (that ask if USB debugging is enabled and asus usb drivers are installed).
The CMD then showed the following message:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
However the CMD just stopped there. It didn't show the following flood of text that should show up when rooting w/ ViperMod (like shown in this video: http://www.youtube.com/watch?v=C3OQkxmUyLc at 2:35)
I'm not sure if I'm missing something here. The guide however did say that I needed to "Kill Asus Sync and Splashtop" though I'm not exactly sure what it means by "kill". I don't have Splashtop running on my Prime nor Splashtop remote running on my PC. I also don't have ASUS Sync software installed on my PC and I disabled Auto-Sync on my Prime (HOWEVER, the ASUS Sync icon is still visible in my Prime's notification bar when I connect it via USB to my PC).
Any advice?
I had a similar problem
I tried to use superoneclick to root my Samsung Gravity and it hung on waiting for phone. I used the adb commands to load the zergRush exploit. So you need to find which exploit works on your phone, adb push the exploit, busybox, and su to your phone and use adb shell to do the root.
** DISCLAIMER: I'm pulling this command sequence out of my memory... you should find a better guide but this stuff may give you clues as to what to google for, or if you're familiar with shell you may see the gist of what you're trying to do **
The commands will look something like this:
adb push exploitfilename
adb push busybox.apk
adb push su
adb shell
chmod 755 exploitfilename
./exploitfilename
(wait for the exploit to finish)
pm install busybox.apk
pm install su.apk
reboot
Once it rebooted, I installed terminal through the market so I could do cool stuf like so:
su
mount -o remount,rw /dev/whateverdevhasyoursystemfolder /system
rm /system/app/Vendorgarbagebloatapp.apk
and so forth. Knowledge of linux and shell commands is your friend here for sure. Basically, you should know what you're doing or don't do it. I'm no fan of one-clicks for anything like this, it's too hard to figure out what went wrong if it goes wrong, plus this way you can learn new skills.
Can't seem to run Vipermod
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
sasori563 said:
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
Click to expand...
Click to collapse
U should tried on another comp with windows seven imo
I would if i had one but my laptop got stolen so my only computer besides my desktop is my transformer, Are their any .bat files out their that i can use to run it from? I found out that its a problem with windows 8 not allowing .exe files to open command prompts, but if its a .bat file it will run.
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?
Questions should be posted in Q&A (Questions & Answers) Section.
I assume you're running the script as Administrator? Also, I'm not sure what you're getting at with the drivers not being able to install if the phone is in debugging mode. It has nothing to do with the phone, you just download the latest drivers and install to your PC, then enable debugging on the phone, connect via USB, and run the script as Administrator...
Sent from my fingers to your peepers
Hi everyone, I've been doing a good bit of googling and found nothing yet, so if this has been asked before I'm very sorry but I haven't yet seen anyone on the forum with the exact same issue. I actually updated to JB OTA when I first got the device in Canada (US version), when I got back to the UK I decided to root, but then found out that you can't on JB, luckily I managed to downgrade to ICS V9.4.5.30 downloaded from the ASUS website! I was not able to downgrade to an earlier version however, stock recovery wouldn't allow it so NVFLASH root method is out the window... Now I would prefer not to unlock my bootloader for now.
When running debugfs.bin 1 click root method, on my desktop (not run as admin) it says:
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
'find" is not a recognized as an internal or external command, operable program or batch file.
Less than half a second later it just closes down.
When run as admin, it does the same thing and instead of closing down it goes back to the first screen where you can select what method you want to use.
On my netbook it runs and just stops at daemon started successfully, the tablet has no response and debugfs just stays on that screen till I close it down.
Both my computers have all the correct drivers and the latest version of debugfs running, both are windows 7 Ultimate 64-bit.
Please help me as my Infinity is just sitting around doing nothing as when I downgraded to ICS all 190 apps I installed were wiped too, and obviously there's no point me reinstalling any apps till I get this bad boy rooted...
Many thanks in advance!
Make sure you're connecting to a USB 2.0 port, not 3.0, on your computer.
Try not to use any intervening USB hub.
Try to make sure that you're using the back ports on a desktop machine as sometimes the front ports and be a bit sketchy.
Reboot both tablet and computer before starting, and as always, make sure the tablet has USB debugging enabled.
only my netbook has usb 3.0 and I used the 2.0 port, I will now try the back ports of my desktop, I didn't use any extensions or usb hubs, I have debugging and unknown sources checked. I have tried the restarting already, which I'll do right now again... thanks though..
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Android SDK and Java DK were not installed, just installed them still exactly the same issue, haven't rebooted since installing them though
Is there a way I could use Linux to root, as I do have Linux Mint running?
johnlgalt said:
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Click to expand...
Click to collapse
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
johnlgalt said:
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
Click to expand...
Click to collapse
Thanks so much anyway! I've already tried that file, it's exactly the same
Yeah, it looked very similar, but it included more things in the actual Download like the drivers.
Not sure why it is not working - can you run those three commands in a command prompt window and see what you get?
well they say 3's a magic number, computer number 3 worked! For some reason something on my desktop and netbook was causing the root to fail, now I'm updating to jb ota... Thanks for the quick responses otherwise I would have assumed the problem was with the tablet and not my machines...
Glad you got it working. Quite possibly an antivirus program, firewall, or other such problem.
I am running Win7-64 and was attempting to root my TF700T on 4.21. I had a devil of a time with ADB errors when trying to root with Motochopper. In particular, I dealt with "**daemon still not running Error: cannot connect to daemon" despite the fact that the ADB would recognize my device.
This appears to be an error of ADB instances getting in one another's way by running multiple instances. After trying ADBfix (which did not work for me), I placed the Motochopper files in my "Program Files (x86)\Asus\Asus Sync" directory with the ADB.exe that comes with the install package. This caused only one ADB instance to run, and my root with Motochopper was successful and error free.
Took awhile to get here, so hopefully I can save folks some time. Good luck to you!