Related
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.
p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?
VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.
Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.
Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me
Hello,
I was having no IMEI found issues with my cc9 pro (note 10) and probably broke something in my EFS/modem partition as now when i flashed back to stock via fastboot its telling me my NV data is corrupted. Looking for any help regarding this, aswell as any files that i could use (a QCN for when i get back into the system, EFS backup/modem files) I have access to fastboot and that's pretty much it. The phone gets to the MIUI logo sometimes butthen goes back to the basic recovery.
Defineltd said:
Hello,
I was having no IMEI found issues with my cc9 pro (note 10) and probably broke something in my EFS/modem partition as now when i flashed back to stock via fastboot its telling me my NV data is corrupted. Looking for any help regarding this, aswell as any files that i could use (a QCN for when i get back into the system, EFS backup/modem files) I have access to fastboot and that's pretty much it. The phone gets to the MIUI logo sometimes butthen goes back to the basic recovery.
Click to expand...
Click to collapse
you need flash in TEST Point mode to get back imei an nvdata
Could you explain a little bit more on how to do that?
Lussardi said:
you need flash in TEST Point mode to get back imei an nvdata
Click to expand...
Click to collapse
Could you explain a little bit more on how to do that?
Defineltd said:
Could you explain a little bit more on how to do that?
Click to expand...
Click to collapse
first at all, you need open phone (remove back cover) and make testpoint you got a Qualcomm Loader 8008 mode, before that get latest firmware to your device and and use Miflashpro and flash whole flash in qualcomm mode, no fails at all! whith this you get working device
this is latest firmware Global rom
https://bigota.d.miui.com/V12.0.3.0.QFDMIXM/tucana_global_images_V12.0.3.0.QFDMIXM_20201026.0000.00_10.0_global_8f1fa67095.tgz
this is pinout to go in qualcomm mode 8008
Lussardi said:
first at all, you need open phone (remove back cover) and make testpoint you got a Qualcomm Loader 8008 mode, before that get latest firmware to your device and and use Miflashpro and flash whole flash in qualcomm mode, no fails at all! whith this you get working device
this is latest firmware Global rom
https://bigota.d.miui.com/V12.0.3.0.QFDMIXM/tucana_global_images_V12.0.3.0.QFDMIXM_20201026.0000.00_10.0_global_8f1fa67095.tgz
this is pinout to go in qualcomm mode 8008
Click to expand...
Click to collapse
So what do i do? touch the pins? or remove them? or?
So ive managed to get it into EDL mode using : "fastboot oem edl?"
ON device manager says port9008 like it should, but when flashing i got error : edl authentication, you are not authorized to download
Defineltd said:
So ive managed to get it into EDL mode using : "fastboot oem edl?"
ON device manager says port9008 like it should, but when flashing i got error : edl authentication, you are not authorized to download
Click to expand...
Click to collapse
when ask for edl auth use your mi account, remember phone its blocked by your account, if fail you need a UMT box to flash, try again
Hi guys,
so after I got my xiaomi with a global ROM and wanted to update and that is when I accidentally relocked the bootloader. The version of ROM was invalid apparently and wouldn't let me boot and now I'm stuck in fastboot mode.
My problem is as follows:
-can't enter recovery, stuck at fastboot no matter how many times I try and reboot
-adb not working since I didn't enable it
-bootloader locked (miflash says so and it can't unlock it since I didn't check 'oem unlock enable' and I cannot boot ROM so I can't enable it)
-fastboot flashing says 'not allowed in lock state'
-edl mode not available
I've seen tutorials where people opened their phones to force the phone into edl mode via the testing points but is that the only way`?
Any suggestions on how I could unbrick it?
Much appreciated
yes, it is the only way.
koniv90 said:
Hi guys,
Any suggestions on how I could unbrick it?
Much appreciated
Click to expand...
Click to collapse
you can use this tool to flash the phone on fastboot mode
Xiaomi King Tool - Home.
xiaomikingtool.com
its cost you only 5 credit
Can you flash files by fastboot? if so, flash the global rom images one by one, then reboot
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
I need help please my phone redmi k50 gaming is no recovery and . bootloader is locked
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
This what I'm facing
Dims_Camper said:
yes, it is the only way.
Click to expand...
Click to collapse
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
kskksks said:
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
Click to expand...
Click to collapse
Nope, only very old devices.
NOSS8 said:
Nope, only very old devices.
Click to expand...
Click to collapse
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
kskksks said:
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
Click to expand...
Click to collapse
Have you tried to flash stock rom?
I mean, if you have Chinese rom before, just flash with latest Chinese rom.
Ghanaba said:
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
Click to expand...
Click to collapse
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
jholfran3 said:
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
Click to expand...
Click to collapse
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
flashing is possible with modified firehose programmer (no auth factory loader) or with authorized xiaomi account. both solutions are paid service and cannot advertised here.
please -as always- read the thread you posted in. I can see useful information shared already. wait for other replies.
letsgofly said:
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
Click to expand...
Click to collapse
Hi, try to flash the .img files from the fastboot stock rom whit cdm in fastboot, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
example:
fastboot flash boot boot.img
fastboot flash cust cust.img
etc.
jholfran3 said:
Hi, try to flash the .img files from the fastboot stock rom, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
Click to expand...
Click to collapse
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
NOSS8 said:
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
Click to expand...
Click to collapse
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
jholfran3 said:
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
Click to expand...
Click to collapse
To install a recovery, the bootloader must be unlocked.
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
hasan lakha said:
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
Click to expand...
Click to collapse
India, Europe, Global?
hasan lakha said:
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
Click to expand...
Click to collapse
My honest suggestions : Stay away from OOS12 ( even base ). Besides, if u want to boot into EDL, just force power off the device totally. Then press and hold both Vol +- and plug the device into the computer with MSM stared, ur device will be in EDL ( ofc, u will have to install all necessary drivers beforehand )