Semi-bricked stock Kindle Fire HD - 7" Kindle Fire HD Q&A, Help & Troubleshooting

This is my mother's Kindle. I believe it's a 3rd-gen; it has no cameras and a 7" screen. She's elderly so I doubt she's done any playing with the firmware.
It boots to a screen that says "Enter Boot Password". She'd contacted Amazon, who tried "a few things", and then told her she'd need to buy a new one. I'd prefer to fix hers instead.
I tried booting to the recovery mode (power-volume down) several times. Lots of messages about "Failed to mount /cache (invalid argument)", and then "Reset to Factory Defaults" spends some time churning before returning me to the boot password prompt.
I downloaded a "Kindle Unbrick Utility". In the batch files it called, Adb reported "device not found". Found instructions for a tweak to an .inf file to get Windows to recognize the device and now get "device offline" instead, which isn't much better. New install of Android Studio reports that the device is unauthorized; since I can't get in, I can't authorize things nor turn on Developer mode.
I've read enough to know that a Fastboot cable is another thing that may help but what I don't know is if it's worth pursuing, or is this Kindle suitable for parts only? Is there another route I should be following on trying to get it working again?

Related

Unmodded restore problems!!!Write protected? Also some Valuable Information

I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!
Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom
I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?
Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?
Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.
What's the common denominator, here? Were these all purchased used/3rd party?
Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing
I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?
I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?
Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.
wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.
Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!
I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.
any luck with this any 1? =(
I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.

Trouble Rooting Kindle Fire HD

i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Zponds360 said:
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Click to expand...
Click to collapse
WARNING!!
Firstly your Using a Kindle Fire HD. That is different to the Kindle fire. Even with root I dont think your gonna be running Jelly Bean just yet. You will probably brick the device if you use a standard Kindle Fire ROM!!!!!!!!!!!!!!!!!!!!!
Ok first download and Install the Android SDK. Put it where its easy to find. I use c:\ . Once thats done open SDK manager and tick next to Android SDK Platform-tools and click the box for Install packages.
Once thats done See this page: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
This gives the most stable ADB I have found.
OK next see this thread. This is automated root. http://forum.xda-developers.com/showthread.php?t=1893838.
If that still doesnt work (It didnt for me and others). Watch this Video. http://youtu.be/CYDBoTtdvcE This is the manual method. For a bigger look at the code see this page: http://www.redmondpie.com/how-to-root-amazon-kindle-fire-hd-7-8.9-on-android-4.0.4-ics/
On this page the open quote looks like a tilde EDIT thats actually a grave accent...I always called it the tilde key. Its not just use the KB apostrophe ( ' ) wherever you see a quote!
Hope this helps and I hope I dont get into trouble for posting external Links. Just trying to help!

[Q] Wiped Kindle Fire Hd 7" Tate

I have a Kindle Fire HD 7" device model "tate" (yes I'm sure) that I rooted, installed TWRP, and Cyanogenmod. Recently, I decided to upgrade it. After having several difficulties, I mistakenly wiped the system and data partitions, leaving with a device that has no OS. This wouldn't be a problem save for the fact that my computer has seen some of my less tech savvy times where I wasn't careful with drivers. Regularly, I'd mount the internal SD Card via the recovery's fancy ui, then transfer whatever ROM image I wanted, installed it, and voila! My computer is aware that I have a Kindle plugged in to it. In the Device Manager, it's has named it several different things, usually a heading saying "Kindle Fire" with a sub-heading saying "Android ADB Composite Interface." (I believe that was it.) I've tried manually installing the Kindle drivers with the executable and removing the actual driver file from the executable to "select from list of drivers on my computer" to no avail. ADB detects my device as booted into recovery, but I can't mount the storage from the device. I have no external access to the internal memory to put any OS on the Kindle. I've tried every option in the Kindle Unbricking Tool and KFFA. Hopefully someone can point out an error on my behalf or perhaps a solution.

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?

Sideloading firmware fails with unmount error

I could not find anything similar using the search and google, so I hope I can find some help here.
I have the XT1900-7 device and I have to upgrade it to Android 9 as my banking app will stop working otherwise next week. I don't get the update offered via the Android settings, but the support confirmed that it is available.
I already tried to use the Lenovo Rescue and Smart Assistant as they recommended, but it says the device is not supported after downloading the firmware file.
I tried sideloading with the file I got from the assistant as well as with the one from https://motostockrom.com/motorola-moto-x4-xt1900
But when I enter recovery menu and select to sideload from ADB (same issue when trying with SD card), it always fails at the first step.
It prints "failed to unmount /" and then "failed to set up expected mounts for install".
Another frequent entries in the recovery log say "failed to open driver control: No such file or directory" and "[libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt".
But I could not figure out the reason for these or if they are related.
I wiped all data as well, but it made no difference.
Not directly related, but I mention it in case someone has a suggestion for that:
As the sideloading failed, I unlocked the bootloader (sideloading still does not work) and tried to install the firmware with fastboot.
But it seems that the communication is not stable or corrupted. I have to type most commands at least twice to receive a response other than "not found" or "remote: unknown command".
I read that this could be related to a bad USB cable. I already tried switching ports, but I don't have another USB cable available right now.
Could there be another reason for this issue?
Thanks for any help with this. I really don't want to buy a new phone again just because of that.

Categories

Resources