Mi A3 hard bricked - Xiaomi Mi A3 Questions & Answers

My Mi A3 was hard bricked and unbricked it using Mi flash tool , again after a few months in got bricked , I unbricked it again but this time I guess I somehow locked the bootloader , Now my device is bricked again , it's not responding not even charging , I set it in edl mode and tried to flash rom using mi flash tool , but this time the mi flash tool is showing me error "write time out , device may be disconnected"

Have you googled the error message "write time out , device may be disconnected"? There are a few suggestions.

bjlabuk said:
Have you googled the error message "write time out , device may be disconnected"? There are a few suggestions.
Click to expand...
Click to collapse
Yes mate , i tried everything searching on Google , can you please help me mate

I haven't experienced your problem. Could the message relate to the EDL connection? I found this link https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
So (i) when you used Mi Flash Tool did you use 'clean all' or 'clean all and lock'? - that might explain the locked bootloader. (ii) Did you check in Device Manager as per the link I have given? (iii) have you tried the patched firehose file method, as per https://www.droidwin.com/unbrick-mi-a3-fastboot-commands/ ?
Can't suggest anything else other than a repair shop where someone with more experience might be able to sort it.

bjlabuk said:
I haven't experienced your problem. Could the message relate to the EDL connection? I found this link https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
So (i) when you used Mi Flash Tool did you use 'clean all' or 'clean all and lock'? - that might explain the locked bootloader. (ii) Did you check in Device Manager as per the link I have given? (iii) have you tried the patched firehose file method, as per https://www.droidwin.com/unbrick-mi-a3-fastboot-commands/ ?
Can't suggest anything else other than a repair shop where someone with more experience might be able to sort it.
Click to expand...
Click to collapse
Thanks mate for your assistance , i guess last time i flash the device i mistakenly use " clean all and lock"
The device is in edl mode as the port is recognised in the device manager and yes i tried the patched firehose , got the same error "write time out may be device was disconnected"

Okay, how about trying to get out of EDL mode? https://www.droidwin.com/how-to-exit-edl-mode-in-android/ Can you do that?
If you can get out of EDL mode then try flashing the STOCK ROM using the platform-tools, not Mi Flash Tool! https://www.thecustomdroid.com/xiao...2a11363abaea7ed177f9037d4693fae#comment-33230
You will get the latest fastboot images here https://xiaomifirmwareupdater.com/miui/laurel/

bjlabuk said:
Okay, how about trying to get out of EDL mode? https://www.droidwin.com/how-to-exit-edl-mode-in-android/ Can you do that?
If you can get out of EDL mode then try flashing the STOCK ROM using the platform-tools, not Mi Flash Tool! https://www.thecustomdroid.com/xiao...2a11363abaea7ed177f9037d4693fae#comment-33230
You will get the latest fastboot images here https://xiaomifirmwareupdater.com/miui/laurel/
Click to expand...
Click to collapse
My Device is hardbrick so I guess doing it using platform tools won't work

Pyro556 said:
My Device is hardbrick so I guess doing it using platform tools won't work
Click to expand...
Click to collapse
Okay, if it is stuck in EDL mode the only think I can think of is to try using QFIL but you will need to search for the stock firmware for your device in 'Flat Build format' - see attached link and instructions https://www.droidwin.com/unbrick-xiaomi-fix-device-stuck-in-edl-mode-via-qfil-tool/
I have successfully unbricked a Wileyfox Swift 2 recently using the QFIL method.

I did try the qflash , it shows
download fail firehose fail fhloader fail process fail

Are you using QFIL from within QPST? https://forum.hovatek.com/thread-30141.html
Also download the Engineering ROM from here. It has the firehose file. https://mifirm.net/downloadfile/66

You're leaving it in edl too long. Hold down the power button for a full 30 seconds. Seriously, count. Now, hold vol up and down for the same. Attach the cable. Release volume buttons. Now, you are freshly in edl. It should work. If you go QFIL, you will need to do this in between each patch.

Check out this link on Sahara: https://www.droidwin.com/fix-sahara-fail-qsaharaserver-fail-process-fail-error-qfil-tool/

Also, you mind posting your patched programmer file? Been having trouble with that.

