Database Info

Help - this is a difficult one

Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.

If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.

tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.

I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.

grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.

Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.

grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one

The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.

Try flashing it by adb?

Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/

ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One

have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try

Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter

markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?

ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try

markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..

ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread

luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help

[Q] Oneplus won't start anymore...

Hello all,
My oneplus one (64gb black) wont start anymore.
How did this happen?
Well,
yesterday after some trouble on my oneplus i tried an factory reset but my TWRP got stuck,
so i started the phone which was still fully working and wiped this: dalvik cache, system, data and cache
But because of that i didn't had a OS anymore ( i didn't know this was going to happen)
So i tried to install CM11 through fastboot commands but every time i got CRC errors in CMD.
So i tried it again and suddenly my phone wouldn't turn on anymore.
I charged it then for 12 hours but still didn't work.
Fastboot wont work, recovery won't work, it doesn't charge ( or atleast i cannot see it on the screen and on the led)
I tried to powercycle it but that doesn't work either.
Can anyone help me please?
Thanks!
BTW: Sorry for the bad english.

Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.

TriKE27 said:
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
Click to expand...
Click to collapse
Thanks for the answer but that doens't work either.

And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

rtomakov said:
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks

bboy521 said:
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
Click to expand...
Click to collapse
Can you see your phone in modems or ports section of device manager?

rtomakov said:
Can you see your phone in modems or ports section of device manager?
Click to expand...
Click to collapse
Thanks for the answer!
My phone is working again! Jeejj
The problem was the unknown device at device manager, so what i did was disconnecting my phone from pc and then press the power button for 1 min, connect it back and then the device manager recognized it!
I'm now flashing it back to exodus rom!
Thanks all!!

I have this situation before, wiping everything dalvik/cache/system/data and internal storage. So my phone has nothing, just few empty file. Now how do I solve it ?
Simply I boot into TWRP. Luckily the driver detect my phone after I connect to pc so I open internal storage, copy the rom and gapps and put em on TWRP folder. Then just go to install on TWRP and look for the folder and voila, flash and phone back to healthy state.
Never ever ever delete that internal storage again lol.

Indeed man
But with me TWRP wasn't available either so yea...
It wont happen again haha
But thanks bro!

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

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!

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.