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
Related
hi guys..
is there any chance to repair MT6795 device..? after wrong flashing only vibrating and not power on normally..
t-mobile_mda said:
hi guys..
is there any chance to repair MT6795 device..? after wrong flashing only vibrating and not power on normally..
Click to expand...
Click to collapse
Old thread but I hope this will help someone else in the future. When you format all + download with SP Flash Tool, it wipes every partition including pg1fs and pg2fs. Without these partitions HTC phones will not be able to boot. You can easily fix this by flashing these partitions after modifying the scatter file to download: true and file name: pg1fs.img and pg2fs.img for pg1fs and pg2fs partitions. You can get the partitions from another one m9+ or if you had backed them up with SP Flash Tool readback.
To flash with SP Flash Tool in this situation you have to press and hold both volume buttons and power button while connecting phone to PC until when flashing begins
Gibz97 said:
Old thread but I hope this will help someone else in the future. When you format all + download with SP Flash Tool, it wipes every partition including pg1fs and pg2fs. Without these partitions HTC phones will not be able to boot. You can easily fix this by flashing these partitions after modifying the scatter file to download: true and file name: pg1fs.img and pg2fs.img for pg1fs and pg2fs partitions. You can get the partitions from another one m9+ or if you had backed them up with SP Flash Tool readback.
To flash with SP Flash Tool in this situation you have to press and hold both volume buttons and power button while connecting phone to PC until when flashing begins
Click to expand...
Click to collapse
can you tell me how to do that ??
Nilmotoo said:
can you tell me how to do that ??
Click to expand...
Click to collapse
What happened to your phone?
Gibz97 said:
What happened to your phone?
Click to expand...
Click to collapse
It was installing update and after finished it didn't boot up again keeps vibrating every minute and nothing on screen whatever I do it doesn't responde and when I connect to pc it recognize as Mediatek preloader .then I tried to flash it with sp flashtool but keeps geting error 2004
Nilmotoo said:
It was installing update and after finished it didn't boot up again keeps vibrating every minute and nothing on screen whatever I do it doesn't responde and when I connect to pc it recognize as Mediatek preloader .then I tried to flash it with sp flashtool but keeps geting error 2004
Click to expand...
Click to collapse
Was the phone s-off?
I have been speaking with @t-mobile_mda, the OP for this thread and what I have discovered is that for the m9 plus and maybe other HTC devices with the mt6795 SoC, SP Flash Tool will only be able to flash them is they are s-off.
For your case, have you found the correct files with the scatter file? Can I see the snapshot for the files?
Gibz97 said:
Was the phone s-off?
I have been speaking with @t-mobile_mda, the OP for this thread and what I have discovered is that for the m9 plus and maybe other HTC devices with the mt6795 SoC, SP Flash Tool will only be able to flash them is they are s-off.
For your case, have you found the correct files with the scatter file? Can I see the snapshot for the files?
Click to expand...
Click to collapse
My phone was s-on so you nean my phone is dead
Nilmotoo said:
My phone was s-on so you nean my phone is dead
Click to expand...
Click to collapse
It could be.
Just to confirm, how were you updating the phone?
Was it an OTA or an RUU? Was the flashing process successful?
If it was successful then it's highly likely a hardware issue.
Have you tried holding volume up when connecting phone to PC to flash?
That error 2004 means the phone's security is restricting SP Flash Tool from flashing it, pressing button combinations might trigger the security off
Gibz97 said:
It could be.
Just to confirm, how were you updating the phone?
Was it an OTA or an RUU? Was the flashing process successful?
If it was successful then it's highly likely a hardware issue.
Have you tried holding volume up when connecting phone to PC to flash?
That error 2004 means the phone's security is restricting SP Flash Tool from flashing it, pressing button combinations might trigger the security off
Click to expand...
Click to collapse
It was OTA and yes it finished flashing and what combination should I try? I tried the volume up while connecting but the same error
Nilmotoo said:
It was OTA and yes it finished flashing and what combination should I try? I tried the volume up while connecting but the same error
Click to expand...
Click to collapse
This a pic of my bootloader before the phone's death
Nilmotoo said:
This a pic of my bootloader before the phone's death
Click to expand...
Click to collapse
The link to the photo does not work.
Try holding all buttons together or volume down as in different combinations
Gibz97 said:
The link to the photo does not work.
Try holding all buttons together or volume down as in different combinations
Click to expand...
Click to collapse
Tried everything seems like the phone is dead anyway thanks alot for helping
Nilmotoo said:
Tried everything seems like the phone is dead anyway thanks alot for helping
Click to expand...
Click to collapse
Hi Gibz97, do you have any idea how to flash the phone using rx,tx or something like that , i've searching and there is videos about flashing mtk devices using the main board but when I opened the device I didn't see any kolo or colo or gnd so if you have any idea about that I can try it
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80120c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
raptorddd said:
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Edit: nvm I read what nuke download mode is (when no recovery and can't boot). I will try it now and see if it helps...
brickedvice said:
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Click to expand...
Click to collapse
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
raptorddd said:
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
Click to expand...
Click to collapse
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
brickedvice said:
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
Click to expand...
Click to collapse
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
raptorddd said:
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
Click to expand...
Click to collapse
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
brickedvice said:
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
raptorddd said:
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
Click to expand...
Click to collapse
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
brickedvice said:
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
Click to expand...
Click to collapse
i do not know either.. shortening the mother board is to enter download mode..
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
This thread here : http://forum.xda-developers.com/showthread.php?t=2449670 might help you installing twrp via adb
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.
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
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
TweakybirdsTheWord said:
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
Click to expand...
Click to collapse
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Nilesh112 said:
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Click to expand...
Click to collapse
Although the process that you've described will work to reflash the phone from being hardwrecked it's not going to be possible unless you get a two-factor authentication code directly from the OnePlus servers and that's only possible if you have the proper credentials so good luck with that. Now if you want a third party service that can unbrick it for you I can recommend somebody but other than that you're pretty much screwed when it comes to a OnePlus phone these days...
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
TweakybirdsTheWord said:
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
Click to expand...
Click to collapse
I believe tthey're exclusive to the chipset or motherboard that's in the phone.. because some phones can use the same firehose but have nothing other than the chipset/board being the same.. or i couild be wrong on that? Definitely might wannna google that before taking that as a concrete.
Well that's good news so far if it's true
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Except I can't access fastboot. All I have is EDL.
dmtec said:
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Click to expand...
Click to collapse
Except I can't access fastboot. All I have is EDL.
Good luck because all msm tools now require a 2FA to initiate data restore.. I've used the guy who helped create rom2box for 20 bucks.. I can vouche for his validity and success rate and usually responds within 20 minutes or so..
Here's his telegram contact info
Great news. I've figured out that firehose loaders are NOT specific to tool or firmware that they're packaged with BUT they are processor specific if I'm not mistaken.
TweakybirdsTheWord said:
Except I can't access fastboot. All I have is EDL.
Click to expand...
Click to collapse
You can use rom2box to reflash from EDL.
dmtec said:
You can use rom2box to reflash from EDL.
Click to expand...
Click to collapse
which version