Develop Bugs

Flash bootloader and boot.img?

When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?

xdadevelopersrocks said:
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
Click to expand...
Click to collapse
No. Everything else is contained in the rom zip.
Sent from my Nexus 5X using Tapatalk

OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?

xdadevelopersrocks said:
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
Click to expand...
Click to collapse
The rom dev will inform you which Android base is installed if you read their changelog. Then you download that factory image from Google to flash vendor. Radio and bootloader are optional.
Sent from my Nexus 5X using Tapatalk

Re-Lock Bootloader Of Moto G5 Plus (Indian Variant)

This Article Will Guide You to how to relock the bootloader of your moto g5 plus (Indian Variant) It should work on other Variants to but tested only on the indian variant.
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom Link:- (https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
Download the last file that has brasil in file name
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock​ Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
After locking bootloader, flash full Rom to get ota
https://pastebin.com/ZWTaWuyr
This are the commands to flash full rom.
Thanks To Telegram Group for the commands link.

Nirbhay2 said:
This Article Will Guide You to how to relock the bootloader of your moto g5 plus (Indian Variant) It should work on other Variants to but tested only on the indian variant.
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom (Available In The Moto G5 Plus forum)
3.Nothing Else
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock​ Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
*Don't Skip Any Command.
Click to expand...
Click to collapse
The process worked I could reblock the bootloader of my G5 Plus XT1680

Knight sparda said:
The process worked I could reblock the bootloader of my G5 Plus XT1680
Click to expand...
Click to collapse
Nice. Means it working for other Variant also

I don't think you will receive OTA updates even after locking the bootloader again.
Sent from my Moto G (5) Plus using Tapatalk

You have forget for flashing Recovery too.

matrixzone said:
I don't think you will receive OTA updates even after locking the bootloader again.
Click to expand...
Click to collapse
After locking bootloader, if u flash the whole rom again then u will be able to get OTA updates as normal. 100% Tested by me

Schrotty35 said:
You have forget for flashing Recovery too.
Click to expand...
Click to collapse
Flash full Rom after locking the bootloader.

After? You mean bevor.

Schrotty35 said:
After? You mean bevor.
Click to expand...
Click to collapse
Yes. After locking the bootloader you can flash full rom.

Nirbhay2 said:
Yes. After locking the bootloader you can flash full rom.
Click to expand...
Click to collapse
Can you elaborate?
Do we need to do something else after executing these commands to get otas

Rajul said:
Can you elaborate?
Do we need to do something else after executing these commands to get otas
Click to expand...
Click to collapse
You have to flash full rom to get ota.
Commands are here:- Taken From Telegram Group.
https://pastebin.com/ZWTaWuyr

Nirbhay2 said:
You have to flash full rom to get ota.
Commands are here:- Taken From Telegram Group.
https://pastebin.com/ZWTaWuyr
Click to expand...
Click to collapse
Now that my bootloader is locked,cqn these commands be executed?

Rajul said:
Now that my bootloader is locked,cqn these commands be executed?
Click to expand...
Click to collapse
Yes

I ran in the rom Brazil latam Mexico did not work, and also tested other roms and to no avail, always asks for the signed system image.

reuber said:
I ran in the rom Brazil latam Mexico did not work, and also tested other roms and to no avail, always asks for the signed system image.
Click to expand...
Click to collapse
You have done something wrong. This method is working 100%. Explain the error. Which build you are trying to flash...?

I am using the stock XT1681-XT1683_POTTER_BRASIL_latam_MEXICO (NPNS25.137-15) and following all the commands and in the end returns the message (still requires signed boot.img) will it be due to my device being Brazilian?

I get same error on my EU Version.

everything works perfectly in indian variant
1.download the brazillian variant of stock rom
2.follow these steps
3.flash whole stock rom using commands posted.
4.you will get ota as soon as you start device

Schrotty35 said:
I get same error on my EU Version.
Click to expand...
Click to collapse
In fact this is not a bug, but a bootloader requirement to flash a signed system image, I think!
---------- Post added at 08:27 PM ---------- Previous post was at 07:40 PM ----------
Rajul said:
everything works perfectly in indian variant
1.download the brazillian variant of stock rom
2.follow these steps
3.flash whole stock rom using commands posted.
4.you will get ota as soon as you start device
Click to expand...
Click to collapse
Should only work then in the Indian variant

reuber said:
In fact this is not a bug, but a bootloader requirement to flash a signed system image, I think!
---------- Post added at 08:27 PM ---------- Previous post was at 07:40 PM ----------
Should only work then in the Indian variant
Click to expand...
Click to collapse
The full rom is already signed.

How to get back to original STOCK ROM?

Hello,
i am currently running Dedrak Essential 1.3.0 which is a kind of 7.0 Stock ROM. But i want to get the orginal Moto-Stock. How to get that? I know there ist a Service Image of 6.0 and i had to do some fastboot/mfastboot actions. But i am not really sure if would this work or brick my device.
Can anyone give me an advice?
thanks
Peter

Just use RSD lite and flash original FW for youe device.
Here you can get 7.1.1 fully stock ROM (retin or retus - I don`t sure)
I flash it to my XT1635-03 and it works just perfect.
P.S. If you have issues with RSD flashing - just use fastboot with the next commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot

acutally i need reteu. Well i will look for it.
Thanks so far

Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.

i dont have that july patch. Dedrak was still on January.... so its 7.0 and it this was also the las official update i got changed to dedrak.
So it should work.

Dchoi229 said:
Keep in mind if you already upgraded your bootloader from the official July Patch and patch you'll hard brick your Moto Z play if you upgrade and downgrade. I'd advise you to flash the ROM and not the actual firmware.
Click to expand...
Click to collapse
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.

Dchoi229 said:
I honestly can't give you a solid answer. If you look at other threads you can find out why. It definitely has something to do with the bootloader.
Click to expand...
Click to collapse
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?

Zixione said:
Every other thread (that I found) just states as axiom - "downgrading will hardbrick" without clarification - why. But wouldn't
Code:
fastboot flash bootloader bootloader.img
solve all that "bootloader related stuff"?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492

Dchoi229 said:
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc.
Click to expand...
Click to collapse
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.

Zixione said:
Already seen this. The only useful bits of info about downgrading\bricking cause is, again, just statement, that "some updates/flash packages do not allow downgrading", but again without much clarification how exactly some data, sent to flash memory, will block itself from being written:
Many thanx, anyway !:good: I just need deeper explanation, will search onward myself.
Click to expand...
Click to collapse
yea.. sorry I'm not much of a developer. You can definitely look inside that thread and see that there are deeper explanations. I believe after a certain update (april security patch i believe) the bootloader is upgraded and when downgrading to a official firmware (MM 6.0.1) the updated bootloader will not work correctly and hard brick the Moto z play. I dont play with the bootloader anymore after hearing of this. Your best option is just to flash stock roms. Best of luck to you my friend. :good:

I am in a similar position wanted to go back to stock deodexed N but I can't because it is rooted with super su and I want to root with magisk which is not possible. Or I think as much anyway.

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
<snip>
Why hardbrick?
Click to expand...
Click to collapse
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device. The likely reason for this appears to be that the OTA only verifies your system version and whether the system, OEM and other partitions are of the same patch level. It does not necessarily check whether your bootloader and GPT are matching your system before patching. Also, downgrading may not downgrade your bootloader (and sometimes doesn't, where it's blocked by a 'security downgrade' warning), leaving you with a mismatched system. Looking through the OTA scripts for the Moto G4 updates, for example, the checks are mainly: is this the correct build to flash over, and are the system partitions unmodified? If yes to both, then it proceeds to flash and then copies over the bootloader files for that OTA. I've not seen an OTA check to verify your bootloader is of the correct patch level (if someone knows better, feel free to correct me).
To use your illustration:
Code:
F1: STOCK FIRMWARE [B]V.2[/B]
O2: OTA UPDATE V.3
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O3O3O3O3F1F1O3O3O3O3F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
This is after the OTA update to V3, taken after the OTA to V2. We assume that boot is the bootloader (the secondary bootloader, including the TrustZone and other bootloader partitions), and system includes the kernel and other system components.
If you downgrade to V1 from V3:
Code:
F1: STOCK FIRMWARE V.1
F1O3F1O3O3O3O3F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
You'll notice your bootloader has not downgraded (which can occur in fastboot), since the bootloader blocks you from downgrading your bootloader, especially in the newer stock firmwares. You'll also notice that your system is V1 though. Thus, though your system is V1, your bootloader is V3.
If you take an OTA update to V2, therefore, the OTA appears to look at your system, think your device is all V1 (including your bootloader), and proceed to patch to V2. Of course, as your bootloader is V3, then there is a high likelihood of the V2 OTA corrupting your V3 bootloader, leading to a hard brick.
We've seen this with the Moto Z Play (from the 7.1.1 to 7.0), Moto G4/Plus (downgrading from the June 2017 patch), and other Moto devices. Though this behaviour isn't restricted to Moto devices, it seems to more prevalent after the April/May/June 2017 stock patch updates (possibly to stop you reopening the Motorola bootloader vulnerability?). Thus, as others have suggested, do not downgrade if you can, or be careful and do not flash OTA updates. Try to flash the same stock ROM as what was on your device previously.
Hope that explains things a little more clearly.

Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found

RoboticBuddy said:
Whenever I try use any command on fastboot, i get this message
Code:
(bootloader) slot-count : not found
(bootloader) slot-suffixes : not found
(bootloader) slot-suffixes : not found
Click to expand...
Click to collapse
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.

echo92 said:
I think those messages are normal, as the Moto Z Play doesn't appear to have the A/B partition system found on the Pixel. Thus, those messages are more informational as there's no separate slot to flash to.
Click to expand...
Click to collapse
Now I'm getting that I cannot write to /data.

echo92 said:
As I understand it, the hardbrick comes not when you downgrade, but when you use OTA updates to upgrade your device.
[snip]
Hope that explains things a little more clearly.
Click to expand...
Click to collapse
Your explanation adds up missing bits and makes everything much more clear to me. Thank you very much!

im not much of a programmer or anything but I can tell you this. my MZP was down for a month due to this. I was on 7.0 custom rom I think either on the april or January patch, wanted the ota for 7.1, sooooooo I figured I would just downgrade to 6 and accept the ota....... Well that was not wise. If I recall upgrading changed the bootloader which is not able to be downgraded so there was a mismatch and the phone could not boot itself to anything. I would advise double and triple checking the threads. before you hard brick. Luckily for that particular problem there is now a method to recover it. just wanted to give you as much info as possible

Zixione said:
Please explain a little bit more how is it possible. As far as I understand it should be as following
When I get phone from store it will look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
When I get OTA update it will look something like:
Code:
F1: STOCK FIRMWARE V.1
O2: OTA UPDATE V.2
F1O2F1O2O2O2O2F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1O2O2O2O2F1F1O2O2O2O2F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Then I downgrade via fastboot and it should look like:
Code:
F1: STOCK FIRMWARE V.1
F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1F1
┗━━━ BOOT ━━━┛┗━━━━ RECOVERY ━━━━┛┗━━━━━━━━━━━ SYSTEM ━━━━━━━━━━━┛
Why hardbrick?
Click to expand...
Click to collapse
Where did you get these hex values so I can check my own?

These values are just part of schematic illustration (as a version numbers are) and doesn't meant to have any meaningful sense.

Need help with Error 7 in twrp,no install possible

Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.

Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse

messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.

Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.

Then you didn't flash it but just boot it

Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.

tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!

How to relock and restore original fw?

Hello everyone. I tried relock the bootloader, but when the process finished it gave me the error "The system has been destroyed". I unlocked it again and retried the procedure with the same result. Do you have any idea what's the problem? Thank you.

I am quite surprised that it allowed you to unlock it again.
Anyway, are you sure that you have 100% stock ROM? Including, but not limited to system, boot and recovery partitions?

_mysiak_ said:
I am quite surprised that it allowed you to unlock it again.
Anyway, are you sure that you have 100% stock ROM? Including, but not limited to system, boot and recovery partitions?
Click to expand...
Click to collapse
I flashed the original fastboot rom. I try first whit the command 'flash all" successfully. Then i try "flash all and lock" and compare error message. Fortunately in the fastboot mode i unlock again. Sorry for bad english.

xire68 said:
I flashed the original fastboot rom. I try first whit the command 'flash all" successfully. Then i try "flash all and lock" and compare error message. Fortunately in the fastboot mode i unlock again. Sorry for bad english.
Click to expand...
Click to collapse
After flashing, can you start the phone? Does it boot completely to the welcome screen?

_mysiak_ said:
After flashing, can you start the phone? Does it boot completely to the welcome screen?
Click to expand...
Click to collapse
When I "flash all" start normally.
When I "flash all and lock" bootloop

Did you have a custom ROM installed before? If so, which one?

_mysiak_ said:
Did you have a custom ROM installed before? If so, which one?
Click to expand...
Click to collapse
Yes, xiaomi.eu, Arrows, lineage OS and dotOS, evidently one of these ROM has corrupted the system files. With other models I have never had similar problems (redmi note 7, note 8t etc ...)

xire68 said:
Yes, xiaomi.eu, Arrows, lineage OS and dotOS, evidently one of these ROM has corrupted the system files. With other models I have never had similar problems (redmi note 7, note 8t etc ...)
Click to expand...
Click to collapse
The only thing which comes to my mind is that there might be some partition which has been modified by custom ROM, but did not get reflashed with stock image. You will probably need to check installation script of all ROMs which you tried to check which partitions are overwritten and compare it with stock ROM flashing script.

_mysiak_ said:
The only thing which comes to my mind is that there might be some partition which has been modified by custom ROM, but did not get reflashed with stock image. You will probably need to check installation script of all ROMs which you tried to check which partitions are overwritten and compare it with stock ROM flashing script.
Click to expand...
Click to collapse
Ok thanks for support.

Xiaomi Provides Flashable ROMs of MIUI Updates for all its Devices
Step 1: Download MIUI Fastboot ROM for your Device.
Step 2: Extract the ROM package on your Computer.
Step 3: Boot your device into Fastboot Mode.
Step 4: Launch Mi Flash Tool on the Computer.
Step 5: Install Xiaomi USB Drivers (if Required)

xire68 said:
When I "flash all" start normally.
When I "flash all and lock" bootloop
Click to expand...
Click to collapse
xire68 said:
When I "flash all" start normally.
When I "flash all and lock" bootloop
Click to expand...
Click to collapse
here is a guide

Mi flash let's you lock the bootloader again

No
Mi Flash
1.clean all - flash_all.bat
2.save user data - flash_all_except_storage.bat
3.clean all and lock - flash_all_lock.bat
Install number 2
MiFlash2020-3-14-0

Thanks, but all the proposed solutions, I have already tried them without success.

I wonder if anyone else successfully re-locked bootloader... I hope that someone will give their experience!

It's definitely dead. QDLoader 9008.

xire68 said:
It's definitely dead. QDLoader 9008.
Click to expand...
Click to collapse
Are you saying you broke the mobile?
F

EDL methode install rom

jinx11 said:
EDL methode install rom
Click to expand...
Click to collapse
Yes, but I need an autorired account for this...

Not
download program QPST_2.7.496.zip
download prog_emmc_firehose_Sdm660_ddr.mbn
download phone fastboot rom
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
QPST Tool v2.7.480 - QPST Tool
Download the official QPST Tool v2.7.480 which allows you to flash the stock firmware on your Qualcomm Smartphone and Tablets.
qpsttool.com
illustration video QPST is on youtube