Database Info

Please help - messed a few things up

Hello,
hope someone can help me with the mess i created. I have spent the last few days reading here but nothing seems to help.
What happened so far. I purchased a Mate 8. Downloaded the SRK toolkit and unlocked the bootloader, installed TWRP and root. So far everything went fine. I booted into TWRP and was smart enough to format the phone in TWRP in the hope to straight after that flash the official 3 ROM files. However, this failed and i was stuck with a phone without anything on it.
Next step was to download the italian knife, i picked unbrick and then "continue i have all the files..." which works fine
{
"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 a reboot the phone is stuck on "your device has been unlocked..." "Your device is booting now.." forever.
Any idea what else i can try? I have spent days mocking around with it and reading tutorials so far.
TIA

pcdd2015 said:
Hello,
hope someone can help me with the mess i created. I have spent the last few days reading here but nothing seems to help.
What happened so far. I purchased a Mate 8. Downloaded the SRK toolkit and unlocked the bootloader, installed TWRP and root. So far everything went fine. I booted into TWRP and was smart enough to format the phone in TWRP in the hope to straight after that flash the official 3 ROM files. However, this failed and i was stuck with a phone without anything on it.
Next step was to download the italian knife, i picked unbrick and then "continue i have all the files..." which works fine
After a reboot the phone is stuck on "your device has been unlocked..." "Your device is booting now.." forever.
Any idea what else i can try? I have spent days mocking around with it and reading tutorials so far.
TIA
Click to expand...
Click to collapse
- Which 3 rom files you mean ?
- rom version ?b???
- phone model? L29 or AL10
- You still have twrp recovery on phone or have stock recovery?

Thanks for the reply.
update.zip, update_full_NXT-L09_hw_eu.zip, update_data_full_public.zip
Phone model is NXT-L09
I believe it is stock recovery now since the flash went all fine with the italian knife.
Unfortunately i can' post a screenshot since i am a new user

This is what the Italian knife reports
===============================================================================
*** HUAWEI MATE 8 Italian knife by Raimondo Martire 2016.14.02 ***
===============================================================================
===============================================================================
*** Flashing Unbrick Files Mate 8 ***
===============================================================================
AXS02164290XXXXX fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15864 KB)...
OKAY [ 0.338s]
writing 'boot'...
OKAY [ 0.328s]
finished. total time: 0.672s
target reported max download size of 471859200 bytes
sending 'cust' (130851 KB)...
OKAY [ 2.790s]
writing 'cust'...
OKAY [ 1.650s]
finished. total time: 4.444s
target reported max download size of 471859200 bytes
sending 'recovery' (43872 KB)...
OKAY [ 0.936s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.821s
target reported max download size of 471859200 bytes
sending sparse 'system' (458199 KB)...
OKAY [ 10.439s]
writing 'system'...
OKAY [ 5.180s]
sending sparse 'system' (443157 KB)...
OKAY [ 10.413s]
writing 'system'...
OKAY [ 5.405s]
sending sparse 'system' (431150 KB)...
OKAY [ 10.024s]
writing 'system'...
OKAY [ 5.410s]
sending sparse 'system' (458239 KB)...
OKAY [ 10.731s]
writing 'system'...
OKAY [ 5.410s]
sending sparse 'system' (119170 KB)...
OKAY [ 2.805s]
writing 'system'...
OKAY [ 1.318s]
finished. total time: 67.161s
Press any key to continue . . .

L09 b???
Android 6 or 7?

hamadazh said:
L09 b???
Click to expand...
Click to collapse
I am sorry but i have no idea what you mean

pcdd2015 said:
I am sorry but i have no idea what you mean
Click to expand...
Click to collapse
I mean your Rom nougat or MM

hamadazh said:
I mean your Rom nougat or MM
Click to expand...
Click to collapse
THe last working ROM on it was Android 6

pcdd2015 said:
THe last working ROM on it was Android 6
Click to expand...
Click to collapse
Ok try this Go to recovery then factory reset then reboot

hamadazh said:
Ok try this Go to recovery then factory reset then reboot
Click to expand...
Click to collapse
THat's the problem, i can't boot into recovery. Just shows me the erecovery which offers me to download something but that fails

pcdd2015 said:
THat's the problem, i can't boot into recovery. Just shows me the erecovery which offers me to download something but that fails
Click to expand...
Click to collapse
Remove usb cable from phone and try again you already flashed stock recovery.

Hi , , where r u
I'm in second page in thread

pcdd2015 said:
THat's the problem, i can't boot into recovery. Just shows me the erecovery which offers me to download something but that fails
Click to expand...
Click to collapse
I have finally managed to boot into TWRP again. the official ROM's require official recovery and boot, right? Do you maybe know any ROM i can flash straight out of TWRP to a L09?
TIA

pcdd2015 said:
I have finally managed to boot into TWRP again. the official ROM's require official recovery and boot, right? Do you maybe know any ROM i can flash straight out of TWRP to a L09?
TIA
Click to expand...
Click to collapse
No I don't have more info about L09,,, sorry
Search in general threads.
https://forum.xda-developers.com/mate-8/general/nxt-l09c636b521-official-firmware-guide-t3544729

Why I got these, help!

I flash the factory image with the flash-all.bat, but I got these.
What shoule I do?
Code:
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.188s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
{
"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"
}

The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?

mikeprius said:
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?
Click to expand...
Click to collapse
The flash all command works fine on an unlocked bootloader. I've used it several times (I play around too much ) As for your second question, I haven't used a custom kernel but I have flashed Magisk which writes to the bootloader and I've never had a problem using the flash-all.bat file. Some people for some reason or another were able to use it (the flash all) for the December update but it would fail to write the bootloader for some reason or another. Some tried flashing the bootloader manually with fastboot and that would fail too. From what I've seen, the only way out for those with that problem was to flash the OTA. I don't know how many of them were using custom kernels so I can't really say if that's the problem or not. I can only tell you I flashed the December update using the flash all and had no problems at all.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
I have sloved this problem, I changed TYPE-C to TYPE-C cable to TYPE-C to TYPE-A cable and I flashed it.
I think it's google's cable's problem.

Bricked One plus 6 [no software workd] [Help post]

My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??

you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?

soihuvuontrang said:
you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?
Click to expand...
Click to collapse
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
{
"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"
}

zobayer.a.m said:
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
Click to expand...
Click to collapse
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!

soihuvuontrang said:
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!
Click to expand...
Click to collapse
Unfortunately my boot loader is locked. This will not work. I tried it also

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result

Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?

zobayer.a.m said:
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result
Click to expand...
Click to collapse
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...

°Washy said:
Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?

zobayer.a.m said:
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?
Click to expand...
Click to collapse
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you did not unlock bootbloader.and fastboot rom was completely failed.you should read on forum how to unblock bootloader,root oneplus 6.wish you success!

°Washy said:
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.
Click to expand...
Click to collapse
Negative. When I laslt flas MSM tool oos 10.3.0 boot loader was locked. I unlocked it as normal procedure (under developer opetion
turn on oem, usb debugging and other then go to fastboot mood any type command "fastboot oem unlock").

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??
Click to expand...
Click to collapse
Flash whatever build you want...and then go to mauronofrios xda page where it has fastboot roms for op6...download the oos version that you have...and there will be one option FLASH ONLY PERSIST(FLASH PERSIST)...flash it via fastboot with oos installed and sensors should work...but for that you have to unlock your bootloader first...
Feels like you've damaged your phones critical partitions....I SAID READ MAURONOFRIOS THREAD CAREFULLY... ESPECIALLY FLASHING INSTRUCTIONS...
Wait here for a minute...

Read this carefully...i said you damaged all your phones CRITICALS...SO WHAT YOU NEED TO DO?
ALSO READ FOR THE SENSOR FLASH THAT I'VE SAID...AND TRY IT...i also had a sensor problem back in the days(touch worked...but no other sensor like proximity or gyro working)...and tried msmtool several times... didn't helped me...but this guys thread helped a lot with that...
Here is the thread also if You can't find it
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/amp/

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.

soihuvuontrang said:
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.
Click to expand...
Click to collapse
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.

zobayer.a.m said:
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.
Click to expand...
Click to collapse
it's quite strange.Did you unzipped the file"IMAGES.ZIP"?
---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------
zobayer.a.m said:
My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??
Click to expand...
Click to collapse
error at"images.zip" it means that you have to unzip the file images.zip.

Lineage os 17.x, 18.x GSI

Hello, someone have bootloader unlocked and Is willing to try Lineage OS?
Here is the roms: Lineage OS 16.x, 17.x, 18.x
Download the a/b versión (treble_arm64_bv)
no root needed or twrp, just bootloader unlocked and a pc.
If someone tried, please let me know!

Did you try to install any GSI rom ???

works with all gsi? so I test

Niick.Ok said:
works with all gsi? so I test
Click to expand...
Click to collapse
Yes, should work with any GSI roms, please Let me know if you tried!

Someone tried this? I dont know how to install the rom, but i've already installed twrp

CæsarAM said:
Someone tried this? I dont know how to install the rom, but i've already installed twrp
Click to expand...
Click to collapse
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!

SaocMc said:
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!
Click to expand...
Click to collapse
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions

CæsarAM said:
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions
Click to expand...
Click to collapse
yes, because of it, you need to flash via fastbootd
After some research, this could be a posible solution:
flash the stock vbmeta with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
deleted product partition with fastboot delete-logical-partition product
flash the rom with fastboot flash --u system lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img
Factory reset from recovery
you can extract the vbmeta file from stock rom, https://mirrors.lolinet.com/firmware/moto/astro/official/

{
"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"
}
same error

I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me

Niick.Ok said:
I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me
Click to expand...
Click to collapse
because this device has dynamic partitions, can't install rom via recovery, only via fastbootd, but seems the lineage OS is larger than the system partition of our device, so we need to find a lighter rom or keep searching a solution

What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many

Niick.Ok said:
What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many
Click to expand...
Click to collapse
Basically, Fastbootd is a newer version of fastboot.
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
This steps are how fusion+ flash GSI roms(Copied from here: https://forum.xda-developers.com/t/rom-11-official-omnirom-liber.4232413/), the boot, dtbo and vmeta files are from stock rom, If anyone wants to try this, please let me know! Remember you need stock recovery and a factory reset after flashing the rom

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s

Niick.Ok said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s
Click to expand...
Click to collapse
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.

That's what I thought, when I got that error yesterday I tried to unlock the bootloader again, I tried via fastbootd and it didn't let me, I had to do it from the bootloader menu and there it left me, from fastbootd it told me that it did not know the commands, (summarizing I tried to unlock the bootloader again from the fastbootd menu and it wouldn't let me, so I tried from bootloader and it left me, but it told me that it was already unlocked, any other solution?

I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta

Niick.Ok said:
I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta
Click to expand...
Click to collapse
I found this tutorial: https://forum.hovatek.com/thread-32719.html
Method 3 is for flash a empty vmeta and disable verification.
You can try with both, the stock vmeta or the empty one.

I tried everything and I could not, I will wait for a developer to find a way, or for a rom to come out for this cell phone, I already tried the three methods that you sent me and more

SaocMc said:
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.
Click to expand...
Click to collapse
I get the exact same error no matter the GSI I try, bootloader is unlocked, flashing using fastbootd, I already hate this device...

Can't boot into TWRP

My aim here is to root my phone so I can run data recovery software to recover my WhatsApp.
I've unlocked my bootloader with "Mi Flash Unlock tool"
Then flashed "twrp-3.5.2_9-0-violet.img" via fastboot. It was successful.
Then I've tried multiple ways but can't boot into TWRP. Either the TWRP gets overwritten and my startes into stock recovery or it goes into a bootloop.
I've been at it for 2 days now and I even reached "The system has been destroyed" once. Had to download and install stock MIUI via fastboot again.
Additional info: MIUI 12.0.5 Global/Indian version. Bootloader unlocked.
Help me get through this ASAP please.

In this case, you should try executing 'fastboot boot twrp.img'.
This will auto reboot and bring you to a non-pernament TWRP, and the TWRP will disappear once you rebooted. If your interest is only in flashing a ROM and/or rooting, it is ok.

LR7875 said:
In this case, you should try executing 'fastboot boot twrp.img'.
This will auto reboot and bring you to a non-pernament TWRP, and the TWRP will disappear once you rebooted. If your interest is only in flashing a ROM and/or rooting, it is ok.
Click to expand...
Click to collapse
Tried. Goes into a bootloop

Have you tried other TWRP?

LR7875 said:
Have you tried other TWRP?
Click to expand...
Click to collapse
I"ve tried 2 versions - "twrp-3.5.2_9-0-violet.img" and "twrp-3.3.1-0-violet.img"
Just tried again
fastboot flash recovery twrp-3.5.2_9-0-violet.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.599s]
writing 'recovery'...
OKAY [ 0.312s]
finished. total time: 1.927s
fastboot boot twrp-3.5.2_9-0-violet.img
downloading 'boot.img'...
OKAY [ 1.473s]
booting...
OKAY [ 0.109s]
finished. total time: 1.613s
Didn't reboot at all. Kept sitting in the fastboot mode. If I try vol up+power it goes into a bootloop. So I repeated the command again.
fastboot boot twrp-3.5.2_9-0-violet.img
downloading 'boot.img'...
OKAY [ 1.430s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 6.623s

Then try flashing orangefox recovery, it basically does the same thing.
Xiaomi Redmi Note 7 Pro (violet) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi Note 7 Pro (violet)
orangefox.download
Extract the zip downloaded. Find the file 'recovery.img' (if you can't find it just open each folder and find).
Then try flashing the recovery.img image.

LR7875 said:
Then try flashing orangefox recovery, it basically does the same thing.
Xiaomi Redmi Note 7 Pro (violet) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi Note 7 Pro (violet)
orangefox.download
Extract the zip downloaded. Find the file 'recovery.img' (if you can't find it just open each folder and find).
Then try flashing the recovery.img image.
Click to expand...
Click to collapse
Thanks man. Will try and get back in a while.

LR7875 said:
Then try flashing orangefox recovery, it basically does the same thing.
Xiaomi Redmi Note 7 Pro (violet) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi Note 7 Pro (violet)
orangefox.download
Extract the zip downloaded. Find the file 'recovery.img' (if you can't find it just open each folder and find).
Then try flashing the recovery.img image.
Click to expand...
Click to collapse
Worked magic. I had orangefox within minutes. Thanks
I flashed orangefox via fastboot as you suggested and then used "fastboot reboot" with vol up pressed.
Now the next issue I'm facing is I can't find magisk zip file in orangefox. I'm going into the leftmost "files" tab opening "sdcard". It's full of files and folders with garbage names and my actual internal storage is nowhere to be found.
I tried toggling some things in the settings but I don't understand these. Can you or anyone suggest me how to use orangefox?
(FYI - The timing in my phone in the pic is wrong. ignore)
{
"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 think encryption was the issue. using "fastboot erase userdata" and booting straight to recovery from fastboot fixed it for me. My phone is rooted.
Thanks to this guy.
And thank you so much @LR7875 for all the help.

Hello,I was on official miui latest version for Violet. I unlocked my bootloader and erased the userdata in fastboot and installed twrp 3.5.2_9 on my violet and when I opened the TWRP the touch is not working.
I then again erased the userdata and tried installing orange fox recovery, but still I faced the same issue.
Please help me

MohdAhmed said:
Hello,I was on official miui latest version for Violet. I unlocked my bootloader and erased the userdata in fastboot and installed twrp 3.5.2_9 on my violet and when I opened the TWRP the touch is not working.
I then again erased the userdata and tried installing orange fox recovery, but still I faced the same issue.
Please help me
Click to expand...
Click to collapse
Try older builds of both TWRP and orangefox maybe?