Develop Bugs

Phone is Stuck in FTM Mode or Soft bricked?

Hey guys, I've tried to hold off posting as long as possible and don't know what to search for to answer the question. I'll start from the beginning. I tried to flash a custom recovery after taking the OTA update to KK. I then rooted with IORoot and everything worked great. I used that Freegee app to try to flash TWRP 2.7 and it went into recovery, started flashing and then immediately rebooted. The Freegee app and other apps kept saying that I had the stock recovery even after multiple flash attemps. I then used the KK AutoRec tool because I thought that would allow for the custom recovery. After doing that, the phone was soft bricked and I was stuck in Fastboot. I used this: http://forum.xda-developers.com/showthread.php?t=2477595 to reflash everything except PrimaryGTP because I couldn't figure out how to do the PrimaryGTP portion. That worked great and my phone would reboot, but it rebooted into FTM mode with NO software buttons on it. After multiple reboots FTM mode will not exit. Here is the log of the adb terminal commands
C:\>fastboot erase recovery
erasing 'recovery'... OKAY
C:\>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY
writing 'recovery'... OKAY
C:\>fastboot erase aboot
erasing 'aboot'... OKAY
C:\>fastboot flash aboot aboot.img
sending 'aboot' (1024 KB)... OKAY
writing 'aboot'... OKAY
C:\>fastboot reboot
rebooting...
C:\>fastboot erase modem
erasing 'modem'... OKAY
C:\>fastboot flash modem 1-modem
error: cannot load '1-modem'
C:\>fastboot flash modem modem.img
sending 'modem' (57856 KB)... OKAY
writing 'modem'... OKAY
C:\>fastboot erase boot
erasing 'boot'... OKAY
C:\>fastboot flash boot 6-boot.img
sending 'boot' (11264 KB)... OKAY
writing 'boot'... OKAY
C:\>fastboot erase PrimaryGPT
erasing 'PrimaryGPT'... FAILED (remote: Partition table doesn't exist
)
C:\>fastboot erase primarygpt
erasing 'primarygpt'... FAILED (remote: Partition table doesn't exist
)
C:\>fastboot erase sbl1
erasing 'sbl1'... OKAY
C:\>fastboot flash sbl1 2-sbl1.img
sending 'sbl1' (512 KB)... OKAY
writing 'sbl1'... OKAY
C:\>fastboot erase dbi
erasing 'dbi'... OKAY
C:\>fastboot flash dbi 3-dbi.img
sending 'dbi' (512 KB)... OKAY
writing 'dbi'... OKAY
C:\>fastboot erase aboot
erasing 'aboot'... OKAY
C:\>fastboot flash aboot aboot.img
sending 'aboot' (1024 KB)... OKAY
writing 'aboot'... OKAY
C:\>fastboot erase rpm
erasing 'rpm'... OKAY
C:\>fastboot flash rpm 5-rpm.img
sending 'rpm' (512 KB)... OKAY
writing 'rpm'... OKAY
C:\>fastboot erase boot
erasing 'boot'... OKAY
C:\>fastboot flash boot 6-boot.img
sending 'boot' (11264 KB)... OKAY
writing 'boot'... OKAY
C:\>fastboot erase tz
erasing 'tz'... OKAY
C:\>fastboot flash tz 7-tz.img
sending 'tz' (512 KB)... OKAY
writing 'tz'... OKAY
C:\>fastboot erase misc
erasing 'misc'... OKAY
C:\>fastboot flash misc 8-misc.img
sending 'misc' (8192 KB)... OKAY
writing 'misc'... OKAY
C:\>fastboot erase persist
erasing 'persist'... OKAY
C:\>fastboot flash persist persist.img
sending 'persist' (5120 KB)... OKAY
writing 'persist'... OKAY
C:\>fastboot reboot
rebooting...
C:\>adb devices
List of devices attached
C:\>^A
Click to expand...
Click to collapse
I then tried to flash stock TOT to start completely over because I thought that would work. This is the error I keep getting: (Picture below)
I then thought a factory reset would do the trick. I did that and it worked using the power button + Volume down method. It rebooted like normal as if it was completely stock yet the FTM mode is still on there. When I get into download mode and attach it into the LG Flash tool and that Firmware Update screen comes onto my phone, the box says:
910K S0.0 AS0.0 B99 UHS
S U LG-LS980 04.4.2 Hrev_10
LS980ZVC_12
ROOTED
Click to expand...
Click to collapse
I have no clue where to go from here. Please Help

Just an update if this helps. I can make calls with the "Q-Slide" feature, but I still don't have software buttons. The phone activated just like it should have and it shows everything great and I have LTE but after multiple restarts it still goes into FTM mode and I can't exit the mode when the phone is off. I just so happen to get lucky and get into the setting menu and hit update PRL and activate, which activated LTE. So thats one step forward I guess. Does anyone know whats going on?? In the LG flash tools both the PID and IMEI read: NULL.

Z2 Force dead, just turn on with USB connected, don't charge

Hi, guys!
I just found XDA on internet search and hope you guys help me
I have a Z2Force and it don't turns on unless the USB are connected on charge or PC. When I connect the cable, the charge icon display appears but stays on an infinite loop and does not show the charge percentage.
When I try to turn on the phone (with charge connected), it goes into infinite loop on Motorola logo.
I can get into the fastboot menu pressing power + vol - , but only with USB connected. There on that screen, it says "Power OK".
I tried to flash stock rom using Minimal ADB and fastboot, I got the ROM on "lolinet dot com" (I can't post links, 'cause I'm new user). I downloaded on nash/official/RETBR (my Z2F is from Brasil). I used this commands:
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 adspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
the installation goes to the end, but after restarting, the phone keeps looping on the logo screen...
I don't know if this information will be helpful, but the bootloader is locked (oem_locked).
I don't have developer knowledge, but I can follow your guidance, just tell me what to do.
I will be happy to pay a beer for those who help me
Please, guys, help me, I don't have another phone
Thank you very much in advance.
Edit: I got this phone from a friend, he tried to use a custom ROM, the phone worked but without Play Store, he tried to restore to stock ROM and got to this situation. So, he gave me the phone, because my Z2Play fell on water and died

Anyone??
Please, can anyone help me? :/

Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.

41rw4lk said:
Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.
Click to expand...
Click to collapse
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/

AgrippaJr said:
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/
Click to expand...
Click to collapse
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
Yeah, this one...

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737

AgrippaJr said:
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
Click to expand...
Click to collapse
Not adb/fastboot, the flashall.bat that you're using where did you get that?

41rw4lk said:
Not adb/fastboot, the flashall.bat that you're using where did you get that?
Click to expand...
Click to collapse
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...

AgrippaJr said:
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...
Click to expand...
Click to collapse
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.

41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
OK... I will try here... I'll let u know

Test result, questions
41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(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 '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'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?

AgrippaJr said:
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(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 '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'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?
Click to expand...
Click to collapse
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.

41rw4lk said:
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.
Click to expand...
Click to collapse
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...

AgrippaJr said:
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...
Click to expand...
Click to collapse
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.

What is your battery voltage when you fastboot getvar all?

Uzephi said:
What is your battery voltage when you fastboot getvar all?
Click to expand...
Click to collapse
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...

41rw4lk said:
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.
Click to expand...
Click to collapse
I follow all the tutorial steps, in two different PC's, windows versions and cables, cmd says 'waiting for device'... It don't detect the phone...
When i do the 'devices' command at adb and fastboot:
C:\Users\Junior\Desktop\adb and fastboot>adb devices
List of devices attached
C:\Users\Junior\Desktop\adb and fastboot>fastboot devices
0042953957 fastboot
Did i miss something?

AgrippaJr said:
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...
Click to expand...
Click to collapse
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.

Uzephi said:
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.
Click to expand...
Click to collapse
I see... And where do you think the defect is? Maybe the battery or something else? What can I do about it? :|
maybe I should open and measure the battery voltage with a multimeter... What do you think?
If you have another solution, let me know

moto g5 even after passing software stays on the motorola logo and does not start

Guys I have the G5 that even passing software on it it remains on the motorola logo and does not start in any way to enter fastboot mode needs to be connected to the data cable + the Power buttons and volume less.
Normally just by pressing the combinations the motorolas will enter more this one does not enter and even passing software does not start, any suggestion of what might be?
Model: XT1672
Version ROM: XT1672_CEDRIC_RETBR_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Details:
I took it already so I tested some versions of the rom but only the most current version worked (ran the chambers without errors)

braganetx said:
Guys I have the G5 that even passing software on it it remains on the motorola logo and does not start in any way to enter fastboot mode needs to be connected to the data cable + the Power buttons and volume less.
Normally just by pressing the combinations the motorolas will enter more this one does not enter and even passing software does not start, any suggestion of what might be?
Model: XT1672
Version ROM: XT1672_CEDRIC_RETBR_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Details:
I took it already so I tested some versions of the rom but only the most current version worked (ran the chambers without errors)
Click to expand...
Click to collapse
As long as you get into the bootloader it will be possible to fix - hopefully (When the bootloader is away there are chances too - but that's harder). Can you check the battery? And how did this happen?

nift4 said:
As long as you get into the bootloader it will be possible to fix - hopefully (When the bootloader is away there are chances too - but that's harder). Can you check the battery? And how did this happen?
Click to expand...
Click to collapse
Yes it normally enters fastboot. Give to run all fastboot commands on it, just not ADB because the bootloader is blocked and the usb debugging option is disabled, and as I can't get into the system, then there is no way to activate it. I managed to run the software on it, but even after finishing the commands it does not start.
I don't know exactly what happened, I took this phone only on the Motorola logo.

braganetx said:
Yes it normally enters fastboot. Give to run all fastboot commands on it, just not ADB because the bootloader is blocked and the usb debugging option is disabled, and as I can't get into the system, then there is no way to activate it. I managed to run the software on it, but even after finishing the commands it does not start.
I don't know exactly what happened, I took this phone only on the Motorola logo.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot

TheFixItMan said:
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot
Click to expand...
Click to collapse
Ig bootloader is blocked means locked

TheFixItMan said:
Is your bootloader unlocked?
Post the entire cmd output of you trying to flash stock firmware via fastboot
Click to expand...
Click to collapse
Yes, locked bootloader
HTML:
$ fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
$
$ fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.085s]
finished. total time: 0.104s
$
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.553s]
finished. total time: 0.745s
$
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.296s]
writing 'modem'...
OKAY [ 1.046s]
finished. total time: 3.343s
$
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.115s]
writing 'fsg'...
OKAY [ 0.103s]
finished. total time: 0.218s
$
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
$
$ fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
$
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.090s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.187s
$
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.605s]
writing 'boot'...
OKAY [ 0.439s]
finished. total time: 1.044s
$
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.445s]
finished. total time: 1.026s
$
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 8.888s]
writing 'system'...
OKAY [ 5.917s]
finished. total time: 14.805s
$
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 5.509s]
finished. total time: 14.548s
$
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 9.312s]
writing 'system'...
OKAY [ 6.536s]
finished. total time: 15.847s
$
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 8.987s]
writing 'system'...
OKAY [ 7.513s]
finished. total time: 16.500s
$
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 8.816s]
writing 'system'...
OKAY [ 11.196s]
finished. total time: 20.012s
$
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 9.297s]
writing 'system'...
OKAY [ 5.525s]
finished. total time: 14.823s
$
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 9.387s]
writing 'system'...
OKAY [ 6.682s]
finished. total time: 16.069s
$
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 9.803s]
writing 'system'...
OKAY [ 6.820s]
finished. total time: 16.622s
$
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 8.308s]
writing 'system'...
OKAY [ 7.428s]
finished. total time: 15.736s
$
$ fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.10error: cannot load 'system.img_sparsechunk.10': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.11error: cannot load 'system.img_sparsechunk.11': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.12error: cannot load 'system.img_sparsechunk.12': No such file or directory
$
$ fastboot flash system_b system_other.img
error: cannot load 'system_other.img': No such file or directory
$
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.175s]
writing 'oem'...
OKAY [ 7.627s]
finished. total time: 12.803s
$
$ fastboot flash oem_b oem_other.img
error: cannot load 'oem_other.img': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.3
error: cannot load 'vendor.img_sparsechunk.3': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.4
error: cannot load 'vendor.img_sparsechunk.4': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.5
error: cannot load 'vendor.img_sparsechunk.5': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.6
error: cannot load 'vendor.img_sparsechunk.6': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.7
error: cannot load 'vendor.img_sparsechunk.7': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.8
error: cannot load 'vendor.img_sparsechunk.8': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.9
error: cannot load 'vendor.img_sparsechunk.9': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.10error: cannot load 'vendor.img_sparsechunk.10': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.11error: cannot load 'vendor.img_sparsechunk.11': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.12error: cannot load 'vendor.img_sparsechunk.12': No such file or directory
$
$ fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.078s]
finished. total time: 0.078s
$
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
$
$ fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.002s
$
$ fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot reboot
rebooting...
finished. total time: 0.152s

