Database Info

[Q] Can I force an upgrade to JB? And do I want to?!

I'm in the UK, but haven't received a notification yet that there is a software upgrade available to me. I'm currently running ICS 4.0.3. which I rooted.
Presumably the JB update is out in the UK? Why am I not receiving it? Do I want it, given a few comments on here about glitches? And assuming the consensus is that it is a decent upgrade, can I force an OTA download somehow? Clicking Check update doesn't help!
Thanks

aliaird said:
I'm in the UK, but haven't received a notification yet that there is a software upgrade available to me. I'm currently running ICS 4.0.3. which I rooted.
Presumably the JB update is out in the UK? Why am I not receiving it? Do I want it, given a few comments on here about glitches? And assuming the consensus is that it is a decent upgrade, can I force an OTA download somehow? Clicking Check update doesn't help!
Thanks
Click to expand...
Click to collapse
I'm not sure why you're not getting the update, but you can get JB on your tablet by flashing custom ROMs. If you haven't unlocked your boot loader yet, beware that it voids your warranty. The AOSP based ROMs, mainly Cyanogen Mod 10, has the latest JB build. There are ROMS based on stock Asus's build, and they're also blazing fast, with no bugs & glitches AFAIK. If you are flashing the stock-based ROM, you should also know that you can't flash non-stock Roms afterwards, at least for now, due to the different bootloader for asus' JB build.
Or alternatively, you can download the UK JB firmware from the ASUS website, copy it to your internal storage and reboot. There should be a notification for firmware update then. Hope this helps.

sosroz said:
I'm not sure why you're not getting the update, but you can get JB on your tablet by flashing custom ROMs. If you haven't unlocked your boot loader yet, beware that it voids your warranty. The AOSP based ROMs, mainly Cyanogen Mod 10, has the latest JB build. There are ROMS based on stock Asus's build, and they're also blazing fast, with no bugs & glitches AFAIK. If you are flashing the stock-based ROM, you should also know that you can't flash non-stock Roms afterwards, at least for now, due to the different bootloader for asus' JB build.
Or alternatively, you can download the UK JB firmware from the ASUS website, copy it to your internal storage and reboot. There should be a notification for firmware update then. Hope this helps.
Click to expand...
Click to collapse
The current cm10 is for the ICS bootloader not JB.
I downloaded the zip from asus support, unzip once which leaves a zip. Placed that on sdcard, reboot, notification triangle displayed, clicked it and agreed to update.
I wish I had stayed on ICS and used the current cm10.
or
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.asp...300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Rename the extracted .ZIP to "EP201_768_SDUPDATE" (without the " ") and copy it to your MicroSD card
5. Insert the MicroSD card in your tablet
6. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
8. At this point the device will go in recovery and should start updating your firmware

Look into getting NVFlash before you do anything, while you're still on ICS

tobdaryl said:
The current cm10 is for the ICS bootloader not JB.
I downloaded the zip from asus support, unzip once which leaves a zip. Placed that on sdcard, reboot, notification triangle displayed, clicked it and agreed to update.
I wish I had stayed on ICS and used the current cm10.
Click to expand...
Click to collapse
Yep, that's why I said he can't flash AOSP ROMs anymore once he upgrades to JB...
There's less customization for the stock-based ROMs, but in my experience, CM10 doesn't seem to play nice with the keyboard dock compared to the stock-based builds. For example, my lock/unlock key doesn't work on CM10, as well as auto-sleep when I close the tab-dock. The cursor is changed too when using the trackpad (it shows a big-arse circle instead of a pointer).
Anyway, it's only a matter of time until CM10 can be flashed via stock bootloader, we'll just have to be patient (I miss playing around with CM10 too).

sosroz said:
Yep, that's why I said he can't flash AOSP ROMs anymore once he upgrades to JB...
There's less customization for the stock-based ROMs, but in my experience, CM10 doesn't seem to play nice with the keyboard dock compared to the stock-based builds. For example, my lock/unlock key doesn't work on CM10, as well as auto-sleep when I close the tab-dock. The cursor is changed too when using the trackpad (it shows a big-arse circle instead of a pointer).
Anyway, it's only a matter of time until CM10 can be flashed via stock bootloader, we'll just have to be patient (I miss playing around with CM10 too).
Click to expand...
Click to collapse
Thanks for the additional info I was not aware.

[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).

[Opinion] Worth updating from ICS to JB with rootkeeper?

Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!

psjw12 said:
Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!
Click to expand...
Click to collapse
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.

As for your launcher crashes, have you tried an alternate launcher such as apex launcher?

Organized_Chaos said:
As for your launcher crashes, have you tried an alternate launcher such as apex launcher?
Click to expand...
Click to collapse
I've not tried any other launcher. I think there's problem coming from the graphics because after some time of the tablet being on (about 24-48 hours), all 3D applications will crash and the home screen will not draw correctly.

Dredz said:
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.
Click to expand...
Click to collapse
I'm planning on sticking to the stock room on JB. So plan is I won't unlock it. I think warranty runs out in May so I'm waiting till then to unlock.

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)

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.