Related
This is a modified CWM-based recovery for the Motorola Atrix 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3/4 formatting
Unified kernel for international users
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition. Additionally, I have an AT&T phone so that is the kernel I am using. I doubt the memory issue would matter in recovery mode but testing from UNLOCKED international users would be appreciated. UPDATE: Initial indications are it works fine on UNLOCKED international phones. Versions for different tegraparts have also been compiled. UPDATE 2: Unified kernel patch has been applied. Choose whatever color you prefer regardless of phone version!
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
Example from my phone:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Atrix 4G. I have personally tested this on my phone but YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
ALL USERS
Orange 5.0.2.7-atrix5 / ZIP version.
MD5 aebe29124d8c6d6c4b9873bd9ea4ca3b / 1f9a1d6fc83610e5c7c8f2d60e489b69
Cyan 5.0.2.7-atrix5 / ZIP version.
MD5 eb44b910983434d3996383098dff53b6 / 91365993488a9ae060b22c8b820d1c5b
Light green 5.0.2.7-atrix5 / ZIP version.
MD5 e7c7ec152e9e3269ef2ab1ce99b8943e / 1e720c8760898549226a10d4776f5077
Dark green 5.0.2.7-atrix5 / ZIP version.
MD5 c8a4438e5889d5e681a754555c40bc51 / 121d8d9102eac3ed24f1e0be6f8cd5d1
Blue 5.0.2.7-atrix5 / ZIP version.
MD5 9a1fd3c8796d2e768b54d39143c17ea3 / 9059c0c37fd2c547ec8508c893986815
Red 5.0.2.7-atrix5 / ZIP version.
MD5 036a9d9cc390a6071011d4d50b008875 / aa069d1aed20c5cbd13b2098b6a88975
Original ROM Manager installable zip thanks to SolidHelix. You must still be UNLOCKED to use them.
Source is here.
A few notes:
The capacitive buttons can be used to navigate as well. Back is back, search is select. Menu and home are up and down.
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext3/4 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. The only use I'm aware of on our phone currently is Sogarth's webtop2sd.
Thanks to:
Koush and the CM team for CWM
Everyone who has made unlocking the Atrix possible
** Changelog **
2011-11-14 (5.0.2.7-atrix5):
Minor bugfix release mostly
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental.
2011-09-24 (5.0.2.3-atrix4.1):
Fix an issue with using ext4 formatting on stock ROMs
2011-09-23 (5.0.2.3-atrix4):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-atrix3.3):
Unified kernel patch from eval-
New kernel to fix the stuck at "Entering Android Recovery" prompt. Big thanks to bamastang for helping test this.
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in the CM7 device config when building the recovery image (again, just cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-atrix3.2):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-atrix3.1):
Swap kernels to re-enable soft keys. Ext4 support should still work.
Fix for external SD card partitioning (internal is not supported).
CWM zip changed slightly.
2011-08-12 (4.0.1.4-atrix3):
Experimental ext4 support. Thanks to SolidHelix for testing it.
Fix for restoring large yaffs2 images (greater than 10,000 objects).
Tweak to the SD card space check before starting Nandroid backup.
Miscellaneous minor bugfixes and tweaks.
2011-08-07 (4.0.1.4-atrix2):
User is now prompted to wipe sd-ext (webtop2sd) on "Wipe data/factory reset".
User is now prompted to backup or restore webtop (/osh and /sd-ext) during Nandroid.
Four alternate colors created.
Versions for different tegraparts (international phones) created.
2011-08-05 (4.0.1.4-atrix1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots:
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
sd-ext (webtop2sd) is inadvertently wiped on "Wipe data/factory reset". Next version will make this optional. Fixed in -atrix2.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking or crashing, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
If I currently have tenfar's latest recovery, is it worth installing this one?
xploited said:
If I currently have tenfar's latest recovery, is it worth installing this one?
Click to expand...
Click to collapse
yes..Nandroid support
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
bamastang said:
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
Click to expand...
Click to collapse
were you using Tenfar's old version.
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
munchy_cool said:
yes..Nandroid support
Click to expand...
Click to collapse
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
bamastang said:
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
Click to expand...
Click to collapse
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It should be from my tests, but you should also test it.
romracer said:
It should be from my tests, but you should also test it.
Click to expand...
Click to collapse
I have several backups of my PDS partition. I am very busy tonight, but was planning on spending tomorrow re-building my laptop. So while I'm doing that I'll do a backup, wipe, and restore to see what happens and report back.
DK
DeathKoil said:
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Click to expand...
Click to collapse
PDS is definitely backed up. It's not restored by default, just as a wimax partition is not on those devices that have them. It is available under Advanced Restore but you should help test it and have a separate backup just in case.
Backup early and backup often.
romracer said:
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Click to expand...
Click to collapse
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Bug during backup?
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
Edit: In the advanced restore options there is also an option to restore the external sdcard, but it is against referenced as the mount point "sd-ext" instead of sdcard-ext".
Like I said, I'll wipe the phone clean tomorrow and test restore it then make a new post with the results.
So far so good!!
DK
bamastang said:
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Click to expand...
Click to collapse
Boot regularly and then in Settings enable USB Debugging. From a command prompt, "adb devices" should show your phone. From there, "adb reboot recovery" and wait 10-20 seconds.
Does that get you into recovery? Does the "Motorola Dual Core" boot image change at all when you try to boot into recovery? Like to a little Android guy with a yellow hazard sign?
The "plugged into AC" recovery is just a hijack of the normal system, so if your phone boots normally I'm not surprised that method works.
DeathKoil said:
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
DK
Click to expand...
Click to collapse
"sd-ext" refers to an ext3 partition on the external SD card. On other phones, this is used for crap like "data2sd" and "apps2sd". On our phones, the only current use I've seen of this is for Sogarth's webtop2sd.
Standard CWM does not backup SD card contents (it backs up to them) so there is no support for that in mine. I could consider adding it eventually.
You will see references to "sdcard-ext" in my recovery if you do something like Apply update.zip and then choose External SD card (look at the path it shows you for update.zip on the confirm screen).
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
guidoido004 said:
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
Click to expand...
Click to collapse
Yes. I have personally tested this particular item a few times. mke2fs from Koush's CWM segfaults, but I have supplied a working one.
Will you be including international support?
I just enabled data2ext and I need to know whether i have to stay on Clockwork 3.0.0.5 or will nandoid backup/restores work on Clockwork 5.0.2.7 ?
They should still work when you upgrade
Mobiono said:
I just enabled data2ext and I need to know whether i have to stay on Clockwork 3.0.0.5 or will nandoid backup/restores work on Clockwork 5.0.2.7 ?
Click to expand...
Click to collapse
I think anything above 2.5.0.7 will work for you and back up that partition for you (and wipe too). I am a firerat's person, but I know that all of the builds above the recovery you are using will be fine. 5.0.2.7 is the newest.
I went to 5.0.2.7 and i tried backing up but it's taking a extraordinary amount of time to finish. It's been on backing up the "last_log" for cache for almost a full 60 minutes. Is this normal?
Edit- It's been close to 2 hours, so i pulled the battery out. Could the size of the partition as well? I set mine to 2048. Also, backups and restores work on 3.0.0.5 but not on 5.0.2.7.
I have another issue. Not sure if i should make a thread since it's still dealing with data2ext but it looks like this thread is dead. In the event that someone does come across this, I'm getting an error while typing tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2. It says tune2fs: not found. I tried reinstalling busybox to the lastest version but no results. Not sure what to do.
I could use some advice/help here ...
I have a P7300 with CWM v5.5.0.4 flashed and have been performing Nandroid backup/restores quite happily trying out various ROM versions. My last backup was approx 4 weeks ago. I went to perform a new backup today and the CWM displays "backing up boot, recovery & system" and then very quickly I get the "Samsung Galaxy Tab 8.9" logo in the center of the screen and it jumps back to the CWM main recovery menu.
No Backup is performed and no directory is created with the date/timestamp in the /sdcard/clockworkmod/backup directory.
I tried re-flashing the CWM v5.5.0.4 zip but get the same results - I checked free space on the /sdcard partition and I have over 5GB of free space.
The device re-boots fine into the ROM itself.
Any ideas/thoughts on how I can fix this so I can perform Nandroid backup/restores again ?
Many thanks!
b8drf said:
I could use some advice/help here ...
I have a P7300 with CWM v5.5.0.4 flashed and have been performing Nandroid backup/restores quite happily trying out various ROM versions. My last backup was approx 4 weeks ago. I went to perform a new backup today and the CWM displays "backing up boot, recovery & system" and then very quickly I get the "Samsung Galaxy Tab 8.9" logo in the center of the screen and it jumps back to the CWM main recovery menu.
No Backup is performed and no directory is created with the date/timestamp in the /sdcard/clockworkmod/backup directory.
I tried re-flashing the CWM v5.5.0.4 zip but get the same results - I checked free space on the /sdcard partition and I have over 5GB of free space.
The device re-boots fine into the ROM itself.
Any ideas/thoughts on how I can fix this so I can perform Nandroid backup/restores again ?
Many thanks!
Click to expand...
Click to collapse
First this belongs in the General Forum or the Q&A forum!
Maybe you can try to install CWM 6.0.0.8 from Kallt_Kaffe's CM9 Thread!
I'm having exactly the same problem See my thread here - http://forum.xda-developers.com/showthread.php?t=1815348
safariking said:
First this belongs in the General Forum or the Q&A forum!
Maybe you can try to install CWM 6.0.0.8 from Kallt_Kaffe's CM9 Thread!
Click to expand...
Click to collapse
Updating CWM was the first thing I tried and didn't work for me - give it a try though, OP. Apparently restoring to stock then rooting and flashing again works, but this wipes everything, including the /mnt/sdcard Backing it up is a real pain too cause windows doesn't like the long directory names. Nightmare!
I'll try the suggestion of .hidenandroidprogress but otherwise it looks like it's restore time for me :/
CM7/Zeus v7alongside any rom with GB bootloader and CM7 alongside v28a
Hi!This is my"how to" for installing two roms on one OB.
1.We need to partition sdcard
partition #1 : format it to fat(will be used as sdcard)
partition #2 : format it to ext4(will be used as system of zeus and must be at least 320 MB)
partition #3 : format it to ext4(will be used as data of zeus and must be at least 400 MB)
2.Now if u want:
1.Zeus flash this
2.cm7 flash this
(DO NOT FORGET TO PUT YOUR INTERNAL ROM`S KERNEL TO /sdcard/boot/ and name it nandboot.img!)
3.cm7 alongside v28a flash first this, then flash v28a with SFT, then root your v28a and after that put files from this bin.zip to the /system/bin
3.Now if u want to boot:
1.Zeus type in the terminal
Code:
su
bootzeus
2.cm7 type in the terminal
Code:
su
bootcm7
3.v28c ICS
Code:
su
bootsd
4.your nand rom
Code:
su
bootnand
NOTE:If u change your nand rom first install your new rom and after that copy your new rom's boot.img and put it to /sdcard/boot.img and after that rename it to nandboot.img and after all this install this if your sdrom is cm7 and if Zeus this
Now partition table is:
Code:
Zeus/CM7/v28c ICS
system /dev/block/mmcblk1p2
data /dev/block/mmcblk1p3
CM10
system /dev/block/mmcblk0p8
data /dev/block/mmcblk0p9
YouTube
suleymanovemil8 said:
Hi!So is it possible to boot android from sdcard?I think changing root directory to mmcblk1 in the default kernel kommand line could help, have anyone done smthing like this before?
Click to expand...
Click to collapse
Even if it works you'll still be using the same kernel and ramdisk which will only work on ROM very similar to your base.
Sent from my LG-P970
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
suleymanovemil8 said:
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
Click to expand...
Click to collapse
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
xonar_ said:
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
Click to expand...
Click to collapse
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
suleymanovemil8 said:
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
Click to expand...
Click to collapse
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
xonar_ said:
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
Click to expand...
Click to collapse
as i said "and it have created app, data, etc. folders on data (sd) partition"
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
here it is(this is kernel for cm10(26.10.2012))
suleymanovemil8 said:
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
Click to expand...
Click to collapse
What are you going to do with the GB thats on the phone and not used?
EDIT: its rebooting to recovery because the kernel is set to reboot to recovery when it's 'panicking'.
Sent from my LG-P970
xonar_ said:
What are you going to do with the GB thats on the phone and not used?
Sent from my LG-P970
Click to expand...
Click to collapse
no this kernel boots with normal system and data at sdcard and now i will make kernel with booting from data directory and with data at sdcard)
YES! I have now two roms on one phone!
suleymanovemil8 said:
YES! I have now two roms on one phone!
Click to expand...
Click to collapse
Do a walkthrough for us! :laugh::laugh:
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
Yes ,pls
sent from my Nokia 1100 with droid 4.0
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
As much I understand, bootloader is needed for dualboot and it applies same on Android. So you got access to our bootloader or just directing the boot.img from 1st ROM to 2nd one? Like handshaking?
xonar_ said:
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
Click to expand...
Click to collapse
Well I have installed rom's kernel to the recovery partition but after booting to this new kernel i couldn't boot back tonormal kernel till i reflashed recovery from rom manager
ps.recovery partition is at mmcblk0p4 and boot mcblk0p3
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
tada!
As I expected, not real dualboot. But very much appreciting try. Keep it up
Anyway i still want to make one rom at nand and anouther on sdcard, but if i set in kernel system directory to mmcblk1p1(sdcard) it starts to boot but smthing goes wrong but it starts to boot and i know it because it creates app, data, app-private etc. folders on data partition of sdcard(mmcblk1p2), i think this is because it remounts sdcard or smthing like this.Any ideas about soving this problem?
I am working on Ubuntu 15.04 and I used the Heimdall suite to do the necessary flashing.
Before I start: I created this post to share my experience with trying to flash a custom ROM on the GT-i9000 and receive some suggestions, though my main concern is the fact that I am unable to mount /system and /data. And yes, I have read posts concerning this issues, but they were too vague, so I decided to write my own.
First I figured I should flash a custom recovery, so I tried flashing the latest CWM for the galaxysmtd in Download Mode and it appeared to have been successful, though when I pressed the 3-button-combo (UP-HOME-POWER), It would boot the default Android System Recovery.
I tried flashing a few CWM and TWRP recoveries (though I didn't try PhilZ Touch, because goo.im is down and I couldn't find a proper PhilZ Touch recovery anywhere else), though I noticed that none of them would work, even though the flash was successful. So I figured I could try flashing a kernel, which would include some recovery - and it worked, to my surprise, though after attempting to wipe a few folders, I got the error: unable to mount /system and /data.
So I came to realise that the only way for me to get a working custom recovery was to flash a kernel, which should include a working recovery. So I ended up flashing Mackay_kernel_0.692_twrp_CMC-signed.zip, which includes TWRP v2.8.0.0. The recovery seems to work fine, though the same error persists: unable to mount /system and /data.
I tried formatting /system and /data, though to no avail: it just forced the recovery to reboot (I have attached the recovery log to this post).
Any help is much appreciated!
I am glad to inform that I managed to resolve the issue by reverting to the stock firmware, ROM and kernel by using Odin v1.83. Though this leaves me with the default recovery, which isn't able to flash a 5.1 ROM.
I tried flashing a kernel with CWM and then flashing a 5.1 ROM with said CWM recovery by installing its .zip, though this method causes the same issue: unable to mount /system and /data.