[Q] need help unbricking nexus 7 - Nexus 7 (2013) Q&A

okay, so i tried to return my rooted nexus 7 to stock using wugfresh toolkit. for some reson it failed when flashing to stock and locked the bootloader. now whenever i try to unlock the bootloader to flash stock manually i get this...
[email protected]:~$ fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (No such device))
finished. total time: 31.426s
[email protected]:~$ fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (No such device))
finished. total time: 121.599s
[email protected]:~$ fastboot oem unlock
Anyone have any suggestions? i have tried multiple usb cables and multiple computers. also it is not recognized by windows but fastboot is recognized in linux.

Get to a windows laptop. Boot to fastboot. Go into control panel, device manager, find the tablet connected to the computer. Download the latest Google USB drivers and unzip them. Right click the device in device manager, click update driver. Click find on my computer, and navigate to the folder with the drivers you unzipped. Click OK until they are installed.
Open cmd as admin. Try again.
If that doesn't work, do the same thing, but instead of have driver on my computer, select choose from a list of installed drivers, and choose Android ADB USB Interface. Click OK to the warning and install the driver. Open cmd as admin again and try it.
One of those should work. Had the same problem and that's how I fixed it.

SwoRNLeaDejZ said:
Get to a windows laptop. Boot to fastboot. Go into control panel, device manager, find the tablet connected to the computer. Download the latest Google USB drivers and unzip them. Right click the device in device manager, click update driver. Click find on my computer, and navigate to the folder with the drivers you unzipped. Click OK until they are installed.
Open cmd as admin. Try again.
If that doesn't work, do the same thing, but instead of have driver on my computer, select choose from a list of installed drivers, and choose Android ADB USB Interface. Click OK to the warning and install the driver. Open cmd as admin again and try it.
One of those should work. Had the same problem and that's how I fixed it.
Click to expand...
Click to collapse
problem in windows is fastboot devices doesnt show up my tablet in cmd, fastboot isnt even a command even though i have all the drivers and adb..

You need to open the command prompt window in the directory the fastboot files are in unless you set it up as a global variable. Hold shift and right click in the folder where the fastboot files are and select open command prompt here.

SwoRNLeaDejZ said:
You need to open the command prompt window in the directory the fastboot files are in unless you set it up as a global variable. Hold shift and right click in the folder where the fastboot files are and select open command prompt here.
Click to expand...
Click to collapse
yea i got it to work but its still stuck on erasing user data

Is anything happening on the tablet?

SwoRNLeaDejZ said:
Is anything happening on the tablet?
Click to expand...
Click to collapse
its just still at the unlock bootloader screen

Did you press the button to select yes? Sometimes, you have to really mash the thing to get it to register.

yea..its been erasing user data for 45 mins in cmd and still on unlock bootloader

well after all the waiting it failed again..it said FAILED <status read failed <too many links>>

You are not alone. Many users including me having same problem. Can't unlock bootloader. No one has fix for it yet.

This is why I don't use toolkits and never recommend them either.

nhizzat said:
This is why I don't use toolkits and never recommend them either.
Click to expand...
Click to collapse
All toolkits do is send terminal commands to automate a process. They are perfectly safe to use and can often save time and headaches.

I'm in the same situation as others here and created a post on the Google help forum because I've not seen Google respond to this issue.
https://productforums.google.com/forum/m/#!category-topic/nexus/nexus-7/lJxoEm1LvMg

Related

[Q] Flash back from IMM30B to 4.0.2 for new leak

Hey guys, first time on here and im kinda a noob when it comes to the rooting stuff (ive done a few things but nothing hardcore) and i need some help getting onto this (IMM76K) update (and not sure if this is the right thread to put this in). A few weeks ago i unlocked my bootloader and (after some of the same issues im having now) temp booted into CWM and installed the 4.0.4 IMM30B update. Now with this new update, i wanted to get it installed or flash back to get the OTA (not sure if i can get the OTA on the leak update)
But, everytime i try to boot into CWM again (using this toolkit: http://forum.xda-developers.com/show....php?t=1614827) i constantly get fail messages. And it happens if i try to boot into CWM or try to flash the factory 4.0.2 update.
With the phone on and trying to use these (http://www.droid-life.com/2011/12/16...factory-state/) instructions, i constantly get the error "sending 'bootloader'... FAILED (remote: Invalid Command)". Im already in the fastboot bootloader.
With the toolkit, it wont start the factory img flash if the phone is on, and if im in the fastboot bootloader, it says it "fails" to boot into the bootloader (which, again, im already in) and fails to install all the img files and then just boots back into the older 4.0.4 leak.
I havent rooted my phone (but i tried that to get past this problem but i get the same error messages), only unlocked the bootloader. Sorry for the long post and if it seems like a block of text. This is just starting to really frustrate me. Thanks
Do you have ADB installed on your computer? It's hard to troubleshoot your problem if you don't.
Yea, i do. Im in school for programming and have installed all the android SDK stuff and eclipse since i want to make android apps/games (hopefully). I downloaded the fastboot.exe file and have it in the platform-tools folder with the adb.exe file
Go here (https://developers.google.com/android/nexus/images) and download mysid for Gnex.
It's gzipped so you will need to extract those files using 3rd party software (winzip works nicely).
Boot your phone normally. Connect to your computer and open a command prompt.
Type 'adb devices' and note the result.
Type 'adb reboot bootloader' and wait for the phone to enter the bootloader.
Once there type 'fastboot devices'.
If you don't get a response you have a driver problem. You need to DL the samsung driver.
If you do, flash each zip file in that package you DL'ed from google.
Start with 'fastboot flash bootloader <location of bootloader zip>'
Then, 'fastboot flash radio <file>'
ect. until you've flashed all the zip files. (Exactly like the instructions in your link but replace the files they gave you with the ones from google.)
Post here if you get an error message.
Ok, everything is fine until i get to flashing the bootloader, heres what i get (sorry it isnt an image)
D:\Android\android-sdk\platform-tools>adb devices
List of devices attached
0146A5B30300B014 device
D:\Android\android-sdk\platform-tools>adb reboot bootloader
D:\Android\android-sdk\platform-tools>fastboot devices
0146A5B30300B014 fastboot
D:\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-
primekk15.img
sending 'bootloader' (2308 KB)... FAILED (remote: Invalid Command)
finished. total time: 0.001s
D:\Android\android-sdk\platform-tools>
This is what happens even when i use a toolkit to do it for me. Ive used the toolkit to reinstall the drivers a bunch of times and it still happens
Did you relock the bootloader? Type 'fastboot oem unlock'
---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------
If that's not it then it's a driver issue.
Uninstall the ones you have (Control Panel -> Device Manager) and go to http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW? and install the samsung ones.
If you have problems with that I can walk you though it.
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
blipp said:
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
Click to expand...
Click to collapse
1) Throw away the toolkit;
2) Uninstall all drivers;
3) Install these drivers;
4) Make sure your bootloader is unlocked;
5) Open a command prompt in the directory where your both your fastboot file and CWM are located;
6) Reboot your device into fastboot mode (vol+ & vol- & power), and plug into your PC;
7) Make sure your device is recognized by your PC: fastboot devices
8) Flash or boot CWM
a) Flash by typing: fastboot flash recovery cwm.img
b) Boot by typing: fastboot boot cwm.img
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
blipp said:
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
Click to expand...
Click to collapse
Extract the zip to a directory. Plug your device in fastboot mode to your PC. Open device manager and find the phone. Right-click on it and select update driver. Select install yourself or whatever the option is, and navigate to the folder where you extracted the zip. I've found that those drivers are better than the Samsung-packaged drivers.
Also, do one or the other, but not both. Make sure you remove the old driver before you start the new.
In windows 7 you're gonna want to go to (install Universal Naked Driver)...
Control Panel -> Hardware and Sound -> Device Manager
In the list click the driver for your phone. It will either be in the USB list or listed as some kind of phone. Right-click and uninstall the driver. Reboot. Go back to device manager. Plug in device. Click update driver software when your device shows up. Then 'Browse my computer'. Then 'Let me pick from a list'. Then 'Have Disk'. Find the .inf files and windows will install the driver.
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
blipp said:
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
Click to expand...
Click to collapse
What OS are you running on your PC?
Windows 7
blipp said:
Windows 7
Click to expand...
Click to collapse
Ok, try this: go into the directory where you unzipped the drivers. Right-click on android_winusb.inf and select install.
Get an error popup - "The INF file you selected does not support this method of installation"
blipp said:
Get an error popup - "The INF file you selected does not support this method of installation"
Click to expand...
Click to collapse
Hmm. Not sure what is going on.
Let's try this step-by-step:
Boot your device into fastboot mode, plug into your PC, and open up device manager. Does your PC recognize your device? What does it show in task manager?
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
blipp said:
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
Click to expand...
Click to collapse
Ok, good. Now right click on the Android 1.0 and select "update driver software". Then click on "browse my computer for driver software", then click on the "Browse" button and make sure "include subfolders" has a check.
Now navigate to where you unzipped the drivers and click ok.
Its not giving me that option. Its not in device manager, its only showing in control panel->hardware and sound->devices and printers. Right clicking only gives me Eject, Create shortcut, troubleshoot, and properties. Properties only has General and Hardware. I even went into device manager and checked "show hidden devices" and its still not there. It only shows up now when its actually booted into android
Sent from my Transformer using XDA

