Database Info

Pixel will not power on after TWRP 3.2.1.2 flash

Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!

I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.

By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.

I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk

KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol

shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip

KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.

shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.

KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.

Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP

Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.

mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.

I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.

What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314

Help me fix a bricked OPO :(

Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?

try charging the phone for a few hours

se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.

sounds like u need a new battery

ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.

@bmark240
help please

se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.

bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.

kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.

Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.

THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os

THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out

FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.

i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.

Your Device is Corrupt and Cannot be Trusted on Pie 9.0

guys,
I went from rooted op6 5.1.11 to stock 9.0.3.
I flashed the complete stock 9.0.3 through local upgrade on the device settings. Next, after reboot, I went to recovery and wiped entire devices. after each reboot I get this; Your Device is Corrupt and Cannot be Trusted in red text, I have to press twice the power button to reboot device propperly, if i dont press the power button twice it gets in a bootloop, this is really strange and also annoying !
How can I fix this, please help

I have no idea if it's the correct thing to do, but after putting up with that message for months (no ill effects from that warning BTW), this post is what fixed it once and for all on my OP6:
https://forum.xda-developers.com/showpost.php?p=78699763&postcount=12

foomanjackel said:
I have no idea if it's the correct thing to do, but after putting up with that message for months (no ill effects from that warning BTW), this post is what fixed it once and for all on my OP6:
https://forum.xda-developers.com/showpost.php?p=78699763&postcount=12
Click to expand...
Click to collapse
thnx, i tried something else which required to use a tool called msmdownload, it now works.

If you are rooted enable Dmverity & force encryption and install magisk again using direct method

I f up

My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Edit: you know maybe im a genius, i fix it by myself
1. Boot to bootloader (mine work again after I type adb reboot bootloader on the terminal. Volume down + power button
2. I tried to reboot to lineage recovery but apparently it seems to ignore it so I flash twrp fastboot flash (I drag my twrp file here)
3. On twrp I reboot to recovery to get to lineage is recovery
4. I tapApply update and the From adb
5. On the terminal I type adb sideload (I drag lineage system file here)
4. And that's it,

aL_09 said:
My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Click to expand...
Click to collapse
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.

All-In-One said:
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.
Click to expand...
Click to collapse
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot

aL_09 said:
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot
Click to expand...
Click to collapse
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.

All-In-One said:
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.
Click to expand...
Click to collapse
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.

aL_09 said:
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.
Click to expand...
Click to collapse
Is there any chance you can take a photo and show me that screen? Never heard of it before.

All-In-One said:
Is there any chance you can take a photo and show me that screen? Never heard of it before.
Click to expand...
Click to collapse
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u

aL_09 said:
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u
Click to expand...
Click to collapse
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.

All-In-One said:
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.
Click to expand...
Click to collapse
Who's the mod?
https://forum.xda-developers.com/attachment.php?attachmentid=4929067&stc=1&d=1579303524

Question Half-Brick? Power/Sleep Button Shuts off Phone Immediately like CRT/Old TV

I have an OP 9 LE 2115 Global in USA
I was on LOS 19.
I had some issues and wanted to revert back to stock OOS 11.
First I tried via Recovery to flash Stock ROM OOS 11, but I had an error regarding the system version being too old and it didn't complete. The phone would no longer boot to OS.
I got the MSMDownloadTool from here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R/
I used the tool successfully and got my phone booting to OS again.
But now my power button IMMEDIATELY turns off the phone whenever pressed, and does this kind of CRT TV shutdown, where the screen phases out vertically with colors.
This happens in recovery/fastboot menus as well, most of the time, and makes booting into recovery/fastboot *almost* impossible, as when I let go of the power button it turns off, and when I select and option with the power button it shuts off.
Any information would be so helpful! Thank you fine knowledgeable people of XDA.

For anyone to help, we need to know which model you have and which version of msm tool did you use?

Updated my original post. My apologies for the lack of important details.
Also I got a TWRP recovery successfully installed, so I have a recovery again.
I found this article that explains how to install each part individually via fastboot
Do you think this would help with my errors of non-existent partitions?
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
I'm tempted to try, but if anyone could chime in first?

Still having this issue, has anyone ever even heard of this problem?

wakeeshi said:
Still having this issue, has anyone ever even heard of this problem?
Click to expand...
Click to collapse
This sounds like a hardware problem. If just after msm the phone does this, hardware it is then.

Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?

wakeeshi said:
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
Click to expand...
Click to collapse
Flash with msm again. If problem persist after first time setup, hardware problem.

MrSteelX said:
Flash with msm again. If problem persist after first time setup, hardware problem.
Click to expand...
Click to collapse
I have flashed with MSM a couple more times and same thing.
But for example, I got it to boot without the issue again, and everything works as normal, but as soon as I turn the phone off or it dies, I will struggle to get a boot that works properly.
I end up fiddling with the holding the volume buttons and power buttons in different combinations and eventually it works. I'm not sure if that's just random, or if I'm actually causing it.
If I can have a completely working boot, where the power/sleep button functions as normal, it seems like it's a firmware, data issue. Could you elaborate?
Thank you!

Hoping to bump this and try to get some help. My GPS also has failed to get a fix in this kerfuffle. (this is one of the reasons I was originally resetting to stock from LineageOS 19). Any advice?

Hardware problem and the fact it is 100% repeatable is a sign of hardware problem.