braganetx said:
Yes, locked bootloader
HTML:
$ fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
$
$ fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.085s]
finished. total time: 0.104s
$
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.553s]
finished. total time: 0.745s
$
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.296s]
writing 'modem'...
OKAY [ 1.046s]
finished. total time: 3.343s
$
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.115s]
writing 'fsg'...
OKAY [ 0.103s]
finished. total time: 0.218s
$
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
$
$ fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
$
$ fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
$
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.090s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.187s
$
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.605s]
writing 'boot'...
OKAY [ 0.439s]
finished. total time: 1.044s
$
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.445s]
finished. total time: 1.026s
$
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 8.888s]
writing 'system'...
OKAY [ 5.917s]
finished. total time: 14.805s
$
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 5.509s]
finished. total time: 14.548s
$
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 9.312s]
writing 'system'...
OKAY [ 6.536s]
finished. total time: 15.847s
$
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 8.987s]
writing 'system'...
OKAY [ 7.513s]
finished. total time: 16.500s
$
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 8.816s]
writing 'system'...
OKAY [ 11.196s]
finished. total time: 20.012s
$
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 9.297s]
writing 'system'...
OKAY [ 5.525s]
finished. total time: 14.823s
$
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 9.387s]
writing 'system'...
OKAY [ 6.682s]
finished. total time: 16.069s
$
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 9.803s]
writing 'system'...
OKAY [ 6.820s]
finished. total time: 16.622s
$
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 8.308s]
writing 'system'...
OKAY [ 7.428s]
finished. total time: 15.736s
$
$ fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.10error: cannot load 'system.img_sparsechunk.10': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.11error: cannot load 'system.img_sparsechunk.11': No such file or directory
$
$ fastboot flash system system.img_sparsechunk.12error: cannot load 'system.img_sparsechunk.12': No such file or directory
$
$ fastboot flash system_b system_other.img
error: cannot load 'system_other.img': No such file or directory
$
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.175s]
writing 'oem'...
OKAY [ 7.627s]
finished. total time: 12.803s
$
$ fastboot flash oem_b oem_other.img
error: cannot load 'oem_other.img': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.3
error: cannot load 'vendor.img_sparsechunk.3': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.4
error: cannot load 'vendor.img_sparsechunk.4': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.5
error: cannot load 'vendor.img_sparsechunk.5': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.6
error: cannot load 'vendor.img_sparsechunk.6': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.7
error: cannot load 'vendor.img_sparsechunk.7': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.8
error: cannot load 'vendor.img_sparsechunk.8': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.9
error: cannot load 'vendor.img_sparsechunk.9': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.10error: cannot load 'vendor.img_sparsechunk.10': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.11error: cannot load 'vendor.img_sparsechunk.11': No such file or directory
$
$ fastboot flash vendor vendor.img_sparsechunk.12error: cannot load 'vendor.img_sparsechunk.12': No such file or directory
$
$ fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.078s]
finished. total time: 0.078s
$
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
$
$ fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.002s
$
$ fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
$
$ fastboot reboot
rebooting...
finished. total time: 0.152s
Click to expand...
Click to collapse
I can see a few errors where have typos eg dsp in the commands and you are also trying to flash a lot of stuff that simply doesn't exist
You've also erased stuff that doesn't need erasing and hopefully won't cause an issue
Please use the following commands to flash your firmware and in the order shown below and I presume you are using the following firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

