OmniROM Android R (11) for Pi 4
- Thread starter maxwen
- Start date
Mount /dev/block/mmcblk0p1 and copy ramdisk.img to your /sdcard/Download directory. This is the image Magisk will patch and deposit a modified version in the /sdcard/Download directory. You will replace your original ramdisk.img you originally copied over. If you wanted to install the Magisk app via TWRP, feel free but I find the adb install of the apk from the magisk.zip we download easier than using TWRP.
I just found my notes. You need to combine the the "Image" and "Ramdisk.img" for Magisk.
apt install mkbootimg
mount partition1 somewhere
mkbootimg --kernel /<mountpoint1>/Image --ramdisk /<mountpoint1>/ramdisk.img --output boot.bin
mount partition4 somewhere
cp boot.bin /<mountpoint4>/media/0/Download/ (becomes /sdcard)
apt install mkbootimg
mount partition1 somewhere
mkbootimg --kernel /<mountpoint1>/Image --ramdisk /<mountpoint1>/ramdisk.img --output boot.bin
mount partition4 somewhere
cp boot.bin /<mountpoint4>/media/0/Download/ (becomes /sdcard)
The modified boot.img needs to be unpacked.
git clone https://github.com/anestisb/android-unpackbootimg.git
cd android-unpackbootimg
make
<path-to>unpackbootimg -i magisk_patched*.img
cp from new folder magisk_patched-xxxx.img-ramdisk.gz to /boot/ramdisk.img
done!
git clone https://github.com/anestisb/android-unpackbootimg.git
cd android-unpackbootimg
make
<path-to>unpackbootimg -i magisk_patched*.img
cp from new folder magisk_patched-xxxx.img-ramdisk.gz to /boot/ramdisk.img
done!
Do you have a guide for compiling only the kernel for OmniRom that can be transferred into the already built system? Is there a way to find out the kernel config for a current build? I can't find a kernel config or config.gz or similar anywhere else.
Last edited:
Does overclocking the gpu work? i.e. gpu_freq=750.
Also there's a persistent notification that says:
Also there's a persistent notification that says:
Attachments
Last edited:
Hi all,
i'm new here and I need help, every time that I download OmniRoom for Raspberry Pi 4, when I try to burn the image with balena or with rpi imager I only get the boot 134 MB available to burn in the sd card. Where can I download an image file, or how can I fix the file downloaded?
Thanks for your help
i'm new here and I need help, every time that I download OmniRoom for Raspberry Pi 4, when I try to burn the image with balena or with rpi imager I only get the boot 134 MB available to burn in the sd card. Where can I download an image file, or how can I fix the file downloaded?
Thanks for your help
The AOSP build system reads the kernel defconfig from here https://github.com/omnirom/android_...fdf67be939f44b301374b62e07/BoardConfig.mk#L57
Nathanchance's Guide is still my go to for kernel compilation, but modern kernel have custom toolchains like ones used in case of rpi4 https://github.com/omnirom/android_...fdf67be939f44b301374b62e07/BoardConfig.mk#L65
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
14OmniROM
Download
Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/
Images tagged with WEEKLY can be used to setup
official Google gapps
- 64bit build
- Tablet mode configuration (not Android TV)
- At least 4GB model recommened
- No HW accelerated video playback
- Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
- Support of booting from SD or USB by just changing config.txt (check README below)
- GPIO support - monitor and set README.gpio
- chrome (ium) is broken use alternative browser (firefox, edge)
- for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
- if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
- how to do updates? - check README.update
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800
Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720
Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community
For current progress and how to build yourself check
README.build
XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4
Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/
ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP
Version Information
Status: Stable
Created 2020-10-28
Last Updated 2020-10-283Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts
20201016
- Just a snapshot of the current state
- Non microG builds will come later
20201028
- WEEKLY and MICROG build
20201105
- TWRP included
IMPORTANT
Check new recovery section in README for all the details
EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
But after all of that hassle from now on updating will be much easier since with TWRP you can create
userdata backups on an external USB device very easy
So going from this release an update could work like this.
1) boot your current install into TWRP
2) create an userdata backup on an external USB device
3) flash the new build - you dont need to care about userdata
just do whatever you always do with it e.g. resize
4) boot new build
5) go into Advanced settings and switch boot mode to recovery and restart
6) in TWRP restore the backup you created before from external USB device
7) flash switch_boot_rom.zip and reboot system
8) enjoy - add boot mode switch in Advanced settings
- add audio output switch in Advanced settings
- whatever has been done since the last build
20201115
- fixed 5GHz WiFi AP
- fixed Fondar USB touch screen
- actual development
20201122
- switch to new kernel base - big thanks to Konsta - with update to 5.4.77
- update mesa to v20.2
- initial work to support pi camera - not yet working but close
- initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
- all core system updates and fixes
20201128
- performance tuning
- November security update
- gpio support update
- all core system updates and fixes
20201206
- added gpioi-fan
- cpufreq config in advancded settings
- all core system updates and fixes
20201214
- property persist.debug.drm.mode.force to adjust screen resolution
- all core system updates and fixes
20201224
- added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
- enabled showing BT device battery level if applicable
- all core system updates and fixes
- Best Xmas wishes for those who care about it and looking forward to 2021
20201231
- add WiFi firmware for p400
- kernel update 5.4.85
- add userdata resize and project quota enable script in TWRP
- reduce dB of max media volume
- all core system updates and fixes
1
Hello, i have the same problem. I would like to use the Omni ROM with my RPI4 an the 7" Raspberry Touch Screen. Please add the option to your nice ROM.
Please1is there a changelog somewhere ? i see there is a lot of development at https://dl.omnirom.org/tmp/rpi4/ - but no changelog.
I'd like to know if there is progress at USB-camera-support.
