Database Info

[Q] Ultra-newbie: Help! tf3oot stuck bootloading; locked & unrooted.

Progress circles keep circling til battery dies. Coldboot didn't work. (Although Asus said I shouldn't try android icon.)
Don't want to wipe data if I don't have to because I was in the middle of backing up data when it got stuck (can I connect it to my 2 1/2 yr. old laptop to copy files I need?)
Have all updates except last one two weeks ago. Not under warranty.

hi
Try to connect it to PC when you turn it on..if your computer recognized it...other wise no way to copy data as far as i know..(I am also not a PRO).
For your tablet to boot again i think go into recovery and then wipe everything and it ll re format your tablet then it should be in factory condition.
If this dosent works try my guide see the first posts in here u ll find it!!..
Hope u ll recover it!

You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.

Can't Find adb download link
UndisputedGuy said:
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto

pjspener said:
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
Click to expand...
Click to collapse
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.

How to find Link to sdk with adb
UndisputedGuy said:
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Forgive my ignorance. That link didnt lead me to an sdk with adb in the directories, which sdk do I use?
Also, I cant figure out how to get a list of the guides on this forum or all forums.
Thanks!

If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.

adb devices command didnt work
UndisputedGuy said:
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
Click to expand...
Click to collapse
"adb devices" didn't work for me either, how did you make it work? I'm in the same place you were.
Also are there separate adb drivers?
Thanks

Jacked myself up - help please

o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S

you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer

meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.

bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.

So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905

aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?

RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.

RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.

Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.

I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.

I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).

Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app

Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.

TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5

Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk

Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.

Glad you got it sorted.

Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.

Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?

Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.

Bricked my device

Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?

Just wrote a thread about adb. Click link in signature then look for section 1
Sent from my Nexus 5 using Tapatalk

spluxor said:
Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?
Click to expand...
Click to collapse
Google 15 second adb drivers xda. It's probably in rootSu's guide. That'll set up the adb you need
Sent from my Nexus 5 using XDA Free mobile app

It is indeed
Sent from my Nexus 5 using Tapatalk

I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!

spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement

bitdomo said:
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement
Click to expand...
Click to collapse
That was already told in my thread.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------
spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
Well, you need to fix that.
If you want help please explain in detail your issue
Sent from my Nexus 5 using Tapatalk

Well the good thing is that I unbricked it, by following How to Unbrick or Unroot the Nexus 5 (incl. Tamper Flag Reset) on YouTube by C4ETech, the bad thing is that I have to install everything again, but okay my fault
Anyways guys thanks for help !

If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.

vanessaem said:
If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.
Click to expand...
Click to collapse
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.

rootSU said:
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.
Click to expand...
Click to collapse
By that term, anything nonrecoverable can be considered a brick which is still more accurate than a device being bricked or software bricking a device yet it can still be turned on and/or charged.
Anyway, I say all that to say to the OP and all who think they are bricked, all is not lost if your device functions at all.

ADB / Fastboot / Driver problem

Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!

Follow the next step on my thread and install the naked drivers

Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?

Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader

EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!

Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section

To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.

Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.

Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!

EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!

Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device

EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.

Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general

rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat

Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.

[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.