Database Info

[XT-1033] Unable to mount /data, /system...

Translation by goole translate
Hello guys,
Recently, I updated the bootloader for the "Brazil - 5.0.2 - Bootloader.tar.gz", not to have problems installing the builds of CyanogenMod 12 . However, I install the cm12.1 and started the problems. When he failed installation of cm12.1 , I wipe and I install android 5.0 by fastboot , and failed , I tried to flash the 4.4.4 and failed again. Now I'm no OS on the device, and can only enter the bootloader mode and recovery mode ( TWRP ) , can anyone help me ? Thank you all.

Up!
Sent from my Nexus 5 using XDA Free mobile app

Try an advanced wipe of system, cache, data, internal storage, and dalvik cache then format the storage then sideload the rom. If that doesn´t work, you can get a zip file from somewhere to format your storage, seemed to work better for me than the format function in recovery.

Mancora1 said:
Try an advanced wipe of system, cache, data, internal storage, and dalvik cache then format the storage then sideload the rom. If that doesn´t work, you can get a zip file from somewhere to format your storage, seemed to work better for me than the format function in recovery.
Click to expand...
Click to collapse
Hello my friend,
Thanks for your help me, come on!
I tried to do a full wipe, as shown in the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I connected the Moto G on pc, and tried to copy and paste the rom.zip:
FAIL
I tried to connect an OTG cable with a USB stick with rom.zip , but the device did not work out:
FAIL AGAIN
Gentlemen, already tried all procedures in relation to this device , but have not lost hope, and I believe some xda developer, can help me solve this problem.
:good::good::good:

Looks like your partition table is messed up. Maybe you need to reinstall the stock ROM using mfastboot.

_that said:
Looks like your partition table is messed up. Maybe you need to reinstall the stock ROM using mfastboot.
Click to expand...
Click to collapse
Thanks for you help me, i tried flash the stock rom kk 4.4.4, view the log:
Code:
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot devices
0423483639 fastboot
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.410s]
writing 'boot'...
OKAY [ 0.699s]
finished. total time: 1.121s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.423s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.133s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.520s]
sending 'system' (249379 KB)...
OKAY [ 9.251s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 7.053s]
finished. total time: 16.841s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.512s]
sending 'system' (252566 KB)...
OKAY [ 9.405s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 6.521s]
finished. total time: 16.458s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.515s]
sending 'system' (249711 KB)...
OKAY [ 9.095s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 7.147s]
finished. total time: 16.771s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.749s]
writing 'modem'...
OKAY [ 1.209s]
finished. total time: 2.971s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot erase
modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.067s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot erase
modemst2
erasing 'modemst2'...
OKAY [ 0.063s]
finished. total time: 0.070s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash fsg
fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 5.569s]
finished. total time: 5.682s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.329s]
finished. total time: 0.336s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot erase
userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 2.927s]
finished. total time: 2.934s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.132s]
writing 'logo'...
OKAY [ 0.116s]
finished. total time: 0.263s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot flash
recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 0.304s]
finished. total time: 0.695s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>
Result: Bootloop

Lealdpo said:
Thanks for you help me, i tried flash the stock rom kk 4.4.4, view the log:
Code:
C:\Users\Rafael\Documents\Android Devices\Moto G XT-1033\ADB>fastboot devices
0423483639 fastboot
Click to expand...
Click to collapse
Is that the special Motorola fastboot? Regular fastboot probably can't flash the system sparsechunk files correctly. Also, doesn't the complete ROM include a partition table (gpt.img)?
If you can boot into TWRP, run "adb shell cat /proc/partitions" and post the output.

_that said:
Is that the special Motorola fastboot? Regular fastboot probably can't flash the system sparsechunk files correctly. Also, doesn't the complete ROM include a partition table (gpt.img)?
If you can boot into TWRP, run "adb shell cat /proc/partitions" and post the output.
Click to expand...
Click to collapse
Thank's my brother for his tip, I solved the problem . I downloaded the stock 5.0, downloaded and installed the mFastboot , did the flash and everything went well!
:good::good::good::good::good::good::good::good:

Blue Screen after booting up, any tips? I have already tried flashing new stock rom!

My xt1033 has been acting up and I can't boot it anymore. It literally finishes the boot on a full blue screen (nothing on the screen but the blue) and reboots. I have tried flashing a new rom following both "[GUIDE] Restore softbricked phone after Lollipop update" and "[ROM][4.4.4][STOCK][FLASHABLE ZIP] Stock Motorola KitKat ROM Collection" found on the stickies but they didn't fix my issue and now I am out of ideas... can someone please help me?
Thanks.

