Database Info

Problem with rooting Oneplus One

I have a problem with rooting my Oneplus One. It all goes well until twrp needs to start.
My screen is all black and its not reacting to anything. I have to wait till the battery is empty to turn off.
Also when its in this stage my laptop gives me an error: 'USB Device is Not Recognized'.
I hope you can help me.

Did you check the md5 of the recovery image before flashing it? Please copy/paste the text from the command prompt on a flash attempt.
Transmitted via Bacon

Can you access fastboot mode?

It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.

hazefetish said:
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
Click to expand...
Click to collapse
That doesn't make sense, what do you mean by bootmode? And you didn't answer either of my questions, I asked those for a reason, if you're not going to provide the information that's needed it's pretty much impossible to help you.
Transmitted via Bacon

You can always turn off your phone by holding the power button for 10 seconds.
Try fastbooting the latest TWRP. => http://techerrata.com/browse/twrp2/bacon
It's possible that you have flashed a corrupted file or even a TWRP for a different device.

Alright
Ive tried it again.
At the moment it should boot into twrp the screen turns black.
It shows up as normal adb device, its still connected but my screen wont show me a picture.
I did it with Oneplus One Toolkit 2.0.
Did everything the steps told me.

You still haven't answered my questions...
Transmitted via Bacon

I didnt check the md5 hash but due to the tool its the right iso.
And i cant copy something out of the command promt because it closes automatically.
When i did it the command promt way i didnt even get a message that something failed.

Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon

timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.

hazefetish said:
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
Click to expand...
Click to collapse
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root. And at no point did you mention doing it yourself, you've only mentioned using a tool.
Transmitted via Bacon

timmaaa said:
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root.
Transmitted via Bacon
Click to expand...
Click to collapse
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
When i did it the command promt way i didnt even get a message that something failed.
Click to expand...
Click to collapse

Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
hazefetish said:
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
Click to expand...
Click to collapse
My problem is you came here asking for help, and then it took me asking three times over the course of 19 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon

timmaaa said:
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
My problem is you came here asking for help, and then it took me asking three times over the course of 31 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
Click to expand...
Click to collapse
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.

hazefetish said:
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
Click to expand...
Click to collapse
We can though, we can find out what went wrong by investigating. I'm trying to help you, but I need this information:
Check the md5, let me know if it matches or not.
Make another manual attempt and copy the text here.
And answer whether you've tried any recovery other than TWRP.
Transmitted via Bacon

timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
Listen to Timmaaa.... His guides & other experts from XDA-OPO forums has helped me understand a lot of things about rooting, flashing & other areas.........

Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.

skyguy126 said:
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
Click to expand...
Click to collapse
It's a nice idea, very generous, but I don't think it's the right way to go, nobody learns anything when using an automated process.
Transmitted via Bacon

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

Bricked Verizon One M8

Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.

darkhelmet46 said:
Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.
Click to expand...
Click to collapse
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.

dottat said:
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.
Click to expand...
Click to collapse
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!

darkhelmet46 said:
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!
Click to expand...
Click to collapse
Actually, I take that back... It makes the "ding" noise like it's connected, but ADB complains "device not found" when I try to run commands...

Forgot to update this. dottat helped me out earlier this week and he is indeed the man! I'm good to go!

Stuck in boot loop

My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?

Shounak Gupte said:
My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?
Click to expand...
Click to collapse
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon

drivers
timmaaa said:
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon
Click to expand...
Click to collapse
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.

Shounak Gupte said:
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.
Click to expand...
Click to collapse
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon

timmaaa said:
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.

no luck
Shounak Gupte said:
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.
Click to expand...
Click to collapse
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?

Shounak Gupte said:
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon

timmaaa said:
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?

Shounak Gupte said:
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?
Click to expand...
Click to collapse
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon

timmaaa said:
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon
Click to expand...
Click to collapse
i think i spoke a bit too soon. everything worked fine, but now my phone is getting stuck when it boots. the screen it totally unresponsive. this was the same thing which happened when i restarted my phone. it might be some app i have installed.
i might have to redo the process.
is there a way to find out which one it is?

The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.

timmaaa said:
The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.
Click to expand...
Click to collapse
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?

Shounak Gupte said:
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?
Click to expand...
Click to collapse
Did you install your apps again or is this still happening without them?

timmaaa said:
Did you install your apps again or is this still happening without them?
Click to expand...
Click to collapse
i installed them one at a time. its all the usual apps. nothing special. the phone worked fine until today morning.

I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.

timmaaa said:
I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.
Click to expand...
Click to collapse
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?

Shounak Gupte said:
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?
Click to expand...
Click to collapse
I've gone through any potential solution that I know of. I'm in Australia too, it sucks, but we took a risk when buying this phone that something like this might happen.
Transmitted via Bacon

OPO Just Reboots, around 40 to 50 times a day

Things I have tried
Flashing Factory Image
Flashing Different Roms
Using different ToolKits to restore to stock
Relocking/Re-Unlocking the Bootloader
Messing with the performance settings
Manually fastboot reflashing everything
Erasing the persist image and rewriting it
make_ext4fs /dev/block/mmcblk0p15
Flashing 25r
Flashing 38r
Flashing 44s
It does NOT work. The reboots remain the same, they have nothing to due with the CPU or heat. I tested that. When everything seems normal.... Reboot. Phone sitting by its' self? Reboot...Sometimes it will just reboot over and over for minutes. Sometimes it will go hours and then just go crazy.
I'm out of ideas. 95% sure motherboard failure of some kind.
Everyone's thoughts?

Have you tried using the phone with none of your own apps installed? Completely and utterly stock?
XDA Moderator
Transmitted via Bacon

Heisenberg said:
Have you tried using the phone with none of your own apps installed? Completely and utterly stock?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
Big 10-4 there sir. I have. Tried with no accounts a d just pure factory default. Even safe mode. It makes no difference.

What are you doing right before it reboots?
When did you first start experience these reboots?
Did you have these reboots when you just got the phone?
What modifications did you ever do to your phone? For instance, you could've flashed some custom firmware/bin file onto your phone.
What I would do in a situation like this is find out how to get back to complete stock. So I assume this includes locking the bootloader, and using CM1xS. No gimmicks, just your phone when you first got it. If you still experience these reboots, it might be a hardware issue. I'd fill in a report at Oneplus and let them do their research.
Good luck.

This is a common issue. It may lead to your phone being bricked as the partitions become corrupted due to the rebooting. Take it to a service centre and have it looked at
---------- Post added at 05:29 PM ---------- Previous post was at 05:29 PM ----------
@akhilnarang Is this what you said happened to your phone?

Locklear308 said:
Big 10-4 there sir. I have. Tried with no accounts a d just pure factory default. Even safe mode. It makes no difference.
Click to expand...
Click to collapse
Does it reboot while in recovery or fastboot modes?

No.
Is that good?
It also can run CPU tests for an hour straight but still crashes randomly after words. It is just trying to using it or also letting it set
I am going to try the coloros tool

Locklear308 said:
No.
Is that good?
It also can run CPU tests for an hour straight but still crashes randomly after words. It is just trying to using it or also letting it set
I am going to try the coloros tool
Click to expand...
Click to collapse
Well if it isn't happening while in recovery or fastboot it isn't likely to be a hardware problem, so that's a plus. Which stock images have you flashed with fastboot?
XDA Moderator
Transmitted via Bacon

Heisenberg said:
Well if it isn't happening while in recovery or fastboot it isn't likely to be a hardware problem, so that's a plus. Which stock images have you flashed with fastboot?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
Everything 25r and up except LP.
Are you familiar with this... Bulk mode?

Locklear308 said:
Everything 25r and up except LP.
Are you familiar with this... Bulk mode?
Click to expand...
Click to collapse
Bulk mode isn't good. Maybe you should head here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
XDA Moderator
Transmitted via Bacon