Database Develop

[BRICKED] fastboot mode with black screen

So.. My Huawei P10 won't boot neither into system nor recovery, the screen is off and there's no LED indication.
It is recognized in fastboot, I can erase and flash both system and recovery, though rebooting the device does nothing, it just shows up in fastboot again, still with screen off.
Is there any way to save this phone? I installed a new battery too.
dc pheonix and hcu client did not help either.
:crying:

I have the same issue. Hard brick, doesnt turn on after I upgraded to oreo.

Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.

Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you

NowLearn said:
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
Click to expand...
Click to collapse
For adb it’s needed that the phone starts completely into system or twrp - both not possible for me.
With fastboot it’s not possible to flash eRecovery, just recovery.

Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
Yes, I tried the same, and also got the security patch warning, though little did I know I could get a refund. I did not try the 'test point' method. Not sure if I get it, do you connect/solder usb-cable onto the phone's motherboard?

You need to connect the test point to ground, you can use the shielding right beside of it. Take a small wire or tweezers for it.
I did it like this:
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
DC should work now. But if it doesn’t, write it in the dc forums and you’ll get refund

Huawei P10 Successfully Recovered from Fastboot black screen on latest Security 9.
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera

chsaim said:
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
Click to expand...
Click to collapse
Can you explain exactly how?

