Originally Posted by tdmcode

Honestly you should not be flashing this. You are in way over your head. Wait until I stabilize the mtd conversion at least.

Did you do a full backup like the op says in red text? That is how you go back. If you don't have a backup of efs, some data (your device mac addrs for wifi and bt) may be lost forever.

I've already used heimdall to flash back using Zaclimon's method (as per Klin's recommendation) and I'm back to stock till you get this more hammered out. My wifi is working fine and I did use CWM to make a backup but when restoring it I was having issues (no home button amongst them). I have a few issues but I posted about them on the thread for his restore method so as to not hijack your thread.

Okay so it looks like I have more work to do on the convert script. I'll make a new build before noon tomorrow, Seattle time.

Originally Posted by daniel644

I've already used heimdall to flash back using Zaclimon's method (as per Klin's recommendation) and I'm back to stock till you get this more hammered out. My wifi is working fine and I did use CWM to make a backup but when restoring it I was having issues (no home button amongst them). I have a few issues but I posted about them on the thread for his restore method so as to not hijack your thread.

Ok cool. Just want to make sure your efs is safe.

The only reason I can see for your home button not working is that it's still using my kernel, or an intl kernel.

Originally Posted by tdmcode

Ok cool. Just want to make sure your efs is safe.

The only reason I can see for your home button not working is that it's still using my kernel, or an intl kernel.

using the method I mentioned in my last post got the home working on the stock kernel.

Also I had flashed several Rom and kernels while trying to get back to normal, and the reason I wanted to try yours is because I have played with literally every other rom available so far.

Okay here is another test ROM. md5=d45b2fbfa236813cad3d45e04f23e434.

Changes:
* Hopefully fixed the convert script
* Should reboot back into recovery after the first install
* Got rid of the no-signal indicator in the status bar (but lockscreen text remains)

Originally Posted by tdmcode

Okay here is another test ROM. md5=d45b2fbfa236813cad3d45e04f23e434.

Changes:
* Hopefully fixed the convert script
* Should reboot back into recovery after the first install
* Got rid of the no-signal indicator in the status bar (but lockscreen text remains)

Hmm I need some help here. I deleted my backup of efs.tar and it seems that my /efs is mounted yaffs2 or mtd. So for result I can't flash CM7 anymore as I got an error about the script. The script can detect efs in ext4 or rfs but not in yaffs2. I know this is stupid I didin't flashed efs but I forgot to do it so.

Originally Posted by zaclimon

Hmm I need some help here. I deleted my backup of efs.tar and it seems that my /efs is mounted yaffs2 or mtd. So for result I can't flash CM7 anymore as I got an error about the script. The script can detect efs in ext4 or rfs but not in yaffs2. I know this is stupid I didin't flashed efs but I forgot to do it so.

If the efs data exists in yaffs2 format, you can retrieve it.

Get an adb shell with the new kernel running in recovery and do this:

mount /sdcard
mount /efs
cd /efs
tar -c -f /sdcard/efs.tar .
cd /
umount /efs

Now, if you want to back it up again in rfs format, you would go back to an RFS based recovery and do something like this:

mount /system
/system/bin/newfs_msdos /dev/block/stl3
mount -t rfs /dev/block/stl3 /efs
cd /efs
tar -x -f /sdcard/efs.tar
cd /
umount /efs
dd if=/dev/block/stl3 of=/sdcard/efs.img

Originally Posted by tdmcode

If the efs data exists in yaffs2 format, you can retrieve it.

Get an adb shell with the new kernel running in recovery and do this:

mount /sdcard
mount /efs
cd /efs
tar -c -f /sdcard/efs.tar .
cd /
umount /efs

Now, if you want to back it up again in rfs format, you would go back to an RFS based recovery and do something like this:

mount /system
/system/bin/newfs_msdos /dev/block/stl3
mount -t rfs /dev/block/stl3 /efs
cd /efs
tar -x -f /sdcard/efs.tar
cd /
umount /efs
dd if=/dev/block/stl3 of=/sdcard/efs.img

Ok so the msdos thing is to convert it back to stl/rfs partition right?

Originally Posted by zaclimon

Ok so the msdos thing is to convert it back to stl/rfs partition right?

Yes that's correct.

Originally Posted by tdmcode

Yes that's correct.

But then if it's the case what happens to the mtdblock? (sorry for asking these questions but I want to learn more about this.)

EDIT: Ok I understand now the /efs switch place so it can be in stl3 and mtdblock0 gets deleted.