Hi
I have a ASUS TF300T and have installed the TWRP bootloader as recommended by another site.
I have tried Cyanogenmod 9, Cyanogenmod 10 and Cyanogenmod 10.1 nightly and none of them will boot. The device gets stuck at the ASUS logo screen and I get no further.
Obviously I have cleared cache etc (I'm familiar with the basics of installing a different ROM).
Can anyone advise me what to do? I have restored to the default ASUS software through a backup I made but I am really not happy with the performance of this.
I either want to be able to get Cyanogenmod on this tablet or I'd like to restore it to the default bootloader to make it ready for sale.
Thanks so much in advance.
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
mattburley said:
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
Click to expand...
Click to collapse
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
mattburley said:
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
Click to expand...
Click to collapse
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
EndlessDissent said:
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
Click to expand...
Click to collapse
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
mattburley said:
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
Click to expand...
Click to collapse
Since you're using the unofficial build, you won't be able to use the CM Updater. Or, at least, I would assume you can't. I'm pretty sure that it would download the newest official version, and the official ones won't boot. So you'll have to watch the unofficial thread for updates for now, until everything's fixed and it becomes official.
As for waiting to update, that applies to the ASUS OTA updates, not the CM updates. ASUS, as I've mentioned, makes changes to the bootloader in some of their OTAs that can cause bricks. If you're just updating CM nightlies, you shouldn't have anything to worry about. It's the stock updates that get hairy.
If you would like more stuff working, you could downgrade your tablet to 4.1 (forum.xda-developers.com/showthread.php?t=2195883), and install CyanogenMod 10.
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Me too. Just sits there spinning. Went to my backup for now.
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
roberto767 said:
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
Click to expand...
Click to collapse
I have the 4.2 boot loader. So I finally figured out you the 4.2 version recovery instead of the JB version. That unofficial one still would not work so I flashed this and it works great.
http://forum.xda-developers.com/showthread.php?t=2204166
thx for this thread, I had these issues myself,,, shame it wont work on 4.2 bootloader
Stuck at CyanogenMod Logo durng boot
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
roberto767 said:
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Click to expand...
Click to collapse
rdh23 said:
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
Click to expand...
Click to collapse
Just an FYI: the official CM10.1 now supports the 4.2 bootloader. It has for over a month now. Plus, the experimental build has been abandoned.
Same story again
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
p.s. I did make sure to get the right recovery for my bootloader, i.e. openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Emalice said:
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
Click to expand...
Click to collapse
What OS is your PC running??
lj50036 said:
What OS is your PC running??
Click to expand...
Click to collapse
windows 7 64bits...
adb
Emalice said:
windows 7 64bits...
Click to expand...
Click to collapse
You have the adb driver install?? if so turn your tablet off and in a command window move to the directory that adb is in and type
Code:
adb logcat > logcat.txt
now boot your tablet.... your PC will pick it as adb device and output the logcat to a text file in that directory post the logcat file....Let the logcat run for about 90 sec or so.....
Related
Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
alldog said:
Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
Click to expand...
Click to collapse
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Thanks for tips mister, since I dont can find the right version from ASUS I have to ask...in Europe is it the WW version i suppose to use, and its the Firmware not the Source code?
alldog said:
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
Click to expand...
Click to collapse
Why not installing a stock rom (the same version you had before the issues started) with TWRP, that should get you back on track.
Edit: Yes european version should be WW_SKU and please use the firmware not the source.
Got one step further ..or did I? Tryed to put in stock .30 used "fastboot -i 0x0B05 flash system blob" in fastboot usb-mode. Seemd ok until this message arrived: Failed to prosess flash system error (0x17003)
So, close but not there. There are some problem with flashing since other images also refuse to install. What now?
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
Hi everyone, I'll go ahead and apologize for being a bit of a noob. I've got the TF300T, it's unlocked, rooted, running 4.2.1 bootloader, and I've installed TWRP 2.5.0.0. I've tried flashing the latest CM 10.1 nightly from here as well as the AOSPA 3+ from here. Both of them gave me the same result, after wiping the cache and dalvik, I rebooted and they both get hung up on the boot animation. I made a recovery before flashing that I keep going back to when this happens so it's definitely not bricked. Am I missing a step somewhere? I'll probably give one of the other ROMs a shot tomorrow, but in the meantime any help would be appreciated
Robo_Bear said:
Hi everyone, I'll go ahead and apologize for being a bit of a noob. I've got the TF300T, it's unlocked, rooted, running 4.2.1 bootloader, and I've installed TWRP 2.5.0.0. I've tried flashing the latest CM 10.1 nightly from here as well as the AOSPA 3+ from here. Both of them gave me the same result, after wiping the cache and dalvik, I rebooted and they both get hung up on the boot animation. I made a recovery before flashing that I keep going back to when this happens so it's definitely not bricked. Am I missing a step somewhere? I'll probably give one of the other ROMs a shot tomorrow, but in the meantime any help would be appreciated
Click to expand...
Click to collapse
The CM 10.1 ROM you are trying to flash will not work with 4.2.1 bootloader. You will need to either downgrade or use f69m's unofficial version for your bootloader version,, which can be found in Development section.
I would recommend the latter. Not that downgrading is difficult, but it does involve an element of risk of bricking your device if you do not flash correct version of custom recovery. There are excellent guides written for this, which should be easy to find.
Thanks for your quick response, I really appreciate it. I'll look around tomorrow and see if I can get it all sorted.
Robo_Bear said:
Thanks for your quick response, I really appreciate it. I'll look around tomorrow and see if I can get it all sorted.
Click to expand...
Click to collapse
You're welcome. If you choose to downgrade for using the official CM 10.1 nightly here is a guide:
http://forum.xda-developers.com/showthread.php?t=2195883
Choose the latest JB 4.1 version (10.4.2.20) and follow the guide. Make sure you flash the correct TWRP as stated in the guide. This is where far too many bricked their device.
Hi All,
I am looking for a complete guide (or links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information that's dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
snoopspecial said:
Hi All,
I am looking for a complete guide (on links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information thats dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
Click to expand...
Click to collapse
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
snoopspecial said:
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
Click to expand...
Click to collapse
To be honest, the lag is still there accross all the 4.2 roms I tried, even debloated. Its not as bad but its still there. My alternate device has a beastly exynos in it so im used to a perfect smooth experience. I notice even a little bit of jitter and it drives me crazy ( hence why I downgraded to 4.1 ) .
As far as what bootloader to use for which CM rom, each will tell you which to use specifically. I saw there is a cm10.1 for 4.2 and for 4.1. Just make sure to match things.
I used to be a CWM user all the way, but twrp does trump it in features and usability, especially for the transformer series. I beleive there is only one single twrp that works properly on the new bootloader for stock based roms ( no cwm will work on it at all). It ends in .42 so make sure you flash the correct one. If not, your partitions wont be writable.
One MAJOR warning.........
Do NOT use the wipe / factory reset on ANY bootloader. You will brick your tablet!!! Permanently!!!!
You can ONLY use the wipes inside of twrp / CWM.
Sent from my SGH-T889 using xda app-developers app
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
okay - lots of options in TWRP - going the simple safe route and just following the norm:
http://teamw.in/whattowipe
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
Im assuming you are flashing CM10 then? The only important thing is fully read the OP and match your bootloader to whatever one they tell you. Its generally not a suggestion, but an actual requirement.
Mines a 32gb so I keep all of my backups and rom flashes right on the internal storage. I feel its safer in case of SD corruption or an accidental wipe. It doesnt hurt to have it in 2 places though ( backup your original rom to SD card but keep everything on the internal as well ). I always flash from internal ( roms and nandroids alike ). Ive never had an issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
snoopspecial said:
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
Click to expand...
Click to collapse
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
snoopspecial said:
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
Click to expand...
Click to collapse
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
snoopspecial said:
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
Click to expand...
Click to collapse
yeah so that worked fine. the CM10.1 version must require some different combination.
taking your suggestions now and downgrading to the 4.1 bootloader. will also install the CleanInheritance rom.
by the way, thanks again for your help and suggestions!
So just for other people out there... if you want to run the TF300T downloads from get.cm (the nightlies as of now).
I've confirmed the following requirements:
1. 10.4.2.20 - TWRP 2.5.0.0 - JB
2. CM 10.1 5/25/2013 Nighty (This is a 4.2.2 ROM - requiring the JB, not 4.2 bootloader - i imagine at some point this will be updated)
3. GAPPS 20130301-signed
ah so nice!
My TF700 is bogged down pretty hard and randomly freezing/rebooting so time to upgrade from Cleanrom 3.4.1 (JB 4.1) to whatever is out there now. It has been a few years since messing with roming and don't want to screw anything up. I also did some searching but didn't find anything on this specifically.
I see twrp is the way to go now for recovery but I am running cwm 6.4.x I think? I forgot since rebooting and looking. Anyways, I can just use adb per the instructions and re-flash twrp over the cwm then flash a KK rom right? I just want to make sure because my GS3 has to be reverted then something changed then re-updated...something crazy to not brick it and I obviously don't want to happen.
First of all you need to determine what your botloader version is. It's probably outdated if you've been on a CleanROM. You need to have the 10.6.1.14.10 bootloader if you want to flash a KK rom.
The easiest way to uograde your BL is to grab the BL/TWRP package from the OP of the CROMi-X thread in Development and flash it in your current recovery.
Reboot to let it install, then boot to recovery and check the version number. I forgot what TWRP version sbdags packaged in that file. If it is TWRP 2.6.0.1 go to the Teamwin website, downlaod TWRP 2.8.0.1 and flash it in fastboot.
Then you need to do a full factory wipe in TWRP (default under the Wipe command) and then you can flash the KK rom.
For general instructions read this:
http://forum.xda-developers.com/showthread.php?t=2688891
A little confused. It sounds from your message that I can flash the new recovery? The thread you sent me to said to flash in fastboot. I only ask because I don't have a windows box handy and am lazy.
Thanks for the help!
edit* - refamiliarizing myself with the terminology and starting to get it again.
Fastboot was kind of a pain to get working but once it had connection and I learned how to use it, worked like a charm. Thanks a ton!
Have CM11 working on my tab now. It has been in pretty desperate need for some time now.
lowriderdog37 said:
Fastboot was kind of a pain to get working but once it had connection and I learned how to use it, worked like a charm. Thanks a ton!
Have CM11 working on my tab now. It has been in pretty desperate need for some time now.
Click to expand...
Click to collapse
If you're in the mood for it, nandroid CM11 and try ZOMBi-X. I love it!