Jannomag said:
Can you explain exactly how?[/QUOTE
you need to know exactly build number and flash latest firmware according to build number with chimera tool.
make sure that phone is in fastboot mode... am sorry if i cant explained well ... for more details write me at [email protected]
Click to expand...
Click to collapse

Yes, please share some information how can we recover our dead p10. It would greatly help the community. Thank you

I tried it with DC and Chimera. Both aren't working for me, because of the security patches. Huawei did some deep changes between October and December 2018 and made it very hard to flash even with test points - another reason for me to leave Huawei to my alltime smartphone enemy Samsung...
The DC-Phoenix and Chimera teams are working hard on a solution, take a look at their forums and you'll notice that many people have this problems, just because Huawei ****ed it up.
I mean, we did all something wrong, otherwise this threat won't exist. But Huawei made it hard for us to revive the devices and this reminds me of Apples politics. Huawei doesn't need to give support to unlocked phones but it's very unfair to prevent their customers from doing what they want including unlocking.
Back to topic:
Follow the forums of DC and Chimera. If you found any solution or fix, please post it here.
My device, also bricked while flashing the wrong firmware for rolling back from pie, shows just black screen and fastboot is working.
Test point didn't work, also Chimera couldn't flash anything.
My device gets quiet warm while in fastboot, so I disconnected the battery to prevent deep discharging.

Dear the same situation was happened with my p10 but i recovered... So if you want to recover your phone then give ultra view id and pass....... If you have chimera and dc phoenix you can make it possible.. But remember you must need to know exactly build number
If any one needs my help here is my WhatsApp contact me anytime... +923007969629

If you can share the steps. It would help the community thank you @chsaim

Yes, please share the steps to help the community.
Thanks!

There's absolutely no reason for not sharing the steps in a simple tutorial. Instead @chsaim is begging for remote access to our computers, I don't know why.
I chatted a lot with Chimera support and they told me that there's currently not way to recover, with faulty partitions caused by flashing, with the Dec.2018 security patches and newer. This included the firmware 382, on some 380 devices it doesn't work either.
They also want to send me an E-Mail when they find a solution for this. For now I got my money back from them - great support, also the DC team.
I'm happy to get a used mainboard from local market and now have my P10 as spare phone.

yeap.same **** again with Huawei phones.ı want to try pie rom and when ı try rollback oreo phones turn off and not open again.this is not like a other hard or soft brick problem because I have a experiance about other problems.phone cant charge or pc can't see the device ı cant see red led too.just dead.ı use this phone 2 years but never buying huawei again neverrrr.anybody found a solition ?

Jannomag said:
You need to connect the test point to ground...
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
...
Click to expand...
Click to collapse
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?

lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
I can access fastboot with dc-phoenix. Once I tried to send erecovery, recovery, or kernel w
Through cmd. It reads but it can't write. That's where I get stuck. If dc it's able to write then I would be able to recover my dead phone. Thank you

lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
Test point needs to be shorted until the computer recognizes the P10 as an USB serial device. You need drivers for this, which you can get from DC Phoenix.
DC couldn't flash the bootloader:
Code:
BOOTLOADER File to update: Kirin960_T0_A7.0_V1
20.02.2019 21:34:26 Starting to write device...
Writing bootloader...
Error writing Bootloader
20.02.2019 21:35:36 Writing device finished - INCOMPLETE

G900A Galaxy S5 Android 6.0 Odin Update Files - Without Wiping!

Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350

Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again

3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again

iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?

3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/

Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots

Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of

iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?

Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset

iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.

Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?

When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?

iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?

Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse

Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?

I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help

1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes

iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?

Hard Bricked Mi9 Global

So have I done something that apparently no one else has on XDA.
Hard bricked my Mi9?
I have heard that you cannot go back from Miui 11 to Miui 10 on China based models or try an install a rom with a locked bootloader.
None of those things are the case here as this is a global Mi9 purchased within New Zealand.
None of the usual tricks work. No battery light black screen no input response from buttons.
Appears like a total hard brick an I have no idea why. Does anyone have any suggestions or experience with hard bricked Mi9s that have bricked for no reason after I did standard things an the bootloader was unlocked?

what about edl ? do you already try it?

DJ_Thirtheen said:
what about edl ? do you already try it?
Click to expand...
Click to collapse
The idea of unsealing my Mi9 an looking for 2 tiny points to connect does not appeal.
Maybe I could pay a technician to try it

Bryceicle1971 said:
So have I done something that apparently no one else has on XDA.
Hard bricked my Mi9?
I have heard that you cannot go back from Miui 11 to Miui 10 on China based models or try an install a rom with a locked bootloader.
None of those things are the case here as this is a global Mi9 purchased within New Zealand.
None of the usual tricks work. No battery light black screen no input response from buttons.
Appears like a total hard brick an I have no idea why. Does anyone have any suggestions or experience with hard bricked Mi9s that have bricked for no reason after I did standard things an the bootloader was unlocked?
Click to expand...
Click to collapse
Connect the charger, hold all the buttons (except the AI one), until you feel the phone vibrate or at least see the battery charging LED blink.
Don't let go after 5-10 seconds, but keep holding for 30+ seconds. See if anything happens.

a while ago i bricked my mi9se (because of lazyiness while flashing wrong android rom version with a wrong twrp without changing twrp version before).
so fastboot or recovery not worked. EDL mode was only enterable with contact/test point method -> opening back, connect the two points, connect usb cable. (you have to look on youtube for the right contact points for mi9).
so i entered EDL mode, but:
you have to have a authorized xiaomi account to flash something, and a special xiaomi tool to do that. no chance to skip that. believe me.
on older xiaomi devices you maybe can flash something on your own in edl mode. not so on newer devices like the mi9se, and presumably also on mi9.
you have to have your phones back removed, and look for somebody on the internet with a authorized xiaomi account. there are some ppl out there, which maybe can unbrick your phone in EDL mode via teamviewer for a charge around 15 to 25 bucks.

MeltdownSpectre said:
Connect the charger, hold all the buttons (except the AI one), until you feel the phone vibrate or at least see the battery charging LED blink.
Don't let go after 5-10 seconds, but keep holding for 30+ seconds. See if anything happens.
Click to expand...
Click to collapse
Yes I will try this. Someone else tried something like this an the battery charging light started turning on an off

Bryceicle1971 said:
Yes I will try this. Someone else tried something like this an the battery charging light started turning on an off
Click to expand...
Click to collapse
When you connect the phone to the PC , go to control panel and then under device manager, Com ports you should see Port 9008. if so you are in EDL mode. As long as your phone is bound to you ( you have the needed credentials to sign into MiCloud, you should be able to restore your phone.)
I do not have the mi9 Yet. I have a Mi8 and I am considering a Mi9
Try flashing the global fastboot rom for your device.
IMPORTANT >>>>>>> It must be a fastboot images rom and not a regular recovery rom<<<<<<
Use google for the absolute latest build, I spent 30 seconds just now and found this page which as it linked : https://xiaomifirmware.com/roms/download-official-miui-roms-for-xiaomi-mi-9/ You want/NEED the one called " 11.0.3.0 QFAMIXM | Fastboot | Download"
Unpack Rom twice on your desktop, ( Its double compressed, must be unpacked twice.)
Open folder and you will see a folder that is called Images and a series of batch files.
With phone connected and in EDL or fastboot , double click "flashall.bat" Do not choose the file that asks to lock the bootloader , if it exists) This batch file will restore every single partition from the folder called images.
When it is finished the phone will reboot, sign into your wifi, and then Mi Cloud account and begin setup.
Be sure to make a Twrp backup and save it to your desktop.
You are welcome, enjoy your phone.
PS: if this fails you may need to buy a deep flash cable from Amazon, they cost $6 to $20
https://www.amazon.com/Flash-Cable-xiaomi-Models-Engineering/dp/B06ZYG46VZ Another option is using a program called QPST
If this helped you, you are welcome to buy me a beer,via my paypal. If you can afford to do so.