Follow the flashing instructions in first post exactly:
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection​

Wipe data via recovery or fastboot. This #$%$#%# bug is pretty common on Motorola's stock ROM.

Tried both recommendations and different stock roms (4.4.4, 5.0.2, 5.1 untouched and patched) and it simply won't boot... Decided to give CM a go, and it works on the first try. I guess I wil have to learn how to use CM...
Edit: And I was happy for only a few minutes... back to square 1 and bs resets/blue screens

dambros666 said:
Tried both recommendations and different stock roms (4.4.4, 5.0.2, 5.1 untouched and patched) and it simply won't boot... Decided to give CM a go, and it works on the first try. I guess I wil have to learn how to use CM...
Edit: And I was happy for only a few minutes... back to square 1 and bs resets/blue screens
Click to expand...
Click to collapse
In TWRP, did you Format Data (Wipe > Format DATA > Yes) ?

lost101 said:
In TWRP, did you Format Data (Wipe > Format DATA > Yes) ?
Click to expand...
Click to collapse
Yes, I always start the process by doing it, as specified in the threads.

It sounds to me like a hardware fault. Maybe try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
It sounds to me like a hardware fault. Maybe try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I am starting to consider to be a hardware fault as well. I already tried the factory firmware, same result :/ Just one thing about wiping data: should I do it AFTER finishing the flash as well?

dambros666 said:
I am starting to consider to be a hardware fault. I already tried the factory firmware, same result :/ Just one thing about wiping data: should I do it AFTER finishing the flash as well?
Click to expand...
Click to collapse
Provide a log - copy and paste command prompt screen - take screenshots. Fastboot cannot be trusted, flashing can completely fail without a single error message.

lost101 said:
Provide a log - copy and paste command prompt screen - take screenshots. Fastboot cannot be trusted, flashing can completely fail without a single error message.
Click to expand...
Click to collapse
This is the log for the Factory Firmware XT1033_FALCON_RETBR_DS_5.1_LPB23.13-56_cid12
Code:
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.313s]
finished. total time: 0.342s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.114s]
finished. total time: 1.215s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.060s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.157s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.377s]
writing 'boot'...
OKAY [ 0.917s]
finished. total time: 1.295s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.387s]
writing 'recovery'...
OKAY [ 0.920s]
finished. total time: 1.309s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257535 KB)...
OKAY [ 8.095s]
writing 'system'...
OKAY [ 16.439s]
finished. total time: 24.536s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256925 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 15.465s]
finished. total time: 23.545s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (256980 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 15.421s]
finished. total time: 23.502s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (175936 KB)...
OKAY [ 5.549s]
writing 'system'...
OKAY [ 11.219s]
finished. total time: 16.770s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.607s]
writing 'modem'...
OKAY [ 2.228s]
finished. total time: 3.836s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.036s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.066s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.093s]
writing 'fsg'...
OKAY [ 5.315s]
finished. total time: 5.409s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.096s]
finished. total time: 0.097s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.721s]
finished. total time: 1.721s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s

Everything looks okay with the flashing process. I've never heard of the issues you describe before.

lost101 said:
Everything looks okay with the flashing process. I've never heard of the issues you describe before.
Click to expand...
Click to collapse
I took some rain last week, and I am guessing it was the problem...
This is what I see after thr boot, and then it resets:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I got the same issue today, please help. Mine is pure stock lolipop 5.1.1

same issue, I have tried different kernels, roms and recovery but, still same. Is there anybody who knows how to fix this?

Facing the same problem.Getting restarted automatically and stucked at Blue scree.
It look like a hardware problem. Anyone tried to contact motorola service center?

same problem with blue screen stucked sometimes
Hi all... i have the same problem. my phone moto g xt1032 is stucked at blue screen sometimes.... i tried different roms and recovery and still the issue
the last i tried it was check on logcat in adb, waiting... and when the phone is stucked on blue screen... the log cat say something about... corruption internal...
sorry i cant save the screenshot of the logcat
actually i have installed the last stock firmware 5.1 EU version with the stock recovery
sorry for my poor english
@lost101 can you help me please??

@manjs - Via a PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

hi, i also got this problem.. i think its a hardware problem..

