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.
Related
Sorry for my english...
Today i unlock the tf300t bootloader and i root it... I flash the Custom Rom JB Hydro 4.1 (i did the ota jb) ... After i want try the cm10... i flash it but it doesn't work... The tab don't work.. i see the bootlogo ... The cmw work, so i tried to restore to jb hydro... but it doesn't work... Now how can i resolve?
hi !
In the recovery mod, try to wipe dalvik, cache and data after that flash your rom again...
if you can try CWM or TWRP recovery ...
I'm having the same Problem
Today i went to CyanogenMOD site and downloaded the most resent Nightly build of Cm10, flashed it into my TF300T and now im stuck in Boot Loop. I used CWM to make a full rom backup before than, but when i do restore from backup everythign goes well, until i reboot it, then it hangs in boot loop again. What can i do? (I followed more than 3 tutorials step by step so i dont know what went wrong. It was OTA JB 4.1.1 , then i unlocked bootloader and rooted, then i did stock rom backup with cwm and then i flashed cm10 nightly and issues started. =(
ozkrtech said:
Today i went to CyanogenMOD site and downloaded the most resent Nightly build of Cm10, flashed it into my TF300T and now im stuck in Boot Loop. I used CWM to make a full rom backup before than, but when i do restore from backup everythign goes well, until i reboot it, then it hangs in boot loop again. What can i do? (I followed more than 3 tutorials step by step so i dont know what went wrong. It was OTA JB 4.1.1 , then i unlocked bootloader and rooted, then i did stock rom backup with cwm and then i flashed cm10 nightly and issues started. =(
Click to expand...
Click to collapse
There is no way of flashing Cyanogen JBs if you are on stock JB. Only Rom available for you is Hydro JB. All otheres are not flashable until the Cyanao Crew get the new Kernel and bootloader to run.
Did you do a full-wipe (wipe data, cache, dalvik-cache, and system) if you did, try TWRP recovery 2.2.2.0 it might say it wiped, but it might be leaving some data behind or you can try a double wipe. I usually wipe front to back, but some people wipe back to front.
Sent from my Nexus 7 using XDA Premium HD app
What can i do?
sammael1069 said:
Did you do a full-wipe (wipe data, cache, dalvik-cache, and system) if you did, try TWRP recovery 2.2.2.0 it might say it wiped, but it might be leaving some data behind or you can try a double wipe. I usually wipe front to back, but some people wipe back to front.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
.
ozkrtech said:
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
Click to expand...
Click to collapse
Ok.. I solved it... I downloaded the fw from asus site... And i flashed blob file with fastboot.. Now my pad works
ozkrtech said:
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
Click to expand...
Click to collapse
EZ is not working on Hydro. No OC possible till now.
Im going back to stock then.
mikaole said:
EZ is not working on Hydro. No OC possible till now.
Click to expand...
Click to collapse
Ok then, im going to download stock JB from Asus site , and after it boot ur and start running smooth im goign to restore backup, and hope it all return normal, thanks for the help, i let ya'all know if it worked.
Edit: I downloaded stock firmware from Asus site and extracted the blob file, moved blob file to c:\Fastboot, then put tablet in fastboot mode via recovery, and flashed blob following this instructions to make it work again.
"U could reflash your unit with stock ROM using fastboot. I just unbricked my unit doing that after 5 days of fighting.
This is what I did, I downloaded job update from Asus then moved the blob to c/fast boot, loaded unit to fast boot then typed
fastboot -i 0x0B05 flash system blob
But make sure our boot loader is 10.4 or it will signature mismatch, so down load the appropriate boot loader .
That's what I did at least and my unit is working again. "
So i'm happy again, thanks for support xda-developers !!! (the instructions in the quote are also from xda-developers)
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
I bought my Asus tf300t and upgraded to Jelly bean last night. I was able to install TWRP and CWM sucessfully and was able to root using Superuser-3.2-RC3-arm-signed.zip but everytime I try to flash a room it gets stuck on the AsUS screen with top left saying "the device is unlocked" and doesn't move past that point and I have to restore from my backup. I've tried using the CM10 nightly rom and the Hydro rom with the same issues.Am I missing something?
ethereals0ul said:
I bought my Asus tf300t and upgraded to Jelly bean last night. I was able to install TWRP and CWM sucessfully and was able to root using Superuser-3.2-RC3-arm-signed.zip but everytime I try to flash a room it gets stuck on the AsUS screen with top left saying "the device is unlocked" and doesn't move past that point and I have to restore from my backup. I've tried using the CM10 nightly rom and the Hydro rom with the same issues.Am I missing something?
Click to expand...
Click to collapse
This is probably not the case, but better just double check... You are not trying to flash ICS based ROM on JB boot loader ?
Or perhaps you have not properly wiped all cache/dalvik/data etc before attempting to flash new ROM ?
All the rom's that I've tried were all JB based roms.
Using TWRP i went to wipe - dalvik/cache and then did a factory reset and then tried installing the rom. I think at one point I tried doing a system wipe as well but still no luck
Did you get an answer?
ethereals0ul said:
All the rom's that I've tried were all JB based roms.
Using TWRP i went to wipe - dalvik/cache and then did a factory reset and then tried installing the rom. I think at one point I tried doing a system wipe as well but still no luck
Click to expand...
Click to collapse
I am having exactly this problem with mine. Did you ever get an answer to the problem?
Which custom recovery have you installed? Version?
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
Hello, I am having some problems installing a working recovery, here is my story... So first the device was 10.6.1.27.5 and its unrootable, so i downgraded to 10.6.1.15.3, where I installed TWRP recovery, and flashed CM 10.2 ROM, but it was too glitchy, so i wiped all data, and fastbooted 10.6.1.15.3 build and stock ROM. So I am now stock,
I am rooted using MottoChop method, and I cant install a custom recovery... I tryed to install TWRP 2.5.0.0 thats the version I was on before, and also tied 2.6.3.0, when flashing the .blob My device turns unresponsive, even when rebooting it with fastboot.
So left with no choice i tried flashing the .img one for JB, (Note: It is currently NOT a OTA update, but manual, so i used the 4.2 first)
I was Able to Flash the custom recovery 2.6.3.0 JB.img and it booted up and worked fine, but then it couldnt mount anything,
I was getting error message:
E: Cant mount /data
and so on... I then tried to flash 2.5.0.0 and got the same result.
GooManager cant find a recovery script for this device...I flashed the TF300T, since thats the kind i have not TF300TG
Im really lost now... I tried ClockworkManager to find a recovery and it said the same thing, I dont want to flash a CWM with flashboot since i here It is terrible.
Any Help Is greatly Appreciated
I notice that alot of these problems, I end up fixing myself... I fixed the issue
But If anyone ever comes into the same situation, heres the fix...
UPDATE to 10.6.27.5 (Yes newest version) Im using US...
Install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob IMPORTANT dont flash the JB version because its only for OTA updates
Open recovery and TWRP will prompt you to install, and beleive it or not, but apparently you can root the newest version,
Just not With MottoChopper and other quick root methods!
If you have any more question, post!