Eliliyah said:
Also, you mind posting your patched programmer file? Been having trouble with that.
Click to expand...
Click to collapse
Who are you asking? Not sure which file you are referring to?

bjlabuk said:
Are you using QFIL from within QPST? https://forum.hovatek.com/thread-30141.html
Also download the Engineering ROM from here. It has the firehose file. https://mifirm.net/downloadfile/66
Click to expand...
Click to collapse
i will try using this rom let's see

Related

how I unbrick my pocoF1

it is unlocked with twrp recevory and I flashed the new stabil rom miui_POCOF1Global_V10.1.3.0.PEJMIFI_f05771189d_9.0 zip,via twrp ,before flash new rom It has miui_POCOF1Global_V10.0.6.0.OEJMIFH_c5f0857b02_8.1 rom,twrp and root (magisk), afterthat it is bootlooping ,power off and bricked.no recovery mode,no fastboot mode ,only edl mode working.
I have tried the unbrick it with edl mode(no problem on edl mode win 10 64 bit Pc ).I have used Miflash exe, xiaomi miflash exe,Qualcomm_Flash_Image_Loader,AFTool,Miflash,bla bla what ever I know . I had changed cable,changed usb port,changed programs , no result.
need more idea,please
hope that somebody could you give a some solution
Sent from my [device_name] using XDA-Developers Legacy app
ayhanaykut said:
it is unlocked with twrp recevory and I flashed the new stabil rom miui_POCOF1Global_V10.1.3.0.PEJMIFI_f05771189d_9.0 zip,via twrp ,before flash new rom It has miui_POCOF1Global_V10.0.6.0.OEJMIFH_c5f0857b02_8.1 rom,twrp and root (magisk), afterthat it is bootlooping ,power off and bricked.no recovery mode,no fastboot mode ,only edl mode working.
I have tried the unbrick it with edl mode(no problem on edl mode win 10 64 bit Pc ).I have used Miflash exe, xiaomi miflash exe,Qualcomm_Flash_Image_Loader,AFTool,Miflash,bla bla what ever I know . I had changed cable,changed usb port,changed programs , no result.
need more idea,please
Click to expand...
Click to collapse
Yo any change yet?
RangerSpartan said:
Yo any change yet?
Click to expand...
Click to collapse
yes,found authorized user to flash rom via edl. paid 35$, no problem
I'm facing the same Issue. However, my phone got bricked during an update. Bootloader is locked. Can anyone help. Phone still bricked.
ThunderEmperor said:
I'm facing the same Issue. However, my phone got bricked during an update. Bootloader is locked. Can anyone help. Phone still bricked.
Click to expand...
Click to collapse
Use mi flash tool and flash the phone
rizwm14 said:
Use mi flash tool and flash the phone
Click to expand...
Click to collapse
In brick phone you can't go to fastboot mode
SamyakJ said:
In brick phone you can't go to fastboot mode
Click to expand...
Click to collapse
Is it hard bricked ?
rizwm14 said:
Is it hard bricked ?
Click to expand...
Click to collapse
I don't know because it's not my device
SamyakJ said:
I don't know because it's not my device
Click to expand...
Click to collapse
It's not hardbricked. I'm able to go into Fastboot, but when i try using the Mi tool to Flash it, i get am error message that, " Cannot Flash when Device is locked"
ThunderEmperor said:
It's not hardbricked. I'm able to go into Fastboot, but when i try using the Mi tool to Flash it, i get am error message that, " Cannot Flash when Device is locked"
Click to expand...
Click to collapse
Your device is hard bricked, you cannot access EDL when bootloader is locked. You have to bring your device via nearest Xiaomi service center. I think you will pay for a fee.
---------- Post added at 02:03 AM ---------- Previous post was at 01:26 AM ----------
I made a thread on how unbrick by installing flash stable rom via fastboot (EDL Mode)
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152

Redmi note 4 - brick, no fastboot, no twrp, only red led

