Hi all!
I'm sticking with the update of my firmware using the super vomer's guide here: http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958&nocache=1&z=7697684632189703
i've got this :
MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip
sending 'zip' (26802 KB)...
OKAY [ 2.276s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.844s
MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip
< waiting for device >
sending 'zip' (26802 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (Operation timed out))
finished. total time: 2.239s
MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip
ERROR: could not get pipe properties
ERROR: could not get pipe properties
sending 'zip' (26802 KB)...
ERROR: bulkOut endpoint not assigned
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip
ERROR: could not get pipe properties
ERROR: could not get pipe properties
sending 'zip' (26802 KB)...
ERROR: bulkOut endpoint not assigned
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
I can't flash the zip with fastboot.... What's wrong?
Can i restart my phone or will he remain bricked?
Thank you so much in advance if someone can help me!
I fixed the problem this thread can be closed.
just reconnect the USB cable....
Related
Hi, I S-OFF my phone by alpharevx and used 4ext touch recorvery. Today I try flash RUU.
1) From goo-inside.me/stock/vivo/ruu I downloaded PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.zip,
2) renamed to PG32IMG.zip
3) copied to sdcard
4) restart phone
5) I confirm update.
And now echo this:
img: ales.nejdr.cz/incs.jpg
I try unlock bootloader from htcdev, but
Code:
[skeeve:~]$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Revolutionary doens't work, because adb doesn't work (only fastboot).
I try make golden card from this tutorial: mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/ , but with this I still can't flash RUU.
Now phone is brick. What can I do to turn the phone work?
I know, my english is ugly, sorry.
ales.n said:
Hi, I S-OFF my phone by alpharevx and used 4ext touch recorvery. Today I try flash RUU.
1) From goo-inside.me/stock/vivo/ruu I downloaded PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.zip,
2) renamed to PG32IMG.zip
3) copied to sdcard
4) restart phone
5) I confirm update.
And now echo this:
img: ales.nejdr.cz/incs.jpg
I try unlock bootloader from htcdev, but
Code:
[skeeve:~]$ fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Revolutionary doens't work, because adb doesn't work (only fastboot).
I try make golden card from this tutorial: mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/ , but with this I still can't flash RUU.
Now phone is brick. What can I do to turn the phone work?
I know, my english is ugly, sorry.
Click to expand...
Click to collapse
Can you access Fastboot/Recovery?
Sent from my HTC Incredible S using xda premium
When I turn on the phone booted straight to recorvery, but nothing much to do here. When connected the phone to my computer than fastboot command works, but adb don't.
Code:
[skeeve:~]$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Now I tried another way, but without success.
Code:
[skeeve:~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.171s]
finished. total time: 0.171s
[skeeve:~]$ fastboot oem rebootRUU
...
OKAY [ 0.168s]
finished. total time: 0.168s
[skeeve:~]$ fastboot flash zip Stazene/PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed.zip
sending 'zip' (254241 KB)...
OKAY [ 42.201s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 84.778s
ales.n said:
Now I tried another way, but without success.
Code:
[skeeve:~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.171s]
finished. total time: 0.171s
[skeeve:~]$ fastboot oem rebootRUU
...
OKAY [ 0.168s]
finished. total time: 0.168s
[skeeve:~]$ fastboot flash zip Stazene/PG32IMG_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed.zip
sending 'zip' (254241 KB)...
OKAY [ 42.201s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 84.778s
Click to expand...
Click to collapse
You are trying to flash a RUU that is older than the last one you flashed. Please reboot into Fastboot USB mode and enter
Fastboot getvar all
And post the results here so we can help you determine which RUU you need to flash.
Solved
Solved!
Code:
[skeeve:~]$ fastboot getvar all
...
(bootloader) version-main: 2.32.1010.1
...
Then I flashed
Code:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
Although 2.32.1010.1 is probably a Korean version of the rom, but I tried it and the second attempt is OK.
All works fine! Thanks
I have a soft-bricked Raider that I dont know the history of and looks like it was updated to a ICS ROM with out updating the hboot, it has hboot 1.83.0014 and unlocked, a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
That's relocked. Reboot into hboot.
Sent from an HTC Vivid via XDA Premium
I have do.e fastboot OEM lock 5 or more times on this phone and it says *** locked *** when I reboot into hboot
http://forum.xda-developers.com/showthread.php?t=1421760
Maybe you can try this tool to wipe your device. I have no idea if it will work. It's worth reading up on though.
Tx I will check that when I get home
MORE BAD NEWS
I yanked zom.zip out of the RUU for my Raider.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.197s]
finished. total time: 0.199s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip c:\
junk\zom.zip
sending 'zip' (420878 KB)...
OKAY [ 39.172s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.786s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
so ends up the EMMC chip has bad sectors and this is a problem with this phone. I ended up on freenode at #htc-holiday and had a good chat with IOMonster, so I will try to return the phone to HTC 866.449.8358 and if not I will do the following.
by the way fastboot boot recovery-beta2.img did get me into recovery -- strange no one pointed that out to me...
The above error is how I found out the EMMC chip has write errors.
I will try to remember to come back and post what happens when I call HTC tomorrow.
bobmutch2 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
Click to expand...
Click to collapse
Did you solved it? I have a same problem [SD/EMMC]Error status=0x400008.
NEED HELP PLZZ
I was trying to change the MID,CID with this guide http://forum.xda-developers.com/showthread.php?t=2322820 and now i'm stuck on the last step with my HTC One on with that gray screen and whenn i try to flash the RUU from this guide http://htc-one.wonderhowto.com/how-to/convert-any-htc-one-into-stock-google-play-edition-with-bootloader-recovery-ota-updates-0148068/ i get this:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?
SaHiLzZ said:
Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?
Click to expand...
Click to collapse
when i use : fastboot oem reboot RUU the screen gose black and nothing hapens :/
Post a fastboot getvar all output
SaHiLzZ said:
Post a fastboot getvar all output
Click to expand...
Click to collapse
so i manage to get my HTC running again but couldn't install tha RUU:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.046s]
finished. total time: 0.046s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
sending 'zip' (467625 KB)...
OKAY [ 22.085s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.430s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
< waiting for device >
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.033s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 23.450s
The error is obviously MID. Fix it!
SaHiLzZ said:
The error is obviously MID. Fix it!
Click to expand...
Click to collapse
i fixed the MID isue and now sows an other error -.-
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.207s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.242s
You didn't do rebootruu
sahilzz said:
you didn't do rebootruu
Click to expand...
Click to collapse
omg works perfect now i have htc one google play edition thanks a lot :ddddd
Ok, so I bought a Moto X4 (XT-1900-7) with the goal to install lineage OS. I got with android 7.1.1 installed and I updated it with the built-in updater to 8.1 (I guess). After that there were no more updates available.
I unlocked the bootloader and tried flashing pie with a flash-all script I got somewhere.
No I am stuck in a boot loop: The Motorola logo appears with the note "Verity mode is set to logging" for a few seconds, than it turns black an starts over.
When I try to flash a ROM I get:
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.110s]
Finished. Total time: 0.113s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.340s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
OKAY [ 0.188s]
Finished. Total time: 0.533s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.101s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.288s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.186s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.004s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.150s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.579s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (2153 KB) OKAY [ 0.068s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (20625 KB) OKAY [ 0.692s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516148 KB) OKAY [ 17.491s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523995 KB) OKAY [ 18.490s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (520953 KB) OKAY [ 17.796s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523244 KB) OKAY [ 17.745s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (522088 KB) OKAY [ 17.449s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (487694 KB) OKAY [ 16.998s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (524133 KB) OKAY [ 18.174s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (222598 KB) OKAY [ 7.805s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (134369 KB) OKAY [ 4.625s]
Writing 'system_b' OKAY [ 1.023s]
Finished. Total time: 5.649s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.291s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.011s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.242s]
Finished. Total time: 0.243s
Erasing 'ddr' OKAY [ 0.003s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
Here is the flash-all:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
Click to expand...
Click to collapse
Since the first command of the script is "flash partition gpt.bin", I hoped I could repair the mess by flashing the right Stock ROM, so I tried several - with no luck. I got the ROMs from here: mirrors.lolinet. com/firmware/moto/payton. There are so many of them - I don't know which one is right. Not all of the ROMs tell you whether they are for my kind of X4 or not. Is it important to get a ROM specifically designed for a XT1900-7? I guess so, but why don't all the ROMs say which model they are for?
OK, so I hoped I could fix the device by installing twrp, format it and sideload a ROM. Again no luck. I managed to install the latest twrp and format the thing, but was unable to sideload anything. twrp says the internal sorage had 0MB.
I don't know what to do and need help. I am using ubuntu and have no windows pc available.
Your phone is RETEU variant on lolinet
Try flashing:
XT1900-7_PAYTON_RETEU_DS_9.0.....
You can open the script and copy each step in manually in fastboot to check for any errors, or just run the MAC script in linux.
OK, I thought so. I tried flashing said ROM and got the same problem.
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.128s]
Finished. Total time: 0.171s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.329s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
OKAY [ 0.195s]
Finished. Total time: 0.566s
Rebooting into bootloader OKAY [ 0.012s]
Finished. Total time: 0.263s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.191s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.185s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.003s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.147s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.538s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (2153 KB) OKAY [ 0.076s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (20625 KB) OKAY [ 0.701s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516148 KB) OKAY [ 17.138s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523995 KB) OKAY [ 17.363s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (520953 KB) OKAY [ 17.834s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523244 KB) OKAY [ 18.286s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (522088 KB) OKAY [ 18.237s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (487694 KB) OKAY [ 17.075s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (524133 KB) OKAY [ 18.088s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (222598 KB) OKAY [ 7.794s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (134369 KB) OKAY [ 4.592s]
Writing 'system_b' OKAY [ 1.026s]
Finished. Total time: 5.634s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.264s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.170s]
Finished. Total time: 0.170s
Erasing 'ddr' OKAY [ 0.003s]
The problem is in the first line I guess:
(bootloader) is-logicalartition: not found
Click to expand...
Click to collapse
How do I address this?
If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp
If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.
johnjingle said:
If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp
Click to expand...
Click to collapse
What do you mean by "fix"? I dont know, what else I can do?
KrisM22 said:
If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.
Click to expand...
Click to collapse
I went forward and backward with the ROMs, but how can I change the bootloader? What is a "M."?
M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.
KrisM22 said:
M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.
Click to expand...
Click to collapse
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.
Please report back on how this goes for you...
I've done some more research on lmsa.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute) click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.
derknobber said:
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.
Click to expand...
Click to collapse
Hello, did you managed to fix your problem ? im having exactly the same insue on my moto g7 plus
I followed steps to install the original build onto my g power and wiped the partition but then the flashing the bootloader failed. Now I can see I needed to unlock the bootloader first and I had not done that. I wiped the partition. I can get the phone into fastboot and that is it. Trying to go into recovery mode fails with "No valid operating system could be found. The device will not boot."
My device is the XT2041-4 and I was intending to revert back to Android 10 and now I'm stuck. I'm not sure how to unlock the bootloader. What can I do to recover? Or is there a way to get a build back on it?
Code:
[email protected]:~/android/stockmoto$ fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.004s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.359s]
Finished. Total time: 0.364s
[email protected]:~/android/stockmoto$ sudo fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.444s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/stockmoto$
Dang, I got a code to unlock the bootloader but I didn't enable a setting before wiping the partition. Any tips?
Code:
[email protected]:~/android/stockmoto$ sudo fastboot oem unlock (code snipped)
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/stockmoto$