Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
try with C432B170 file... that may help
amageek said:
try with C432B170 file... that may help
Click to expand...
Click to collapse
Thank you for your suggestion. I grabbed the update.app file for HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU and extracted the BOOT.img, CUST.img, RECOVERY.img and SYSTEM.img with the HuaweiUpdateExtractor. After which I flashed my device again, console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.582s]
writing 'boot'...
OKAY [ 0.650s]
finished. total time: 1.234s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.196s]
writing 'cust'...
OKAY [ 3.977s]
finished. total time: 10.175s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.807s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.712s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.539s]
writing 'system'...
OKAY [ 7.464s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.425s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.435s]
writing 'system'...
OKAY [ 7.380s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.311s]
writing 'system'...
OKAY [ 7.180s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.624s]
writing 'system'...
OKAY [ 7.391s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.378s]
writing 'system'...
OKAY [ 0.809s]
finished. total time: 101.698s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
C:\adb>
However it did not end the boot loop sequence. I am presented with the logo then straight into a black screen. After 2 or 3 minutes the device reboots.
Did I do it incorrectly?
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
amageek said:
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.583s]
writing 'boot'...
OKAY [ 0.645s]
finished. total time: 1.231s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.805s]
writing 'recovery'...
OKAY [ 0.896s]
finished. total time: 1.704s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.192s]
writing 'cust'...
OKAY [ 3.968s]
finished. total time: 10.162s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.667s]
writing 'system'...
OKAY [ 7.465s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.933s]
writing 'system'...
OKAY [ 7.410s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.644s]
writing 'system'...
OKAY [ 7.389s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.462s]
writing 'system'...
OKAY [ 7.152s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.775s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.403s]
writing 'system'...
OKAY [ 0.805s]
finished. total time: 102.527s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
Still no luck through, however the reboot cycle is much faster if that means anything.
I transferred the dload folder onto a SD card in order to restore. Holding down the volume up and down buttons along with power for 12 seconds. While the device does vibrate as if command was accepted it never shows anything beyond the logo.
Do you have any further advice or an idea as to what is my device's problem?
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
amageek said:
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
Click to expand...
Click to collapse
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
marcolomboss said:
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
Click to expand...
Click to collapse
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
YetAnotherP8Owner said:
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
Click to expand...
Click to collapse
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
YetAnotherP8Owner said:
Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
Click to expand...
Click to collapse
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
marcolomboss said:
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
Click to expand...
Click to collapse
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
cristi.blidariu said:
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
Click to expand...
Click to collapse
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
very interesting. You're in the wrong place, but where
Marcolomboss
YetAnotherP8Owner said:
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
Click to expand...
Click to collapse
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
cristi.blidariu said:
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
YetAnotherP8Owner said:
Flashed with the provided images; console results:
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
To enter the recovery mode you need to press and hold volume up and power buttons only
YetAnotherP8Owner said:
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
cristi.blidariu said:
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
YetAnotherP8Owner said:
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
Click to expand...
Click to collapse
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
cristi.blidariu said:
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
YetAnotherP8Owner said:
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
Click to expand...
Click to collapse
You can extract from any firmware stock recovery using huawei update extractor,what i gave you is a custom recovery,the command is fastboot flash recovery recovery.img
Sent from my ALE-L21 using XDA-Developers mobile app
After i i flash custom rom the i cant turn on the wifi so i decided to reset factory of my red magic 3 but after a rest i got stuck in FASTBOOT MODE no matter what i choice from reboot from recovery mode or reboot from system it will just restart and back again to FASTBOOT MODE can some one help me please is this permanent brick?
I USE ALL COMMANDS BUT DON'T WORK :
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ -0.000s]
writing 'vbmeta'...
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.819s]
writing 'dsp'...
OKAY [ 0.406s]
finished. total time: 2.230s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.219s]
writing 'splash'...
OKAY [ 0.031s]
finished. total time: 0.266s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144196 KB)...
OKAY [ 4.018s]
writing 'modem'...
OKAY [ 0.869s]
finished. total time: 4.888s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.780s]
writing 'boot'...
OKAY [ 0.469s]
finished. total time: 3.253s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.234s]
writing 'dtbo'...
OKAY [ 0.063s]
finished. total time: 0.297s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' (767446 KB)...
OKAY [ 24.161s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (786430 KB)...
OKAY [ 33.767s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (744616 KB)...
OKAY [ 30.043s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (786429 KB)...
OKAY [ 37.173s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (532404 KB)...
OKAY [ 26.319s]
writing 'system'...
OKAY [ 0.002s]
finished. total time: 151.675s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.800s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 3.339s
Instructions are everywhere. Follow them, or forever hold your peace.
after "fastboot flash recovery recovery.img"
write fastboot oem nubia_lock NUBIA_NX629J
and then fastboot reboot
u will get into recovery mode
Sir my Nubia red Magic 3 stuck on logo can any one help me please
Hello everyone, I own a Moto g6 xt1925-4 and I decided to root the device. First thing I unlocked the bootloader, it worked (with bad key logo). Second, I flashed TWRP, which I downloaded the IMG of from the official thread here on XDA. Third, I flashed the no-verity modified image: now I think I made a mistake because I flashed a OPS image which I should suppose is Oreo but the device was already updated to PIE.
Then the troubles started. I couldn't flash magisk, so I tricked too much on the MOUNT page on TWRP, perhaps I have mounted system or storage, then I also pulled out the USB cable without safe ejection and in the end, when I rebooted the phone in Bootloader mode and pushed Start, nothing happened at all.
I thought then: I have to restore to stock. I followed the procedure on the thread here on XDA, and I should say, something happened, but strange.
Now the phone boots up, but goes in a kind of a strange bootloop, because sometimes it says the "hello moto", sometimes not, sometimes it even starts the initial configuration, but the screen flashes on and off at random, and a few centimeters of the bottom screen are black. This happened also on TWRP recovery, the bottom part of the screen appeared cut by 2/3 centimeters.
Now I surely made mistakes, but I can't get what's wrong, and most of all this in going to get me crazy. I'm near to desperation, so I pray you to help me, please!
This is the result of the stock firmware flash I tried twice. I can see a couple of "failed" and "no such files"
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Programmi\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.090s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71577 KB)...
OKAY [ 10.255s]
writing 'modem'...
OKAY [ 0.571s]
finished. total time: 10.836s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (6780 KB)...
OKAY [ 2.464s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 2.564s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 3.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.300s]
finished. total time: 3.815s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'system' (259756 KB)...
OKAY [ 65.294s]
writing 'system'...
OKAY [ 2.293s]
finished. total time: 67.587s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'system' (253441 KB)...
OKAY [ 27.379s]
writing 'system'...
OKAY [ 1.763s]
finished. total time: 29.142s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.2
target reported max download size of 534773760 bytes
sending 'system' (254074 KB)...
OKAY [ 32.957s]
writing 'system'...
OKAY [ 1.773s]
finished. total time: 34.730s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.3
target reported max download size of 534773760 bytes
sending 'system' (260545 KB)...
OKAY [ 44.554s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 46.357s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.4
target reported max download size of 534773760 bytes
sending 'system' (259733 KB)...
OKAY [ 28.171s]
writing 'system'...
OKAY [ 1.813s]
finished. total time: 29.983s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.5
target reported max download size of 534773760 bytes
sending 'system' (246724 KB)...
OKAY [ 36.092s]
writing 'system'...
OKAY [ 1.682s]
finished. total time: 37.794s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.6
target reported max download size of 534773760 bytes
sending 'system' (246141 KB)...
OKAY [ 24.425s]
writing 'system'...
OKAY [ 1.702s]
finished. total time: 26.148s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.7
target reported max download size of 534773760 bytes
sending 'system' (262029 KB)...
OKAY [ 26.448s]
writing 'system'...
OKAY [ 1.933s]
finished. total time: 28.391s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.8
target reported max download size of 534773760 bytes
sending 'system' (262001 KB)...
OKAY [ 26.198s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 28.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.9
target reported max download size of 534773760 bytes
sending 'system' (25072 KB)...
OKAY [ 2.654s]
writing 'system'...
OKAY [ 0.170s]
finished. total time: 2.824s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'vendor' (260148 KB)...
OKAY [ 35.711s]
writing 'vendor'...
OKAY [ 2.023s]
finished. total time: 37.744s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'vendor' (178315 KB)...
OKAY [ 16.644s]
writing 'vendor'...
OKAY [ 1.412s]
finished. total time: 18.056s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.080s]
finished. total time: 0.080s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.681s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.751s
C:\Programmi\Minimal ADB and Fastboot>fastboot reboot
EDIT:
Good news, at least for me. I solved by flashing the PIE STOCK ROM, despite I liked OREO the most, I find this PIE slower and less smooth but anyways, that's it, I have my phone back.
But still..... I can't get the root, but that's fine, I'm still enjoying the feel of victory... maybe I'll try, some day...
We will flash the ubuntu touch boot image which is required temporarily. And the currently latest sfos build for the QX1050.
1. Download ubuntu touch build from here and extract the boot.img
Ubuntu for Pro¹ X build job 2830649718 artifact.zip
2. Download SailfishOS 4.4.0.64 build from here and extract the userdata.simg
SailfishOS for Pro¹ X job 2807435728 artifact.zip
3. Flash using fastboot
Code:
fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg
4. Reboot using fastboot reboot or fastboot continue
Thanks for moving mods! Did not realize its more appropriate here in the guides section than in the development section.
fastboot flash userdata userdata.img
fastboot flash userdata userdata.simg Typo
Nope, the sailfish userdata is in sparse format. So its .simg correctly.
Thats why you will not have the infamous "Invalid sparse file format at header magic" message from fastboot when flashing that .simg. Since fastboot expects sparse images, but *****es about raw images like the ubuntu boot.img above.
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
bobnot said:
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
Click to expand...
Click to collapse
what version of the android platform tools are you using? I'm on r33.0.2 and "fastboot flash userdata userdata.simg" works just fine for me
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
eltmosen said:
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
Click to expand...
Click to collapse
Neither SFOS or UT will boot
I also updated to latest fastboot from googles source. Still same issue as previously stated.