Database Info

[Q] Can't receive update to 8.4.4.11

I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.

I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....

Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.

You can get the update in the "Just got an OTA update" thread.

Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk

...................

martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...

for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.

TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms

TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk

Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.

You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.

It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk

Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...

Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.

None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.

I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?

superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116

Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.

Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.

[Q] TF101 thinks it's a TF101G

I've got a TF101 with prime 2.1.1 installed with 3g enabled. The only problem is my device seems to be reporting to the market as being a TF101G.
As such with today's release of GTA 3 I can't install it as it says its not compatible with my device. However futher down the the list is my TF101 from before I put the new rom on.
Has anyone else seen this and is there anyway I can change it without going back to stock.

just wonder why gta 3 is compatible with tf101 but not with tf101g.... hardware is the same.
very strage and very sag, i have the "g" version. maybe theres a patch in die futre allowing playing on the tf101g
greetings

Silly me posted the same question in General. I'm sorry, and I know I should be whipped good.
But I found a solution to our "G" problem. Flashing the 3G disabler removes the G from the product name. Voilá! GTA3 available!

ive flashed the diabler on three different roms and no luck. everything stays the same. is there something else i need to do or is my tf missing something to make this flash successfully?

Hard to say. I'm not that into the details, it just worked when I did it.

Where is the flashable 3g disabler? Searched but no results.
Thanks

if all else fails, and you have a PRE B70 model and have used nvflash before, replace the included blob (its a tf101g blob) with the tf101 blob thats available on the same page to download...
standard WARNING applys, this will be a WIPE, you will lose ALL DATA, and as far as I know, if the 3G disabler doesn't work, then theres no way around it, but once you have done it, you can flash whatever you like without worry and it will still be listed as a TF101 (its what I had to do a while back when i first got my TF101 and wondered why it showed up as TF101G on my google account)
cheers

EDIT:
Should be working fine ^^
So with other stories in properties it says to be an TF101G but its an TF101, or is it an TF101G then just change to TF101 in build.prop (Which this says what version you got)
but before do a nandroid backup, as in some cases your PAD/Phone wont boot due to some line missing or misspelled (if your very unlucky)
BTW i tried cracked version (Sorry but still i got no credit card to be linked to google market)
but game crashed ^^ but as said it was cracked, and yeah, was Data for Tegra2 Acer (but anyhow)
it should work ^^ Good Luck ill post if i find any solution to your problem, but if the game wont start it will be a H*** to get money back, according to someone it was 15 minutes Max to get money back if it didn't work correctly O___o so sometime's its good to wait for sure

The-Kevster said:
Where is the flashable 3g disabler? Searched but no results.
Thanks
Click to expand...
Click to collapse
Here
http://forum.xda-developers.com/showthread.php?p=17495220

baseballfanz said:
Here
http://forum.xda-developers.com/showthread.php?p=17495220
Click to expand...
Click to collapse
Thanks that's great. I was looking for a CWM file as it is flashable!

Freemantig said:
ive flashed the diabler on three different roms and no luck. everything stays the same. is there something else i need to do or is my tf missing something to make this flash successfully?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showpost.php?p=20347866&postcount=2065

no luck
baseballfanz said:
Try this
http://forum.xda-developers.com/showpost.php?p=20347866&postcount=2065
Click to expand...
Click to collapse
market fix does nothing either. flashed it on prime and android revolution with no change. still shows tf101g and i still cant get my apps. i read that i could replace the blob but to be honest without someone explaining this a little better im not sure how to do this. i would greatly appreciate someone explaining the process possibly with some links to resources. sorry for sounding like a noob but ive never used nvflash and i dont want to just dive in and end up with a brick.

"Failed to unlock your device, Please try again later"....ugh

OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.

its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.

Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.

EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?

turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.

OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably

ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)

Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.

Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.

I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.

EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.

mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!

Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now

OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?

still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?

turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).

bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.

Did you manage to get this working?

[Q] Is it possible to root after jellybean update WITHOUT unlocking?

