Mi 9T Hard Brick After MIUI11 Test

[Waidowai]

New Progress.
I'm back to 54GB now. Dunno if that's a big progress or small one. But at least something is changing.
Before it had 11GB

 

[Soapy!]

New Progress.
I'm back to 54GB now. Dunno if that's a big progress or small one. But at least something is changing.
Before it had 11GB

I was at 11 last night then messed something up. Can you try to put a rom on internal storage and see if it goes through?

 

[Waidowai]

I was at 11 last night then messed something up. Can you try to put a rom on internal storage and see if it goes through?

I'm trying to flash the latest eu beta now. i think 9.8.15??? I hope it goes through.
If it does I'll update how I did stuff.
I would prefer to be on stable but if beta is the only thing that works that's fine by me.

If it does not work I have 1 more twrp to try. I would like to try the chinese twrp that came installed with mi11 but i don't remember where i put it/ i'm not able to boot into it anymore???

I did was however able to boot into stock recovery.

Anyhow I'll let u know when the flash goes through. For now it will take some time I think.

---------- Post added at 09:46 PM ---------- Previous post was at 09:13 PM ----------

Ok after 2hours ish flash went through.
Unfortunately it said again the partition is write protected.
So again we have to bypass or decrypted our phones somehow

 

[datchico305]

I just flashed eu beta developer with fixed twrp and dirty flashed miui 11 and it booted just fine.

 

[Soapy!]

I can help you with that!!!!

Basically I helped a guy fix his Mi 9 which had the same issue

Download this: https://forum.xda-developers.com/attachment.php?attachmentid=4494670&d=1525641258

Then transfer the "gdisk" to your phone in TWRP with adb push

With adb shell do the following commands:
chmod 777 gdisk
./gdisk

Then in gdisk show the info of userdata partition and copy its GUID code. Then delete the userdata partition and create a new partition (with default first and last sector) and change its GUID code to the one you copied from userdata and change its name to userdata

Then in TWRP click Format Data, type in yes, continue and you're done!

I trailed back to your solution and found the correct path: /dev/block/sda. I was able to delete userdata (sda32) through gdisk and create a new userdata partition but after exiting, it seems like nothing has changed. When I reboot into TWRP, it still remains stuck on the splash screen and while browsing through the files in adb shell, it appears that the old userdata partition is restored. If this extra information helps, data is encrypted with AES 128-bit w/ ICE key wrapper (or something along those lines). Do you have anything else I could try?

 

[Arif Ferdian]

I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.

Finally, i can pass the splash screen, now its on the boot animation, ill wait will this pass the animation boot or not.

 

[Soapy!]

Finally, i can pass the splash screen, now its on the boot animation, ill wait will this pass the animation boot or not.

I give up with this device. Best of luck.

 

[Waidowai]

Finally, i can pass the splash screen, now its on the boot animation, ill wait will this pass the animation boot or not.

I've been there 2 days ago. I waited 8 hours nothing happened.

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------

I give up with this device. Best of luck.

Yeah I gave up.
I managed to get access to the internal storage from my pc and could move stuff without adb commands, basically I could move stuff normally and my pc recognized the memory but again that doesn't fix anything if we can't flash stuff.

 

[Arif Ferdian]

I've been there 2 days ago. I waited 8 hours nothing happened.

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------



Yeah I gave up.
I managed to get access to the internal storage from my pc and could move stuff without adb commands, basically I could move stuff normally and my pc recognized the memory but again that doesn't fix anything if we can't flash stuff.

Buakkakakka yaaaass... im also gave up.
You are right, nothing happened...
Ill send it back with guarantee card.

 

[loqi]

Buakkakakka yaaaass... im also gave up.
You are right, nothing happened...
Ill send it back with guarantee card.

Gl with guarantee, if they see you have unlocked bootloader...

 

[Arif Ferdian]

Gl with guarantee, if they see you have unlocked bootloader...

Easy to relock bootloader, flash stock rom clean flash and lock. And youll ready relocking ur bl

 

[Waidowai]

Gl with guarantee, if they see you have unlocked bootloader...

If he sends it back unlocked it's stupid. But just relock the bootloader and it looks normal.

 

[Soapy!]

Any volunteers?