commandprompt does not work

Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastboot getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Joheee said:
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastbood getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Click to expand...
Click to collapse
Probably just a typo, but you wrote 'fastbood' in your post. Computer definitely won't recognize that. If you are spelling it right, either 1) you're in the wrong directly in terminal, (cd /(wherever adb is installed), or 2) adb package didn't install correctly, (reinstall). While you're testing it, you can just type 'fastboot', and you should get a list of command options, showing that it is installed.
Sorry yes fastbood was a typo. But what do you mean with: you're in the wrong directly in terminal, (cd /(wherever adb is installed).
A terminal is the same as a command prompt right?
And to reinstall adb package, i would have to delete the platform-tools right? And when i click on delete package, it asks if Im sure about it, bacause it can not be undone.
When you open command prompt, you're 'in a directory', usually in Windows, it's C:/(user)/desktop, or something. You need to get to the directory where adb is. If you installed it with defaults, it's probably C:/adb. If so, once you open command prompt, type 'cd /adb', and hit 'enter'. Then you'll be 'in the right directory'. If adb installed somewhere else, you'll have to find out where, then type 'cd /(whatever)/(whatever)/adb.
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Joheee said:
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Click to expand...
Click to collapse
First thing you have to do is find out where on your PC the adb files are. The computer won't recognize anything you type with fastboot, adb, etc., unless you're in that directory. I believe adding the environmental variable path is supposed to make that easier, but obviously it's not working out for you, so I would just skip that and find out where the files are, then you can just use 'cd', and go there. It should be easy to do a search in Explorer if you can't find it.
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Joheee said:
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Click to expand...
Click to collapse
Can you tell me what directory on your PC the adb files are located? As far as drivers, best bet is usually PC companion, or Flashtool.
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Joheee said:
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Click to expand...
Click to collapse
If PC Companion is giving you that msg, you might be OK w/ drivers. With that being the location of your adb files, you would open command prompt, and type - cd \Users\BTO\AppData\Local\Android\sdk\platform-tools\adb - then you'll be 'in' the right directory, (just to make sure, look in the 'adb' folder and see if fastboot exe is in there). Your command prompt should show - C:\Users\BTO\AppData\Local\Android\sdk\platform-tools\adb. Then type 'fastboot', and you should get output of command options.
If all goes well and you want to make it easier in the future, just move the whole 'adb' folder to C drive root. Then you'll only have to type 'cd \adb'.
Or you could just open a window in the correct directory, hold right shift button on keyboard and click right mouse button and select "open command prompt here "
Easy peezy
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Joheee said:
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Click to expand...
Click to collapse
Sorry i missed that... How about Flashtool driver installer? If you DL Flashtool, there's an exe in the 'drivers' folder that will install for you.
Hey you might be using windows 10,8,8.1 if so follow this guide http://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114
All The Best
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Joheee said:
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Click to expand...
Click to collapse
Try different files. Here's a boot IMG that I've used successfully - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM - and try this for recovery - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
Use 'fastoot devices' before flashing to confirm connection.
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Joheee said:
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Click to expand...
Click to collapse
The boot and recovery files will just enable you to get into recovery. You'll need a ROM file to put a ROM on your phone. There are many to choose from in the 'android development', and 'original android development' threads. To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img'). Then you can reboot into recovery. Once you download your ROM file, you want it to be on your SD card in the phone. When you get into recovery, you go to your ROM file and install.
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 40 minutes on the blue 'waving' startscreen, and getting quite hot even.
Click to expand...
Click to collapse
If your phone is stock, it won't boot with the new IMG you flashed. That's also why the computer doesn't recognize it. You can copy your ROM onto the SD card with your computer, using a card reader or adapter. Just flash both IMGs, then unplug, then turn it on, and hit vol up when you see purple. Make sure you type flash 'boot' for the boot, and flash 'recovery' for the recovery, not 'boot' for both. Also, if you want, there are custom IMG files with recovery on xda for stock ROM that you could flash the same way, if you just want to use your stock.
---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Click to expand...
Click to collapse
Try this for stock - https://mega.nz/#!k0cTUQbS!5XUZhTEK4xBKVBSeO83TEHE3xs9JEpvxt3g1Sc8tVH8

Help rooting & installing cyanogen mod on H811 10n

