After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
simonastani said:
After playing with some custom ROM, my device is stuck in EDL mode. i.e Stuck in primary bootloader. I cannot get to the secondary bootloader. either, recovery mode or fast boot mode.
Solution and issues faced.
Solution 1: Flash original Rom via Mi flash tool.
Issues: Xiaomi restricts the user to flash room when the device is in EDL mode. After some research found only authenticate accounts can install ROM in EDL mode via the mi flash tool. It will ask for EDL authentication. that I don't have access to.
I think the only solution is to somehow reverse back to fast boot or recovery mode and install back the rom.
Has anybody faced such issue and know the solution.
Click to expand...
Click to collapse
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
SubwayChamp said:
Your device can't be stuck in EDL mode timeless, to get it out of there, you just have to disconnect it from the PC and press the three buttons at the same time for about 10 seconds.
A different thing is that your device can't enter to fastboot nor recovery. Firstly get it out from EDL mode and see which modes are available after that.
Click to expand...
Click to collapse
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
simonastani said:
My secondary bootloader files are corrupted and can't get to it. Have only access to EDL mode. Can't get back to fast boot or recovery mode. The only option found is to somehow install flashable firmware via QFIL and get back to the secondary bootloader to access the flash tool of vendor-specific devices.
Click to expand...
Click to collapse
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
SubwayChamp said:
Well, to be clear and not put effort where no results have to be expected; there’s no a secondary bootloader, this device have a fastboot mode (accessed usually pressing PWR + volume down buttons), a recovery mode (usually accessed pressing PWR + volume up), an EDL mode (usually accessed on an unlocked device pressing the two volume buttons at same time while connecting to PC or through test point method), and additionally a user space friendly fastbootd mode that only can be accessed using either ADB or fastboot command, also can be accessed through some custom recoveries in the PWR menu.
If you are totally sure you tried all the combination keys indicated WHILE your device is off, then you have to move it to the next:
- Search for a patched Firehose file either for your specific device or from a device with the same motherboard that can work too onto your device, this is to bypass the Mi account authorization or to work in qfil.
- Search for an engineer firmware for your device, if something exists have to bypass the Mi Flash tool restriction.
Click to expand...
Click to collapse
My device is poco x3 pro. unable to find the patched firehose file..
simonastani said:
My device is poco x3 pro. unable to find the patched firehose file..
Click to expand...
Click to collapse
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
SubwayChamp said:
Man, you are not reading well, it's not so simple like that, I can't give you the exact solution in your hands but I giving you the direction that you have to take in order to find some solution and avoid taking it to a service center, not all countries have one at hand like mine.
- Search for a programmer firehose similar to your device if the exact for your model doesn't exist.
- Search for a programmer firehose for sm7150, it's the same as yours. Take a look here https://www.droidwin.com/patched-firehose-file/
- Search for an engineering/combination ROM for your device (it must be specific for your device, not for a similar one), this is one example https://testedrombd.com/poco-x3-pro-eng-fix-firmware/ some engineering ROM have the ability to bypass restrictions, not always, but it is worth to give it a try.
- And the last resort, exploiting/modifying/editing firehose vulnerabilities, read this https://github.com/bkerler/edl
Click to expand...
Click to collapse
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
simonastani said:
Yeah. Its not simple. Prior to giving link ,I have tried those methods. Thanks for the information
From my findings.
1. Patch programmer firehose file for sm7150 not found anywhere. Tried using different patch firehose file of other compatible devices that uses 860 chipset. Unsuccessful result.
2. Tried Engineering ROM of Vayu. Unable to bypass restrictions. It ask for edl authentication same as of vendor specific rom. I think the reason is xiaomi restrict user to flash room via edl mode. Still searching some way to bypass authentication.
3. Last resort. modifying firehose and hex files. Need a lot of research.
Didn't find any solution for poco x3 pro specific devices in community.
Can We install 860 chipset flashable frimware of oneplus via QFIL . Need to tried that one. Is it possible.?
Click to expand...
Click to collapse
QFIL is slightly outdated, so it needs a special programmer, even I don't know if it can work for new UFSs (or a limited range of them) it used to work for devices with eMMCs.
Xiaomi restricts users to flash in EDL mode using Mi Flash tool (the restriction can't apply beyond this tool).
A firmware from other device definitely will brick it.
Research if the PX3P has a counterpart device, I mean Xiaomi released every year a certain model for Global and the same model (with other name) as it happened i.e. with the Mi A3 and the MiCC9 and other models though, in this case it could be possible that the programmer file for this model could work for you.
Also, I saw on the OnePlus thread a tool capable to flash through EDL, maybe replacing the files it could work, I didn't try it yet.
E eu fui passar a .eu via Fastboot no meu e tava demorando dms... fui e fechai o CMD, e matei meu celular
Related
This is for realme xt, but I believe that it is similar to a lot other devices based on qualcomm MSM chipsets.
In my specific case, I have a brand new realme xt phone with a locked bootloader (default from factory). I've upgraded it to latest stock realme Adnroid 10 from realme only to notice that the official unlock tool didn't work anymore. So I've tried to downgrade it from Android 10 to Android 9 stock ROM. It seemed to go ok, but it failed. Now system, recovery and fastboot are unaccessible. When turned on, it only stays at the logo screen.
So, after searching a lot, I've found out that there is a hidden EDL (Emergency Download Mode) from Qualcomm that it is used in situations like this. I've found the stock firmware (official ROMs in a .ofp file format). Since I can't reach recovery or fastboot mode, EDL seems to be the only option.
Again I've serched a lot, including what people would use for other phones, but I can't get any of those EDL tools to work: sometimes either you must have some secret credentials or the software have viruses (and I don't know if it still requires credentials). Other options require the firmware in other file formats: XML, MTN, etc, which I haven't figured out how to extract or acquire. Finally, there are many texts that says that QFIL, etc tools can't be used for realme xt, because they wouldn't be able to write the filesystems.
In my region there is no realme service center, so that's not an option. I've bought the phone from a registered importer, which is also clueless. The phone has all the invoices and related paperwork correct.
So, in a nutshell:
1) The phone is softbricked (hopefully), but requires EDL mode to be recovered. Sending it to a service center is not possible (because of import/export procedures);
2) Where can I find a tool to enable me to revive it to stock ROM (I already have ofp and ozip files)?
3) How can I acquire the required credentials (if necessary) for it to work?
4) Failing 2 and 3, does anybody know of someone who can provide remote services to fix it? (I'm thinking of setting up my computer and someone remotely using their credentials and procedures)
Thank you all in advance for any help. This would be my mother's Christmas gift, It is very expensive for us and right now it is only a very expensive paper weight.
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar
Well you're in luck as it is just a .bat file program simple notepad++ will do.
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD
that sucks... could try reseating the screen's ribbon cable :-/
can anybody share the full update rom about android 11?
top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page
Edit: I am keeping the information below intact, just incase someone goes through the same issues that I had gone through.
My recommendation is follow through with Johnny886 video on his installation guide and just skip any steps that aren't applicable to your set up. I recommend using his 0-update_image_edl.bat and not using Qfil or xiaomi. His video ends up showing most of the steps required to accomplish the repair, with exception of showing the phone and when you have to bring your phone into bootloader mode and what not.
I can personally attest to the fact this does bring a hard bricked phone from the grave. When I mean hard bricked, I mean black screen and in edl mode (shows up as a usb devices or port on your PC).
I am not a regular on these forums so I probably won't be here for long. I'll help if I see your posts, if I can help.
//////////////////////////////////////////////////////
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
EDIT, Fix found:
So I found out what was wrong. It shows "program speaks firehose protocol while your target is speaking sahara" because I was using the ddr.elf file.
If you pay attention to it, which I didn't at first, it says this:
"
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13: prog_firehose_lite.elf)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target"
I found out you are suppose to use the prog_firehose_lite.elf file (or whatever file it say is the device programmer first).
When using the QFIL program, I was using the prog_firehose_ddr.elf and this caused the error to appear.
I will post an image showing how it is suppose to look like when configured correctly.
NOTE: (I ended up bricking my phone to the point of not having an accessible bootloader/recovery when ONLY using raw program 0 and patch 0 files). This made it so you can only turn on the phone using the - volume and power button and it gets stuck on the "republic of gamers" splash screen. I have a solution for that issue further down in the thread.
Trash.umu said:
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
Click to expand...
Click to collapse
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
JazonX said:
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
Click to expand...
Click to collapse
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
You need to install the correct Qualcomm driver, and then your folder cannot have spaces or some unsupported characters.
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
johnny886 said:
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Click to expand...
Click to collapse
So my phone attempted to install the firmware but now it does not have a bootloader, it does not connect to the PC and it can only get up to the point of showing the republic of gamers logo and letters.
I am guessing the only way forward is opening this thing up or buying a new phone. Unless you have a way out of this?
1. It is no able to go into edl via computer through adb.
2. It does not appear on device manager nor disk management.
3. It does not have a recovery option appearing and pressing +volume and power button does nothing.
4. You can only press the - volume and power button, the regular power button does nothing and when using the - volume button and power button, it just gets stuck on the republic of gamers screen.
5. It does not go into edl mode when connected to either the bottom or the side port on the phone.
6. It does not connect to the computer even if you delete the device, the drivers, reinstall the drivers and device. reset the computer and device and all forms of these things in different orders.
If the only way forward is possibly removing the battery and maybe shorting two pins together, do you have an idea which pins these are?
EDIT, Fix found:
So I found out that if you connect the ROG 5s phones side port to the computer while it is frozen in the republic of gamers logo for about 20 minutes, it resets and the android recovery screen pops up with only the options of "try again" and "factory data reset" and appears as an asus I005D in universal serial bus devices on my device manager. Now that I have it connected to the PC, I have a way forward.
It appears as in recovery mode in adb. you can not do anything other than enter "adb devices" and "adb reboot edl"
forcing the phone into edl using the adb cmd of "adb reboot edl" makes the device appear as a port device. This will allow me to reinstall the firmware again using the QFIL program.
I seem to keep falling through the same loop of errors. I wonder if there is a firmware error somewhere or if my phone is somehow rejecting the firmware.
I will update if I get anywhere.
NOTE:
If for some reason you can not get your phone to turn on or it turns off as you press the recovery option.
You need to connect the usb port to provide power via the bottom port and NOT the side port.
I am not sure why it is required, maybe the bottom port energizes more things than the side port does and it causes this fault. If you have both ports connected, it disconnects the bottom port and automatically uses the side port.
Trash.umu said:
我似乎不断陷入同样的错误循环。我想知道某个地方是否存在固件错误，或者我的手机是否以某种方式拒绝了固件。
如果我到达任何地方，我会更新。
Click to expand...
Click to collapse
There is no error in the firmware, and it is only released after it has been tested and there is no problem.
johnny886 said:
There is no error in the firmware, and it is only released after it has been tested and there is no problem.
Click to expand...
Click to collapse
I'll attempt to figure out why my phone isn't working properly. It may take awhile. Maybe it has to do with multiple attempts of installing the same firmware, or it could be that some of my phones components are already dying and it is just a coincidence.
NOTE: My phone kept failing to properly download johnny886 firmware because my phone (in particular) kept requiring me to switch between the side and bottom ports to keep my phone alive. I am unsure why I this was the case but I was able to finally install the firmware on my phone and my phone is now up and running properly.
I have to give thanks to johnny886 for his files, his video and his efforts. If not for him, my phone would still be a brick.
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.
Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan
Hi, I accidentally bricked my phone flashing the wrong image.
Now i can't turn off the phone, cant access to recovery or fastboot. (device doesn't respond when i click any button).
'Poco' logo is in loop. Anyone knows a way to install a ROM? Any way to access fastboot in this situation?
Try pressing the buttons for a long time. It resulted for me to get to recovery mode, but no to download mode. Sometimes it works.
I bought a poco x4 gt like that too, hoping to get it fixed, I believe the way to get it is via EDL mode and miFlas, but for now miflash still doesn't recognize the image of the poco x4 gt. I hope that in some future update I will recognize it.
i have same problem
Same problem here
did anyone was able to find a fix? or at least locate the test points for EDL?
mtk devices use a different way to access edl mode. in my case I access the edl mode, the computer recognizes it, the software recognizes it, but when running it says that SPflash still does not work with the scartter version of the rom that I downloaded
how did you manage to boot into edl mode? i tried several hw key combinations but it gives me "preloader handshake failed" or several BROM error.
i think my scatterfile seems ok. its just the brom/edl connection.
when you turn it on with the volume button less pressed and it connects quickly to the pc install the MTK driver and then run the python where it will read the brom
Mine already fixed
butaw1 said:
Mine already fixed
Click to expand...
Click to collapse
what did you do?
if any one want to fix his poco x4 gt bootloop only. can't reach fastboot or recovery. at first you need auth to bypass dim 8100 security. i found a person on github name Rafon he fixed my phone and it's working perfectly right now. his username on telegram is @Rafon24
same issue
the only way of fixing is through an authorized xiaomi account sadly
i however found a way to turn it off when nothing works:
press all 3 buttons (volume up, down and power for like 20 seconds)
and then it will turn off