Out of boredom and a bit of depression, I "deleted" /dev/block/sda with gdisk and now I'm met with: "System is destroyed" on boot. TWRP is gone and the bootloader relocked itself. Fastboot can't erase or flash jack since the BL is locked. I feel like if I bought an EDL cable, put the phone in EDL mode, and use miflash to flash the fastboot rom on it, it will magically be fixed. I don't know if anyone is crazy enough to try on their end though.

Steps performed (THIS IS NOT A FIX, DO NOT TRY WITHOUT EDL):
1. download zip provided by nicolassmart and extract gdisk file into the same directory as adb
2. connect phone and boot into TWRP
3. on splash, open CMD
4. type in adb push gdisk /etc/ then press enter
5. enter adb shell and change directory to /etc/
6. type in chmod 777 gdisk then press enter
7. type in ./gdisk /dev/block/sda then press enter
8. navigate to extra functionality menu (or something along those lines) then select zap blah blah
9. yes to all prompts
10. Reboot

From there you could pry the K20 open or buy an EDL cable, boot into EDL mode, and then use miflash to flash fastboot rom.

 

[Waidowai]

Out of boredom and a bit of depression, I "deleted" /dev/block/sda with gdisk and now I'm met with: "System is destroyed" on boot. TWRP is gone and the bootloader relocked itself. Fastboot can't erase or flash jack since the BL is locked. I feel like if I bought an EDL cable, put the phone in EDL mode, and use miflash to flash the fastboot rom on it, it will magically be fixed. I don't know if anyone is crazy enough to try on their end though.

Steps performed (THIS IS NOT A FIX, DO NOT TRY WITHOUT EDL):
1. download zip provided by nicolassmart and extract gdisk file into the same directory as adb
2. connect phone and boot into TWRP
3. on splash, open CMD
4. type in adb push gdisk /etc/ then press enter
5. enter adb shell and change directory to /etc/
6. type in chmod 777 gdisk then press enter
7. type in ./gdisk /dev/block/sda then press enter
8. navigate to extra functionality menu (or something along those lines) then select zap blah blah
9. yes to all prompts
10. Reboot

From there you could pry the K20 open or buy an EDL cable, boot into EDL mode, and then use miflash to flash fastboot rom.

I gave up on the phone I tried EDL too but EDL wouldn't even boot. Or it would have taken hours too and I didn't have the patients.
After the EDL reboot command the screen turned just black ( I waited 1 hour nothing happened, maybe more time woulda helped but like I said I gave up on the phone).

 

[Soapy!]

I gave up on the phone I tried EDL too but EDL wouldn't even boot. Or it would have taken hours too and I didn't have the patients.
After the EDL reboot command the screen turned just black ( I waited 1 hour nothing happened, maybe more time woulda helped but like I said I gave up on the phone).

Yes but this is EDL after wiping the entire sda storage.

 

[Waidowai]

Yes but this is EDL after wiping the entire sda storage.

I did wipe everything. Data, Cache, persist, internal storage, everything that you could wipe.
Like I said I've had access to every partition again.

My guess is if you wan't to fix it you have to wait until a new twrp version comes out. But even then it's questionable.

There are to possibilities. Either the device "forgot" that it is a Mi9T and therefore no ROM wheter it's costume or stock is flashable/ is accepted after the flash. Or the current twrp versions are not able to flash, but that would not explain why stock doesn't work.

But my guess is that former option. Because even stock recovery can't get through the encryption even after formatting every single damn thing on the storage (without errors). Basically my storage was kinda like it was a new one.

Again the furthest that I've gotten is having the device recognized on my PC with the "full 56gb storage" i guess the rest was taken by the OS. And my pc could normally move stuff in and out like a fully functional phone would.
But even than after flashing stock or costume rom it says no OS installed, even if you remove safety lines from the zip file to remove error 7 and decrypt the storage. Cuz after flashing anything the storage just gets encrypted again and the storage size goes back to 11gb and the pc won't recognize the phone anymore.

Maybe there is something wrong with the mobo or there is some kind of memorie that stored inforation about the device being on miui11 and now not a signle flash with for any rom that's mi10 works.

Your best shot is to wait for a stable miui11 or a costume working rom that is based on mi11. maybe you could try and flash an asoap rom and this works. But i'm 99% sure that you won't have any luck getting this device running with a miui10 version again.

But I'm not gonna waste any more time on this phone. The fact that every try takes 4ish hours because booting up twrp and flashing/formatting anything takes 2 hours each is just way to long for a slim chance to get it working again. If it was not for the slowdown I could try all the other stuff that I just mentioned but yeah. Someone else with patients might do.
For me I'm gonna stick on stock rom now, since eu was not that different tbh. That being said the current stock rom is 10.3.12 on global at least that is what my phone says. So 10.3.11 isn't even up to date.

 

[wives1989]

Out of boredom and a bit of depression, I "deleted" /dev/block/sda with gdisk and now I'm met with: "System is destroyed" on boot. TWRP is gone and the bootloader relocked itself. Fastboot can't erase or flash jack since the BL is locked. I feel like if I bought an EDL cable, put the phone in EDL mode, and use miflash to flash the fastboot rom on it, it will magically be fixed. I don't know if anyone is crazy enough to try on their end though.

Steps performed (THIS IS NOT A FIX, DO NOT TRY WITHOUT EDL):
1. download zip provided by nicolassmart and extract gdisk file into the same directory as adb
2. connect phone and boot into TWRP
3. on splash, open CMD
4. type in adb push gdisk /etc/ then press enter
5. enter adb shell and change directory to /etc/
6. type in chmod 777 gdisk then press enter
7. type in ./gdisk /dev/block/sda then press enter
8. navigate to extra functionality menu (or something along those lines) then select zap blah blah
9. yes to all prompts
10. Reboot

From there you could pry the K20 open or buy an EDL cable, boot into EDL mode, and then use miflash to flash fastboot rom.

Ive been hiring into a job all week and plan on trying whatever methods this weekend.

PS - you dont need an edl cable if you cn get to fastboot just endter 'fastboot oem edl' from your windows powershell.

 

[Soapy!]

I did wipe everything. Data, Cache, persist, internal storage, everything that you could wipe.
Like I said I've had access to every partition again.

My guess is if you wan't to fix it you have to wait until a new twrp version comes out. But even then it's questionable.

There are to possibilities. Either the device "forgot" that it is a Mi9T and therefore no ROM wheter it's costume or stock is flashable/ is accepted after the flash. Or the current twrp versions are not able to flash, but that would not explain why stock doesn't work.

But my guess is that former option. Because even stock recovery can't get through the encryption even after formatting every single damn thing on the storage (without errors). Basically my storage was kinda like it was a new one.

Again the furthest that I've gotten is having the device recognized on my PC with the "full 56gb storage" i guess the rest was taken by the OS. And my pc could normally move stuff in and out like a fully functional phone would.
But even than after flashing stock or costume rom it says no OS installed, even if you remove safety lines from the zip file to remove error 7 and decrypt the storage. Cuz after flashing anything the storage just gets encrypted again and the storage size goes back to 11gb and the pc won't recognize the phone anymore.

Maybe there is something wrong with the mobo or there is some kind of memorie that stored inforation about the device being on miui11 and now not a signle flash with for any rom that's mi10 works.

Your best shot is to wait for a stable miui11 or a costume working rom that is based on mi11. maybe you could try and flash an asoap rom and this works. But i'm 99% sure that you won't have any luck getting this device running with a miui10 version again.

But I'm not gonna waste any more time on this phone. The fact that every try takes 4ish hours because booting up twrp and flashing/formatting anything takes 2 hours each is just way to long for a slim chance to get it working again. If it was not for the slowdown I could try all the other stuff that I just mentioned but yeah. Someone else with patients might do.
For me I'm gonna stick on stock rom now, since eu was not that different tbh. That being said the current stock rom is 10.3.12 on global at least that is what my phone says. So 10.3.11 isn't even up to date.

gdisk's zap doesn't wipe, I think** it deletes/zeroes the partitions on the sda disk and everything would need to be re-partitioned again. But I get you, I gave up and bought a Pixel lol.

Edit:
I'm going to tag a mod to lock this thread since we've all given up.

 

[Soapy!]

@Funk Wizard Could you kindly lock this thread?

 

[Funk Wizard]

@Funk Wizard Could you kindly lock this thread?

Thread locked on OP request.