TheFixItMan said:
I can see a few errors where have typos eg dsp in the commands and you are also trying to flash a lot of stuff that simply doesn't exist
You've also erased stuff that doesn't need erasing and hopefully won't cause an issue
Please use the following commands to flash your firmware and in the order shown below and I presume you are using the following firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
I ran the commands as suggested, but even so it does not enter the system, I notice that it gives a slight wink on the screen but does not enter the system it enters the recovery menu.
Code:
$ fastboot oem fb_mode_set
...
OKAY [ 0.012s]
finished. total time: 0.012s
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.099s]
finished. total time: 0.133s
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.575s]
finished. total time: 0.790s
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.104s]
writing 'logo'...
OKAY [ 0.119s]
finished. total time: 0.223s
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.446s]
finished. total time: 1.102s
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.143s
$ fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.597s]
writing 'dsp'...
OKAY [ 0.293s]
finished. total time: 0.890s
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.711s]
writing 'oem'...
OKAY [ 7.667s]
finished. total time: 13.378s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 9.917s]
writing 'system'...
OKAY [ 5.930s]
finished. total time: 15.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.641s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 15.175s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 10.827s]
writing 'system'...
OKAY [ 6.586s]
finished. total time: 17.413s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.385s]
writing 'system'...
OKAY [ 7.547s]
finished. total time: 18.932s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 11.734s]
writing 'system'...
OKAY [ 11.231s]
finished. total time: 22.965s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.661s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 17.196s
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 11.027s]
writing 'system'...
OKAY [ 6.719s]
finished. total time: 17.746s
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 10.969s]
writing 'system'...
OKAY [ 6.857s]
finished. total time: 17.826s
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 10.007s]
writing 'system'...
OKAY [ 7.431s]
finished. total time: 17.438s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.825s]
writing 'modem'...
OKAY [ 1.060s]
finished. total time: 3.885s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.064s
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.153s]
writing 'fsg'...
OKAY [ 0.132s]
finished. total time: 0.285s
$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.171s]
finished. total time: 0.171s
$ fastboot oem fb_mode_clear
...
OKAY [ 0.014s]
finished. total time: 0.014s
$ fastboot reboot
rebooting...
finished. total time: 0.166s
$

braganetx said:
I ran the commands as suggested, but even so it does not enter the system, I notice that it gives a slight wink on the screen but does not enter the system it enters the recovery menu.
Code:
$ fastboot oem fb_mode_set
...
OKAY [ 0.012s]
finished. total time: 0.012s
$ fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.099s]
finished. total time: 0.133s
$ fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.575s]
finished. total time: 0.790s
$ fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 0.104s]
writing 'logo'...
OKAY [ 0.119s]
finished. total time: 0.223s
$ fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.446s]
finished. total time: 1.102s
$ fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.143s
$ fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.597s]
writing 'dsp'...
OKAY [ 0.293s]
finished. total time: 0.890s
$ fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.711s]
writing 'oem'...
OKAY [ 7.667s]
finished. total time: 13.378s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (258344 KB)...
OKAY [ 9.917s]
writing 'system'...
OKAY [ 5.930s]
finished. total time: 15.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256570 KB)...
OKAY [ 9.641s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 15.175s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (246510 KB)...
OKAY [ 10.827s]
writing 'system'...
OKAY [ 6.586s]
finished. total time: 17.413s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.385s]
writing 'system'...
OKAY [ 7.547s]
finished. total time: 18.932s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (261322 KB)...
OKAY [ 11.734s]
writing 'system'...
OKAY [ 11.231s]
finished. total time: 22.965s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (262141 KB)...
OKAY [ 11.661s]
writing 'system'...
OKAY [ 5.534s]
finished. total time: 17.196s
$ fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (262143 KB)...
OKAY [ 11.027s]
writing 'system'...
OKAY [ 6.719s]
finished. total time: 17.746s
$ fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (256817 KB)...
OKAY [ 10.969s]
writing 'system'...
OKAY [ 6.857s]
finished. total time: 17.826s
$ fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (237909 KB)...
OKAY [ 10.007s]
writing 'system'...
OKAY [ 7.431s]
finished. total time: 17.438s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (66358 KB)...
OKAY [ 2.825s]
writing 'modem'...
OKAY [ 1.060s]
finished. total time: 3.885s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.064s
$ fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (2956 KB)...
OKAY [ 0.153s]
writing 'fsg'...
OKAY [ 0.132s]
finished. total time: 0.285s
$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.024s
$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.171s]
finished. total time: 0.171s
$ fastboot oem fb_mode_clear
...
OKAY [ 0.014s]
finished. total time: 0.014s
$ fastboot reboot
rebooting...
finished. total time: 0.166s
$
Click to expand...
Click to collapse
If you enter bootloader mode and then select start normally from the menu option does the phone boot normally? You can also try safe mode
As your bootloader is locked it will be very hard to fix if it doesn't start normally from this option
You may have a hardware fault if the bootloader has never been unlocked - obviously if you have relocked it after modding your phone this could cause issues which is why you should never re-lock the bootloader after unlocking it

