Database Info

Question Hard Bricked device

I hard bricked my phone while attempting to convert my device to global. I have never seen a device this dead though, it won't attempt to boot, it gives no vibration when chargers are plugged in, holding the power and volume keys for extended times does absolutely nothing, the device acts like it is absolutely fried.
I tried leaving it on the charger for about an hour and still, there is no sign of life. This was a new (to me) refurbished device that I just got a few weeks ago. Is there anything I can do or try?

You should have all this in place prior to doing anything to device. Unsure if you can even boot edl mode for msm tool now. Probably so !! https://onepluscommunityserver.com/list/Unbrick_Tools/
Find your variant and Google how to use msm tool. Gl bud

mattie_49 said:
You should have all this in place prior to doing anything to device. Unsure if you can even boot edl mode for msm tool now. Probably so !! https://onepluscommunityserver.com/list/Unbrick_Tools/
Find your variant and Google how to use msm tool. Gl bud
Click to expand...
Click to collapse
And power button and vol + & vol - all 3 together plugged into pc will get you to edl mode. Which is how msm tool connects to device

mattie_49 said:
And power button and vol + & vol - all 3 together plugged into pc will get you to edl mode. Which is how msm tool connects to device
Click to expand...
Click to collapse
For some reason I could never get into EDL mode after brick to Qualcomm error. I used the key command you mentioned after plugging in and nothing happened. I even held it for over a minute. Also the tool on OP site didn't work either. I had to send my device for repair under warranty with OnePlus and lost my unlocked bootloader and device was locked and OEM option greyed out again. After OTA A12 update the other day I could OEM unlock. Waiting for unlock code again

mattie_49 said:
And power button and vol + & vol - all 3 together plugged into pc will get you to edl mode. Which is how msm tool connects to device
Click to expand...
Click to collapse
Turn your phone off, 30 secs or so, then hold +- volume buttons only, then connect usb lead keep hold until the Qualcomm driver is visible inside device manager ,

Here's driver msm tool from op direct , driver is setup exe ,worked for on total brick m8, and downgrade from android 12 with it too
File folder on MEGA
mega.nz

Here's driver msm tool from op direct , driver is setup exe ,worked for on total brick m8, and downgrade from android 23 with it t
File folder on MEGA
mega.nz

Tried relocking bootloader and now cannot enter bootloader

Hi, I just flashed my stock rom (oos10) and it was working, but then I tried to relock the bootloader for banking apps to work without root.
As soon as I did, I got a message saying "Your device is corrupt. It can't be trusted and will not boot."
It shows this message as soon as I power on the device and no boot animation. When I tried holding down power+volume up and then immediately power+volume down to get to bootloader, it still showed the message and didn't do anything. Is there any way to get out of this loop?
Cheers!
Edit: My device is the original nord from india on indian firmware.