I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
Thanks for the reply, but i've been working on this for the past couple of hrs and my issue is solved. i'm currently back at 4.1.1 Jellybean again and Root Checker has verified that root is in place. the su binary is also present and all apps that need root work properly (Busybox, Titanium Backup, etc). i've also rebooted and rechecked several times to be sure, it say rooted every time now, whereas it didnt before. I managed to do all of this without unlocking the bootloader as well, even though what i've read elsewhere says it is necessary to do so.
I would have agreed with you before on your point that OTA updates are irreversible, and they usually are, but my experience today shows otherwise. however, you are right that each OTA will probably make it harder to reroot or stay rooted. you're also right that factory reset only wipes data but not firmware, which i just recently figured out today before you posted. i used the "about tablet" section in settings both before and after my steps below to verify that i had indeed downgraded/upgraded firmware/Android versions from JB to ICS and vice versa.
here are the steps i took, in sequential order, so that maybe anyone else with my issue can benefit. i cant gaurantee it will work for everyone:
1. downgraded from 4.1.1 JB firmware to "Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3)". This will roll you back from Jellybean to Ice Cream Sandwich. go to support.asus.com, enter TF700T as the model number, and scroll down until you find this, then download it and unzip the zip file to the root of your sdcard (there is a zip file within the downloaded zip, place that at the root, not the downloaded file itself). if you are using a TF700T that is not US-based then download the appropriate file for your region, just make sure that it has .30 in the file name. I read on a forum somewhere that this is the only firmware update for this device that enables downgrading from higher version to 4.0.3, although it's possible that others may work. then power off your device and do a cold boot (hold down left volume and then followed by power button, do this for about 10 seconds. when you get to the desktop/start screen you will see "Safe Mode" in lower left corner, then your device will notify that an update is available. tell it to apply and let it reboot. when it powers back on you should be back at 4.0.3
2. Do a factory reset, this can be done either before or after the step above, but i did it after. i'm not sure if this is necessary , but just to be on the safe side. back-up all important info, apps, etc beforehand
3. I used the method at Simple Guide to Root TF700T Asus Transformer Pad Infinity : Tips For Tab . this guide can also be found at other websites, but the steps are the same and the files/utilities needed are the same as well. just follow the steps. this will not work if you are still at 4.1.1, you will get the error i detailed in my last post.
4. Download Root Checker (to verify root access) and make sure you have the latest Superuser installed from Play (SuperSU may also work but i'm not sure, i'm using the paid version of Superuser Elite). and also get Voodoo OTA RootKeeper (free), this has a function that will allow you to restore root access after upgrading to 4.1.1. Superuser Elite also has a "ota survival" function that does essentially the same, both worked for me (this software isnt free). and get Busybox and a terminal emulator like Better Terminal Emulator or Android Terminal Emulator. i'm not even sure if these last 2/3 are absolutely necessary, but they install essential must-have functions that all root users should have.
5. then use RootKeeper and make a backup of the su binary, or place a checkmark beside the "ota survival" function in Superuser Elite. either will backup the su info so that it can be restored.
6. Next, do a direct OTA upgrade to 4.1.1 JB , either by using the built-in firmware update function, or by manually downloading from the website and updating using the method listed above. Do NOT do a restore to factory backup state after this point (especially after), it will most likely wipe out the backups of su made by RootKeeper/Superuser Elite.
7. after the upgrade is finished you will be back at start screen at at 4.1.1, use Root Checker and it will say you're not rooted. Then use either of the 2 programs ive outlined to restore the su binary from the backup. in SU(E) just uncheck and recheck the OTA Survival box, or in RootKeeper just restore from backup. Then go back to Root Checker after doing either of these, it should say rooted. reboot and recheck to make sure.
8. That's it! just wash, rinse and repeat when the next firmware update is available, hopefully these same steps should work
Also make sure to keep a backup of the su binaries/app from here onwards, otherwise at some point in the future you may lose the ability to simply restore from backup after each OTA Firmware update. you will have to start over from the beginning.
I'm sure someone figured this out already, but i figured i would post anyways.
Click to expand...
Click to collapse
but i couldn't even downgrade

Beret67 said:
I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
but i couldn't even downgrade
Click to expand...
Click to collapse
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.

hx4700 Killer said:
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.
Click to expand...
Click to collapse
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.

Beret67 said:
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.
Click to expand...
Click to collapse
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.

hx4700 Killer said:
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.
Click to expand...
Click to collapse
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
The link you supplied that has all the firmwares there are several that say 9.4.5.30
The first one is WW, World Wide. You need to make sure you get the correct one for your device. So if you bough retail in the US get the second one that says "US". The firmware will not work if you don't get the correct one.
An easy way to tell what you need is to go to settings and scroll down to "About" on the left. Tap About and on the right half scroll down to "Build Number" My daughters TF201 says JRO03c.US_epad........
So she has the US one and would need the US Firmware.
If you have a US device and tried to apply the WW firmware from what I have read it will fail, won't work.. dead andy. Make sure you have the right firmware for your device.
Please post back your results as I am sure many would be interested if ASUS broke reverting to ICS.

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
After you download the zip file, first you have to UNZIP the zip file and you're going to see another zip file. Now rename this new zip to EP201_768_SDUPDATE.zip , then copy this to the root of your sdcard, boot into recovery and try again.

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
I assumed the file rename was in the directions above

