Database Users

Mi A1 Hard brick

Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.

Does it enter fastboot mode? Turn it on holding volume down+power.

whoadood said:
Does it enter fastboot mode? Turn it on holding volume down+power.
Click to expand...
Click to collapse
No, it doesn't even turn on

R4aPt0rX said:
No, it doesn't even turn on
Click to expand...
Click to collapse
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.

whoadood said:
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.
Click to expand...
Click to collapse
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)

R4aPt0rX said:
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)
Click to expand...
Click to collapse
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.

whoadood said:
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.
Click to expand...
Click to collapse
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:

R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
Did you fix the restarting issue?

R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
WiFi not working means you have a wrong kernel. Flash a full system image again

Edwin Hamal said:
Did you fix the restarting issue?
Click to expand...
Click to collapse
Not yet, I am still trying to
tinyXperia said:
WiFi not working means you have a wrong kernel. Flash a full system image again
Click to expand...
Click to collapse
Which image do you recommed me to use, and which tool do you recommed me to use?

R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.

Edwin Hamal said:
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.
Click to expand...
Click to collapse
OMG it worked!! Thank you man!! I really appreciate all the help!

R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Any full image (1GB size) should work. Use mi flash tool to flash it

Hey guys,
I'm having the same problem. My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:

earthscaper said:
My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74978236&postcount=310
https://forum.xda-developers.com/mi-a1/help/mi-a1-stuck-edl-9008-flash-t3724567/

R4aPt0rX said:
Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.
Click to expand...
Click to collapse
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..

my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader

Try persist from other builds.
leo_hacker82 said:
my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader
Click to expand...
Click to collapse
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.

Edwin Hamal said:
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.
Click to expand...
Click to collapse
phone failed i try many persist.img i got latest and old firmwares and when i flash it fails...isnt allowed to download

leo_hacker82 said:
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..
Click to expand...
Click to collapse
Lo cargue con MiFlash con la opción de limpiar y bloquear.
I flashed it with MiFlash with the Clean and lock option active.

MI A1 Bricked HARD!!!-AlekDev

Hi Guys my MI A1 was bricked i just use the test point to fix and my pc recognized as Qualcomm 9008 so flashed latest 8.0 everything worked but wifi and bt was broken so i decided again to put in EDL and flash it with same firmware after that MI flash shows success but device doesn't turn it jsut keep blinking led and goes to EDL everytime i connect to PC...tried with Nougat and Oreo firmwares same...i checked logs and saysthat device is successfully flashed and rebooted...but nothing just black screen and blinking led..Can anyone Help me?I can't send to Service because i will need to wait 1 month also i opened the back cover so i lost the warranty.....:crying::crying:

Hi,
did you try to flash with qfil or only mi flash ?
I'm not sure but may you ask Cosmic Dan he was planing to do an unbrick guide and he mentioned files which you can use with qfil to unbrick your device. I don't know how far he is with it.
But if you did manage to unbrick so far and only BT and WiFi is your issue aren't there several fix guides for the persist partition ?
For my personal experience after I had to unbrick my old n6p I had the same issue after flashing. Phone stays black and led just blinking. Try to long pressing power, or other button combinations while plugg and unplugging USB to pc and I mean really long pressing the buttons. It sounds a bit weired but my n6p came back and booted as usual.
I'm sry, but I can't tell you the right combination because I tried so much that time, because it was my only phone.
Good luck !

Bro if You Have A Backup Of Your phone Then flash It.
Sent from my [device_name] using XDA-Developers Legacy app

Qfil doesn't work because we have A/B Partition Layout....i have backup of my partitions that's not issue....

How much battery had you left at flashing ? May its just drained and not able to boot. Sometimes it's the stupid and simple things. If you have partition backups you should be able to fix your WiFi and BT.

coremania said:
How much battery had you left at flashing ? May its just drained and not able to boot. Sometimes it's the stupid and simple things. If you have partition backups you should be able to fix your WiFi and BT.
Click to expand...
Click to collapse
70%

