Hi all, I just have a small handful of questions before I proceed on a venture of mine.
I've got a TF300T I bought about a month ago and I love it. I've spent time customizing it and pimping it out, and its great. My only issue is I -really- miss some of the features that come on the stock ASUS Rom, like the Swype keyboard, SuperNote, and the Polaris Office suite, to name a few. At the moment I've got the tablet rooted and unlocked running CM9 and I think its off of the .29 firmware, but I'm not sure. That being said, I've got a few questions:
1) Is there any way to port those specific features that I want from the stock ROM to CM9? So that would be the Swype keyboard, PolarisOffice, SuperNote, and a few others like the Asus weather app widget, and some of the other asus-specific widgets.
2) I know restoring a backup breaks the wi-fi, and I was given a fix (Flash the stock ROM over the current install without wiping out) but before I do that, which ROM would I use? I was at .29 when I rooted it a few weeks ago and I download the .30 Stock ROM from Asus' website today, but don't want to flash the wrong one and break compatibility or do anything like that.
3) I read somewhere that flashing the stock ROM would overwrite my recovery manager. If that is the case, would I lose the backups I've done with the recovery manager? (Clockwork Recovery Mod) Is there a way I can make a copy of my backups, then have those in case I lose them through the flashing of ROMS?
4) Since I won't receive OTA updates with unlocking it and whatnot, is it OK for me to go ahead and flash the .30 ROM from Asus' website that has the latest updates and what not? Or is there another resource I can access that has rooted versions of the .30 for my enjoyment? (I hope to install CM10 as soon as it becomes available!!)
Thanks so much for any and all help, I do appreciate it.
-Opethfan89
opethfan89 said:
Hi all, I just have a small handful of questions before I proceed on a venture of mine.
I've got a TF300T I bought about a month ago and I love it. I've spent time customizing it and pimping it out, and its great. My only issue is I -really- miss some of the features that come on the stock ASUS Rom, like the Swype keyboard, SuperNote, and the Polaris Office suite, to name a few. At the moment I've got the tablet rooted and unlocked running CM9 and I think its off of the .29 firmware, but I'm not sure. That being said, I've got a few questions:
1) Is there any way to port those specific features that I want from the stock ROM to CM9? So that would be the Swype keyboard, PolarisOffice, SuperNote, and a few others like the Asus weather app widget, and some of the other asus-specific widgets.
2) I know restoring a backup breaks the wi-fi, and I was given a fix (Flash the stock ROM over the current install without wiping out) but before I do that, which ROM would I use? I was at .29 when I rooted it a few weeks ago and I download the .30 Stock ROM from Asus' website today, but don't want to flash the wrong one and break compatibility or do anything like that.
3) I read somewhere that flashing the stock ROM would overwrite my recovery manager. If that is the case, would I lose the backups I've done with the recovery manager? (Clockwork Recovery Mod) Is there a way I can make a copy of my backups, then have those in case I lose them through the flashing of ROMS?
4) Since I won't receive OTA updates with unlocking it and whatnot, is it OK for me to go ahead and flash the .30 ROM from Asus' website that has the latest updates and what not? Or is there another resource I can access that has rooted versions of the .30 for my enjoyment? (I hope to install CM10 as soon as it becomes available!!)
Thanks so much for any and all help, I do appreciate it.
-Opethfan89
Click to expand...
Click to collapse
1.) You can try downloading the rebloat zip from Seanzscreams' thread and installing the apps like that. I think Polaris and SuperNote should work fine. The Asus stuff, I'm not sure about.
2.) The one from the Asus site should be the right one. Just make sure you get the one for the correct region (actually, I don't think the region matters a whole lot if you aren't expecting OTAs).
3.) You won't lose the backups because you lose recovery. You will lose the backups because the stock ROM will wipe the internal storage. The best thing to do is just copy and paste the entire contents of /sdcard to a normal computer hard drive, then when you have stock flashed, just copy and paste it back.
4.) Getting the ROMs from Asus is perfectly fine. There are also a couple stock-based ROMs at various levels of "stockness" in the development section. However, in order to flash them correctly, you need to be on the stock Asus ROM anyway. So go ahead and flash the Asus ROM. You'll need to anyway.
Thanks for your response. I guess I didn't clarify my question about backing up programs. So, I read somewhere that you can buy a paid program, and within 15 minutes cancel that payment and not be charged. Within that 15 minutes, you can just backup the .apk file and have a paid program for free. Based on this logic, my question should have been stated Is there a similar way to backup the specific .apk files for the programs I want, such as SuperNote, Polaris Office, etc, or will those programs be searching for the specific version of the Stock ROM and not run unless the ROM is an Asus ROM?
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!
Is upgrading to jelly bean worth it on the tf700?
pollardhimself said:
Is upgrading to jelly bean worth it on the tf700?
Click to expand...
Click to collapse
As an only partially joking short answer lacking nuance to a really short question lacking nuance: yes.
not worth it IMO unless you unlock and put custom rom. ICS ran pretty smooth.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Do you find ICS to be running fine and smooth? Then it may not be worth it.
Do you find ICS to be a bit laggy? Try JB.
ICS wan't too bad, actually, but I do like the smaller inprovements JB has brought us, even on stock-based ROMs. If you're into the options that other JB ROMs provide (AOSP/AOKP/CM10), then you should really consider unlocking and installing them. I forego them for now, for I see little to no difference in terms of smoothness and fluidity, or raw speed.
Might be my eyes getting stuffed, though. Old age.
what the problem of updating to jelly bean?
if you have the stock ROM then yes updating worth it and in 90% cases updating is better
Most pepole saw a huge different when upgrade from ICS to JB .20. The newest version .23 only give a slightly smoother with the browser and others. So I would say YES. Beside, life must go on, do you want to stay with windows 98 for the rest of your life??
Well there are two camps as far as ICS then JellyBean and of course the CustomROM folks.
I found ICS OK for me as an unknowledgeable user.
JellyBean was supposed to be a tab users dream come true.
After the first OTA into JB I thought "well it's a little better" (not really)
Then the second OTA for JB appeared and I thought "ah this will fix all" (no sir)
Adobe flash had to be side loaded (well this happened after JellyBean initially anyway)
The stock browser was a nightmare.
Fleeting gray lines appeared thru games and all the web browsers.
On screen keyboard had a 1-2 second delay after tapping
YouTube crapped
I renamed project butter "project stutter"
JellyBean for me meant only one way out:
Unlock-Root-Custom ROM
Now living happily ever after.
I'm not pushing the unlock root blah-blah-blah route.
My tab was in my possession almost three months before jumping to CleanROM then CROMI
There are quite a few very happy Infinities out there on stock ICS or JB.
This is just my story...soooo IMO it's totally a toss-up about moving to the latest Android version.
update
this is kinda off topic but i have a unlocked boot loader but not rooted. and i wanna apply the 10.4.4.23 update, i installed the file from the asus website then unzipped it and relocated it in my micro sd card. restarted it and powered it back up with holding volume down and power button, then went into RCK mode, i get the android then it turns into the android with the red exclamation point, someone please help me .
ham67high said:
this is kinda off topic but i have a unlocked boot loader but not rooted. and i wanna apply the 10.4.4.23 update, i installed the file from the asus website then unzipped it and relocated it in my micro sd card. restarted it and powered it back up with holding volume down and power button, then went into RCK mode, i get the android then it turns into the android with the red exclamation point, someone please help me .
Click to expand...
Click to collapse
You need to delete the Asus firmware zip fle in your micro sdcard
First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.
rreedy30 said:
First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.
Click to expand...
Click to collapse
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108
cmendonc2 said:
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108
Click to expand...
Click to collapse
Thanks so much I was able to load both ROMs. I really appreciate it. My mobile dock does not work with either of them but I think I'll search around for that before posting another question.
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?