0

I am using CM10 nightly version and TWRP for tf201. Wanted to try the unofficial CM11 version android 4.4 on my tablet and it says that is not compatible with this recovery, so I downloaded the latest version of CWM 5.8 from its website and using adb fastboot (and second time with the tablet terminal) flashed the new recovery over the older one. Now the problem is I can't enter the recovery mode, it gets stuck while entering the mode. I tried that procedure with two more recent version of CWM (both touch and classic) and also its ROM manager but the problem persists. Some info:

1- I have my device unlocked, rooted 2- adb fastboot said completely Done while flashing 3- i could see the blue bar completed on the tf201 device and then i used fastboot reboot.

Any suggestions?

Improve this question

1 Answer 1

Reset to default
3

I've found that if I run into problems with the custom recovery, I can get rid of it altogether by re-flashing the stock firmware, and then I can install the custom recovery again. You have a different device, but that's what works on a Samsung Galaxy S4, so it might work for you. Of course, there's always the possibility that if you try installing CWM again you'll run into the same problems, but at least that should let you start again from square one, as if you had never flashed a custom recovery in the first place.

Improve this answer
14
  • I have mentioned it, its tf201 (asus transformer prime)
    – Amir
    Commented Oct 29, 2014 at 18:07
  • Oh, it wasn't clear to me that that was a device model. In any case, my suggestion remains the same.
    – Adi Inbar
    Commented Oct 29, 2014 at 18:18
  • Ok. Thanks for the info. I will try that and report the results here
    – Amir
    Commented Oct 29, 2014 at 18:28
  • Now we have a problem: I can't seem to find my stock recovery! where should I download that from ?
    – Amir
    Commented Oct 30, 2014 at 1:19
  • 1
    Awesome! Glad to hear you're back in business. Just a thought, maybe it's not all those versions of CWM that failed. Maybe just the first one messed things up, and the others seemed not to work because the bootloader or recovery was already hosed. You might want to try again, starting with the most recent version. Then again, you might want to avoid inviting further headaches. ;)
    – Adi Inbar
    Commented Oct 30, 2014 at 17:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .