Database Develop

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

How do I restore a Fullbackup?

Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.

romanrsr said:
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
Click to expand...
Click to collapse
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers

AsItLies said:
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
Click to expand...
Click to collapse
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!

romanrsr said:
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
Click to expand...
Click to collapse
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers

AsItLies said:
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
Click to expand...
Click to collapse
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.

romanrsr said:
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
Click to expand...
Click to collapse
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck

AsItLies said:
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
Click to expand...
Click to collapse
You were correct! I Press the volume down + power keys, and then pressing the up key several times the QFIL detected it again. I have already flashed your backup and boot OK.
Now I have the following problem, when I insert another SIM it does not appear to enter the unlock code, but I get the error "This phone is permanently locked and can not be unlocked", did you have any experience with this?
It occurred to me to try to update it to the latest version via FOTA and LG Software, but it tells me that the latest version is already installed. Can you think of something? Thanks!

Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers

AsItLies said:
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
Click to expand...
Click to collapse
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?

romanrsr said:
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
Click to expand...
Click to collapse
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.

AsItLies said:
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
Click to expand...
Click to collapse
Check this:
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz

romanrsr said:
Check this:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Use this xml. I created it to flash Q all at once, there aren't 0-6 luns, as the names are unique and not needed.
But just as a warning, it should work, I've used it, but it's only been tested on my device, which was originally at&t. And, I'd point out, doing this isn't going to unlock the sim.
cheers

Bricked after attempting to unlock bootloader. What now?

I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?

protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.

AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.

protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.

AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.

protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.

Bricked LG V40 LM-V409N

I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.

Maple06 said:
I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.
Click to expand...
Click to collapse
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.

AsItLies said:
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.
Click to expand...
Click to collapse
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.

Maple06 said:
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.
Click to expand...
Click to collapse
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers

AsItLies said:
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers
Click to expand...
Click to collapse
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.

Maple06 said:
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.
Click to expand...
Click to collapse
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.

AsItLies said:
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.
Click to expand...
Click to collapse
I just reflashed all of them and enter the download mode and it works! Now I can access LGUP and when I try to start flashing my .kdz file it failed but I'm now trying redownloading the .kdz file with KDZ downloader. Just in case that .kdz really need a special download. I'll update when my .kdz is finished downloaded and if the flash is successful or not. In the meantime, do you have any sources for the LG V40 LM-V409N .kdz file version? It'll be very useful in case this file failed.
Thank you very much

Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do.
Edit: Apparently, my phone still got the issue that it restarts randomly. I have no idea how to fix it now since the issue still persists after several different phone stock ROM.
Many thanks.

Maple06 said:
Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do,
Many thanks.
Click to expand...
Click to collapse
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.

after unbrick how to get IMEI? I have no backup. using V409N korean model.

AsItLies said:
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.
Click to expand...
Click to collapse
Thank you for your answer. It would've been working now if I didn't get unlucky on the device. You're really helpful to help from my hard-bricked phone into firmware booted.
Again, thank you very much

irfan64672 said:
after unbrick how to get IMEI? I have no backup. using V409N korean model.
Click to expand...
Click to collapse
If you unbricked your device with the stock firmware, just go to telephone and call *#06# and you got your imei. Best to backup your firmware with QFIL.

Question IDK Redmi 10S

Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.

Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?

Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it

gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working

tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS

Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?

gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.

What do you mean it doesn't work?
Can't enter into fastboot mode?

gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".

Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode

gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text

I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.

gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH

Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss

Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D

I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one

Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money

Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/

tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...

gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today