Alek Dev said:
Hi Guys i ws experimenting something with my device so i bricked fully i just use the test point to fix and my pc recognized as Qualcomm 9008 so flashed latest 8.0 everything worked but wifi and bt was broken so i decided again to put in EDL and flash it with same firmware after that MI flash shows success but device doesn't turn it jsut keep blinking led and goes to EDL everytime i connect to PC...tried with Nougat and Oreo firmwares same...i checked logs and saysthat device is successfully flashed and rebooted...but nothing just black screen and blinking led..Can anyone Help me?I can't send to Service because i will need to wait 1 month also i opened the back cover so i lost the warranty.....:crying::crying:
Click to expand...
Click to collapse
You can get it back. You have lost the Wifi and Bluetooth (Mac Address files). You can boot your phone if it is in edl mode. Just press the Power Button for more than 30-40 seconds. Your phone will boot. If possible, try to stick the back cover and show it to service center. They will change your phone's motherboard! They don't know about edl and everything! They only change internal parts! :good:

birarvindersingh said:
You can get it back. You have lost the Wifi and Bluetooth (Mac Address files). You can boot your phone if it is in edl mode. Just press the Power Button for more than 30-40 seconds. Your phone will boot. If possible, try to stick the back cover and show it to service center. They will change your phone's motherboard! They don't know about edl and everything! They only change internal parts! :good:
Click to expand...
Click to collapse
Yes Go service centre When Your phone in warrenty.
Sent from my [device_name] using XDA-Developers Legacy app

Try updating your drivers. Happened to me once, MiFlash didn't detect it, but driver MANUAL update helped.

If u r using Mac Then Try in windows with Fastboot Rom.

Phone sent to Service Center....hopefully they will repair with my warranty,So No releases/No Builds around 1 month

After lot of waiting (FROM 23 MAY) this is what i got from my service center
" AFTER SERVICE REVIEWS AND SOFTWARE INSTALATION DEVICE REMAINS WITH A LOADING / DAMAGED MEMORY CHIP"
"The phone is stuck in EDL Mode due to improper use and serious damage from all sides. The same after a service overview and software installation could not be turned on or raised (shows no signs). The service order states that if you want to service, you will be offered an offer to change the motherboard. Greeting"
After that they tell me this"
"Otherwise, changing the motherboard with a working hand would be around 182 USD. Greeting"
i don't have that money it's too much expensive for me so i'm without any phone....

Alek Dev said:
Qfil doesn't work because we have A/B Partition Layout....i have backup of my partitions that's not issue....
Click to expand...
Click to collapse
I restored my Mi A1 at least 3 times with QFIL, not a problem.

meltbanana said:
I restored my Mi A1 at least 3 times with QFIL, not a problem.
Click to expand...
Click to collapse
What version of QFIL? What OS did you have? what firmware did you use? or you have made backup with qfil then restore it? if you have that will be good to send me at least i can try it ....i ussually get this error dmssfail with QFIL.....ty

Alek Dev said:
What version of QFIL? What OS did you have? what firmware did you use? or you have made backup with qfil then restore it? if you have that will be good to send me at least i can try it ....i ussually get this error dmssfail with QFIL.....ty
Click to expand...
Click to collapse
Windows 10 Pro, QFIL latest (2.7 or so), I used the latest stock ROM (tissot_images_V9.5.11.0.ODHMIFA_8.0) provided by Xiaomi.
I can only recommend to extract a ROM to a path close to your volume root, for example D:\Temp\tissot_images_V9.5.11.0.ODHMIFA_8.0.
By using deeper paths you'll probably get errors. Flat build. :good:

meltbanana said:
Windows 10 Pro, QFIL latest (2.7 or so), I used the latest stock ROM (tissot_images_V9.5.11.0.ODHMIFA_8.0) provided by Xiaomi.
I can only recommend to extract a ROM to a path close to your volume root, for example D:\Temp\tissot_images_V9.5.11.0.ODHMIFA_8.0.
By using deeper paths you'll probably get errors. Flat build. :good:
Click to expand...
Click to collapse
Thanks when i get the phone back from my carrier i will try it and post here

@meltbanana What Drivers did you use? some link?

