I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
When connected to my windows laptop, it says "ASUS Android composite ADB interface" in device manager when booted normally. And it says "AsUS Android bootloader interface" when I'm supposedly in fastboot.
thanks
mrjayviper said:
I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
thanks
Click to expand...
Click to collapse
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
_that said:
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
Click to expand...
Click to collapse
just says waiting for device.
tried:
1. fastboot continue
2. fastboot -i 0x0b05 continue
3. the nvflash command above
4. fasboot reboot
5. fastboot -i 0x0b05 reboot
I was on 4.0.3 ICS before unlocking and I suppose still on 4.0.3 just unlocked. thanks!
Related
So I just bought this tab. And stupidly upgraded to JB right away (not a big fan with first impression) and was following the 3 step guide for recovery and root on JB. Starting on step 3
When I reboot into bootloader from advanced, or manually (power + V down, then V down to navigate to USB sign, V Up to confirm (already unlocked bootloader of cource)
In the top left corner where the words are, the last line says "starting fastboot mode" or something like that, but nothing just stuck in the bootloader screen with 4 options RCK, ANDROID, FASTBOOT, AND WIPE DATA. Untilled I hold power to reboot.
Tried several times. What am I doing wrong?
trevor7428 said:
So I just bought this tab. And stupidly upgraded to JB right away (not a big fan with first impression) and was following the 3 step guide for recovery and root on JB. Starting on step 3
When I reboot into bootloader from advanced, or manually (power + V down, then V down to navigate to USB sign, V Up to confirm (already unlocked bootloader of cource)
In the top left corner where the words are, the last line says "starting fastboot mode" or something like that, but nothing just stuck in the bootloader screen with 4 options RCK, ANDROID, FASTBOOT, AND WIPE DATA. Untilled I hold power to reboot.
Tried several times. What am I doing wrong?
Click to expand...
Click to collapse
Hi,
you are doing everything fine....
It just stays there when "starting fastboot mode" appears!
Now you can open a terminal on your pc.
When you enter "fastboot devices" (without quotes), a number will appear so you know the device will be recognized when you want to flash recovery. Just like "adb devices".
Do you have to enter fastboot devices first to flash recovery threw adb?
Cause last night after it said starting fastboot (when I thought it was stuck)
I extracted the twrp Jb recovery from same post. To the same folder as adb.exe and fastboot.exe (named the folder fastboot on the C drive) shift + right click on fastboot folder - open in command prompt
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
The responded was like can't complete command. File or folder doesn't exist (or something like that, will try again when I get home with the exact response)
And tried extract to a folder named, recovery1 on my c drive
C:\recovery1: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Still with the same response
Thank you for the help
trevor7428 said:
Do you have to enter fastboot devices first to flash recovery threw adb?
Cause last night after it said starting fastboot (when I thought it was stuck)
I extracted the twrp Jb recovery from same post. To the same folder as adb.exe and fastboot.exe (named the folder fastboot on the C drive) shift + right click on fastboot folder - open in command prompt
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
The responded was like can't complete command. File or folder doesn't exist (or something like that, will try again when I get home with the exact response)
And tried extract to a folder named, recovery1 on my c drive
C:\recovery1: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Still with the same response
Thank you for the help
Click to expand...
Click to collapse
Try fastboot -i 0x0b05 flash recovery C:\recovery1\tf300t-jb.blob
Thank you so much, that did the trick
Hi,
I just unlocked my bootloader with v8 on the latest OTA update. I rebooted into the bootloader, and ”fastboot devices" returned mine just fine. Then I ran "fastboot -i 0x05B0 flash recovery twrp.blob" with the latest 2.6.3.2 version, but it has been about 10 minutes and nothing has happened, just the cursor flashing below the command as if it's doing something.
How long does this normally take? Should I interrupt it if it's abnormal? What should I do from here?
Thanks!
Robbie_G said:
Hi,
I just unlocked my bootloader with v8 on the latest OTA update. I rebooted into the bootloader, and ”fastboot devices" returned mine just fine. Then I ran "fastboot -i 0x05B0 flash recovery twrp.blob" with the latest 2.6.3.2 version, but it has been about 10 minutes and nothing has happened, just the cursor flashing below the command as if it's doing something.
How long does this normally take? Should I interrupt it if it's abnormal? What should I do from here?
Click to expand...
Click to collapse
Flashing the recovery takes only a few seconds - press Ctrl+C to abort. You mistyped the -i parameter - it's 0x0b05, not 0x05b0. If "fastboot devices" returns a proper serial number instead of "???????", you may also omit the parameter completely ("fastboot flash recovery ...").
_that said:
Flashing the recovery takes only a few seconds - press Ctrl+C to abort. You mistyped the -i parameter - it's 0x0b05, not 0x05b0. If "fastboot devices" returns a proper serial number instead of "???????", you may also omit the parameter completely ("fastboot flash recovery ...").
Click to expand...
Click to collapse
Thanks, I actually typed it correctly in the command prompt. Fastboot.exe ended up crashing in windows (which I have used multiple times for other devices...). I restarted windows, downloaded the ”minimal adb and fastboot" tool, tried again with that one, and it worked.
Thanks for the tip about the -i and your prompt, helpful reply!
_that said:
Flashing the recovery takes only a few seconds - press Ctrl+C to abort. You mistyped the -i parameter - it's 0x0b05, not 0x05b0. If "fastboot devices" returns a proper serial number instead of "???????", you may also omit the parameter completely ("fastboot flash recovery ...").
Click to expand...
Click to collapse
Ahhh! I sense the chance for another lesson!!
I have always wondered about this: When do you need to use the -i 0x0b05 parameter and when not - and why?
And yes - I did google it and didn't find an answer
Odd thing really, When I type "adb Devices" when My Moto G is in fastboot, No devices are found.
How ever, When I Simply boot up my phone, adb can find it perfectly fine.
My drivers are up to date.
Can someone help me with this?
Do you have adb debugging enabled?
If your phone is in fastboot mode, type "fastboot devices" at the command prompt.
I don't believe ADB commands work in fastboot. ADB commands are used in debugging mode.
audit13 said:
If your phone is in fastboot mode, type "fastboot devices" at the command prompt.
I don't believe ADB commands work in fastboot. ADB commands are used in debugging mode.
Click to expand...
Click to collapse
oh Such a rookie mistake, Thanks.
Trying to fix my dumb error, I have a XT1034 but Resored it to A XT1033 Firmaware
Did the fastboot command find you phone when the phone was in fastboot mode?
We were all rookies at one point
It's very, very, unfortunate that this happened so early in the life of my new Pixel 2. Here's what I did:
fastboot oem unlock
Device erases and boots normally, power off and boot into bootloader using volume and power.
Flash Android 8.1 beta using flash-all.bat
<Device is stuck in bootloader>
Flash factory Android 8.0 image, same thing
Try "fastboot --set-active=a" followed by "fastboot continue" and "fastboot --set-active b" followed by "fastboot continue", neither worked.
Try entering recovery or download mode from bootloader, neither worked.
I contacted Google support, and they didn't have any suggestions other than an RMA, so a new device should be on the way soon. Given the comments in this thread about using the wrong version of fastboot, I'll point out that I do have the latest version of platform-tools, and my fastboot version is:
Code:
C:\>fastboot --version
fastboot version 3db08f2c6889-android
Installed as C:\android-platform-tools\fastboot.exe
Anyone else have this experience? (I hope not.)
Edit: Okay, thanks to this post, I learned that I flash-all.bat, which uses "fastboot -w update image-*.zip", leads to this condition. However, flashing each img file in the zip archive individually gets the device back to health. Phew.
can you share the .bat file please?
I didn't use a bat script to recover the device, I typed each "fastboot flash <partition> <partition>.img" command by hand. Not the most efficient, but I wasn't expecting to do this more than once.
It's possible you had a bad download, did you attempt to redownload the stock image?
While Unlocking Bootloader, Fastboot Commands are stuck on "waiting for device"
I have a 6045I version Idol 3 and I've installed the 15 second adb fastboot setup. When I type the command "adb devices" I get the id number and rebooting to bootloader works fine. Once I reboot, the command fastboot -i 0x1bbb devices shows the id number. The problem is when I try either fastboot flashing unlock or fastboot oem unlock both result in the cmd saying "waiting for device". I don't know how to fix this but I've done some research and I think it might have something to do with drivers or maybe alcatel blocked fastboot after a certain update? All I want to do is flash the lineage rom to get android 7.1 nougat so I would really appreciate any help.