Develop Bugs

S710d HTCDev Unlock 2.3.4 hboot 1.04 help, please

Hey, guys.
Been searching around the forums for a couple days. Found plenty of people with my problem, but no one seemed to post their solutions. I'm a Candian living in China, and am looking to root for obvious reasons.
Running HTC S710d, 2.3.4 with Hboot 1.04
I'm using Prototype7's guide, however when I get to: adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tmp/misc_version -s 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
Is my return.
Any help would be greatly appreciated.

Exzyle said:
Hey, guys.
Been searching around the forums for a couple days. Found plenty of people with my problem, but no one seemed to post their solutions. I'm a Candian living in China, and am looking to root for obvious reasons.
Running HTC S710d, 2.3.4 with Hboot 1.04
I'm using Prototype7's guide, however when I get to: adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tmp/misc_version -s 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
Is my return.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Firmware version? Are you running a custom ROM or stock 6.x?

Actually, the ROM version says 3.x.

type
"adb shell
/data/local/tmp/misc_version -s 2.18.605.3"

JehC said:
type
"adb shell
/data/local/tmp/misc_version -s 2.18.605.3"
Click to expand...
Click to collapse
C:\Android>adb shell
$ /data/local/tmp/misc_version -s 2.18.605.3
/data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
$​
Recognized the dollar sign, so I tried SU.
$ su
su
# /data/local/tmp/misc_version -s 2.18.605.3
/data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
# exit
exit
$ exit
exit
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HC27JMA00835 fastboot
C:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s​
That however, got me here...
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 62.949s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 102.758s​
There is an option to disable signature verification in 4ext. Is this what I want to do?

Exzyle said:
C:\Android>adb shell
$ /data/local/tmp/misc_version -s 2.18.605.3
/data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
$​
Recognized the dollar sign, so I tried SU.
$ su
su
# /data/local/tmp/misc_version -s 2.18.605.3
/data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
# exit
exit
$ exit
exit
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HC27JMA00835 fastboot
C:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s​
That however, got me here...
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 62.949s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 102.758s​
There is an option to disable signature verification in 4ext. Is this what I want to do?
Click to expand...
Click to collapse
Relock your device then flash
Sent from my Goonified Paranoid Jelly Droid Incredible 2

The device was locked, although I should have included that. Skipped it since it worked. Here's all of the pertinent code, of course as I said, the device has been relocked at this stage.
C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01
.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
C:\Android>fastboot devices
HC27JMA00835 fastboot
C:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s
C:\Android>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.141s]
finished. total time: 0.141s
C:\Android>fastboot oem rebootRUU
... OKAY [ 0.146s]
finished. total time: 0.147s
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra
dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 60.221s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 110.190s​

Exzyle said:
The device was locked, although I should have included that. Skipped it since it worked. Here's all of the pertinent code, of course as I said, the device has been relocked at this stage.
C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01
.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
C:\Android>fastboot devices
HC27JMA00835 fastboot
C:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s
C:\Android>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.141s]
finished. total time: 0.141s
C:\Android>fastboot oem rebootRUU
... OKAY [ 0.146s]
finished. total time: 0.147s
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra
dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 60.221s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 110.190s​
Click to expand...
Click to collapse
Try again, redownload and try a few times. If it still won't work, try renaming it to PG32IMG.zip, put it in the root of your sdcard and just boot into the bootloader.

I re-downloaded the file, renamed the file PG32IMG and dropped it in the root of my SD card. Booted into bootloader, the bootloader found the zip file, a blue progresss bar filled, then said it was checking, a yellow progress bar filled and then... Nothing. Figured maybe you meant the Radio file, so I did the same. Also nothing.
Am I missing something?

Still no luck guys.
Anyone able to offer any help?
Getting very frustrated.

You're still at 2.3.4 s-on right?
try this in command prompt/terminal whichever you use:
"fastboot devices"
"fastboot getvar mainver" make sure its 2.18.605.3
"fastboot oem lock" (unless your bootloader already says relocked)
"fastboot erase cache"
"fastboot oem rebootRUU" wait until you're at a black screen that says HTC
"fastboot flash zip (name of zip, the RUU)" it'll take awhile, don't touch anything till it's done.
you'll now be at android 2.3.3, run revolutionary. once that's finished.
"adb devices"
"adb reboot bootloader"
"fastboot oem rebootRUU"
"fastboot flash zip (name of zip, the radio)" same as before

[SOLVED] Won't boot and random fastboot errors after upgrade attempt

Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!

hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows

Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#

hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update

Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…

hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:

All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!

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.

Pixle 2XL stuck in fastboot loop

Hi all, really annoying problem where my phone is stuck in a fastboot loop. The phone loads into fastboot and if it is plugged into the PC via USB it keeps rebooting into fastboot. I can use this command 'fastboot oem fb_mode_clear' when it's about to load and it sometimes causes it to stop rebooting. As soon as I input another command like fastboot devices, it begins the loop again. It also only shows ?????? as the device name.
Is there anything I can do if I do manage to get it to stop rebooting while it's connected to the PC? Thanks.
An example of the rebooting -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (remote: unknown command)
finished. total time: 0.014s

Here's what happens when I try and flash the factory image:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
W/ziparchive(133904): Unable to open 'image-taimen-opd1.170816.010.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.010.zip': I/O error
Press any key to exit...

This is the best I've done I think...
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.009s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.199s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1866 MB) to disk... took 9.931s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.077s
archive does not contain 'vendor.sig'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.012s
Press any key to exit...

Hi, in case you stumble on this self-rambling thread looking for an answer, it turns out changing the port fixed it. In my case I plugged it into a usb-c hub that had usb-a ports and that allowed it to work properly. God knows why, but worth a shot if anybody is having issues with their PC's usb ports.

soft brick bootloop after twrp flash

Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>

liltechie said:
Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>
Click to expand...
Click to collapse
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)

Kirasu2080 said:
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)
Click to expand...
Click to collapse
Thank you. Helped solving the bootloop issue.