mount("ext4", "EMMC", "/data");
or
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/data");
I already wrote the manual ( but in very rough english - not my native language - c is native language ). you should replace the: update-binary-installer with your previous/normally used update-binary, but renamed.
Why I still use update-binary-installer in aroma? (not implement all functions in one binary)
* I am afraid the binary was device/manufacture independent
* Many user was familiar with something like mount need 4 arguments, but other binary only support 3 arguments.
* Some binary support different functions that usable in some devices but unusable for another devices.
I had a plan to include all installer functions in aroma binary, but it need so so many tester in so so many devices, and user need to use aroma standard installer functions.
If there somebody who can help me to create simple manual about it, I will be happy.
Also I need to create update-binary repository with folder format like this:
Manufacture/device/type.
example:
htc/bravo/mui - update-binary from htc desire mui
htc/bravo/cm7
etc....
or
mount("ext4", "EMMC", "/dev/block/mmcblk0p23", "/data");
I already wrote the manual ( but in very rough english - not my native language - c is native language ). you should replace the: update-binary-installer with your previous/normally used update-binary, but renamed.
- First time Aroma wouldn't start: I think you accidentially replace the aroma update-binary with your old update-binary (without renamed it).
- Aroma started it self within the Aroma installer: Then I think you copy the aroma update-binary and rename it to update-binary-installer (both binary was aroma binary) - it's called never ending loop
Why I still use update-binary-installer in aroma? (not implement all functions in one binary)
* I am afraid the binary was device/manufacture independent
* Many user was familiar with something like mount need 4 arguments, but other binary only support 3 arguments.
* Some binary support different functions that usable in some devices but unusable for another devices.
I had a plan to include all installer functions in aroma binary, but it need so so many tester in so so many devices, and user need to use aroma standard installer functions.
If there somebody who can help me to create simple manual about it, I will be happy.
Also I need to create update-binary repository with folder format like this:
Manufacture/device/type.
example:
htc/bravo/mui - update-binary from htc desire mui
htc/bravo/cm7
etc....
Last edited: