I tried that in different variations. The easy thing to do is taking the recovery.img getting built by the CM build-process and choosing "format /data and /data/media" there. This actually creates a filesystem which makes e2fsck happy.
What also works is running "e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/userdata" from the terminal or an adb shell in OR after the first boot. This will produce a lot of output about broken entries but will finally finish.
The third solution should be just waiting for a long time on the bootloader-image, as e2fsck is running (and producing the same output you could see in OR, but it's not visible). I straced e2fsck and saw that it was actually fixing errors while the phone seems stuck in the bootloader image. Prepare to wait for 15 to 20 minutes.
The big question is: Why does the filesystem created by OR or TWRP has so many errors in the first place and what is CWM doing differently so the fs does not have these problems?
Here is a bit of the straced e2fsck running while the phone was on the bootloader screen:
It seems I'm having the same problem. Formatted data, reflashed Recoovery TWRP 220.127.116.11 like a zillion times. After a second reboot the phone won't boot. I'll just keep it in the charger and hope the mainboard isn't fried when I wake-up later.
Will post in the morning.
|Thread Tools||Search this Thread|