Question Unbricking Motorola G40 through EDL - Moto G40 / G60

After a decade,5 phones and countless roms later I finally bricked an android. I relocked bootloader after flashing custom rom without proprt thinking and now phone is stuck on fastboot but will not let me flash anything.
If i try to boot it shows "no os found" error. Fastboot shows "flashing_locked" and i can't unlock it again as it won't boot into OS.
I managed to get into edl mode and QFIL tool is recognizing the device and is reading the imei,partitions. So I think with proper firehose file and elf firmware It is possible to bring back the phone to life.
i want to know if it is possible to port stock rom(xml) to QFIL compatible(elf) file? there are already manuals on creating raw and patch files. So what would it take?

Hi vamsi,
I am also in same problem. I have moto g40 and in the same situation no os found" error. Fastboot shows "flashing_locked". Not able to flash anything.
Can you please guide me how to get into edl mode.I tried below command/sites and none of them worked :-
fastboot oem blackflash - Got error "command restricted"
And tried everything mention in this site https://www.ytechb.com/how-to-boot-into-edl-mode-android/#:~:text=1 Download Fastboot EDL zip file and extract,This will boot the phone into EDL Mode. Nothing worked

vamsi53 said:
Contact
Click to expand...
Click to collapse
Sure i will check with him.
Thanks

Sonu19kr said:
Sure i will check with him.
Thanks
Click to expand...
Click to collapse
I Am Facing Th Same Problem And I am Already Scammed In The Telegram Groups Please Can You Help Me And Can You Tell How To Get Into EDL MODES In Motorola G40 Fusion
vamsi53 said:
After a decade,5 phones and countless roms later I finally bricked an android. I relocked bootloader after flashing custom rom without proprt thinking and now phone is stuck on fastboot but will not let me flash anything.
If i try to boot it shows "no os found" error. Fastboot shows "flashing_locked" and i can't unlock it again as it won't boot into OS.
I managed to get into edl mode and QFIL tool is recognizing the device and is reading the imei,partitions. So I think with proper firehose file and elf firmware It is possible to bring back the phone to life.
i want to know if it is possible to port stock rom(xml) to QFIL compatible(elf) file? there are already manuals on creating raw and patch files. So what would it take?
Click to expand...
Click to collapse
Can You Please Help How To Get Into EDL MODES

Related

EDL mode through fastboot

Guys look what i found
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Happy flashing
daca0 said:
Guys look what i found
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Happy flashing
Click to expand...
Click to collapse
are you tried this method before? the thread for Kenzo
It could work with devices with unlocked bootloader but in this case we couldn´t need it; devices with unlocked bootloader can be flashed using MiFlash Tool/fastboot and eventually TWRP.
It doesn´t work in devices with locked bootloader.
Technically script sends device to EDL but like the bootloader it´s locked it refuses to boot in EDL mode and restarts in the system finally.
SubwayChamp said:
It could work with devices with unlocked bootloader but in this case we couldn´t need it; devices with unlocked bootloader can be flashed using MiFlash Tool/fastboot and eventually TWRP.
It doesn´t work in devices with locked bootloader.
Technically script sends device to EDL but like the bootloader it´s locked it refuses to boot in EDL mode and restarts in the system finally.
Click to expand...
Click to collapse
is it true EDL flashing more 'clean' than fasboot flashing method?
EriecTan said:
is it true EDL flashing more 'clean' than fasboot flashing method?
Click to expand...
Click to collapse
Sorry, What do you mean?
If you ask if through EDL it's a cleanest method, no, there's no difference with fastboot method that you can use using MiFlash Tool or using fastboot commands to flash partitions
SubwayChamp said:
Sorry, What do you mean?
If you ask if through EDL it's a cleanest method, no, there's no difference with fastboot method that you can use using MiFlash Tool or using fastboot commands to flash partitions
Click to expand...
Click to collapse
thanks mate for the answer!
Do not worked
Hi.
This treatment does not work for redmi note 6 pro.
In my opinion Google should make EDL mandatory on any and every phone. If I remember correctly EDL makes Snapdragon phones unbrickable. Though Xiaomi has been locking it off and using proprietory code to put authorization locks on it.
I'm guessing because it's a major vulnerability (on Kenzo, I think EDL meant you could throw any file at the phone) but the easy fix there is simply enforcing a hardcoded checksum for any incoming recovery file.
But really Google needs to make sure phones can be easily recovered by consumers from even the dodgiest bootloader flashes, botched flash memory situations, modem edits, mismatched firmware somehow flashing to the wrong phone and whatever other ways a phone can be messed up.

