Replicant

I hope this isn't about a NAND bug. Did you succeed installing CyanogenMod with another recovery image?

Thanks Paul for getting back.

Following the above issue, i reverted to stock rom using odin.

Later I got this recovery image flashed using odin.

CF-Auto-Root-m0-m0xx-gti9300
http://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip

Is there any other method to flash replicant on I9300?

The only way is to use our recovery image. What happens if you try to mount the partitions separately from our recovery?
Also, if recovery fails at mounting the partitions, the Replicant kernel will likely behave the same, so trying to force-install Replicant inst' really an option. We should rather try to understand what's going wrong.

Can you check whether your phone is affected by any EMMC bug: http://wiki.cyanogenmod.org/w/EMMC_Bugs ?

What happens if you try to mount the partitions separately from our recovery?

Please bare my answer this is my first android device and learning curve is bit steep now.

With odin,i was able to flash the stock rom.

Also with CF-Auto-Root-m0-m0xx-gti9300 recovery rom, there were messages for mount error.

Another thing that i got the same mount error with CF-ROOT CF-Root-SGS3-v6.4.zip.

Info regarding EMMC bug:

I retrieved this information within the phone using root shell.

cd /sys/class/block/mmcblk0/device

1. cat name
   V3WOOM

#cat cid
15010056335730304d006d4946c1a0e7

1. cat manfid
   0x000015

1. cat date
   10/1997

A typo mistake writing the first part of comment again:

What happens if you try to mount the partitions separately from our recovery?

Please bare my answer this is my first android device and learning curve is bit steep now.

With odin,i was able to flash the stock rom and it worked.

With CF-Auto-Root-m0-m0xx-gti9300 recovery rom, there were no messages for mount errors. I could see both internal and external sd cards.

Another thing that i got the same mount error with CF-ROOT CF-Root-SGS3-v6.4.zip, even though i flash this with odin.

A silly question?

I m within the replicant directory:
$>ls
boot.img i9300.md5 recovery.img system.ext4.img

$>sudo heimdall flash --BOOT recovery.img --RECOVERY recovery.img

why do we use?

$>sudo heimdall flash --BOOT boot.img --RECOVERY recovery.img

Okay so this is quite weird. I suppose this is not a Replicant-specific issue but rather something wrong with recovery. I suppose you should provide dmesg log from our recovery (adb shell dmesg) and the recovery log (adb shell /cache/recovery.log) but it may fail if /cache is not mounted.
Also, what happens if you try to mount the partitions manually using mount from adb shell when running our recovery?

$>sudo heimdall flash --BOOT recovery.img --RECOVERY recovery.img

Flashing the recovery image on the BOOT partition as well ensures that the phones reboots directly to recovery without any particular key holding.

adb shell /cache/recovery.log

/sbin/sh: /cache/recovery.log: not found

1. mount /dev/block/mmcblk0p1 /external_sd

tail ./etc/recovery.fstab
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p12 length=-16384
/preload ext4 /dev/block/mmcblk0p10
/modem emmc /dev/block/mmcblk0p7

/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1

Current devices

/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6

Please find the attached dmesg.txt for (adb shell dmesg)

Would it be safe if i do something like:

Get the stock recovery.img flashed.

sudo heimdall --RECOVERY recovery.img

then flash replicant images

sudo heimdall flash --BOOT recovery.img --SYSTEM system.ext4.img

Correction to my earlier message

Would it be safe if i do something like:

Get the stock recovery.img flashed.

sudo heimdall --RECOVERY recovery.img

then flash replicant images

sudo heimdall flash --BOOT boot.img --SYSTEM system.ext4.img

Okay so looking at dmesg clearly reveals this is a kernel/hardware issue, even though it really is I9300:

<3>[ 1.764808] c2 mmc0: error -22 whilst initialising MMC card

So basically, since this isn't a one-time issue but something that happens everytime, Replicant will not work for your device, no matter how you install it. I suppose it will do the same for CyanogenMod. Though if you can get CM 10.1 to work on your phone, then it means Replicant 4.2 will likely work, so you'll have to wait for it. Sorry.

then flash replicant images
sudo heimdall flash --BOOT boot.img --SYSTEM system.ext4.img

Definitely not! The system image format is not correct for direct flashing but is only relevant for the installer.

Thanks Paul really appreciate.

I am able to install CM 10.1.

http://download.cyanogenmod.org/get/jenkins/42508/cm-10.1.3-i9300.zip

Any expect date for 4.2?

It's hard to give any ETA. It may be in a couple weeks.