Hi everyone,
I have Xiaomi Redmi Note 4, and when I using him, hes gone. Nothing work, no fastboot, no twrp, only Red led when i charge battery.
And i want to flash miui global in MiFlash and... I have error PING TARGET VIA FIREHOSE.
Guys please help me, I tried in 6 miui globals, china, any MiFlash version(Beta,2014,2015,2016) and dont work
Have a nice day.
P.S I have Qualcomm HS-USB QDLoader 9008 (COM3)
Try to flash in edl mode... For this you have an authorized mi account
I got same issue some time before just remove the battery connector after that connect the phone with pc (WITHOUT BATTERY CONNECT) flash again using miflash tool
ismail.ahmed84 said:
I got same issue some time before just remove the battery connector after that connect the phone with pc (WITHOUT BATTERY CONNECT) flash again using miflash tool
Click to expand...
Click to collapse
I tried IT and dont work
anil5462 said:
Try to flash in edl mode... For this you have an authorized mi account
Click to expand...
Click to collapse
I flashed on edl and dont work
i experienced same issue before and nobody in XDA cant fix this (or wont bother to reply,, idk)
try test point method. if it doesn't work, i'm afraid that you have broken hardware. you have to replace it
anil5462 said:
Try to flash in edl mode... For this you have an authorized mi account
Click to expand...
Click to collapse
rs168 said:
i experienced same issue before and nobody in XDA cant fix this (or wont bother to reply,, idk)
try test point method. if it doesn't work, i'm afraid that you have broken hardware. you have to replace it
Click to expand...
Click to collapse
I tried testpoint and always have error writing on Device in miflash
Snajper322 said:
I tried testpoint and always have error writing on Device in miflash
Click to expand...
Click to collapse
okay .. too bad you should replace your device, or you can find a good mechanic to replace some broken parts. it usually works
did you drop it?
or it happened during installing rom or something?
How does it happened please tell us.
Charge it overnight
Hold the power button 20-30 seconds the next day
Boot the device in fast boot mode by holding volume down+power button. Then go to MiFlash and flash fastboot redmi note 4 rom in edl mode(Unlock bootloader by running the last script file and then proceed to do the following steps). Download stock fastboot rom for redmi note 4 from official mi website(Note: The stock fastboot rom is different from stock recovery rom). While flashing the rom, below you have the option to choose three modes, click clean all and lock. Flash this rom and you're device will be working in no time. Make sure your device has adequate battery

Help needed, stuck at Fastboot Mode

Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.

Mi A3 stuck with EDL mode when flashing the Pixel experience

i try to flash pixel experience, the developer guide to flash firmware+vender zip after flashing the ROM zip, as per the guide I flash the ROM ZIP and firmware zip, after flashing the firmware, mobile rebooted and nothing to show in display. so i try to force boot in to recovery. the screen nothing to show. so i try to boot on fastboot. still nothing to show in mobile screen even the fastboot logo. i connect my mobile to computer, and i noticed the HS-USB QDLoader 9008 driver was installed. so guess it was in EDL mode, then try to flash the stock ROM using MI flash tool And get the error " cannot receive hello pocket." "object reference not set to an instance of an object " so i try to flash using QFIL , still not get any improvement, so kindly guide any possible to unbrick my phone.
Hey there I'm kinda having the same problem, any progress on your end ? I waited a few days for the battery to die and then connected to MiFlash but it keeps asking for an EDL authorized account, which is apparently a rarity. Exploring other options such as bypassing EDL authorization, long shot but what could be worse eh ...
freeze1994 said:
Exploring other options such as bypassing EDL authorization, long shot but what could be worse eh ...
Click to expand...
Click to collapse
Could you solve the problem? I have the same problem. Did you find information or a method to bypass EDL authentication?
Anandkrish40 said:
i try to flash pixel experience, the developer guide to flash firmware+vender zip after flashing the ROM zip, as per the guide I flash the ROM ZIP and firmware zip, after flashing the firmware, mobile rebooted and nothing to show in display. so i try to force boot in to recovery. the screen nothing to show. so i try to boot on fastboot. still nothing to show in mobile screen even the fastboot logo. i connect my mobile to computer, and i noticed the HS-USB QDLoader 9008 driver was installed. so guess it was in EDL mode, then try to flash the stock ROM using MI flash tool And get the error " cannot receive hello pocket." "object reference not set to an instance of an object " so i try to flash using QFIL , still not get any improvement, so kindly guide any possible to unbrick my phone.
Click to expand...
Click to collapse
got any solution? same thing happened to me too, help please
help I have the same error, any solution?
Syden! said:
help I have the same error, any solution?
Click to expand...
Click to collapse
What version of mi flash are you using? If it is the one from 2017 then it will not work as it isn't compatible with EDL.
Update miflash to latest or at least 2018 version to use EDL mode

