Can you manage to boot the recovery?
During the boot process, some partitions are mounted.
If the mounting of some partions fails for some reasons, that leads to symptoms similar to what you have.
So it might be a good idea to first try to boot to the recovery.
Then and if that works, it could be a good idea to try to mount the following partitions:
- /dev/block/platform/omap/omap_hsmmc.0/by-name/system
- /dev/block/platform/omap/omap_hsmmc.0/by-name/efs
- /dev/block/platform/omap/omap_hsmmc.0/by-name/dgs
- /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
- /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
If you already have adb setup in Replicant you might need to mount system in the recovery through the graphical user interface before getting access through adb.
If that fails you will need to find another recovery that has shell access by default. The Replicant 4.2 recovery should work for that.
If all partitions above can be mounted, then the problem might be something else.
It would be great to document in more detail this common issue in the wiki.