Develop Bugs

[Q] final steps when installing custom recovery

Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help

asanz00 said:
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
Click to expand...
Click to collapse
Usually that happens when the device isn't at the bootloader. Did you run "adb reboot bootloader" to get to the bootloader?
Sent from my Nexus 7 using xda premium

Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader

MIght be a driver issue. On mine the first time I booted into fastboot mode I had to go into device manager, found the android device with a yellow triangle, and had to install the drivers manually with "have disk". Hope this helps.

asanz00 said:
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
Click to expand...
Click to collapse
Same thing happened to me, I never saw anything until I fastbooted the .img. And then I had to try it on 3 displays before one would show CWM. However after I flashed the .zip I have since tried all the displays and they all have worked every time.

Wow problem solved!
In devices administrator, there was one small called "fastboot" with yellow triangle.
I manually installed a driver called "android bootloader interface" and now it is working
thanks a lot!!!

No problem, always glad to help.

Now im fighting to get multi usb support via using a 5 ports usb-hub, i will write if i can ge througt

Can you post about that in the USB thread ? I just bought an active USB cable and 4 port hub, I hope they weren't a waste. I'll still get some use on my laptop, but not enough to justify the purchase.
Sent from my GT-P3113 using Tapatalk 4 Beta

[Solved] Soft Bricked Nexus 7 (2013)

Hey there,
i have a Nexus 7 (2013) with android 4.4.2 (KOT49H). I unlocked the bootloader with wugfresh´s toolkit - so far no problems. Then i tried to root... The toolkit installed TWRP and launched into recovery to install the needed root files, but the device remained there...and nothing happened. On the PC the process froze showing the message "waiting for device". I rebooted the device manually from recovery. After the reboot i had no root access.
Because of these problems i decided to use the "Flash Stock + Unroot" option in the toolkit. First i completely reinstalled all related drivers with the full driver intallation guide and i got the "Success" message after testing. I enabled usb-debugging and went through the restore process. Then i got the message "FAILED (data transfer failure (Too many links))". My device remained in bootloader mode. At least it is possible to boot into bootloader mode every time. But when i try to start the device normal it freezes on the google logo, because the rom is partially wiped.
What can i do to get my device to stock firmware without to exacerbate the situation? Should i enable "Force Flash Mode"?
Please help me, thank you very much!
I attached the log below...

Ditch the toolkit. Download the Google revert to stock package, unzip it, connect your device in fastboot and run the flash all batch file
Sent from my Nexus 7 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
Refer to this guide http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using Tapatalk

SwoRNLeaDejZ said:
Ditch the toolkit. Download the Google revert to stock package, unzip it, connect your device in fastboot and run the flash all batch file
Sent from my Nexus 7 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
Refer to this guide http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks! I will try this method. Is it necessary to install some further specific fastboot drivers or are the ones installed by the toolkit sufficient? USB-Debugging was checked before in developer options but the android os is partially wiped. So will this be a problem? Is there a possibility to control if the device is recocnized correctly before i run the batch file. I think i don´t have to remove the "-w" from the fastboot update command because everything has to be wiped.

Just follow the tutorial, you should be good to go. And the adb and fastboot drivers are the same.
Sent from my LG-MS770 using Tapatalk

SwoRNLeaDejZ said:
Just follow the tutorial, you should be good to go. And the adb and fastboot drivers are the same.
Sent from my LG-MS770 using Tapatalk
Click to expand...
Click to collapse
Ok i started the batchfile but it said that the fastboot command couldn´t be found. Then i copied the 5 files of the unpacked factory image into the sdk -> platform tools directory. Am i right? Now when i run the flash-all file it says "waiting for device" I do this for the first time so i´m a little bit uncertain. Is all i have to do now to connect my nexus in fastboot mode? Thank you very much again!
Here are some screenshots...

Have you looked in Device Manager from Windows if the hardwaredriver of device is correctly installed. While in recovery and usb-connected type 'adb devices' in Command Window to see if there is connnection before flashing.
I had the same problem in Windows 8 first time flashing. Only way to get driver and device in recovery mode working in my case: In Device manager I clicked 'update driver' of 'unknown device', browsed to unpacked driver Folder and let Windows install correctly.
Verstuurd vanaf mijn Nexus 7 met Tapatalk