appu1988 said:
hi, i also got this problem.. i think its a hardware problem..
Click to expand...
Click to collapse
Most likely. It's certainly not a software issue I have ever seen.

Just insert a sim card
idk how but it solved in my case.

How can i make my moto g dual sim again...

Hi this is my first request for help ever, have tired almost all roms available on xda
I never needed to touch my rom till was on kitkat, i had heard the hole world crying for bugs with kitkat but my phone never reported any major bug (i had not even rooted my phone) then came the curse LOLIPOP 5.02 there were two things that made me force to unlock bootloader 1> slow 2nd> ghost windows showing up in taskbar
from the day i flashed to stock rom kitkat 4.4.4 us retail (xt1032) availabe on xda forum i lost my second sim working
till this date i have flashed endless roms even cwm 12 and all versions of stock for asian retail have not tried flashing and brazil fimware.
it just doesn't detect if any sim is inserted.
i have tried the stock radio thread for kitkat 4.4.4 , 5.02, 5.1 none of them work.
If anyone is having moto g xt1033 indian stock rom with dual sim working
can you please send me a screen shot of about section in settings
i want to check what baseband version you guys are having
one last thing i had made a backup using cynogen recovery but on restoring the backup my moto g never boots it was of stock lolipop can anyone help in this regards..
currently am on stock lolipop 5.1
my baseband version is MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
i think 1032 in above baseband means radio of xt1032 while i need 1033 (i guess)
i have updated using indian ota update of stock rom using stock recovery.
Issue still persists sim 2 not detected, both sims used to work before flashing any firware manually.

Simply flash the latest XT1033 Retail Asia 5.1 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log of the flashing process if this does not resolve your problem. Copy and paste the contents of Command Prompt. Take screen-shots if necessary.

edit: above method

new problem
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

huzeifa88 said:
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
Click to expand...
Click to collapse
now flashed 5.02 and it too just shows me the boot logo saying warning bootloader unlocked nothing else is happening getting a little tense now log for 5.02
C:\adb>flash.bat
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

Please stop trying different Firmware Images. Only do as directed for your own safety.
Edit: Manually type commands, do not use a .bat file or script. Skip the command related to motoboot.img - repeatedly flashing the Bootloader is dangerous and completely unnecessary.
Type the following command before any other:
mfastboot oem unlock​

lost101 said:
Please stop trying different Firmware Images. Only do as directed for your own safety.
Click to expand...
Click to collapse
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.

bootleoader version is 41.1A system is 5.02
huzeifa88 said:
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.
Click to expand...
Click to collapse
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.

huzeifa88 said:
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.
Click to expand...
Click to collapse
Stop flashing / messing with the Bootloader. Period. You will end up with a dead phone.

Finally back from dead
I flashed kitkat stock rom without trying to downgrade boot loader as i knew it could brick my phone and just as usual phone did not boot past boot logo of boot recovery stating boot loader unlocked...
but my luck turned kitkat stock rom recovery started to work without wasting time i flashed twrp recovery over kitkat stock recovery
once twrp i flashed cm12 last stable built volla cm12 booted
now still only one sim will work but i guess i had enough experiments i had once tried the donkey kernel on cm12 it never booted. so lets forget dual sim.
please dont recommend anyone to flash 5.1 stock rom i has some bug never boots or maybe coz i already had 5.1 installed using ota method.

@huzeifa88 - You are going to destroy your phone. I have tried to help you, but you ignore what I say.
Do not flash old Firmware Images and then accept an OTA Update. Your phone will switch off and never turn on again. I have already warned you to stop trying random Firmware Images.

phone doesnt boot on 5.1 had no options
I did flash the 5.1 lolipop image but phone did not boot it would just kept stuck at bootloader spash image (White color image saying boot loader unlocked) and did not reach the motorola animated boot screen
I left it there for around 30 mins after which i was sure its not gonna boot
Again even tried deleting all data and cache using fastboot command
even the recovery would not open it would stay on the bootloader splah screen
what i am experiancing with this phone is rare and happened 1st time maybe all those who have updated their boot loader should not mess with there cell anymore
anyway all is GOOD now i am HAPPLY using CM12 ROM and am never gonna flash any stock rom again.

Error 70 when trying to install GAPPS

