Recovering from a Bad Flash --How i almost bricked my OUYA - Ouya Q&A, Help & Troubleshooting

First of all I am not a DEV and this is something i messed up over the Weekend, with a bad flash of custom rom.
This is something i picked up poking around the forums trying to resurrect my almost bricked OUYA.
I recently got my OUYA last week, rooted and installed the mods -- xposed framework playstore from this forum with the exception of installing a custom CWM recovery and installing a custom rom -- (Stock Plus) -- saving the best for last.--- :cyclops: Been very happy with my Ouya Experience, all is working until one saturday afternoon i decided to install a custom Rom and custom CWM.
How i messed up:
- I flashed CWM
- I flashed the Custom Rom with an error --- Assert failed , status 7, some changes not installed blah blah blah..
- Bad drivers installation from my desktop , was using a modified USB drivers from a different toolkit, was not able to update my device manager configuration before flashing -- my PC is detecting OUYA as Nexus 7, and was trying to install OUYA as MTP device on bootup -- i got adb working though and was able to run the toolkit for the mods before messing my setup.
Stucked on FASTBOOT
So i ended up blank screen on boot up and a very expensive paperweight after a bad flash of the Custom Rom
- Since my ouya is still being detected by my Desktop setup, i installed the correct USB drivers, managed device manager and updated the detection of my device as Nexus 7 to an Android ADB interface and correctly installed the fastboot drivers
- Since ouya doesn't have the hardware buttons, for the recovery, reading around, it can be bypassed:
Hook a keyboard on OUYA and press the power button + ALT+PrintScreen, after sometime press the combination with i
Code:
POWER+ALT+PrintSCREEN and I
press the combination a lot of times, with a better timing you will be forced to enter into recovery mode -- there's a better explanation for this over at the ouya forums and with luck you will be on the recovery.
Once my OUYA was on recovery mode, my desktop was able to detect an ADB device hooked up and was able to run an adb shell
Code:
adb devices
adb shell
From the toolkit i reinstalled my CWM and ensured that my Dekstop is able to load the FASTBOOT drivers
Downloaded the OTA official update from the threads, and pushed it via adb on my sdcard,
--- was trying to push the OTA via /sdcard but was able to via /data/media
Code:
adb push <source directory\xxx.zip> /data/media/xxx.zip
from the adb shell, navigate to /data/media you will be able to see your file there
Reboot recovery
Code:
adb reboot recovery
Flash as you would flash any other ROM
Reboot Reconfigure OUYA -- its now back on stock and re-apply the mods.
Lessons Learned
- Always have a copy of your flashable zips on your sdcard
-Install the proper ADB and Fastboot drivers, and ensure the device is detected as it is
-Make sure to have your CWM working properly.
- RTFM and Instructions from the thread.
Just sharing my experience hopefully save another OUYA from bricked.
Happy Modding!! :victory:

Related

[HELP] Phone in bootloop, adb can't connect

Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?
You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.

[Q] Can't mount SD Card in TWRP

I recently rooted my kindle fire and installed twrp along with cm7, but I accidently did a factory reset inside cm7 and was stuck on the firefirefire logo, I used an unbrick tool, but that erased all my user data and did not help. I managed to get my boot back to 4000 and install twrp again, but it won't let me mount sd card and will only allow me to mount system.
Sorry Im a noob
Im having the same issue, trying to moun it, but I keep getting
Error mounting /sdcard!
Is there a way to fix it? Im stuck on recovery (CW)
Heres a great idea get off of the discontinued recovery and switch to touch screen clockworkmod recovery its way better when it comes to things like that
Link: http://forum.xda-developers.com/showthread.php?t=1454241
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Thanks b63 for the fast reply. I dont have twrp I have CWM recovery, im trying to install TWRP but I get an error:
error: device not found
Is there another way to install TWRP?
Thanks
i don't know about cwm but i would try to boot to it and test if adb is working
then it should be the same - you only need adb root access
if you have this access with cwm also then there is no need to install twrp
Well if I boot into CWM
I can do adb shell
But then nothing happens
If I let Kindle boot normally (after the Yellow triangle) the screen goes black and I cant adb shell anymore
What im doing wrong or what im missing.
Thanks again
BTW
When I boot int CWM I get this message
E:Can't Mount /cache/recovery/command
stay in your recovery
after the command the sdcard should mount to your computer
check your device manger
follow the first desciption
if you can't get it gimme a pm ...
Wooooot!
Thank you so much b63!!!!I couldnt sleep for this damn problem
In the end this one help me out
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
I dont know why it worked with >> its the same (for this case) but I could finally mount it on windows
Now im back to CM7, really thanks!!!!!
really glad that it worked ...
b63 needs a medal lol.
Sent from my HTC Glacier using xda premium
Thanks b63 I got twrp to mount the sd card, with this:
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
But, when trying to install cm7 I get an error:
E:Cannot load volume /misc!
ignore it - the kf don't have a volume "misc"
Stuck in twrp!!!!
b63 said:
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Click to expand...
Click to collapse
I can get into TWRP, but when I type in ADB DEVICES in command prompt, it says the standard daemon not running, then daemon started successfully. This is followed by List of Devices attached, but it's blank after that.
I used the Kindle Fire Utility to install drivers, and when I use ADB DEVICES Command Prompt with my T-Mo Vibrant, I can get into ADB Shell.
Any advice?
Please note, this isn't mine. I've never owned a Kindle Fire, so I'm banging myself raw with information overload on this type of device. I'm trying to help a co-worker out with his Fire that he borked. I've owned three android phones/tablets and rooted/ROMed all of them, so I follow instructions. So far, I've tried the Kindle Fire Utility and the Kindle Fire Unbrick Utility found in these forums. My co-worker didn't get to the point of making a back-up or installing the Stock Image as an Update.zip. I have the stock image downloaded, and have renamed it, but I can't get it onto the tablet at all. Selecting Mount in TWRP always locks everything up, and there is nothing to Install or Restore. So, like I said, I'm getting bloody here, but no joy.
Any help would be appreciated!
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
b63 said:
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
Click to expand...
Click to collapse
He says he rooted it, installed FireFireFire, and the ICS-ish launcher (name eludes me at this point). Then, it basically boot-looped (Yellow Triangle, then Kindle Fire, back to Yellow Triangle).
My first thought was ADB Shell, but the KF is apparently a stranger animal than most of the other Androids I've dealt with, so it didn't automatically pop up. I installed KFU (Kindle Fire Utility, most recent version), installed the windows drivers (I have Win7 Pro 64-bit) that came with the KFU, and attempted to get it to boot normally, recovery, or anything. Note - A couple of times (like 4 or 5 out of 100), it did make it to a full boot for a few seconds, but would crash within seconds. TWRP was not installed at that point, so I successfully pushed that with the KFU. I also downloaded the stock image, and renamed it. TWRP won't mount the SD card so that my computer can see it, so I'm losing that battle. Also, at some point along the way, the KF started attempting to connect to the PC when plugged in, with the typical USB device connected sound, but two seconds later, it acts like it is unplugged, with that sound. If the KF is visible in the Device Manager, it must be hidden, cuz I can't see it. This was not the case at first, with an Unmount icon for the Kindle being displayed in the notification (right) side of the Windows toolbar. This is in conjunction with the device now booting straight to TWRP, and not even attempting to go the normal boot route. I've also tried a Kindle Fire Unbrick Utility to restore it, with no luck. It wipes the User Data, wipes cache, downloads the update.zip, but can't mount the unit to push the data. I've never been able to get ADB to find the unit.
If I can get the update.zip to the SD root, or if I can ADB shell it, I think I've won. But I'm being blocked on both those counts.
Thanks for being willing to look into this for me!
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
b63 said:
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
Click to expand...
Click to collapse
You're giving me a lot of hope. I'll give this a try when I get home tonight, and I'll contact you with any other hurdles. THANK YOU SO MUCH!
halfway there
Ok so I have run the command under the adb shell after adb did detect the device, however when I run the command it says that "non existent directory" What am I missing?
echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexis
tent directory
Getting that when i try to issue the command,
Any hint?

[Q] Semi-bricked Nexus and not sure what to do

So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?
Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)
MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!
Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium
Drivers
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250
You're booted into TWRP when trying adb?
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250
Just for understanding, USB debugging is only activated through recovery?
It's also under settings >> developer options so you can use adb while the android is running.
3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot
MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.

[Q] CWM & Fastboot but No drivers for pc

It's been a while since I have updated my recovery and rom so I downloaded latest CWM and CM. I formatted all the options inlusing sdcard and system. That turned out to be a big mistake because now I can not push any files to the phone to flash a rom. I can get to CWM inlcuding the option to adb sideload but my computer does not have the fastboot or adb drivers installed. Is there a way for me to push a rom to the device to get back up and running? I have tried to install the fastboot drivers but the mahine is not recognizing the device.
***Update**
I ended up using the universal toolkit in linux so I wouldn;t have to set up the drivers and was able to get back to a stock image and work from there.

How to transfer a zip on my sdcard without adbsideload

I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent

Categories

Resources