Well, it's hard bricked - OnePlus 6T Questions & Answers

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

Related

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse
laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse
laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.
dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

Unusable A2017G

So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?
I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.
Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.

Your device is corrupted. It can't be trusted and ...

After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
You're not waiting long enough.
And by the way it tells you to press the power button to PAUSE booting.
It's only a few second wait (possibly one second longer than the default unlocked message on other devices). I just timed it. It's 8 seconds. A regular device will display that message for 3-4 seconds.
It just means that your bootloader is unlocked.
Sent from my ONEPLUS A6013 using Tapatalk
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
Had this issue on my op6. This solution fixed it for me. not sure if we have this tool for the 6t yet. If the message is orange then it's the unlocked bootloader message. If it's in red it's the corrupt message and you gotta hit the power button twice to boot.
The message i get is in RED color. Not in ORANGE.
And yes if you press twice the power button it boots normally.
My question is about how to get rid of this!!!
If for some reason the device is gonna reboot -like in Settings-> Utilities-> Scheduled power on/off- it wont boot until I get action...
Fear!!!
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
azzinder said:
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
Click to expand...
Click to collapse
And password
iaTa said:
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
Click to expand...
Click to collapse
Waiting patiently for news...
azzinder said:
Waiting patiently for news...
Click to expand...
Click to collapse
Rescheduled to tomorrow
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Done
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
This works! It is a lot easier than the MSM download tool solution. However, I wonder if it just mutes the notification, or solves the problem indeed?
I flashed a TWRP backup afterwards and that did not go well. I wonder if that could be caused bij the corrupt problem?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Doesnt working for me. after reboot also i can see same error. however i can boot after twice pressing on power. i do not want to use Msm tool as it will format data. seems no other way as of now
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Hey that's amazing! I think this has finally solved this for me on my OnePlus 6. I was perfectly content to just put up with that warning forever, but this seems to have cured it ... And simple too! Thanks ?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Thanks, this worked.
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
No the device is not corrupted. Unlocked bootloader warning vs the device is corrupt are 2 different things. My bootloader ia unlocked since the day 1 and never had the corrupt warning until I flashed OOS 9.0.5. The step above resolved the device is corrupt issue.
---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------
kitcostantino said:
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
Click to expand...
Click to collapse
Yeah I agree its something to do with the slot A and B. I was running the phone with unlocked bootloader since day 1 and had flashed multiple twrp updates, kernels etc and never had the issue. It's when i recently flashed OOS 9.0.5 and then twrp on it is when this started.
Not sure about OP6T but on my OP6 the terminal commands helped.
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
This worked on my 6T ! Thanks !

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?

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.

Categories

Resources