[Q] Bricked my Ouya - Ouya Q&A, Help & Troubleshooting

Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP

gueschmid said:
Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP
Click to expand...
Click to collapse
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip

prophetjinn said:
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.

nex86 said:
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.
Click to expand...
Click to collapse
The firmware on the site you mentioned is not up to date!
Here is the official link for the latest firmware.
If you have adb access, you could try to fastboot CWM recovery.

Related

[Q] KFU Stuck trying to remove root checker.

I have been trying to reroot my Kindle Fire for some time now but recently when I try to run KFU it gets to the point where it installs TWRP but gets stuck in there trying to remove the root checker. The only way I can go back and actually use the kindle is by flashing the update.zip from the amazon website. Any help?
Were you actually successful in getting TWRP installed? Have you tried to access it?
soupmagnet said:
Were you actually successful in getting TWRP installed? Have you tried to access it?
Click to expand...
Click to collapse
It boots into TWRP while its rooting the Kindle. The problem is that it stays there and doesn't continue. TWRP is also missing some options and some text. I have to flash the update to gt out of TWRP
notdeadyet01 said:
It boots into TWRP while its rooting the Kindle. The problem is that it stays there and doesn't continue. TWRP is also missing some options and some text. I have to flash the update to gt out of TWRP
Click to expand...
Click to collapse
Download this and push it to your sdcard
http://forum.xda-developers.com/attachment.php?attachmentid=1286034&d=1346085105
It is a flashable version of TWRP that can be installed in recovery (this is to fix any potential bad installation of TWRP).
Reboot and access TWRP again.
Once in TWRP, enter the following code to remove the root check:
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
If you get an error message that says:
Code:
mv: can't rename '/system/bin/check_rooted': No such file or directory
You have nothing to worry about. It just means the "check_rooted" file does not exist.
While in TWRP, you can do whatever else you need to do to root your device or just flash a ROM (they're pre-rooted). If you do flash a ROM, be sure to wipe "system" and "factory reset" first. Otherwise you're looking at possibly needing a factory cable (or firekit) to fix the problem.

[Q] Error in /sdcard/update.zip (Status 7)

Hi,
I got my wife a 1st gen Kindle fire for Easter and she asked me to flash it so that she could get to her Google apps. So I used the KFU v0.9.8+ and with some luck and a lot of driver conflicts was able to get it rooted. The device has intermittent charging issues and needs to be returned. Every time I try to revert back to the stock rom or any version I can find, I get the error:
E:Error in /sdcard/update.zip
(Status 7)
Error flashing zip '/sdcard/update.zip'
I know this is a common error as it happens on many devices. I also have searched for 6 hours on the forums and other various sites trying to find a solution. I have also downloaded and re-downloaded update-kindle-6.3.2_D01E_4110520.bin and update-kindle-6.3.1 and renamed them to update.zip and deleted the old one to see of the download was bad, but to no avail. I even added the raw bin file to the amazon update folder and tried to push it with the update, inside the OS, but still no success.
Can anyone point me into the right direction? Do I need to change the fastboot from 4000 to 4002? Would that make a difference? I have to send this thing back to Amazon and I know that after I flash a stock rom to eliminate root, I have to manually delete all of the twrp files with ES file explorer.
I would really appreciate the help.
Batt
Update or downgrade your version of TWRP or install COTR
soupmagnet said:
Update or downgrade your version of TWRP or install COTR
Click to expand...
Click to collapse
Man, thank you for the quick response and I have to say you are quite the resource on XDA! I have seen your signature what seems to be a thousand times! Now I don't mean to sound noobish and I have to be honest, when it comes to the Kindle I most certainly am, but, what are you referring to when you say COTR, you mean Cannibal recovery right? Would that be less painless than reverting to a prior version of TWRP, and is there an option inside of TWRP to revert like there is in CWM?
Batt
HDBattery said:
Man, thank you for the quick response and I have to say you are quite the resource on XDA! I have seen your signature what seems to be a thousand times! Now I don't mean to sound noobish and I have to be honest, when it comes to the Kindle I most certainly am, but, what are you referring to when you say COTR, you mean Cannibal recovery right? Would that be less painless than reverting to a prior version of TWRP, and is there an option inside of TWRP to revert like there is in CWM?
Batt
Click to expand...
Click to collapse
There may or may not be a recovery flashable version of COTR available, but I'm not sure. The new version of KFU is supposed to include COTR as an option, but I'm not sure if it has been released just yet. I love TWRP and use it all the time, but I couldn't say for sure what version(s) had the (status 7) issue when reverting to stock. You could try rebooting the device into recovery to see if that helps (it has for me a couple of times) but I think your best bet, to avoid the hassle, is to install COTR.
There are several ways you can go about installing it...
1) You can download and rename it to twrp.img and replace the twrp.img in KFU to install it.
2) You can install it via fastboot:
Code:
fastboot flash recovery <filename>
3) In recovery, you can use ADB to transfer it to your sdcard and run the following command:
Code:
adb shell dd if=/sdcard/<filename> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
4) Or you can scour the COTR XDA forum thread for a user-posted recovery flashable ".zip" and flash it in recovery.
Of course, the same goes for (mostly) any version of recovery you want installed.
Just remember to factory reset if you're reverting to stock or you may have to get a factory cable to fix the resulting problem.
Thank you so much! This error have been driving me crazy for the past few days, no mater what rom i get this same error. Just flash COTR and all is good THANKS!
Help!
Hello! I have a big problem. I wan't to flash my P700 device whith CM11 and I have this error :
http://forum.xda-developers.com/attachment.php?attachmentid=2595602&stc=1&d=1393142285
Please help me!!!!!!!

[Q] Unable to install stock ROM on Kindle Fire

Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: http://kindle-fire-updates.s3.amazonaws.com/update-kindle-6.3_D01E_4019920.bin, and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Also having trouble taking my KF back to factory...
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
BriteLeaf said:
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
Click to expand...
Click to collapse
Yes I am getting almost the exact same error. I would really like a solution to this.
Ethanzh said:
Yes I am getting almost the exact same error. I would really like a solution to this.
Click to expand...
Click to collapse
So would I. I am glad that I am not the only one.
I am guessing...
I am guessing either us 3 are the only ones with this problem, or just no one wants to, or knows how to fix this problem =(
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have redownloaded the flash from Amazon at least five times, all with the same results.
As far as pushing it to the sdcard via twrp, I guess I for one don't know how to do that.
As to why I would want to go back to factory with it, I guess for me, it is what I prefer.
Thank you for answering though. I do appreciate it.
Same here, fixed!
Ethanzh said:
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: , and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Click to expand...
Click to collapse
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks, trying this now.
TWRP 2.2.2.1 Worked
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks for the tip. Worked like a champ.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
I just get stuck at < waiting for device > on my command prompt. Where am I supposed to open the cmd?
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Bump
Having the exact same issue when using KFU it just hangs there on activating fast boot
Cronus3166 said:
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Click to expand...
Click to collapse
This worked perfectly for me. Felt a little weird sitting there repeatedly pressing the power button as KFU searched for my device, but it worked. Thanks.

[Q] Stuck in ClockworkMod recovery mode loop.

My FireTV was rooted, I got the ClockworkMod recovery installed and working. I chose to do a factory reset on my FireTV because I wanted to start clean. After I chose to reset to factory settings, I keep getting back to the ClockworkMod menu. If I put it through a reboot, I see it booting up and it shows me the following on the screen:
- Choose a language.
- setting up ethernet.
- downloading firmware (this lasts about 2 seconds)
- restarting the FireTV
and then I'm back to the ClockworkMod menu.
I tried installing from Zip and going to bueller-51.1.3.0_513011820-rooted.zip, but I when I try this I get the following in the ClockworkMod menu:
Installing: /sdcard/bueller-51.1.3.0_513011820-rooted.zip
Finding update package...
Opening update package...
Installing update...
Amazon kernel detected: not patching
Install from sdcard complete.
I assume something went wrong, and if I try to reboot after this it brings me back to the same cycle as I've mentioned before and I end up right back in the ClockworkMod menu.
Can anyone give me some advise on how to get this thing back to the bueller-51.1.3.0_513011820-rooted.zip?
Thanks in advance.
Did you try restoring the cwm backup you made before flashing?
nhumber said:
Did you try restoring the cwm backup you made before flashing?
Click to expand...
Click to collapse
I didn't make one
What are my options from the CWM menu to bring this back to life (in any form rooted/stock)?
That message is fine. It's not an error. The newest CWM can install custom kernels and they need to be patched. That message in red is just saying it found a stock Amazon kernel that does not need patching. When you say you "reboot", what are you doing? Are you pulling the power because you think the install failed? You just need to hit esc to get back to the main menu and "choose reboot" system from there.
kraqh3d said:
That message is fine. It's not an error. The newest CWM can install custom kernels and they need to be patched. That message in red is just saying it found a stock Amazon kernel that does not need patching. When you say you "reboot", what are you doing? Are you pulling the power because you think the install failed? You just need to hit esc to get back to the main menu and "choose reboot" system from there.
Click to expand...
Click to collapse
That is exactly what I'm doing (reboot through CWM). The reboot brings up the Amazon boot up logo, and then proceeds to check ethernet, says it is downloading some firmware and then spits me back into the CWM menu.
DaveTO said:
That is exactly what I'm doing (reboot through CWM). The reboot brings up the Amazon boot up logo, and then proceeds to check ethernet, says it is downloading some firmware and then spits me back into the CWM menu.
Click to expand...
Click to collapse
If it's booting into the OS, it could be detecting that there is an updating, downloading it, and then rebooting to install it. CWM won't auto update, so it's just going to sit there. If you aren't on the latest version, that'll be why. So you'll need to update to that latest version through the prerooted roms.
And you'll have to get the latest pre-rooted image onto the firetv either via adb while cwm is running or from a usb stick.
kraqh3d said:
And you'll have to get the latest pre-rooted image onto the firetv either via adb while cwm is running or from a usb stick.
Click to expand...
Click to collapse
The easiest way to install updates is just to select install from sideload in cwm and use adb connect ip and then adb sideload.
rbox said:
The easiest way to install updates is just to select install from sideload in cwm and use adb connect ip and then adb sideload.
Click to expand...
Click to collapse
Is it pretty straight forward? I've sideloaded apks but not OS zip files. I'll try this when I get home tonight:
1) Install from sideload.
2) Connect to FireTV via adb.
3) adb sideload bueller-51.1.4.0_514006420-rooted+updated.zip
4) reboot after some on screen indication that the process is done?
DaveTO said:
Is it pretty straight forward? I've sideloaded apks but not OS zip files. I'll try this when I get home tonight:
1) Install from sideload.
2) Connect to FireTV via adb.
3) adb sideload bueller-51.1.4.0_514006420-rooted+updated.zip
4) reboot after some on screen indication that the process is done?
Click to expand...
Click to collapse
Yup.

OP3 bricked - Please help!

In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
simu_lacrum said:
In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
Click to expand...
Click to collapse
Your not bricked at all. Just stuck with a phone without OS I think? Why does ADB sideload not work? Do you get the "cannot read" error? Use adb push file directory then manually flash it with twrp. Make sure you are in the latest one from Bluspark!
Yes, I'm stuck with a phone without OS. I did get the "cannot read" error but I don't know why because all the necessary files were in the very same directory from where I issued the adb commands. Where do i find or define an adb push file directory? Currently I habe TWRP 3.0.3-0. installed. Will that be sufficient?
Please keep in mind that I've also lost my partition information. adb sideload alfeady didn't work before that because of the "cannot read" error. Still I don't know what's the reason for that error.
Here you will find everything you need to recover your phone:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Categories

Resources