Shows the NVIDIA logo, but then after a while it shows the Android guy with the Exclamation point and says NO COMMAND.
I can get to fastboot, but now I'm getting one of two errors in the CMD.
Either:
target didn't report max-download-size
sending 'recovery' (15140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
or
target reported max download size of 67108864 bytes
sending 'recovery' (15140 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
Then the shield reboots and I see the NVIDIA logo, and goes right back to the android guy with the exclamation point.
Any ideas?
do you have the latest fastboot and adb? when in fastboot go into control panel and update drivers if you see the yellow exclamation. sounds like a pc to shield connection issue
Figured it out. 2 bad USB cables. 3rd one solved the issues.
Thanks!
Same old story, yeah the Shield TV is picky.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Hey guys,
I can't install TWRP anymore on my unlocked "P8 lite" after the last Stock ROM Update. I've done the installation many times before without problems using Minimal ADB and fastboot and even the Universal Fastboot and ADB tool. When I try to flash I get no failed command, but nothing happens on my phone. I've tried with the newest grace .img (for "P8") and with an older .img that I've used in the past successfully. Commands "adb devices" and "adb reboot bootloader" work fine.
Any solution?
thx
CMD commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 2.625s
Hello,
my essential phone was working great. i unlocked the bootloader and installed magisk.
The problem is that i got 3 dead pixel in the middle of the screen over night.
I know need to return it to amazon.
As i tried to get back to stock i get the following error(i am on the newest Firmware):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.004s
When i try to flash the stock img i get the following error:
FAILED (Write to device failed (Unknown error)) on every task
for example:
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_a system.img
Sending 'system_a' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_b system.img
Sending 'system_b' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
Thank you for helping.
kappagei said:
Hello,
my essential phone was working great. i unlocked the bootloader and installed magisk.
The problem is that i got 3 dead pixel in the middle of the screen over night.
I know need to return it to amazon.
As i tried to get back to stock i get the following error(i am on the newest Firmware):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.004s
When i try to flash the stock img i get the following error:
FAILED (Write to device failed (Unknown error)) on every task
for example:
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_a system.img
Sending 'system_a' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_b system.img
Sending 'system_b' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
Thank you for helping.
Click to expand...
Click to collapse
after 4 hours of finding a error with the fastloader -w command i finally got it. it was the combination of a usb 3 port and the usb cabel from essential and a windows 10 computer.
My phone is now on oreo and and the bootloader is logged again!
Yeah don't use the usb c cable that comes with the phone for data. I have a USB c to A cable from Anker that I use.
kappagei said:
after 4 hours of finding a error with the fastloader -w command i finally got it. it was the combination of a usb 3 port and the usb cabel from essential and a windows 10 computer.
My phone is now on oreo and and the bootloader is logged again!
Click to expand...
Click to collapse
Bro, i didn't get what you are trying to say.. i am stuck with the same situation.. which cable you used to solve the problem
chauhansonu104 said:
Bro, i didn't get what you are trying to say.. i am stuck with the same situation.. which cable you used to solve the problem
Click to expand...
Click to collapse
The Essential supplied usb-c cable should not be used for anything but charging. Even Essential admits it is too poor to use for data transmission. Get a good quality usb-c cable and try again.
When I pulled down the notification bar, my phone suddenly restarted and could not enter the system interface. I tried to flash in TWRP to recover, but I got an error:
target didn't report max-download-size
Sending 'boot' (65536 KB)...
FAILED (remote: Requested download size is more than max allowed
)
When I checked its slots, I found that all the slots were lost.
When I use the command: fastboot getvar current-slot
It returns: current-slot:
Finished. total time: 0.004s
(Nothing is displayed after "current-slot".)
I want to retain and export my important data, how can I do this?
Thread closed at OP request, due to issue being solved.
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Did you unlock the bootloader again? Or was it just a wipe
Is usb debugging turned on?
Perhaps revoke it and cycle it then test ADB again.
If so run ADB kill-server
Then run ADB reboot bootloader should work then.
Also did you get the prompt when you did ADB devices on your phone to allow connections to that device?
Seems like driver issue.
Search for
ualcomm-hs-usb-qdloader-9008-driver-64-bit
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Hey I'm having the same issue. Did you get this resolved?
It’s 100% a driver issue
If you're using Windows 7 there's a known issue with drivers, use Windows 10
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
ymDroid said:
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
Click to expand...
Click to collapse
Quite strange that.
From a completely fresh win 10 installation I just plugged in my phone, install the OnePlus drivers, then activated USB debugging, allowed all drivers to be installed.
Added necessary ADB and fastboot files in a folder to C: and then typed ADB devices via powershell in that folder, got prompted to accept the device.
From that point fastboot worked and always has.
try this solution https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
-
This did the job for me.
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
This is my list of commands I used :
D:\LENOVO TAB M8\platform-tools>fastboot devices
HGT6FPQP fastboot
D:\LENOVO TAB M8\platform-tools>fastboot getvar version-bootloader
version-bootloader: akita_row_call-622276bd-20220223142906-20220706021818
Finished. Total time: 0.003s
D:\LENOVO TAB M8\platform-tools>fastboot flashing unlock
(bootloader) Start unlock flow
D:\LENOVO TAB M8\platform-tools>fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 1.219s]
Writing 'boot' OKAY [ 0.470s]
Finished. Total time: 1.867s
D:\LENOVO TAB M8\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/24 (130096 KB) OKAY [ 5.518s]
Writing 'system' OKAY [ 1.905s]
Sending sparse 'system' 2/24 (128056 KB) OKAY [ 5.592s]
Writing 'system' OKAY [ 1.865s]
......
Sending sparse 'system' 24/24 (31296 KB) OKAY [ 1.241s]
Writing 'system' OKAY [ 0.482s]
Finished. Total time: 198.984s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 1.271s]
Writing 'recovery' OKAY [ 0.472s]
Finished. Total time: 1.907s
D:\LENOVO TAB M8\platform-tools>fastboot flash cache cache.img
Sending 'cache' (128 KB) OKAY [ 0.016s]
Writing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.062s
D:\LENOVO TAB M8\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery twrp34.img
Sending 'recovery' (4562 KB) OKAY [ 0.163s]
Writing 'recovery' OKAY [ 0.069s]
Finished. Total time: 0.254s
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>fastboot reboot
< waiting for any device >
^C
As you can see , fastboot reboot fastboot was the last command I used and then my tablet restarted and fastboot mode disabled for ever. So turning off and then keeping Down+Power keys for going to fastboot not working
How can I enable fastboot mode again ?
M323 said:
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
...
Click to expand...
Click to collapse
I am fairly certain you'd be better off asking in your Lenovo Tab forum, not here in the Oneplus 8 one.
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
M323 said:
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
Click to expand...
Click to collapse
No, that's not a command I've ever used, only JUST fastboot reboot
NO idea, sorry.
Romyo717 said:
This did the job for me.
Click to expand...
Click to collapse
Had this issue on my LG V30 unlocking the bootloader and this worked for me. Looks like a scam, and I'd uninstall it thoroughly after using it, but it did work! I also had to swap to a usb-2.0 hub to get the process I was doing to work so that might be useful.
Did you ever get it fixed?