Database Info

[ROM] CyanogenMod 6 For Vega (unofficial)

I have created the vendor files for the advnet vega based apon the cyanogen ones for the Gtab, and compiled CM6 for the vega. This is not supported by cyanogen's team yet as the vega isnt officialy supported by them yet so please take that into mind (dont ask for support on the cyanonen irc ect u probably wont get it) but feel free to ask support on this thred.
Nither me or the CyanogenMod team take no responsability for any damage caused bu this rom. by flashing it means u understand this risks and accept the risks.
What doesnt work :-
- Camera
- Rotation can be funny (if it works at all)
[UPDATE]
- Black Screen Of death can occur when rebooting (looking into this ASAP) so be prepared to restore
What works :-
- Every thing else (i think)
[INSTALL]
1) get the .zip file from the bottion of the post
2) copy it to SD card
3) reboot into recovery
4) MAKE NANDROID BACKUP
5) flash zip from recovery (you will get a boot write error thats normal)
6) reboot
7) DONE
[DOWNLOAD]
http://db.tt/UmV1dYK
[CREDITS]
CyanogenMod Team for there src
Bekit for the Gtab vendor this is based on
Anyone else i have forgotten
[MY VENDOR]
If anyone else wants to try and improve on this please feel free.
https://github.com/BuzzBumbleBee/android_device_vega/tree/froyo
(Please note at the current time the boot.img that the compile creates will not work on the vega to u will have to make one by extracting the original ramdisk from the boot.img)

thanks mate been tring with cyanogenmod for gtablet..gonna try now. THis bad boy vega need some action
got error message:
assert failed: package_extract_file("boot.img" ,"/temp/boot.img")
E:Error in /sdcard/CM-6.2.0-Vega.zip
(status 7)
Installation aborted.
edit: fixed.
I successfully installed, I put the original boot.img from vega into the zip, taking it for a spin now. Thanks Apache14.

I sold my Vega because of the screen imo wasnt great and the wi-fi issue.
Would have loved to have tried this rom though.
Good work !!!

Thanks to apache14 and everyone involved
How do we get market onto the tab. thanks in advance

Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)

Apache14 said:
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Click to expand...
Click to collapse
thx mate, misread the first post

Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.

arad85 said:
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
Click to expand...
Click to collapse
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Follow the instruction paul gave on modaco.
Download the Recovery image and flash utility and extract to desktop
open terminal
adb devices to make sure your device is connected
cd to the directory of file you just extract
then type
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 4755 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
thats done.
If you on mcr 6, the vega reboot recovery is already installed if not download from the market.
cheers

alphaola said:
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Click to expand...
Click to collapse
Yes, it's very straightforward. I've done it a few times too and followed the instructions. I still get the bsod as do a number of others. Without CM installed, no bsod...
Try power cycling your Vega back-to-back using the power button. I bet you'll get it to bsod reasonably quickly.

BSOD
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon

Apache14 said:
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
Brilliant - thanks

Apache14 said:
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
arad85 said:
Brilliant - thanks
Click to expand...
Click to collapse
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Note: Do not unzip the cyanogengenmod, just use winrar to open it and copy those files into it then close it

alphaola said:
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Click to expand...
Click to collapse
Sorry, being particularly thick today. How do I get hold of the three .img files?

arad85 said:
Sorry, being particularly thick today. How do I get hold of the three .img files?
Click to expand...
Click to collapse
download the advent vega system file from advent vega website,zip it using winrar.

alphaola said:
download the advent vega system file from advent vega website,zip it using winrar.
Click to expand...
Click to collapse
<facepalm>

arad85 said:
<facepalm>
Click to expand...
Click to collapse
no stress man. Its quite smooth and fast, love the animation as well

alphaola said:
no stress man. Its quite smooth and fast, love the animation as well
Click to expand...
Click to collapse
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!

To get the market and apps
Download http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip, then flash using rom manager. then once you reboot you should get all your apps and market. enjoy

arad85 said:
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
Click to expand...
Click to collapse
ahahha mate,it works.
Download button savior to make navigation easy

Hello all
Really looking forward to a stable version with an idiot proof install for folks like me.
Great work
Rgds
Lok

[GUIDE]How to load CM9 on GSIII

**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.

Very informative. Would read again.
Sent from my Transformer Prime TF201

dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html

I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.

Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium

dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.

is the data not working due to the ril??

suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out

I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.

Will these same instructions work for the CM10 build that is in the server list?

17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium

neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.

17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium

i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?

seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.

Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.

17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium

DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.

[Q] Unfortunately Launcher has stopped and other issues

Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.

irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.

tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!

irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!

tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.

irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server

tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.

tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks

irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.

tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.

Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?

tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.

Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!

tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.

irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!

New Builder Question

This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.

_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?

psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.

You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot

sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).

_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message

_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:

psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.

sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:

@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---

psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.

_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.

psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:

sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk

psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab

sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:

@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:

psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.

Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh

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.