Hey folks, first time poster. I've been lurking all day trying to find answers to some of my questions and haven't gotten very far. I know there are several threads related to many of the issues I'm having, as well as instructions for getting cyanogen on my G4, but none of them seem to address the problems I'm having directly or in a way that makes sense to me.
My iPhone 6+ succumbed to bendgate yesterday, and I picked up a new LG G4 from TMobile this morning. My plan was to root it and have cyanogen installed in an hour or two, and here I am nearly 12 hours later at my wits' end. I jailbroke my iPhone, but I've never rooted an Android device, so I apologize for my relative ignorance in advance.
I'm trying to follow the instructions from cyanogenmod.org (I can PM a link to them, but can't add to this post because I'm a new user), but I've only managed to get as far as step 6. When the G4 is in fastboot mode (put there manually or with adb), it can't connect to my Windows PC; <fastboot devices> doesn't even return an error.
I read that it was probably a driver issue, so I installed many different drivers over several hours: Intel USB drivers, LG USB drivers, new ADB drivers through the Android SDK & then the 15-second install tool found here on xda. I also read if the device is throwing some kind of driver error in the device manager, as my G4 seems to be doing when it's in fastboot mode indicated by the yellow warning sign, you can force install the correct drivers for it. But when I tried to do that, Windows doesn't show me any of the ADB drivers I want to install (though I know they're installed on the machine because they're visible in the device manager when the device is connected normally rather than in fastboot mode) - all the options are MTP drivers.
So, I'm stuck and frustrated. I've tried three different USB cables, every USB port (some 3.0, some 2.0) on my machine, disabling driver signature verification, rebooting the phone and the PC at various junctures, all in different combinations. I just don't know enough about this to be able to fix it myself, and scouring the internet hasn't yielded anything helpful yet.
If anyone here at xda could be so kind as to help me stumble through this process, I'd be very greatful! I'm sure there's information needed that I didn't think to supply, I'll try to answer requests for more information ASAP. I have screenshots, but as I'm a new user I can't post them - I can PM links. Thanks in advance!
ADB/Fastboot issues are a pain in the a** to detect and resolve. Before going any further, I'd recommend you try it on a different PC. If you can, just do the following:
Install "LG BRIDGE" to get the correct and latest drivers.
Install "15 Second ADB Installer". Be sure to use Version 1.3 as 1.4.3 is known to have issues.
Before connecting your G4 to your PC, got to Settings\Developer Options\ and enable "Allow OEM Unlock" and "USB Debugging".
Connect your G4 to your PC via USB.
Open Command Prompt (CMD). CD to the ADB/Fastboot directory, or: Go to C:\adb\, hover your cursor anywhere on the white space in within the ADB/Fastboot folder, hold shift and press the right mouse button. Now choose "Open Command Promt Here".
Type adb devices
A pop-up will appear on your G4. Click "Always Allow From This Computer" (or something similar) and allow the ADB connection.
Proceed the tutorial on CM Wiki on how to install CyanogenMod on the H811.
If you don't have access to another PC, remove/uninstall all G4 related drivers. Remove any traces of ADB from your PC and proceed at step 1 as described above.
Let us know if it did work.
Hi nitrous, thanks for responding. I appreciate you taking the time to help me out.
I went through the steps you outlined here on my Windows 10 (x86 this time) laptop, but still no go. When I try <fastboot devices>, cmd prompt still returns nothing.
When I enter bootloader mode on my G4 and connect it via USB, LG Bridge doesn't recognize the phone (I'm not sure if it's supposed to) and in device manager under Portable Devices the G4 shows up but with an error (which I'm sure it probably should not be doing).
When I try to go to Update Driver Software > Browse > Let me pick from a list of devices on my computer, Windows never allows me to "Select your devices type from the list below" -- it just skips that step entirely and goes right to "Select the device driver you want to install for this hardware" -- and even when I uncheck "Show compatible hardware," the only drivers I'm able to choose are MTP- or WPD-related.
Any further suggestions I can try?
edit: Actually, I've decided to upgrade to MM and follow the [STOCK][M][TMO] H811 20i Images + KDZ + Flashable Zips + OEM Unlock process instead. I'll come back with updates once I'm finished.
update: works like a charm after upgrading to MM.
Spoke too soon!
fastboot IS working, but I'm stuck at this error when trying to flash the recovery with the twrp img:
c:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (33004 KB)
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.784s
jdeviant said:
Spoke too soon!
fastboot IS working, but I'm stuck at this error when trying to flash the recovery with the twrp img:
c:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (33004 KB)
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.784s
Click to expand...
Click to collapse
No, that's not how you're supposed to flash TWRP on the G4.
- Save an img of TWRP anywhere on your int. or ext. storage.
- Upon booting into download mode, type the following:
Code:
[B][FONT="Courier New"][COLOR="Indigo"]fastboot boot twrp.img[/COLOR][/FONT][/B]
After a couple seconds, TWRP should fire up. Here, press "Install" and press "Install Image" in the down right corner. Still in the same menu, navigate to the location where you have already stored an image of the latest TWRP.img. Click on it. IMPORTANT: Immediately after pressing on the img file, a menu will pop up. It's important to choose "Recovery" (obviously). Swipe to confirm Flash. And Bob's your unc... who the F is Bob, anyway?!

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:

Corrupted Pixel 2 XL

I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse
Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.
5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!

Categories

Resources