Database Info

I Need a root package

hey guys... all the root packages I have seen so far have a survey to download ... I cant do surveys because .. well its a long story .
in a short version .. I am looking for a direct root package download without being troubled in doing a survey .
I would be grateful if some one can help me out

Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita

timmaaa said:
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
*** UNLOCKED ***
evita pvt ship s off RL
CID-HTC__622
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128

What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita

timmaaa said:
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
Click to expand...
Click to collapse
tried to flash recovery ...
"error : cannot load "recovery file name" (openrecovery-twrp-2.6.0.0-evita)
though it is in the same folder of android where I put fastboot and all that stuff..

The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita

timmaaa said:
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
Click to expand...
Click to collapse
oh I forgot the img thing haha
thanks a lot
though now I wanna flash the venom rom (sense 5 , 4.2) and step 3 says : "Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)" what does that mean ?

If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita

timmaaa said:
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
Click to expand...
Click to collapse
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread

madshark2009 said:
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
Click to expand...
Click to collapse
Thanks, I've just been doing this for a while. Give yourself some time and try to keep up with things and you'll gain a whole lot of knowledge too.
Sent from my Evita

[Q] Painted myself into a corner...

I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?

Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.

Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)

jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.

Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.

solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S

[p500][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21

Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?

Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???

ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this

Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:

I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...

sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.

Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.

indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.

Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.

I built using official p500 armv6 repo
They should fix the device recovery size in that case!!

Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk

eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.

Installing CM11.M11 on Nexus 5

Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap

Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.

Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.

Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.

Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".​- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.​- fastboot flash recovery twrp.img​- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.

Noob Not Sure What To Do Next....

Hi all,
First off, I am not familiar with alot of the technical wording in these forums so I hope that I am able to communicate properly with my issue.
I was not happy with how slow the stock version of this tablet was so I decided to install a custom rom, however, I managed to get to the point of unlocking it but that's about as far as I got out of being overwhelmed with what came next! Here is where I am at:
I am currently on Android version 4.2.1 and my laptop is running Windows 10.
I have downloaded latest TWRP image file and renamed that twrp.img and it is stored in the main root folder of my tablet (SD Card aka Internal Storage). USB debugging has been enabled after I activated the Developer Options.
The custom rom I am looking at is CyanogenMod version 11 which I have downloaded, however it should be noted that on the download page it says that there is no recovery available for this build?? whatever this means? I also downloaded Minimal ADB and Fastboot but when I connect the tablet to the laptop (the tablet connects fine) I type in the command prompt "fastboot devices" but nothing happens.
I am at a point now where do I try to continue with the custom rom? or go back to stock?
Can anyone help with basic instructions please?
Thanks in advance.

Head to the General section and read the Beginners Guide. It's the first sticky, so it's easy to find.
It's your decision which rom you run, but you should give Katkiss LP or Katshmallow a good look.
The latter is the only rom for this tablet that is still under active development.
Sent from my Nexus 5X using Tapatalk

Can I ask questions in this thread with reference to the beginner guide?

Sure. Ask away
Sent from my Nexus 5X using Tapatalk

I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks

binx77 said:
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2688891
As many times as it takes to understand it. :laugh:
In the meantime I will update post #2 a little.
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)

I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?

binx77 said:
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
Click to expand...
Click to collapse
It's all in my Beginner's Guide - you just have to read it:
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery
Click to expand...
Click to collapse
And I gave you the remaining steps in my last post....
Now it's up to you to read and read again. And google terms you do understand. Then read again
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tran...p-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
Click to expand...
Click to collapse

This is where I am up to now as per the beginners guide
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
the error I get says "cannot open twrp" (I renamed the TWRP file that I downloaded) even though this image file has been moved into the fastboot directory on my PC (I downloaded and installed the ADB, Fastboot and Drivers tool)

How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk

berndblb said:
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I renamed the file just in windows explorer and I can confirm that the file name is twrp.img

That's with file extensions enabled? Do you see the extensions for all the files in that folder or just for TWRP?
BTW, which TWRP version do you try to flash? Downloaded from where?
Sent from my Nexus 5X using Tapatalk

Ok I got past this point, I hadn't added .img to the command prompt.
Now I am in TWRP and attempted to install KatKiss but it came up with "Zip Signature Verification Failed!" Error installing zip file '/sdcard/download/katkiss-6.0_TF700T_026.zip".
It did say that it could not find MD5 file?
I now have 2 options
1 - Wipe Cache/Dalvik
2- Reboot System

Just hit the Home button in TWRP, go back to Install and this time uncheck the box that says "verify zip signature" then flash the rom. It always checks if you have a md5 checksum file, but it doesn't matter if you don't. The flash goes through anyway
Sent from my TF700T using Tapatalk

Excellent, I successfully installed KatKiss 6.0.1!
Thanks for your help mate!

well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)

binx77 said:
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
Click to expand...
Click to collapse
You got it resolved?

Katkiss Marshmallow - Can't run Goggle Services/Play
I converted my TF7000T from 4.2.1 to KatKiss Marshmallow, using TWRP Manager on the installation end. Steps included boot access, rooting, wiping/formatting and flashing. Marshmallow functions fine. My problem is that I can't get Google Play or Google Services to run. I tried one installation that was a 'moderate' Gapps installation. It was completely unstable despite some of the apps actually updating. I then repeated the wipe and reinstall of KatKiss-026 and Android 6.0.1 with a minimal Gapps installation - just Google Play Store and Google Play Services. Google Play Services flashes constantly that it is not working. I am also not able to log into my Google Play Store account. I'm afraid I have an outdated version of Google Play. However, I cannot figure out a way to update Play Store or Play Services. Does anyone have a solution to this problem? If I could download a minimal Gapps zip that contained either the current, or update-able version of these two apps, I would also be in business. Help!!

You are running the wrong gapps package I think. You need to install the pico gapps and only the pico gapps package that is linked in the KatKiss OP.
And you have to flash rom, gapps and Supersu(if you want root) in the same recovery session together in that order. Every time. You cannot just flash a gapps package on MM rom anymore.
ROM, pico gapps, supersu - reboot
Oh - and to start out with I'd highly recommend you wipe, better format data before flashing. Wiping of cache and Dalvik goes without saying right?
Sent from my TF700T using Tapatalk

Yes I did thanks, I haven't played around too much with it though - I did experience it to be very slow when trying to install Facebook app though. I do plan to start using it more often so time will tell.