Develop Bugs

[Q] kindle fire boot loop-ing CM9 after gede ROM flash

Hi
I rooted my KF using kindle fire utility 0.9.5 -successfully.
After flashing gede ROM, KF is boot looping (there is a CM9 logo with the android guy flashing on the screen)---rebooting KF brings me back to the same screen
I have absolutely no access to the device. Kindle unbrick v.1--does not do anything, it gives: waiting for device
kindle fire utility gives: device offline
adb device gives: error: device not found
however, when i plug in the KF into my computer, under Device Manager--the KF is listed as "Galaxy" with a yellow triangle. No longer listed as kindle.
Please help! Thanks

Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299

soupmagnet said:
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
Click to expand...
Click to collapse
Thank you for your response. the KF is fully charged so power is not an issue. The biggest issue is I have no access to the device in order to do anything. Device cannot be recognized and it reads as a Galaxy in device manager

Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709

soupmagnet said:
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
Click to expand...
Click to collapse
Thanks soupmagnet. However still no progress. my device is still bootlooping.
How can I get into recovery while it is still bootlooping.

I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.

soupmagnet said:
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
Click to expand...
Click to collapse
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.

mrslax said:
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
Click to expand...
Click to collapse
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?

soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Qem can't post links so I posted her response instead.
"Again, thanks for your response. Yes I have clockwork Mod.
At first the KF kept bootlooping to the KF intro screen followed by a small portion of the ROM intro.
After multiple resets the intro just continues forever.
Here is a link to what it looks like. Its been like this even after powering off and on.
http://www.youtube.com/watch?v=npx9HIbF5Po"

Any ideas for bootloop
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Please do you have any ideas re:bootloop. I am stuck.

Qem said:
Please do you have any ideas re:bootloop. I am stuck.
Click to expand...
Click to collapse
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP

no way to mount TWRP
soupmagnet said:
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
Click to expand...
Click to collapse
Thanks.
However did you see the you-tube link in chat #9?
I do not have any access to the device (in order to install TWRP) because no application (KF utility, Kindle unbrick, cmd prompt) can find the device: "ERROR: device not found".
The only place in which the device is found is in device manager but it lists the KF as "Galaxy".
May be I might be missing something...

You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.

soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
I am having the same issue.
The problem is we flashed CWM, then a CM9 rom. Now just runs the aminamtion.zip boot screen and does nothing. it is unable to get into fastboot or CWM. inorder to flash another rom to install TWRP

KF has internal sdcard... cant mount TWRP
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop

Qem said:
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Click to expand...
Click to collapse
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.

soupmagnet said:
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
Click to expand...
Click to collapse
So I was able to find drivers for the "Galaxy" (http://pastebin.com/nhbaaWMu) and installed it. This enabled KFU to recognize my device as "online".
However there are two issues (1) there is no access to the drive. it mounts like an external drive, but does not open/explore. like an external drive or USB would.
(2) when i try to go into recovery mode via KFU, KFU gets stuck.
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input

Qem said:
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Click to expand...
Click to collapse
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.

still boot looping affter fastboot+twrp2
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
Thank you for your help thus fat, I appreciate it. However I still have not fixed the issue...
I tried it (actual path to file), it still said "waiting for device".
after a while, I held held power button to manually reboot, still nothing.
I also uninstalled and re installed the drivers... nothing
using KFU to boot into normal mode still returns "system cannot find the drive specified."
at wits end...

Pardon the typo..
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
In prev post, I meant thanks for your help thus "far" and not "fat"
sorry for the typo

[Q] Wiped the WHOLE Kindle, Need help ASAP!

so yesterday i got tired of my ICS Rom. So, i went to recovery (TWRP) then recovered my old back up of stock. But since it had all the settings like when I flashed the rom, I Factory reseted it. But then suddenly it had deleted the whole stock rom! Couldn't go back. So my kindle was stuck on recovery loop over and over again. I got really impatient. So I started moving around then I mounted my Kindle to my computer and apped the ICS Rom that I used before. Then it flashed but it was still stuck on recovery. started moving more stuff on it, clicked the partitioning sd card and now I can't mount my kindle via Usb -___- and Then I new it was on Recovery fastboot. Please help! I Need this fixed. it deleted everything. and when I connected it to Adb shell, it says "Missing system/bin/sh"
Help me! i'm going to california on next week and I would like my kindle to work for me to play, listen to music, watch tv on it on the way.
Sorry for bad Grammar -___-

Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?

Dasanko said:
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Click to expand...
Click to collapse
I Have FFF 1.4, have TWRP 2.1 and fastboot works. But Mounting USB don't work. In recovery it says (cannot mount /sdcard/ (Invalid argument).)

What's the output of
adb shell "parted /dev/block/mmcblk0 p"
?

Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found

Luise. said:
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Click to expand...
Click to collapse
Means your KF is either not plugged in, or the drivers are wrong. You can't go on until the drivers are properly installed, if that's your issue. Take a look here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

Okay, Installed ADB Drives I think it now works it just tells me (exec '/system/bin/sh' failed: No such file or directory (2))

Can you type "fastboot getvar product" and then restart/plug in the KF?

Dasanko said:
Can you type "fastboot getvar product" and then restart/plug in the KF?
Click to expand...
Click to collapse
Yes i did and it says "Kindle"

Get TWRP (http://teamw.in/project/twrp2/79) and type "fastboot boot openrecovery-twrp-blaze-2.1.1.img" and see if you can get ADB working now.

Okay I already have TWRP Installed on 2.1.1 so Do I just go on Recovery and try to work adb shell on there instead of FFF Fastboot?

You just hinted at your ADB not working properly, try to fastboot boot into that TWRP to see if ADB works fine from it (I guess your drivers are good on the Device Manager, no errors or warnings showing up?). If it doesn't, then I guess the alternative is to try restoring the entire stock layout...

okay, I have TWRP, and when i have the usb connected to Kindle while its on Recovery, My Internet i use a Easytether so you can tell what android devices are connected and while my kindle is on recovery, The Easytether says My Kindle can connect, (but it really cant) and the ID Shows up that 0000005 number? but I Really Need My kindle to work! -__-

These issues have been fixed.
For future reference, this user was experiencing a combination of bad drivers and a corrupt sd card partition (rm 12 + mkpartfs primary fat32 start end + name 12 media).
The ADB issues were gone after fixing the drivers, without a need to reinstall TWRP.

Cant mount SD card on kindle fire.

So I was messing with my kindle and it was trying to upgrade it to jelly bean and i guess i missed one of the steps and bricked it. I was going through the process of unbricking but when i was trying to do extract the update.zip folder it would not allow me to because it could not mount the SD card. All i need to figure out how to do is get the SD slot mounted. I am slowly picking up on command prompt and still trying to figure out adb shell but that is all i need help with.
I can unbrick it if someone knows how i can get my kindle to mount back to my computer!
Any advice or step by step for it would be very helpful, Thanks guys

Could you be more specific as to how your Kindle is "bricked"?

soupmagnet said:
Could you be more specific as to how your Kindle is "bricked"?
Click to expand...
Click to collapse
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see

Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?

soupmagnet said:
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
Click to expand...
Click to collapse
It will go to the kindle fire logo and then it would go to a black screen. It makes no boot animation. It will change some brightness. The words kindle fire are in white and blue. It flashes where is needs to do the boot animation and then just goes to a black screen

dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.

acii22 said:
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
Click to expand...
Click to collapse
I have tried to install it from KFU but it is always has a problem doing so. I let it charge over night and it is still doing the same thing. Here is what is says when i try to install twrp

Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.

soupmagnet said:
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
Click to expand...
Click to collapse
Ok i did that but it still will not let me connect the kindle to the computer it keeps giving me sdcard errors. any idea how to fix the sd card issue?

Hey were u able to fix it??
Had the same problem with mine when I used TWRP to format my SD card..but was able to solve it..
What I did was a very simple thing..got the kindle recognised as a drive..used windows partition manager to format it
It worked.. I tx the stock and installed it
Try it and let me know
Sent from my MB526 using Tapatalk 2

I had the same problem before and only had to reboot the kindle.

Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.

dontgoback4cody said:
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
Click to expand...
Click to collapse
I have an Idea. If you have fastboot working on your computer. You could try flashing a rom from your computer by typing
fastboot -w(wipes device)
fastboot update <path to rom> (flashes rom)
If it works, you can then fix the sdcard easier with adb/shell/partition manager. Its worth a shot.
I also found this on a website
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip

I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.

Then you need a factory cable to get into fastboot.

dontgoback4cody said:
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Click to expand...
Click to collapse
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card

kishorev said:
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
Click to expand...
Click to collapse
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.

soupmagnet said:
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
Click to expand...
Click to collapse
You are right..
But i too was had the same msg when i was trying to fastboot it.. but then it worked.. I had formatted it and then tx the stock rom and flashed it..
Probably i missing something here..
Anyways thnx

Can't mount SD card on kindle fire
I was in a similar situation and after reading the various forums i came across this action "hold down the power button until the kindle goes off and continue to hold for about 30 seconds I believe this resets the kindle and then tick debugging and mount usb storage the sdcard will open on your pc" and then you can go from there. Worked for me so good luck.

[Q] twrp fails doing anything, no os(?)

Ive been working on this kindle fire for the last 2-3 days.Here's what I know I can do:
I can issue commands in fastboot mode
I can issue commands in adb mode
I can even mount the kindle to my PC as a SDcard (when I give it the command in adb)
I checked the partitions and they seem to be stock, (ext4 on data, cache ect.) I ran the oem command anyways just to make sure.
However it appears nothing within TWRP actually works. Wiping anything just comes back with a failed message (right after verifying file systems), trying to load a ROM will act like it doing something (200mb file done in 2seconds) but really doesnt. Im not really sure where to go from here, it just appears that there is nothing on the kindle, no OS or otherwise, and I cant seem to find a way to load one.
Thanks in advance!

Which version of TWRP are you using?

Thepooch said:
Which version of TWRP are you using?
Click to expand...
Click to collapse
2.2.1, I believe its the latest version.

You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .

Thepooch said:
You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
That did the trick, kindle back up and running. Thanks a ton!

Ouya Bricked ?

Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?

Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything

imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?

ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.

I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.

Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !

Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.

labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:

Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium

at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?

glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu

glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.

BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition

glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.

BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed

glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.

BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.

glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.