Database Info

[Q] tf700 cleanrom lagginess?

Hi,
Ever since I remember my tf700 and cleanrom (from 2.x and above) it was kinda laggy. I noticed that during my several application usages (TED, Sketchmobile for tablets etc.).
Anyone else been having that issue? Even chrome is lagging abit ...

advocator said:
Hi,
Ever since I remember my tf700 and cleanrom (from 2.x and above) it was kinda laggy. I noticed that during my several application usages (TED, Sketchmobile for tablets etc.).
Anyone else been having that issue? Even chrome is lagging abit ...
Click to expand...
Click to collapse
Are you on the latest jelly bean bootloader - it makes a difference. Also which options are you installing with?
What is TED?

sbdags said:
Are you on the latest jelly bean bootloader - it makes a difference. Also which options are you installing with?
What is TED?
Click to expand...
Click to collapse
Lagginess in CleanRom is impossible. You must have done something wrong
@sdbags, TED is an app (and website) that lets you stream some of the most interesting videos on the planet with

I tried either the stock kernel or the oc'ed one (1.5ghz I think) version 1.8. It was on top of the list. Also, I added the adaway options and the smooth scrooling.
Other than these, I havn't picked any system tweaks.
I've done this with wipe too.
In fact, right after it boots - it feels "really laggy". It took about 1-2 seconds to go between initial setup screens. Once it finished and I reboot, it works ok - but it still lags in certain apps. Sketch for tablet is an excellent example because you can really see a 0.5s delay between what I draw and what is drawen.
Same goes with titanium bacup by the way .. gets 0.5-1 s delay between certain options.

Doesn't sound right.
Are you sure you are on the latest Asus jelly bean bootloader? You haven't said yet. Which Rom did you come from? Roms will always be laggy after a full reboot. There are many processes and apps starting even after the lock screen becomes available.But you don't shut down and reboot very often do you so it's a moot point.

not able to install some apk
I was enjoying the smoothness of the cleanrom until i couldnt install some apks, says fre up space but i got lil over 5 gig and my micro sd barely has anything in it and i got 32 mico sd, also i know its not same section but is it possible to just root and just continue with stock? LOVE the clean but the error with installing certain apks while under rom upsets me cuz i can use backup to before i used the rom and install but then it wouldnt be rooted
Ok i can act like sucha noob, found how to root without changing anything,but i do still would like to figure about the cleanrom

advocator said:
Hi,
Ever since I remember my tf700 and cleanrom (from 2.x and above) it was kinda laggy. I noticed that during my several application usages (TED, Sketchmobile for tablets etc.).
Anyone else been having that issue? Even chrome is lagging abit ...
Click to expand...
Click to collapse
...again you're on the wrong bootloader.
Were you on ICS when you flashed?
You will have to go back update to Jelly Bean then start the flashing process over.
Take it from me I was seeing exactly what you have now when I first flashed the original ClROM.

mike2001ny said:
I was enjoying the smoothness of the cleanrom until i couldnt install some apks, says fre up space but i got lil over 5 gig and my micro sd barely has anything in it and i got 32 mico sd, also i know its not same section but is it possible to just root and just continue with stock? LOVE the clean but the error with installing certain apks while under rom upsets me cuz i can use backup to before i used the rom and install but then it wouldnt be rooted
Ok i can act like sucha noob, found how to root without changing anything,but i do still would like to figure about the cleanrom
Click to expand...
Click to collapse
You have been using lucky patcher and it has left some patched .odex files in your data/app folder. Please remove them and your problem will go away.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
Thats OK said:
...again you're on the wrong bootloader.
Were you on ICS when you flashed?
You will have to go back update to Jelly Bean then start the flashing process over.
Take it from me I was seeing exactly what you have now when I first flashed the original ClROM.
Click to expand...
Click to collapse
Or try the bootloader flasher I made today here:
CLICK ME

^^^^^^^
LOL should've known...
Very sneaky!!! :laugh:
Excellent work!

sbdags said:
You have been using lucky patcher and it has left some patched .odex files in your data/app folder. Please remove them and your problem will go away.
Click to expand...
Click to collapse
Remarkable sleuthing. My respect!
@OP: start paying for your software, or we will start charging for our help. :silly:

Regarding the bootloader: 10.4.4.16 (got that from the download mode windows)..
Only thing I remember about the BL is that I already got my tf700 with JB on it, so I couldn't downgrade and had to unlock it as is (thus not able to backup some crucial anti-brick files).

[Q] Hanging on ASUS Image after installing ROM

First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.

rreedy30 said:
First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.
Click to expand...
Click to collapse
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108

cmendonc2 said:
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108
Click to expand...
Click to collapse
Thanks so much I was able to load both ROMs. I really appreciate it. My mobile dock does not work with either of them but I think I'll search around for that before posting another question.

Help confirm full Root/Recovery/Rom process

My wife has finally decided she'd like me to put a custom ROM on her TF101. I have experience (both good and bad) on my phones and tablets, but she doesn't want hers "messed up." So, I'm a lot less comfortable taking chances with her device than I am with mine. She still loves her TF101 and uses it daily and I don't want to mess it up. Her TF101 is still stock, not rooted, and has the last available ASUS update on it (IML74K.US_epad-9.2.1.27-20120615).
Initially my research indicated this was going to be the quickest and easiest Root/Recovery process I've ever gone though! Download Razorclaw to the device, run it to get root. Download Recovery Installer to the device, run it to get CWM. Easy peasy mac and cheesy. But, Razorclaw seems to be gone. The link to the tool gives a Page Not Found error. Another link on that site outlines a complicated process with a bunch of adb shell commands that made me a little uneasy. Recovery Installer likewise is no longer available at the link given in the first post of that thread. There's a link to a mirror location later in the thread, but if it's not available from the person who made it, then I have to worry. I've also now realized that her firmware version is not compatible with those tools to begin with!
So with my reluctance to upset my wife, some outdated information floating around in the threads, I just wanted to confirm my current plan was the proper way to go.
Use the PERI-0.42 tool to root and install TWRP. I wish I could find a video or screen shots of the process so I can know what to expect. (Or should I use the "1-Click Transformer Root" tool? I'm thinking not as TWRP would be preferable to Rogue Recovery?)
Nandroid backup from TWRP
Flash ROM following ROM's instructions
That about it?
As for which ROM, Root-Box looks interesting, but it says the camera doesn't work and my wife uses the camera (and the CamScanner app) frequently, so that's a no go. So, I was thinking about Paranoid-Android or No-name CM10?

First, Razorclaw only works on a very few firmwares, and the .27 is not one of them.
I wrote a guide on rooting the TF here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This uses EasyFlasher and APX mode. It does install an older TWRP, but if you replace the twrp.SOS file in the EasyFlasher "tools" folder with the latest official 2.3.2.3 file found here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob (rename to twrp.SOS and replace the file) then EasyFlasher will flash the 2.3.2.3. EasyFlasher will show the old version in the menu drop down, however it will flash the newer version. If you want TWRP 2.5.0.0 you will need to get it from the thread in the development section.
I have used Peri 0.4 in the past, and it is very easy to follow the prompts. I have not made a tutorial or video of it, but as I said it is pretty straight forward.
As far as the ROM to flash, I am using Domination right now and have flashed the RootBox one as well. At the current time the keyboard dock has little support for both of these ROMs. Many users have had issues with SOD and RR on the CM10.1 no-name. My favorite for stability and features is still TeamEOS 4. It has full dock support and is very very fast and stable.
I am actually looking to restore my EOS 4 Nandroid later today.

Easyflasher is about as no-brainer as you can get, I would recommend using that to install TWRP recovery (note: and update to a newer version as per above poster).
http://forum.xda-developers.com/showthread.php?t=1688012
I've used it with three different PC's and three different TF101's without any issues, and I've used it to revert to stock a couple times on mine.
As far as ROMs are concerned, I have had the best luck in term of a happy blend of fully-baked (everything works)/stability/compatibility/features/speed-smoothness with the EOS 4 ROMS and KAT kernals, though I have as of yet only given the latest PA ROMs (with halo) a quick look. I am admittedly biased on that front since I switched to EOS 3.0 long ago, but I also haven't heard of any complaints from my folks or a friend who are running slightly older versions of the EOS 4 ROM.
Some people say they aren't pleased with smoothness with the stock launcher in EOS (I run Nova Prime on mine and Nova free version on the other two I've helped "upgrade", seems quite smooth to me). I don't know if that is a perception issue, a difference in hardware, or maybe installed apps/widgets. Or if it is still even an issue.
The only issues I have had on mine (SOD's/RR's) in many months was with one short-lived version of the Kat Kernal, which was fixed asap. For me, it's just as stable as the last official ASUS ICS update, and way way more stable the the preceding one.
By all means, give them all a shot, but I have never really had a problem with using EOS as a daily driver.

Thank you, Gentlemen! That's just the sort of help and information I needed. I don't know how I overlooked EasyFlasher in my research.

I had the same firmware - I used PERI to root and went with EOS nightlies v118 and KatKernel v103. Best decision I ever made. Stable, fast and enough features to sink a battleship.
I overlock to 1400mhz using smartassV2 governor. IO scheduler is set to 'sio' (settings->EOS control center->syste,->Performance settings). Since then its been a dream to use, no lag, no waiting. I stuck the dolphin browser on for good measure. Since all that was done, its smooth, fast and really enjoyable. To think a week ago I was ready to sell it and get something new, no need to do that now!
good luck!

About a month ago I had what I thought was a hardware issue with my microSD card reader and started a thread in this subforum about that. Someone suggested I try flashing a custom ROM before I try replacing hardware. Long story short I am now running TeamEOS + Kat kernel and everything is great. Tablet is faster and more stable than it ever was on stock and its nice to be running JellyBean. Only warning, you'll need TWRP not CWM to flash ROMs using Android 4.1+ but otherwise there really isn't too much to worry over.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2

