[Q] Cyanogenmod on TF300t stuck at boot screen

[mattburley]

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.

 

[EndlessDissent]

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.

 

[mattburley]

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.

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!

 

[EndlessDissent]

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!

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.

 

[mattburley]

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.

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.

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!

 

[EndlessDissent]

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!

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.

 

[mattburley]

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.

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!

 

[EndlessDissent]

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!

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.

 

[c0ded]

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.

 

[roberto767]

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?

 

[texascbx]

Me too. Just sits there spinning. Went to my backup for now.

 

[roberto767]

Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work

 

[texascbx]

Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work

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

 

[Sovn]

thx for this thread, I had these issues myself,,, shame it wont work on 4.2 bootloader

 

[rdh23]

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?

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.

---------- 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.)

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?

 

[EndlessDissent]

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.)

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.

 

[Emalice]

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

 

[lj50036]

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

What OS is your PC running??

 

[Emalice]

What OS is your PC running??

windows 7 64bits...

 

[lj50036]

adb

windows 7 64bits...

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

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.....