Related
Can someone outline how I unroot (for insurance) I want to get it back to stock in case I have to take it in. Do I just have to flash the stock RUU?
Now that we have full NAND root, how do I unroot from that?
run the stock Ruu like just like the hero
Yep just run the stock 1.32.651.6 RUU I did your Link searching for ya just plug in your phone and run it.
http://shipped-roms.com/shipped/Sup...Radio_1.39.00.05.31_release_171253_signed.exe
lostinroot:) said:
Yep just run the stock 1.32.651.6 RUU I did your Link searching for ya just plug in your phone and run it.
http://shipped-roms.com/shipped/Sup...Radio_1.39.00.05.31_release_171253_signed.exe
Click to expand...
Click to collapse
Thank you very much!
seems like a simple process..but Im new to android phones.
Do you run this .exe on the phone? or connected to USB to PC. Not that I will be wanting to un-root anytime soon but it might be good to know down the line.. thanks..
elstupidos said:
seems like a simple process..but Im new to android phones.
Do you run this .exe on the phone? or connected to USB to PC. Not that I will be wanting to un-root anytime soon but it might be good to know down the line.. thanks..
Click to expand...
Click to collapse
.exe will always run from windows computer. android is linux based, no .exe file will run on the android phone.
for the RUU .exe follow the directions on your windows computer, it will guide you through the process, will need USB cable.
joeykrim said:
.exe will always run from windows computer. android is linux based, no .exe file will run on the android phone.
for the RUU .exe follow the directions on your windows computer, it will guide you through the process, will need USB cable.
Click to expand...
Click to collapse
Is it possible to flash it from the phone, and not need a windows computer?
Re: Un-Root
Not with a exe. I'm not sure how the architecture is built for the phobe, but u don't see why flashing a ruu from SD wouldn't work if one were built that way.
-------------------------------------
Sent via the XDA Tapatalk App
All a Ruu is a wrapper. The Ruu just checkes a few things then executes scripts. its kinda just like an automatics ADB.
If you run the EXE is extracts a bunch of files including a ROM.zip. You could probably copy that to your phone and install it from there using the recovery firmware.
I'm trying to restore using this method. The phone is definitely recognize by the software, (it shows the current .1 image version) it jumps to the black HTC screen then sits at "waiting for bootloader" then times out with a ERROR 171 "cannot connect to your android phone" message. Any suggestions? If I run adb devices command the phone is recognized. Any suggestions?
Edit: It seems on the 4th try it worked. At least the updating percentage is moving up.
Why can't a basic rooted rom with recovery be created using this method. That would really be a "1 click" root.
mrono said:
Is it possible to flash it from the phone, and not need a windows computer?
Click to expand...
Click to collapse
i've seen it posted on here, if you take the rom.zip which comes inside the ruu .exe and put it on the root of the sdcard, rename it PC36IMG.zip and boot into the bootloader, vold down + pwr, it will flash the phone w/o needing a computer.
i haven't personally tested it, so use at your own risk.
Updated first post
"Now that we have full NAND root, how do I unroot from that?"
mrono said:
Updated first post
"Now that we have full NAND root, how do I unroot from that?"
Click to expand...
Click to collapse
Run the ruu, you will be completely stock after that.
danknee said:
Run the ruu, you will be completely stock after that.
Click to expand...
Click to collapse
Thank you
When un-rooting, do you need to have the HTC drivers installed on your Windows machine? What mode (charge, disk mount, etc) does the EVO have to be in when you connect it via USB? Does HTC sync have to be installed or the Android SDK?
mrmack said:
When un-rooting, do you need to have the HTC drivers installed on your Windows machine? What mode (charge, disk mount, etc) does the EVO have to be in when you connect it via USB? Does HTC sync have to be installed or the Android SDK?
Click to expand...
Click to collapse
Phone should be fully charged. Really you just need enough juice to ensure it doesn't crap out during the flash process (could brick your phone).
I don't believe you need the HTC drivers, but every time I've run a ruu they were already installed on my machine, so I don't know.
Disk mount mode won't matter because the ruu will restart the phone before it has its way with it.
sync and sdk don't matter, the ruu is a self contained utility that issues adb commands to your phone.
Alternatively the ruu can be "run" by putting the proper file on the root of your sd card and powering your phone on with your volume down button pushed in.
To make the change back
I have done it 2x's and this worked both times. I tried to install the original Sprint Rom with the file provided here. Each time it stopped at the black HTC screen. All that needs to be done is to re-try the install of the original sprint Rom when it is at the black HTC screen. When the installation program says it can't complete and closes (wait for that to happen) just double click on the install program again (while you are at the black HTC screen (don't unplug from your computer)). When you try the install the second time at the black HTC screen, a green progres bar shows up on said screen and will show you the install progress. Hope this helps
Thanks guys! I was trying to mount the disk, then install HTC sync, etc. Leaving it on the black screen seemed to make the difference for whatever reason...
danknee said:
Phone should be fully charged. Really you just need enough juice to ensure it doesn't crap out during the flash process (could brick your phone).
I don't believe you need the HTC drivers, but every time I've run a ruu they were already installed on my machine, so I don't know.
Disk mount mode won't matter because the ruu will restart the phone before it has its way with it.
sync and sdk don't matter, the ruu is a self contained utility that issues adb commands to your phone.
Alternatively the ruu can be "run" by putting the proper file on the root of your sd card and powering your phone on with your volume down button pushed in.
Click to expand...
Click to collapse
Hey there! Having trouble unrooting from latest xda root method. I run the RUU and keep getting error 170- usb connection error. Is the driver not installed. Stupid me, when it prompted to install the driver before, I hit 'never for this device'. Any reversal for this??? Thx in advance!
Ive been through alsorts of the posts all the guides i can find, even ones that say they are for unrooted phones and all of them fail.
Does anyone know if there is acutaly any way that works to get the USB functions to work again?
all the guides ive found need to copy the files to the phone, which cant be done on a none rooted phone because you cant enable SU to move the files.
There must be some way of fixing this.
Tools i have
a windows PC
a linux Laptop
a working rooted desire
and a USB bricked none rooted desire
Have you read this?
To use this tutorial you should already have some skills, anyway, here's my translation:
1. Turn on your Desire holding Back+Power buttons, you will enter Fastboot (drivers should be installed).
2. Download fastboot.zip from here , unzip and execute sdcard_repair.cmd from fastboot folder.
3. Press reboot on your device and wait for it to be fully loaded.
4. In Android Market search for Android Terminal and install it.
5. Search for z4root (it doesn't support Desire but it will give you temporary root (until you reboot your device)).
6. Go to here , read it carefully, download files, necessarily edit the CID in mtd0.img,
put in SDCARD root folder (using cardreader or via internet, cos it's USB Brick )
7. Launch z4root, choose temporary root, close it.
8. Launch Android Terminal, write in it su, agree with root rights and now follow the usual UnBrick process. (for ex. this (use translator)).
9. Reboot.
well im getting somewhere now, usb functions are working again, sadly not getting anywhere with http://unrevoked.com/ just isnt seeing my phone, thanks for at least getting usb up again; )
* okay seems the unrevoked problem is my Hboot, currently downgrading it, fingers crossed
Just got a new Epic 4g from sprint.
Still has the stock on it running FROYO.EC05
-downloaded and installed latest drivers from Samsung
-downloaded and extracted One Click Root zip.. and extracted.
-Android SDK is installed (and java requirement)
-phone debug is on under settings.
-ran run.bat
got the not connected issue (which looking at the bat file makes total sense as you restart the server in the batch file)
run.bat gets stuck in some loop so I did some debugging.
-turned off ECHO in bat and followed along. the device is discoverd, listed and "get-state" does return "device"....... then....
the batch gets to:
FOR /F "tokens=*" %i in ('adb shell id | find "uid=0"') do SET ROOT=%i
where it sits and hangs.
have tried rebooting both, remove all downloads and redownloading. also fully uninstalled all drivers for Epic and reinstalled them.
anyone?
[MOD][One Click Root]ClockworkMod version 3.1.0.1[RFS & EXT4]
Try changing wire cause the one that sammy gives us is crap
Also try running as administrator
Sent from my SPH-D700 using XDA Premium App
Make sure to disable any antivirus software too. NVM, I see you are using 3.1.0.1, no rageagainstthemachine file in there. Probably the cable like was mentioned. Also try another USB port.
Hello,
I have a rooted Galaxy Gio (GT-S5660) with CWM and CM10.1 (from
Maclaw). I now need to restore it to factory firmware,
but am running into a brick wall no matter what I try.
I have downloaded S5660XXKTK_S5660COVKS1_COV.zip and tried with
Odin but that fails (don't remember the error message). And
anyway, it seems really unnecessary to boot into Windows to do
this, one should be able to do it all from Linux.
Is there any way to restore factory firmware using adb/fastboot?
adb connect to the phone etc., but fastboot doesn't work, it just
gets stuck in the "< waiting for device >" state.
(Yes, of course I run the adb/fastboot commands as root.)
I haven't found any tutorials/howtos on how to do this in Linux,
can anyone write one or point me in the right direction?
Or, if Odin is the only way, what files do I need to download to
make it all work? Obviously S5660XXKTK_S5660COVKS1_COV.zip isn't
enough.
I have tried the instructions found at android.gs, androidaddition.com
and mobotechie.com (seems I'm not allowed to post links...) but
nothing works.
Thanks,
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Click to expand...
Click to collapse
No I did not extract the S5660XXKTK_S5660COVKS1_COV.zip , I've assumed it's supposed to be used as-is, just like custom ROMs.
But there is no .ops file in the archive:
Code:
$ unzip -t S5660XXKTK_S5660COVKS1_COV.zip
Archive: S5660XXKTK_S5660COVKS1_COV.zip
testing: S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 OK
testing: SS_DL.dll OK
No errors detected in compressed data of S5660XXKTK_S5660COVKS1_COV.zip.
And no .ops file in the .tar.md5 file within the archive either:
Code:
$ unzip -xp S5660XXKTK_S5660COVKS1_COV.zip S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 | tar tvf -
-rw-rw-rw- a.oldak/0 18784256 2012-03-04 09:18 amss
-rw-rw-rw- a.oldak/0 459132 2012-03-21 09:40 arm11boot
-rw-rw-rw- a.oldak/0 6451200 2012-03-21 09:40 boot.img
-rw-rw-rw- a.oldak/0 19116032 2011-10-14 15:08 csc.rfs
-rw-rw-rw- a.oldak/0 786432 2012-03-21 10:11 mibib
-rw-rw-rw- a.oldak/0 566888 2012-03-21 10:11 oemsbl
-rw-rw-rw- a.oldak/0 368640 2012-03-21 10:11 qcsbl
-rw-rw-rw- a.oldak/0 6864896 2012-03-21 09:40 recovery.img
-rw-rw-rw- a.oldak/0 212430848 2012-03-21 09:40 system.rfs
Now what?
http://www.4shared.com/rar/ttIilfrh/Odinv442GIO_v10ops.html
Put .tar.md5 file in one package and flash. Don't forget .ops file
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
URL removed since I'm a new user and as such not permitted to post links...
Put .tar.md5 file in one package and flash. Don't forget .ops file
Click to expand...
Click to collapse
So, I'm supposed to extract the .tar.md5 file from the .zip file, separately download a .ops file from some completely other site (riddled with ads and popups and requiring registration, btw), and create a new .zip file containing the .tar.md5 file and the .ops file? Is that correct, or do I need to bundle more files into the new .zip file?
And in Odin (version 3.07), should I add the file as a PIT, Bootloader, PDA, PHONE, or CSC?
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration http://hotfile.com/dl/140235732/ec749d2/?lang=ro
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration (removed as I'm not allowed to post links...)
Click to expand...
Click to collapse
Well, that almost worked. I put the phone in download mode, connect it to a USB port, start Odin, the phone is detected as COM8, I add the .ops file, check "One Package" box, and add the .tar.md5 file. Odin has up until this point replied with this in the Message box:
Code:
<1> Added!!!
<1> Detected!!!
Check MD5 Filename : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Open File Name : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Check MD5 ...
Tail MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Image MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Check MD5 ... ok
The I click the Start button in Odin. The Message box is cleared, and this appears:
Code:
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
And after a few more seconds, this line is added:
Code:
<1> --- cannot open the usb serial port. code: 32
It doesn't matter whether I start Odin as Administrator or a regular user, the phone is detected but the "error 32" appears when trying to flash. The phone is the only thing connected to any USB port.
Any ideas?
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Click to expand...
Click to collapse
1. USB debugging was not checked. Is it supposed to be?
2. Kies was installed, I guess perhaps drivers come along with that? I just deinstalled Kies, and now Odin doesn't detect the phone any more. Should I install just some drivers and not Kies? If yes, which drivers, where do I find them?
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Click to expand...
Click to collapse
The phone can still boot, and USB debugging is activated.
To solve the error code 32 problem, people on forums suggest killing Kies using the Task Manager, and trying out different USB ports and making sure I use the USb cable that came with the phone. Well, I have tried reinstalling Kies, rebooting, deinstalling Kies but keeping the USB drivers, different USB cables and different USB ports, but no luck... nothing works. The phone is not detected by Odin any more.
It is detected by adb under Linux, though, so USB is still working.
When searching for a 3 file ROM I found the pages
www modaco com /topic/361399-latest-odin-309-odin-185-odin-183-all-versions-samsung-rom-flashing-tools/
and
www modaco com /topic/361286-18072013-latest-samsung-usb-drivers-for-mobile-phones-15270-win-87xp-adb-fastboot/
so I downloaded the latest Samsung USB driver, and made sure I was using an Odin version compatible with my phone.
And still, now after reinstalling Kies, Odin does not even detect the phone any more. Windows chimes when the phone is plugged in, but it does not appear in Odin, regardless of whether I start Odin before or after plugging in the phone, and regardless of whether I run Odin as administrator or not.
Seriously, is there no way to do all this using adb and fastboot under Linux? I get more and more homicidal when I have to spend time using Windows.
I sent you PM
EDIT : http://hotfile.com/dl/106492222/cc53f0f/S5660_XXKB9_OXXKB8.rar.html download this
http://droidangel.blogspot.ro/2011/05/procedure-how-to-flash-updateupgrade.html this is tutorial
Gyovany96 said:
I sent you PM
EDIT : (URL removed as I don't have permission to post them... moronic forum rules...) download this
(URL removed as I don't have permission to post them... moronic forum rules...) this is tutorial
Click to expand...
Click to collapse
Well, I finally managed to flas in Samsung stock firmware.
The instructions on the page
nguyenkieuhung1984 blogspot se /2012/01/how-to-upgrade-samsung-galaxy-gio-s5660_13.html
comes closest to describing what I did, except I used S5660XXKTK_S5660COVKS1_COV.zip and GIO_v1.0.ops .
I don't really know what I did to resolve the USB connections problems, but hey, when using Windows it's all trial-and-error, right?
First, install, deinstall and reinstall Kies a couple of times, and inbetween installs try the Odin procedure described in the nguyenkieuhung1984 blog mentioned above. And download the very latest Samsung USB drivers (I used 1.5.27.0) and install that. Repeat these steps until you feel like vomiting all over your keyboard. Oh, and install Odin 4.42 too while you are at it. And keep SS_DL.dll and GIO_v1.0.ops in the same folder as the Odin executable file. I don't know if it matters, but getting Windows to work is 80% magic, 15% luck and 5% skills, so why not?
Then reboot to Linux, read mails, surf, code, whatever is needed to regain sanity.
Reboot into Windows, install Kies again, including the bundled USB driver. After Kies has installed, verify that the Samsung USB driver version is still 1.5.27.0 and not whatever version came with Kies (I think Kies came with 1.5.23.0 ?). Anyways, 1.5.27.0 is what's on my system now, along with Kies 2.5.3.13043_14.
Start Kies and close it. Do NOT go into Task Manager to kill off any Kies processes; at least I didn't. Other tutorials tell you to, at least if you run into the error code 32 problem. Well, I didn't have that problem on my 30th attempt (on attempts 10-29 I did, though...).
Follow the steps on the nguyenkieuhung1984 blog mentioned earlier in this post, replacing filenames if needed (like I did, I mentioned that at the start of this post...).
The phone might now enter a reboot loop (mine did). Press and hold the Power and Home buttons to reboot the phone into the bootloader(?), and there you wipe settings and caches (two different wipes if I remember correctly).
The phone should now boot to stock firmware. Enjoy Android 2.3.6 or whatever Samsung ROM you selected.
It's recomended to "wipe data/factory reset" in recovery mode after you flash a stock ROM. But, enjoy ROM finally
Sent from my GT-S5660 using Tapatalk 2
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
PHYSC-1 said:
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
Click to expand...
Click to collapse
Quick follow up,you can sideload over adb if it's turned on,this applies to standard recovery as wel.So you can unbrick using the adb sideload method above even with a stock ouya to unbrick it guys/gals.