Related
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.
I am having major issues with GFIL working. My bootloader showed locked, though I know it was unlocked. Now it is grey out and says it is unlocked, it there a way to get that back to showing locked so I can manually unlock it again.
I am thinking that is the only reason QFIL is not working
Thank you:good:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
KouaV1 said:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
Click to expand...
Click to collapse
It is unlocked, but greyed out. QFIL won't work so no way to get into fastboot, to lock and unlock. So I am pretty well SOL.. QFIL won't bring up the option to get into Partiton Manager.
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
KouaV1 said:
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
Click to expand...
Click to collapse
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Droidman61 said:
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Click to expand...
Click to collapse
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
KouaV1 said:
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
Click to expand...
Click to collapse
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Droidman61 said:
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Click to expand...
Click to collapse
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
KouaV1 said:
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
Click to expand...
Click to collapse
Wow thank you for the info, sadly I have Sprint and there is NO kdz for this. to lock and re-lock. I think I am screwed.
Thank you.:good:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
KouaV1 said:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
Click to expand...
Click to collapse
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Droidman61 said:
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
awesome good for you
I was trying to get lineage and made a lot of mistakes... Now i dont have download mode, my phone is bootlooping on the LG V40 logo screen... Please help me out!!
Do you know if you are able to get into 9008 mode? If you are able to, it might be possible to save your phone still.
Having the same issue
I have the same issue, and yes I can ONLY get into it and nothing else...
I'm no longer with AT&T and wanted to use my V405 with T-Mobile, I know now that I can't but, I still wanted to have it unlocked to cross upgrade to the unlocked 405QA version, any assistance will be greatly appreciated.
If it is still bootloader unlocked and still has fastboot then you can still save it by using adb to boot into twrp. You don't need to wipe laf partition/download mode because you can always access fastboot either way so its pointless to nuke it.
Crossflashing will not make it unlocked for carrier use. You have to carrier unlock it before crossflashing. Just go out and buy an phone unlocked for the us market or the V405QA7 model.
I'm having also same problem AT&T coming from cross flashed pie
I need help!!!!
My phone is bricked flashing Lineage 17.1 and series of lots of mistakes...
erased laf_a laf_b till i got to unable to fastboot flash anything and it will return CANT FLASH IN UNLOCK STATE...
Tried to relock bootloader if it will solved the issue only worsen things...
Now,
no download mode no fastboot and connecting charger doesn't charge phone the security warning pops up and when i try to use vol+ and usb to pc combination, i get to the security warning page and ALL SLOT ARE UNBOOTABLE error...
Pc doesnt recognise phone it only reboots to same security warning screen
Any help please?
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
Factory reset holding VOL- POWER BUTTON, releasing POWER BUTTON when screen on and still keeping VOL- pressed and pressing POWER BUTTON again doesn't change anything.
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom.
The thing about getting into qfil is that you can do it from **any** screen (well, maybe not with the device off, never tried that scenario). The difference doing it in other screens than a booted device is you won't get any 'count down' screen, you'll just have to wait the 5 seconds and when screen changes spam the vol up.
good luck
AsItLies said:
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom.
The thing about getting into qfil is that you can do it from **any** screen (well, maybe not with the device off, never tried that scenario). The difference doing it in other screens than a booted device is you won't get any 'count down' screen, you'll just have to wait the 5 seconds and when screen changes spam the vol up.
good luck
Click to expand...
Click to collapse
Luckily I was able to get to edl mode even when phone turned off
Turn off your phone and boot into edl mode (when phone is off connect usb or leave usb connected and immediately hold vol down and power buttons and keep rapidly pressing the vol up)
---------- Post added at 06:58 PM ---------- Previous post was at 06:42 PM ----------
AsItLies said:
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom
Click to expand...
Click to collapse
the original abl (a and b) and original laf (a and b)?
That is where the problem is now!!! :crying:
Instructions GUIDE by Xsavi never adviced to save the original abl and laf_a laf_b
Coming from Cross flashed US Unlocked 20e stock pie to Lineage 17.1(not latest)
Please how do I solve this???
yemkoid said:
Luckily I was able to get to edl mode even when phone turned off
Turn off your phone and boot into edl mode (when phone is off connect usb or leave usb connected and immediately hold vol down and power buttons and keep rapidly pressing the vol up)
---------- Post added at 06:58 PM ---------- Previous post was at 06:42 PM ----------
the original abl (a and b) and original laf (a and b)?
That is where the problem is now!!! :crying:
Instructions GUIDE by Xsavi never adviced to save the original abl and laf_a laf_b
Coming from Cross flashed US Unlocked 20e stock pie to Lineage 17.1(not latest)
Please how do I solve this???
Click to expand...
Click to collapse
Try these, they should work.
AsItLies said:
Try these, they should work.
Click to expand...
Click to collapse
LIKE A CHARM! :good::good::good::good:
Many Thanks
abl and laf flashed appropriately to each slot and i now have download mode
Flashed stock pie 20e and starting over again
thanks , work
AsItLies said:
Try these, they should work.
Click to expand...
Click to collapse
Can you help me to get the abl and laf_a laf_b for v409N android Q?
My V409N also stuck in fastboot after i flash a wrong oreo image to abl_a.
Thanks!!!
hkguy80 said:
Can you help me to get the abl and laf_a laf_b for v409N android Q?
My V409N also stuck in fastboot after i flash a wrong oreo image to abl_a.
Thanks!!!
Click to expand...
Click to collapse
is it 30d? 30e? 30f? I don't think they are interchangeable....
AsItLies said:
is it 30d? 30e? 30f? I don't think they are interchangeable....
Click to expand...
Click to collapse
Is there anyway to figure out which version it is in the EDL?
EDL is the only thing i can enter now.
Can I flash the rom via EDL directly?
hkguy80 said:
Is there anyway to figure out which version it is in the EDL?
EDL is the only thing i can enter now.
Can I flash the rom via EDL directly?
Click to expand...
Click to collapse
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
AsItLies said:
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
Click to expand...
Click to collapse
I didn't flashed any KDZ as the the seller flashed it already.
Since I only flashed the ABL_A, Can I save the ABL_B from the phone and comparing it with your files to guess which ABL_A should be used?
hkguy80 said:
I didn't flashed any KDZ as the the seller flashed it already.
Since I only flashed the ABL_A, Can I save the ABL_B from the phone and comparing it with your files to guess which ABL_A should be used?
Click to expand...
Click to collapse
they are all the same size, don't think that will tell you anything.
Here's what to do, use edl to save the 'b' versions (hopefully you didn't overwrite those also). Then take them and flash them to 'a'. Then write down what your version is when it boots
AsItLies said:
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
Click to expand...
Click to collapse
I just found that I may click "Read Data" during EDL before i flash the ABL_A. and i found this file ReadData_ufs_Lun4_0xdd06_Len256_DT_25_04_2021_19_07_11. Should I flashed it to ABL_A again and try to boot it again?
hkguy80 said:
I just found that I may click "read partition" before i flash the ABL_A. and i found this file ReadData_ufs_Lun4_0xdd06_Len256_DT_25_04_2021_19_07_11. Should I flashed it to ABL_A again and try to boot it again?
Click to expand...
Click to collapse
you obviously haven't used qfil at all. Yes, what u want to do is 'read partition' after selecting abl_b. Then, as you know, the file is a bizarre name found in the folder / port that qfil is using.
That file will match the output name given when it reads the data. All you need to is rename the file to (whichever partition you backed up) like abl_b.img
Then select that abl_a partition and use the manager to 'load' an image to that partition, select the one u just saved.
Keep in mind, I have no idea which one of your slots is active. In the examples above, it's assuming your 'a' slot is the active slot. If it's not! then reverse a and b examples above.
So, in worst case scenario, I'd suggest you save off both your abl_a and abl_b, and rename the results to something like abl_a_current, and abl_b_current, that way if copying one to the other doesn't make it boot, redo it but copy the opposite ones back. (because you're not on the slot you think it is.)
make sense?
AsItLies said:
you obviously haven't used qfil at all. Yes, what u want to do is 'read partition' after selecting abl_b. Then, as you know, the file is a bizarre name found in the folder / port that qfil is using.
That file will match the output name given when it reads the data. All you need to is rename the file to (whichever partition you backed up) like abl_b.img
Then select that abl_a partition and use the manager to 'load' an image to that partition, select the one u just saved.
Keep in mind, I have no idea which one of your slots is active. In the examples above, it's assuming your 'a' slot is the active slot. If it's not! then reverse a and b examples above.
So, in worst case scenario, I'd suggest you save off both your abl_a and abl_b, and rename the results to something like abl_a_current, and abl_b_current, that way if copying one to the other doesn't make it boot, redo it but copy the opposite ones back. (because you're not on the slot you think it is.)
make sense?
Click to expand...
Click to collapse
Yes..Italso help me to understand more about the qfil.
Thanks a lot for your help..
I just figured out that I actually backed up the original abl_a before i flashed the v35eng.img. After i restore the original abl_a to abl_a, my phone finally resume normal.
Can you also suggest a proper way to restore fastboot on my phone? because I want to disable the vbmeta and replace the open_kr with open_us.
hkguy80 said:
Yes..Italso help me to understand more about the qfil.
Thanks a lot for your help..
I just figured out that I actually backed up the original abl_a before i flashed the v35eng.img. After i restore the original abl_a to abl_a, my phone finally resume normal.
Can you also suggest a proper way to restore fastboot on my phone? because I want to disable the vbmeta and replace the open_kr with open_us.
Click to expand...
Click to collapse
good. Yes the best way, especially with korean rom, is to flash the v35 eng abl to your not active slot, which I think in your case is 'b', so abl_b.
the key to that working is you need to have twrp installed, so you can use it to set 'b' partition as active, then select 'reboot bootloader' and it will boot to fastboot. You can then use fastboot and follow the info in this vbmeta link. Read the directions.
the other option (if u don't have twrp yet), would be to flash v35 eng to a, boot to fastboot, do the vbmeta stuff, then use fastboot to flash the original abl_a back, so it will boot.
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.
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse
mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.