Alek Dev said:
@meltbanana What Drivers did you use? some link?
Click to expand...
Click to collapse
I used the drivers provided by QFIL. Btw. flashing a flat build by QFIL recreates the partition layout, it really doesn't care about two system partitions.
Flashed EDL mode when I went back from treblizing earlier without going back to stock partition layout in first place.
Qualcomm Flash Image Loader handled it flawlessly to restore the standard gpt provided by rawprogram0.xml .

meltbanana said:
I used the drivers provided by QFIL. Btw. flashing a flat build by QFIL recreates the partition layout, it really doesn't care about two system partitions.
Flashed EDL mode when I went back from treblizing earlier without going back to stock partition layout in first place.
Qualcomm Flash Image Loader handled it flawlessly to restore the standard gpt provided by rawprogram0.xml .
Click to expand...
Click to collapse
So it restores the partition layout right? Also can you provide me link of QFIL?

Alek Dev said:
So it restores the partition layout right? Also can you provide me link of QFIL?
Click to expand...
Click to collapse
true, it restores the default partition layout, please pick one, that's what I used: https://duckduckgo.com/?q=QPST_2.7.438.3&atb=v89-4_g&ia=web
and here's the ROM link provided by Xiaomi: http://bigota.d.miui.com/V9.5.11.0....0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz

LeEco Pro 3 X727 stuck in fastboot

I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!

Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!

CltFlyBoy said:
Well I finally got the phone to be recognized in qfil mode and tried to force the factory ROM back onto it. The process, using FlashOne, appears to work, but the phone remains in an endless boot loop.
Anyone have any ideas? Really stuck here...
Thanks!
Click to expand...
Click to collapse
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium

mchlbenner said:
Before you had it only going fastboot what did you flash.
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Nothing - The phone was bone stock and started going into a boot loop, recovery did not work (when entering recovery mode it would exit after a few seconds and reboot). The only thing I can get to is fastboot. adb does not recognize the device at all, but fastboot does, as does the low level qfil drivers.
BUT - no matter what I push to the device it remains in the exact same boot loop. I cannot even get the (supported) TWRP to boot after I successfully flash it (either via fastboot, the Tool All In One util, etc). The boot loader is unlocked (I did that first before trying to TWRP it).
Any ideas at all before I buy another phone? REALLY appreciate the help!

I have same problem

Bumping, hoping for any traction here. I'm willing to try anything to get this phone working again (it's now a matter of principle).
I thought that the Qualcomm chipset was supposedly "unbrickable". If that's the case then I would love to understand where the failure point is...

Wish this reply was to help you, but I'm experiencing the exact same problem. Phone was acting a little laggy this morning. Turned it off and turned it back on. It shows LeEco, vibrates twice, and then loops again. Pressing Vol-Up brings it to a LeEco - RECOVERY screen, but it only sits for 2-3 seconds before rebooting again. Pressing Vol-Down brings it to fastboot, and that's about it.
I haven't gone so far as to install TWRP or anything, but this is a completely stock phone updated to 20S.
What the hell happened to our phones??
Is there any way to recover any of the data?

I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>

