Database Info

[Q] rooting tablet

I was looking at rooting my tablet with this "1-click" method. has anyone actually used it? I am wondering if I should go ahead and use it on my tablet. i have a B90.

Just use thing-o-Doom's Peri
http://forum.xda-developers.com/showthread.php?t=1681155
I haven't used it but it seems to be getting pretty good feedback

So I know that I am unable to unbrick my tablet (if it were to happen.... hopefully not!). but i noticed in the documentation, it says:
"I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know. "
So if I were to brick mine, would I be able to unbrick it then? If not, is there any other way to unbrick? I know last time i checked, there wasn't, but just curious if there is now a way.

sniper8752 said:
So I know that I am unable to unbrick my tablet (if it were to happen.... hopefully not!). but i noticed in the documentation, it says:
"I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know. "
So if I were to brick mine, would I be able to unbrick it then? If not, is there any other way to unbrick? I know last time i checked, there wasn't, but just curious if there is now a way.
Click to expand...
Click to collapse
Nvflash work with SBKv2 now so unbricking is a possibility

would this be better to use here now?: http://forum.xda-developers.com/showthread.php?t=1689193
also, with the peri one, do i copy the files to the tablet, then run the .bat file from there? also, how do i prevent "any commands run at the splash screen or in recovery"?

PERI copies files to tablet for you, it's only a couple files. You just run the .bat file, it will always ask you to 'press any key to continue' or etc.. before running any commands. It's pretty straightforward :]

wow! that seemed too fast. how do i know if it did anything?

You'll now have a CWM recovery, hold volume down before (And while) turning on the TF, wait a couple seconds then press volume up when it says (Checking for RCK). You should have a custom touch recovery, which you use to install the superuser.zip to root. :]

there was a red exclamation that appeared.

You'll need to rerun PERI, make Sure to read all instructions, and that USB debugging is enabled. Probably a driver issue.

so after i run the batch file, i should see cwm? i am not seeing it installed still.

Yes, does the device show up in adb devices? (the check before the root.)

Thing O Doom said:
Yes, does the device show up in adb devices? (the check before the root.)
Click to expand...
Click to collapse
sorry; how do i check this?

adb devices...
Or peri will say Error: Device not found
Multiple times if it isn't working.
"cmd,
cd C:\Peri\folder\
adb devices"

here is what it looks like with my tablet plugged in when i run that command prompt:
http://www.mediafire.com/imageview.php?quickkey=2imqi01bcqqkv9v

sniper8752 said:
here is what it looks like with my tablet plugged in when i run that command prompt:
http://www.mediafire.com/imageview.php?quickkey=2imqi01bcqqkv9v
Click to expand...
Click to collapse
nothing under that? there should be a string of letters and numbers and which mode are you in? If you are in andorid is usb debugging enabled?

yep, made sure it was in usb debugging mode.

so i got as far as rebooting and then clearing the cache, but it just shows a droid with a warning triangle.

Why don't you use "easy flash" method to root ? All you need to do is get your tablet in APX mode and root... i did it yesterday as i was messing with kernel n bricked it. So i had to unbrick and go complete stock ICS without root, after all that i used easy flash to root and install revolver ICS rom again...
Sent from my Transformer TF101 using xda app-developers app

where is "easy flash"? and not sure what apx mode is

USB problem. Help Please. Cant root!!!

So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:

jesusroks said:
So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:
Click to expand...
Click to collapse
First of all look for drivers u can try this:
http://junefabrics.com/android/download.php
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
http://android.kcomputerzone.com/extras/Simple-Root-v1.0.zip

shivasrage said:
First of all look for drivers u can try this:
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
Click to expand...
Click to collapse
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.

jesusroks said:
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.
Click to expand...
Click to collapse
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this ?
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
read this ...install it....http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.

shivasrage said:
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this
read this ...install it....
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.
Click to expand...
Click to collapse
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'

jesusroks said:
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'
Click to expand...
Click to collapse
Also, where would I find a fresh jellybean image. How can I get cm on it

jesusroks said:
Also, where would I find a fresh jellybean image. How can I get cm on it
Click to expand...
Click to collapse
Her is a link for the JB images from google:
https://developers.google.com/android/nexus/images
for cm search the forum..

shivasrage said:
Her is a link for the JB images from google:
for cm search the forum..
Click to expand...
Click to collapse
Ok, well, I tried opening it up via command Prompt. It still doesnt recognize my phone is even hooked up. I tried manually installing the drivers, using have disk, and it said i should make sure those drivers are compatable for a 64 bit computer (which they ARE, because they were the ones I used before. Essentially, My issue is this. when i hook up my android device, when I go to (on my computer) Start> computer>Manage> Device manager... I should see android Device, Instead I see... Unknown device. I cant enter my phone via command prompt or anything. Its literally like my phone is only charging and not connected in anyway to my computer. This... really... sucks.... this is almost how i first rooted my phone. Except, then it worked.

Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End

jesusroks said:
Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End
Click to expand...
Click to collapse
Last thing you can try....
http://hotfile.com/dl/142977444/8d38a89/Downloader_v1.81.rar.html
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report

shivasrage said:
Last thing you can try....
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report
Click to expand...
Click to collapse
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.

jesusroks said:
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.
Click to expand...
Click to collapse
So my solution, in the end.
I bought a Galaxy nexus!!!!!
Such a sweet phone...........

My external speaker broke. Can you fix mine like you did yours?
Need new Android!
Sent from my Nexus S using xda app-developers app

Unable to install ClockworkMod on TF101

I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Any ideas? I'm also having an extremely hard time getting my TF101 to connect to ANY PC. Its really weird because sometimes it will work after hours of it not working...most of the time it just comes up as "Unknown Device" with an error.

If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.

frederuco said:
If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.
Click to expand...
Click to collapse
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2

polishfly said:
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Are you really rooted?
I suspect you are NOT rooted, which is why these are not working.
When you opened GooManager, did it prompt you for Root Permissions from SuperUser or SuperSU?
If not, then you need to root again.
Check out PERI or EasyFlasher to root.

polishfly said:
I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Click to expand...
Click to collapse
Razorclaw doesn't work on that firmware. Do as frederuco suggested.

I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win7 x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2

polishfly said:
I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
I used the Naked Drivers v0.72 on mine and it worked great (both ADB and APX). Did you try those?
There is also a chance it is your charging cable (it may still charge, but may not work for USB connections).

Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Sent from my MB865 using Tapatalk 2

polishfly said:
Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Click to expand...
Click to collapse
[ADB/FB/APX Driver] Universal Naked Driver 0.72

frederuco said:
[ADB/FB/APX Driver] Universal Naked Driver 0.72
Click to expand...
Click to collapse
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

polishfly said:
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html

frederuco said:
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Click to expand...
Click to collapse
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?

New USB cable on its way...but from what I have read, there has not been 1 instance where a new USB cord had fixed the exact issues I am experiencing.

Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.

polishfly said:
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?
Click to expand...
Click to collapse
Nothing happens on the tablet, that is normal, screen stays black in apx mode.
The computer should see the a usb device though. Vendor ID is 0955 (nvidia). On linux 'lspci' shows it. On windows you should see it in the device manager, maybe even tagged with a yellow exclamation mark due to drivers not being installed. If you see it there try installing the drivers using device manager.

frederuco said:
Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.
Click to expand...
Click to collapse
I tried what you suggested, but I still get no APX device to show up in Device Manager. It shows up as "unknown device" and when I try to install the APX and/or Win drivers, I get the error stating that I do not have the hardware for the drivers.

I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.

frederuco said:
I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.
Click to expand...
Click to collapse
At this point I think it could be one of 2 things...a faulty USB cable (ordered) or a TF hardware issue (its out of warranty so I'm SOL if that's the case)...worst case scenario, I'm stuck with stock since I can still boot and charge. I would love to run CyanogenMod though =(

Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.

bfmetcalf said:
Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.
Click to expand...
Click to collapse
This, if that doesnt work id go for hardware issue(although even that is highly unlikly due to it being dectect at all) ive had various issues relating to these drivers, you really need to install the naked drivers before trying to install asus sync software as i think asus software causes issues. Best option would be to install windows in a virtual machine and install the naked drivers and try again.

[Q] Do I need the USB cable to root?

Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.

bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.

It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.

Found one of the OEM chargers. $55 + shipping. Not planning to buy.

bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.

berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me

bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.

berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!

bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?

berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.

Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.