Hi people
Yesterday I updated my phone to CyanogenMod(CM)13.0 which went fine. However when I rebooted the phone a popup came up the entire time telling me that google play services stopped working. In an attempt to fix it, I accidently removed google play services, causing a bunch of trouble at the moment.
I went to the CM Wiki and first I downloaded the "nano" variant of the GAPPS, trying to fix everything in the end. I put the file on my phone and tried to install it via recovery. This message came up however:
Insufficiënt storage space available in system partition. You may want to use a smaller GAPPS package or consider removing some apps using GAPPS-config ( bla bla) Error code 70.
As far as I can see, it is able to mount /system and /data, but the partition does not seem to have enough space left, at least so it says.
After that I tried the same with the "pico" variant, which also gave the same result. Pretty strange for a package that small.
So after taking a backup of important files I tried to wipe data/factory reset (was going to reinstall everything), to which I got an error "data wipe failed", which is correct since I can still boot in CM13 after that.
So I'm a bit in trouble here. I cannot seem to wipe my phone entirely, nor am I able to reinstall GAPPS due to this error 70.
Could this be a permissions problem somehow?
Things I have done so far to check what the problem could be:
- I've checked the space left on the /system partition which is 501 MB. Should be enough I guess?
- I've checked the /system partition for errors via adb shell while the phone was in recovery mode, which came out clean.
Below a picture of output of "mount", "df -h" and "uname -a" for extra information.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks

Was the phone dirty flashed from an older cm13 rom or was it dirty flashed over a non-cm13 rom?

What do you mean with dirty flashed?
i got this Phone from a friend and the Original stock rom was installed. I installed Cyanogenmod together with gapps and everything went fine back then.

Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.

audit13 said:
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
Click to expand...
Click to collapse
The Phone is working perfectly on its own, except for the google-applications.
That is the reason I only need GApps, to repair the initial problem.
Would it be a solution to format /data and /system and start all over? Although i'm worried that I will still not be able to install GApps due to error 70...

I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.

Which recovery do you use? TWRP or CWM?
Which build date of open gapps have you tried? The latest one?

audit13 said:
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Click to expand...
Click to collapse
It started installing after I initiated the flash-all command. This is the output. i downloaded the correct image and searched the net to know how I had to work with fastboot and such.
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
The full log:
D:\temp\Hammerhead>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
OKAY [ 0.536s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.107s]
finished. total time: 0.110s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.733s]
writing 'radio'...
OKAY [ 3.121s]
finished. total time: 4.858s
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
So, again something about the file being to large. I locked and unlocked the lock state of my phone to make sure it would remove data, to get more space. I guess it did not really work.
Anything else I can do?

Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?

audit13 said:
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
Click to expand...
Click to collapse
Non, they were not edited out. They just did not show up.
Ok, I got the Android stock rom installed on the phone, but now something else is wrong. here is what i did:
Code:
D:\temp\Hammerhead>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.632s]
sending 'system' (1020413 KB)...
OKAY [ 33.134s]
writing 'system'...
OKAY [ 68.970s]
finished. total time: 102.738s
D:\temp\Hammerhead>fastboot flash data data.img
error: cannot load 'data.img'
D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s
D:\temp\Hammerhead>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.489s]
sending 'cache' (13348 KB)...
OKAY [ 0.647s]
writing 'cache'...
OKAY [ 1.074s]
finished. total time: 2.215s
D:\temp\Hammerhead>fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.481s]
writing 'boot'...
OKAY [ 0.774s]
finished. total time: 1.260s
I first erased the partitions "system", "data" and "cache". After that I flashed "system", "userdata", "cache", and lastly "boot"
The phone booted into the rom, I entered my PIN, after which it complained my data was corrupt. It makes sense because of this:
"D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s"
It prolly needs the data partition to write stuff to.
Somehow the partition table of data seems to be gone.
So, the plot thickens! Is there a way I can recreate this partition table, or am I supposed to do something else?

fastboot flash userdata userdata.img
btw, nothing is wrong with your partition table, there is simply no partition on the phone called data. Data is part of userdata partition.

The commands are:
fastboot erase userdata
fastboot flash userdata userdata.img
The img file has to be extracted from the mmb29s zip file.

Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.

GTCG said:
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
Click to expand...
Click to collapse
Ok, I got it working again. Back on stock rom atm. Thanks for help everyone!

Agassi2-W09B - three buttons update - 5% and failed.

