NativeSD WM #6 Updating
One of the great advantages of the new technique of NativeSD on the HTC HD2 is that all users can benefit from ROM development. So a ROM developed for NAND, implemented using NativeSD, can usually be used by CLK, Windows Phone and Windows Mobile users. Basically the Loader runs an AROMA Installer script http://forum.xda-developers.com/show....php?t=1461712
that allows you to choose which version of the ROM you wish to install. The basic components are the same but individual parts are required for different operating systems. You choose which options you wish to install. As AROMA is a Touch and Customizable ROM Installer, it does not matter if you use a Text based loader. Once AROMA is launched, you select options by touching the screen. Recommendation is to accept the defaults the first time.
Files are extracted from the NativeSD.zip file and copied to both the FAT32 partition and the EXT4 partition on your SD card. They are stored in folder with the same name as the ROM (for example NativeSD\CM10). The FAT32 partition, which you can read in Windows Mobile, has only two files: initrd.gz and zImage for each ROM. initrd.gz is a Linux initial ramdisk that has been compressed using Gzip and zImage is similarly a compressed kernel image file. The way you chose which NativeSD to run is by copying initrd.gz and zImage from the ROM sub-folder into the NativeSD folder. This can be done using file manager (overwriting the ones in the NativeSD folder) or more easily using one of the applications shown in the post above. From Android use "nativeSDMultiBoot" and from Windows Mobile use "Multiple Android-Starter" - both of these copy the files for you. In the NativeSD folder, you run the common set of files CLRCAD.exe and then HaRET.exe to boot the NativeSD using the parameters specified in startup.txt. (These are the first tiny letters you see when the ROM starts booting). This can be automated using some of the above applications. In the EXT4 partition the subfolders of NativeSD for each ROM contain data and system files. With all these files being unzipped and copied during the flash and boot, occasionally things go wrong.
First thing to check is that the NativeSD.zip ROM file was downloaded correctly by checking the Hash checksum. A good Dev will provide this, for example Xylograph recovery_4EXT2.2.7_leo_sd.zip has an MD5: 142c324022b7ea77c3a7ca8d2fcabb70
If your ROM does not boot correctly the first time (after say 15 minutes), you should try and reboot it again. Alternatively you can simply try to flash the ROM again using Recovery. This will keep your data and settings and may correct any problems that have occurred. Search the thread for the ROM to see if other users are experiencing the same problems. Recommend that you look for a post by one of the Learning Never Ends team to say they have flashed the ROM using Windows Mobile successfully.
Updating to new version
When updating to a new version of the same ROM, you can often simply flash the new version on top of the old using Recovery. Conversely, if the new ROM does not suit, you can usually flash the older version again using Recovery. As the different versions of the same ROM are stored in folders with the name of the ROM, this flashing simply overwrites the previous System files, hopefully leaving the data. In some case, the Op will advise a new or fresh install. In that case you should backup the ROM (see above post), delete the existing old ROM (see above post) and flash the new version as if it was a new ROM. You may be able to restore data using either Titanium Backup (or similar app) or data.ext4.tar from Tytung backup.
Over The Air (OTA) Update
is supported by some ROMs and allows you to receive push
notification of new updates so that you can easily download the updated version of a ROM. This is saved to a folder on your SD card called sdcard/OTA-Updater/download
. Using OTA is the same as downloading from the home page but possibly more convenient as it is automated amd you do not have to visit the thread. You do have to use Recovery
to Choose a zip to apply - for example the one saved in sdcard/OTA-Updater/download
Resize EXT4 Partition
Resizing your EXT4 partition can be done in Linux using GParted or from Windows. First recommendation is to Backup all of your NativeSD ROMS to FAT32 using either one of the methods detailed in the above post and then back up your FAT32 Partition to your PC. From Windows, you can then use MiniTool Partition Wizard Home Edition 7.6 to
a) Delete EXT4 Partition
b) Extend/shrink FAT32 to free up the new EXT4 size you want
c) Create a new EXT4 partition with the size you want
d) Format EXT4 Partition again using 4EXT recovery
e) Restore your NativeSD ROMS to EXT4 (following whichever method above that you used to backup)
Please see the next post for: