Database Info

[Q] Regarding what all are possible in an SBKv2 eeePad Transformer

I have an eeePad TF101 (no G) and its serial number starts with B80, so I guess that makes it an SBKv2. My questions are whether the following are possible and what some terms mean.
1) What does SBKv2 mean? Why is nvflash incompatible with it?
2) What is the homepage of nvflash? Is there any other flasher that is compatible with SBKv2?
3) Is it possible to install any custom rom?
4) I read it's possible to run Ubuntu with chroot after rooting. Will that make it slower? Is it possible to get a full linux bash terminal with the option to install stuff?
5) Will rooting give me complete system access? (I once had a Galaxy gt-i5510 which gave me 'permission denied' error even after rooting, for stuff like copying files to system folders running apps etc).
6) Is it possible to use a USB modem (ZTE MG478/AC8700, EvDO) using:
a) wvdial from chrooted linux and then use from android (I know it's crazy).
b) wvdial directly.
c) Any other method.
7) Will rooting cause any problems or 'side effects'?
Sorry if I asked questions that were already asked.

Uh...this is way too many questions to answer when all of the answers can be found by searching. This is your first lesson..you need to search. These are all common questions.

Ok i've only recently got a transformer but ill try answer these questions...If i've got something wrong feel free to correct me.
1) SBKv2 is the newer model of the transformer, Nflash isn't compatible because it runs on a newer bootloader.
2) I'm not sure...
3) Yes.
4) Yes you can run linux ubuntu, but only for the older model :/
5) Yes it will.
6) I'm not entirely sure, You'll have to wait for someone else to answer this
7) Probably not

1. the guy above is not quite right it is that the sbk (secure book key) is diferent and was leaked for the original rom but not the 2nd version
2. wait what? use cwm
3. yes
4. it runs a virtual immage vnc'd within android so ya it is slower
5. as long as you make the system r/w instead of r/o
6. maby try the usbethernet drivers
7. it will casue ota's to fail and you will not be able to purchase movies from the market
Every piece of information here is already here learn to search

mrevankyle said:
1. the guy above is not quite right it is that the sbk (secure book key) is diferent and was leaked for the original rom but not the 2nd version
2. wait what? use cwm
3. yes
4. it runs a virtual immage vnc'd within android so ya it is slower
5. as long as you make the system r/w instead of r/o
6. maby try the usbethernet drivers
7. it will casue ota's to fail and you will not be able to purchase movies from the market
Every piece of information here is already here learn to search
Click to expand...
Click to collapse
2) So custom roms work, dual booting doesn't?
4) But I will still get a full linux bash terminal with the option to install apps and all right?
5) How do you get r/w access? Is that the default mode in nachoroot?
6) Usb modem not ethernet!
7) Movies? What about everything else? OTA? That will be resolved if I use OTA Rootkeeper right? What about the updates from asus website?
I kinda did search. But I guess I'll search more next time....

phoenixv5 said:
2) So custom roms work, dual booting doesn't?
4) But I will still get a full linux bash terminal with the option to install apps and all right?
5) How do you get r/w access? Is that the default mode in nachoroot?
6) Usb modem not ethernet!
7) Movies? What about everything else? OTA? That will be resolved if I use OTA Rootkeeper right? What about the updates from asus website?
I kinda did search. But I guess I'll search more next time....
Click to expand...
Click to collapse
the only way to dual boot is nvflash ubuntu/andorid and that requires nvvflash so no you cannot dualboot
you should but be wary as it is ubuntu arm and not all apps are compatable
it is in the file manager you use ubt in consol you will have system access and if in root explorer you click read/write
i know you said usb. it may work by default not garenteed .you can increace the likleyhood of it working with the 3g dongle drivers and the usb internet drivers (Usb etherent)
it depends if you have a custom recovery installed (CWM) if you do not get cwm you need otarootkeeper and ota's will work if you do install cwm then you will not get the ota's installed

mrevankyle said:
you should but be wary as it is ubuntu arm and not all apps are compatable
it is in the file manager you use ubt in consol you will have system access and if in root explorer you click read/write
if you do install cwm then you will not get the ota's installed
Click to expand...
Click to collapse
Won't the installer (apt or synaptic) auto detect arm like it did in N900 and all?
What's ubt? Do you mean manually add r/w permission to all files?
What about update files downloaded directly from asus website? Will I still get market?

phoenixv5 said:
Won't the installer (apt or synaptic) auto detect arm like it did in N900 and all?
What's ubt? Do you mean manually add r/w permission to all files?
What about update files downloaded directly from asus website? Will I still get market?
Click to expand...
Click to collapse
i am not sure probably though
its a mistype i ment "but"
no in root explorer there is a buton at the top to change mount type it says "mounted as r/0" by default and there is a buton beside it to "Mount R/W"
they may work as they are the same files as the OTA's so it is the same case as the ota's.
Yes the market does not change besides the inability to purchase videos

So lemme summarize.
Nvflash doesn't work, CWM recovery does, so flashes using that also works.
OTA updates or (maybe) the ones downloaded won't work. But OTA's can be modified into ones that are recognized by cwm and retains root (with supercurio's script?).
Rooting without installing cwm doesn't interfere with OTAs.
Use OTA Rootkeeper to retain root after updates (not needed with cwm as cwm flashable stock upgrades are already rooted).
And root+cwm is undo-able.
Did I get all that right?

Please, before you ask any more questions, read THIS GUIDE;
Asus Transformer EPIC NOOB GUIDE
Almost every question you have asked is answered for you now. And probably a lot of future questions. And practice searching before posting new threads, most things you will find are already dealt with by now and the answers are just a search away no need to wait for people to answer you.

luna_c666 said:
Please, before you ask any more questions, read THIS GUIDE;
Asus Transformer EPIC NOOB GUIDE
Almost every question you have asked is answered for you now. And probably a lot of future questions. And practice searching before posting new threads, most things you will find are already dealt with by now and the answers are just a search away no need to wait for people to answer you.
Click to expand...
Click to collapse
I did. Right before posting my previous reply.
BTW thanks for the guide.
Edit: I guess that's it. Close / delete the thread!

Question about rooting 4.3

If I take the 4.3 update is the process to root it the same as it was on 4.2 or will we have to wait for a new way to root? I used this process previously and it worked for each update:
https://github.com/linux-shield/shield-root
Though now that there is a mapping utility I am not sure I will need to root it anymore... Depends on how good the mapping utility is.

This is not going to work unfortunately. I need to update the rooting procedure but am not really aware of how this is done on 4.3 (if anyone has pointers by the way) and the update arrived sooner than I thought. Will try to get that done quickly, please be patient in the meantime!

Great, thanks for the update. I will be sure to not even try then

Evo_Shift said:
Great, thanks for the update. I will be sure to not even try then
Click to expand...
Click to collapse
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.

agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
Can you explain more what you mean. I know how to flash CWM but what do you mean "root that way"?

First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389 (LINK DEAD: MIRROR: http://cl.ly/2o3n3f0C0G2S)
Copy it to your Minimal ADB & Fastboot folder.
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
adb reboot bootloader
fastboot boot recovery.img
Your device should reboot into CWM.
Then, grab the latest SU from here: http://download.chainfire.eu/351/
Copy the SU zip to an SD card. Choose "install ZIP from external SD" in CWM. Choose the SU zip. Let it finish, reboot and you're done!
Way too much damn work if you ask me, but made signficiantly easier thanks to the community. This was cobbled together from the various posts on the subject in xda developers. Thanks guys!

thank you shinratdr, that works perfectly.

Not sure what I did wrong here (have not seen this before myself) I installed the update, and everything seemed to work find. When I finally needed to use root it would not work, so i downloaded the root zip flashed that nothing changed.
From a terminal emulator on my shield when I enter su. I get no errors, and root does not work.
From the supercd /system/binuser app I get that su is not installed and it can't be installed.
From adb shell after entering su the prompt changes to # but noting that needs root works.
su is installed in /system/xbin and has the following permissions -rwsr-sr-x.
I am not sure what to do next.
Update
For now I am just restoring my back up of update59.

shinratdr said:
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
!
Click to expand...
Click to collapse
Maybe stupid question but just download this here?
http://forum.xda-developers.com/showthread.php?p=42407269
Never really rooted something before and not really looking forward to it due to loss of warranty but I really want to use the PS3 controller

Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!

Gnurou said:
Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!
Click to expand...
Click to collapse
Worked great. Thanks

agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
I can confirm that while you need to flash the stock recovery image you provided to update, after updating, I had no problem reflashing your CWM image in fastboot and then flashing SuperSU 1.65

Just posting as a follow up to my earlier post here
I had to download the superuser.zip from this Superuser page on the play store.

shinratdr said:
First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389
Click to expand...
Click to collapse
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!

punraz said:
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!
Click to expand...
Click to collapse
I hope you were able to find it. If not, I located the copy I left on my computer. Enjoy, this strategy seems to work fine with the latest update for a "quick" re-root.
http://cl.ly/2o3n3f0C0G2S

Thank you mate, all done now! Works like a charme. Greetings.

[Q] Looking for root basics, list etc.

As the title states, I need help with understanding the basic steps on rooting the ASUS TF300.
I am not a programmer, I do not know the lingo or terms, and searching on the site has yielded very confusing results.
Basic steps?
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
4. Kernel - What is this?
5. ROM - What is this?
6. Install Super SU or SuperUser (what's the difference?, what does this do?
7. Install a root check app (to check if rooted I presume)
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
9. De-bloat with caution!
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
As you can guess I'm lost. Reading threads after searching for "root TF300" or even the guides or the very good index, I have more questions than answers. How does one know what to do if the acronyms used are cryptic? (example TWRP~ what does this even stand for?)
I believe that not all steps are required, but I also believe the order I do things is important, and I'm concerned about bricking my TF300 by doing something wrong. I also don't want to assume that this is the same for every device or phones. (what steps work for a phone may not be the best for a tablet)
All I want to do is root and remove bloat. After I get this, I may consider upgrading the OS (kernel? Rom?) to something better.
Any links would be greatly appreciated. Please just bear in mind I'm so noob to this I don't know a ROM from a Kernel yet. (When I search, all answers are overly complicated developer definitions.)
Thank you!

Here is a "simple Step by Step" with notes in red as to how my mind tries to grasp this:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2 I assume they mean any OTA upgrade~ my tablet is current with JB 4.2.1 and I do not believe ASUS will plan on upgrading this anytime soon)
2. Be sure the correct drivers for your tablet are installed!! Installed where? on my PC? How do I know what are the correct drivers? Where can I get them?
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit -OK, I can do this!
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2 -This makes sense to me, as I am jellybean 4.2.1
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard -what is a blob file? Is there a size requirement for the SD card? Does the SD have to be blank?
5. Extract the rooting toolkit to a place you like. -I assume the above mentioned motochopper? Does this answer my question above about the SD card?
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit. - with what program? A simple file explorer I assume?
2. Open the run file and follow the instructions -I hope there aren't any cryptic/over my head choices to make!
After installation the tablet should reboot and you should be rooted. -Does this install all the SuperSu stuff or is this it? What about customer recovery? Can I go back? what are the limitations of doing it this way assuming it works....
And this is just PART of the process!

I'll answer in logical order:
broderp said:
5. ROM - What is this?
Click to expand...
Click to collapse
That's the Operating System that's running on your tablet, i.e. what is called Lollipop or KitKat, or even further what makes the difference between Android and iOS.
Your ROM may come with some preinstalled apps, but with some ROMs they are separate (i.e. the Google apps).
broderp said:
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
Click to expand...
Click to collapse
On your ASUS tablet you can, by default, only install ASUS supplied ROMs (i.e. updates).
In order to install a new ROM you need to unlock your device. You do that by unlocking the boot loader. Once you have unlocked the boot loader, you can install a custom recovery, such as TWRP (there are many custom recoveries, but for your device TWRP is recommended).
Once you have a custom recovery, installing a new ROM, or rooting your device, becomes a lot easier. No need to type in commands, but you can now use touch.
broderp said:
4. Kernel - What is this?
Click to expand...
Click to collapse
Your kernel is the most important part of your ROM. It's the software between apps and your actual hardware, the lowest level actually. The kernel determines if you can talk to certain pieces of hardware or not. If the kernel does not support certain hardware, that's it, you can't use it.
When your tablet boots up, the first thing it loads its the kernel, the kernel loads all other programs. Another responsibility of the kernel is to allow you to run multiple programs at once.
broderp said:
6. Install Super SU or SuperUser (what's the difference?, what does this do?
Click to expand...
Click to collapse
They allow you to execute programs with root privileges (i.e. no limit to privileges, can do anything), but also give you some protection so malicious programs cannot become root: you have to give explicit permissions for every app.
broderp said:
7. Install a root check app (to check if rooted I presume)
Click to expand...
Click to collapse
Yes.
broderp said:
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
Click to expand...
Click to collapse
Optional, pick whatever you like.
broderp said:
9. De-bloat with caution!
Click to expand...
Click to collapse
No clue!
broderp said:
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
Click to expand...
Click to collapse
Firmware often is part of the hardware: it gets written to special memory, and "sticks", i.e. when you reboot it stays there. If you get a T300 you should let ASUS run all the updates as it installs new firmware. Some firmware gets written when your device boots, meaning the special program, the kernel, starts, and at some point writes updated firmware to hardware.
So firmware is software that makes hardware a bit more flexible: else everything is hard-wired, if there's a problem you can't fix it, but with software you sometimes can fix a hardware issue.
Hope this helps!

First, to unlock the bootloader, you need to go the asus site and register your tablet. Then you can download the unlock app from the asus site as well. Next, move the unlock app from where ever it downloaded on your pc to your tablet. You can put it on the tablet RAM or on an SD card, it doesn't matter. On your tablet, go into the settings menu. under security(I think it is there) and enable 'unknown sources' for app installation. I haven't had the stock ROM for so long, I can't recall where that option is. Run the unlock app. It may take a couple times to unlock the tablet. WARNING! this will void your warrenty! So if your tablet is relatively new, think hard about this. Once your tablet is unlocked, then you can worry about TWRP and ROMS
TWRP is a custom recovery. It is officially Team Win Recovery Project, hence TWRP. It is a program that will allow you to back up your tablet before you make changes(very important in case you screw something up) and a host of other things including flashing custom ROMs. If you go into the LP 5.1 for the TF300 thread in the development area, it will have all the links for stuff like the current TWRP, Gapps packages and the newest LP ROM. It is great for our tablets and really wakes it up. Oh yeah, the TWRP site will have instructions for flashing TWRP on your newly unlocked tablet as well.
All this seems very intimidating for noobs, I was one about 4 months ago. I now feel sort of not-noobish. To install TWRP you will need either Fastboot or ADB on your computer. Google Fastboot or ADB and you should find plenty of answers. There are also 'lite' versions of Fastboot out there too. If you are on Windows 8 or 8.1 you will need one of those. Windows doesn't like fastboot or ADB for some reason
HTH

TF300T Terminal Emulator TWRP.blob HELP!

Hey guys, I need a little help getting the Custom Recovery TWRP to work with terminal emulator.
I have the Asus Transformer Pad TF300T(WIFI Only)
Android Version: 4.2.1
Build Number: 10.6.1.27.5
Bootloader: Unlocked with Asus Unlock Tool(Restart with small print in top left corner "This device is unlocked")
Root: Rooted with KingoRoot
My problem is everytime I open up the Terminal Emulator(The reason for using this method is because I dont have a USB cable to connect to the computer) I type in
SU (a little popup shows it granted superuser access)
I then type in
dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
It then tells me
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
Full Terminal Emulator DOS screen:
[email protected]: / $ SU
[email protected]: / # dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
I have the file renamed to TWRP.blob. I also have a TWRP.img that I've tried and its in the root of my sd card. I've even tried formatting my sd card for android because before this i never used it for anything.
Any help would be appreciated.

Bamablood94 said:
a little popup shows it granted superuser access
Click to expand...
Click to collapse
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.

ebonit said:
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.
Click to expand...
Click to collapse
Trying it now will update in a second
I already had SuperSU access to the terminal emulator and Ive already tried with that TWRP but i still get the same thing No such file or directory

I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?

Bamablood94 said:
I've even tried formatting my sd card for android
Click to expand...
Click to collapse
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
Bamablood94 said:
I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?
Click to expand...
Click to collapse
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.

ebonit said:
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
I'll have to try that cause if I'm not mistaken it formatted to NTFS.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.
Click to expand...
Click to collapse
Can I use the recovery to install it or TWRP manager app or am I gonna have to do the terminal emulator
It successfully installed katkis mm6.0.1

ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?

Bamablood94 said:
ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?
Click to expand...
Click to collapse
NO!!! Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
You're good, you did good, but get the heck yourself a USB cable so that you have fastboot access. I hate to watch trapeze artists working without a net!!!
It's $7 on Amazon - no excuses accepted!
https://www.amazon.com/Charging-Sync-Cable-TF101-TF201-TF300/dp/B007QUBYDY

berndblb said:
Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
Click to expand...
Click to collapse
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.

ebonit said:
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.
Click to expand...
Click to collapse
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.

berndblb said:
I am sure.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
Thanks a lot for your very instructive reply. I'm gonna to stay on Josh's TWRP until I change the rom.

berndblb said:
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougaamt roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
I am now running nougat 7.1.1 from katkiss using the twrp 3.0.2.0 using the TWRP Manager app and also downloaded the mini GApps. I didnt realize that was something I also had to install until i realized there was no play stor or any other google related apps but I have invested in a 5 dollar usb data cable from ebay which should come in sometime this week. My other problem now seems to be that this thing dont like running too many apps in the background and when you first start up a program it likes to lag it a tad bit untill it runs a little smoother. I appreciate the help guys.

Welcome to the wonderful world of the Transformer, my friend. If you expect this tablet to run anywhere close to the performance of any current device, you will be disappointed.
Asus thought up a genius form factor and then ruined it by crippling it by not giving it enough ram and a cheap, slow memory chip on top of it.
You have to go easy on this baby.
Turn off automatic updates in the Play Store.
Turn off automatic updates and syncing for as many apps as you can stand.
If you don't use an app, get rid of it.
Do NOT use the Facebook app. It's a piece of cra** anyway and really hard on resources
In the 700 forum Tim posted some fine tuning tips a while back. If I find it, I'll add the link later
Develop a good backup/restore routine (e.g Titanium Backup) and then format data every 3 months or so - depending on how much you use the tablet.
If you haven't, convert /data to f2fs. That really helps on this tablet let.
Enjoy
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well

berndblb said:
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well
Click to expand...
Click to collapse
BTW, the same tips put Tim in a TF300T thread as well:
https://forum.xda-developers.com/showpost.php?p=71094836&postcount=615
To my opinion the best performance with KatKiss N7 on the TF300T will be reached with a RAM use of around 65%. That means to keep the amount of apps as low as possible. In my case up to 45 apps, but mostly less. Always have an eye on piggy apps.

I appreciate the help guys I don't use the tablet much since I have an Asus phone but I install the zenui launcher and to my surprise it seemed to help the "lag" just a bit. Again I appreciate the help I don't get on xda often but when I need help this is my go to place.

May Update Help?

Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?

Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly

Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...

Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!

I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.

Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?

Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one

pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it

Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!

pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.

exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).

Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome

Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding​ it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.