Hi. As the topic. I tried to upload lineage but something went wrong so I did a fastboot cleanup. I made the instructions:
fastboot erase preinstall
fastboot erase webtop
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase userdata
fastboot –w
After that I download firmware "Huawei MediaPad T5 AGS2-W09 hw demo Agassi2-W09B 8.0.0.181D(EEAC652) Firmware 8.0.0 r1 EMUI8.0 05015UUP [androidhost.ru]" which i copied in 8gb sd dload/update.app.
the operation lasts until 5% and system returned software install failed. Now I don't know what should I do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

after installation image in fastboot with codes i have another error. During installation i had problem with vbmeta. system returned information "'image verification error'"
C:\adb>fastboot erase system
Erasing 'system' OKAY [ 29.238s]
Finished. Total time: 29.250s
C:\adb>fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.085s]
Finished. Total time: 0.096s
C:\adb>fastboot erase cache
Erasing 'cache' OKAY [ 1.123s]
Finished. Total time: 1.134s
C:\adb>fastboot erase kernel
Erasing 'kernel' OKAY [ 0.219s]
Finished. Total time: 0.230s
C:\adb>fastboot flash kernel kernel.img
Sending 'kernel' (24576 KB) OKAY [ 0.631s]
Writing 'kernel' OKAY [ 0.477s]
Finished. Total time: 1.129s
C:\adb>fastboot erase ramdisk
Erasing 'ramdisk' OKAY [ 0.152s]
Finished. Total time: 0.163s
C:\adb>fastboot flash recovery_ramdisk ramdisk.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.847s]
Writing 'recovery_ramdisk' OKAY [ 0.269s]
Finished. Total time: 1.141s
C:\adb>fastboot erase vendor
Erasing 'vendor' OKAY [ 6.678s]
Finished. Total time: 6.689s
C:\adb>fastboot flash vendor vendor.img
Sending 'vendor' (16384 KB) OKAY [ 0.423s]
Writing 'vendor' OKAY [ 0.134s]
Finished. Total time: 0.578s
C:\adb>fastboot erase vbmeta
Erasing 'vbmeta' OKAY [ 0.055s]
Finished. Total time: 0.066s
C:\adb>fastboot flash vbmeta vbmeta.img
fastboot: error: cannot load 'vbmeta.img': No such file or directory
C:\adb>fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (6 KB) OKAY [ 0.005s]
Writing 'vbmeta' FAILED (remote: 'image verification error')
fastboot: error: Command failed
C:\adb>fastboot flash system system.img
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 12.891s]
Writing 'system' OKAY [ 5.768s]
Sending sparse 'system' 2/7 (459709 KB) OKAY [ 11.909s]
Writing 'system' OKAY [ 3.959s]
Sending sparse 'system' 3/7 (448134 KB) OKAY [ 11.817s]
Writing 'system' OKAY [ 4.148s]
Sending sparse 'system' 4/7 (456673 KB) OKAY [ 12.007s]
Writing 'system' OKAY [ 4.172s]
Sending sparse 'system' 5/7 (442991 KB) OKAY [ 11.536s]
Writing 'system' OKAY [ 3.716s]
Sending sparse 'system' 6/7 (415739 KB) OKAY [ 10.795s]
Writing 'system' OKAY [ 3.489s]
Sending sparse 'system' 7/7 (183048 KB) OKAY [ 4.772s]
Writing 'system' OKAY [ 1.642s]
Finished. Total time: 103.228s
C:\adb>fastboot flash cache cache.img
Sending 'cache' (6200 KB) OKAY [ 0.162s]
Writing 'cache' OKAY [ 0.098s]
Finished. Total time: 0.282s
C:\adb>fastboot flash userdata userdata.img
Sending 'userdata' (24576 KB) OKAY [ 0.632s]
Writing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.275s]
Finished. Total time: 0.930s
C:\adb>FASTBOOT REBOOT
fastboot: usage: unknown command REBOOT
C:\adb>fastboot reboot
Rebooting OKAY [ 0.020s]
Finished. Total time: 0.022s
C:\adb>
Click to expand...
Click to collapse
I added the recovery_ramdisk.img and ramdisk.img files. All the same. continuous bootloop. After all, I also uploaded the os lineage. And then the same.

Go to eRecovery and recover system (you deleted boot partition. that includes part of the bootloader, wich causes corrupt bootloader (or fastboot). vol+ and pwr button. If bootloader unlocked, wait for "your device has been unlocked" screen and then press vol+ for 5-6 sec. If bootloader is not unlocked, follow first part of my LOS18.1 installation guide. That will show you bootloader screen.
I recommend you to use LOS18.1 too. Performance is better than stock emui