Related
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,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
cyaneo said:
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
Click to expand...
Click to collapse
What is your bootloader version? Si it fresh enough?
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
cyaneo said:
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
Click to expand...
Click to collapse
Yeap,.. Bloody bootloader
No problem
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
cyaneo said:
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
Click to expand...
Click to collapse
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
szulco said:
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
Click to expand...
Click to collapse
- now I formatted data and system and also wiped all possible parts
- flashing cwm 6.0.2.3 and installing asus stock ROM (ww_epad-user-10.4.2.20), reboot
- cannot access cwm recovery, so I reeflash it with fastboot method
- access cwm recovery and install latest 10.1 nightly, reboot, done.
Thank you so much!
I'm having the same issue.
I bought my TF300T when if first came out. I finally decided to play around with it.
I unlocked it with the Google Play app.
Used fastboot to push the latest ASUS JB4.2 firmware (US_V10.6.1.8)
My bootloader says: (1.00 e) released by "US_epad-10.6.1.8-20130225" A03
I rooted and installed TWRP v2.4.4.0
Everything is working fine for me and I have taken a solid backup, so I'm able to restore back to that when things fail.
I loved using CM7 on my phone, so I wanted to try CM10 on my tablet.
I have tried installing the stable CM 10.0, and I've tried all of the CM 10.1 Nightlies.
Every single time, the install goes perfectly fine, but when I reboot I just get the plain white Asus screen and then it freezes.
I have tried installing with and without installing the gapps.
Every time I install I do a Factory Reset, wipe the Cache, Dalvik Cache, and System. The only thing I didn't do is wipe Data as I'd prefer not to lose my files. (is that the problem, is the data-wipe required?)
Is there something obvious that I'm missing or a step I left out?
Any help would be greatly appreciated.
I tried doing it again with wiping all my data too...that didn't make a difference either. Still freezes on the white asus screen.
Hi, I just registered to reply, as seems noone did. And Ive been there myself, also with the 10.6.1.8 bootloader. Thats the issue. Cyanogenmod isnt compatible yet with the newest bootloader 10.6.1.8.
I hope it will in the future, Im awaiting it too. Until then I just rooted the stock rom, and using it that way. You could try the CROMI-X rom, but its also stock based, I havent tried it yet, maybe ill give the newest update a try (4.3) which will be available in a couple of days, as I really love their newest boot animation(wich I believe isnt included in the 4.2 version)
Till then, no Cyanogenmod for us with the newest bootloader.....also downgrading is not worth the risk if you ask me,,, even if its possible. So Ill wait for the Cyanogenmod team to update their version to ours.
Advice: dont mess with the bootloader nor the recovery img files. Always read carefully if you wanna change recovery if its compatible with your bootloader. If its not, and you flash it...tada....youre the owner of a cool and expensive brick. Dont wipe data in the bootloader, cuz as I understood reading posts here at xda, it will wipe your entire device, including bootloader...then your kinda screwed. So stick to what you have and let the devs do their work to update their roms for the 10.6.1.8 bootloader...MOST importantly, DONT store your device with the keyboard dock closed...(like a laptop)...your screen will crack eventually.I gathered this info on youtube as well as here, and Ive a friend, who was using the device with the dock till last month like that, had it from last august...result, screen cracked 3 weeks ago...its a design flaw in the transformers, the screen is under heavy pressure while in the keydock..I just got my dock last week,, Im storing it separately, and I never close it, only use it for typing, battery and usb.
im writing all this as I think I wont find this post again to reply if you read it.
I just got my TF700 the other day. I was able to downgrade to .30, root, and unlock the bootloader without incident. I just pushed CWM per this thread: http://forum.xda-developers.com/showpost.php?p=31556045&postcount=1. I tried booting into CWM, got the standard quick vibration but the tablet was dead after that. I messed around for a while and finally after holding the power button several times in a row, it booted as normal. Battery is at 80%
Before I go any further, what just happened? Can I push CWM again the same way to re-install it? How should I proceed?
FWIW, the checksum for download 1 on the page mentioned only matched the checksum for #2. I used #2 because it matched its MD5 as it was listed on the page.
lowriderdog37 said:
I just got my TF700 the other day. I was able to downgrade to .30, root, and unlock the bootloader without incident. I just pushed CWM per this thread: http://forum.xda-developers.com/showpost.php?p=31556045&postcount=1. I tried booting into CWM, got the standard quick vibration but the tablet was dead after that. I messed around for a while and finally after holding the power button several times in a row, it booted as normal. Battery is at 80%
Before I go any further, what just happened? Can I push CWM again the same way to re-install it? How should I proceed?
FWIW, the checksum for download 1 on the page mentioned only matched the checksum for #2. I used #2 because it matched its MD5 as it was listed on the page.
Click to expand...
Click to collapse
The proper way to do this is to upgrade to the latest stock JB (10.4.4.25), unlock, and you can either fastboot the recovery or unlock it be flashing Superuser. It is not advised to downgrade,even if it seems easier, because if you do it the way I stated, everything will be latest and should not have any problems whatsoever. since you downgraded to ICS, you now have a ICS bootloader. an ICS bootloader will not boot JB, nor vice versa. so now you will need to flash a JB bootloader, which will not boot the stock ICS, so you will now need Cromi, Cyanogen,or another custom rom to get it update with JB. Make sure you have them preinstalled on a SDcard before doing any more flashing.
If I am wrong, hopefully someone will correct me.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Tylorw1 said:
The proper way to do this is to upgrade to the latest stock JB (10.4.4.25), unlock, and you can either fastboot the recovery or unlock it be flashing Superuser. It is not advised to downgrade,even if it seems easier, because if you do it the way I stated, everything will be latest and should not have any problems whatsoever. since you downgraded to ICS, you now have a ICS bootloader. an ICS bootloader will not boot JB, nor vice versa. so now you will need to flash a JB bootloader, which will not boot the stock ICS, so you will now need Cromi, Cyanogen,or another custom rom to get it update with JB. Make sure you have them preinstalled on a SDcard before doing any more flashing.
If I am wrong, hopefully someone will correct me.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Click to expand...
Click to collapse
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
lowriderdog37 said:
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
Click to expand...
Click to collapse
I CM10.1 requires the JB bootloader, If you install CM on the ICS it wont boot. I dont see why the recovery is the problem. I would try updating to JB bootloader, use the zips in Cromi's second post, and then try installing Cromi. Downgrading is only recommended if you want to stay on a locked bootloader. Otherwise, you should flash the root.then install recovery, or simply fastboot it.
In order to install CM you will need to update the bootloader, then once it is updated you will not be able to boot into the ICS rom, so you will have to already have CM10.1, also dont forget google apps, so it can be flash afterwards.
IF CM is installed with the ICS boot loader it will just not boot, it will go into recovery but that is it. I dont see any probability in bricking your device. But I am only a newb, so you may wanna wait for another's input.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
---------- Post added at 01:26 PM ---------- Previous post was at 01:20 PM ----------
lowriderdog37 said:
The writeups I had seen prior unlocking said to downgrade to .30...so I did. I am still sitting on .30 and am planning on installing CM 10.1 which I have on both the TF700 internal and an external SD card. The only problem is what I mentioned above where my device wouldn't boot into CWM and subsequently locked up for about 15 min. Should I upgrade to JB .25 prior to booting into CWM and installing CM 10.1?
Click to expand...
Click to collapse
Or you could install the 10.4.4.25 stock, then just fastboot a recovery. I mistakenly said root with zip, you cant without custom recovery so scratch that, the only way to install custom recovery via the method I gave is fastboot. Or the way you did so, but that requires more steps and upgrades. Also greater chance of bricking. This is because of the incompatibility of the rom, boot loader, and recovery. If you have latest recovery,I would install the bootloader, then flash CM10.1 + Gapps and should be good to go.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
Got it working. Yes, it appears CWM is bootloader specific. I flashed the JB bootloader and was able to get into cwm and install CM10.1 I am not up and running. Thanks!
lowriderdog37 said:
Got it working. Yes, it appears CWM is bootloader specific. I flashed the JB bootloader and was able to get into cwm and install CM10.1 I am not up and running. Thanks!
Click to expand...
Click to collapse
Just remember for future reference, keep things up to date,or at least compatible with one another or you will run into trouble later.The #1 reason for tf700's bricking software wise is people do not update their bootloader as they update their recovery. Just keep things recent and you should have not a problem.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
I hate myself, for I am a noob.
Actually, I have just never posted because someone else has always posted the issue and fix for my problems, but this one make me want to paint the walls with my brains.
Obviously I have an Asus TF300T, and I have successfully unlocked and installed a custom recovery. I have TWRP 2.5.0.0 because apparently ClockWorkMod does not like the Asus 4.2 bootloader.
So I have the TWRP 2.5.0.0 Custom Recovery and Asus Stock Android 4.2.1, and every time that I install a new ROM and reboot I get stuck in the "Asus" window, the window it shows right before it loads the oparating system. So it tells me that it cannot read or there is no operating system found. I am doing a wipe Dalvik Cache, System, Cache, and Data before I do the install of the new ROM, but it never gets to the new operating system.
I am wanting to get to CyanogenMod, and I have tried all versions of if with the same result. I have also tried AOKP and Baked Bean and I still get the same thing.
So I found another post earlier and they suggested there was an issue with the Asus 4.2 BootLoader, and I was excited because I was sure that was the problem all along! ... Not...
So I was able to get the .zip of the Asus Stock Android 4.1.1, and I was able to get into TWRP and install that. Magically, that worked and I am now on Asus Stock Android 4.1.1, which to my understanding should mean I have the Asus 4.1 Boodloader. Since the OS Version changed, I also had to change the version of TRWP. It is still TWRP 2.5.0.0, but for Asus 4.1. So I install a new ROM and I get the same exact issue as before...
At this point, I have no idea. I feel ashamed to have to post a question and ask, but does anyone have any ideas what else I might be able to try? Or it looks like I am stuck with the default version of Android and I should have never unlocked it.
Thank you!
Mostly Fixed
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
JEYoung4545 said:
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
Click to expand...
Click to collapse
If you itch so much to install CM 10.2 on your tab, the dedicated thread in development recommends that you run it with 4.2 bootloader. Give it a try to see if it solves your problem.
if you want to run cm10.2 just upgrade to latest stock, flash twrp2.6.0.1/ 2.6.0.0 and flash cm10.2.
cheers
Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
hi!
after recently getting a sl101, i've decided to flash it. i'm not a total n00b in flashing, so i've thought it was easy. i was wrong.
long story short, after several trying, now my sl101 only boot with cm10.2 for a tf101, and only a roguexm 1.5 - cwm 5.0.2.8 based recovery.
but i'm totally unable to make a recent twrp working, nor any more recent rom like kiss kat working.
either flashing a more recent recovery make it stuck in asus logo (recevery loop), or flashing a recent rom with my current cwm makes error during flashing.
what's wrong? my partition table is the same from factory, is there anything to do with that? what i'm missing?
THANKS !!!!
ok, i was able to flash kitkass 4.4 (but not 5.1) (i didn't try that before)
THANK GOD i was able to find an old twrp 2.6.3.9 wich work
https://www.dropbox.com/s/7j5ra5oflh8lp2n/signed_twrp-2.6.3.9_sl101.zip