AM6+ already have its official image so no need to try Vim3.
eMMC install is not been tested on AM6 Plus with the latest Android Firmware cause I feel there is some changes in latest firmware which stops it from boot from emmc.
I have AM6+ running on emmc with the same script but I had Old Android firmware which had come pre-installed. While when I tried the same with AM6B+ It fails to load from emmc but works fine from sdcard. I will have to connect uart and find out what is going on in the backrground.
BTW after you flashed it on emmc. Did you do the following?
Match PARTUUID in /boot/uEnv.ini and /etc/fstab ?
On first reboot enable multi-boot ? which is like pressing hand holding the reset key with Manjaro-SDcard installed. (This is the most important part which gets missed out)
Yes you mentioned here so it is something similar to what I am facing on AM6B+
If both the above was done then we can only tell from bootlogs. I will have to hookup the uart on the board to see whats happening. Maybe in coming days.
Which one? I was not sure which one Iām on, so while restoring stock Android I tried every version and only 0.4.2 worked. Asking that to try downgrading
But thatād require upgrading to latest FW firstā¦
Well latest dev version puts right IDs in both places for root pt
Could you please be more specific here, Iām not sure I understandā¦
First of all, re-enabling multi-boot means Iām on multi-boot firmware, but Iām notā¦
Pressing recovery button would just instantly hard-reset/reboot the box, so Iām not sure how to do that on first reboot. I guess first reboot is right after initial setup wizard, so I should probably make a shutdown instead of reboot, power off, pin-press the recovery button, power on while still pressing it, right?
You have done it already so that have cleared my doubt. That youāre doing the right things but still it doesnt seem to work. You already have multi-boot enabled as per you previous post.
Try these steps.
Flash Android on eMMC and use AM6+ image from sdcard and then update time and run emmc install script.
Reboot with sd card inserted and boot into sdcard version.
Mount emmc and check if the PARTUUID in /boot/uEnv.ini and /etc/fstab is the same for emmc partitions for both boot and root.
If all the above is correct and then it still doesnāt work then I have doubt on android uboot present in emmc.
Done, mounted two partitions of emmc, changed PARTUUID of root in uEnv.ini (emmc boot part), and PARTUUIDs for both boot and root in /etc/fstab (emmc root part)
No news, the same black screen with no text at allā¦
My only guess is install script somehow damages boot loader info or bootloader just canāt find boot partition where it has to be, maybe partition layout has changed on latest firmware. Iām total noob hereā¦
If uboot is not there, how is that supposed to boot from sdcard (which is still ok)?
Iām still interested which FW version does your am6+ run. And could this whole thing be related to encrypted bootloader, which is since 3.9 something.
One thing you could try is to boot from emmc try to point root to /dev/mmcblk1p2 instead of partuid and also try the same with label of the partition to see if it boot.
Also a test using boot from sdcard pointing to emmc rootdevice would be interesting
I am using sdcard. I added rootdelay =10 to bootarg and I can see that the rootdelay in dmesg is added just before HS200. Have you tested booting on EMMC with rootdelay or rootwait args?
Just found that latest builds canāt boot from USB OTG drive either (builds with extlinux boot ok), managed to change sdcard links to usb drive root partition and everything works fine, even wifi started to work after updating kernel to 5.16.7-1-MANJARO-ARM-KHADAS