Develop Bugs

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.

[Q] Stuck on Slimbean Boot Logo

Hello i am having problem with my samsung galaxy nexus I9250
i just factory reset the Slimbean Rom and now got stuck on Slimbean boot logo
i cant even go to the recovery mode, i cant even enter to the download mode,
but on the Slimbean boot logo when i attached the USB on my computer the Galaxy Nexus was detected and i can access the internal storage
but my phone is still stuck on Slimbean Logo
NEED HELP!
THANKS!
a small reward will be sent to anyone that can help me fix this out :good:

You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?

ntybrav infpire
t1.8matt said:
You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?
Click to expand...
Click to collapse
yes i tried that but slimbean wont let me

What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?

t1.8matt said:
What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?
Click to expand...
Click to collapse
no luck, its just proceeding to the ROM, i cant enter fastboot or flashboot or download mode even if i combine any keys

Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.

t1.8matt said:
Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.
Click to expand...
Click to collapse
maybe i guess it was bricked im stuck on the Slimbean logo like forever, sorry but what tool can i use to enter the adb fastboot ? noob here thanks for the response anyway

Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?

t1.8matt said:
Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?
Click to expand...
Click to collapse
Here's what just happened
my brother gave me this phone,
it has a slimbean rom which is my first time seeing that rom
i just go to settings
and click the factory reset
when the phone boots up i can only access the settings no other thing after that
i managed to get into the recovery mode of that rom on the settings
and install the rom again which is still on the sd card
then after the installation is completed when it boots up its now stuck on boot screen
and im screwed
i tried the universal naked driver but no luck device is still not recognized

I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?

t1.8matt said:
I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?
Click to expand...
Click to collapse
yep maybe thats my last luck hope it works, you think usb jig might work on this ? well thank you so much for your time and for trying to help me may god bless you always

No, theres no reason to use a USB jig. It's driver issues or something else simple, I'm just not site what. Not trying to get on you but it helps to know what your doing before you mess with things. If someone else is able to help you figure it out, do a lot of research in the general stickies before you do anything else. I hope you are able to get it going again and sorry I couldn't help you further.

bad flash - stuck in os

hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.

Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot

Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.

andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash

andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?

Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?

andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app

How to wipe android partitons while NO access to Fastboot? PLZ help

Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill

TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!

TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.

pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.

TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp

pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?

TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....

TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.

Can't boot to recovery after uninstalling SuperSU!!!

Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]

kunalvirk said:
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
Click to expand...
Click to collapse
Use magisk and hide root for tez app

visheshjain25 said:
Use magisk and hide root for tez app
Click to expand...
Click to collapse
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....

kunalvirk said:
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
Click to expand...
Click to collapse
Can you access fastboot

selvarajrajkanna said:
Can you access fastboot
Click to expand...
Click to collapse
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks

kunalvirk said:
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
Click to expand...
Click to collapse
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM

selvarajrajkanna said:
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
Click to expand...
Click to collapse
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....

kunalvirk said:
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
Click to expand...
Click to collapse
You can't access abd until your phone is booted into android

Weird, normal here.

selvarajrajkanna said:
You can't access abd until your phone is booted into android
Click to expand...
Click to collapse
So is there any other solution available that can get my phone to woking state.....:crying:

kunalvirk said:
So is there any other solution available that can get my phone to woking state.....:crying:
Click to expand...
Click to collapse
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily

selvarajrajkanna said:
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
Click to expand...
Click to collapse
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......

kunalvirk said:
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
Click to expand...
Click to collapse
Happy to help