CM flash fails on my TF300T unlocked

[p0isonParadise]

Hi,

I re-post here beaucause I posted on TF700T ASUS models..

I unlocked my TF300T tablet with the official bootloader unlock tool from ASUS support, and after, I can see the menu which offer these options : RCK (Recovery Mode), Android, and Wipe Data.

I tried to install CM 10.0 with TWRP Recovery (beaucause ClockWork Recovery isn't compatible with the TF300T), and it fails. I tried after to install CM 9.1 and it fails too..

What is the problem ? When I start my tablet, it's frozen at the ASUS logo start screen and in a corner there is displayed : The device is UnLocked. .. I don't understand why it doesn't work ?

 

[p0isonParadise]

I found a solution for persons who meat this trouble.

1. Unlock the tablet with the official ASUS tool from the ASUS Support.
If it's OK, the "The device is UnLocked" message appears at the start logo.

2. Download at the Support, the last firmwire for your tablet, extract the archive and move the Zip update into a microSD card.
After, insert the microSD card into the tablet.

3. Run in TWRP recovery mode, if you haven't it, follow the instruction at the TWRP official website.

4. Wipe Factory, wipe Data, wipe Dalvik Cache, Install zip from microSD card and reboot.

If it works, at the first boot, the "Signature match" message appears with a progress bar at the start logo screen.

End.

 

[cmendonc2]

Hi,

I re-post here beaucause I posted on TF700T ASUS models..

I unlocked my TF300T tablet with the official bootloader unlock tool from ASUS support, and after, I can see the menu which offer these options : RCK (Recovery Mode), Android, and Wipe Data.

I tried to install CM 10.0 with TWRP Recovery (beaucause ClockWork Recovery isn't compatible with the TF300T), and it fails. I tried after to install CM 9.1 and it fails too..

What is the problem ? When I start my tablet, it's frozen at the ASUS logo start screen and in a corner there is displayed : The device is UnLocked. .. I don't understand why it doesn't work ?

There was probably a bootloader conflict with CM.