The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Rashar said:
The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.

sbdags said:
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.
Click to expand...
Click to collapse
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.

hx4700 Killer said:
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.
Click to expand...
Click to collapse
Yes kernel tweaking brings huge benefits but there are plenty of other tweaks that bring the perks as well outside the kernel

Hello everyone, I just joined XDA and hope to be a successful contributor to this amazing community. This is my first post, hope it will be of help.
I can confirm that 10.4.4.25 did not break the downgrade option. Like others already suggested, make sure you're using the firmware which matches your device (WW/US/etc.) and you should be fine.
I Just got my device tonight from ASUS (RMA due to crashes every 2.5 days on the clock, black lines every few seconds, extremely laggy).
My precious came with 10.4.4.23 and I upgraded it to 10.4.4.25 to check the performance and black lines issue. With 25 it still lags a little but less than 23 and other earlier firmwares. I ran these tests on 23 then on 25:
1. For real life performance (don't care about synthetic benchmarks) I updated all the apps simultaneously. Both firmwares were laggy but 25 was much less than 23.
2. The black line is still there in 25 but much less than 23. I could reproduce it only with the black hole live wallpaper test which is a very good sign as in 23 I reproduced it a couple of times without the black hole live wallpaper.
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25

G0llum said:
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25
Click to expand...
Click to collapse
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.

ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090

buhohitr said:
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
Click to expand...
Click to collapse
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Edit: Tried going straight to 10.4.4.25 and failed. No OTA either.

ils01 said:
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Click to expand...
Click to collapse
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.

buhohitr said:
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.
Click to expand...
Click to collapse
Thank you very much. Will do that.

ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.

G0llum said:
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.
Click to expand...
Click to collapse
Thanks for the update.
Mine did not see any update regarless of multiple checkings performed (this was done before any rooting attempted). I am in the process of dowloading dlpkgfiles and slowly doing the hard way.
Update: After I reflashed back to 9.4.5.30 to root, I went on and started updating using dlpkgfile started with .16, .18, .20, .23, and finally .25. All is good now. However, I had a few errors when going from .16 to .18 due to getting incorrect/wrong dlpkgfile.
Thank you for everyone's help.

New official firmware ?

I've just had an alert pop up on my 101 saying it's downloaded a new system firmware??
I'm already on .27. Is there a new version or is something going on???

Install it and report back
I wouldn't have thought so, it's been about a year since the last one

*Detection* said:
Install it and report back
I wouldn't have thought so, it's been about a year since the last one
Click to expand...
Click to collapse
Yeah, my first thought was to just let it install and see what I get... But I worried that it'll kill recovery or unroot and I won't be able to get it back??

steve1221 said:
Yeah, my first thought was to just let it install and see what I get... But I worried that it'll kill recovery or unroot and I won't be able to get it back??
Click to expand...
Click to collapse
Yea it might replace recovery and unroot you, you should be able to use Easyflasher to root and flash custom recovery again though, it doesn't care which ROM is installed
Im not seeing any other reports of an update though
If you're rooted, you could pull the update and upload it for people here to check, I can't remember the exact location though, something like /sdcard/asus
EDIT - Possibly this location: "<Internal Storage>\ASUS\Update"
Its been so long since I ran stock I've forgotten where it downloads it to
We used to pull them off the TF and upload them for the devs to incorporate into their custom ROMs

Well, went ahead and let it install.... and I'm still on .27??
Is it possible for the version code to get corrupted and misread by the routine that checks for updates???

Anything is possible with ASUS firmware, I dropped ASUS a long time ago
They dropped us even longer ago

I'm almost tempted to switch back to stock to check. I heard that it will still be .27 but they updated some of the firmware?
Maybe they have fixed my opengl issues... Not gonna get my hopes up.
Can someone verify what's new, if anything?

DeadJenkins said:
I'm almost tempted to switch back to stock to check. I heard that it will still be .27 but they updated some of the firmware?
Maybe they have fixed my opengl issues... Not gonna get my hopes up.
Can someone verify what's new, if anything?
Click to expand...
Click to collapse
Apart from the OP of this thread, there is no-one else reporting an update, I think something just bugged out on his TF and downloaded the .27 update again
ASUS haven't updated the TF101 for a year or more, they aren't likely to start again now, and nothing is on their official firmware page for the TF101 either