Database Users

Well, it's hard bricked

I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?

For clarity, you were running a OP6 rom on the 6T?

Krunk_Kracker said:
For clarity, you were running a OP6 rom on the 6T?
Click to expand...
Click to collapse
XxX made a 6/6T rom.

The rom was made for the 6 and 6T. It flashed and booted with no problems. Multiple reboots no issues. Wasn't until the software update installed itself I had issues

Does a computer recognize it at all, even with any weird key combinations?

skinzy98 said:
Does a computer recognize it at all, even with any weird key combinations?
Click to expand...
Click to collapse
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
I had pretty much the exact same issue Saturday, and I was t even rooted or unlocked bootloader so I know how you feel

There's an option to turn off automatic updates, for future reference.

blue5055 said:
I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?
Click to expand...
Click to collapse
Have you tried to flash the fastboot Rom in the xda thread?
Enviado desde mi ONEPLUS A6013 mediante Tapatalk

blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Using the tool above I was able to unbrick and return to stock. For anyone else bricked, that tool will help you

Bricked my Chinese OP6t (A6010) and not sure what to do. Help??

I was trying to help a friend out by installing the international OS on his new OP6T (A6010) because I know a friend who did it a year or two ago and it worked perfectly. We thought it would work out but I couldn't get the firmware to install using the normal system update--it said that the firmware was lower than the currently installed firmware and therefore couldn't be installed.
So, I tried downgrading using the msm tool (I didn't realize the Chinese version was different...) and now it is stuck in a boot loop saying "build version and HW version is not match!"
What options do I have here? I didn't install TWRP (I was going to but tried the MSM tool because people were recommending it on many other sites...but were only talking about Tmobile and Global variants so I didn't realize Chinese was an entirely separate one).
Is there any way to fix this?

You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.

snatale1 said:
You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.
Click to expand...
Click to collapse
No, when I hold any combination of buttons, it gives me the error message. I can't do anything with it at the moment.
I got it to flash "fastboot mode" for a moment, but then the error message went up again and black screen.

That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.

snatale1 said:
That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.
Click to expand...
Click to collapse
Thank you for the information here with this. Are all msm things specific to certain firmwares or is it possible to throw a firmware into an msm thing? I'm not sure about this one yet.

I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003

mchlbenner said:
I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003
Click to expand...
Click to collapse
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.

nightcow said:
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.
Click to expand...
Click to collapse
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?

snatale1 said:
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?
Click to expand...
Click to collapse
Yeah, I was able to get it recognized by the computer and the msm software. It was just not accepting it.
I actually finally got it to work, though, but using the patched version of the msm tool that Tmobile users were using to install the international firmware, because it ignores the check for hardware/firmware matching and just forces the firmware on there.
It took two different msm tools/firmwares but finally it worked out. It was an incredibly relieving sight to see it boot up and not immediately go into the same bootloop again.

Glad to see you got it going.

Good day, please I got into the same issue of hardbrick on my oneplus 6t chinese variant. Please would you be kind enough to give a break down on how you got it to work. And were you able to finally install Oxygen OS?

OnePlus 8 Pro refuses to install TWRP. Qualcomm Crash Dumps every time. Any advice?

I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.

Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.

Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not

Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.

TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.

Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.

TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch

Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.

TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though

Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.

TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.

Help ! Redmi 2 (2014811) keeps restarting after booting

Hello everyone, that's it. I have a Redmi 2 enhanced version (2014811) . It can be turned on now but it keeps restarting as soon as it enters the first page. Now it can enter the fastboot mode. How can I save it? (The phone should not be rooted before)
Postscript: If possible, can I take this opportunity to use a third party ROM to upgrade to a higher version of Android? (e.g. Android 10 or higher）
Thank you for your comments, thank you very much ! ! !

Deleted.

LR7875 said:
If you know how to use fastboot, try installing TWRP. (Execute command fastboot flash recovery twrp.xxx.img where twrp.xxx.img is the filename of twrp placed into the fastboot folder on your computer. If you don't understand ask me further.)
Wingtech Redmi 2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Then wipe> factory reset in twrp
Then flash this rom
[ROM][11.0][UNOFFICIAL][wt88047x] LineageOS 18.1
Important information: This thread is for LineageOS 18.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Click to expand...
Click to collapse
First of all, thank you very much for your advices, bro! Do I need to unlock/root first before installing TWRP? Because I have not been rooted it before, can I just flash in TWRP directly under the fastboot environment without rooting? Sorry, I still don't know how to do it, maybe some concepts have not been figured out yet. .....

If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...

blackhawk said:
If the phone is stock and not rooted a factory reset should restore it.
You will lose all data.
It may be possible to start it and get it to run stabily in Safe mode, if so it's a 3rd party startup app causing it. Find it...
Click to expand...
Click to collapse
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?

Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.

2021redmi2fans said:
I'm afraid that during the entire flashing process, some things have been done wrong and cannot be remedied in the future. Are there any basic tutorials on flashing that I can learn?
Click to expand...
Click to collapse
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.

LR7875 said:
I apologize that no, you will need to get into system and sign into your mi account in order to unlock the bootloader and allow you to flash anything, which you cannot do as for now.
Click to expand...
Click to collapse
He should be able to reflash the stock rom though, right?

LR7875 said:
Sorry, sent the wrong post. Try factory resetting in miui recovery mode. If it still not boots, your phone is permanently fried on the motherboard level.
Click to expand...
Click to collapse
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......

2021redmi2fans said:
It doesn’t matter, the problem is that I don’t know how to enter the miui recovery mode......
Click to expand...
Click to collapse
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.

However, before the loop occurs, Mokee 7.1.2 was installed and used it normally for a period of time, does that matter?

blackhawk said:
Whatever button sequence is used for that device.
Timing is everything, keep trying until you get it.
It's harder to do when you really need to
Take a break and make sure you got the right sequence/timing.
If it's booting up to the Home page it's salvageable I think... better than a boot loop.
Click to expand...
Click to collapse
Bro really thank you

2021redmi2fans said:
Bro really thank you
Click to expand...
Click to collapse
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.

blackhawk said:
Stock Androids are easy, that's one reason I run stock. The only thing that really kills them is an outright hardware failure.
Click to expand...
Click to collapse
redmi 2 runs on stock rom android 4.2 right? you can not install any single app on that.
when the op fixed it it is advised to install a custom rom.

How to fix OnePlus 8 pro won't turn on

Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.

Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger

jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You all are flashing wrong xbl img. Wrong ram versions

what do u mean xbl img? I remember I have read about the ram versions but I think it wasn't the 8 pro...

duxler said:
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Click to expand...
Click to collapse
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
Im am sorry for you guys but you hard bricked your phones for real.
The only thing you can do now is to replace the motherboard.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com

jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11

AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.

xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Unfortunately that's the case...

jimger said:
Unfortunately that's the case...
Click to expand...
Click to collapse
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.

xtcislove said:
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
Click to expand...
Click to collapse
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...

jimger said:
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
Click to expand...
Click to collapse
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.

xtcislove said:
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
Click to expand...
Click to collapse
Yeah tbh I have every photo etc backed up. Also run my daily swiftkey backup before updating. But the big big bummer now is that I have no way to restore banking apps to tablet atm... Anyway let's hope at least they replace it...

As I understand it, the phone can be thrown away

how will Qualcomm ® Package Manager help if the computer does not see the device.
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse

duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Tbh at least I hope they replace it... For now found an Mi A1 from a friend...

I know this topic has been brought up before. But there is not always a half and full explanation.I have Oneplus 8 pro too. I can't enter recovery mode. Boots into fastboot. I've printed a wide variety of msm tools files from edl. It writes smoothly, but when opening the boot screen, it says "your device is corrupted it cannot be trusted and may not work properly" and does not open. What could be the reason? Android 10 11 msm roms, Coloros Hydrogenos all but all tried. There is no recovery. I can't open the oem lock, I can't do anything.

xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager

AkayamiShurui said:
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
Click to expand...
Click to collapse
Im sorry my friend i dont understand your post.

xtcislove said:
Im sorry my friend i dont understand your post.
Click to expand...
Click to collapse
If your got discord I can show you

duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Hold up. I'm looking for a dead OP8 Pro. I have started a conversation with you; check notification.