I got an N7 about a month ago on sale and the first thing I did was unlock the bootloader. I decided I was going to use it as a "learning" tablet. (I'm still in learning mode, with aspirations of dipping my toes into development - that's a ways away, though.) I flashed TWRP followed by a couple of roms, and then I decided I was going to test my ability to flash a factory image. So I flashed 4.4 (this was last week before the 4.4.2 images went up). And since I was on the back on the OTA path, I figured, "I have an unlocked bootloader. What's the worst thing that could happen if I took this update?" So I did.
And now I'm confused. If I remember correctly, with 4.2.2 (what it came with out of the box), the bootloader had an option to run in "fastboot mode." In 4.4.2, my options are basically Dead Android screen or (if I power+vol up):
Reboot system now
Apply update from ADB
Wipe data/factory reset
Wipe cache partition
Fastboot stopped recognizing my tablet (adb still works, though not in recovery - I didn't think it was supposed to, so I'm surprised to see it as an option). I know there were issues in the past with the USB drivers on x64 machines, but I've tried on both 32-bit XP and 64-bit Win 7 and both machines will recognize that there is an N7 when booted normally, but say there are issues with the drivers when booted into recovery. I searched and saw people using pdanet as a workaround for installing the USB drivers, but those posts were largely from 2011/2012 timeframe - I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat? Even so, ADB doesn't recognize my tablet in recovery, so even if I wanted to sideload something I can't - did Asus release newer USB drivers that I should be using?
Any help anyone can provide would be greatly appreciated.
Thanks!
miss_sticks
miss_sticks said:
I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat?
Click to expand...
Click to collapse
Are you sure to have updated all the drivers for your N7 after update of your SDK?
Weird thing about N7 is that one sometimes needs to re-installi all the drivers after flashing of another firmware. I've flashed a factory image (4.3) via fastboot on two N7s within the same hour. First N7 had 4.2.2 before, After flashing 4.3 on it, I took another N7 with 4.2.0 and- I had to re-install the drivers.
I never had such a situation with Samsung devices.
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
tetakpatak said:
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
Click to expand...
Click to collapse
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
miss_sticks said:
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
Click to expand...
Click to collapse
OK, cool. Don't be ashamed, one just has to learn it
From that point on, (as you are in fastboot mode) your each prompt must begin with
Code:
fastboot (.....)
instead of "adb"
Related
So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device
When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?
I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.
If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.
Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.
I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.
ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.
I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium
Delete
After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.
Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
TreatnHerRight said:
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
Click to expand...
Click to collapse
That looks great ... and uses Windows only
I can boot Windows under VMWare Fusion on my MAC however not 100% sure if that would work within that environment as I need to do some USB passthrough.
Thanks for the pointer though.
ilmoomino said:
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
Click to expand...
Click to collapse
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
nic0lette said:
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
Click to expand...
Click to collapse
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
ilmoomino said:
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
Click to expand...
Click to collapse
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
nic0lette said:
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
Click to expand...
Click to collapse
I am using VMWare Fusion since my Windows work laptop is dead (courtesy of lost charger).
So I must use my Mac (which used the CM installer where things went sour).
Doubt it is a problem since I can get ADB to work.
I have already dowloaded the Android SDK Platoform-tools and stock 4.4.4.
I used ADB on MAC, but after I copy the ROM the phone does some scroll-bar progress, then I clear partitions/factory erase/cache ... and boot loop again.
I will follow your advice and use the described process.
You are right - as long as I have bootloader I am safe.
Might go and buy Moto X+1 or Sony X3 ... as I want to go 4G but thought might use the N4 for another few months.
thanks
following instructions from nic0lette I have now my phone back to normal ...
will try CM using the same instructions ... well, using the flash-all.sh as a base script
thanks (and "thanked")
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse
cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"
dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?
WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!
For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.
Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Also, if you have USB 2 ports, try one of those. I couldn't get anything to flash when I had it plugged in one of my USB 3 ports.
Could be cable issue, USB port issue, driver issue or you can try updating your adb setup etc... I used the Minimal ADB and Fastboot. Mine was out of date and wouldn't recognize device in fastboot after the Oreo sideload.
Works perfectly with the Essential official drivers in Win8.1Pro now.
The cable is brand new by anker, and works perfectly. Drivers and adb are updated.
mrcooter said:
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Click to expand...
Click to collapse
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
basongwe said:
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
Click to expand...
Click to collapse
Something that was odd that may help (assumed it was just my environment setup). I had adb installed to C:\adb and only way fastboot will work consistently for me is to run commands from that directory. Could be unrelated but thought I would mention it.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Try copying fastboot to the folder that has the flash all.bat
What operating system?
Where did you get your driver's?
Reason I ask is at first I had driver's auto install from a Samsung device that I used previously. Caused an issue where it wouldn't start the fastboot process and device got stuck at first step.
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
vergilbt said:
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
This also did the trick for me
You're welcome...
Edit : I have it(drivers from essential website)
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
That did the trick.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
un1ocked said:
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
Click to expand...
Click to collapse
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
kt-Froggy said:
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
Click to expand...
Click to collapse
fastboot version 28.0.3-5475833
Installed as C:\Program Files (x86)\Essential\ADB\fastboot.exe
EDIT:
problem solved by switching to an old PC with a pure usb 2.0 port
un1ocked said:
problem solved by switching to an old PC with a pure usb 2.0 port
Click to expand...
Click to collapse
Ahh... Yeah, that's often the issue. Still doesn't make a lot of sense to me, because your error msg was "unsupported option". Well, good that it worked for you.