Help with fastboot ubuntu - Dell Streak 7

does anyone know where to get help with fastboot in ubuntu? i have tried flashing a recovery image to my Dell Streak 7, but it keeps failing. fastboot is working, and when i send the command "fastboot reboot" it works fine. however, "fastboot devices" returns "????????????". when i try to flash the recovery, i get
"sending 'recovery' (3654 KB)...
FAILED (command write failed (No such device))
finished. total time: 0.000s"
"fastboot getvar version" returns version: LG7 0.4
so i know fastboot is working, and that it has at least some communication with the tablet, but something is not quite working. any ideas?

SOLVED
i'm not sure what happened differently, but i plugged the tablet into a different USB port, and then i got a max-download-size error when flashing the recovery. i came across another post that said to use "fastboot -S 0 flash..." to resolve that error, and it worked. everything seems to be good now

Related

[Q] Phone won't boot or enter recovery

This morning I woke up to discover that my phone will not boot. It just sits on the HTC splash screen until I hold the power button down and turn it off. I can get the phone into bootloader, but when I try to boot into recovery the phone just freezes. I can enter Fastboot mode, and it shows "fastboot USB" when connected to a computer, but any command I try to run via ADB fails. For example, when trying to erase cache it goes like this:
Code:
fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.369s
I've also tried running some commands using Hasoon2000's All-in-one toolkit, but it always returns a "error: device not found" message on the first popup, and then fails to complete the task. For example, attempting to flash a new recovery goes like this:
Code:
sending 'recovery' (7420 KB)...
OKAY [ 1.142s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.322s
The phone does show up as "My HTC" under the "Android USB Devices" heading in my PC's device manager, and the drivers appear to be up to date.
I was running Pac-man ROM nightly from Sept. 19, and I had no issues with it for over a week. Hboot version is 1.44.0000. I haven't flashed a custom kernel or radio at all.
Any thoughts on what could be wrong, and how I might go about fixing it?
I would also accept any tips on getting rid of the "this build is for development purposes only" screen so I can at least return the phone under warranty.

[Q] Not quite Bricked, but can't get anything but Fastboot

Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....
Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.
i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:
Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.
Wipe cache through fastboot and try again. It van help
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!

Fire HD Tate red bricked

Hi,
I am really hoping someone can help. My first attempt at upgrading my Fire HD using flashfire has red bricked it before it even got as far as installing twrp.
I bought a fastboot/factory cable and a few times it has showed the fastboot screen but adb does not list the device and so the tools just say waiting for device.
I have tried multiple versions of the adb usb drivers but none have worked so far when using the fastboot cable. I am using Windows 10 laptop but I also tried win7 desktop with the same lack of results.
I am stuck.
There seems to be as many ways to fix this as there are users who have bricked their kindle.
adb doesn't work in fastboot mode. Try fastboot devices. If you want out of fastboot try, fastboot reboot. Remove the cable before it reboots.
While in fastboot you could flash TWRP. Make sure the img file is in the directory you are in. Type fastboot flash recovery twrp(whatever filename).img
You can get into recovery by holding down the power button and volume up. Let go when the blue fire shows up.
The volume button is broken so it does limit my options.
I just found that to get into Fastboot I have to plugin to the laptop with the fastboot cable and then switch on the KFHD immediately.
> fastboot devices
returns nothing.
> fastboot reboot
says <waiting for device>
Same with the fastboot flash recovery command using either cable.
Then using the normal usb cable I opened Win Device Manager and under the Android Device entry I changed the driver to Android Bootloader Interface. This seems to have helped.
>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: -0.000s
>fastboot -i 0x1949 erase boot
erasing 'boot'...
OKAY [ 0.703s]
finished. total time: 0.703s
So I am currently using ULTIMATE KINDLE FIRE HD UNBRICK TOOL to erase everything and hopefully I can install something afterwards.
I will report back if I succeed.
Many thanks for helping.
It took 2 attempts but it has just finished wiping and installing the os (version 7.3.0 which is lower than the one I had before I think) and has successfully rebooted. Phew!
Thanks again for pointing out my newbie errors.
I now need to work out how to do this properly and which version I can safely update to without bricking the device. The LineageOS website is a bit contradictory. Maybe CM will be better ?
I'm running a cm12 nightly build. Anything more and you lose the camera and HDMI output.
Which bootloader driver did you install? By that, I am referring to the hardware I'd.
ps68060 said:
The volume button is broken so it does limit my options.
I just found that to get into Fastboot I have to plugin to the laptop with the fastboot cable and then switch on the KFHD immediately.
> fastboot devices
returns nothing.
> fastboot reboot
says <waiting for device>
Same with the fastboot flash recovery command using either cable.
Then using the normal usb cable I opened Win Device Manager and under the Android Device entry I changed the driver to Android Bootloader Interface. This seems to have helped.
>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: -0.000s
>fastboot -i 0x1949 erase boot
erasing 'boot'...
OKAY [ 0.703s]
finished. total time: 0.703s
So I am currently using ULTIMATE KINDLE FIRE HD UNBRICK TOOL to erase everything and hopefully I can install something afterwards.
I will report back if I succeed.
Many thanks for helping.
Click to expand...
Click to collapse
you have to put -i 0x1949 in front of ALL your commands. Its a vendor ID for amazon and its the only way to fastboot to the device. (example: fastboot -i 0x1949 reboot, fastboot -i ox1949 flash recovery yeeee.img, etc.)
just trial and error it.
Also to use TWRP (temoporarily) run "fastboot -i 0x1949 boot [path to recovery image]"
On latest platform tools the -i option is gone so where can we get the older fastboot executables?

Root Assistance RP2 Android 9 pie, latest updates.

Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445

[fastboot] problem with booting boot.img

When i use the command "fastboot boot boot.img" to boot twrp it loads endlessly until i interrupt it,
where it then gives me the error : FAILED (Status read failed (Too many links)).
My device is detected by "fastbood devices" and "adb devices".
I already tried to set the current slot to a with this: fastboot.exe --set-active=a
but it failed: FAILED (remote: 'unknown command').
My device is unlocked but when i check device status via "fastboot oem device-info" it tells me: (bootloader) 'device-info' is not a supported oem command.
Same goes for "fastboot oem help" which results in a : "FAILED (remote: 'unknown command')".
Right now i am using Havoc-OS which means it did work before.
Anyone else got any tips how i might get twrp to run again?
are you trying to boot fastboot boot boot.img ? or fastboot boot twrp.img ?
You need USB 2.0 hub.
Hello.Dear said:
You need USB 2.0 hub.
Click to expand...
Click to collapse
I've heard that before but I use a USB3.0 .
KrisM22 said:
I've heard that before but I use a USB3.0 .
Click to expand...
Click to collapse
Fastboot has a problem with USB 3.0. Same thing happened to me then i use usb 2.0 hub and everything works.

Categories

Resources