[Q] Updated to JB, and a few issues started happening... - Transformer TF300T Q&A, Help & Troubleshooting

I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.

BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?

Caduceus46 said:
I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.
Click to expand...
Click to collapse
It's a problem that some users have, and in my mind it was not resolved.
But If you want to install your recovery, you can do with TWRP recovery and Terminal Emulator app (play store)
You should search if you can make it by the same process for CWM, apparently no, cause you need fastboot.
Try this : [GUIDE] Help for flash more faster when you use Fastboot Line Command maybe you've got a problem with your fastboot. I don't know.
It's an easy installation of fastboot.

Caduceus46 said:
BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?
Click to expand...
Click to collapse
There is an option to allow ADB over network, but I haven't experimented with it. If you were adventurous, you could try it and let the community know what happens?
In the ROM I'm running (Baked Blackbean #5, Android 4.1.1 and based on CyanogenMOD) you can select this option by going to Settings-->Developer Options--->"ADB over network"
I just attempted to do this, and it worked rather flawlessly. Enable ADB over network, and it will give you the IP address of your device (in my case, 172.16.1.22:5555).
Then, follow the steps below. This assumes you have a rooted device. To do the terminal commands on my tablet, I use the "Terminal Emulator" program, free from the Market.
This is really simple.
First make sure you are rooted. Download a terminal emulator from market (there are lots that are free). Make sure that your android is connected to your WiFi and get the WiFi IP address. Open the terminal program and type:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Now go to your computer (assuming that you are using windows) create a shortcut on the desktop for "cmd.exe" (without the quotations).
Right click on the cmd shortcut and choose "Run as Administrator"
Change to your android-sdk-windows\tools folder
Type:
adb connect ***wifi.ip.address***:5555
(example: adb connect 192.168.0.105:5555)
adb should now say that you are connected. Note: if you are too fast to give the connect command it may fail. so try at least 2 times 5 seconds apart before you say this doesn't work.
Click to expand...
Click to collapse
To put the device back to USB, once you get it working (because ADB over network is NOT SECURE):
And you can disable it and return ADB to listening on USB with
setprop service.adb.tcp.port -1
stop adbd
start adbd
Click to expand...
Click to collapse
Got this information from: Here
I do want to note that all I did was verify that ADB is detected over wifi. When I type 'adb devices' on my Windows 7 PC, it detects the IP address of my tablet, which indicates the two devices are communicating correctly. I didn't try pushing/pulling files since I have no need for that, but hopefully this helps you.

I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:

philos64 said:
I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:
Click to expand...
Click to collapse
Thanks!!
Sent from my Transformer Pad TF300T using xda app-developers app

@opethfan89, ADB over network will probably not work for me because I don't have root anymore. Appreciate the help :good:
@Philos64, thank you for your post as well. I will try that sometime this week and let you know the results as well.

Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either

Caduceus46 said:
Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either
Click to expand...
Click to collapse
Perhaps I'm wrong, but you don't need root to be able to flash a custom recovery, since the recovery operates outside of the Android OS (and root only affects app permissions within the OS). You would just need fastboot to be able to flash the recovery. Do you have the proper drivers installed on your computer? Can you try different USB ports? Maybe a USB hub? Try it on a different computer to, just to process of eliminate any kinks between the tablet and the physical connection of the USB cable.
Sent from my Transformer Pad TF300T using xda app-developers app

Related

no ADB connection anymore

ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "ADB devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
shouldnt it be adb devices instead of dab ?
I wanna try this ABD but there no link?!!
Shouldn't this ABC post be somewhere else?
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
sheetmetalninja said:
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
Click to expand...
Click to collapse
You're right.
But I also don't know anything about BAD or FASTBOOB or anything like that. I don't like reading. :[
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Check the drivers, you may need to update them
Sent from my Desire HD using XDA App
taney said:
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Click to expand...
Click to collapse
how 2 do that? i mean what do you mean with devmgmt.msc(device management...?)
1) usb cable is good, the original one. also tried different usb cables, it doesn't matter.
2) usb port is also ok, other devices running out of the box (f.e. dvd drive oder dslr)
3) adb driver already updated via "Android SDK and AVD Manager".
i installed Android SDK tools, SDK Platform tools, sdk platform (--> is there sth. missing?)
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Romanbb said:
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Click to expand...
Click to collapse
no sorry...won't work..
getting the same:
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
also tried without fastboot rebooting.
there are news guys:
just got an windows 7 personal computer for a couple of days.
installing the sdk and usb driver just worked fine.
why it doesn't work for mac?
already installed all new...
You may also check the cable you're using to connect the phone to your Mac. I was getting the same problem when trying to use the cable from my car charger - the phone was not even visible on the system list of USB devices. Using the cable that came with the phone did the trick.
(although if you used the same cable with Windows and it worked, my hint won't be of much help)
Do you got HTC sync installed on your PC?
TheStigx said:
Do you got HTC sync installed on your PC?
Click to expand...
Click to collapse
please remember - i'm using a MAC!
so finally i tested my device with several computers at the university.
i just found out, that the problem may been caused of my installed mac osx lion - but don't ask me why!
on the mac of my prof (also osx lion with latest updates) it worked out of the box...
--> so i'm gonna making backups now and will format my hard disk and reinstall lion again.
i'll give u feedback again ;-)
Have you closed the htc-sync application? solved the connection-error for me...
Maeffjus said:
Have you closed the htc-sync application? solved the connection-error for me...
Click to expand...
Click to collapse
again guys:
I'm using a MAC!
is there any official sync app for mac i don't know about??
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
yasinis said:
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
Click to expand...
Click to collapse
ok, just found out where the problem was caused. it was EasyTether!
this will help:
Code:
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext

[ROOT][TOOL]Qemu automated root [09/18/2012]

This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Latest Supported Versions:
v7.1.5
Recent user reported supported version
v7.2.1
Awesome, want to try it when I receive my HD 7 this week...
Wrong thread sorry about that
Works perfectly. Thank you!
Sent from my KFTT using XDA Premium HD app
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
padest.com said:
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Click to expand...
Click to collapse
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
reverendkjr said:
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
Click to expand...
Click to collapse
Thanks.
I get it.
ADB is unresponsive
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
Click to expand...
Click to collapse
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
Interesting, I don't even have that file. I assume it is used to block devices so you could have one plug in for charging and ADB would just ignore it if it is not in the list.
Thanks, sparkym3
After I verified that ADB could see the KFHD7, I ran the 'RootQemu.bat' that was part of what you published. While it took a bit of time (about 1 minute) between reboots, it worked flawlessly. The Kindle Fire HD 7" I have is now rooted. I'll be looking next to replace the launcher, (probably Apex) and scrape the ads off of this.
Pat
Thanks
Thank you so much for this... really makes it easy and fast. However i was worried during the installation haha my device kept rebooting and it warning me to reconnect so i thought i was doing it wrong.
Well it seems that I messed up. Big time.
I got to step 3, and that's where all hell breaks loose. I get message on the cmd window which reads Cannot find specified file, and everything goes downhill from there. There's no more updating whatsoever. But that's not the bad part, I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad. I'm in process of resetting everything to factory default at this moment.
EDIT: Just reset to factory default, everything is smooth again, but be careful when trying this exploit, things can go wrong!
I'm thinking there was something I did wrong, if this seems unfamiliar I'll list the steps I took in trying to manage everything. But I know you're thinking I did this on impulse, hence my low post count, but I have been lurking the kfhd subforum for a very long time now and have tried my best to educate myself. Sorry.
Vespus said:
I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad.
Click to expand...
Click to collapse
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
I tried running the tool and it kept getting hung up on step 3, telling me something along the lines of file not found. I was able to root using the manual method though.
nvrmore100 said:
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
Click to expand...
Click to collapse
I suppose my method fixed it regardless
I'm thinking the reason my root backfired is because I wasn't as systematic as I should have been. Rooting my samsung vibrant allowed me to be a little more sloppy since there are backups and flashing is a cinch.
EDIT: This my 3rd time trying to get this thing to work, I get stuck on Step 3 "The system cannot find the file specified."
I really can't see how I'm managing to screw up this badly. Must be something stupid on my part.
EDIT2: Turns out I was using a crumby network directory the whole time, but even still it did not work. Fellows: Put the QemuRoot folder somewhere on your desktop, it's easier there. But after that the prompt would close immediately after step 4, so that took me a while to circumvent. Anyway, I ended up skipping to step 4 to get the superuser to work. I'm fairly sure everything DOES work, but it's hard to test right now.
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
That's right! I have tested!
This is needed!!!
Thank you for work and contribution.
Thanks for the tip
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
worked!
KF HD has Superuser but no root access
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3
Thanks for all your hard work! I tried it though and it went through all the motions as if it was doing its job, like expected. But at the end of the rooting, I have superuser on the kf HD but no root access! ES explorer and Titanium have no root access. Tried rebooting several times. Still no root access. What could have gone wrong?
Cheers, mate!

[Q] TF101 usb dosent't get connected to linux and windows...

Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
joevirus563 said:
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
Click to expand...
Click to collapse
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
hapahopi said:
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
Click to expand...
Click to collapse
Its already at MTP...
Any way to root without computer?
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Happydondavid said:
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Click to expand...
Click to collapse
Ok and whant have you done to fix it?
New usb cable?
I've not managed to fix it yet . When i plug my TF into my pc it seems to think its charging but the pc doesn't register it at all , if i get a new usb cable and it works i'll report back .
Well does anyone know if this is a problem with the cable or not ?
Happydondavid said:
Well does anyone know if this is a problem with the cable or not ?
Click to expand...
Click to collapse
I have the same problem. I sent my tf101 to the Asus service center to have it repaired. When it came back it would connect to the PC. After a few months it would not connect. Same problem. It appears to me to be software related somehow. In my case the cable has nothing to do with it. None of the suggestions on this or other forums work. Asus does not respond. Maybe Jelly Bean will fix it. Or maybe not.
are you able to ./adb connect to the asus via usb? if so then that will tell you that the problem is not the cable, it's not the usb version, it's not the device hardware. its likely a driver install issue in windows. i would boot into android and make sure that android debugging is selected in the developer settings menu. then try an adb connection. im not sure about how to install all the stupid drivers in windows because i do everything in linux and its soooooo much simpler.
f it is in fact the hardware cable or port that is not working properly then you can always move files to and from the device over wlan connection, with either adb tcp connection, or using some file manager such as es file explorer. just remember as long as you can get an
./adb connection to your android then anything is fixable. ADB IS YOUR FRIEND. get to know it well.
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
qandrav said:
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
Click to expand...
Click to collapse
I dont ever connect my devices as mass storage to he computers at all. i just do everything via ./adb usb or ./adb tcp connections over wifi. or i use es file explorer setup as an ftp server on my devices and move files around that way if i need to. but i went ahead and pulled out my windows asus tf101 drivers and sync app and linked them for you at the bottom. my advice really is to lose windows and stick with doing everything on android with linux. soooo much better.
https://www.box.com/s/q2j8n7h8xi5o3ld2bt5z
thank you for your long reply! and obv for the files, I'll give it a try!
I admit that sometimes I used swiftp (over wifi) but every time I have to disconnect pc & tablet from the modem...Sometimes use bluetooth but it's too too slow!!! thank you again!!!
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
when I rooted moths ago I used "razorclaw" (and my tf101 is a b70). I use adb with other devices and is very cool but I never need to use with the tf101...
joevirus563 said:
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
Click to expand...
Click to collapse
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
The Real Question when USB does not connect.
haxin said:
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
Click to expand...
Click to collapse
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
beware of usb cable
Hi,I personnally own a TF101 sb50.
I had some trouble with usb. Tha cable was ok for charging but didn t register correctly under an usb connection ( it showed up and got kicked out in windows didn t register in lsusb on linux)
If you check the diagram for the cable, it s well endowed there 's resistance inside the cable, and multiple connection.
Depending on your version it doesn t use the same pin, even if it's the same cable.
You can buy a cable on ebay for around 10 euro in europe ( i did it s ok) or buy it cheaper from china(no idea about quality).
to sum it up even if your cable work with another TF, it doesn t mean your cable is not faulty ( i have bounce a nano osci on the faulty cable , and it showed no apparent flaw.) and buying a new one was the solution for me.
good luck for rooting (sb50 :: no need to adb)
The ADB thru WiFi solution worked perfectly for me thankfully, and I am one of the many others who have been having major trouble getting Windows and Linux to recognize the Intercept.
Not sure if this is a duplicate post somewhere, but here's my version using Linux:
1. Go to the Play Store and download the 'ADB over Wifi Widget' app.
2. After installed on your device, the app should be on your home screen. Tap it once to toggle on. You should see an IP address and a port #.
Note the IP address, as this is the address of your device.
3. Open a terminal in Linux.
4. CD to the folder that contains your ADB files. (example: cd /androidsdk/platform-tools)
5. Enter the following code:
chmod 755 ./adb
./adb connect <enter IP address here without brackets of course>
6. You should now be connected to your phone.
Hope this helps...
pm124493 said:
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
Click to expand...
Click to collapse
ok when you say that the tf101 doesnt connect in either your windows or linux machine, what do you mean exactly? you mean it doesnt show up as a mass storage device or an MTP device? and have you downloaded and installed the android-sdk in linux? and when you connect the tf101 to your linux machine, do yo uhave usb debugging enabled in the developer settings menu, and are you using the "./adb devices" command in the linux terminal from your /android-sdk/platform-tools/ directory?
also you should be able to flash a custom recovery which will enable you to flash custom rom without using the usb cable. theres a couple files that you need to put on your tf101 in the /sdcard/ directory first.
one is the recovery blob and if you want to keep the stock rom and kernel but just root it then youll need the superuser zip i have included both of them at the bottom.
for starters you need to install a terminal emulator app on the tf101 from the play store.
then once you have the recovery blob on your device in /sdcard/ you can continue. (remember /sdcard/ is the internal memory not the micro sd card)
start the terminal emulator on the tf101 and enter these commands.
mv /data/local/tmp /data/local/tmp.bak
exit
(open another terminal window on the tf101 and enter these commands)
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
(now reboot the tf101 when it boots into android start the terminal emulator app again then enter these comands)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
exit
(now you should have a team rogue recovery flashed to your tf101)
reboot your tf101.
now you can hold the vol -down button while you power on the tf101 you will see a message at the top of the screen that says soomething like "Checking for RCK" when you see that press the vol- up button right away, this should boot you into the team rogue recovery where you can flash custom roms or just flash your superuser.zip to get root.
hopefully this makes sense and hopefully it works for you.
remember you have to extract the recoveryblob from the zip folder before you move it to the /sdcard/ on your asus. the superuser.zip can remain zipped though.
I had the same problem:
windows will not notice my transformer (rooted).
( usb debugging is on, android 4.0.3 with Android Revolution HD 3.5.1.)
i know in the past it works.
adb list ( of devices) ist empty also. Same Problem with the two cables i have.
can you give me a help what i can do?
Sorry for my poor english
kind regards
gandalf

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.
very interesting Hashcode,thanks for the information :good:
Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now
Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed
dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!
You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

[SOLVED] Anyway to root HP slatebook x2?

I've had the tablets for a few weeks and would like to root it. It has android 4.2.2 but doesn't have an option to connect to pc as it doesn't have a micro usb port on the tablet. The charging port is proprietary and uses a AC adapter style cord similar to a laptop one so it doesnt have a usb end. Am I just SOL?
UPDATE: see post #8 by groumfi
UPDATE 2: thanks to member Taiz for the info. You can now root using an app found at www.towelroot.com No cable required
I returned mine a long time ago but this is good news regardless
Sent from my HP SlateBook 10 x2 PC using Tapatalk 4
Anyway to root HP slatebook x2?
aznmode said:
I've had the tablets for a few weeks and would like to root it. It has android 4.2.2 but doesn't have an option to connect to pc as it doesn't have a micro usb port on the tablet. The charging port is proprietary and uses a AC adapter style cord similar to a laptop one so it doesnt have a usb end. Am I just SOL?
Sent from my HP SlateBook 10 x2 PC using Tapatalk 4
Click to expand...
Click to collapse
Hello,
Apparently these two pages present two procedures for root any android by the sole procedure that allows currently Slatebook: recovery> apply update from zip (only root, no kernel or rom change):
Someone has tested or can test?:
http://forum.xda-developers.com/showthread.php?t=2358996
http://forum.xda-developers.com/showthread.php?t=1746794
Greetings
Daifex said:
Hello,
Someone has tested or can test?:
Greetings
Click to expand...
Click to collapse
Thanks for that, mate. Looks like that someone has tried this but it doesn't work.
Alternatively it has been suggested that root access can be gained from the updated file from HP: http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=4153&product=5400087&sw_lang= but unfortunately I'm not a developer nor technically inclined so I wouldn't know how to extract it. However the file is available from the above link if someone know how to grab and tinker with it.
GrievousMcG said:
Thanks for that, mate. Looks like that someone has tried this but it doesn't work.
Alternatively it has been suggested that root access can be gained from the updated file from HP: http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=4153&product=5400087&sw_lang= but unfortunately I'm not a developer nor technically inclined so I wouldn't know how to extract it. However the file is available from the above link if someone know how to grab and tinker with it.
Click to expand...
Click to collapse
a few of us are anxiosly waiting for this great tablet to get root access. I think the only way to motivate senior xda developers to buy this tablet would be if Hp drop off the price to $299.
gdfrisco said:
a few of us are anxiosly waiting for this great tablet to get root access. I think the only way to motivate senior xda developers to buy this tablet would be if Hp drop off the price to $299.
Click to expand...
Click to collapse
hoho....how much we must wait that? One year? two?
we just need to get HP signature to sign update.zip file...
some informations
Here is the detail or the official OS that we got with the slatebook 10 x2 :
Android version 4.3
3.4.57-g61ce4c9
[email protected] #1
Wed Dec 11 00:41:15 CST 2013
Build number
4.3-17r20-03-23
Many of us can not connect dirrectly the device to a PC. So it will be better to root it with usb flash drive or a SD Card but an apk like Framaroot would the best. I'm posting this to help anyone trying to make this for all slatebook users. There is still hope people!
Hp still don't give us the ability to purchase a usb wire. The. French clients service said that no wire is available. There is still hope to find other devices with the same kind of proprietary port but the next problem will be to find a device with the same kernel.
Envoyé de mon C5303 en utilisant Tapatalk
How to unlock and root HP SlateBook x2
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Edit 23-Aug-14 : I flashed it thru Flashify and it boots. I also installed Quick Boot (Reboot) to easily reboot to recovery. Only issue is that it does not mount internal storage, but with external SD, I was able to perform a Nandroid backup-restore operations
Quick question please ref your post
I have received the cable you mentioned (HP 728141-001) and although it connects, the LED on the cable does not illuminate. Does yours light up? Cheers.
groumfi said:
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Click to expand...
Click to collapse
ericritou said:
I have received the cable you mentioned (HP 728141-001) and although it connects, the LED on the cable does not illuminate. Does yours light up? Cheers.
Click to expand...
Click to collapse
No, no lights
Finally received the cable too! Not going to root it now (but thanks for the procedure!).. I really just wanted an ADB connection.
Some notes:
1. You have to connect the cable to the tablet itself not the base (stupid but took me some time to figure this out as I never use it without the base).
2. I can't get the driver to work on Win7 (device not recognized even though I can see the files), but it works on Ubuntu.
3. You do have to edit the usb_adb.ini and *then* connect the cable, normally you should have an authorization on tablet. Don't do "android update adb" as it wipes the ini file.
4. The light does not seem to ever light up, actually I don't even think it's a light, maybe it's just something to show which side goes up...
Jerem
Well thankx for setting up the guide. Since I'm EU spain I'll try to get a hold on one of those usb cables. Really want root for fps meter and TinyCore I think it's called. It would compliment my gaming on the device very well.
Maybe a stupid questions......
When using this expensive USB cable can you charge the tablet also with it or is it only for USB communication?
B3rt said:
Maybe a stupid questions......
When using this expensive USB cable can you charge the tablet also with it or is it only for USB communication?
Click to expand...
Click to collapse
Definitely not a stupid one. You can NOT charge the tablet, it is only working as a data USB cable
groumfi said:
Definitely not a stupid one. You can NOT charge the tablet, it is only working as a data USB cable
Click to expand...
Click to collapse
No charging yet, but HP is working on a 99$ cable that will do the charge of the tablet too :laugh:
Does someone know if some custom roms developpers are interested with the Slatebook ?
It's a pity at this time because we can not clearly see the end of the tunnel... Not rooted mine because I just don't want to miss the 32Go internal...
Popol640001 said:
Not rooted mine because I just don't want to miss the 32Go internal...
Click to expand...
Click to collapse
Do you mean due to the factory reset done when unlocking bootloader ?
groumfi said:
Do you mean due to the factory reset done when unlocking bootloader ?
Click to expand...
Click to collapse
No my friend, I don't have important data on the internal 32 gigs, so no problem for me that the factory reset delete all the datas.
I mean that I don't want to "lost" this internal memory which is usefull for install applications (because this internal memory isn't well recognized no ? or I don't have well understood...).
Popol640001 said:
No my friend, I don't have important data on the internal 32 gigs, so no problem for me that the factory reset delete all the datas.
I mean that I don't want to "lost" this internal memory which is usefull for install applications (because this internal memory isn't well recognized no ? or I don't have well understood...).
Click to expand...
Click to collapse
Ah, okay, I see what you see.
No risk to loose the internal memory: it is still there once the tablet is rooted.
Issue I was mentioning about "no way to see internal memory in CWM" meant that when you boot CWM (the recovery), it does not see the internal storage. That the reason why, you have to sideload the SuperSU to flash it.
Then, once rebooted (and rooted), internal storage is visible as usual from Android
I would like to fix it into CWM so that we would them have a 100% usable and flashable CWM. Very useful then for flashing other zip that you should copy to internal storage and/or perform nandroid backups to internal storage.
So, you can safely root your device with the method (just be prepared to have the device reset to factory default due to unlocking bootloader)
Cheers
Just found it on Google
Sent from my SM-N900T using XDA Free mobile app
Problem with adb_usb.ini
groumfi said:
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Click to expand...
Click to collapse
Hello,
Thanks for your work. I'm running on windows 8.1 and can't find adb_usb.ini ... I've only two files adbkey (1 File type and 1 Publisher type).
I've trying to install the minimal_adb_fastboot program on two differents pc but I obtain the same results...
I've a macbook pro but I don't know if it's possible to use it to unlock and root my HP slatebook x2 and how to proceed.
Thanks for your help

Categories

Resources