So I've done quite a bit of searching and testing before coming here to post.
I've searched far and wide as well and I seem to be the only one having an issue.
I had read about the NVFlash. Read up on that, and said ok cool let's do it.
So I obtain the files, but initially I discovered I was having an issue on my Linux box getting fastboot to work. I initially got a "no permissions fastboot" reported from 'fastboot devices' Added the udev rules, and then I started getting "?????????? fastboot"
Decided for times sake, I would skip all that Linux stuff, grab the Universal Naked Driver ( which I had done previously to root/unlock my tf700)
Installed said Universal Naked Driver, booted into fastboot mode, and in Windows I get the same exact error... just displayed differently.
I get "? fastboot"
Any ideas?!?!
Thanks in advance for anything
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.
vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Code:
fastboot -i 0x0B05 reboot
(Those are zeroes, not letters. Zero x Zero B Zero 5)
Try that. It should reboot your device just fine. I have also successfully flashed a couple of recovery images and the JB Bootloader using fastboot.
Click to expand...
Click to collapse
This explains it perfectly, I didn't want to move forward until I got that to work, but thanks to you i know now it is just fine.
That reboot command worked perfectly thanks!
vsTerminus said:
'fastboot devices' doesn't work on our tablet (yet).
That said, the other commands should all work fine as long as you remember to pass the vendor ID 0x0B05 to it. For example,
Click to expand...
Click to collapse
Thank you. It worked. This device is "crazy". Hopefully we will get CM10 "stable" in a short time.
Just wanted to clear up that [fastboot devices] works just fine. Not sure why it didn't for you, but I've used it successfully a few times.
Sent from my OGparanoid CM D2tmo
Fastboot not working for me
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?
jdkoren said:
fastboot is not working for my device at all. Neither of the following commands achieves the desired results:
Code:
C:\>fastboot devices
// nothing
C:\>fastboot -i 0x0B05 reboot
< waiting for device >
// stays like this until I cancel the command
I do see the device when I run
Code:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C6OKAS043713 device
To my knowledge, the device drivers were successfully installed. I'm on Windows 7 64-bit, I have the full SDK and all the platform tools installed, and I've used fastboot many times on my HTC Glacier (so it's definitely a working binary). Can anyone help me?
Click to expand...
Click to collapse
Did you boot your device to fastboot mode before you execute fastboot command on your PC?
buhohitr said:
Did you boot your device to fastboot mode before you execute fastboot command on your PC?
Click to expand...
Click to collapse
Hmm, it seems to be working now. Odd that fastboot devices doesn't recognize it, but I guess I can continue without it. Thanks.
Related
I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!
did you reboot your xoom into bootloader mode? (adb reboot bootloader)
does it show any devices when you type
adb devices
Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..
usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )
well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.
Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!
I have a OnePlus running LiquidSmooth (Lollipop edition), which I flashed using my old Windows 7 laptop. I now have a Windows 8 laptop (no access to Windows 7 at the minute), so I have been testing out my ADB and fastboot connections as I'd heard there were issues with Windows 8.1.
I first tested my old HTC One (m7), and installed the drivers as instructed (too few posts to provide a link, but the instructions I followed should come up if you search for Nocturnal ADB Fastboot). Performed a few test commands (adb devices, adb reboot bootloader, fastboot devices, fastboot getvar all, adb push whilst in recovery) and they all worked fine.
I repeated the driver installs for my OnePlus. I'm testing my it now, and adb devices, adb reboot bootloader and fastboot devices all run fine. However, when I try fastboot get var all, I get the following:
Code:
F:\Nocturnal_ADB_Fastboot>fastboot getvar all
all:
finished. total time: 0.001s
You probably notice from the command prompt output that I'm running ADB from a USB; I have also tried from my HDD. I've also tried getvar IMEI and the result is the same.
Could you please advise whether this is a known issue, if I am doing something wrong, or if my ADB/fastboot link is broken.
Thanks!
You're not getting a response from the fastboot getvar all command because it isn't a valid command for this device. Its a valid command for most Android devices but not this one, don't worry, you're not the first person to make this mistake and you certainly won't be the last.
Ah OK, thanks for that!
Is there an equivalent command to get all of the variables? Or what variables can you get from fastboot on the one plus?
Sent from my A0001 using XDA Free mobile app
Unfortunately they've got that information locked down on this phone, I'm not sure why.
Transmitted via Bacon
Oh well, it wasn't important I was just checking my setup. Thanks for your help.
Sent from my A0001 using XDA Free mobile app
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
grimsonfart said:
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
Click to expand...
Click to collapse
Wrong command!
You can't flash whole ROM blob on 'system' (i.e. OS) partition because ROM blob contains bootloader, partition table, recovery, kernel, system and userdata, which are to be flashed to other partitions.
Therefore our Transformers have a 'ramp-up' partition called 'staging'. On reboot bootloader flashes the 'sub'-blobs of blob (blob.EBT, blob.SOS, blob.LNX, blob.PT, blob.USR) to their respective partition.
Use:
Code:
fastboot -i 0x0b05 flash [b]staging[/b] blob[enter]
fastboot -i 0x0b05 reboot [enter]
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
grimsonfart said:
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
Click to expand...
Click to collapse
This should work! However it will last along time. When tab reboots, you will see a blue progression bar, which sometimes seems to freeze. Let tab restart by itself.
If you don't succed, you might have a corrupt blob, either by downloading or by unzipping with an outdated winrar (suffered that myself).
Well, no luck first time. Exactly the same thing happened when using that command in CMD. Not sure if it's a problem with my PC or what... Going to re-download the files from ASUS.
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
I am doing this one a really old computer though (no access to mine atm). It's windows XP SP3, 1gb ram and intel celeron 1.8ghz i think. Not sure if it has anything to do with this but anyways.
grimsonfart said:
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
Click to expand...
Click to collapse
When you flash to staging, bootloader copies blobs to their partitions after reboot, while this happens, a blue progression bar is visible on ASUS Screen not on bootloader screen.
As you report it, you are probably not in fastboot mode.
Try to follow:
1. Press power + vol down -> bootloader screen appears with icon RCK blinking. Now you are in fasboot mode.
2. Connect tb to pc; tab should show up in Win's device manager as ASUS fastboot device(o.s.). If warning sign appears or 'unknown device' label, install proper drivers.
3. Open terminal window with admin permissions in fastboot folder.
4. Type
Code:
fastboot devices [enter]
-> device should be shown; if not: type
Code:
fastboot -i 0x0b05 reboot [enter]
tab should now reboot into OS; if not, fastboot doesn't work.
5. Try procedures 1. to 4. with every single USB port available. If no success try different pc (normally WINXP is no deal breaker, Win 8.1 sometimes might be).
6. Report.
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
grimsonfart said:
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
Click to expand...
Click to collapse
Glad to be of any help.
You might add to your OP tag [Solved]
I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.
xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!
Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything
Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.
Hello, today I finally received my one plus 6. Been loving the device so far
I was on my way to Chuck a custom recovery and rom unlocked the bootloader no drama
I then hit a Plato of fastboot coming up with no command error as in fastboot isn't working in cmd I have researched heaps about it and I can not find a single thing. I tried to reinstall drivers and all that, and yes I'm running cmd in the fastboot files, only adb seems to be working but I can no longer use fastboot on my PC.
Has anyone come across this error, it seems to be that after installing the one plus drivers it stopped working correctly and fastboot commands no longer register in fastboot...
My phone is detected in fastboot mode so it's not the drivers. What could be causing this, is it the computer at fault?