Also, you should be able to use H3ii to burn to eMMc as well, it should perform just the same as if you burnt it to an SDcard and run the installation process and when installing it will grow to the size of the media it is installed on.ģ. "Is there a way to write H3Droid to eMMC" <- Yes, you can simply dd an image from your card to the eMMc, the eMMc in these boards acts like a SDcard anyways, so make an 8GB image on an 8GB Sdcard and then dd that to PC Plus eMMc, or you can even generate a custom image using the installer to the size of the eMMc you have and then dd that image onto the eMMc. "after reboot i got only pink screen and no system running" <- pink screen = hung i2c, to fix this you need to poweroff both board and monitor and then restart and things will work.Ģ. This H3resc, as a recovery like software, is also, a useful tool.Įdited by TheLinuxBug at I will try to address your concerns below:ġ. This H3ii is something like this, but i don't see option for eMMC writing there. I think you only need simple images to write to sdcard from usual programs for that purpose, in any OS. Android users are usually Windows users, or even at the lower level of knowledge (no offence, just honest observation). Your target users (Android users) are not into Linux, very much. But i think you really should consider your installation methods. So what am i missing? Is there a way to write H3Droid to eMMC? As this option is in 00_conf, i thought this is the way.Ībout the project, it's good and useful. But after reboot i got only pink screen and no system running. I added OUTDEV=/dev/mmcblk1 into 00_conf file, writing went well. Board is Orange Pi Plus2e, so i tried to write H3Droid to eMMC, through Armbian Linux, running on sdcard. Kernel 3.9. am not into Android at all, but i decided to try new 1.2.9 version. Started Cleanup of Temporary Directories. Starting Cleanup of Temporary Directories. Listening on D-Bus System Message Bus Socket. Started Record System Reboot/Shutdown in UTMP. Started Trigger Flushing of Journal to Persistent Storage. Starting Record System Reboot/Shutdown in UTMP. Started Recreate Volatile Files and Directories. Starting Trigger Flushing of Journal to Persistent Storage. Starting Recreate Volatile Files and Directories. Mounted POSIX Message Queue File System. Reached target Local File Systems (Pre). Mounting POSIX Message Queue File System. Listening on /dev/initctl Compatibility Named Pipe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |