ok, so my Ouya is soft bricked. and i can get into stock recovery no problem. however when i go into "apply update from adb" i get weird errors.
1: if i try "adb reboot bootloader" i get "Error: closed"
and if i try to sideload OTA/CustomOTA/CWM then i get installation errors AFTER the sideload command transfers the file to the Ouya, but BEFORE its done verifying.
i have tried all 3 possible drivers that windows detects within the .inf folder (android adb interface, composite, bootloader) and none help.
anyone have any ideas? is it possible to tell adb and the ouya to skip the file check and force flash? thanks!
glitchhawk said:
ok, so my Ouya is soft bricked. and i can get into stock recovery no problem. however when i go into "apply update from adb" i get weird errors.
1: if i try "adb reboot bootloader" i get "Error: closed"
and if i try to sideload OTA/CustomOTA/CWM then i get installation errors AFTER the sideload command transfers the file to the Ouya, but BEFORE its done verifying.
i have tried all 3 possible drivers that windows detects within the .inf folder (android adb interface, composite, bootloader) and none help.
anyone have any ideas? is it possible to tell adb and the ouya to skip the file check and force flash? thanks!
Click to expand...
Click to collapse
nvm figured it out. i was using an old OTA and it was getting file errors. newest OTA worked fine. thanks all.
Related
I have been searching all over xda and google to try and solve this problem and I'm stuck. I'm trying to unlock the boot loader for my Nexus 7 (2013) that I just got yesterday and I have been following the video guide.
The problem I'm having is that when I do command "adb devices" it shows that my Nexus 7 is connected to my PC (windows 7) but it says "offline" and when I do "adb reboot bootloader" I get the error "device offline".
I have my device in developer mode and I enabled USB debugging in the settings already. In my search throughout the forums and followed the steps to make sure that my drivers were up to date. I tried doing it by manually selecting the drivers and by using the SDK Manager to install the Google USB drivers, neither of these fixed the problem.
I can't figure out what I'm doing wrong, please help!
Have you tried rebooting into the bootloader manually then if "fastboot devices" work?
If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630
Have u checked camera instead of mass storage? That's how I have to do it.
Sent from my Nexus 7 using Tapatalk 4
Sounds like a driver issue.
Make sure you've got the correct drivers installed. Open up Device Manager in Windows 7 and manually update the driver - http://developer.android.com/tools/extras/oem-usb.html
Read the tutorial and watch/follow the video: http://forum.xda-developers.com/showthread.php?t=2382051
Got this on a Mac today, on the first time I connected this device.
Updated to latest android-sdk, re-installed platform-tools, and it worked fine.
sfhub said:
If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630
Click to expand...
Click to collapse
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip
Forgot10- said:
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip
Click to expand...
Click to collapse
Are you saying you have a download problem or a flashing problem?
The twrp archive I used wasn't a flashable zip. It was just a zip file with twrp.img archived.
You need to unzip and flash the twrp.img (it has a longer name) using
fastboot flash recovery twrp.img
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse
Hi everyone,
just to clarify that It's my first time I try to unlock and root my phone, so no much knowledge.
I basically followed the steps to unlock the bootloader.
Everything worked perfectly, I reached the recovery, went on 'apply update from ADB'.
But then, when I enter in cmd: 'adb sideload <whatever the filename>'
it prints out the Android Debug Bridge instructions rather than transferring the zip file to my phone, and the phone keeps on asking "now send the package you want to apply to the device with adb sideload filename "
N.B.: the phone is recognized by adb, even when I enter adb devices, it is recognized
Any help?
did you try issuing the adb sideload command BEFORE pressing the button in recovery?
I had this issue before when trying sideload, in fact I think it WOULDN'T work if I started it via recovery FIRST. it has been a long time since I did this though, but I swear I remember not even having to press the button in recovery, I think it just automatically started once I issued the command from computer.
Yea, just tried it and same results
which recovery version are you using?(CWM or TWRP? and which version also)
and which adb version do you have on your computer? are you certain it is the latest available? did you install it through the Android SDK?
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!
Hello,
I downloaded the March OTA .zip from the thread in the general forum with the intention of installing via ADB sideload for the first time. I've installed the Android .sdk and confirmed that adb does work. Typing "adb devices" in the command prompt gives me the serial number.
I've used that to reboot to bootloader, go next to recovery, and click the "install via adb" option, at which point it instructs me to go back to the computer and push the file. I shift+right click on the folder containing platform-tools to open a command prompt tied to this folder (which also contains the downloaded OTA update, renamed "update" for convenience).
When I enter the command "adb sideload update.zip" it tells me that the device cannot be found. I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Device is stock, unrooted, bootloader locked. I wanted to try this before messing with fastboot and the binary images to get my feet wet, but it's been a headache inducing afternoon so far. I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Thanks in advance!
Try putting the OTA zip file in the same folder as the adb.exe file (in the platform-tools directory)
Moonboots said:
I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Click to expand...
Click to collapse
Are you using a Windows machine? I am far from an expert on these matters, but my sense is that failing to "see" the phone in recovery is usually a driver issue. See if this thread helps.
Moonboots said:
I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Click to expand...
Click to collapse
My experience has been that the only hard part of sideloading OTAs is the initial step of getting ADB running on a windows computer. Once you sort that out, it is very easy and also very liberating to not have to wait for updates over-the-air. Good luck!
Thanks for the help, all! The trick was letting Windows find its own driver (not the automatic setting, had to select this option) when the phone was in adb sideload mode. It's a different driver than fastboot and with the phone on.
Sideloaded the update last night and we're going strong! ?