juliatan said:
Have you looked in Device Manager from Windows if the hardwaredriver of device is correctly installed. While in recovery and usb-connected type 'adb devices' in Command Window to see if there is connnection before flashing.
I had the same problem in Windows 8 first time flashing. Only way to get driver and device in recovery mode working in my case: In Device manager I clicked 'update driver' of 'unknown device', browsed to unpacked driver Folder and let Windows install correctly.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
In the driver manager there is an android device connected "Google Nexus BootLoader Interface" but when i run the command "adb devices" i don´t get an device listed although i am connected in bootloader mode. Recovery isn´t working anymore (shows android with triangle), because of the bad factory reset with the toolkit. So what can i do to get my device recognized? Actually the needed drivers should be okay, because the universal drivers were installed via the toolkit and i was able to unlock the bootloader etc. What i´m doing wrong?
Thank you for help.

I appologize, but this is out of ny league. I would first try that toolkit-thread. I am sure there will be a repair thread too. Good luck.
Verstuurd vanaf mijn Nexus 7 met Tapatalk

Blizzard300 said:
In the driver manager there is an android device connected "Google Nexus BootLoader Interface" but when i run the command "adb devices" i don´t get an device listed although i am connected in bootloader mode. Recovery isn´t working anymore (shows android with triangle), because of the bad factory reset with the toolkit. So what can i do to get my device recognized? Actually the needed drivers should be okay, because the universal drivers were installed via the toolkit and i was able to unlock the bootloader etc. What i´m doing wrong?
Thank you for help.
Click to expand...
Click to collapse
When you are connected to the computer in the bootloader (on the N7), what does it say when you type "fastboot devices"? (without the quotation marks)

juliatan said:
I appologize, but this is out of ny league. I would first try that toolkit-thread. I am sure there will be a repair thread too. Good luck.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
Thanks, i will do that. After reading some indications in the toolkit thread i found out that i am able to access stock recovery

charesa39 said:
When you are connected to the computer in the bootloader (on the N7), what does it say when you type "fastboot devices"? (without the quotation marks)
Click to expand...
Click to collapse
Thanks, i think you found the solution When i use the command "fastboot devices" i get this: 08f34cbd
Does it mean everything is correctly installed and i´m ready to flash the factory image? I am also asking me if it was right to extract all the files of the razor-kot49h factory image into the platform tools directory of sdk, but otherwise when i just executed the flash-all file somewhere on the computer there were failure messages, so i assume it should be right this way. Thank you!

Blizzard300 said:
Thanks, i think you found the solution When i use the command "fastboot devices" i get this: 08f34cbd
Does it mean everything is correctly installed and i´m ready to flash the factory image? I am also asking me if it was right to extract all the files of the razor-kot49h factory image into the platform tools directory of sdk, but otherwise when i just executed the flash-all file somewhere on the computer there were failure messages, so i assume it should be right this way. Thank you!
Click to expand...
Click to collapse
Yes it does! Nothing was coming up when you typed "adb devices" because that's only when you're in the OS after it completely boots into it's ROM. Fastboot is for when it's in the bootloader menu. And yes, you are correct regarding the factory image zip. Extract everything out of the zip (I can't remember if there's a zip inside that zip, but I think there is). Make sure you unzip that as well if there is. Then, place all the image files into that platform-tools folder. So you should have image files for Bootloader, System, Userdata, Boot, Recovery and Cache. I don't think the cache is necessary, but I suppose it wouldn't hurt to flash it as well.
I followed these steps when restoring the factory image on my N7: http://forum.xda-developers.com/showthread.php?t=2513701
I used Method 2 from the OP. Obviously, those instructions are for the Nexus 5, but it'll work. Just skip over the part where it says "flashboot flash radio". So fastboot flash the bootloader, reboot bootloader, fastboot system, fastboot userdata, fastboot boot, fastboot recovery, fastboot erase cache (or fastboot cache if you want to flash the cache image from the factory image zip). Then, manually select "Recovery Mode" on the phone using the volume buttons on the N7. It'll show that Android on it's back with the red exclamation mark. Hit Power + Vol Up at the same time and it'll show the stock recovery menu. Select "Wipe data/Factory data reset" and reboot. You should be good to go.

Unzip the tar.gz and then double click flash all, no need to unzip anything inside the tar.gz. and yes, adb commands only work from inside the os, you need to use fastboot commands when in the bootloader. I would suggest reading up on it, very useful information.
Sent from my LG-MS770 using Tapatalk

Yeah, all went perfectly well! After the factory image was restored i flashed twrp with fastboot, installed super su over sideload and then busy box from the playstore. I immediately did a full backup in the recovery At this point i want to say thank you to all who helped me! You are awesome!
First i was afraid that my nexus couldn´t be repairable anymore. So i´m really happy now that everything worked.

