Database Develop

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.

[Q] DS7 stuck on setup wizard

Hi,
I'm using a TMobile 4G DS7 in Europe (no SIM card); last week as I restarted it (battery was very low) I started receiving error messages (Email app has stopped unexpectedly, then Gmail and you name it...) and was sent back to the setup wizard.The DS7 was running on the original setup, no OS upgrade had been done.
I tried a factory reboot which didn't change anything.
I started reading this forum and tried the 3 options which are described
1- updating with a 306 .pkg file on the SDCard
the following takes place
Booting kernel recovery Image
Blue text
Finding update package
Opening update package
Verifying update package
Install modem error . System will upgrade again. (90% bar)
Screen turns black then reboots
and back to square one !
Trying other packages results in an error message, process stops at verifying update package .
2- Fastboot mode
I downloaded and installed the drivers
I put DS7 in fastboot mode and get the fwg :
Username : cmbuild hostname : ***** buildnumber : ******
Build on Mar 11 2011 17:19:36
Starting Fastboot USB download protocol
On PC I go to the directory where the fastboot.exe is stored .
When I type < Fastboot devices>
I get <? fastboot> which seems to indicate that no device is identified ( under Config panel in Windows I can see that the device is recognized as an Android device) ....
3- NVFlash mode
I put the DS7 in NVFlash mode connected it to my PC . The config panel showed there was a prob (yellow triangle). I installed the driver .... and now the device does not even appear when I go Config panel / System
So I get nowhere under any of the 3 options ; can I just throw away my DS7 or is there still some hope ? things I haven't done correctly ?
Any help suggestion would be most appreciated.
Thx in advance to whoever wil read this thread.
FG

the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.

giveen said:
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
Click to expand...
Click to collapse
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.

FGMareil said:
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
Click to expand...
Click to collapse
You might be in read-only mode, which can only be fixed by Dell

giveen said:
You might be in read-only mode, which can only be fixed by Dell
Click to expand...
Click to collapse
The OP stated that the battery was low which is one reason some have claimed to cause this.

[Q] No Option to Update

Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!

Well, I guess I stumped everyone in here as well. I just sent the device back to Asus for the second time in 2 weeks. Let's see if they do anything more than just power on the device, deem it "working properly" and promptly send it back to me.

Shaundiesel said:
Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!
Click to expand...
Click to collapse
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.

WeAreNotAlone said:
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.
Click to expand...
Click to collapse
I tried everything under the sun....I extracted the zip, nothing. I left it as a zip, nothing. I went to recovery, nothing. You name it, I did it. So, I sent back to Asus for the second time in 2 weeks. I just checked the status of my RMA with Asus, and it states that "No trouble found." I'm not sure how NO TROUBLE IS FOUND when I can't even update to Asus latest firmware for their device? In addition, I do not get the options to try to manually update (Not that I should even have to go that route when it should be OTA). I will never own another Asus product. I've only had my tablet for 4 months, 2 1/2 months of which it sat in my desk, unused. Asus is garbage.

Did you remove any system files or freeze them? Did you root?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
No I did not remove any system files or freeze them, that I know of. I rooted shortly after purchasing this, but unrooted the device about 2 weeks later.
Thoughts?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
If you are talking to me in which camera(s) both seem to not be found by the OS ME170 is STOCK, STOCK, STOCK.
Contacted the vendor TigerDirect, noticed that they claim they will NOT do exchanges due to "manufacturers polices". While I realize it costs vendor (TigerDirect) to handle exchanges that wording could also indicate they have run the numbers and don't want to be bothered.
Reading about ASUS service, and my interaction with ASUS when I contacted them does not insipre incidence so I'm hoping to be able to flash the device and cameras will start functioning again.
In regards to the customer being able to flash a device (Which I done numerous times on other brands)
I know ASUS is a Asian based manufacturer and sells worldwide but they really need to have persons who can write in better ENGLISH.. ASUS needs to publish detailed instructions on how to flash device, additionally they need to update support pages with any drivers, tools to do so vs just posting the firmware with vaque reference to SOP.
Q: How long after firmware updates appears on ASUS site does OTA update get pushed?
..

Just an update....
Just received my memo pad back, and it appears to be finally fixed. It took sending it back twice, and escalating to a supervisor, but it looks good now. I've actually received 3 firmware updates in 2 days, so it was REALLY behind! What firmware are you all running right now? I have WW-3.2.23.201.

I think 201 is the latest. Mine is still on 199 though and it won't try to update again since it failed a couple of weeks ago.

Semi-bricked stock Kindle Fire HD

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?

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.