TheFixItMan said:
If you enter bootloader mode and then select start normally from the menu option does the phone boot normally?
Click to expand...
Click to collapse
Yes, I tried, but I didn't start, as I mentioned just a slight wink.
You can also try safe mode
Click to expand...
Click to collapse
How can I start safe mode without accessing the system?
As your bootloader is locked it will be very hard to fix if it doesn't start normally from this option
You may have a hardware fault if the bootloader has never been unlocked - obviously if you have relocked it after modding your phone this could cause issues which is why you should never re-lock the bootloader after unlocking it
Click to expand...
Click to collapse

braganetx said:
How can I start safe mode without accessing the system?
Click to expand...
Click to collapse
Option in bootloader menu
As stated if it doesn't boot there's not anything else you can do as your bootloader is locked
If you have never unlocked it then it could be a hardware fault
You will need to take it to a repair shop for diagnosis

TheFixItMan said:
Option in bootloader menu
As stated if it doesn't boot there's not anything else you can do as your bootloader is locked
If you have never unlocked it then it could be a hardware fault
You will need to take it to a repair shop for diagnosis
Click to expand...
Click to collapse
OK.
I appreciate the help, it seems that it is a hardware problem, apparently, there is no logic to not work.

braganetx said:
OK.
I appreciate the help, it seems that it is a hardware problem, apparently, there is no logic to not work.
Click to expand...
Click to collapse
Try using mmcblk0 file method, Maybe it can able to boot the device.

riyan65 said:
Try using mmcblk0 file method, Maybe it can able to boot the device.
Click to expand...
Click to collapse
But this method is when it’s not even entering fastboot, so what did I see here in research or not?
Because mine enters fastboot normally even in the recovery menu just does not start the system

braganetx said:
But this method is when it’s not even entering fastboot, so what did I see here in research or not?
Because mine enters fastboot normally even in the recovery menu just does not start the system
Click to expand...
Click to collapse
The image contain all system files with bootloader and firmware, so I just suggest you to try that method. And your device also not working, you can try this method.

Moto z2 force Flash Stock Wifi Issues x1789-04 tmobile

Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot

Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.

41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(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 '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'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
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.594s]
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' (3151 KB) OKAY [ 0.085s]
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' (23357 KB) OKAY [ 0.721s]
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' (516201 KB) OKAY [ 16.038s]
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' (495129 KB) OKAY [ 15.564s]
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' (519125 KB) OKAY [ 16.524s]
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' (523779 KB) OKAY [ 16.152s]
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' (516309 KB) OKAY [ 16.016s]
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' (420583 KB) OKAY [ 13.061s]
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' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...

If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.

it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?

insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot

41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04

Question Unlocked PAD 5 only shows red fastboot after Update to nabu_eea_global_images_V14.0.4.0.TKXEUXM

So here i am.
I've unlocked my Tab 5 after 7 days of waiting and decied to use the xiaoMiTool v2 to update to the nabu_eea_global_images_V14.0.4.0.TKXEUXM rom. Unfortunately after the successfull flash the tablets reboots 4-5 times and then shows me "fastboot" in red letters.
I'Ve tried to reflash the nabu_eea_global_images_V14.0.4.0.TKXEUXM again but it always ends up bootlooping and showing me the red fastboot letters.
I thought that just flashing the v14 Image over the fastboot option would let me start over (main goal is getting root/magsik).
Did i select the wrong update/image? I would have expected that little miui fastboot android splash screen and red letters seem wrong
Tablet came with miui 13.0.5. and I'm in Germany, that's why I chooses the Europe image with the toolkit.
Just tried to reflash the Global Firmware which also worked and it seems i'm able to go into recovery before all 5 bootloops are happening. So i can access fastboot and i'm able to access miui recovery 5.0 when the first boot happens.
TL;DR and the "Solution"
Flashing V13 worked - V14 did not. So i will update it over android and then root ;-)

Seelbreaker said:
So here i am.
I've unlocked my Tab 5 after 7 days of waiting and decied to use the xiaoMiTool v2 to update to the nabu_eea_global_images_V14.0.4.0.TKXEUXM rom. Unfortunately after the successfull flash the tablets reboots 4-5 times and then shows me "fastboot" in red letters.
I'Ve tried to reflash the nabu_eea_global_images_V14.0.4.0.TKXEUXM again but it always ends up bootlooping and showing me the red fastboot letters.
I thought that just flashing the v14 Image over the fastboot option would let me start over (main goal is getting root/magsik).
Did i select the wrong update/image? I would have expected that little miui fastboot android splash screen and red letters seem wrong
Tablet came with miui 13.0.5. and I'm in Germany, that's why I chooses the Europe image with the toolkit.
Just tried to reflash the Global Firmware which also worked and it seems i'm able to go into recovery before all 5 bootloops are happening. So i can access fastboot and i'm able to access miui recovery 5.0 when the first boot happens.
Click to expand...
Click to collapse
Have you tried re-downloading the file, maybe it's corrupt... https://xiaomifirmwareupdater.com/archive/miui/nabu/
Also, varify the download MD5 sum before flashing. Question; did you note the original ROM version - was it TKXEUXM or TKXMIXM? The latter is global, former EU ROM
Have you also tried with different flashing tool - https://miflashpro.com/ (ignore the box that opens to sign into MiAccount, just close that box if you use this tool)
When you do get it working, here's a good guide for pulling boot img and rooting Guide
OH and... Which ever tool you use to flash your device be sure to CHECK FLASH ALL, not flash all and lock