CltFlyBoy said:
I hear you dude - thanks for the post anyway, there is something to be said for shared misery. FWIW, I never got the dang thing to respond. I let the battery fully drain (I left it in recovery mode then the low level mode as long as it would stay on, then let it sit for two weeks after that). Same thing - I can hit it with fastboot but NOT ADB, I can write flash files to it, it looks like I'm pushing TWRP correctly, but when I try to reboot into recovery - NADA. Just goes back into it's normal boot loop, never hits recovery.
I'm starting to wonder if there is a mechanical problem with the phones. Maybe a flex cable that eventually wiggles just loose enough to do this.
What I'd REALLY love is to find *any* answer - I can't stand a problem like this that never gets explained. So with that said, does *anyone* have *any* other ideas? I'm an electronics guy, I have rebuilt too many phones to count, etc - I can try whatever *valid* suggestions y'all might have.
Thanks for letting me rant, I LOVED this phone (and it's sister, bought exactly the same time, is still rock solid).
</soapbox>
Click to expand...
Click to collapse
Welp, I tried using FlashOne2.0 and QFIL to flash when I got the phone to Qualcomm 9008 mode. After trying it a few times, I got it to flash successfully. Same problem. Didn't help it one bit, FYI.
What I did notice was that the phone was a little laggy and warm so I decided to restart it. Do you think it's a heat issue causing solder to come loose from a chip? It's happened to a laptop before -- it could be causing our issues? Did your phone run hot? I have a dual layer case on mine so it did run hot sometimes...just spitballing some ideas.

That would definitely be a possibility - heat cycling causing an already suspect solder joint to fail is common. Granted, not as common with SMD devices or BGAs like the processors, but still, it happens. That would make a lot of sense too. I'd love to tear into it and look for physical problems - I just dread taking the dang screen off just to get to the insides, I can see me snapping the thing now...
I'm trying to repro the entire thing on a completely different computer - fresh drivers/everything. Will update if I see any success.

Well crap, no joy. Got very excited as QFIL looked like it worked (pushed le_zl1_qfil_ufs_fix), pulled the phone off the computer, booted, back into the same boot loop. Dangit.
I need to learn how to give up sometimes.

CltFlyBoy said:
I need to learn how to give up sometimes.
Click to expand...
Click to collapse
You and me, both. I tried every version of the qfil files I could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that I've had this phone less than a year but I can't find any way to contact LeEco USA. None of their numbers work and they haven't replied to any e-mails I've sent.

ME TOO
epikfone said:
you and me, both. I tried every version of the qfil files i could find. No dice on any of them.
Not sure what else we can do at this point in time. The kicker is that i've had this phone less than a year but i can't find any way to contact leeco usa. None of their numbers work and they haven't replied to any e-mails i've sent.
Click to expand...
Click to collapse
x727
i have the same problem
and it's a good phone to be losse
it happened with the phone after i make an update for android 9
if i have some novelty tell me, every day i have try doing something, and nothing works
flashone 2.0 almost all roms
fastboot i did not try yet ...
if have any news share please
grateful

I have the same problem to

Was anyone able to fix the problem? I got the exact same problem yesterday in the night. Out of nowhere it started vibrating twice and now it's stuck in this loop and with a "broken" white/black screen sometimes. No idea what to do.
On another note, is there anyway to access my files via fastboot?

I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.

That sucks! Well, I am pretty sure I am not going to be able to fix my phone, but do you know if there is a way to recover my files, using only fastboot and my pc?
Thanks!
ricecrispi28 said:
I have the same problem last week and did same as everybody. Endless boot cycle even after QFIL and flashpro. I am certain it is a hardware issue.
I was using Lineage 16 and it ran hot so I put it on extreme battery saver and this helped the issue. I was just bout to change roms but been putting it off. I had it in the car next to car vent with heat blowing and google maps on. I noticed it was hot, not burn hot though. 4 hours later was using it and it had same graphical glitch problem. I'm sure it has to be disassembled and inspected, and maybe heatgun on a BGA chip or some flash memory.
Click to expand...
Click to collapse

Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.

ampped101 said:
Count me in. Same issue. Have tried every QFIL. Every adb, fastboot, recovery, rom possible. All in one tools etc etc. There is something missing from the 727 for sure that no one has access to.
Click to expand...
Click to collapse
If you create a TauBao account ( free) you can have the phone repaired in China. The turn around time is 6 weeks. But apparently you pay $10 down and if the repair is simple resoldering ( most likely) it will cost $30 https://item.taobao.com/item.htm?sp...OXhfJ&id=559560190173&ns=1&abbucket=17#detail
No doubt it seems risky, but may be worth the risk, they seem legit to me and have a lot of positive feedback
Good Luck
PS Use Google translate

the same problem
interesante, exactamente me sucedio lo mismo, estaba utilizando lineage os 16 oficial y recibi una actualizacion, como no tenia bateria suficiente pospuse el reinicio y se apago por falta de carga, al encender me quedo en bootloop, el telefono entra a fastboot y se mantiene encendido, igual funciona con qfid y flashone 2.0, flash todos los archivos pero al reiniciar sucede el mismo bucle... algo me hace pensar que las tablas de particiones en la memoria flash estan corruptas y por eso a pesar de flash con exito, la particion boot o firmware esta dañado
CltFlyBoy said:
I'm banging my head and have been working on this for a few days now. I have an X727 that all of a sudden went into the death boot loop, and all I can get to is the fastboot screen. I can connect via fastboot and push flash files etc, but I cannot connect via adb no matter what I try. Device drivers are correctly recognized (Win10 x64) and all fastboot functions work. I successfully unlocked and rooted it after this happened (in order to push new images). This thing was bone stock beforehand.
I've tried flashing every version of recovery I can find and nothing works - I always either end up back in the loop (stock recovery) or in a screen with distortion (twrp). I've attached an image of what the screen looks like with the latest twrp recovery flashed.
I'm hoping anyone can help here, I'm just about out of ideas. Thanks in advance for your expertise!
Click to expand...
Click to collapse

Security error:This phone has been flashed with unauthorized software & is locked.

Security error:This phone has been flashed with unauthorized software & is locked.
Hello everyone. I have Samsung Galaxy S5e and I tried twrp flashing.
After tablet couldn't start and boot loop.
I tried to clear cache and reboot.
After reboot i got a error,
Security error:This phone has been flashed with unauthorized software & is locked. Call you mobile operator for additional support.
Now i can not do anything.
No recovery no download mode nothing.
Please help me.....
This is the image link because i can't upload picture here.
https://ibb.co/yNvwh7P

You will need to download the original firmware and reflash with Odin, that will fix this error.
Edit: You can get it into download mode, just keep trying...

babafooka said:
Hello everyone. I have Samsung Galaxy S5e and I tried twrp flashing.
After tablet couldn't start and boot loop.
I tried to clear cache and reboot.
After reboot i got a error,
Security error:This phone has been flashed with unauthorized software & is locked. Call you mobile operator for additional support.
Now i can not do anything.
No recovery no download mode nothing.
Please help me.....
This is the image link because i can't upload picture here.
https://ibb.co/yNvwh7P
Click to expand...
Click to collapse
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.

Hi. Thank you for replying but it doesn't help. Every time i get same screen.
Believe me i did correctly.

nsx2brz said:
You will need to download the original firmware and reflash with Odin, that will fix this error.
Edit: You can get it into download mode, just keep trying...
Click to expand...
Click to collapse
Sir i can not enter in download mode.

babafooka said:
Sir i can not enter in download mode.
Click to expand...
Click to collapse
Mine did that once to me, try following the instructions and be persistant...

I am soo stupid. I brocked my tablet after unsuccessful attempts. Last week I bought new same tablet and happened again same situation after update magisk menager.
I tried your method and it works. I love you so much. You saved me.
Last time didn't work because laptop usb port was defective. I brocked 450€ tablet.

nsx2brz said:
Mine did that once to me, try following the instructions and be persistant...
Click to expand...
Click to collapse
You can flash with odin on the warning screen

PetiHun08 said:
You can flash with odin on the warning screen
Click to expand...
Click to collapse
Bro its literally easy

I have flashed tweaked rom on my SM-T820. It worked for a good 6 months and then this error has started to happen. Can reboot once or twice then the security error happens. I then need to reflash original firmware and then twrp, tweaked and repeat. Is there a way to stop this happening?

TiTiB said:
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.
Click to expand...
Click to collapse
***Moderator Edit: Translation provided***
And if this is done, the cell phone data, photos, etc. are not deleted?
Spoiler: Spanish
Y si se hace esto no se borran los datos del celular, fotos,etc.??

RaulValles21 said:
***Moderator Edit: Translation provided***
And if this is done, the cell phone data, photos, etc. are not deleted?
Spoiler: Spanish
Y si se hace esto no se borran los datos del celular, fotos,etc.??
Click to expand...
Click to collapse
Please use English on XDA, per Article 4 of the Forum Rules.
Booting into download mode will not wipe data.

thanks

I have the same problem after trying to flash TWRP on a sm-t295 - tab A.
It seems I need to flash the original firmware - T295XXU4CUF7.
Do you know where can I get it? UK variant.
Thanks

Has anyone succeeded in repairing a bricked Poco M3?

My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!

me too

waiting, someone pls

LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).

That is the points

vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?

me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.

KaMyKaSii said:
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.

did someone successfully recover their bricked poco m3 ?

gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.

KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?

my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again

I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?

Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!

i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.

vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?

gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.

Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
VID_20210514_152510.mp4
drive.google.com