Tried button pushing advice an no luck. Will try this but am pretty sure surgery is probably my best option.
Thanks for trying to help. 11.0.3.0 is an excellent rom an I've had success several times with soft bricks as it bricked in a bootloader loop with the little Xiaomi cartoon thingy.
I might try your suggestion with both my miflash set up an my miflashpro set up ?

MeltdownSpectre said:
Connect the charger, hold all the buttons (except the AI one), until you feel the phone vibrate or at least see the battery charging LED blink.
Don't let go after 5-10 seconds, but keep holding for 30+ seconds. See if anything happens.
Click to expand...
Click to collapse
Thanks mate. Tried 5 times. I'll try other suggestions shared with me

ChillDuder said:
a while ago i bricked my mi9se (because of lazyiness while flashing wrong android rom version with a wrong twrp without changing twrp version before).
so fastboot or recovery not worked. EDL mode was only enterable with contact/test point method -> opening back, connect the two points, connect usb cable. (you have to look on youtube for the right contact points for mi9).
so i entered EDL mode, but:
you have to have a authorized xiaomi account to flash something, and a special xiaomi tool to do that. no chance to skip that. believe me.
on older xiaomi devices you maybe can flash something on your own in edl mode. not so on newer devices like the mi9se, and presumably also on mi9.
you have to have your phones back removed, and look for somebody on the internet with a authorized xiaomi account. there are some ppl out there, which maybe can unbrick your phone in EDL mode via teamviewer for a charge around 15 to 25 bucks.
Click to expand...
Click to collapse
Thanks for the idea bud

Bryceicle1971 said:
So have I done something that apparently no one else has on XDA.
Hard bricked my Mi9?
I have heard that you cannot go back from Miui 11 to Miui 10 on China based models or try an install a rom with a locked bootloader.
None of those things are the case here as this is a global Mi9 purchased within New Zealand.
None of the usual tricks work. No battery light black screen no input response from buttons.
Appears like a total hard brick an I have no idea why. Does anyone have any suggestions or experience with hard bricked Mi9s that have bricked for no reason after I did standard things an the bootloader was unlocked?
Click to expand...
Click to collapse
2 questions. How to get Mi9 in edl mode an what is the com port 9008 listed under in device manager

Bryceicle1971 said:
Thanks for the idea bud
Click to expand...
Click to collapse
I read something a bit before this. I am in the same spot some of you guys are in. Apparently they disabled edl authentication. . . However I am still searching around.

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Question Bricked OP 10 Pro - Help

Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
Your browser is not able to display this video.
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/

Lynxy0 said:
Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
View attachment 5586583
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/
Click to expand...
Click to collapse
Need msm

Theres no msm tool yet you have to wait for it

Is there anyone that had a look on Baido ?I tried everything under the sun.
I downloaded this from mega which has the full firmware files
https://mega.nz/folder/vMYSxBgI#LJXkyX-Ue9a4iFZPQmc80w
The closest I got was downloading the QFIL to flash it in EDL mode, but I couldnt get it to work...

I once took a bricked OP6 (hardly a month old) to service center. They fixed it, no questions asked.

I guess times are tough. GSMMAFIA steals OP software and sells it to you.

g96818 said:
I guess times are tough. GSMMAFIA steals OP software and sells it to you.
Click to expand...
Click to collapse
Considering there's a thred in this forum exactly for that...

The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....

I know this isnt helpful right now, but NEVER re-lock your bootloader. I've seen far too many people brick their ****. Why unlock it to begin with? When you relock the bootloader, anything that's not signed will not boot. I hope you get your phone fixed. Good luck to you bud

can you please tell me your mobile after hard brick have a pc connection ? beacause my phone also bricked and totally terned off no button combination no charging no pc connection
<Moderator Edit>: Quote removed since post deleted.

lordxcom said:
The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....
Click to expand...
Click to collapse
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.

g96818 said:
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.
Click to expand...
Click to collapse
i took the old approach it appears... what is the new way to roll ?

lordxcom said:
i took the old approach it appears... what is the new way to roll ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/

Eventually, I took out insurance on the phone and a week later I said its not working. Insurance support werent very technical and they replaced my phone after a week. Alernatively, I could of sent it off to OP...

i bricked my op10p same way like you... i went to store where i bought it and they sent it to repair after that i got info that they switched motherboard from it

File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Mod Edit: YouTube Video Link Removed

maison1989 said:
File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Video
Mod Edit: YouTube Video Link Removed
Click to expand...
Click to collapse
a complaint. Submit your login information.

El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please

kurador911 said:
El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please
Click to expand...
Click to collapse
Best solution: throw your phone in trash, also boycott OppoPlus and don't buy from BugPlus anymore
F*ck OnePlus !!

Everyone listen to the google logo user. Oppo is hostile to rom developers and releases broken source code and restricts msm. They're just the apple of android products nowadays