I had the same issue. Use the msn tool.
Follow these steps:
1. Turn off your device
2. Connect it to your pc
3.Hold down volume up+volume down+power (you should hear the windows new device connected sound). The screen will NOT turn on but MSN should detect the device now. (if it`s not detected make sure you follow the msn tool guide to have the right drivers)
GL

If exclusive service center is nearby ..go and ask to flash sw..they will not take charges as it's free

I tried MSMtool to revert back to oos. When i did, the device booted to A10 as i used A10 version tool, but when i updated the device, it crashes to qualcomm crash dump mode and cannot boot. I tried everythig but no use Service center says its motherboard issue but i messed with software but never with hardware. Please, i need help of someone who knows the solution or even a suggestion would be thankful.

Your device is corrupt. It can't be trusted and will not boot

Hi, I tried to install a custom rom on my op 8t (latest oos, eu), I failed and I tried to lock again the bootloader with the lock command.
When I did that the phone kinda bricked and I got the following message: "Your device is corrupt. It can't be trusted and will not boot".
MSM doesn't recognize my phone, even after I installed quallcom driver. I can go in fastboot mode but I can't do nothing, I already tried to unlock again the phone, without success.
There is something I can do?

gianm.93 said:
Hi, I tried to install a custom rom on my op 8t (latest oos, eu), I failed and I tried to lock again the bootloader with the lock command.
When I did that the phone kinda bricked and I got the following message: "Your device is corrupt. It can't be trusted and will not boot".
MSM doesn't recognize my phone, even after I installed quallcom driver. I can go in fastboot mode but I can't do nothing, I already tried to unlock again the phone, without success.
There is something I can do?
Click to expand...
Click to collapse
You have to put your phone is EDL mode for the msm tool to see your phone. Turn your phone off, plug your USB cable into your computer, then hold both volume buttons and then plug into your phone. Can be a little tricky sometimes and it might take a few times to get it. The screen will be black like it is off, but it will show up in the msm tool. If your phone turns on then repeat the steps until you get it.

Not able to power off phone no matter what

Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated

zeuses23 said:
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
Click to expand...
Click to collapse
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.

zeuses23 said:
The device seems to be stuck in fastboot mode, but isn't using fastbootd so I can't make changes to critical partitions.
Click to expand...
Click to collapse
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.

Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.

Droidriven said:
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
Click to expand...
Click to collapse
Hey, thanks for the suggestion! But i would very much prefer not to open up my device. I've also heard that there is an EDL cable, but I don't know if that'll work either. Lets see
aIecxs:
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Click to expand...
Click to collapse
Thanks for your reply! A silly question, but what does super.img do? I tried flashing the critical partitions after running "fastboot oem unlock_critical", but that still gave me the error.
innergat:
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Click to expand...
Click to collapse
Hey innergat, unfortunately I believe my phone has a qualcomm chipset, so this probably won't work

Dynamic partitions are logical partitions hosted in physical super partition. logical partitions can only be accessed from fastbootd, physical partitions from fastboot.

To enter EDL mode try selecting power off and then immediately hold volume up + volume down.

Question TA-1188 in red state, can't unlock bootloader and OS won't start

I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.

J_029 said:
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
Click to expand...
Click to collapse
I'm dealing with that issue right now and my device won't even charge or turn on. Let me know if you find a fix. Did you try mtkclient already?

I have found a solution to fix red state. I also unlocked the bootloader afterwards and rooted the device.
The solution to fix red state is as following:
1. Go to: https://androidfilehost.com/?fid=2188818919693749336 and download the firmware (Its from FIH-Firmware.HikariCalyx.com Tutorial how to unlock bootloader)
2. Open SP Flash tool and load the firmware using the scatter file called MT6761_Android_scatter.txt
3. Select Format + Download and klick the download button
4. Now take your phone (Make sure to have it connected to a charger for over an hour bevore doing this, even tho the charging symbol might not show up) and hold down the volume buttons and while holding them, connect the phone to the pc using usb cable.
5. Wait for it to finish downloading.
6. When complete you should be able to start into fastboot. That can take up to one minute. Try putting the battery back in if it doesnt start after holding buttons over a minute.
7. When in fastboot, make sure the drivers are loaded. For this go into Device Manager. If there is an unknown device called Android, select update Driver > Search on my Computer > Select from a list. Then scroll down to TCL and then select Android ADB Interface. The device manager might tell you that it might not be the correct driver, but just continue.
8. Type into ADB and Fastboot window:
fastboot reboot recovery
9. When you see android laying on its back, hold power button and press volume up button (sometimes you have to press it 6 times), then the recovery menu should open up. Now select Wipe Data Factory reset. Select Yes and let it reset. After that start the phone again.
10. Your phone should start normal now. The startup can take up to 10 minutes. if it hasnt started after 30 minutes, repeat the procedure to reset it.
11. To get IMEI back, you have to unlock the bootloader and root the device. If you want to do that tell me. Its a bit complicated but i can tell you.
Make sure to follow the steps exactly

Thanks for the response, my device is a mt8163 and I have mtkclient if I can find the proper firmware what command would I use to flash the file