Database Develop

[ROM] Adeo v0.2 (REDUX) for Atrix 4G

***MOD EDIT***
THIS ROM ONLY WORKS ON 4.1.26. Please consider another ROM unless you know what you are doing.
History & IntroThe first version was done with 3 different batch files, it ended up being very hacky and even ended up bricking one phone because the cleanup script didn't properly work.
I have rebuilt it from the ground up as a shell script. The initial temp root and file push is done with a batch file, it then fires off the install script on the phone which reports back to the batch with helpful info about what it is doing and what to expect from the phone as it goes. You no longer have to accept any superuser requests either.
The new script has been used on tons of phones now, everything executed exactly as I expected it to. I really didn't want to post this until we had a stock firmware to restore to, after the first release I have been worried about you guys bricking your devices, but what the hell, here it is anyways.
Come chat with us!​FeaturesWorks for rooted and non-rooted devices
Deodexed
Reboot Option
Reboot to Recovery option
Ad Blocking
Removed power options header​ChangelogAdeo v0.2: (3/9/2011)
Added Unknown Sources checkbox
Added Preferred install location (internal, sdcard, let system decide)​Adeo v0.1: (2/28/2011)
Reboot to Recovery option
Ad Blocking
Only remove app/framework Dalvik-Cache (fixes /data app issues)
Removed power options header​Four simple rulesDo NOT do a factory reset if something goes wrong(soft brick), you will lose adb access and have a pretty brick
Do NOT do this if you are not familiar with ADB, if you softbrick you need to use adb to fix it
DO NOT PULL THE BATTERY, EVER WHILE INSTALLING
BE PATIENT​How to Install
Read the four rules above
Read the four rules above, again
Read the four rules above, again, one more time to make sure you've got it
Download the installer (AdeoInstallerv0.1.7z, AdeoUpdaterv0.2.7z)
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
DisclaimerIf you brick your device, I cannot be held responsible. Simply restore with the stock SBF to get you phone working again.​Video Walkthru

Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks

A custom ROM?
I'm going to have to buy an Atrix!
EDIT: Bought it!
EDIT2: And Adeo'd it. All UI lag is gone! This is awesome!

I am running this in my Atrix now - I believe my phone was the 4th phone to have this install perfectly on with no issues. Designgears, you are the man, once again! Thank you for this!

PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...

Installed on mine, worked flawlessly. Thanks!

connexion2005 said:
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Click to expand...
Click to collapse
Haha, I understand your PM now... you got my file before I posted this.
psufan5 said:
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
Click to expand...
Click to collapse
the factory reset is only if you brick.
There is no easy way to get back to stock, I will make a thing just like this installer to do that, actually its done, testing it

designgears said:
Haha, I understand your PM now... you got my file before I posted this.
the factory reset is only if you brick.
Click to expand...
Click to collapse
So if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because Im still debating if I want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but I also need to test out custom mods before my decision.
Thanks man.

I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!

psufan5 said:
so if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because im still debating if i want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but i also need to test out custom mods before my decision.
Thanks man.
Click to expand...
Click to collapse
no no no, do not factory reset if it bricks!!! Read the op!!!!

shawnbuck said:
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
Click to expand...
Click to collapse
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk

I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.

psufan5 said:
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
Click to expand...
Click to collapse
I designed this script to handle payloads, just need to package up one with a new payload with stock files and upload it.

Installed... Removed Laggyness i was getting with blur UI.
as to refering to the blur UI....
this is my second Atrix.. had to bring my first one back because when i was on tier 3 support the other night they fried the sim card reader with an update which was killing data signal to my phone... that phone had no laggyness whats so ever at all. I got this one today out of the box was having laggyness and slow response to key presses.. this fixed that as of so far.

designgears said:
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
Click to expand...
Click to collapse
Nice, I will give this shot. Although I am already running DeOdexed already but I figured may be you got it running better than mine
I am also going to start editing small things like animations. No sense oh having all this power without some eye candy

Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!

Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.

uskr said:
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Click to expand...
Click to collapse
Not sure, I didn't get an errors like that.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Try a usb port on the back of your PC

airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Download ADB Wireless from the Market. It'll help solve that one for you.

airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Install the Android SDK
install the MOTO drivers it will also install the moto adb drivers with it.
Install the ADB function drivers into the SDK/tools folder
run...cd to the sdk/tools folder... run... adb devices
should show the device is up which means ADB is enabled

4X extremely slow after rooting/reboot

So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?

Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse

alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?

voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.

Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS

voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.

alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again

laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa

66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!

If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)

Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!

As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.

Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX

The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.

Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...

I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).

Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX

66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this

no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.

Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX

How to root your Samsung Galaxy Gear!

How to Root the Samsung Galaxy Gear:
Firstly:
I AM IN NO WAY, SHAPE OR FORM, RESPONSIBLE FOR THE OUTCOME OF YOU FOLLOWING THESE INSTRUCTIONS! IT WORKED FOR ME, BUT THAT DOES NOT MEAN IT WILL ABSOLUTELY, POSITIVELY, WITHOUT A DOUBT, WORK FOR YOU!
Root Guide:
Preparation:
1. Install Samsung's official ADB Drivers from here.
2. Get Cydia Impactor from here.
3. Go to your Gear's settings and enable ADB​
To Root:
1. Plug in the device and let it install all the drivers it needs.
2.Unzip the Cydia Impactor folder you just downloaded
3. Open Impactor from the folder you just unzipped
4. The default "# drop SuperSU su to /system/xbin/su" is what you need
5. Click start
6. Once the process completes, the device will still look normal, but is fully rooted!​
I will have to leave it to you guys to install a utility like SuperSU or Superuser until there is a functioning recovery for the Gear.
Though this isn't necessary, however, and in some most cases doesn't work! SuperSU or Superuser just manage what apps access the SU command, so if you trust the app, it should be ok!
Enjoy your newly rooted device!​
How to restore back to stock:
Preparation:
1. Get Odin 3.07 from here.
2. Find the proper .md5 file from here.
(If you are in the US, just select the Great Britain file.)
3. Install Samsung ADB drivers from here.​
To Restore:
1. Plug in the Gear
2.From being powered on, (Bootable or not) press and hold the button of the right until the Gear shows "Samsung Galaxy Gear Rebooting" and rapidly press the button until you get to the "Select REBOOT MODE" screen.
3. Highlight "Download" in the list by pressing the button to scroll.
4. Press and hold the button for 3 seconds (and let go! The screen won't change immediately) and let it boot into download mode.
5. Unzip the .zip file you just downloaded that contains the ROM itself.
6. Select the PDA button and open the .MD5 file in the folder you just unzipped.
7. DO NOT ALTER ANYTHING ELSE!!!
8. Click the start button, and you'll be back to stock within a couple of minutes! (Most likely with any data on /data kept and all sideloaded apps remaining.)​
Any questions? Ask below! Want to help me make a ROM or Recovery? PM me!​

I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.

Oops!
BUS DR1V3R said:
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Click to expand...
Click to collapse
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!

photonicgeek said:
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
Click to expand...
Click to collapse
I'm actually not sure what's going on with this thing now. Busybox said the device was rooted, and it installed, but I can't seem to run any commands that require root.
Are you running Superuser or SuperSU, and what version?

Does this mean i will be able to use this with my HTC one? Im a newbie when it comes to this but id love to buy this watch to use with my stock 4.2 HTC One. Thanks.
Sent from ...............

Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?

big_pongo said:
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
Click to expand...
Click to collapse
Haven't rooted mine yet. But seems like the unroot feature in supersu should work
---------- Post added at 06:22 PM ---------- Previous post was at 06:18 PM ----------
This is great news! Thank you sir for creating an account. Just to share ur find. Who knows this might even make it to XDA wall on home page! But I do have to ask, how did you know Cydia Impactor would do the trick?

To answer some questions...
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!

photonicgeek said:
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
Click to expand...
Click to collapse
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?

Someone please sticky this so its easy to find
Sent from my SM-N900V using xda app-developers app

Minecraft on the Galaxy Gear!
BUS DR1V3R said:
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Click to expand...
Click to collapse
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom

photonicgeek said:
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
Click to expand...
Click to collapse
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?

codeman05 said:
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
Click to expand...
Click to collapse
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?

photonicgeek said:
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
Click to expand...
Click to collapse
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot

codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
I figure you can try restoring again!

codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially

codeman05 said:
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
Click to expand...
Click to collapse
Actually, I'm glad you found that!! I've been using ADB all this time!

Mods,
PLEASE pin this thread!

Hey does anyone know if
a) you can get notifications from 3rd party sms apps like handcent and
b) if you can respond to sms by typing yet? its pretty annoying when you get a text on your gear and you're somewhere loud, then you gotta take out your phone and respond. please if anyone knows these answers cant wait for this to take off....pretty excited.

this looks interesting! will have to try it on my gear :laugh:

[TOOL] Ouya SuperScript - One click CWM, Root, Xposed & Play Store for Windows

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

Softbricked after 5.1.1 sideload - HELP!

Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!

spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk

zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes

spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk

zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.

spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.

I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.

Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot

And I suppose if you do NOT already have ADB enabled et al, you're SOL?

AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.