Database Develop

Unable to load FireFireFire onto Kindle Fire Gen 2 / Device not mounting

I originally posted this question in XDA Assist yesterday. I was directed to this forum, and after reading more here, have added a few more questions/concerns with ***___**** that came after digging through the forum stickies. I know this has become a huge post, so apologies in advance.
I'm having some trouble mounting a Kindle Fire HD 7 Gen2 (Tate) in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
******* After reading the Faq here, I am concerned that even if Fastboot were to detect the device, that simply using it to load the FireFireFire bootloader directly onto the device would cause the problem of the wall of fire because of the M-Shield issue. Seems I would have to follow these steps here or here to load FireFireFire as a 2nd bootloader (including downgrading the OS to v7.2.3), is that correct? Also one of those pages says not to use automated tools like FireFireFire... which I thought was a bootloader, so what bootloader should I use to get around the low battery cycle startup problem that FireFireFire specifically addresses with it's startup battery check *******
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus.
******In one of the pages linked above, it makes a passing reference to some fastboot cables not putting the device in Fastboot. Since I cannot connect to the device in the first place when it is in "fastboot", I cannot use their method to confirm fastboot is working. When bootup with my fastboot cable, the "image" on the device does change from orange & flashing "Kinde Fire" to the orange "Kindle Fastboot" pic, so I'd to know if I can rule out the cable as part of my problem... *****
Here is the error from Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I found a tutorial on Ubuntu forums for getting MTP to work that involved using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However that didn't work. It seems that in Fastboot I actually might not MTP to handle the device...
OTOH, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command....
***** Since yesterday, I back and compared the vendor and product codes reported in lsusb and noticed that they are the same regardless of whether I connect the device using a regular cable (when it mounts correctly) and the fastboot cable (when the screen says fastboot, and I get the "raw device" failure to mount. My understanding is that the hardware ID should be different if the device is in fastboot mode vs "normal" mode. Is that correct? How do I deal with this behavior if the device is supposed to load different drivers when in different modes?*****
However, it seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
***** The other thing I tried was using the modprobe command to manually start the usb-storage driver as explained here. However the step to confirm the driver was unsuccessful because the /var/log/messages file was not found by the tail command. Even though that is really an ubuntu / linux question, perhaps someone here can help with some guidance on confirming the mass storage driver as well?*****
Can anybody help with this problem please?
Thank you

Additional detail
In case it's helpful to diagnose the issue, I am now experiencing an odd behavior where the device starts out in Fastboot (using the fastboot cable), and then after about 30+ seconds, it automatically switches to the "swipe" screen as though it was in normal mode.
This happened after I went and rem'd out all references to this device in the MTP rules files. The first time I plugged it in, Ubuntu popup asked how it should handle the device. I didn't see "mass storage" so I hit cancel. At that point, it started to flop over from fastboot into normal automatically even though it is plugged into a fastboot cable.
My understanding was that a fastboot cable forced it into fastboot mode (or else was somehow device in-compatible with certain Kindles). I don't understand how the host OS could do this without issuing an ADB / shell command?

Fast boot <waiting for device>

I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.

ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
Does it work with
Different cable
Different port
Different pc
Different OS like linux
?
If I remember correctly I had issues with windows drivers.

Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works

ambitiousButRubbish said:
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
Click to expand...
Click to collapse
I use Linux Mint Cinnamon for development
I am still happy with it

ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
my same issue adb working but not fastboot on windows 10.
i solved using ubuntu on virtual machine. on windows i can't use fastboot but with ubuntu on oracle virtualbox all is work perfectly

yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device

ambitiousButRubbish said:
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
Click to expand...
Click to collapse
is it possible to install adb and fastboot from magisk and do it from another android device?
is it possible to do it with a 32 bit device? i have a galaxy note 4 as a second phone with snapdragon 805 32 bit

MartinX3 said:
I use Linux Mint Cinnamon for development
I am still happy with it
Click to expand...
Click to collapse
Arch linux only ?

Don't see why not, the binaries are just compiled for ARM, don't think they are architecture specific.
My mi mix 3 is ARMv8 (64 bit) sd845, and it worked fine, not sure about ARMv7, but as I say, I think the binaries are ARMv7 anyway.
So long as the device can host a USB connection it will work.

For anyone having problems with the,"Waiting for Device" in windows,
USB debugging enabled on the phone.
Connected to PC through USB data cable and Phone screen unlocked and File Transfers enabled.
In windows> Device Manager> Android device(or your device/phone) >ADB driver or similar > Properties> Driver> Update Driver > Browse Computer > Let me pick from a list of devices and Un-tick the show compatible devices and find one that works.
I've had to keep this general as there are quite a few variables with different phones makes/models but the problem is caused by Window's Device Mangler not getting the correct ADB driver installed/chosen and or too many varied ADB driver packages installed
HTH

First hit in google... so let me explain it again. (Yeah... fresh windows install ****ed me over... )
You need ADB/Fastboot.
Sony Drivers?: https://developer.sony.com/file/download/xperia-xz2-driver/
Google USB Drivers: https://developer.android.com/studio/run/win-usb
If you can't install it. Disable Driver signature enforcement (Hold Shift while you press the restart button with the mouse)
When ADB works but fastboot isn't recognized reboot into bootloader "ADB reboot bootloader" and then in Device Manager find the "Android!" device and manually select the Android Bootloader as driver.

Can't Flash Fastboot ROMs

MiFlash ver: 2020.3.14.0 & 2019.12.6.0.
Latest platform-tools installed systemwide. I also tried some outdated but I got an even worse result.
Phone: Mi 9T Pro 6/64 Global with unlocked bootloader.
I softbricked my phone trying to flash a ROM but for some weird reason I can't flash MIUI on fastboot. I've tried to flash the following builds:
V12.0.1.0.QFKMIXM (downloaded from XiaomiFirmwareUpdater)
V12.0.2.0.QFKMIXM (downloaded from 3 different places: Xiaomi, XiaomiFirmwareUpdater and with XiaoMiTool V2)
I've also confirmed that the phone is indeed unlocked (that's what the MiUnlockTool tells me as you can see in the printscreen here).
The error I get is the following:
Code:
Sending sparse 'vendor' 1/2 (773888 KB) FAILED (Error reading sparse file)
Logs and printscreens here:
LOG
PRINTSCREEN
I've also tried other tools like MiFlashPro, XAFT (Xiaomi ADB / Fastboot Tools) and simply executing the script (in both Windows the .bat and Linux the .sh ) but to no success.
For Linux I used FWUL.
I also tried 4 different computers but the result was always the same. The computers where:
AMD Ryzen 1600 based (with both Linux and Windows)
AMD Ryzen 2600 based
AMD A8-7410 based (with both Linux and Windows)
Intel Core i7 3632QM based
I think I should also tell that for some reason fastboot only works if I connect a phone to a USB hub. I've tried many things but to no success. I've tried USB 2.0, USB 3.0 and USB 3.1 ports, still no success.
Only thing left is swapping the cable but as this is my first USB-C device I don't have a spare one. And I bought this phone used and it came with every factory accessory except for the cable. I'll try a new cable as soon as I can but maybe you guys know something that I don't.
On a side note, I also tried flashing manually vendor alone and got the same result. I also tried to do the same with system and got the exact same error, so I suppose it has something to do with the sparse thingy. I also tried to do fastboot flash:raw xx xx.img but instead got an allocation error.
I can provide more info if needed. All ideas are welcome.
EDIT: it was the cable all along. Have a nice day

