Related
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
bullpen7979 said:
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
Click to expand...
Click to collapse
you can push adb when the phone is connected as a camera. To connect it via ptp, you just scroll down your notifications bar and click on the usb notification, you can switch to ptp there. But like i said, adb works when connected as a camera device, so you are doing something incorrectly with adb. Possibly the commands you are running. The OS for your computer might be causing the problem (but that would mean oyu have the wrong stuff downloaded to adb with the computer set up you are using). You don't have the correct drivers. You are using a faulty data cable. you are using a usb 3.0 port that isn't compatible. it is an endless list. Also, you can copy stuff to your device in camera mode as well.
also would like to note that whether you phone is rooted or not has nothing to do with your ability to use adb or push files to your phone.
finally, this is a question which should go under q&a not the general discussion subforum.
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
so whats the problem. you have adb working. What do you mean you can't copy things to the phone. What error do you get when you try to push a file to the sdcard on the phone? You see your phone in the list of devices so you can put files on it that way too. Really confused at your dilemma.
you trying to root? you trying to push files to the phone? IDK, but you clearly should be able to push them if you have adb running. Perhaps you aren't running the right commands to push files to your phone.
Don't you have to have USB debugging on?
Sent from my XT1060 using Tapatalk
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Click to expand...
Click to collapse
Unless you have another android device connected to your computer, your X has USB Debugging mode turned on, and Windows & ADB properly sees your phone.
As jayboyyyy posted, in this state you can use ADB to push files from the PC to phone, or pull files from the phone onto the PC, assuming you are using the right commands. But if all you are looking to do is copy files back and forth, this is overkill as you can do it with windows. ADB is usually only need for hacking and flashing your phone.
As I said in the other thread... Please include what you were doing and what the results are. You haven't given us a complete enough of a picture to understand 1. what you are trying to do. 2. Any/all steps you have taken. 3. EXACT error message you are receiving.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader. But your second paragraph starts saying you can't get the thing rooted to save you life.. So which is it? Are you rooted or trying to root? If you are trying to root, what process are you trying to follow? What step in that process are you stuck at? What did you type and what did you get back?
I know you are probably frustrated, but its just as frustrating on this side when you don't give a complete picture that allows us to help you. Look, rooting and hacking isn't easy. It can even result in turning your phone into a paper weight. So these details are important so we don't screw things up and add to the headaches and frustrations.
bullpen7979 said:
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
I'm not sure what you are doing, or trying to do, as you said in the first post that you unlocked the boot loader and rooted.
The Moto X wont show as a drive letter in "My Computer." Even if USB Debugging is on, it should show up as a "Media" device, or Player type device with an icon in a separate section from your hard drives, DVD drive, mapped network drives, or even USB memory sticks/flash drives. It does this because the X supports/uses MTP/PTP, and NOT USB MASS STORAGE MODE.
MTP/PTP wont show a drive letter in My Computer. This is by design. You don't have to "stop" or "eject" the phone from windows when you are done. This mode also allows the phone to access the "storage" or emulated "SD" partition at the same time a connected Computer can.
USB Mass Storage mode will give you a drive letter in My Computer, IF the phone supported it. However the X doesn't, at least not out of the box, and I'm unaware of any app or hack to enable this. In USB Mass Storage mode, the PHONE looses access its storage partition or emulated internal SD card while the PC is connected. You'd need to "stop" or "eject" the device when you want to disconnect form the PC in order to prevent data corruption of the "emulated SD"
So again, its important for us to know exactly what you are trying to do.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader.
Im sorry I was unclear. Bootloader is unlocked, but I am not rooted. What I said was that I had another thread about getting it rooted.
I'm sorry for the mis-speak. And I'm sorry I'm being such a pain, but others in the thread I'm referencing are clearly having the same issue I am. I just need to know what to do to obtain root access if my bootloader is already unlocked. To be clear, I do NOT have root access.
This is my procedure.
Start with this link:
http://forum.xda-developers.com/showthread.php?t=2509676
Download Cydia Impactor. Check.
Download RockMyMoto.zip attachement. Unzip two files to directory x. Check.
Download PuTTYtel file "puttytel.exe" Check.
Step one. I have my ip address. At bottom of wireless config on phone, it is 10.59.1.6. So far so good.
I run adb shell getprop dhcp.wlan0.ipaddress just to be sure. same ip addy. Good.
I start command window. push the two files to the phone. all is well.
Step two i open the puttytel window and proceed to run the exploit
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
and I can't run the damn thing because i get PuTTytel Fatal Error
Network Error: connection timed out.
exactly like this dude: http://dl.xda-developers.com/attach...f04a/5290120c/2/3/8/1/6/0/9/1384014224630.jpg
The end. I read the rest of the thread, and post #22 is the first of about five other posts that mentions the same time out problem, a solution for which is NEVER ADDRESSED, except indirectly as a possibility that the the two devices are not on the same network. My wireless card is on dhcp and the phone is the IP address above.
that's where it stops. I can't run the exploit because i can't type the command fast enough. Several people mention this problem, but I read all SIX pages of the thread and this defect is experienced my many and adressed by nobody.
This is driving me stark raving Bat S#!+ crazy.
And yes I have USB debugging on.
If your boot loader is already unlocked, there is another process.
https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Is the process and while I think that twrp version should work, you might need the older version. Had to take my mom to the hospital so not in a good position to find older if newer doesn't work.
EDIT: this thread -> http://forum.xda-developers.com/showthread.php?t=2536200 has some discussion too
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:
No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure
26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct
dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X
dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!
I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app
i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
So recently I reinstalled ADB after a computer wipe due to a virus. And when doing so I had done something to where in Device Manager, I saw two "Android Composite ADB Interface"s in Device Manager. ADB was working. Very confused, I tried lots of things and eventually I got it working. Later I decided to get back to that position and experiment.
First of all, without ADB enabled in the device settings, you are allowed to view device contents in This PC like any normal device. I decided to try if I could get THOSE drivers and install them instead of one of the two listed devices in Device Manager. I extracted the drivers using DriverExtractor to my desktop. Then I turned on ADB in my Kindle Settings and still saw the two listings. I picked one and updated it using the extracted drivers. It succesfully updated, showing MTP Device or something similar, then auto updated to "Fire".
Then ADB worked still, AND I could see my device in This PC and view its contents.
Obviously its not meant to happen, but it works, and I want to know if this is a common thing to be done that I've just not heard of yet? Is there anything wrong with this?
Having a fire hd 7 sucks becuase no one ever posts or answer questions...
If you see this please at least comment or let me know that this post is not invisible. Thank you