No Android build working!

[slow_motion]

Ok so if i understood your explanation, all i need to do is download the three binaries and execute the bash script, this would maintain manjaro as the primary os on emmc, and i would then be able to boot android from sd.
The next question is how can i be sure that i have the v2 branch please?

That is correct! On the Github page, right under the Code tab, there's a branch dropdown selector.

Hi again, sorry but no luck with the update. Deep sleep isn't working either, so i don't know if the update was successful.
Is there a simple way to check this out?
At the end of the script, another script was executed to clean the boot, but i was afraid to delete the files suggested by the script, so maybe that's why it didn't work?

[tophneal]

Hi again, sorry but no luck with the update. Deep sleep isn't working either, so i don't know if the update was successful.
Is there a simple way to check this out?
At the end of the script, another script was executed to clean the boot, but i was afraid to delete the files suggested by the script, so maybe that's why it didn't work?

No worries!

You really don't even need all of the script, you just need these 3 lines from the script run in terminal:

Code:

sudo dd if=idbloader.img of=<eMMC/microSD> bs=32k seek=1 conv=fsync
sudo dd if=u-boot.img of=<eMMC/microSD> bs=64k seek=128 conv=fsync
sudo dd if=trust.img of=<eMMC/microSD> bs=64k seek=192 conv=fsync

you can use any disk management software to find out if your emmc is mmcblk0 or mmcblk1 (do NOT write it to a partition ie mmcblk0p1.)

For deep sleep, there's a single file change that gets made to enable it. This post outlines what you need to do (you can skip the first step) https://forum.pine64.org/showthread.php?...0#pid68720

[slow_motion]

You really don't even need all of the script, you just need these 3 lines from the script run in terminal:

Code:

sudo dd if=idbloader.img of=<eMMC/microSD> bs=32k seek=1 conv=fsync
sudo dd if=u-boot.img of=<eMMC/microSD> bs=64k seek=128 conv=fsync
sudo dd if=trust.img of=<eMMC/microSD> bs=64k seek=192 conv=fsync

Yes that's what i ended up doing, but still no luck booting the android image.

I went to /boot/ to check what's in there, and i can only see idbloader.img modified on june 13th. u-boot.img and trust.img aren't there.

you can use any disk management software to find out if your emmc is mmcblk0 or mmcblk1 (do NOT write it to a partition ie mmcblk0p1.)

I used the command

Code:

[root@MakkiPBP ~]# findmnt -n -o SOURCE /
/dev/mmcblk2p2

so i deduced that emmc is mmcblk2.

For deep sleep, there's a single file change that gets made to enable it. This post outlines what you need to do (you can skip the first step) https://forum.pine64.org/showthread.php?...0#pid68720

I'll give this a try soon and see how it goes (maybe my PBP isn't cursed after all )

Thanks again for your time.

[tophneal]

Yes that's what i ended up doing, but still no luck booting the android image.

I went to /boot/ to check what's in there, and i can only see idbloader.img modified on june 13th. u-boot.img and trust.img aren't there.

What does the PBP do when you try to boot the Android SD?

You won't actually see them there. IIRC, the Manjaro partitions are offset from those areas of the drive that the uboot imgs actually reside. What you see in /boot are the mainline uboot files that can be updated with Manjaro (when updating Manjaro's uboot packages in CLI, you'll actually see a message to write the updated files to the drive and complete the uboot update.)

[slow_motion]

Yes that's what i ended up doing, but still no luck booting the android image.

I went to /boot/ to check what's in there, and i can only see idbloader.img modified on june 13th. u-boot.img and trust.img aren't there.

What does the PBP do when you try to boot the Android SD?

It just boot to manjaro. The microSD isn't the problem because when i already booted debian and kali with the same card.

[tophneal]

When Manjaro boots, instead of the SD, does Manjaro mount or show the SD?

If you downloaded any other Android imgs, it might be worth verifying that you're only working with the specific android that was linked. All the Androids linked for specific SD card sizes, will do that exact same thing.

[slow_motion]

When Manjaro boots, instead of the SD, does Manjaro mount or show the SD?

If you downloaded any other Android imgs, it might be worth verifying that you're only working with the specific android that was linked. All the Androids linked for specific SD card sizes, will do that exact same thing.

No it doesn't even detect the SD. Whereas it immediately shows the SD when i flash debian.
I will flash the android image linked again using etcher, in case i got confused with the images.

[tophneal]

No it doesn't even detect the SD. Whereas it immediately shows the SD when i flash debian.
I will flash the android image linked again using etcher, in case i got confused with the images.

I'd say go ahead and delete all the andoird imgs you downloaded, then download the confirmed working one (again?) that should help clear out any clutter/confusion.

[slow_motion]

No it doesn't even detect the SD. Whereas it immediately shows the SD when i flash debian.
I will flash the android image linked again using etcher, in case i got confused with the images.

I'd say go ahead and delete all the andoird imgs you downloaded, then download the confirmed working one (again?) that should help clear out any clutter/confusion.

Still booting to Manjaro despite flashing the sd again.
Maybe i'm missing something, here's the system info attached.

[tophneal]

What's in KDE's partiton manager?