turbohobbit
Android Enthusiast
Righto. Last night I rooted my TF and flashed Megatron and recommended kernel, no problem. I've had no problem taking nandroid backups or restoring as I've done that several times today, all with expected results.
Then I opened ROM Manager and allowed the app to update, I guess updating CWM too.
I then fiddled with SetCPU overclocking the CPU. This caused the tab to stutter a bit. Then freeze. Anyway, I hard rebooted and went into recovery to try and flash the backup I took about an hour ago. Now, CWM looks different (I guess this is where ROM Manager updated). I flashed the backup which seemed to go ok, but then when the TF rebooted I got an Android message saying that encryption hadn't worked properly, and that I would need to do a full (factory) reset. I hit ok and let it do it's think. The TF rebooted, but went direct into Recovery.
I tried wiping everything using Factory Reset, and wiping Dalvik, etc, but every time I tried I got a message saying "E: Can't mount /sdcard/" and then it reverted back to the main menu structure.
Any thoughts? I think a) ROM Manager may have caused this and b) it's royally wrecked.
Cheers muchly in advance!
Then I opened ROM Manager and allowed the app to update, I guess updating CWM too.
I then fiddled with SetCPU overclocking the CPU. This caused the tab to stutter a bit. Then freeze. Anyway, I hard rebooted and went into recovery to try and flash the backup I took about an hour ago. Now, CWM looks different (I guess this is where ROM Manager updated). I flashed the backup which seemed to go ok, but then when the TF rebooted I got an Android message saying that encryption hadn't worked properly, and that I would need to do a full (factory) reset. I hit ok and let it do it's think. The TF rebooted, but went direct into Recovery.
I tried wiping everything using Factory Reset, and wiping Dalvik, etc, but every time I tried I got a message saying "E: Can't mount /sdcard/" and then it reverted back to the main menu structure.
Any thoughts? I think a) ROM Manager may have caused this and b) it's royally wrecked.
Cheers muchly in advance!
