I managed to brick my X3

SKULLHEADHJ

New member
Jan 1, 2013
4
0
0
Hi forum,

I tried really hard and in the end I think I've hardbricked my phone. Of course, I started with unlocking my bootloader and flashing TWRP. I then tried flashing a custom ROM (Nitrogen) so the process for that was:
  1. Flash miui_SURYAGlobal_V12.0.2.0.QJGMIXM_c8f2531a02_10.0
  2. Wipe
  3. Install ROM
  4. Install GAPS
All went well, after which I flashed Magisk's manager which I think corrupted my ramdisk and /sdcard folder. The phone wouldn't boot into system and went straight into recovery. I'm unfamiliar with the new android folder structure, however my /sdcard folder was corrupted (all folders were just random base64 text). After that I did a full system wipe for some reason, and couldn't flash the stock firmware from recovery anymore with messages like:
Failed to mount ´/vendor´
Failed to mount ´/product´
Now this is where I probably messed up the most. I downloaded the EEA stock fastboot image instead of the global one. I flashed it with MiFlash and all went well. But now when the phone rebooted it went into the Nitrogen logo and was stuck there for half an hour. I thought something was up so I now downloaded the global image, went into fastboot, tried to flash it but I couldn't due to the "Flash xbl error". This is when I knew I really **** the bed. Both the global and eea image wouldn't flash because of that error. I left fastboot and my phone wouldn't boot again.

Good news is I installed the Qualcomm drivers and my phone at least shows up as a Qualcomm device and is detected by QFIL. I quickly tried flashing the stock global rom with QFIL but I got Sahara errors that could be due to other stuff but I don't want to push it any further before asking you guys. Any advice?:cool:

Update: The current state is black screen, however I can get it to flash stock ROM until it asks for authentication and tells me I'm not authorized to do this ( I'm guessing this is EDL). Should I ask my vendor if they provide such services?
 
Last edited:

editheraven

Senior Member
Jan 27, 2013
167
10
38
Ploiesti
Ask this guy to flash through edl. +7 967 777-15-98

It costs about 30 USD.

To boot into edl you need to specifically boot though key combinations or testpoint.

I would recommend against flashing a China based rom on a global device. Don't switch versions around as you can mess up your persist.img partition.

Try running the bat flash script directly into cmd and don't relock bootloader.
 

jcyrdrgz

Member
Nov 2, 2019
25
2
0
I got the same scenariS.

---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------

Hopefully someone can help us
 
Last edited:

Speedo.thc

Senior Member
Jun 7, 2013
1,270
1,468
153
Paris
I got the same scenario right now after I wipe my data and tried to install v12.0.3.0 EEA coming from Havoc OS.

---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------

Hopefully someone can help us with the EDL thing for MiFlash
Do you know where are points edl ?

---------- Post added at 08:11 PM ---------- Previous post was at 07:59 PM ----------

I got the same scenario right now after I wipe my data and tried to install v12.0.3.0 EEA coming from Havoc OS.

---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------

Hopefully someone can help us with the EDL thing for MiFlash
Fake points in red
True in green
https://www.mediafire.com/view/c7mdrgjgi83nrjl
Credit to @mahajant99 at télégram
 

dustojnikhummer

Senior Member
Mar 1, 2017
133
21
18
I think you messed up somewhere else. EEA should be flashable on Global phones. EEA is just European version of the Global ROM that ships with stuff like Google Dialer. And besides, when you flash Global MIUI on Chinese phone you just get an error that it can't be used
 

Speedo.thc

Senior Member
Jun 7, 2013
1,270
1,468
153
Paris
Oh I doesn't open the battery cover of my phone to do that. It's just automatically being detected as Qualcomm 9008 something under Device Manager which means that it's on EDL Mode without touching those points.

The only solution I have in mind is to wait for the latest fastboot file for v12.0.3.0 EEA (Because this is the last update my phone have, which i think causing the problem not letting me flash the V12.0.2.0 EEA due to rollback protection) so that I can see if it MiFlash will let me flash it without the EDL Authentication.

Or somebody who has the capability to edit the firehouse for the firmware to disable the EDL Authentication.
You can wait, it's right.
At the point that you enter edl like the command "fastboot oem edl" you have more luck to unbrick device.
For your information we are minimum 3 to get brick now , more than yours coz it's not booting in edl but die.
Flashing (paid) with edl didn't help anymore.
 

jcyrdrgz

Member
Nov 2, 2019
25
2
0
You can wait, it's right.
At the point that you enter edl like the command "fastboot oem edl" you have more luck to unbrick device.
For your information we are minimum 3 to get brick now , more than yours coz it's not booting in edl but die.
Flashing (paid) with edl didn't help anymore.
Well, I'm planning to visit a service center by the end of the week
 
Last edited:

Speedo.thc

Senior Member
Jun 7, 2013
1,270
1,468
153
Paris
Well, I'm planning to visit a service center by the end of the week if v12.0.3.0 fastboot file is still not out. I'm just really tired of searching for hundred+ threads already about this EDL Authentication when I tried to flash the v12.0.2.0. I really hope that they'll release it soon and it will let me flash it without the EDL Auth Acct.
Hi, no bypass for PocoX3 actually.
But you can miss time and download virus in search.
 

cogli0ne

Member
Jan 3, 2013
30
12
0
Have you tried a deep flash cable to force the phone into EDL-mode?
I'm not sure that it still works, but it was a solution to save a bricked Xiaomi a couple of years ago.
 

mikai1

New member
Aug 28, 2016
1
0
0
how I solve the same situation

Hi forum,

I tried really hard and in the end I think I've hardbricked my phone. Of course, I started with unlocking my bootloader and flashing TWRP. I then tried flashing a custom ROM (Nitrogen) so the process for that was:
  1. Flash miui_SURYAGlobal_V12.0.2.0.QJGMIXM_c8f2531a02_10.0
  2. Wipe
  3. Install ROM
  4. Install GAPS
All went well, after which I flashed Magisk's manager which I think corrupted my ramdisk and /sdcard folder. The phone wouldn't boot into system and went straight into recovery. I'm unfamiliar with the new android folder structure, however my /sdcard folder was corrupted (all folders were just random base64 text). After that I did a full system wipe for some reason, and couldn't flash the stock firmware from recovery anymore with messages like:

Now this is where I probably messed up the most. I downloaded the EEA stock fastboot image instead of the global one. I flashed it with MiFlash and all went well. But now when the phone rebooted it went into the Nitrogen logo and was stuck there for half an hour. I thought something was up so I now downloaded the global image, went into fastboot, tried to flash it but I couldn't due to the "Flash xbl error". This is when I knew I really **** the bed. Both the global and eea image wouldn't flash because of that error. I left fastboot and my phone wouldn't boot again.

Good news is I installed the Qualcomm drivers and my phone at least shows up as a Qualcomm device and is detected by QFIL. I quickly tried flashing the stock global rom with QFIL but I got Sahara errors that could be due to other stuff but I don't want to push it any further before asking you guys. Any advice?:cool:

Update: The current state is black screen, however I can get it to flash stock ROM until it asks for authentication and tells me I'm not authorized to do this ( I'm guessing this is EDL). Should I ask my vendor if they provide such services?
I installed twrp and the xiaomi eu and my phone ended in twrp only boot with sdcard partition encrypted, tried to write with miflash fastboot rom I get xbl error , reboot in twrp format data then installed xiaomi eu.zip without any problem so far.