When i tried to Boot from recovery mode i got Error message with no command.. none of those option in recovery mode working. My phone is UN rooted running on official 4.3 Jellybean. Is this only i m getting? or because my phone is unrooted its locked?
Some Assist would be nice thank You
try using ADB commands:-
connect your phone using usb cable (with usb debugging enabled in developer options)
open command prompt (windows)
if you have ADB as environmental path then just type "adb reboot recovery"
else you need to navigate to the adb.exe and then type the upper command.
it worked for me
can u link where can i download ADB tool
i've attached the latest ADB version 1.0.31 (don't use older versions as they wont work on our device)
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
As it says. I've used this cable to unlock/root my HTC M9, and the Win10 machine I have shows the Shield's storage when connected. However, neither ADB nor Fastboot are connecting. Error message says 'Error: device not found" or something like that. What am I doing wrong?
Disregard. Had to install the device drivers for Win10 from Nvidia.
adb reboot bootloader works but not fastboot oem unlock
I can reboot bootloader and get to the fastboot menu, but the fastboot oem unlock command does nothing, the command window simply says "waiting for device".
When I go to device manager on my PC to change to the Nvidia drivers, windows says I already have the best driver installed.
Any ideas what to do to get this working properly? Is the "hardware method" better somehow?
Thanks.
BillTheCat said:
As it says. I've used this cable to unlock/root my HTC M9, and the Win10 machine I have shows the Shield's storage when connected. However, neither ADB nor Fastboot are connecting. Error message says 'Error: device not found" or something like that. What am I doing wrong?
Click to expand...
Click to collapse
OK, so I am at a loss. I have installed Android Studio, SDK Manager and updated everything I can think of, plus everything that any developer on the web says should be updated. I have checked that the drivers are updated, but every time I try to sideload the latest OTA for my Nexus 6P I get the message "error: no devices/emulators found."
I have done the following:
a) USB debugging is enabled under Developer Options on the device
b) When I execute "adb devices" it shows the device
c) When I execute "adb reboot recovery" it reboots into In recovery
d) I then choose "select update from adb" on the device
e) And then try to execute "adb sideload angler-ota-nrd90u-ffef6b27.zip" only to be given the message that its loading and then "error" no devices/emulator found"
I have searched the web and tried all of the "fixes" and still cannot get the OTA to load, currently tried about 10 times and all have ended up needing to just reboot the system. Does anyone out there have any ideas of the problem and a solution? I have seen several forums that show others with the same issue, but none seem to verify if they have been able to correct the problem. Currently updated to Nougat through the beta program, but my devices shows that I am on NRD90M, which according to the Nexus Files for Developers is for the "ryu" for Pixel C?
Really would like to update the OS to the latest security patch prior to the October date, can anyone help?
There are different drivers for Fastboot and Recovery modes. Once your phone is in Recovery, execute "adb devices", if the phone is not listed there, go to Device Manager in Windows and install the driver.
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
I finally found a solution, had to do a lot of research but basically I needed to wipe the cache partition. Here is the site that shows you what to do.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
Currently my device is updating and is at about 75%! Success!!!
AP_Nex said:
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
Click to expand...
Click to collapse
This is exactly what worked for me. Happened twice and this fixed it twice.
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.