Database Info

[Q] ClockWork : upgrade, downgrade...

Hi there!
I'm a owner of a TF101 (B50) for month now, and recently I had the need to switch between multiple version of Android (as I'm an Android dev) : back and forth to/from Honeycomb from/to ICS for example, multiple time a day!
So, as I'm used to do with all my "Google's Experience" devices (Nexus S, Galaxy Nexus), I installed CWM on my TF101 to be able to generate nandroid. So far, so good.
I then downgraded my tablet to stock 3.2 using nvflash, installed CWM, and did a nandroid. Great, I now have an Honeycomb backup. Of course, at this point, I'm no more able to upgrade using OTA, so here's my first question :
1- Once CWM installed, how do you upgrade to the latest build ? Asus blobs are not compatible with CWM!
Then, since I needed an ICS nandroid, I reverted to stock 3.2 (using NVFLASH), and I let the OTA did the job for me - before installing CWM. Ok, now, I have both Honeycomb and ICS as backup : let's test that.
I rebooted in recovery, and then restored my 3.2 nandroid (from ICS, remember?). All I had once the job was done, was the android logo with an exclamation mark
After some Googling, I understood why : unlike my Google's devices, on the TF101, it seems CWM can't restore the boot partition. So, the bootloader used was the one for ICS, and the tablet failed to boot.... Here's my 2nd question :
2- Am I right? What guys are you suggesting to be able to switch easily between different nandroid versions ? Should I nvflash the boot partition by hand? If so, where to find a documentation on NVFLASH ? (I'm regretting fastboot )
Thanks for reading.

You can repackage the blobs so that they can be flashed from cwm. I think one roach's 3201 recovery is packaged this way, so you can take it apart to see how it all works. Essentially blobs are flashed through the staging partition. There is a blob tools thread in the dev section that has all the details.
If you want to go back and forth between roms, I think that nvflash will be your best bet. Rayman and bubble bee have the most info. Check out therenwebsite. It's something like androidroot.mobi? There is also a full backup and restore thread in the dev section that explains a lot of the details of nvflash.
sent from my transformer

I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?

nono240 said:
I read, somewhere, that we can flash stock Asus firmwares using CWM ('update zip') by first extracting the initial zip (which contains another zip containing the blob). Is it true?
Click to expand...
Click to collapse
yes but you will loose root and cwm recovery. It's the easy unroot method.

Not a big concern. I can easily recover both root and CWM using the universal root method since I have a B50!
Thanks

Will you lose root/cwm even if you have OTA Rootkeeper installed?

You Shouldn't but no guarentees x)

[Q] Question on ICS to JB update - Bootloader or Full?

Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
mikaole said:
just fastboot TWRP for ICS and then flash the 1st JB StockRom(dl from Asus and unzip once) in TWRP.
Then fastboot TWRP for JB, then flash the latest JB StockRom(dl from Asus and unzip once) .
Then fastboot TWRP for JB and then the Rom you like
Click to expand...
Click to collapse
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?

I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD

bsaman said:
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Thanks! So you were going from another set of instructions but ended up just flashed twrp-jb and installed the unzipped zip of Asus JB release via TWRP (I left out the revert to ICS part since I'm already there)? And do you have nvflash installed? No issue running the JB version of TWRP prior to upgrading to JB (had thought bootloader or ... would have an issue with it)? Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.

wha2do said:
Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
Click to expand...
Click to collapse
I think you're right... I was on BB6 w/ICS bootloader (NVflashed, though I don't think it matters) and had to roll back to ASUS ICS ROM first, then rooted, then upgraded to ASUS JB ROM, and then it goes blurry. Not sure if I upgraded TWRP or rooted stock JB at this point.
In any case, I followed the "update to JB" thread to a tee, and all went well except for the step regarding the actual JB update.
Sent from my Transformer Pad TF300T using Tapatalk HD

wha2do said:
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
Click to expand...
Click to collapse
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.

tobdaryl said:
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
Click to expand...
Click to collapse
Thanks for the info. To add to your one comment (for others that may come across this looking for add'l info), flashing a full stock rom will overwrite any custom recovery previously in place. TWRP (using the appropriate version for your firmware) or CWM will need to be reflashed again...
Checking, it does appear v10.4.2.9 is the first version of JB on the TF300T.
I've come across at least one or more posts/guides that mention ICS v9.4.3.30 should be installed before updating to JB - one being: [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]. I'm wondering if it's because that method updates to JB using the dlpkgfile (not sure what format it is)?
My take is doing the additional flash to v9.4.3.30 first can't hurt anything, but quite possibly unnecessary here? Any other thoughts or words of warnings from anyone? Thanks!

Install TWRP & CWM Side by Side & Radio Files?

I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473

Just flash it with twrp. It'll work just like if you did it with cwm.

I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949

Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4

lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.

I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.

I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky

Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!

lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.

I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?

lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky

lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4

I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?

Or you can use Odin.
Sent from my HTC One using Tapatalk 4

So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.

I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk

Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.

[Q] reboot loop after flashing the PAC-MAN rom, but can still enter recovery

I have my TF300T with official rom, but unlocked and installed TWRP 2.3.3 about 1 years ago,
after that I didnt do anything special liking flashing rom except regular use
Yesterday, my wife complained the tablet is too slow, so i tried to flash the customized rom PAC-ROM 4.3, then my device enters reboot loop.... and it hangs at the ASUS logo for about 30 second for every reboot.
since I still can enter recovery and run TWRP, so i searched around and followed some posts by doing wipe system, factory reset, reflashing multiple times....but nothing helped. I also did the wipe data button on the recovery menu besides the RCK, but after reading some posts, i am afraid that i softbricked my device by doing that.
however, now i still can enter TWRP, but dont know what to do to restore my device, I wish some one can help me here by giving some suggestions
I would also to know the cause of the failure, my device is running the offical 4.1 ROM, and i followed exactly the steps mentioned by the post on PAC_MAN, Is that because my TWRP is too old?

shelper said:
...i tried to flash the customized rom PAC-ROM 4.3, then my device enters reboot loop....
...my device is running the offical 4.1 ROM...
Click to expand...
Click to collapse
There is two version of JB bootloaders. It looks like You have an older one and all current custom roms require new one. So here is Your mistake. To unbrick Your device it need to be reflashed to 4.1 stock rom. Then, if You still need to flash pac-rom, upgrade to 4.2 stock rom first.

Thanks so much!
i just want to confirm, since i already did wipe data button, do i need to goto fastboot to push the stock rom?
or i can just flash the 4.1 stock (or customized rom) using twrp?
in addition,how should i upgrade to 4.2 stock rom? can you refer me a thread?
thanks again!:good:
Graiden05 said:
There is two version of JB bootloaders. It looks like You have an older one and all current custom roms require new one. So here is Your mistake. To unbrick Your device it need to be reflashed to 4.1 stock rom. Then, if You still need to flash pac-rom, upgrade to 4.2 stock rom first.
Click to expand...
Click to collapse

I think fastboot is prefered to restore 4.1 stock. And IMHO best way to upgrade to 4.2 is stock recovery.

sorry that i am a newbie without much experience.
i am not very clear about the steps.but if i understand correctly, i need to
1. goto fastboot to restore stock 4.1, which will automatically remove TWRP and replace it with stock recovery
2. copy stock 4.2 rom to the root of a sdcard and run stock recovery for udpate
3. root the device again? and install TWRP
4. use TWRP to install the PC-man 4.3
am i miss anything?
thanks alot!
Graiden05 said:
I think fastboot is prefered to restore 4.1 stock. And IMHO best way to upgrade to 4.2 is stock recovery.
Click to expand...
Click to collapse

All right. Little hint: twrp for new bootloader have 4.2 in the end of file name and version 2.5.0.0 is most stable.

Hope this Helps
Try here. http://forum.xda-developers.com/showthread.php?t=2187982
Basically, you have 2 options. If you want to stay on 4.1 bootloader, download the older 4.1 Asus factory image zip (v10.4.x.x) from this thread, http://forum.xda-developers.com/showthread.php?t=1949758, and install it using one of the three options mentioned in the first thread.
Option #2 is to update to the newest 4.2 bootloader, download the newest 4.2 Asus factory image zip from the same thread (v10.6.x.x), and install it
I would go with #2 because most of the newer custom ROM are made for 4.2 bootloader, plus it's the offical newest Asus bootloader. The only reason I can think of to use option #1 is for some of the older custom ROM that still uses 4.1 bootloader.
Hope this helps.
---------- Post added at 12:32 AM ---------- Previous post was at 12:27 AM ----------
mlee18 said:
Try here. http://forum.xda-developers.com/showthread.php?t=2187982
Basically, you have 2 options. If you want to stay on 4.1 bootloader, download the older 4.1 Asus factory image zip (v10.4.x.x) from this thread, http://forum.xda-developers.com/showthread.php?t=1949758, and install it using one of the three options mentioned in the first thread.
Option #2 is to update to the newest 4.2 bootloader, download the newest 4.2 Asus factory image zip from the same thread (v10.6.x.x), and install it
I would go with #2 because most of the newer custom ROM are made for 4.2 bootloader, plus it's the offical newest Asus bootloader. The only reason I can think of to use option #1 is for some of the older custom ROM that still uses 4.1 bootloader.
Hope this helps.
Click to expand...
Click to collapse
Make sure to follow the instructions in RED exactly, there's a reason they are in red.

[Q] Help - Clarification on [How To's]

Hi
I finally have decided to try and unlock, root and install custom ROM to my TF300T. It's lagging a lot and I am going crazy over it.
I am not new to rooting and flashing roms, I have done the same numerous times to my beloved GNex and a couple of other mobile phones I owned before. Having said that, I have only followed the tutorial to flash. So, not a total newbie but sort of.
I am trying to make this tablet more usable (my usage is is restricted to browsing, streaming sports/movies and a few games). The more I read the more I am getting confused. I just would like a clean ROM which doesn't lag and hopefully a method that has lesser possibility of Bricking.
I am on the latest firmware from Asus (But, It did come with ICS if I remember correctly before I updated to 4.2.1). I know when I updated it came with new BL so, using custom recovery/roms designed for 4.1.x is not an option (please correct me if I am wrong). I intend to follow these steps -
Please point me in right direction/correct the steps/suggest better steps where ever needed. I just want to know if I am on the right path so far.
1. Unlock BL with latest Unlock tool from Asus website.
2. with [UNLOCKED BL], install 2.5.0.0 TWRP &SuperSU ( will follow - [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices ) - OR should I install 'openrecovery-twrp-2.6.3.0-tf300t-4.2.img' from TWRP site?
3. Once #1 & #2 are complete, I can choose a Custom Rom and flash. Anything else to be wary about?
Questions
1. Should I use 'Flatline - Unbrickable Transformer TF300T - Jellybean edition'?
2. I do not have much data and I can download the apps again if needed. So, Is Nandroid backup/Backup with Titanium necessary? (for recovery of the system/ROM - I do not care about the apps/user data at this point)
3. Can someone suggest what they think is a better combination of ROM+Kernel? From a post I see the following ROMS I can choose from
joelalmeidaptg's post :
Here you have a list of ROMs that are compatible with the new bootloader and are safe to flash once you are on 4.2.1 firmware:
CleanROM Inheritance Xenogenesis from sbdags
Energy™ from NRGZ28
GRIMLOCK from hardslog
CyanogenMod 10.1 Unofficial from pcoussa
ROM-THEME- STOCK KERNEL Stock Asus Firmware 10.6.1.15.3 from surdu_petru
Click to expand...
Click to collapse
Thanks in advance.

janusman said:
Hi
I finally have decided to try and unlock, root and install custom ROM to my TF300T. It's lagging a lot and I am going crazy over it.
I am not new to rooting and flashing roms, I have done the same numerous times to my beloved GNex and a couple of other mobile phones I owned before. Having said that, I have only followed the tutorial to flash. So, not a total newbie but sort of.
I am trying to make this tablet more usable (my usage is is restricted to browsing, streaming sports/movies and a few games). The more I read the more I am getting confused. I just would like a clean ROM which doesn't lag and hopefully a method that has lesser possibility of Bricking.
I am on the latest firmware from Asus (But, It did come with ICS if I remember correctly before I updated to 4.2.1). I know when I updated it came with new BL so, using custom recovery/roms designed for 4.1.x is not an option (please correct me if I am wrong). I intend to follow these steps -
Please point me in right direction/correct the steps/suggest better steps where ever needed. I just want to know if I am on the right path so far.
1. Unlock BL with latest Unlock tool from Asus website.
2. with [UNLOCKED BL], install 2.5.0.0 TWRP &SuperSU ( will follow - [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices )
3. Once #1 & #2 are complete, I can choose a Custom Rom and flash. Anything else to be wary about?
Questions
1. Should I use 'Flatline - Unbrickable Transformer TF300T - Jellybean edition'?
2. I do not have much data and I can download the apps again if needed. So, Is Nandroid backup/Backup with Titanium necessary? (for recovery of the system/ROM - I do not care about the apps/user data at this point)
3. Can someone suggest what they think is a better combination of ROM+Kernel? From a post I see the following ROMS I can choose from
Thanks in advance.
Click to expand...
Click to collapse
After unlocking the bootloader and installing TWRP, I would recommend installing CROMi-X.
It is based on stock so you do not need to wipe before installing (you can keep all your apps).
It has a nice graphical installer and you can choose lots of different tweaks.
It comes with a variety of different kernels - I use _that's OC kernel.

grit96 said:
After unlocking the bootloader and installing TWRP, I would recommend installing CROMi-X.
It is based on stock so you do not need to wipe before installing (you can keep all your apps).
It has a nice graphical installer and you can choose lots of different tweaks.
It comes with a variety of different kernels - I use _that's OC kernel.
Click to expand...
Click to collapse
Thanks for the reply. Which version of TWRP? 2.5.0.0 or the latest one from TWRP site that ends with 4.2.blog?

janusman said:
Thanks for the reply. Which version of TWRP? 2.5.0.0 or the latest one from TWRP site that ends with 4.2.blog?
Click to expand...
Click to collapse
Use the one that ends in -42 since you are on the 4.2 bootloader. Flatline NvFlash is always a good idea. A helpful guide is here: http://forum.xda-developers.com/showthread.php?t=2545610.

cromi x for sure
cromix is def the way to go with this tablet-get a fast microsd-partition and use a kernel with data2sd like thats.
good luck, if installed correctly you'l feel like it's a brand new tablet
---------- Post added at 11:25 AM ---------- Previous post was at 11:17 AM ----------
also, i find it's better to install cromi without installing a kernel first (using stock). then after cromi is up and running, use kernel installer to install desired kernel and tweaks. have fun and make sure to read everything