Hi,
I want to root my phone and I just tried it with superoneclick. I followed the guide posted in the faq which explains all that with cmd.exe, but it still won't work, superoneclick is stuck at "waiting for device". Does anyone know how I can root my phone? My phone is running official GB 2.3.3 V20e.
THanks in advance
Look at step 1c here:
http://forum.xda-developers.com/showpost.php?p=15309588&postcount=2
That's exactly the one I used ... However, whenever I typed in the things in cmd, it said "List of devices attached" (for the first one), and after that it just said "the system couldn't find ..." So what did I do wrong?
Thanks
Do you have the usb drivers installed? If not, check this out:
http://forum.xda-developers.com/showpost.php?p=15960064&postcount=3
Also check to see if you have usb debugging under settings>applications>development.
Reedddd said:
That's exactly the one I used ... However, whenever I typed in the things in cmd, it said "List of devices attached" (for the first one), and after that it just said "the system couldn't find ..." So what did I do wrong?
Thanks
Click to expand...
Click to collapse
Is it Showing some numbers after saying list of devices attached... if no then it couldn't find your device..
make sure you have usb debugging enabled and have installed lg United drivers..
Sent from my LG-P500 using xda premium
to root gb 2.3.3 follow http://forum.xda-developers.com/showthread.php?t=1200167
works perfectly
Reedddd said:
That's exactly the one I used ... However, whenever I typed in the things in cmd, it said "List of devices attached" (for the first one), and after that it just said "the system couldn't find ..." So what did I do wrong?
Thanks
Click to expand...
Click to collapse
dude when you see list of device attached and waiting
go to settings>>application>>development
check debugging mode and you are done
follow rest of ur rooting process
Related
1: get SuperOneClick from its original thread if you don't already have it. Latest version is 1.5.5, but most versions seem to work fine.
2: Delete the "rageagainstthecage" file (no filename extension).
3: get psneuter.zip from the Xperia X8 Android Development forum thread.
4: Unzip it. Rename "psneuter" to "rageagainstthecage" (no filename extension), and move it to your SuperOneClick folder, to replace the rageagainstthecage file you deleted in step 2.
5: run SuperOneClick. Mine rooted without looping.
6: reboot your phone. Test your shiny new root!
Remember to put your phone in debugging mode, etc. Someone in the X8 thread claims that X10 Mini can be rooted via this method; I don't have a Mini so I don't know for sure. But I've got a Mini Pro and it just worked.
Update:
The file you need in Step 3 is "psneuter", not "psneuter.c". psneuter.c is the source file for psneuter. You can ignore it.
donetus says that if you have problems with Titanium Backup (even after step 6!), uninstall it, reboot, and reinstall Titanium. This appears to have worked for several users.
Amey006 says that s/he had to install drivers from the Sony Ericsson PC Companion for SuperOneClick to move past "waiting for device". I had PC Companion already installed when I did mine, so I don't know whether the process works without PC Companion... if you don't have PC Companion, you can get it here.
Update 03-2011:
The latest version of SuperOneClick now includes psneuter; you no longer need to follow the steps above. Just use SuperOneClick!
Mine doesnt root. I followed all the steps.
Can u please give a detailed procedure.
Thanks.
Hi, I just registered to give my thanks.
Now I test it and confirm if it works, but of course thank you very much
Thanks
----------------------------------------------------
EXCELLENT! It worked without problems tested in mini Xperia (E10i - E10A)
Thank you very much!
Amey006 said:
Mine doesnt root. I followed all the steps.
Can u please give a detailed procedure.
Thanks.
Click to expand...
Click to collapse
What happens when you try
porcupineadvocate said:
What happens when you try
Click to expand...
Click to collapse
SuperOneClick gets stuck at waiting for device.
I tried the usb debugging enable disable also.....
Still no success.
I have an U20i india.
Amey006 said:
SuperOneClick gets stuck at waiting for device.
I tried the usb debugging enable disable also.....
Still no success.
I have an U20i india.
Click to expand...
Click to collapse
Does your phone say that it is connected? Try another USB port?
ADB will say "waiting for device" because SuperOneClick tells it to wait until a device is connected; if it says "waiting for device", ADB isn't seeing your phone at all.
porcupineadvocate said:
Does your phone say that it is connected? Try another USB port?
ADB will say "waiting for device" because SuperOneClick tells it to wait until a device is connected; if it says "waiting for device", ADB isn't seeing your phone at all.
Click to expand...
Click to collapse
Yes my phone says it is connected.
The usb debugging and usb flash symbol come up on my status bar.
After the message waiting for device the applicaton (SOC) stops responding.
I changed my usb port too.
Helpppppppppppp....................
Victor18 said:
Hi, I just registered to give my thanks.
Now I test it and confirm if it works, but of course thank you very much
Thanks
----------------------------------------------------
EXCELLENT! It worked without problems tested in mini Xperia (E10i - E10A)
Thank you very much!
Click to expand...
Click to collapse
Which file did u take ????? psneuter or psneuter.c ?????/
Can u please guide me ???
Help. Thanks.
psneuter, not psneuter.c
Amey006 said:
Yes my phone says it is connected.
The usb debugging and usb flash symbol come up on my status bar.
After the message waiting for device the applicaton (SOC) stops responding.
I changed my usb port too.
Helpppppppppppp....................
Click to expand...
Click to collapse
Follow the instructions here, namely this bit:
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
porcupineadvocate said:
psneuter, not psneuter.c
Click to expand...
Click to collapse
Can you please give a detailed guide ????
please.please.please.......
Does it need java ???
I have done almost everything. Restarted my phone and pc but still stuck at waiting for device.
Installed java too and also edited system environment variables.
Still no root.
I have SOC 1.5.5
porcupineadvocate said:
Follow the instructions here, namely this bit:
Click to expand...
Click to collapse
Thanks. But i will try it again tomorrow. Thanks for your help.
Works like a charm. Thank you very much
worked on my tiny x10 mini =) tnx a lot
thank you so much
had root -> SE update last week -> no root
Hi all,
I had rooted my x10 mini pro with the z4root tool before. Last week ran a SE update that unrooted my device and also installed back all the crapware.
The z4 root tool doesn't work no more.. it stays on the 'busy rooting' notice forever.
Then I tried the here mentioned method with SuperOneClick with with replaced pseudo file etc..
The program say it has rooted and the superuser app appears in the drawer. However Titanium and Root explorer apps do not have SU accress..
What can I try? I used superoneclick v. 1.5
cheers
vmonk said:
Hi all,
I had rooted my x10 mini pro with the z4root tool before. Last week ran a SE update that unrooted my device and also installed back all the crapware.
The z4 root tool doesn't work no more.. it stays on the 'busy rooting' notice forever.
Then I tried the here mentioned method with SuperOneClick with with replaced pseudo file etc..
The program say it has rooted and the superuser app appears in the drawer. However Titanium and Root explorer apps do not have SU accress..
What can I try? I used superoneclick v. 1.5
cheers
Click to expand...
Click to collapse
You have to reboot your device..!!
Hi.
It work´s on a mini-pro???
Thanks.
works like a charm without looping, thank you very much!
well done ...great job
Tried out both these sets of instructions:
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
http://www.androidauthority.com/atrix-4g-android-2-3-6-firmware-4-5-141-root-63533/
None of them since I can't even get past step one with the command lines. The command prompt won't recognize either saying "[name] is not recognized as an internal or external command, operable program, or batch file.
When I rooted while I was using 2.3.4, I had no issues doing it manually this way. I'm at my wits end. Don't know if it's a problem on my end or just the result of Motorola intentionally trying to make it hard to root and unlock this phone(apparently rooting also voids the warranty with them).
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
moto-fastboot.exe flash preinstall preinstall.img
Click to expand...
Click to collapse
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
octahedron said:
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
Click to expand...
Click to collapse
Did you try just fastboot instead of moto-fastboot? I had to use fastboot the other day and that held me up. But if its waiting for devices then it possibly is a driver issue. Im on the xda app so going to the link you provided wont work for me. Trying uninstalling and reinstalling the drivers.
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
octahedron said:
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
Click to expand...
Click to collapse
Go to device management of the computer and under usb should be your phone (when plugged in). If you aren't seeing it, then the drivers didn't install correctly. I can't remember where I got my drivers from to point you in the direction for that.
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Just to clarify the one I'm referring to is "Motorola ADB Interface". "MB860" has everything current on it.
octahedron said:
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Click to expand...
Click to collapse
When I get on my computer, ill see if I still have all the drivers that I dl. If so will ul to dropbox and post.
Ok this is what I have. Don't know what is what so included what I've got.
http://db.tt/jKixEKQL
http://db.tt/QmpO0ZUx
http://db.tt/CEu1k5q5
The description will pop up with each download. Hope it helps.
Thanks for the help!
I went back to an old bookmark I had when I rooted with 2.3.4 and found drivers. For some reason the motohelper link in my second post in this topic was not helpful. Here's a link for future reference in case anyone needs it:
http://db.tt/XHjBBnGh
I got my phone rooted again and now that I know that works I'll probably go ahead and try unlocking my bootloader to install cm7
Change question, sorry
i found a thread on thow to install CWM..
Now when i enter fastboot mode and type "adb reboot bootloader" cmd says device not found?
Had that too, I found a post where they say installing PdaNet drivers fix the issue, worked for me. Sorry don't remember which topic it was, use search with Pdanet, device not found, etc.
Edit : "device not found" or "waiting for device" ? My issue was with "waiting for device"
babylonbwoy said:
Had that too, I found a post where they say installing PdaNet drivers fix the issue, worked for me. Sorry don't remember which topic it was, use search with Pdanet, device not found, etc.
Edit : "device not found" or "waiting for device" ? My issue was with "waiting for device"
Click to expand...
Click to collapse
Device not found for me.. ill try to search that
Edit..
where do i search that? is that on this forum or the whole xda?
arcsuser said:
Device not found for me.. ill try to search that
Edit..
where do i search that? is that on this forum or the whole xda?
Click to expand...
Click to collapse
Look here : http://forum.xda-developers.com/showthread.php?p=24284355
Please forgive my ignorance I am very new to this. I just want to flash the new firmware to the nexus 9 manually. I have downloaded minimal adb and fastboot but it doesn't find my device. I have enabled developer mode and allow usb oem ect but nothing when I type the commands it says waiting for device and nothing happens, obviously I am missing something obvious, but if you could please help me out I would be grateful.
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
Not sure what the first question means??, I think I ran the adb commands at the right directory??
anobium said:
Not sure what the first question means??, I think I ran the adb commands at the right directory??
Click to expand...
Click to collapse
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
AjunNg said:
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
Click to expand...
Click to collapse
No never had a popup, asking me toconfirm???.
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
AjunNg said:
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
Click to expand...
Click to collapse
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Use Wugfresh's Nexus toolkit, and use the full driver installation.
anobium said:
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Click to expand...
Click to collapse
Right click on it. Go to where it lets you pick from a list on your computer. Choose android adb interface driver, or something along those lines
Sent from my Nexus 9 using XDA Free mobile app
AjunNg said:
Use Wugfresh's Nexus toolkit, and use the full driver installation.
Click to expand...
Click to collapse
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
No root needed to update.
anobium said:
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
Click to expand...
Click to collapse
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Migamix said:
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i get to flashing the image and it goes to quick and comes up with errors saying I have different firmware image on my device?, I thought that was the idea im going from lrx21r to lrx22c, do I have to put I already have the 22c in the option list??.
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
there is nothing wrong with ADB, or fastboot, if you use it exclusively, good for you.
as the OP title sais, it is not expected for a new user, and even some experienced users, to have such a firm grasp of the ways of the mighty command line, and the fact that the toolkit gathers all of the files in one convenient place, is not without its bonus. i dont know, nor do i really care who started the whole elitist "toolboxes are for lamers", or whatever. toolboxes are nothing more than their name suggests , tool-boxes, to help when we need it. they are nothing more than an interface to commands, much like you running a GUI on top of your OS, or are also running command line only for your primary computer. xda, is designed and expected to be help for all who want to know, not a pond of elitists that would rather brag they have overclocked their device, water cooled it, but can still make a grilled cheese sandwich on their CPU. i have email accounts older than many of the forum members here, so not too much impresses me in that 1337 area. im here to help if i can, and learn if i need to., so since im here alot, im always learning.
Please start this thread
Here:
http://forum.xda-developers.com/m4-aqua/development/bl-locked-twrp-touch-recovery-bl-locked-t3257430
http://forum.xda-developers.com/m4-aqua/development/root-xm4aqua-e2303-bolek-t3340399
well, I'm looking for rooting this phone, and this isn't of any help. The first guide linked requires an already rooted phone. The second one isn't for the E2333 I own but for E2303 instead, and it sends me back to the first guide.
marchrius said:
well, I'm looking for rooting this phone, and this isn't of any help. The first guide linked requires an already rooted phone.
Click to expand...
Click to collapse
NOT TRUE !!! Read carefully there are steps to root phone.
On page 17 there are updated links
http://forum.xda-developers.com/m4-aqua/development/bl-locked-twrp-touch-recovery-bl-locked-t3257430/page17
Here you have link: http://www60.zippyshare.com/v/Wk6bArMJ/file.html
BOLEK_PL said:
NOT TRUE !!! Read carefully there are steps to root phone.
On page 17 there are updated links
http://forum.xda-developers.com/m4-aqua/development/bl-locked-twrp-touch-recovery-bl-locked-t3257430/page17
Here you have link: http://www60.zippyshare.com/v/Wk6bArMJ/file.html
Click to expand...
Click to collapse
Exactly, what I have to do to have an "adb environment" in windows 8?
marchrius said:
Exactly, what I have to do to have an "adb environment" in windows 8?
Click to expand...
Click to collapse
You need this: http://www73.zippyshare.com/v/0A8vqmsQ/file.html
BOLEK_PL said:
You need this: http://www73.zippyshare.com/v/0A8vqmsQ/file.html
Click to expand...
Click to collapse
Mate, you're very kind, but even after installing it, when I run the install.bat to root my phone, it gets stuck at "daemon started successfully". Then it does nothing, no prompts on phone either.
marchrius said:
Mate, you're very kind, but even after installing it, when I run the install.bat to root my phone, it gets stuck at "daemon started successfully". Then it does nothing, no prompts on phone either.
Click to expand...
Click to collapse
You enable USB Debugging
Yes, but for some reason I have not got the prompt on my phone asking for allowing it on my PC until now. I installed some adb drivers on PC then rebooted then got the prompt so maybe it was a drivers issue.
Anyway, what I did for rooting my E2333... I downgraded to 27.1.B.1.85 with xperifirm (for downloading the firmware) and flashtool (for flashing it). On xperifirm choose to download the firmware for commercial and journalists, then flashtool is very straight forward, if you need help look for a guide, and remember that when you connect the phone to PC it has to be turned off and you have to hold the "volume down" button while you insert the usb cable on PC. Flashtool will ask something about a fsc thing or something while flashing, just say yes. The first boot will take a while.
Then just use the rootkit provided by Bolek PL. remember to activate debug usb.
hash67899 said:
Please start this thread
Click to expand...
Click to collapse
Since this thread is for an issue already found in the forums it will be closed as being a duplicate.
If you have the same issue please use the existing threads.
Thread closed.