If you have only used Xiaomi Tool V2 and downloaded/flashed ROM automatically, would you like me to provide you with steps to flash fastboot rom using MiFlash Pro (MiFlash)??

Thanks for your reply!
No unfortunately i did not note which version was installed at the beginning.
I've let the XiaomiTool2 do the downloading because i assume those tools would check the md5 and tried Global, EU and "Other" Region but it did not help.
Also the tgz files don't have their md5 setup And miflashpro is always asking for flash skripts (which so far only got generated by the XiaomiToolv2)
The flash in fastboot goes completely trough but then it bootloops the whole time until it stays on fastboot.
At the beginning of the bootlops i'm also able to get into the recovery and then into sideload mode (because recovery is unauthorized) but flashing trough sideload fails 33 seconds after starting the flash and then immediately reboots.
I would have expected that atleast either the global or EU miui Rom would work if i flashed it trough fastboot but so far i did not have success.
I only know that i have miui 13.0.5 installed but i guess it shouldn't be a problem to flash 14.x.

reg66 said:
If you have only used Xiaomi Tool V2 and downloaded/flashed ROM automatically, would you like me to provide you with steps to flash fastboot rom using MiFlash Pro (MiFlash)??
Click to expand...
Click to collapse
Xiaomi Tool V2:
Done with EU set in the tool which automatically downloads/downloaded
nabu_eea_global_images_V14.0.4.0.TKXEUXM_20230305.0000.00_13.0_eea_d3eaf75a6f.tgz
1. Start the Tool
2. Agree the Disclaimer
3. wait till the drivers are installed
4. Select right option: "My Device is bricked I want to unbrick it"
5. OK, I understand
6. Device is charged --> Ok, I understand
7. Search for connected devices
- Device is in fastboot and shows serial and status fastboot
- Codename, Brand and Model are unknown
- Select that Device
8. Select my Device from the list (as it isn't recognized) (nabu - Xiaomi Pad 5)
9. Flashing starts (since the tgz has been downloaded already)
10. Flash done and automatically reboots
7 bootloops later (only seeing the android logo and the unlock icon) it shows fastboot and i can start the flashing process again.
At the beginning of the bootloops after the flash i'm able to get into the recovery by pressing Volume up.
But after the bootloops are done i can't seem to go into recovery mode.
Also here is the output from the flash_all.bat which gets created by the tool:
Spoiler: output from flash_all.bat
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>flash_all.bat
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot getvar product 2>&1 | findstr /r /c:"^product: *nabu" || echo Missmatching image and device
product: nabu
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot getvar product 2>&1 | findstr /r /c:"^product: *nabu" || exit /B 1
product: nabu
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if exist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\anti_version.txt (for /F "delims==" %a in (C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a ) )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if [1] EQU [] set CURRENT_ANTI_VER=1
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>(set version=1 )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if [1] EQU [] set version=0
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>set anticheck="antirollback check pass"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase boot_ab ||
Erasing 'boot_ab' (bootloader) Partition boot_a erase successfully
(bootloader) Partition boot_b erase successfully
OKAY [ 0.026s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash crclist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\crclist.txt ||
Sending 'crclist' (0 KB) OKAY [ 0.006s]
Writing 'crclist' OKAY [ 0.006s]
Finished. Total time: 0.027s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash sparsecrclist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\sparsecrclist.txt ||
Sending 'sparsecrclist' (0 KB) OKAY [ 0.015s]
Writing 'sparsecrclist' OKAY [ 0.003s]
Finished. Total time: 0.032s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash xbl_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\xbl.elf ||
Sending 'xbl_ab' (4054 KB) OKAY [ 0.103s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.031s]
Finished. Total time: 0.155s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash xbl_config_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\xbl_config.elf ||
Sending 'xbl_config_ab' (120 KB) OKAY [ 0.017s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.013s]
Finished. Total time: 0.046s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash abl_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\abl.elf ||
Sending 'abl_ab' (204 KB) OKAY [ 0.012s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.044s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash tz_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\tz.mbn ||
Sending 'tz_ab' (3115 KB) OKAY [ 0.083s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.050s]
Finished. Total time: 0.154s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash hyp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\hyp.mbn ||
Sending 'hyp_ab' (476 KB) OKAY [ 0.017s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.014s]
Finished. Total time: 0.049s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash devcfg_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\devcfg.mbn ||
Sending 'devcfg_ab' (53 KB) OKAY [ 0.016s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.009s]
Finished. Total time: 0.041s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash storsec C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\storsec.mbn ||
Sending 'storsec' (20 KB) OKAY [ 0.010s]
Writing 'storsec' OKAY [ 0.006s]
Finished. Total time: 0.033s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash bluetooth_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\BTFM.bin ||
Sending 'bluetooth_ab' (1020 KB) OKAY [ 0.032s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.024s]
Finished. Total time: 0.073s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cmnlib_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cmnlib.mbn ||
Sending 'cmnlib_ab' (385 KB) OKAY [ 0.023s]
Writing 'cmnlib_ab' (bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.016s]
Finished. Total time: 0.058s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cmnlib64_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cmnlib64.mbn ||
Sending 'cmnlib64_ab' (503 KB) OKAY [ 0.021s]
Writing 'cmnlib64_ab' (bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.014s]
Finished. Total time: 0.055s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash modem_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\NON-HLOS.bin ||
Sending 'modem_ab' (108236 KB) OKAY [ 2.565s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.783s]
Finished. Total time: 3.366s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash dsp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\dspso.bin ||
Sending 'dsp_ab' (65536 KB) OKAY [ 1.546s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.449s]
Finished. Total time: 2.019s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash keymaster_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\km41.mbn ||
Sending 'keymaster_ab' (273 KB) OKAY [ 0.019s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.058s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash aop_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\aop.mbn ||
Sending 'aop_ab' (196 KB) OKAY [ 0.016s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.045s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash qupfw_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\qupv3fw.elf ||
Sending 'qupfw_ab' (69 KB) OKAY [ 0.006s]
Writing 'qupfw_ab' (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.033s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase imagefv_ab ||
Erasing 'imagefv_ab' (bootloader) Partition imagefv_a erase successfully
(bootloader) Partition imagefv_b erase successfully
OKAY [ 0.013s]
Finished. Total time: 0.023s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash imagefv_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\imagefv.elf ||
Sending 'imagefv_ab' (2060 KB) OKAY [ 0.056s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.025s]
Finished. Total time: 0.103s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash uefisecapp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\uefi_sec.mbn ||
Sending 'uefisecapp_ab' (122 KB) OKAY [ 0.013s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.042s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash multiimgoem_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\multi_image.mbn ||
Sending 'multiimgoem_ab' (32 KB) OKAY [ 0.006s]
Writing 'multiimgoem_ab' (bootloader) Partition multiimgoem_a flashed successfully
(bootloader) Partition multiimgoem_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash super C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\super.img ||
Sending sparse 'super' 1/10 (722548 KB) OKAY [ 17.279s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 2/10 (744888 KB) OKAY [ 33.288s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 3/10 (772940 KB) OKAY [ 34.978s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 4/10 (775676 KB) OKAY [ 35.538s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 5/10 (786356 KB) OKAY [ 37.458s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 6/10 (735148 KB) OKAY [ 36.288s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 7/10 (735060 KB) OKAY [ 34.237s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 8/10 (743876 KB) OKAY [ 32.977s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 9/10 (785057 KB) OKAY [ 34.347s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 10/10 (478244 KB) OKAY [ 34.968s]
Writing 'super' OKAY [ 0.005s]
Finished. Total time: 331.443s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase metadata ||
Erasing 'metadata' OKAY [ 0.011s]
Finished. Total time: 21.497s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash metadata C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\metadata.img ||
Sending 'metadata' (48 KB) OKAY [ 0.005s]
Writing 'metadata' OKAY [ 0.008s]
Finished. Total time: 0.036s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vbmeta_system_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vbmeta_system.img ||
Sending 'vbmeta_system_ab' (4 KB) OKAY [ 0.013s]
Writing 'vbmeta_system_ab' (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vbmeta_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vbmeta.img ||
Sending 'vbmeta_ab' (8 KB) OKAY [ 0.014s]
Writing 'vbmeta_ab' (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.036s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash dtbo_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\dtbo.img ||
Sending 'dtbo_ab' (32768 KB) OKAY [ 0.769s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.240s]
Finished. Total time: 1.030s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash userdata C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\userdata.img ||
Sending 'userdata' (6136 KB) OKAY [ 0.147s]
Writing 'userdata' OKAY [ 0.183s]
Finished. Total time: 0.347s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash rescue C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\rescue.img ||
Sending 'rescue' (40 KB) OKAY [ 0.012s]
Writing 'rescue' OKAY [ 0.008s]
Finished. Total time: 3.529s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vendor_boot_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vendor_boot.img ||
Sending 'vendor_boot_ab' (98304 KB) OKAY [ 2.274s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.680s]
Finished. Total time: 2.972s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cust C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cust.img ||
Sending 'cust' (110024 KB) OKAY [ 2.615s]
Writing 'cust' OKAY [ 3.202s]
Finished. Total time: 5.843s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash boot_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\boot.img ||
Sending 'boot_ab' (131072 KB) OKAY [ 3.085s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.920s]
Finished. Total time: 8.885s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash misc C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\misc.img ||
Sending 'misc' (4096 KB) OKAY [ 0.105s]
Writing 'misc' OKAY [ 0.138s]
Finished. Total time: 0.263s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot set_active a ||
Setting current slot to 'a' OKAY [ 0.011s]
Finished. Total time: 0.015s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot reboot ||
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.003s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>
MiFlashPro:
1. Start the Application
2. Select MiFlash 2022.5.7.0
3. Select the Path to the extracted Package (extracted and prepared by XiaomiToolV2
4. Hit Refresh to see the Device
5. Hit Flash
Under configuration i had the defaults active which means nothing checked, no factory, main program set and Checkpoint has "\$fastboot -s .* lock" as an entry.
RawProgram xml and Patch xml are also empty.

Ok, so you have MiFlash Pro installed, right? Open it up and close the dialgue about signing in with Xiaomi account. Go to the 4th tab along the top 'Mi Flash' and select that.
Download the fastboot version at the bottom of this page (it's Global to try for now).
Extract the tgz file twice until you get a folder containing the images. Best to extract to the root of C: drive.
In Mi Flash click 'select' and point it to the main extracted folder of your ROM that contains the images folder and the RUN scripts.
Plug your phone into a USB 2.0 port in fastboot mode and click refresh in Mi Flash. Device should show under 'id'.
IMPORTANT: In Mi Flash, select 'clean all' in bottom right corner and NOT 'clean all and lock'
Click 'flash'.
Hopefully, fingers crossed you'll get flashed properly this time after 500+ seconds. Device will reboot when it's done. 1st boot takes some time. Mi Flash will probably give an error after flashing because the 'lock' wasn't done, but you don't want that anyway.
Good luck, report back when ur done if poss

Ahh, looks like you made another post while I was typing! Just incase something is up with Miflash tool V2 download, download it manually from the link in my post above and follow those instructions. Unfortunately there's no md5 to compare it with for that rom version on that site

Thank you very much for your help <3
I was always trying to install an V14 MIUI Version because obviously i wanted to have the latest version before starting the rooting and so on.
Now i just tried to flash a V13:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And it just works like you would expect, or atleast it booted into the starter setup.
What a hazzle.
Never thought that flashing the 14.x version wouldn't work, so i guess i will update to the latest version within android/miui and then start the rooting process.
Thanks for giving me the link which explains how to extract the boot image, this will make it easier for me
And yeah, extracting the tgz files will give me the batch-files anyways which miiflash also takes (as long as i don't lock it. Altough you can unlock it again with the mi unlock tool since that happened to me ).

Seelbreaker said:
Thank you very much for your help <3
I was always trying to install an V14 MIUI Version because obviously i wanted to have the latest version before starting the rooting and so on.
Now i just tried to flash a V13:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And it just works like you would expect, or atleast it booted into the starter setup.
What a hazzle.
Never thought that flashing the 14.x version wouldn't work, so i guess i will update to the latest version within android/miui and then start the rooting process.
Thanks for giving me the link which explains how to extract the boot image, this will make it easier for me
And yeah, extracting the tgz files will give me the batch-files anyways which miiflash also takes (as long as i don't lock it. Altough you can unlock it again with the mi unlock tool since that happened to me ).
Click to expand...
Click to collapse
Are you saying you're going to update each time via miui every update until you reach the latest?
Only I had a thought... You could try flashing/skipping to the last miui 13.1.4 before 14 was released.
(md5: eae12a3156a814d4ac6a7af801ab40b7)
Then flash miui 14 as before.

reg66 said:
Are you saying you're going to update each time via miui every update until you reach the latest?
Only I had a thought... You could try flashing/skipping to the last miui 13.1.4 before 14 was released here.
(md5: eae12a3156a814d4ac6a7af801ab40b7)
Then flash miui 14 as before.
Click to expand...
Click to collapse
No, i fastboot flashed to V13.1.5.0.SKXEUXM which worked (altough i can't even explain why the fastboot Flash to V14.x did not work) and after Android booted up and did the initial setup i've updated to the latest MIUI Version within Android which means i'm now on 14.0.4.0 (TKXEUXM).
Now i just gonna get my boot.img and then i can root.
But the recovery mode doesn't let me adb shell because i'm not authorized...​

Seelbreaker said:
No, i fastboot flashed to V13.1.5.0.SKXEUXM which worked (altough i can't even explain why the fastboot Flash to V14.x did not work) and after Android booted up and did the initial setup i've updated to the latest MIUI Version within Android which means i'm now on 14.0.4.0 (TKXEUXM).
Now i just gonna get my boot.img and then i can root.
But the recovery mode doesn't let me adb shell because i'm not authorized...​
Click to expand...
Click to collapse
Download 14.0.4.0.TKXEUXM fastboot rom and extract the tgz twice until you get the images folder. In images folder you'll find the boot.img for that EU version in order to root then flash

reg66 said:
Download 14.0.4.0.TKXEUXM fastboot rom and extract the tgz twice until you get the images folder. In images folder you'll find the boot.img for that EU version in order to root then flash
Click to expand...
Click to collapse
stupid me.
Yep, after unzipping these folders for some time, it just hit me while i was in the shower
Thanks again for your help, really appreciate that!

Seelbreaker said:
stupid me.
Yep, after unzipping these folders for some time, it just hit me while i was in the shower
Thanks again for your help, really appreciate that!
Click to expand...
Click to collapse
No worries, it dawned on me too that the other guide i linked you was using a custom recovery and that you're running stock miui, in which case the boot img is easily found as above. A big 'DOH' on both our parts!! Good luck with it all

I had the same problem. Why does flashing version 14 not work? any ideas?

opesel said:
I had the same problem. Why does flashing version 14 not work? any ideas?
Click to expand...
Click to collapse
Have you updated to latest/last 13 before flashing 14?

reg66 said:
Have you updated to latest/last 13 before flashing 14?
Click to expand...
Click to collapse
Yes I did, I just downloaded the latest 13 version and then flashes it and it worked, but the 14 doesn't.