Re down load fadtboot rom and fladh

Yet again, Fastboot is stuck on “Sending 'boot.img'”

Fastboot version 30.0.4-6686687
Trying to temporarily boot TWRP recovery image twrp-3.4.0-0-lake.img on my unlocked Motorola Moto G7 Plus.
Phone is connected via USB Type-C to Type-C cord from the box to my laptop running Linux (Manjaro 20.0.3) Live USB system.
When I run ./fastboot boot twrp-3.4.0-0-lake.img or ./fastboot boot boot.img (same file, renamed) with and without sudo, it always gets stuck at Sending 'boot.img' (30080 KB) doing nothing.
Bootloader logs section of fastboot mode shows only cmd: download:01d60000.
The PC I use now is the only PC that helped me to actually unlock the bootloader. Other PCs I have were not able to send correct fastboot commands (for example, oem help transformed into oem helpersion, and oem get_unlock_data cut to oem get_unlock). Those PCs had regular USB Type-A 3.0 ports, so I had connected them to my phone with corresponding 3rd-party cable. It might've been of insufficient quality though.
All files are located near to the root of extrenal SSD connected to another Type-C port, so the absolute paths to TWRP image and fastboot executable should not be too long.
Type-C cords I'm using now are new and OK.
Motorola doesn't distribute Linux drivers for their devices.
What else could be wrong here? Please help. Any advice is appreciated.
Will update this post later with my own findings as well for people who could stumble a similar problem.
Update 1
Tried fastboot boot boot.img on another PC. It is also running Linux (Ubuntu 20.04). Connection is from Type-A to Type-C. Wire is good. No noticeable changes. Main issue persists.

