fastboot mode generates usb error 43 (solved) - Nexus 7 Q&A, Help & Troubleshooting

Hi
I was recently having trouble activating fastboot mode on a Lollipop nexus 7 (2012 wifi). The Windows device manager reported error 43 most of the time and occasionally error 10. Since it couldn't identify the device It wouldn't allow installation of the correct drivers. I didn't have a custom recovery rom installed, and the default recovery was failing to install updates via adb sideload xxxxxxxxx (Which I didn't fix).
The solution I was to plug it into a powered usb hub. Afterwards it was initialized correctly as a android bootloader, and fastboot worked.
I hope this helps somebody, It took me many hours of frustration to figure out.
credit for the idea goes here - pcsupport. about .com/od/ findbyerrormessage/a/code-10-error .htm (I don't have enough posts to post links)

Related

Another Can't boot after unlock and twrp install

I'll try to make this brief and to the point as I realize how many people come here seeking help.
I've rooted many android devices (my first was an htc incredible) so I'm not exactly "new" per say, but don't really fully understand what I'm doing either long story short.
Got my nexus 7 today, tested some things with the screen when I first got it (just playing videos to see how bright it is)
I Followed a video suggested (somewhere) on the forums (video here (but I can't post urls))
-Sat down, got the usb drivers from here - Can't post link
-got adb fast boot tools - can't post link
-Downloaded SuperSU
-Enabled usb debugging in settings
-Booted into recovery
-Updated Driver when prompted
-allowed usb debugging after entering adb devices command
-used adb reboot bootloader command
-used fastboot oem unlock command (worked succesfully)
-used flash recovery openrecovery-twrp-2.6.0.0-flo (personally I think it didn't flash correctly because I don't know how to explain issues I will detail below
- (unless this is where I went wrong) rebooted to get into os so I could place supersu.zip on internal storage for rooting
- sticks at glowing X
ADB won't recognize the nexus 7 in recovery or bootloader
Windows only sees the nexus 7 as either
QHSUSB_DLOAD
MTP USB Device
flo
I've tried wiping from recovery, it fails.
I DO seem to be able to get adb to recognize the tablet when it is in recovery mode now.
Adb lists
06d9e78e Recovery
I've tried reflashing Twrp, still can't wipe, Is it possible for me to just install kitkat from recovry straight from adb or fastboot? It's been a while but I was thinking if I could just reset the os it might work. I have razor-krt16s-factory-7235eb0d.tgz ready to go I just don't know how to put it on the tablet without an sd card to transfer with
I have also installed Wugs Nexus Root Kit but since I have no idea what build of 4.3 my n7 is running...it really isn't doing me any good -_-.
any help would be appreciated, I'm stumped but will be continuing to dig for answers.
Thanks

Sideload issue

Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10
I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.
Can't anybody help us?
Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

"Waiting for any devices" with Moto G4

Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message 
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!

Need help

I have nexus 7 2012 wifi. Its most recent update had some bugs so I tried to reinstall an older firmware using adb (i got the firmware from google website). The tablet entered a boot loop during installation and the adb (on ubuntu terminal) gave me an error so I disconnected it. The device is now off when I try to turn it on (or even into recovery mode) the screen doesn't turn on, the device gets hot and I hear some strange noise from the PCB. I think I destroyed the bootloader or something like that. when I run the command ($ lsusb )on the terminal the device is recognized as Nvidia device (but adb doesn't detect it). any help?
IS there any way to install firmware without detecting the device?
Thanks in advance.
If it is being recognised as an Nvidia device it's possible that it is now in APX mode, and if that's the case, you can reflash the bootloader with a tool called NvFlash. There is a (Windows) tutorial here: https://android-forums-app.blogspot.com/2016/03/tutorial-how-to-unbrick-nexus-7-using.html
I vaguely remember having to flash the bootloader like this because the tablet was dead but I don't remember using wheelie or blob.bin, only NvFlash.
You can get the latest bootloader from here, for a Wi-Fi model you will need the grouper file: https://forum.xda-developers.com/showthread.php?t=2417097

PC fastboot recognition issue

Today i tried to install a custom ROM update which caused a softbrick and now my device is stuck at the logo. I naturally decided to flash a stock rom in order to solve this. I went ahead and downloaded a MIUI 11 global stable one, next was rebooting into fastboot and connect it to my PC...
...When i rebooted my phone into fastboot, my PC didn't recognize the device at all. Device Manager says "USB Unknown Device (Device Descriptor Request Failed)". I verified the USB port and cable works properly with another phone, i installed USB drivers and ADB/fastboot ones, still nothing.
Is there anything I'm missing? I'm not very adept at these topics, I previously flashed mine into a PE custom ROM purely by following tutorials mindlessly.
Try the app "Xiaomi ADB/Fastboot Tools", this has the option to flash stock ROMs. The USB drivers that I have installed on my computer are "minimal ADB Fastboot 1.4.3".
You could also solve the problem with the tool "MiFlash Pro".

Categories

Resources