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.
Related
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:
Hello,
My phone is bricked. I have no backup on sdcard. I cannot reach sdcard from PC either. I have CWM recovery but I cannot push files or install zip files using adb sideload. It is waiting for device. I also tried with Odin but it doesn't connect either.
Now It has only CWM recovery and no connection from PC. Do you think Can I do anything?
Have you ever used ADB successfully on your computer before? You may not have the drivers installed properly.
if u fail to use fastboot and ADB try ODIN, samsung phones are capable of a delicate system-phone flash .
Thanks to all. I did it with wugs necus tool kit.
Guys, i have a bit of a problem, when trying to flash Omni ROM 4.4, i installed TWPR Recovery but wiped everything, included sdcard, mistake, now, i wanted to use KDZ to flash stock firmware or through CMD push ROM file to sdcard but can't get to connect the device, if i'm in download mode or recovery, adb is not working, in Devices it lists as "Android" but with trouble to obtain drivers, and if i boot normally, can't enter the OS because i wiped, i get MTP installation and another ones, but device in ADB (adb devices) is Offline.
What can i do?
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
atifsh said:
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
The problem was about drivers, that i knew, so i found some universal adb drivers, and they got installed, device was recognized but not as online, just as host, so i couldn't use adb sideload or just use adb to push the file. Found out that adb was outdated so i downloaded another one and, everything working, sideloaded the files, and now everything is runinng up again.
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
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.