What does "fastboot devices" say? Try running the commands with root and with a different USB cable.
Edit: It should work. I just bootet TWRP 3.4.0-0 several times. I used Fedora Linux with android-tools-20180828gitc7815d675-4.fc31.x86_64 which includes fastboot. BL on device is MBM-3.0-lake_retail-38523c9-200214

Any further update on that ?
Same happens with my device (motorola one power).
The bootloader logs shows "cmd: download:<8 letter hash/code>"
And cancelling the operation doesn't do any harm, just your next command will fail with
"FAILED (remote: 'unknown command')", and bootloader logs will print an empty line starting from cmd:.
Did it work later on, what change did it require if you remember a bit ?
Update: The OP has put the question on reddit:
https://www.reddit.com/r/MotoG/comments/iwcx2v
The solution that worked for him was using windows... dont get angry sometimes we have to use the unused : )

SOLUTION: connect the phone using a USB hub
When plugin the G7 Plus, functioning MTP and ADB, but fastboot “Sending 'boot.img'” dont worked properly
The HUB worked for me, even in the same port
Regards

Hello!
I came here, just to say that I had the same issue with my Moto Z3 Play (beckham), when trying to fastboot boot. It was stuck in "Sending 'boot.img'".
Doesn't make any sense, but when I tried the solution of USB Hub, it worked. Command was accepted and loaded as it was normal as usual.
Thank you very much for this tip!
Best regards

Question Partially bricked phone

Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast

Audoghast said:
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Click to expand...
Click to collapse
While your phone is in fastboot and connected to your laptop; How is it shown in device manager?

Good evening.
I found the solution to unbrick my Oneplus Nord CE 5G and here it is.
Status: - normal start leading to Qualcomm Crash Dump screen
- Recovery mode into TWRP possible but no transfer of files to/from phone
- No Fastboot possible
Procedure:
Install Qualcomm USB Drivers from
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
You may have to launch the command prompt as admin and type:
bcdedit /set testsigning on
I did not have to do it because the Qualcomm Driver installation did it for me.
After restart you will see the following message in the lower right side of your PC:
Testmode Windows 10 Pro + build number
To get rid of end at the very end type:
bcdedit -set testsigning off
Download the following package:
Europe: https://onepluscommunityserver.com/...BA/R/OnePlus_Nord_CE_EU_OxygenOS_11.0.9.9.zip
India:
https://onepluscommunityserver.com/...R/OnePlus_Nord_CE_India_OxygenOS_11.0.4.4.zip
These packages contain the MSM Download Tool and the respective files. Beware that you have to get the correct bundle for your phone. Other bundles contain MSM Download Tool too but will not be compatible and the tool generates a failure message.
Launch MSM and type OTHER at login.
Target was EU in my case.
Then click on start.
Now your phone needs to boot into EDL mode. It worked for me from the TWRP Reboot screen but supposedly starting the phone by holding the volume up and down buttons for 45 seconds does the same.
The screen will be totally black, no beep, no vibration, no feedback.
Then connect the USB cable and MSM will start working. After about 5 minutes the phone should be back to normal.
ADB commands worked again too (phone was being recognized as USB device under device manager). However, fastboot did not work. The device was listed as other device in the manager.
After updating the driver using the following files everything worked:
https://drive.google.com/drive/folders/1D96njoYn-n3alu3ggaK3Kw8hMGLKhJVg
Now I am back to rooting and will report about that too.
Good luck