Database Users

[HELP] Bricked my phone

Helo!
I recently purchased a Redmi 3s which came with a fake rom so I decided to flash a new rom. I tried it via the updater app but it didnot work. Then after reading a few trick I tried the fastboot method but the process got stuck and now my phone cant boot. I was able to boot in fastboot and I see it in list of the devices but the mi flash tool keeps crashing.
Note: my bootloader is locked and I dont have any custom recover it was a stock phone.

Hi,
what means crashing? You get an error message?
You habe to try another MiFlash Version. The latest also didnt work for me.
You have to flash the latest developer rom to unlock the bootloader.

You can't flash ROMs through fastboot if your bootloader isn't unlocked... Never mind now you try to enter fastboot and flash a TWRP into it.

Yappuccino said:
You can't flash ROMs through fastboot if your bootloader isn't unlocked... Never mind now you try to enter fastboot and flash a TWRP into it.
Click to expand...
Click to collapse
I cant flash a reccovery because it says it is locked.

Apparently there's a method that involves using EDL mode and a deep flash cable, not sure if it'll work in your case or not

psychopac said:
Apparently there's a method that involves using EDL mode and a deep flash cable, not sure if it'll work in your case or not
Click to expand...
Click to collapse
Yes I heard about that but it seems a bit dangerous.

r.omega888 said:
Yes I heard about that but it seems a bit dangerous.
Click to expand...
Click to collapse
Considering that the said method restores your phone and you have a spare USB cable lying around, I'd say it's worth a try

r.omega888 said:
Helo!
I recently purchased a Redmi 3s which came with a fake rom so I decided to flash a new rom. I tried it via the updater app but it didnot work. Then after reading a few trick I tried the fastboot method but the process got stuck and now my phone cant boot. I was able to boot in fastboot and I see it in list of the devices but the mi flash tool keeps crashing.
Note: my bootloader is locked and I dont have any custom recover it was a stock phone.
Click to expand...
Click to collapse
same issue here, I was talking about my problem here
Trying to find a way to fix it, thanks!

If you have locked bootloaders, the only way to recover your phone is flashing ROM using MiFlash. To do it, you need to enter EDL. Now the only way for locked bootloader users is deep flash cable. You can google for guide how to make it. The trick is to connect green cable to the black one.
If you want to unlock bootloader and don't stuck at 50%, you need to flash a DEVELOPER ROM (International/Chinese, doesn't matter).

Forget all the complicated deep flash cable making guides. There's an ultra easy way to make one. Just strip off the outer jacket of a usb cable, about an inch or so, exposing the 4 wires inside. Then just push a pin or needle through the green and black wires like this guy has done. Easy peasy!
I made mine this way and was able to enter edl mode and flash a fastboot rom.

I can' get it to boot properly. Help me please!

A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.

Tried ZUI QPST image or CM one?

ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.

kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.

ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM

kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?

ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.

kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?

ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.

kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.

ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.

kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns

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

device bricked by itself..? unable to boot or charge

i shut down my device by tapping power off. then removed sim card and sd card after screen went black. but when i tried to power on, it doesnt respond.. i tried holding the power button for 10s, it gives me a black screen and vibrates and instantly closes again.. so i cant boot into recovery, i cant boot to fastboot, and its unreadable on pc, it doesnt charge, no bootlogo, nothing. just bricked..
.
i dont know why, but it just bricked by itself.. i've been using mokee 9 date of 1/1/2020 thats the last update i installed, with add on su and everything was working perfectly and even if i reboot multiple times..
bootloader was unlocked so xiaomi centers wont help me..
how is it possible to make it boot again? i mean like wtf even happened? i did nothing.. i didnt flash anything and system was READ ONLY before powering off.. all i did was remove sim and sd cards... even after flashing mokee updates yesterday, it booted normally and idk what's going on..
any help?
EDIT: the phone's hard disk IC was damaged. I went to a tech guy and he changed it but then the motherboard broke entirely after flashing the qcn file for imei. Device out of warranty of course because of the damn bootloader. Thank you xiaomi for the great phone that only lasted one month before dying completely.

attempt 2
in attempt 1 i tried force reboot as mentioned, didnt work
attempt 2 : i tried force reboot while plugged to pc, this showed up

attempt 3
i tried to flash a new firmware, but device unreadable. must be on fastboot mode for mi flasher to be able to read it. im starting to lose hope.. the device is new though it makes me sad