I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!

HeathicusF said:
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
Click to expand...
Click to collapse
Awesome!
Check out my FAQ guide on EOS 4 to help explain many questions you may have, and how to set it up the way you (or your wife) likes.

let us know how she gets on with it ,it really is a great rom my tab has never been so quick i use nova launcher and dolphin overclock it in setting to 1400 i have mine on 1504 and still see good battery life ,,,,,,install goo manager from play for updates to rom and also pimp my rom is good for a few tweaks here and there ,,but first when its all set up and working good MAKE A BACK UP i always make back ups as i go along i have 2 all the time only takes 320 seconds ,,,,,enjoy
Sent from my Transformer TF101 using xda premium

She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!

HeathicusF said:
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
Click to expand...
Click to collapse
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?

Thing O Doom said:
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Click to expand...
Click to collapse
I tried that ParanoidAndroid and it wouldn't get past the boot animation. I didn't try that Kernel, or an older non-Halo'd version of PA.
Thing O Doom said:
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Click to expand...
Click to collapse
Yep, the TWRP install via Peri worked flawlessly. It was vesion 2.5 of TWRP (Peri v0.42)

Is this normal?

Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.

chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM

shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris

Going back to stock is good advice.Should certainly fix the video problem which you said was important.

Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.

Yes.My use of the word "video" should have been "video recording".

The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.

chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]

Help Please, removing KatKiss 4.4.4 and Unrooting!?

Hi, . . . I'm a Noob to Rooting, get that out of the way.
I just bought a used ASUS TF101A with KB dock off EBay to replace mine that suffered a premature death in a flood. I was running (poorly) the last version of ICS, 4.03 If I recall. This one was advertised as "Excellent" and it is very clean but stinking of cigarette smoke, except that the jerk EBay seller failed to mention that was Rooted and running KatKiss 4.4.4 which I hate, the desktop is essentially blank, there are like 6 apps in the library and no Google Play access.
While I do want to install a "Factory Image" of KitKat 4.4.4 as if it was a OTA install, I want to get this awful KatKiss off, even it it means going back to a restored last version of ICS so I can even use this TF101, which it is completely useless in this state with katKiss.
Not being familiar at all with Rooting and Flashing, can someone please help and direct me on how to:
1 - Remove KatKiss and restore it to at least a full Factory install of ICS with all the original apps, Play access ... well like it wold have been.
2 - OR preferably, install a "street" Factory Image of normal KitKat 4.4.4 - Is that possible at all?
Thanks so so so much and remember you're deal with a Noob.

VintageGuitarz said:
Hi, . . . I'm a Noob to Rooting, get that out of the way.
I just bought a used ASUS TF101A with KB dock off EBay to replace mine that suffered a premature death in a flood. I was running (poorly) the last version of ICS, 4.03 If I recall. This one was advertised as "Excellent" and it is very clean but stinking of cigarette smoke, except that the jerk EBay seller failed to mention that was Rooted and running KatKiss 4.4.4 which I hate, the desktop is essentially blank, there are like 6 apps in the library and no Google Play access.
While I do want to install a "Factory Image" of KitKat 4.4.4 as if it was a OTA install, I want to get this awful KatKiss off, even it it means going back to a restored last version of ICS so I can even use this TF101, which it is completely useless in this state with katKiss.
Not being familiar at all with Rooting and Flashing, can someone please help and direct me on how to:
1 - Remove KatKiss and restore it to at least a full Factory install of ICS with all the original apps, Play access ... well like it wold have been.
2 - OR preferably, install a "street" Factory Image of normal KitKat 4.4.4 - Is that possible at all?
Thanks so so so much and remember you're deal with a Noob.
Click to expand...
Click to collapse
1. If you un-install KatKiss it will be a huge mistake. There is no better rom for the tf101 than it except for the 5.1.0 version. If you follow the direction word for word from the OP it can't be beat. Tim is also one of the nicest and most helpful devs that I know.
2. No, it's not possible.

There is no "Factory Image" of KitKat 4.4.4. the latest ASUS update was Ice Cream Sandwich (ICS), Android 4.0.3.
My opinion is that the KatKiss ROM KitKat 4.4.4 is the best you can install on your TF-101:
http://forum.xda-developers.com/showthread.php?t=2592890
A clean install will most likely fix any concerns you may have on this ROM.
If you really want to downgrade to ICS, the easiest way will be to use Easy Flasher:
http://forum.xda-developers.com/showthread.php?t=1688012
You will need to install the APX Drivers:
http://forum.xda-developers.com/showthread.php?t=1514942
TF101 will need to be put into APX mode:
With the device off, hold down the volume up key and the power button at the same time for ~10-15 seconds. It will look like nothing happened but when you connect the cable from your TF101 to computer USB port the APX drivers will get recognized.
You really need to do some reading on the XDA forums before attempting to install anything on your TF101.