Database Info

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

Trouble getting adb to work

Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob

SD card not found
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob

emueyes said:
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
Click to expand...
Click to collapse
What USB cable are you using? Try to use your Xoom oem cable. Also, make sure that you try different USB ports, especially the ones tied more directly to the pc motherboard. It's finicky like that. Recheck your drivers. I'm not familiar with that PDAnet source. Motodev is the place to get them from. You may also need the java sdk from oracle.
There are some useful guides on setting up adb/fastboot/rooting in General...you may have to go back a few pages but it will be worth it to make your task easier.
Good luck!
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
emueyes said:
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
Click to expand...
Click to collapse
Which recovery mode are you talking about? Have you unlocked and installed a custom recovery, as in a ClockworkMod-based recovery? If so, which one? They have some different behaviors. If it is stock recovery, I don't think it sees the external sdcard at all.

Also make sure usb debugging option is enabled. And flash another recovery image.
You don't really need to root. Just unlock the bootloader. Push the recovery image. Reboot to recovery. And flash a pre rooted rom from team EOS.
Sent from my MZ601 using Tapatalk 2

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!

[Q] Have TWRP No OS no SU can't install os

Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.

Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.

I still haven't had any luck. Does anyone have any ideas?

You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.

http://forum.xda-developers.com/showthread.php?t=2646279

berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so

Whoops, forgot screen shot

Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....

berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.

hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...

berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.

_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?

berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.

So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....

hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!

hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

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