Maybe I'm the only one confused (I doubt that though ) but there is a lack of clarity on different elements in the Development section (and others) about what is what.
To clarify (from what I understand:
Asus Firmware Updates
(things you get OTA if you're not unlocked and have nothing to do with Android per se., but Asus's implementation)
.22 was the release
.26 updates the scheduler and a few other things
.30 updated the camera
Was there a different JB release or is that only ROM dependent? There is a lot of talk about moving between .30 and JB.
Some ROMs/Recoveries are for ICS, others for JB, some for both. Which are which?
ex. CM10 is JB based, but will it work on an ICS BL and .26? From what I understand it will. If that is the case, what would be the advantage of updating my firmware? Does the Firmware update the bootloader as well? If I update firmware should it be to .30 and then to JB (see previous question about this)
Now, lets pull in the bootloaders:
TF700 ICS BL
TF300 BL
TF700 JB BL
There are also different guides for updating certain things, but not others. It's all generally confusing.
I'm not trying to piss and moan, I just think that there is a lot of information out there in specific pieces but not all of it connects. Lots of great options exist, but those of us who want to flash better ROMs and different Recoveries also need to understand how they are connected so we don't brick.
Thanks for anyone who can put this all together. I have a feeling it would be a pretty long post .
wolfman87 said:
Maybe I'm the only one confused (I doubt that though )
Click to expand...
Click to collapse
I am also confused, but at a different level, so I can at least clarify some of your points and ask others for more clarification.
wolfman87 said:
Asus Firmware Updates
(things you get OTA if you're not unlocked and have nothing to do with Android per se., but Asus's implementation)
.22 was the release
.26 updates the scheduler and a few other things
.30 updated the camera
Was there a different JB release or is that only ROM dependent? There is a lot of talk about moving between .30 and JB.
Click to expand...
Click to collapse
The ASUS firmware consists of everything your tablet needs - bootloader, Android kernel, recovery kernel, Android apps and custom apps. Some updates may not include new versions of all components. The combination of everything except the bootloader is what most would call "ROM".
The version numbers in your list are 9.4.5.x, and all are based on Android 4.0 (ICS).
The ASUS JB release (Android 4.1) is firmware version 10.4.4.16.
wolfman87 said:
Some ROMs/Recoveries are for ICS, others for JB, some for both. Which are which?
ex. CM10 is JB based, but will it work on an ICS BL and .26?
Click to expand...
Click to collapse
Now it gets interesting. First of all, starting with the bootloader released with 9.4.5.30, Asus changed something in the bootloader that disallows - if I understood it correctly - flashing an unsigned bootloader even on unlocked devices, and that means no downgrade to the .26 bootloader, and more importantly, no way to flash the AndroidRoot bootloader that enables us to create the initial blobs for wheelie and NVFlash.
And there appear to be some incompatibilities between versions of bootloaders and kernels - I would also like to know why exactly.
Also, some recoveries are incompatible either with specific bootloaders, or with some changes in the Android system partition introduced with JB. If anyone could shed some light on this, it would be very appreciated.
wolfman87 said:
Maybe I'm the only one confused (I doubt that though ) but there is a lack of clarity on different elements in the Development section (and others) about what is what.
To clarify (from what I understand:
Asus Firmware Updates
(things you get OTA if you're not unlocked and have nothing to do with Android per se., but Asus's implementation)
.22 was the release
.26 updates the scheduler and a few other things
.30 updated the camera
Was there a different JB release or is that only ROM dependent? There is a lot of talk about moving between .30 and JB.
Some ROMs/Recoveries are for ICS, others for JB, some for both. Which are which?
ex. CM10 is JB based, but will it work on an ICS BL and .26? From what I understand it will. If that is the case, what would be the advantage of updating my firmware? Does the Firmware update the bootloader as well? If I update firmware should it be to .30 and then to JB (see previous question about this)
Now, lets pull in the bootloaders:
TF700 ICS BL
TF300 BL
TF700 JB BL
There are also different guides for updating certain things, but not others. It's all generally confusing.
I'm not trying to piss and moan, I just think that there is a lot of information out there in specific pieces but not all of it connects. Lots of great options exist, but those of us who want to flash better ROMs and different Recoveries also need to understand how they are connected so we don't brick.
Thanks for anyone who can put this all together. I have a feeling it would be a pretty long post .
Click to expand...
Click to collapse
I can't speak for the other guides, but I do try to organize the ROMs by what version they are (JB or ICS), and if there are specfic limiations for recoveries or kernels, i try to note those items too.
As for the moving between JB and .30, or downgrading for various reasons, there were a lot of things people did to port the TF300 ROMs to work on the 700 at the same time a patch came out for the 700 (.30). The combination of these things happening at the same time meant that people had bootloader issues, or had ROMs that limited what they could do long term. I know that does not clarify what they do, but hopefully helps explain why it happened.
I try to keep the directory i maintain updated every day M-F and once during the weekends. If there are specific things you would like to see, please feel free to PM me with details.
OK, here goes with what very little I know. You are correct, as far as I know, in the things you put on there...
NOTE: PLEASE, PLEASE, PLEASE... Call in when you have something to add, correct or detract -- I've had several long, busy, stressful night shifts and I'm bound to have screwed up here and there. Please correct me if so.
ASUS Firmware updates:
* .22 was the release firmware
* .26 changed the scheduler from noop to cfq, smoothing out disk-write performance a bit, alleviating I/O issues to at least some extent; some minor app updates as well, it seems.
* .30 updated camera firmware (removing the clicking sound, amongst other minor fixes). The big thing was it updated the bootloader as well (without notice), which later turned out to prevent installation of Nvflash. This effectively shuts out those who flashed the .30 OTA or .30 manual ASUS firmware files from the added security of Nvflash... for now.
* .16 is the initial JB update
Confusion may stem from our colloquial designation for JB (.16) being out of order with the ICS builds that came before it (.22/.26/.30) -- our tendency to abbreviate anything needing more than three keystrokes has turned to shoot some people in the foot. If, however, you look at the full build number, the difference is quite evident:
.22 = ASUS firmware version 9.4.5.22 = ICS
.26 = ASUS firmware version 9.4.5.26 = ICS
.30 = ASUS firmware version 9.4.5.30 = ICS
.16 = ASUS firmware version 10.4.4.16 = JB
Bootloaders:
I believe any CM10/AOKP-based ROM will happily boot off of both the ICS and JB bootloaders. Currently, however, there seems to be no specific need or benefit to using the JB bootloader, so I'd stay away from it whenever possible.
Recoveries:
* The official ClockworkMod 6.0.1.4 Touch recovery: http://forum.xda-developers.com/showthread.php?t=1926286 and
* The official ClockworkMod 6.0.1.4 Non-touch recovery: http://forum.xda-developers.com/showthread.php?t=1886901
both support ICS and JB bootloaders and carry device-specific fixes for the TF700
* TWRP 2.2.2.3 touch recovery: http://forum.xda-developers.com/showthread.php?t=1797692
supports ICS and JB bootloaders and carry device-specific fixes for the TF700
ROMs, with the criteria as set forth by their devs, updated with users' experience:
* CleanROM Ultra Lite Edition 1.2: http://forum.xda-developers.com/showthread.php?t=1919851
UPDATED: Jellybean bootloader and TWRP 2.2.2.x+ are a preferred combination (by way of its developer), but the (.30) ICS bootloader works as well (thanks, Nebucatnetzer!)
* Stock Root Odex / De-Odex - 10.4.4.16 Base: http://forum.xda-developers.com/showthread.php?t=1919271
REQUIRES JB bootloader and recent version of either ClockworkMod or TWRP (for it, obviously, needs JB support)
* Zeus_TF700T_series_v4.0: http://forum.xda-developers.com/showthread.php?t=1803386
has only been tested by Zeus on TWRP, but can install with ClockworkMod 6.0.1.4.
* Team EOS 3 *JELLYBEAN* Nightlies: http://forum.xda-developers.com/showthread.php?t=1887948
Currently DOES NOT BOOT AT ALL.
* Baked Black Bean 5 - Infinity Edition: http://forum.xda-developers.com/showthread.php?t=1884703
Installs with both ICS and JB bootloaders, and should install with either ClockworkMod or TWRP (have only tested it using TWRP)
* TF700T PARANOIDANDROID 2.17: http://forum.xda-developers.com/showthread.php?t=1904894
Installs with both ICS and JB bootloaders, and should install with either ClockworkMod or TWRP
Individual kernels:
* Mystical Kernel v0.1 for Official TF700 JB: http://forum.xda-developers.com/showthread.php?t=1922747
As the name implies, this is ONLY for JB.
Works with: CleanRom1.x and probably other stock-based ROMs
Does NOT work with: Black Bean v5 -- and therefore probably other CM10/AOKP-based ROMs
NOTE: you will lose ADB as root. This is a very young kernel. (NOTE: 'Immature' has a derogatory feel to it, which I tried to avoid.)
* Nice link aggregate how-to of STOCK ICS (.26 and .30) and STOCK JB (0.16) kernels and UNOFFICIAL CM10 kernels, and boot restore how-to added in for good measure, courtesy of Pretoriano80: http://forum.xda-developers.com/showthread.php?t=1919961 and http://forum.xda-developers.com/showthread.php?t=1833212 as well.
Loose ends:
I think a lot of the confusion stems from the fact that, in and of themselves, kernels and recoveries are interdependent, but not equivalent -- several times something was posted along the lines of "JB recovery kernel". It's probably best to stay on the ICS bootloader if you can help it, and only update it when you really need to (which doesn't actually seem to have been the case, yet). If it ain't broken, don't fix it.
MartyHulskemper said:
Bootloaders:
I believe any CM10/AOKP-based ROM will happily boot off of both the ICS and JB bootloaders.
Click to expand...
Click to collapse
Thanks for writing all of this amongst a busy schedule - it's happening to me top (XDA is a nice short release during the day when I have a free minute )
When you say both ICS and JB Bootloaders, do you mean .26 and .30 respectively (since those are the ROMs that came bundled with them)?
numbers v. names is another thing we can add to the confusion pile
MartyHulskemper said:
* CleanROM Ultra Lite Edition 1.2: http://forum.xda-developers.com/showthread.php?t=1919851
REQUIRES Jellybean bootloader and TWRP 2.2.2.x+
Click to expand...
Click to collapse
It's suggested buy the dev but it doesn't actually need the Jellybean bootloader.
I'm running .30 and it works without a problem so far.
Nebucatnetzer said:
It's suggested buy the dev but it doesn't actually need the Jellybean bootloader.
I'm running .30 and it works without a problem so far.
Click to expand...
Click to collapse
Ouch -- managed to get Nvflash beforehand or have we lost you? :fingers-crossed:
---------- Post added at 02:36 AM ---------- Previous post was at 02:25 AM ----------
wolfman87 said:
Thanks for writing all of this amongst a busy schedule - it's happening to me top (XDA is a nice short release during the day when I have a free minute )
When you say both ICS and JB Bootloaders, do you mean .26 and .30 respectively (since those are the ROMs that came bundled with them)?
numbers v. names is another thing we can add to the confusion pile
Click to expand...
Click to collapse
Good point! Actually, the answer would be 'no' -- I updated my reply above to answer this; I'll add it here for the sake of chronology and readability -- the first three (.22/.26/.30) contain ICS bootloaders, and the first (and as of now only ) JB bootloader is .16, so, as above:
.22 = ASUS firmware version 9.4.5.22 = ICS
.26 = ASUS firmware version 9.4.5.26 = ICS
.30 = ASUS firmware version 9.4.5.30 = ICS
.16 = ASUS firmware version 10.4.4.16 = JB
Note that the confusion stems from us having called the first few firmwares by their incremental build number -- this is what is currently shooting some people in the foot. If, however, you look at the full build number, the difference is quite evident.
Marty and Wolfman, thanks for the question and thanks for the summary. I try to keep the links in one place, but also see all the confusion! I have taken liberty of referencing this thread, and copying part of it into the Directory thread that I maintain.
Hope that you don't mind!
MartyHulskemper said:
OK, here goes with what very little I know. You are correct, as far as I know, in the things you put on there...
NOTE: PLEASE, PLEASE, PLEASE... Call in when you have something to add, correct or detract -- I've had several long, busy, stressful night shifts and I'm bound to have screwed up here and there. Please correct me if so.
ASUS Firmware updates:
* .22 was the release firmware
* .26 changed the scheduler from noop to cfq, smoothing out disk-write performance a bit, alleviating I/O issues to at least some extent; some minor app updates as well, it seems.
* .30 updated camera firmware (removing the clicking sound, amongst other minor fixes). The big thing was it updated the bootloader as well (without notice), which later turned out to prevent installation of Nvflash. This effectively shuts out those who flashed the .30 OTA or .30 manual ASUS firmware files from the added security of Nvflash... for now.
* .16 is the initial JB update
Confusion may stem from our colloquial designation for JB (.16) being out of order with the ICS builds that came before it (.22/.26/.30) -- our tendency to abbreviate anything needing more than three keystrokes has turned to shoot some people in the foot. If, however, you look at the full build number, the difference is quite evident:
.22 = ASUS firmware version 9.4.5.22 = ICS
.26 = ASUS firmware version 9.4.5.26 = ICS
.30 = ASUS firmware version 9.4.5.30 = ICS
.16 = ASUS firmware version 10.4.4.16 = JB
Bootloaders:
I believe any CM10/AOKP-based ROM will happily boot off of both the ICS and JB bootloaders. Currently, however, there seems to be no specific need or benefit to using the JB bootloader, so I'd stay away from it whenever possible.
Recoveries:
* The official ClockworkMod 6.0.1.4 Touch recovery: http://forum.xda-developers.com/showthread.php?t=1926286 and
* The official ClockworkMod 6.0.1.4 Non-touch recovery: http://forum.xda-developers.com/showthread.php?t=1886901
both support ICS and JB bootloaders and carry device-specific fixes for the TF700
* TWRP 2.2.2.3 touch recovery: http://forum.xda-developers.com/showthread.php?t=1797692
supports ICS and JB bootloaders and carry device-specific fixes for the TF700
ROMs, with the criteria as set forth by their devs, updated with users' experience:
* CleanROM Ultra Lite Edition 1.2: http://forum.xda-developers.com/showthread.php?t=1919851
UPDATED: Jellybean bootloader and TWRP 2.2.2.x+ are a preferred combination (by way of its developer), but the (.30) ICS bootloader works as well (thanks, Nebucatnetzer!)
* Stock Root Odex / De-Odex - 10.4.4.16 Base: http://forum.xda-developers.com/showthread.php?t=1919271
REQUIRES JB bootloader and recent version of either ClockworkMod or TWRP (for it, obviously, needs JB support)
* Zeus_TF700T_series_v4.0: http://forum.xda-developers.com/showthread.php?t=1803386
has only been tested by Zeus on TWRP, but can install with ClockworkMod 6.0.1.4.
* Team EOS 3 *JELLYBEAN* Nightlies: http://forum.xda-developers.com/showthread.php?t=1887948
Currently DOES NOT BOOT AT ALL.
* Baked Black Bean 5 - Infinity Edition: http://forum.xda-developers.com/showthread.php?t=1884703
Installs with both ICS and JB bootloaders, and should install with either ClockworkMod or TWRP (have only tested it using TWRP)
* TF700T PARANOIDANDROID 2.17: http://forum.xda-developers.com/showthread.php?t=1904894
Installs with both ICS and JB bootloaders, and should install with either ClockworkMod or TWRP
Individual kernels:
* Mystical Kernel v0.1 for Official TF700 JB: http://forum.xda-developers.com/showthread.php?t=1922747
As the name implies, this is ONLY for JB.
Works with: CleanRom1.x and probably other stock-based ROMs
Does NOT work with: Black Bean v5 -- and therefore probably other CM10/AOKP-based ROMs
NOTE: you will lose ADB as root. This is a very young kernel. (NOTE: 'Immature' has a derogatory feel to it, which I tried to avoid.)
* Nice link aggregate how-to of STOCK ICS (.26 and .30) and STOCK JB (0.16) kernels and UNOFFICIAL CM10 kernels, and boot restore how-to added in for good measure, courtesy of Pretoriano80: http://forum.xda-developers.com/showthread.php?t=1919961 and http://forum.xda-developers.com/showthread.php?t=1833212 as well.
Loose ends:
I think a lot of the confusion stems from the fact that, in and of themselves, kernels and recoveries are interdependent, but not equivalent -- several times something was posted along the lines of "JB recovery kernel". It's probably best to stay on the ICS bootloader if you can help it, and only update it when you really need to (which doesn't actually seem to have been the case, yet). If it ain't broken, don't fix it.
Click to expand...
Click to collapse
Thanks Alot for this very helpfull post
Can this post be added to a sticky and be updated when new roms are released, this info would help so many searching for answers
NeoGodSpeed said:
Thanks Alot for this very helpfull post
Can this post be added to a sticky and be updated when new roms are released, this info would help so many searching for answers
Click to expand...
Click to collapse
I would say that some of that guidance is a bit out of date, but it is very nicely organized!
First, think whether you will want to go with stock-based roms. CleanROM Inheritance v2.5.1 is the latest and greatest version of the TF700 Infinity's stock-based offerings and this has the Aroma installer and has Clemsyn's overclocked kernel as an option during the install process. For this ROM, it is a good idea to use the latest TWRP recovery (install through Goomanager) but CWM is OK too. Another offshoot of scrosler's original CleanROM is being supported through the original CleanROM thread. The ROM I had tried was very nice.
If you would rather go Cyanogenmod-way, then you have the official CM ROM, you also have CM based Paranoid Android, Baked Black Bean and LiquidROMs. You also have Clemsyn's CM kernels, and CWM recovery. I think it's best to stick with CM/AOKP/AOSP--or--stock-based. They're like complete systems. There are other offerings too, and I don't mean any disrespect if I've missed any currently supported ROMs here, but there are a few that don't appear to be current anymore.
Good luck!
Related
Hi All,
A few questions about my xoom, but first here are the details
-Canadian Wi-fi Xoom, but flashed to USA for ICS update
-Rooted of course, I see Rom Manager, CWM, and Adfree as programs the previous owner has added.
-Looks like stock rom: Android 4.0.3,
-Kernel 2.6.39.4-gf03a679 , [email protected]#1
-Build number IML77
Since I am new to this, and my android education will come to flashing and optimizing my setup, should I change anything about what I currently have?
So far everything seems to work properly, would I be able to accept OTA updates without risk of bricking things?
Seems the previous owner removed his account info, but would I have any security concerns from things he may have left behind?
It seems I am going to spend more time learning the platform than actually using it, and this greatly interests me. I thank all in advance for your help.
Cheers
Canadian owner here also
Official OTA's will not install on a rooted device, as for security concerns. You could always do a fastboot erase userdata/cache/system reinstall an official motorola from (available on their website).
Use the universal root for Xoom, flash the recovery and use one of the currently available rom (rogue, EOS, Alfonso). Im pretty sure any left over from previous owner will be gone by then!
Pretty much all of it explained in the thread: Xoom Heaven: Rooting, Roms, Kernels... You Name It!
That's just me tho!
Or just flash the correct EOS nightly (wingray) followed by the newest GApps (10.5).
The Unofficial Transformer Infinity(TF700) ROM & Kernel Listings v 2.0
Updated 10/23/2013
It is finally time for a complete re-write of the guide, so here goes. Hopefully this will make it easier to follow and use!
HOW-TOs
Rooting & Tuning/Tweaking 1
Rooting & Tuning/Tweaking 2
Unlocking
Development Guide
I take no credit for the work represented here, and no credit for the idea, and no credit for incredible amount of work that has gone into figuring out how to cook tasty ROMs for the TF700. This is just an attempt to provide a quick and easy starting point for users looking for ROMs and their details.
If you have any [ROM/KERNEL] specific question ask in the appropriate thread for that. Please do not post them in the thread for this listing as you are not as likely to get your question answered as quickly as you would in the appropriate thread.
Glossary
Rooting: This is an operation that you do to a device that gives you "Root" level access to your tablet or phone or whatever. Other terms for this may be "SuperUser", it means you have access to the entire device, including areas that the manufacturer or provider may not want you to have access to.
Unlocking: Unlocking is the step past rooting, where you "unlock" your bootloader. This gives you full access to the bootloader, and is the second part required in order to be able to flash new ROMs. **MAY VOID MANUFACTURER WARRANTY
OTA: Over the Air Updates. These are the ROM updates that come directly from ASUS (or whomever built your tablet). When you root and flash you almost always lose OTAs.
Flash (or Flashing): This is where you replace the Operating System for the device with a new one. There are many reasons for flashing, Google has lots of discussions about the topic.
Bootloader: Computers have a process when you turn them on, the first part is the Bootloader which contains just enough information to tell the device where the harddrive is, etc. Accessing the bootloader is required in order to replace the ROM, or in other words to Flash your device.
Recovery: This is an important part of the Android system, it allows you to turn on the device and get ALMOST to the full ROM load. Recovery is where you go to load custom ROMs, perform full backups and many other tasks. There are several different recovery apps, two of the most popular are CWM or ClockworkMod and TWRP. Most of the ROMs you will see are supported by one or both of these.
Hopefully this little bit of information helps, of course the opinions and answers are mine alone so if you have any issues let me know!
Current ROMs
4.3 based ROMs
CMB ROMs TF700: CM Based ROM with a dark theme.
CyanogenMod 10.2 Nightlies: Official nightly 4.3 builds
PAC-man AIO Offical:: Hybridized ROM combining CM Nightlies, AOKP and Paranoid Android ROMs
4.2 based ROMs
CROMi-Xenogenesis (5.1.1): This is a true 4.2.x ROM for the TF700 with all sorts of goodies
Paranoid Android 3.69 (HALO): PA 4.2 based ROM for tablets and phones. Tons of control over everything.
HAIRYBEAN Unleash the Beasthttp://forum.xda-developers.com/showthread.php?t=2225264: A new JB 4.2.1 based ROM for the ASUS Tablets.
Cornerstone Bryce_ROM: Built off the CM10.1 nightlies using Cornerstone. Provides multiwindow capabilities.
Baked Black Bean 8:Latest and greatest from teamBAKED. Dark Bliss Black KANG ROM.
Official CM10.1: Cyanogenmod 10.1 Nightlies for the TF700. Now updated to the 4.2.2 Build
TF700 Stock Upgrade (Bootloader and 4.2.1): The newest ROM from ASUS, including 4.2.1!
4.1 based ROMs
CleanROM Inheritance 3.4.7: Deodexed OC ROM based on scrosler's ROMs.
TF700 Stock ROM - JB 10.4.4.25: Odex version of the Stock ASUS ROM, taken from the WW version but modded for any locale.
Linux Ports for the TF700
Multiboot Linux for Infinity TF700http://forum.xda-developers.com/showthread.php?t=2026919evelopers thread for the WIP Linux port for the TF700
Native Arch Linux for TF700thttp://forum.xda-developers.com/showthread.php?t=2222710:WIP for 3.4.7 CROMI-based tablets. Currently on-hold while dev works on kernel for CROMi-X
Ubuntu for Infinity: A dev build of Native Ubuntu Linux
Native Ubuntu on TF700 Lubuntu, LXDE Unity2D, Gnome for the Infinity!
Kernel Packs
10.6.1.14.4-that Kernelhttp://forum.xda-developers.com/showthread.php?t=2222301: Great, stable and fast for 4.2 ROMs on the new bootloader
10.6.1.14.4-that2 Kernelhttp://forum.xda-developers.com/showthread.php?t=2230059: Tweaked and improved version of Asus kernel
MaxKernelhttp://forum.xda-developers.com/showthread.php?t=2230856: CROMi Overclocked Kernel with lots of tweaks
Hundsbuah Kernel: Great and Stable Kernel from Hundsbuah
Bryce Kernel: Updated and changed version of the CM10.x kernel. Verified on PA and LiquidSmooth ROMs
3.1.10 Kernel + CIFS + ROW: A new kernel with some of the new experimental features.
Tweaks
Data2SD Enhanced A different approach and solution to improve I/O
Extended Power Menu: Adds the option to Reboot or Reboot into Recovery. Only for JB 4.1.1 ROMs. for .16 or .18 Based ROMs
Infinity Tweaks: Some performance, root and other tweaks
Disabled Scrolling Cache: A performance tweak for deodexed ROMs that may improve lag.
Recovery and Backup
TWRP 2.5.0.0 Recovery: Touch-based recovery tool with on-screen keyboard.
[TOUCH]ClocworkMod Recovery 6.0.3.0http://forum.xda-developers.com/showthread.php?t=1926286: Touch enabled version for JB ROMs and bootloaders.
[NON-TOUCH]ClockworkMod Recovery 6.0.3.0 A version of CWM for the TF700, used for backups and ROM Installation
NVFlash for the TF700: NVFlash is a great utility that basically eliminates almost any chance of a software brick due to flashing or updating ROMs and Kernels.
Unlocking/Rooting/Restore Guides
All in one ADB Tool: A veritable swiss army knife tool, automates updates, backups and other functions.
Guide/Tool - Update to Official JB then Root: A guide to upgrading and rooting JB ROMs from the developer of Scott's ROMs
Manual Firmware Update using dlpkgfile: Guide for those that want OTA but have unlocked
Restore Root if Lost After Upgrade to JB: For those that lost Root after they upgraded.
All-in-One Guide for Asus Infinity: So this is the mac-daddy of posts, one stop to root, flash, and unlocking. Well written, well laid out and easy to follow.
Restore to Stock Recovery: For unlocked bootloaders, allows you to go back to the stock recovery and receive OTAs
Resource Guide: Quick Reference Resource Guide
Bootloader Unlocker: Links and instructions to unlock your Bootloader
How to Manually Update Firmware: Explains how to manually perform OTAs
There is an excellent thread started by Wolfman87 over in the Q&A Section talking about the confusion around OTAs, bootloaders and recoveries. The entire thread can be viewed here: http://forum.xda-developers.com/showthread.php?t=1927095
I have taken the liberty of cross-posting an excellent summary by MartyHulskemper on the basics
ASUS Firmware updates:
* .22 was the release firmware
* .26 changed the scheduler from noop to cfq, smoothing out disk-write performance a bit, alleviating I/O issues to at least some extent; some minor app updates as well, it seems.
* .30 updated camera firmware (removing the clicking sound, amongst other minor fixes). The big thing was it updated the bootloader as well (without notice), which later turned out to prevent installation of Nvflash. This effectively shuts out those who flashed the .30 OTA or .30 manual ASUS firmware files from the added security of Nvflash... for now.
* .16 is the initial JB update
Confusion may stem from our colloquial designation for JB (.16) being out of order with the ICS builds that came before it (.22/.26/.30) -- our tendency to abbreviate anything needing more than three keystrokes has turned to shoot some people in the foot. If, however, you look at the full build number, the difference is quite evident:
.22 = ASUS firmware version 9.4.5.22 = ICS
.26 = ASUS firmware version 9.4.5.26 = ICS
.30 = ASUS firmware version 9.4.5.30 = ICS
.16 = ASUS firmware version 10.4.4.16 = JB
Bootloaders:
I believe any CM10/AOKP-based ROM will happily boot off of both the ICS and JB bootloaders. Currently, however, there seems to be no specific need or benefit to using the JB bootloader, so I'd stay away from it whenever possible.
Older ROM links
Older/Decommed ROMs - Archived Tweaks
Stock Rooted Odex 10.4.4.23: Pre-rooted ROM Based almost completely on the ASUS Stock ROM. Adds some new camera libs.
Paranoid Android 3.0 RCIE: AOSP 4.2.1 release with a Tablet UI
LiquidSmooth JB 4.1.2 RC8: Latest and greatest AOSP based ROM
Stock Rooted De-Odex / Odex: A new ROM from Scott based off the 10.4.4.20 ASUS update
[JB4.1.1] 10/18 Stock Root Odex/De-Odex: Based on the official ASUS 10.4.4.18 Base ROM from Scott's ROMs
CleanROM 2.3 - The Infinity Unleashed!: Minimalist ROM based on 4.1.1 JB Stock ROM. Tweaked for minimal bloat and maximum speed.
Stock ODEX and Rooted ROM: Stock ROM based off the 10.4.4.16
ParanoidAndroid 2.53 [ROM-ALPHA]: A hybrid PerApp ROM for tablets and phones.
Team EOS ROM for the TF700 Nightlies: A Team EOS port, we have been added to the list of their nightly builds.
Mysticial ROM v1: A "ported" version of the TF300 ROM tweaked for the Infinity
Baked Bean 7.1(tf700t)[JB 4.2.1]: An AOSP Based ROM with lots of goodies!
Unofficial CM10 Builds 10/18[Alpha]: Unofficial nightly build from Hiemanshu.
TF300 JB ROM on the TF700 This is a discussion about installing the JellyBean build for the TF300 on the Inifinity.
[AOSP]4.1.1 Pure AOSP Build (pre-Alpha): You need TWRP, and it is pretty hacked, but a new ROM for the Infinity!
CyanogenMod 10 Unofficial 4.1.1 (Round 3): Experimental CM 10 Build
CM10 TF700: A WIP CM 10 Build for the Infinity
.30 Firmware Update: The Official ASUS update for the firmware, contains some different system tweaks. Not JB, and do not use if you are planning on installing NVFlash
Zeus TF700T Series v 4.0 ONLINE: Stock with Full Add-ons
Stock US 9.4.5.26 with Root: Vanilla deodexed, rooted ROM with Busybox included
CWM Repackaged OTA 9.4.5.26: Repackaged OTA for those that have either unlocked or rooted and are using CWM
Maniacs ROM: Built off of .26, this is a base ROM from Maniac.
9.4.5.26 with Tweaks: Deodex, rooted, busybox, debloated, tweaked with BeatsAudio added
Stock 10.4.4.25 Kernel + insecure +init.d + nodpi: The kernel from the latest ASUS Rom for those that want to tinker, or for people that only want the new kernel.
Clemsyn's Kernel for TF700: Overclock to 1.8ghz or run at 650 GPU
Data2SD - I/O Boost: Makes changes to the RAM disk configuration to address I/O performance
root.zip ChainsDD Superuser.apk: That's right, a version of ChainsDD superuser built specific for the TF700.
Mystical Kernel v0.1: Provides a true root, and also allows for changing lcd density. More to come as well.
Transformer ADB v6 with Flash Recovery: Provide a nice ADB-based tool to flash recoveries, unlock or update from your PC.
Blob Tool : This is a tool for working with Blob files, makes building and deconstructing much quicker.
Complete Flash Layout: Complete analysis and deep dive of the Flash Layout of the tablet.
Boot Partition Restore: A Fix to restore the Boot Partition with CWM/TWRP
I look forward to this thread filling up with awesome ROMs and such.
The Rooting utility is the easiest way to root a Transformer Infinity: Beginners can read out this tutorial, http://tutznet.com/root-tf700t-asus-transformer-pad-infinity.html
Utkarsh.bhatt12 said:
The Rooting utility is the easiest way to root a Transformer Infinity: Beginners can read out this tutorial, http://tutznet.com/root-tf700t-asus-transformer-pad-infinity.html
Click to expand...
Click to collapse
It's just sparkym3's Debugfs method, which is linked on the site you linked to, so no need for an intermediary really.
Updated with new ROM and other link updates
Updated to include the TF300 install links for brave souls.
Not one but TWO new ROMs in the past 24 hours!!! Hopefully a great sign of things to come.
So, i moved this thread back to Development since it is well updated and i think that this can cohabit with the other sticky thread hence do not report this to us.
Hmm. I didn't get a request to confirm the uid & gid. Superuser's there & Root Explorer works but Titanium & Root Checker both think I'm not rooted.
Curses. Foiled, and I would've gotten away with it if it wasn't for those kids and that mangey dog.
I need to unroot in order to unlock my tablet.
Can that be done ?
Thanks!!!
Deeds4sure said:
I need to unroot in order to unlock my tablet.
Can that be done ?
Thanks!!!
Click to expand...
Click to collapse
You do not need to unroot to unlock the bootloader.
urrlyx said:
You do not need to unroot to unlock the bootloader.
Click to expand...
Click to collapse
Hi,
I'm having troubles unlocking the bootloader, i wrote ASUS VIP support, and told them my troubles.
I'm getting an error when running the unlock tool " An unknown error occurs....this may be a network issue...:"
I was told by ASUS support that i should manually update which i did, and then i needed to unroot, otherwise they thought i'm having troubles communicating with the ASUS unlock servers.
Thanks for your time, i'm dreaming of the day when i can have a custom ROM on my infinity tablet
factory reset
Can I do factory reset after I rooted my pad?
Will it work right after it? Would I can to get official updates?
Deeds4sure said:
I need to unroot in order to unlock my tablet.
Can that be done ?
Thanks!!!
Click to expand...
Click to collapse
Deeds4sure said:
Hi,
I'm having troubles unlocking the bootloader, i wrote ASUS VIP support, and told them my troubles.
I'm getting an error when running the unlock tool " An unknown error occurs....this may be a network issue...:"
I was told by ASUS support that i should manually update which i did, and then i needed to unroot, otherwise they thought i'm having troubles communicating with the ASUS unlock servers.
Thanks for your time, i'm dreaming of the day when i can have a custom ROM on my infinity tablet
Click to expand...
Click to collapse
NarkotiZ said:
Can I do factory reset after I rooted my pad?
Will it work right after it? Would I can to get official updates?
Click to expand...
Click to collapse
I just want to tell you that it's not a Questions-Answers thread.
If you need to ask some questions about your problem, post your questions in the specific thread or Transformer TF700 Q&A
Thanks
added information covering the basics for Bootloaders and ROM versions from the Q&A Thread, very useful stuff
Should update the "how to root" portion with the fact that JB has not easy root method
I keep getting errors when trying to root with this method. Is it because im on JB? Do you have to be on Ice cream sandwich to use this method?
qiuness said:
Should update the "how to root" portion with the fact that JB has not easy root method
Click to expand...
Click to collapse
JB is easy to Root :victory:
Check this thread
Click
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.
I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
brennen.exe said:
I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
Click to expand...
Click to collapse
This is how I did it this afternoon on my new TF300T:
Rooted ICS with this: http://forum.xda-developers.com/showthread.php?t=1704209
Installed supersu: https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Updated su binary using supersu
Installed OTA rootkeeper: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Backed up su with OTA rootkeeper
Installed ES File Explorer(you really don't have to do this but I wanted to make sure some other app had root access before I upgraded to JB)
Made sure supersu authorized all these root apps by running them at least once.
Upgraded to Jelly Bean
Restored root access with OTA rootkeeper
Wiped the sweat from my brow afterwards!
I am staying with stock JB locked to keep getting OTA updates. If you want a custom rom, you need to unlock:
http://forum.xda-developers.com/showthread.php?t=2055886&highlight=unlock
Unlock APK is here: http://forum.xda-developers.com/showthread.php?t=1949758
NOTE: If you upgrade to Jelly Bean without OTA rootkeeper in place, you will not be able to root it without unlocking it first. There is no root exploit yet for the TF300 Locked Jelly Bean.
Yep. This will do the trick.
Still Charged Up
bads3ctor said:
This is how I did it this afternoon on my new TF300T.
Click to expand...
Click to collapse
Thanks badsector, I'll give it a go today and report back how it went.
Alright, thanks for the help in getting started, but I forgot to mention I had unlocked the tablet beforehand as a first step to another guide, so OTA updates were a no-go for me with this approach. What I ended up doing was, after performing 1-7 from your list, install TWRP using fastboot, manually install the JB update from ASUS, install TWRP for JB (again w/ fastboot), and then load a custom ROM. I'm all up to date and running fine, and had I intended to stay on the stock ROM I could have just left it at that when I flashed the ASUS firmware.
Thanks again!
It's been a while since i've played with android, but I just want to load a fully functioning custom ROM.
Info (from about tablet)
Model Number
TF300TAndroid Version
4.2.2Kernel Version
3.1.10-10.4.2.20AOKP Version
fully_aokp_tf300t_unofficial_Mar-03-13
Info from bootloader screen
cardhu-user bootloader 1.00 e
ww_epad-10.4.2.20-20121228 A03This bootloader has the 4 icons (includes the USB fastboot icon)
Recovery:
TWRP 2.5
The tablet is actually a TF300TG, but all the roms seems to be for the TF300T and I read some posts saying the only thing you lose by cross flashing is the 3g functionality - although, I also read some stating not to.
Q1. It says it's running Android 4.2.2, but the bootloader is still the old JB type - is this because it's a custom rom?
Q2. Is there anything I can do to get WiFi working on this ROM? The wifi never moves to the 'on' position.
I followed the instructions from the link in the bellow quote (the first time around I was on the new bootloader) - I tried flashing both
ASUS Transformer Pad TF300T Firmware: V10.4.2.20 Only for WW SKU (Android 4.1) - 2013.01.18 update
ASUS Transformer Pad TF300TG Firmware: V10.4.3.9 Only for WW SKU (Android 4.1) - 2012.11.14 update
and then installing AOKP, but this just leaves me back where I started.
This ROM is really nice and I would like to continue using it.
The wifi works when using the asus stock software, and I believe it also worked when trying the Hydra ROM.
Many Thanks in advance.
wetbiker7 said:
luishawk said:
But will it work on roms with 4.2.1 bootloaders?
Click to expand...
Click to collapse
Surdu got this ROM to boot on the new bootloader but wifi doesn't work yet. I would wait on him to post the steps needed to get everything working correctly. I have a feeling that it won't be long before he has the newer version ready.
If you can't wait and want to run this ROM with everything working then you can downgrade back to the 4.1 bootloader.
Here is the thread that will tell you how to downgrade the bootloader if you decide to do so.
http://forum.xda-developers.com/showthread.php?t=2195883
Click to expand...
Click to collapse
Q1: You can still run Android 4.2.2 on the stock 4.1.1 bootloader, and you still are using the stock 4.1.1 bootloader. CM10.1 and AOKP do this.
Q2: When you flashed AOKP (which i used for a few months), did you format cache/dalvik/factory reset?