on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything, because it didnt actually boot into EDL mode, had to open my device physically and use test points. so attempt 4 failed

does this mean fastboot works?
after attempt 4, it said successful so if fastboot works like that then i can flash stock boot.img or something.. right? which image should i start with

forum
boody shaban said:
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything. so attempt 4 failed
Click to expand...
Click to collapse
this is the forum of the bricked phone similar to mine, except that i didnt try any flash like him it just happened randomly
https://c.mi.com/thread-2334646-1-0.html

attempt 5
attempt 5 failed, i tried flashing whole firmware one by one, i started with vbmeta, then recovery but it failed. idk what to do

notice
i have noticed that it only flashes small img files, if its 100kb or more it will fail. maybe due to device restart because the only way to make it read in fastboot mode is to force restart multiple times until it flashes. what to do now?

attempt 6
so according to this video
https://www.youtube.com/watch?v=yJoIiLE_w3w
he installed a driver (name in attachment) then refreshed on mi flash so his device became readable on mi flasher
i tried that but it didnt work.

final attempt.. out of hope
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.

boody shaban said:
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
Click to expand...
Click to collapse
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.

Reason for brick
cg730620 said:
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Click to expand...
Click to collapse
Yes, I hate tearing up my device so I took it to a professional. He failed to open ADL but he did the 9008. Now he waits some kind of credit. Not sure if for the app to work or for the bootloader to unlock, although it was already unlocked but maybe somehow got locked..
Any way, expected reason for brick is either latest magisk module, or kernel tweaks..

I gave the device to a professional, but he also failed to flash it even with test point. He said he was searching for a file.. I dont remember its name, something like IMOH..

Now I need to know any possible reason that might brick my phone again to avoid it
cg730620
Click to expand...
Click to collapse

cg730620 said:
.
Click to expand...
Click to collapse
The app he used was called ultimate multi tools

test point attempt failed
i did the test point, booted to 9008 mode but still nothing.

i think i know why the phone got bricked by itself, it got ARB stands for AUTOROLLBACK
read more about it here https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
bootloader got automatically locked again.

Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
boody shaban said:
i did the test point, booted to 9008 mode but still nothing.
Click to expand...
Click to collapse
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/

cg730620 said:
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
Click to expand...
Click to collapse
but im sure i have all drivers installed in fact i used mi flash more than once and it worked perfectly fine, and i swear i didnt try to lock it or anything, what happened is, mokee auto updates installed add on magisk and it was the latest version so i think this might have bricked it. idk..

ok i downloed all the drivers and reinstalled them, same error : "library not registered"

Phone acting strange - Bricked?

Hi
My phone stopped working a couple of days ago, I had been running a custom rom for 2 mths. I tried to restart and boot to recovery TWRP as I was going to reflash the rom. It charegs with no lights, for a day I couldnt boot to TWRP if it did it stayed on the start screen with no options. Today I can get options in TWRP so I tried to start fresh install but intstallation stops at step 1 ?
I have no idea what happened to the phone or why it just died, but dont understand why I can get into TWRP but cant flash rom etc. Also sometimes it say system destroyed message? but still can get into TWRP ?
Any ideas or help will much appreciated really would like to fix this rather than write the phone off.
Thanks

i think flashing firmware is the only option

ranjodhricky said:
i think flashing firmware is the only option
Click to expand...
Click to collapse
Hi, yeah I think thats what I try, is this flashing stock rom via MI flash or a different process?

try miflash if doesn't work try QFil

update
ranjodhricky said:
try miflash if doesn't work try QFil
Click to expand...
Click to collapse
Hi, been playing with this when i have time over the last few weeks.
I have been trying to flash firmware, I dont seem to be able to get QFIL to work for me, it wont reconsise the port. However MIFlash does but I get errors, sometimes it flashes but doesnt end? other times i have had error flashing modem_a or error flashing modem_b (maybe device is locked).
In ADB it says already unlocked. Also I can only boot into fastboot, not recovery so i cant intall anything from adb sideload, it wont boot into bootloader just powers off if i try this. I guess theres no recovery on it now as I cannot boot into it.
Any ideas on where to go from here , EDL? I really didnt want to attempt to open the phone.
Thanks

Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'

Yincen said:
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Click to expand...
Click to collapse
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.

healy2k said:
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
Click to expand...
Click to collapse
try doing a factory reset from Recovery , good luck