Question Hard Brick Oxygen OS 12

Hello everyone, I have problems after updating Oxygen OS 12, my system stopped starting, more precisely, a cyclic reboot
There were attempts to enter the bootlocker but it does not start
And the Brom mode through mtkclient gives an error - hardshake failed
What other ways are there to restore the device to me very urgently
Sorry for the wrong translation, I used google translate
Have you tried Volume Down + Power button for fastbootd? I suggest you keep trying to connect with mtkclient, check the drivers or as a last resort try to use the bootable livedvd provided on the mtkclient github page.
Coconut_cube said:
Have you tried Volume Down + Power button for fastbootd? I suggest you keep trying to connect with mtkclient, check the drivers or as a last resort try to use the bootable livedvd provided on the mtkclient github page.
Click to expand...
Click to collapse
Tried it doesn't work the same gave out hardshake failed in liunx livedvd
SashaPalamaryuk said:
Tried it doesn't work the same gave out hardshake failed in liunx livedvd
Click to expand...
Click to collapse
Chances are high that your device is truly hardbricked. BROM mode was disabled with the OOS12 preloader and fastboot doesn't work. Did you update through stock recovery with locked bootloader or did you do it differently?
You can try asking in the official TG group @OnePlusNord2GlobalOfficial. Maybe somebody will have an answer.
Coconut_cube said:
Chances are high that your device is truly hardbricked. BROM mode was disabled with the OOS12 preloader and fastboot doesn't work. Did you update through stock recovery with locked bootloader or did you do it differently?
You can try asking in the official TG group @OnePlusNord2GlobalOfficial. Maybe somebody will have an answer.un
Click to expand...
Click to collapse
unlocked bootloader via TWRP
SashaPalamaryuk said:
unlocked bootloader via TWRP
Click to expand...
Click to collapse
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Coconut_cube said:
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Click to expand...
Click to collapse
Maybe somehow through a test point
SashaPalamaryuk said:
Maybe somehow through a test point
Click to expand...
Click to collapse
Unfortunately not, the button combination has the same effect as test point (I discussed it with a dev in another thread). The only way to get BROM mode now is to short the CLK pin on the UFS flash chip (whose location is currently unknown) to ground but that requires expertise otherwise further damage can be done.
I'm on OOS 12 and I can use mtkclient in Brom mode no issues.
It's annoying to use on Windows but on Linux there's no need for specific drivers. On Arch specifically and have to sudo to use it but hey whatever.
That said and I'm sorry if that's gonna sound condescending but have you tried different cables and ports on your computer . It could be just that
SP Flash Tool
Coconut_cube said:
Unfortunately, updating through TWRP is known to brick this phone. Your preloader (which is responsible for booting into BROM mode) got corrupted. I've heard that some people have had success with SP Flash Tool instead but use it at your own risk. Servicing the phone would be your best option if possible.
Click to expand...
Click to collapse
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Coconut_cube said:
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Click to expand...
Click to collapse
wait for next update!
Donaldmagee said:
wait for next update!
Click to expand...
Click to collapse
What?
Try using SP Flash Tool after you disable auth with that application. If it doesn't work, CM2 MT2 is the only other tool I've heard which people have had success with by enabling the Force BROM option.
File available for dead repair with imei+baseband remind me on monday
Mr Hassan said:
File available for dead repair with imei+baseband remind me on monday
Click to expand...
Click to collapse
i need that file my nord 2 imei null and fingerprint not work please reply
Coconut_cube said:
You need to bypass DA authentication with mtk-bypass. It can be found on GitHub. You also need to download the payload exploits collection provided there and extract it into the mtk-bypass folder. Then run mtk-bypass, connect USB to phone while holding button combination and run SP Flash Tool when done. This is a more detailed video, see if it works for you.
Click to expand...
Click to collapse
Where to download SP Flash Tool?
Thank you!
roldev said:
Where to download SP Flash Tool?
Thank you!
Click to expand...
Click to collapse
you can get it from here

Categories

Resources