[G8s] is unlock for other variants possible?

Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
corpsegrinder62 said:
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
Click to expand...
Click to collapse
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
antintin said:
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
Click to expand...
Click to collapse
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
corpsegrinder62 said:
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
antintin said:
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
Click to expand...
Click to collapse
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
corpsegrinder62 said:
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
Click to expand...
Click to collapse
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
antintin said:
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
Click to expand...
Click to collapse
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
corpsegrinder62 said:
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
Click to expand...
Click to collapse
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
antintin said:
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
Click to expand...
Click to collapse
Thats great! When you say flash though. You mean dd flash with terminal with su to flash boot_b using said root access right? Then using fastboot to switch to boot_b and use that to unlock, correct?
But no abl yet for G8s as far as im aware, so i take it we need to wait on firehose for it or would cross flashing abl from another device work? Also android 10 update is around the corner, im still on pie 10i for now.
Thanks alot for your patience to help

Question Bootloop to fastboot logo and back in lock state

Hi everybody,
yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot..
(before this I flashed twrp and the arrowOS recovery and images a few time trying, without succes, to install this rom)
Last thing I did was flash via the mi-flash tool and did't see the "clean and lock" selection so it's also in lock state again.
I cant get adb to find the phone although the mi-flashtool is finding it.
anyone any tips?
I tried the vol up power trick, but this didn't help, keeps loading into fastboot
Did Mi Flash give an error message after trying to flash?
dreamytom said:
Did Mi Flash give an error message after trying to flash?
Click to expand...
Click to collapse
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled
Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.
dreamytom said:
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled
Click to expand...
Click to collapse
this doesn't seem to be an option. there is a checkbox with "erase all" but all are already unchecked
dezborders said:
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.
Click to expand...
Click to collapse
This is what I feared already..
Kaayman said:
This is what I feared already..
Click to expand...
Click to collapse
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!
If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.
mar.ur said:
If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.
Click to expand...
Click to collapse
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly
Rstment ^m^ said:
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly
Click to expand...
Click to collapse
thanks everyone for all the replies!
tried unlocking it via the mi unlock tool (latest) but it says (in chinese) its locked by nr 123***456 by searching the phone - can't unlock
edit:
google lens translates:
X The phone has been locked by the account number 661****647 by searching the phone, Can't unlock
but it's not the nr. of my account..
dezborders said:
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!
Click to expand...
Click to collapse
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?
dreamytom said:
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?
Click to expand...
Click to collapse
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I also tried to simulate a local OTA by copying update.zip to internal storage using ADB push command and booting into recovery mode to flash ... But it doesn't work for me
dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting
I think a warranty repair claim is your best bet ... I have never read anywhere that unlocking bootloader invalidates Xiaomi warranty (Unlike Samsung and so many other brands!)
If warranty repair is re refused try a few independent repair shops
Last resort is get the back cover off the phone and short out the EDL pins
Good luck!
Let us know if you manage to get your phone booting up again
See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
[Solved] Stuck in fastboot with locked bootloader
HI there! After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it...
forum.xda-developers.com
Kaayman said:
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting
Click to expand...
Click to collapse
I once hardbricked (complete blackscreen, not even Fastboot reachable) a Poco F3.
I requested a replacement from Amazon and that worked.
I said a software update bricked it.
Of course having to do that is really bad, but I was scared of opening the back.
dezborders said:
See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
Bootloop to fastboot logo and back in lock state
Hi everybody, yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot.. (before this I flashed twrp and...
forum.xda-developers.com
Click to expand...
Click to collapse
You pasted the current thread, do you have the link to the thread you meant?
Kaayman said:
You pasted the current thread, do you have the link to the thread you meant?
Click to expand...
Click to collapse

Question another 11t boot error

hi guys.
im from Austria and have a Xiaomi 11t.
yesterday i tryed to update my phone ota and now the problem is that i can't boot it anymore.
to bad that i have locked bootloader and snapdragon ;(
i tried with almost every tool i have found for xiaomi to open bootloader to flash the rom or recover it.
also fastboot dont let me flash rom cause of locked bootloader.
fastboot is working and sometimes i got recovery option working.
does anybody has another option to try?
thx for help
mozzi75 said:
hi guys.
im from Austria and have a Xiaomi 11t.
yesterday i tryed to update my phone ota and now the problem is that i can't boot it anymore.
to bad that i have locked bootloader and snapdragon ;(
i tried with almost every tool i have found for xiaomi to open bootloader to flash the rom or recover it.
also fastboot dont let me flash rom cause of locked bootloader.
fastboot is working and sometimes i got recovery option working.
does anybody has another option to try?
thx for help
Click to expand...
Click to collapse
You can try this tool.
https://xiaomitools.com/sp-flash-tool-en/
There are also other tools, do a search on XDA and Google.
thx. i tried it, but the problem is that i could not get into edl. the com port is showing up for 1 sec and then it reboots and get into fastboot.
sp tool doesnt accept the scatter file from my rom.
is it possible to flash twrp with locked bootloader and restore it?
or is the only way to get a remote support?
thx
mozzi75 said:
thx. i tried it, but the problem is that i could not get into edl. the com port is showing up for 1 sec and then it reboots and get into fastboot.
sp tool doesnt accept the scatter file from my rom.
is it possible to flash twrp with locked bootloader and restore it?
or is the only way to get a remote support?
thx
Click to expand...
Click to collapse
It is not obvious for recent devices if the soc is not supported.
EDL mode is only for Qualcomm devices.
A few links that might be helpful:
EDIT:
Sorry but this does not apply to your device.
https://qpsttool.com/qpst-tool-v2-7-496
https://qfiltool.com/qfil-tool-v2-0-3-5
https://forum.xda-developers.com/t/stuck-in-bootloop-xiaomi-11t.4546381/
https://forum.xda-developers.com/t/bootloop-not-letting-me-access-fastboot.4520745/
See also https://www.xiaomitool.com/V2/ choose my device is bricked
thx,
so i've tried the tools.
i get into preloader state but wihout serial port so mtk stucks. Maybe its windows 11?
i also tried the xiaomi tool v2 but its horrible, cause our phone is not in recovery list (i wrote the developer to import it)
also in sp flash tool i don't get the button to bypass security
If still under warranty, send it.

Question Brick relock bootloader

Let's see if someone can help me, I locked the bootloader again after putting the last stock rom of my moto g10 and it does not start. I only have access to fastboot with flash locked. i can't unlock it again or flash stock rom. with lmsa it gives me an error and stops at 26%. I have tried to flash the blankflash but it does not take the qualcomm drivers but the android device. I don't know what to do to revive it.
sorry for my bad english, google translate
I managed to put it in edl mode and flash a blankflash, but I get the same result bootloader locked. I can't flash anything or unlock the bootloader, it's definitely dead. It only remains to find a motherboard to replace it...
Ok, what I have is to find a compatible blankflash and stock firmware so that it will let me flash stock rom. someone could help me? I have already tried 3 different ones with no result.
whit themagictoolinstaller.exe i managed to change the flashinglocked mode to oemlocked. After this with rescue & smart assistant I was able to flash his stock rom. Solved

Categories

Resources