Blizzard300 said:
Yeah, all went perfectly well! After the factory image was restored i flashed twrp with fastboot, installed super su over sideload and then busy box from the playstore. I immediately did a full backup in the recovery At this point i want to say thank you to all who helped me! You are awesome!
First i was afraid that my nexus couldn´t be repairable anymore. So i´m really happy now that everything worked.
Click to expand...
Click to collapse
Glad it all worked out for you. :thumbup:
Sent from my Nexus 5 using xda app-developers app

Adb recognizes my device ID, but fastboot does not

Hello all, I am looking to unlock the bootloader and have installed all the drivers. I am able to see the device ID through "adb devices" when my phone is on. But when i enter the fastboot mode, I am not able to see the device ID.
Have installed all the drivers, dont know what i am missing here.
Sent from my ASUS_Z00AD using Tapatalk

saggiboy231 said:
Hello all, I am looking to unlock the bootloader and have installed all the drivers. I am able to see the device ID through "adb devices" when my phone is on. But when i enter the fastboot mode, I am not able to see the device ID.
Have installed all the drivers, dont know what i am missing here.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
When in the bootloader, are you typing "fastboot devices" on the computer? "adb devices" will not work at that point.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
When in the bootloader, are you typing "fastboot devices" on the computer? "adb devices" will not work at that point.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes, in the bootloader i am typing "fastboot devices", and nothing appears, comes back to the cursor.

Here's how I did it.
1. Download Nexus Root Toolkit http://www.wugfresh.com/nrt/
2. Install and set the device to Nexus 5x.
3. Click on Unlock Bootloader. It will show you the required steps to unlock. Follow the instructions.
4. If you already have installed adb drivers, it will automatically reboot into bootloader menu.
...
Now here I got the problem 'Fastboot not detected'. I resolve it by doing the following steps.
(While remaining in bootloader menu)
Go into 'Device Manager' ----> There was an icon 'Nexus 5X' but it had a yellow icon so I right clicked ---> update driver --> Browse my Computer --> Let me pick from a list --> Android/Google --> android adb interface --> OK
It will install the required drivers and now then you can simply unlock by following the remaining steps on the dialog box.

Help! Bootloop - no recovery - no usb debugging

I just need to install TWRP

charackthe said:
I just need to install TWRP
Click to expand...
Click to collapse
Boot into Fastboot? If you can't use the unbrick guide, make sure you follow ALL steps or it won't work.

Puddi_Puddin said:
Boot into Fastboot? If you can't use the unbrick guide, make sure you follow ALL steps or it won't work.
Click to expand...
Click to collapse
Booting into fastboot doesn't do anything for me since "adb devices" command shows no device connected even though device is listed under "Android Phone" in device manager (OnePlus Android Bootloader Interface driver is installed)
I tried unbricking guides this (Mega Unbrick Guide) didn't work for mee because the Recovery Tool that has been provided in the thread (Mini and Full) doesn't recognize my device.
My device is listed as Qualcomm *something something* 9008 but it is required to be named "Qualcomm 9008"
1. ADB Doesn't see my device
2. Unbrick guide is useless
What should I do

charackthe said:
Booting into fastboot doesn't do anything for me since "adb devices" command shows no device connected even though device is listed under "Android Phone" in device manager (OnePlus Android Bootloader Interface driver is installed)
I tried unbricking guides this (Mega Unbrick Guide) didn't work for mee because the Recovery Tool that has been provided in the thread (Mini and Full) doesn't recognize my device.
My device is listed as Qualcomm *something something* 9008 but it is required to be named "Qualcomm 9008"
1. ADB Doesn't see my device
2. Unbrick guide is useless
What should I do
Click to expand...
Click to collapse
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.

tnsmani said:
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.
Click to expand...
Click to collapse
Yep you didn't follow the guide properly I believe.

tnsmani said:
First of all, "adb devices" can not be used when the phone is in bootloader mode. The proper command is "fastboot devices". Try that.
Next, the Unbrick Guide has to be followed to the letter. No skipping or changing is permitted. Did you disable driver signing in Win 10?
If the driver is not named as stated in the Guide, you have to change the driver.
Click to expand...
Click to collapse
Puddi_Puddin said:
Yep you didn't follow the guide properly I believe.
Click to expand...
Click to collapse
Guys thanks a lot. I figured this out like an hour before you replied. This was because I was too distracted. I knew both "fastboot devices" and "adb devices" but I've been awake for like 32 straight hours so I never thought of trying "fastboot devices" which is the right one. I've fixed my problem through fastboot.
But Mega Unbrick Thread's drivers weren't showing correctly and yes I disabled that annoying but useful driver signature thing. Thanks for your help!
I hope one day a fellow flashaolic read this and realize he needs to use "fastboot devices".
TL;DR: Device closed? "fastboot devices"
Device on? "adb devices"

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive: