Database Info

[Let's Get] Root Achieved for Le Pan II (TC979)

JCASE HAS DONE IT GUYS:
http://www.forum.lepanlife.com/showthread.php?tid=322

No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037

rocketero said:
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
Click to expand...
Click to collapse
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.

Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.

PresidentMcCain said:
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
Click to expand...
Click to collapse
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.

dbaybay said:
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
Click to expand...
Click to collapse
Maybe this will help you with ADB drivers:
http://rootzwiki.com/topic/15624-how-tocm9-adb-interface-on-usb/
---------- Post added 24th January 2012 at 12:15 AM ---------- Previous post was 23rd January 2012 at 11:50 PM ----------
If you can at least use Root Explorer to zip up some of it, it'd be helpful
(I believe the drivers are .so files in the lib folder under /)

dbaybay said:
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Click to expand...
Click to collapse
I just downloaded again the link for "Drivers" and I connected the Lepan2 again to the computer and the same problem as before.
Then I checked the "File hashes" for the files "WdfCoInstaller01009.dll" and the other 2 inside the folder "amd64" and the cr32/md5/sha-1 are identical for the ones I had downloaded before and this ones. So where are the new ones you said you re-uploaded ?
About the ROM, I am also interested on obtaining the "original" ROM that came with the LepanII, as I updated the system with a still-in-development that Lepan tech support had uploaded to the server without even first testing it, and now I can not revert back to the original because they have not provided to me in a support-ticket I opened at their website. I don't know much about ROM extracting or management but I could learn a thing or two about it.

WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!

There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.

rocketero said:
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
Click to expand...
Click to collapse
Been there, done that. Hopefully you'll have better luck, but their standard reply is to email two people from HQ if you are a developer, which I've also been there and done that. They don't reply. I'm fairly positive that we are on our own considering they didn't release the ADB drivers for the LP1 or LP2 as of yet and no source code for either, either. They are GPL-violators to the MAX. *puke*
We'll get it tho.

dbaybay said:
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
Click to expand...
Click to collapse
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.

ghuron said:
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
Click to expand...
Click to collapse
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.

dbaybay said:
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
Click to expand...
Click to collapse
I thought adb pull /system/lib/ does not require root

ghuron said:
I thought adb pull /system/lib/ does not require root
Click to expand...
Click to collapse
Nor did I, but I'm getting permission denied for about everything except adb reboot [recovery / bootloader] or 'ls'. SU, Pull, Push, Root, Remount, etc. etc. etc. are giving me "permission denied" or "can't in manufactor mode" errors.
I'm working on getting it to work in Fastboot, but ADB just won't recognize the device in Fastboot no matter what I do. I'm at a loss right now, so any suggestions would be helpful. I'm gonna keep trying different methods to get ADB to work with root permissions.
Code:
$ pull /system/lib c:\users\admin\desktop
pull /system/lib c:\users\admin\desktop
pull: permission denied
$
A list of the contents is the best I can get for you atm - http://pastebin.com/ZqvXqE0Q

Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?

PresidentMcCain said:
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
Click to expand...
Click to collapse
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.

dbaybay said:
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
Click to expand...
Click to collapse
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Edit: never mind, the reset button worked

anonguy2 said:
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Click to expand...
Click to collapse
Try holding power button + home button at same time for 10 seconds.

Bootloader/fastboot are the same thing from my understanding. When I use adb reboot bootloader, it reboots to my fastboot screen. I use the reset button, as you figured out to get out of it.
I need to get adb or fastboot.exe [platform tools] working in fastboot mode and I should have root access but no such luck.
Any Le Pan II users who managed to get the v116 update - did you get an update.zip placed on your SD Card that you can share? If I can get an properly signed update.zip with the stock ROM inside, I can most likely modify it for with SU access built in.

this may be a stupid question, does this app http://www.androidapps.com/finance/apps/299480-root-explorer-file-manager-speed-software give you root access or do you need to have root permission in order to use that app.

Frequently Asked Questions for Asus Transformer TF300T Thread

Welcome to the Frequently Asked Questions for your Asus Transformer TF300T
Click to expand...
Click to collapse
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd post, be sure to come back here and read some more. It will help you to learn even more.
​
Click to expand...
Click to collapse
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most, and we need your help for a good FAQs​
Code:
[B][CENTER]
[B]1.[URL="http://forum.xda-developers.com/member.php?u=4518416"][B][COLOR="Blue"] - QuantumFoam[/COLOR][/B][/URL] who is the chief editor of the FAQ
2. - [URL="http://forum.xda-developers.com/member.php?u=2559267"][B][COLOR="Green"]tobdaryl[/COLOR][/B][/URL] - Help provider
3.
4.
5.[/B][/SIZE][/CENTER][/B]
​
Asus TF300 Moderators
Click to expand...
Click to collapse
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - babijoee, chrisd1a1, Divine_Madcat, GODZSON, Moscow Desire, zacthespack . If you have any questions about this forum in particular then feel free to drop them a PM or you can use the button report
XDA In General
Click to expand...
Click to collapse
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Asus TF300T links further down this post.
The first of all is the Forum Rules, which is the first thread that you must read and implement for taking good time here
The XDA Tour and Report Posts
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
ASUS TF300T Helpful Links
Click to expand...
Click to collapse
- [INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
- [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]
- (TF300T)For All Your Jelly Bean discussions-problems
- (TF300TG)For All Your Jelly Bean discussions-problems
- Small guide for Install recovery and rooting when you are already to JB
- [GUIDE] Help for flash more faster when you use Fastboot Line Command
- How to install Universal Naked Drivers
In post 2 there'll be an FAQ which will help you out aswell
And don't forget to rate for this thread -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance

Reserved for FAQ

Reserved again

Reserved again

Aaaand I'll take #5

USB ADB Drivers (both OS and Recovery modes)
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks

fuzzynco said:
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks
Click to expand...
Click to collapse
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!

sigh MTP works but ADB doesn't
tobdaryl said:
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Click to expand...
Click to collapse
can'tn test fastboot yet, but guessing when one work both will.

fuzzynco said:
can'tn test fastboot yet, but guessing when one work both will.
Click to expand...
Click to collapse
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer and you will either see asus adb interface or maybe a driver failure. Either a larger screen capture or try to explain the changes in device manager is needed.
It would be good if I knew the state of your tablet while you are doing this.
My screenshot for adb (at the top ) and data at the bottom.

followup: tf300 adb drivers?
tobdaryl said:
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer
and you will either see asus adb interface or maybe a driver failure. Either a larger screen
capture or try to explain the changes in device manager is needed. It would be good if I
knew the state of your tablet while you are doing this.
Click to expand...
Click to collapse
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
http://support.microsoft.com/kb/943104
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks

fuzzynco said:
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks
Click to expand...
Click to collapse
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!

progress ADB for JB works, ICS doesn't.
tobdaryl said:
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!
Click to expand...
Click to collapse
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks

fuzzynco said:
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks
Click to expand...
Click to collapse
It is very possible that adb will not work properly on ICS unless it is unlocked. I can't remember but would say it is very likely since JB does work and both use the same drivers. In two days I was unlocked, on the latest JB, twrp installed and waiting for a non stock based rom.
There are some differences between JB and ICS. I received ICS input from wha2do concerning methods of entry into apx and bootloader while I was gathering info to update my thread. Here are the ones we identified.
or - no need to hold volume with these
8. adb reboot bootloader
or
9. fastboot -i 0x0B05 reboot-bootloader
or
10. from terminal - you must be rooted for this to work
su
reboot bootloader
Note 1: If you have nvflash installed some of the commands presented in this post may not work; possibly 8, 9, and 10 - THANKS TO wha2do for this info!
I need to update my info to: If you have ICS or Nvflash.
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.

OK - 1st try will be unlock and attempt adb again
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.
Click to expand...
Click to collapse
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works

fuzzynco said:
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works
Click to expand...
Click to collapse
Good list and order. I'm always in favor of getting adb and fastboot working properly before going forward. If you experience problems you have done everything possible to give yourself a path to recovery.
Let me know If I can help further.
Good Luck!
Be positive! It's going to work!
Just take your time and try to stick to your list.
Note: do not use WIPE DATA on the bootloader menu!!!

Note: do not use WIPE DATA on the bootloader menu!!!
Note: do not useWIPE DATA on the bootloader menu!!!
Click to expand...
Click to collapse
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.

fuzzynco said:
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.
Click to expand...
Click to collapse
+1
Thanks for the explanation.

how to unlock bootloader please?
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q

quantum3 said:
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q
Click to expand...
Click to collapse
Quot from Asus: ※This tool now only works with TF300T ICS & JB of TW,US,WW CN SKU. It won’t work on other devices.
Register your unit with Asus, log into play store, run the unlocker. The bricks I have seen unlocking have been caused by WIPE DATA on the bootloader/recovery menu. Never use that!
Note: I failed to add this link earlier. This is good simple directions for unlock.

I'm not sure how to search for my problem, but I can try to describe it
all of my root directory has been moved into a folder called 0, and now there are just some random folders in the new root directory
I recently unlocked my bootloader and flashed twrp, and I made a recovery image at that point.
Then I flashed CM10.1
Then I decided not to use CM10.1 , so i tried to restore from the recovery image
So now thats where I am, and I am trying to root it now.
The default root directory that i had previously placed the CM10.1 zip is in the folder 0, and it wouldnt read any zips i placed in the regular root directory.
So if i place the root-signed zip into the regular root directory, it doesn't read it.
It does read it if it is in the same directory as the CM10.1 zip, or the folder called 0
I flashed the zip, and it didnt seem to do anything.
I may have not done a certain step during the recovery or restoration process, but I was pretty sure to wipe cache before flashing stuff, and I reset to factory before flashing CM10.1
So the main problem I am having now is that I am unable to be rooted.
Im sorry this is horribly worded >.<
any help would be greatly appreciated!

[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

[Q] Problems while updating drivers

Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !

Chyquito said:
Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !
Click to expand...
Click to collapse
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....

...

playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?

Chyquito said:
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?
Click to expand...
Click to collapse
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve

playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
playya said:
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve
Click to expand...
Click to collapse
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...

Chyquito said:
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...
Click to expand...
Click to collapse
OK with android and rooting following instructions is key. By your response you did not follow all the steps. Please follow each one to the letter
There are more steps for you to do after a reboot

ASUS ZenPad C 7.0 (Z170C - P01Z) - Working Root Method

Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All credit lies where it is due.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all you guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you. This guide has been reported to also work with the Z170CG and Z370C tablets, in which case owners of these tablets can attempt this method but with caution. Beware, this method has not been tested by myself and prepare yourself for the event of a brick.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
UPDATE: A quick update for all you guys on what is currently happening.
v1.0.2 - Minor update, grammar corrections.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.

Success!

With latest updates on my device tried and it works thx for great job

great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.

Asus p01z z170c tablet rooting access /custom recovery anyone?
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Thanks for all your work and research. I must wait till I'm home and try this method out! Has anyone been working on a custom recovery for this!? Thanks again!

hayabusa_gsxr said:
great job AwesomeLewis24.
I complete all steps and the device Z170CG ( p01y) boot into normal mode without any root rights.
After repeating the method, device is hanging on asus boot screen and even factory reset not helped.
Fortunately i was able to flash stock rom and device turned on and now working normally again.
wish me luck, i'm going to try rooting again.
Click to expand...
Click to collapse
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
Good luck buddy! If you could, do you mind sharing where you got the stock ROM from? This could come in handy sometime...
Also, @totalppl so far there's nothing in terms of custom recoveries or the such for this device. Maybe I'll see if there's any chance of an available TWRP port I can port over from a fellow x86 asus device. Until then, this is as far as we have gotten in terms of dev support.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
This (as it stands) is much appreciated.....
No need to hurry on the recovery front...
Root (for me at least) is the important bit....being able to use TiBu to get rid of the bloat.....that's my priority.....
http://i.imgur.com/rVnFwJM.jpg

@keithross39
Can confirm for me that the majority of the bloatware has been successfully removed and the tablet runs much cleaner now.
Thanks for the messages guys, but like I said credit is where it stands to the guys who found the root.
Sent from my Moto G 2014 LTE using Tapatalk

http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.

@hayabusa_gsxr
Thanks for the link, I've been searching on ends for stock ROMs for this tablet. It's been stressing me out! 4pda has been a good forum to us Zenpad users.
Other than that, maybe I'll link that in the top forum post, just in case worse comes to worse.
Sent from my Moto G 2014 LTE using Tapatalk

hayabusa_gsxr said:
http://4pda.ru/forum/lofiversion/index.php?t679135-1600.html
Here is the stock rom.
rom flashed using the official rom(there are 2 roms 1GB and 2GB, i'm using 1GB version,don't know the difference) and boot from sdcard.
Click to expand...
Click to collapse
Just to confirm.....what is the exact process for flashing these firmwares?
tia.....Keith
http://i.imgur.com/rVnFwJM.jpg

Thank you very much, working 100% in my P01Y.
Please share if you know about custom roms for this tablet.

Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs

chrisupi007 said:
Having root is amazing, I created a bootloader already:
https://youtu.be/H5eXCwYpRvs
Click to expand...
Click to collapse
Nice work! Awesome to see how we are slowly but steadily finding out and developing more and more for this nimble tablet.
Sent from my Moto G 2014 LTE using Tapatalk

Need a little help
AwesomeLewis24 said:
Forenote: Root has finally been achieved for us on the Asus Zenpad C 7.0! Special shoutout to @InvisiBot (source) and @b0joker (source). Not only that, but also to the Russian 4pda forum where the root process was brought up and discovered (source). All rightful credit can be paid to those.
This topic is not me claiming to have made the root process, but only instead simplifying the process (hopefully) for all y'all guys to get root up and running on your ZenPad C 7.0. Let's do this!
I am not responsible for any screwed tablets, rekt skrubs, or anything that happens as a result of you following this guide. It worked for me on my Z170C, so there's no reason as to why it probably shouldn't work for you.
ASUS ZenPad C 7.0 Root Prerequisites
ADB + Fastboot Drivers (can either use Google's, Intel's or ASUS')
Z170C Root img
Patience
Android SDK (and platform tools installed, can be installed through the SDK Manager)
Ensure that the ADB + Fastboot drivers are correctly installed by opening a new command prompt window, and typing the command "cd {this should be the directory to your Android-sdk/platform tools folder - the folder where adb.exe and fastboot.exe are located". Now, type "adb devices". If you see your device in the list with 'unauthorised', ensure that you check your tablet and allow ADB debugging to continue with your computer.
A full backup of everything that you would like to keep (because the device is unrooted, we cannot complete a Titanium Backup or likewise. Instead, ensure that all valuable photos, music, apps are backed up and are kept a note of to reinstall afterwards. We will have to be factory resetting the tablet in order to unlock the bootloader and boot from the root img.
(downloads are below in the attached files)
ASUS ZenPad C 7.0 Root Process
Ensure that ADB Debugging is enabled on your device, and that a full backup of everything that you want to keep has been made.
Connect your Z170C to your computer with ADB Debugging checked, and ensure that the ADB drivers are installed and working as intended.
Download the Z170C root img, and store it on your desktop.
Open a new command prompt window, cd to your Platform tools folder (with adb.exe and fastboot.exe) and run adb devices to ensure that your device is connected.
Once connected successfully...
Code:
adb reboot fastboot
to reboot into fastboot.
Now you are successfully in fastboot, here's the tricky part. Follow the code as exactly given below:
Code:
fastboot oem unlock
fastboot oem unlock confirm
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
IMPORTANT: The window will request that you follow the code "adb format userdata" and "adb format cache". DO NOT DO THIS. You will risk bricking your tablet (this was the mistake I took when I tried rooting this tablet for the first time, so it's no biggie). If you accidentally follow this by accident and end up bricking your tablet, follow the guidance below.
Allow the tablet to boot up. Give it a few minutes, and you should be at the ASUS tablet setup screen again. Proceed with setting the device up.
Once set up, proceed to the Play Store and install SuperSU (maybe even 'Root Checker' for further confirmation that root is successfully installed on your device). Once SuperSU is installed, be sure to update the root binary when it first prompts you to. At the prompt screen, select 'Normal' installation rather than 'TWRP/CWM'.
When the binary has installed, reboot your device one final time. Welcome to your rooted Z170C!
Endnote
I hope this brief tutorial helped you to gain root onto your ASUS ZenPad C 7.0. It is disappointing that you will have to go through all of this trouble in order to obtain root, but if you follow all of the steps exactly I can guarantee that it will work. And not forgetting, again, all credit stands to where it's due (check top of forum post).
In case of brick...
It happened to me, and it'll probably (not) happen to you. If by any chance you make a mistake and go wrong, fear not.
Firstly, leave fastboot by powering off the device.
Power back on the device, and when you reach the 'ASUS' boot up screen, hold the power + volume down buttons at the same time. Wait roughly 5 seconds.
At the 'recovery menu' screen, use the volume keys to select "Factory reset" and press the power button to select.
Wait a minute or two, and when the process has completed, use the volume keys to scroll back up to the top and reboot your device.
Once you are back inside the ASUS Setup, reboot your device and try again! This time, following the steps... Good luck.
Unbrick process not working for you? Download the stock firmware .zip here, and be sure to boot into recovery mode (power + volume down at boot) and flash the .zip. - I haven't tested this yet so I cannot confirm 100% that this method works, but it should. It could be either an update package or the full stock firmware, but one user has confirmed this method to be working.
v.1.0.1 - Topic created. Will require cleaning up and simplifying sometime.
Click to expand...
Click to collapse
Okay, I am not sure what I am doing wrong, i can run the adb devices command and it shows that it is connected. After i run the adb reboot fastboot my p01z is at a green screen with the little android guy on it. Then I try to run the next command and it says waiting for device. What am I doing wrong? What info do I need to provide for some help? Any and all help is appreciated. Thanks

@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
@corvusfan23
When you're in the green screen where it says "waiting for device", check your Device Manager (windows key + R, search for devmgmt.msc"). If you see your device with the yellow warning symbol next to it, it isn't correctly installed. Simply double click on it, and click browse to manually install the driver and click on either the Google / ASUS / Intel or any other compatible ADB driver and let it install. It should then be usable to and from your computer.
This happened with me and is quite frequent. For me however, the device kept connecting and disconnecting every 20 seconds so I had to be very quick at reinstalling the correct driver. After the driver was reinstalled for my tablet again in fastboot, I could continue on with the process.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Okay I did end up getting my device rooted, how would I go about making a backup of my device? I saw something about titanium backup, and the next thing I want to do is remove the bloatware. Any help is appreciated!

@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk

AwesomeLewis24 said:
@corvusfan23
That's great to hear! To make a backup of your device, yes definitely I'd recommend Titanium Backup. It's a pretty powerful tool for root users to make full backups of the system, media, specific apps, etc. I haven't actually used it much myself as usually I don't keep much important stuff on my device (photos and music I usually keep in the cloud now) but on the odd occasion that I have used it, its been very good. I have it installed on my Moto G for "emergency situations".
Also, to uninstall the bloatware you can indeed use Titanium Backup but I'm quite a fan of Link2SD. I prefer the material design interface and the easy visuals, but that's just me. In terms of uninstalling bloatware, they work pretty much the same so its your choice. I've been loyal to Link2SD for a while now.
As far as bloatware comes, uninstall (or even better, freeze) as much crap as you want. I haven't experienced any problems with it so far - (on my old Acer tablet that I got at Christmas, the first thing after root I did was uninstall the Amazon app store. It bricked my tablet and there was nothing like stock firmwares around, or any dev support, so I returned it and got this asus). However, stay cautious and of course don't mess around with any apps that seem to be tied in with the system in some way.
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
Last question I have for now. What apps would you recommend uninstalling/freezing? I don't use a lot of the asus apps that came with it. Could I get rid of the "Asus Demo" app and "Asus Support" apps?

@corvusfan23
I've uninstalled most of the preinstalled apps (non asus) but also I've uninstalled some of the asus cloud and "do it later sort of apps. I've frozen the asus keyboard, the ZenUI launcher, and the built in browser as well because I use alternative Google apps.
Sent from my Moto G 2014 LTE using Tapatalk