[ROM][7.1.2][UNOFFICIAL][EYEUL] Resurrection Remix OS [5.8.5]

[ROM][7.1.2][UNOFFICIAL][EYEUL] Resurrection Remix OS [5.8.5] - HTC Desire Eye

Changelog
2018/02/16
sync upstream updates and fixes.
updated to Android 7.1.2_r36 with December Security Patches.
[*]revert back to original LineageOS kernel sources with latest security patches and android alarm patches. (front camera flash is now working)
2017/11/04 2017/11/04 RE-UPLOADED
fixed RIL issue of previous build, no need to flash other zips.
sync upstream updates and fixes.
2017/10/30
please flash this ZIP after ROM flashing to fix RIL/SIM problem. : HERE
sync upstream updates and fixes.
updated to RR 5.8.5.
with October Security Patches.
kernel security updates.
camera and codec updates.
bluetooth updates.
audio driver updates.
GPS config updates.
minor fixes and updates.
2017/09/12
sync upstream updates and fixes.
fixed Camera Key features that was broken on previous build.
rebasing kernel to latest LOS based, front LED might be broken for now.
2017/09/05
sync upstream updates and fixes.
revert all Gestures changes (should fix wake issue on previous build?).
older builds
2017/09/01
sync upstream updates and fixes.
switch to source-built GPS, AGPS should works now.
no more built-in Magisk, you have to flash it manually if you need.
Gestures supporting.
media profile updates.
2017/08/21
sync upstream updates and fixes.
switch to source-built RIL, please let me know if it works.
2017/08/08
sync upstream updates and fixes.
updated to Android 7.1.2_r29 with August Security Patches.
2017/08/06
updated to RR 5.8.4.
sync upstream updates and fixes.
GPU driver updated.
minor audio fixes.
2017/07/20 / 2017/07/22 2017/07/28
sync upstream updates and fixes.
updated Magisk to 13.3 Stable. (proper version)
fixed battery issues.
fixed camera button issues.
2017/07/07
sync upstream updates and fixes.
updated to Android 7.1.2_r24 with July Security Patches.
kernel: update WiFi driver.
update sepolicies.
2017/06/28
sync upstream updates and fixes.
merge many kernel CVE patches to improve security.
2017/06/09
sync upstream updates and fixes.
updated to Android 7.1.2_r17 with June Security Patches.
2017/06/06
upstream updates and fixes.
2017/05/23
upstream updates and fixes.
Camera Button can launch the camera from screen-off state with long pressing. (seems not waking device with a single click?)
correct battery capacity that showing on Android system. (2400mAh)
some minor tweaks related to sepolicy.
2017/05/08
upstream updates and fixes.
fixed Navigation Bar not showing when you finished SetupWizard.
added missing config for Sense Camera, you can set ISO and other settings now.
2017/05/07
upstream updates and fixes.
NFC fixed, Android beam is now working!
2017/05/06
initial build RR 5.8.3 for eyeul, eyetuhl (bring up all sources by importing M8 device sources)

Screenshots
Screenshots

Instructions
if you get device checking error when flashing build with TWRP, use this build for eyeul support properly -> TWRP
if you came from M8 modified ROM, re-install your driver on Windows will fix Device name in MTP mode.
no other boot.img needed for this ROM if you are doing clean flash or flashing same ROM from here over older version of RR.
if you are facing issue on Sense Camera like changing ISO or recording resolution, you can flash this fix to get it to work : FIX, also you have to download both Sense Camera and Sense Album to make preview works in camera.
in order to bypass SafetyNet checking for Android Pay , you have to enable Magisk Hide, and hide the following apps for bypassing:
com.android.cts.ctsshim
com.android.cts.priv.ctsshim
com.google.android.gms.setup
Google Play Store
Google Frameworks(com.google.android.gsf)
then reboot your phone.

tarkzim said:
if you get device checking error when flashing build with TWRP, you can edit META-INF\com\google\android\updater-script, and delete first line to bypass the checking.
if you came from M8 modified ROM, re-install your driver on Windows will fix Device name in MTP mode.
i will build a new TWRP for EYE, which can fix device name properly.
Click to expand...
Click to collapse
You mean I can do dirty flash from RR 5.8.3 M8 version?

WalterSilverio said:
You mean I can do dirty flash from RR 5.8.3 M8 version?
Click to expand...
Click to collapse
no, you will have to clean flash i think.

I have a AT&T tu_ca phone, s-off, unlock etc.
I tried cyanogen, cypher (with their new_boot.img 7.1.1), m8 ROM(RR and another one which i forgot the name) using new_boot.img 7.1.2 and ALL comes to the same problem : wifi and LTE crashes the OS.
So your ROM I doesn't need any boot.img or tuhl_to_eye.zip or something alike?

DoctorPINK said:
I have a AT&T tu_ca phone, s-off, unlock etc.
I tried cyanogen, cypher (with their new_boot.img 7.1.1), m8 ROM(RR and another one which i forgot the name) using new_boot.img 7.1.2 and ALL comes to the same problem : wifi and LTE crashes the OS.
So your ROM I doesn't need any boot.img or tuhl_to_eye.zip or something alike?
Click to expand...
Click to collapse
No need for any other boot.img

tarkzim said:
if you get device checking error when flashing build with TWRP, you can edit META-INF\com\google\android\updater-script, and delete first line to bypass the checking.
if you came from M8 modified ROM, re-install your driver on Windows will fix Device name in MTP mode.
change it from
Code:
(!less_than_int(1494001715, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat May 6 00:28:35 CST 2017) over newer build (" + getprop("ro.build.date") + ").");
assert(getprop("ro.product.device") == "htc_eyeul" || getprop("ro.build.product") == "htc_eyeul" || getprop("ro.product.device") == "eyeul" || getprop("ro.build.product") == "eyeul" || getprop("ro.product.device") == "eyetuhl" || getprop("ro.build.product") == "eyetuhl" || getprop("ro.product.device") == "htc_eyetuhl" || getprop("ro.build.product") == "htc_eyetuhl" || abort("E3004: This package is for device: htc_eyeul,eyeul,eyetuhl,htc_eyetuhl; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: htc/htc_asia_tw/htc_eyetuhl:6.0.1/MMB29M/707673.1:user/release-keys");
....
to something like this
Code:
ui_print("Target: htc/htc_asia_tw/htc_eyetuhl:6.0.1/MMB29M/707673.1:user/release-keys");
....
i will build a new TWRP for EYE, which can fix device name properly.
Click to expand...
Click to collapse
error 3004, modified and now error: 6
just another Nougat ROM fail for me.... :crying:

DoctorPINK said:
error 3004, modified and now error: 6
just another Nougat ROM fail for me.... :crying:
Click to expand...
Click to collapse
use my new TWRP instead... DOWNLOAD

tarkzim said:
you might deleted something shouldn't be removed...
copy it
Code:
(!less_than_int(1494001715, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat May 6 00:28:35 CST 2017) over newer build (" + getprop("ro.build.date") + ").");
ui_print("Target: htc/htc_asia_tw/htc_eyetuhl:6.0.1/MMB29M/707673.1:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" RRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRR ");
ui_print(" R::::::::::::::::R R::::::::::::::::R ");
ui_print(" R::::::RRRRRR:::::R R::::::RRRRRR:::::R ");
ui_print(" RR:::::R R:::::R RR:::::R R:::::R");
ui_print(" R::::R R:::::R R::::R R:::::R");
ui_print(" R::::R R:::::R R::::R R:::::R");
ui_print(" R::::RRRRRR:::::R R::::RRRRRR:::::R ");
ui_print(" R:::::::::::::RR R:::::::::::::RR ");
ui_print(" R::::RRRRRR:::::R R::::RRRRRR:::::R ");
ui_print(" R::::R R:::::R R::::R R:::::R");
ui_print(" R::::R R:::::R R::::R R:::::R");
ui_print(" R::::R R:::::R R::::R R:::::R");
ui_print(" RR:::::R R:::::R RR:::::R R:::::R");
ui_print(" R::::::R R:::::R R::::::R R:::::R");
ui_print(" R::::::R R:::::R R::::::R R:::::R");
ui_print(" RRRRRRRR RRRRRRR RRRRRRRR RRRRRRR");
ui_print(" ");
ui_print(" ");
ui_print(" **************** Software *****************");
ui_print(" OS ver: RR-N-v5.8.3-20170505-eyeul-Unofficial");
ui_print("");
ui_print(" Android ver: 7.1.2");
ui_print("");
ui_print(" Security patch: 2017-05-05");
ui_print("");
ui_print(" SDK ver: 25");
ui_print("");
ui_print(" Root status: Enabled");
ui_print("");
ui_print(" Build ID: N2G47O");
ui_print("");
ui_print(" Build date: Sat May 6 00:28:35 CST 2017");
ui_print("");
ui_print(" Build type: Unofficial");
ui_print("");
ui_print(" Build host: enfeckerserver1");
ui_print("");
ui_print(" Maintainer: enfecker");
ui_print(" **************** Hardware *****************");
ui_print(" Device codename: eyeul");
ui_print("");
ui_print(" Manufacturer: HTC");
ui_print("");
ui_print(" LCD density: 480");
ui_print("");
ui_print(" *******************************************");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("f2fs", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print(" ");
ui_print("Flashing Magisk...");
ui_print(" ");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/magisk.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("/sbin/sh", "/tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/magisk.zip");
ui_print(" ");
show_progress(0.200000, 10);
set_progress(1.000000);
Click to expand...
Click to collapse
Same error: 6

DoctorPINK said:
Same error: 6
Click to expand...
Click to collapse
well, you can wait for my proper TWRP for EYE to flash it,
then you will get no issue.

TWRP support
hey guys, updated in OP,
uploaded my TWRP build for properly support eyeul ROMs flashing, no more device-name check while flashing, but MTP for TWRP is broken for now,
i'm working on it to fix, so if you are facing any flashing issue please use this TWRP to flash this ROM, thanks.

new builds released
with NFC fixed, please test it with android pay, thanks.

new builds released
with some minor changes, including:
fixed navigation bar sometimes not showing.
fixed sense camera configs for adjusting settings.

AT&T, UL_CA, S-OFF
still can't install, error : 7 with your TWRP

DoctorPINK said:
AT&T, UL_CA, S-OFF
still can't install, error : 7 with your TWRP
Click to expand...
Click to collapse
What exactly that error says? Can you take a picture or post it here? Thanks.

tarkzim said:
What exactly that error says? Can you take a picture or post it here? Thanks.
Click to expand...
Click to collapse
I don't remember, tired of flashing ROMs that doesn't work.
But I Flashed Cypher, Cyanogen, cr, Lineage and all worked except it crashes when using Wifi and LTE. (Nougat 7.1.2)

DoctorPINK said:
I don't remember, tired of flashing ROMs that doesn't work.
But I Flashed Cypher, Cyanogen, cr, Lineage and all worked except it crashes when using Wifi and LTE. (Nougat 7.1.2)
Click to expand...
Click to collapse
A photo of the error would help.

Network settings are lte/utms or lte/gms and apn settings are nexgenphone use *#*#4636#*#* to see network settings and go to settings, then data usage, click three dots upper right corner, cellular networks, then apn hope this helps. Lte will show as 4g on status bar.

Related

[Kernel][DS]NeOcOre-Hybrid™ [release 5][Discontinued]

HELLO WORLD,
thirdzcee here and once again i bring new kernel for our beloved device, i have come to a decision to stick with a modified 4.2.2 stock c2005 firmware crossflashed to my c1905 and in the process rebuilt my kernel from scratch to work with the c2005 firmware, so here it is guys, my initial release,,,, hope you guys like it....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Advanced Kernel for our Xperia M
Whats inside???
Compiled from 15.2.A.1.12 stock kernel source Now on 15.2.A.2.5 Kernel source
XZ compressed
cwm 4.0.4.5 4.0.4.6
Compiled with linaro 4.7.4 toolchain with O2 O3 optimizations
CPU overclocked to 1.4ghz 1.7ghz for more performance
CPU underclocked down to 162 mhz for more power saving during standby
GPU overclocked to 450mhz 487mhz plus 2D gpu tweaks to increase the mediocre performance of 2D graphics in our phone
GPU underclocked to 128 mhz for more battery savings when on non gprahics intensive situations/apps
intellidemand badass governor as default cpu governor
ROW sioplus as default io scheduler
dynamic fsync, a great partner to row iosched
gentle fair sleepers disabled for more responsiveness
asynchronous io latency increased
entropy random tweaks partnered with frandom module for blazing fast randomness generation
zram,optimized for android too, we just cant have enough ram.. LOL
ARCH Power & CPU Power, lets make use of the optimized arm architecture for handling multithreading rather than generic architecture handling
MORE IN THE CHANGELOGS BELOW
Click to expand...
Click to collapse
BEFORE WE DOWNLOAD AND INSTALL.. A FRIENDLY REMINDER
Code:
[COLOR="Red"][SIZE="4"]* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems[/SIZE][/COLOR]!
DOWNLOADS
release 1
release 2
release 3 cwm flashable
release 4 cwm flashable
release 5 cwm flashable
HOW TO INSTALL
Hard Way/fastboot Method
BOOTLOADER MUST BE UNLOCKED
ADB & FASTBOOT ALONG WITH XPERIA M DRIVERS MUST BE INSTALLED IN YOUR PC
open cmd in the location where you saved the kernel image
run this command from cmd
Code:
fastboot flash boot neocore.img
now this
Code:
fastboot reboot
wait for phone to boot and enjoy
Easy Way/CWM Method
BOOTLOADER MUST BE UNLOCKED
Download CWM FLASHABLE ZIP RELEASE
Reboot to recovery
INSTALL ZIP FROM SDCARD0/SDCARD1 (DEPENDS ON WHERE YOU SAVED IT)
INSTALL AND WAIT FOR PHONE TO REBOOT
changelogs
release 1
initial release
Compiled from 15.2.A.1.12 stock kernel source
XZ compressed
cwm 4.0.4.5
Compiled with linaro 4.7.4 toolchain with O2 optimizations
CPU overclocked to 1.4ghz for more performance
CPU underclocked down to 162 mhz for more power saving during standby
GPU overclocked to 450mhz plus 2D gpu tweaks to increase the mediocre performance of 2D graphics in our phone
intellidemand governor as default cpu governor
ROW as default io scheduler
dynamic fsync, a great partner to row iosched
gentle fair sleepers disabled for more responsiveness
asynchronous io latency increased
entropy random tweaks partnered with frandom module for blazing fast randomness generation
zram,optimized for android too, we just cant have enough ram.. LOL
ARCH Power, lets make use of the optimized arm architecture for handling multithreading rather than generic architecture handling
i might have forgotten the other stuff
Click to expand...
Click to collapse
Release 2
removed underclock - eventually sods were encountered
intelliactive governor added
BFQ iosched added
SIOPLUS iosched added
optimized aes & sha1 routines with support for bit sliced aes using neon intructions
vm max readahead set to 2048
enabled system wide mounting
GPU OCincreased to 487mhz, added 266mhz in between and underclocked to 128mhz
LMK tweaked,
android logger reserved memory lowered some more
some other stuff added as well but disabled from config due to wifi breakage, scumbag prima module still wont work :crying:
Release 3
Finally FIXED SOD's and random reboots, was caused by my gpu fiasco, max gpu back to 450mhz and no more 266mhz
added badass governor
added fiops iosched
added zen iosched
readahead reduced to 512kb
thermal throttle increased limit to 75 degrees (stock was 60)
increased the minimum undervolt limit just to make sure no more SOD's or random reboots
Release 4
cwm 6.0.4.6 touch gesture recovery added
new intelli thermal driver used over the stock thermal driver, use trickster mod to tweak it
OC up to 1.7ghz
compiled with o3 optimizations
compiled with ARM specific optimization flags
updated sources to the latest 15.2.A.2.5 kernel source
retuned the frequencies to use only effecient clock speeds
Release 5
faux sound control now working i think ( could be placebo somebody confirm, download faux sound control (paid) to test
retuned the voltages
added arm auto hotplug driver
added intelliplug to replace mpdecision (enabled by default, use trickster mod to disable mpdecision)
added usb fast charge
some more tweaks to random/entropy
enable/disable fsync (use trickster mod, phone flies with fsync and dynfsync disabled)
some more build optimizations
faster integer sqr root operation
zram tweaks
wheatley cpu governor added
Credits
linaro for toolchain
alvinhochun for cwm
icoolguy1995 discussion and some commits
andro-SYR for cwm kernel flasher
faux123
showp1987
GPL compliance :angel:
kernel SOURCE
XDA:DevDB Information
Neocore Hybrid Engine, a Kernel for the Sony Xperia M
Contributors
thirdzcee
Kernel Special Features: o3 optimized, Arch Power, CPU Power, zram, CPU OC/UC, GPU OC, intelliplug, autoplug, row iosched, intellidemand, frandom, intelliactive, badass, zen, fiops, sound control by faux123
Version Information
Status: Beta
Current Beta Version: release 3
Beta Release Date: 2014-02-27
Created 2014-02-09
Last Updated 2014-03-30

Reserved
how to features???
zram
Method 1, easy method
use trickster mod and turn on the zram switch, 10% of phone ram will automatically be allocated to zram
Method 2, hard but configurable method
USE ANY TERMINAL EMULATOR OF YOUR CHOICE
1)need to be root 1st so use this command
Code:
su
2) create zram size
initialize /dev/zram0 with 96mb disksize with this command
Code:
echo 10066329 > /sys/block/zram0/disksize
note: Disksize cannot be changed if the disk contains any
data. deactivate first before you can change its disksize.
use this formula for calculating the disksize you want
( ill use my 96mb as an example)
Code:
96mb= 96×1024×1024)
3) activate:
Code:
mkswap /dev/block/zram0
swapon /dev/block/zram0
4) stats: To check if you have swap enabled
Code:
free
and it should return something like this
Code:
total used free shared buffers cached
Mem: 506188 419736 86452 0 49404 121960
-/+ buffers/cache: 248372 257816
Swap: 1534200 100348 1433852
*its from my pc not my phone but it should look similar
5) deactivate:
Code:
Swapoff /dev/block/zram0
Click to expand...
Click to collapse
Intelli Thermal Driver
Use Trickster Mod to enable (disabled by default) and adjust settings,
settings are self explanatory
Click to expand...
Click to collapse
Intelliplug
open source replacement to qualcomm's mpdecision,
enabled by default, also has eco mode enabled by default
use trickster mod to enable/disable
Click to expand...
Click to collapse
fsync toggle
use trickstermod to switch fsync/dynfsync on/off (enabled by default)
Click to expand...
Click to collapse
Sound Control
kernel level control of sound parameters, use faux's sound control app or donate version of trickster mod to access, if not you can manually tune parameters by editing the values in /sys/kernel/sound_control
Click to expand...
Click to collapse

Reserved
latest release 4 performance

I think you should disable ARCH power. I have done lots of test and found that ARCH power reduce battery life.

icoolguy1995 said:
I think you should disable ARCH power. I have done lots of test and found that ARCH power reduce battery life.
Click to expand...
Click to collapse
Battery seems fine to me... 9hours has passed, 1hour of screen time on and only 20% was drained, I have yet to verify with a continuous use though rather than a sort of checking phone from time to time method
Sent from my C2005 using XDA Premium 4 mobile app

Why you don't use base 15.2.A.2.5?
Is it save to use that firmware?
Thanks

Cause its the firmware my phone is on... Its probably safe and ill be updating the sources anyway...
Sent from my C2005 using XDA Premium 4 mobile app

thirdzcee said:
Cause its the firmware my phone is on... Its probably safe and ill be updating the sources anyway...
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Release 3, but the source is same?
I think you must update to 15.2.A.2.5, to give more performance n stability...

mathacer said:
Release 3, but the source is same?
I think you must update to 15.2.A.2.5, to give more performance n stability...
Click to expand...
Click to collapse
if you checked my github youll see i already have a branch for 15.2.A.2.5, ill be merging them maybe tonight if im not tired or tommorow :fingers-crossed: , release 2 had reboot and sod bug due to wrong gpu tables,

Great to see development kernel on M dual is up to date...
Yeah release 4 is more stable n no random reboots, very nice n go on...
:cheers

Wait till release 5, we will enter the realm of the nexus 4
Sent from my C2005 using XDA Premium 4 mobile app

thirdzcee said:
Wait till release 5, we will enter the realm of the nexus 4
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Damn! Now that's some serious scores! Btw, which kernel are you talking about? Your kernel (ironbuang) or Neocore?

It's probably NeOcOre
Sent from my C1905 using Tapatalk 4

Status 6 error in CWM.
Cant install on C1905.
Re downloaded but still the same error sdcard0 or 1,doesnt matter.
Any tips?
N.

Hey its for Dual sim version......
Sent from my C2004 using Tapatalk 4

Install with flash tool, extract and find boot.img
Sent from my C2004 using xda app-developers app

@roulley....
Hey he is saying that he got an error on c1905 and the kernel is for c2005....
Sent from my C2004 using Tapatalk 4

I just told him what I do to my Xperia M single sim device, and it work with no problem
Sent from my C2004 <---- it's because I use xm dual firmware using xda app-developers app

BlackArtsInc said:
Status 6 error in CWM.
Cant install on C1905.
Re downloaded but still the same error sdcard0 or 1,doesnt matter.
Any tips?
N.
Click to expand...
Click to collapse
Open updater-script with notpad+ and add ; to the end of every line and retry
Sent from my C2005 using Tapatalk

Advanced Kernel for our Xperia M
Click to expand...
Click to collapse
No one said anything about Dual M.
Anyway,I ll try the script edit and report back!
Thanks for the suggestion.
N.
Here s what the script looks like:
ui_print("Neocore Release 3");
ui_print("Ironbuang-Systems™");
ui_print("by thirdzcee @ XDA");
run_program("/sbin/sleep", "5");
ui_print(" YOU HAVE 15 SECONDS TO PULL OUT THE ");
ui_print(" PHONE BATTERY IF YOU CHANGED");
ui_print(" YOUR MIND IN FLASHING KERNEL ");
run_program("/sbin/sleep", "10");
ui_print("time is almost up");
run_program("/sbin/sleep", "5");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" ");
package_extract_dir("system", "/system");
ui_print("writing kernel...");
package_extract_file("boot.img", "/dev/block/mmcblk0p17");
ui_print("complete");
ui_print("Rebooting phone in");
run_program("/sbin/sleep", "1");
ui_print("5")
run_program("/sbin/sleep", "1");
ui_print("4")
run_program("/sbin/sleep", "1");
ui_print("3")
run_program("/sbin/sleep", "1");
ui_print("2")
run_program("/sbin/sleep", "1");
ui_print("1")
run_program("/sbin/sleep", "1");
ui_print("Rebooting")
run_program("/sbin/busybox", "reboot");
run_program("/sbin/reboot");
ui_print("Reboot fail, reboot manually ")
Click to expand...
Click to collapse

[ROM] [4.4.2] TeamEOS - The Revival || Nightlies

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Eos! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Bigrushdog - Project lead, Chief Developer [Xoom || Galaxy Nexus || HTC One (M7)]
RaymanFX - Co-leader, AOSP code maintainer [Xperia S || Nexus 7 (2013) || OPPO N1 || OPPO Find7a]
jrior001 - Jenkins/Gerrit Admin, CAF code maintainer [HTC One X]
anders3408 - Frameworks Developer [OPPO Find5 || OPPO N1]
Roach - Frameworks Developer [Nexus 4 || Nexus 7 (2013) || HTC One (M8)]
Connor Baker [Nexus 4 || HP Touchpad]
Code:
NX Gesture Navigation Bar
EOS Weather Engine
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Network Indicator
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Force Navigation Bar on any device
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded.
Team EOS N1 Nightly builds
N1 <<< Link >>>
G-Apps Package
Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:
GApps <<< Link >>>
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.4.x COMPATIBLE RECOVERY.
Detailed instructions:
Going to EOS4.4.x from a rom < 4.4.x:
Backup everything !
Go to recovery
Make a full wipe / factory reset
format /system
Flash the rom
Flash optional kernel
Flash gapps
Reboot
Updating from EOS 4.4.x #XX to #YY:
You can usually skip the full wipe step.
If ever you encounter an issue make sure you make a full wipe first before reporting though.
N1 comes with a custom kernel, featuring the latest CAF kk_2.7-stable patches and designed specially for EOS.
Contribute
Gerrit Review
Jenkins Build System
Github
XDA:DevDB Information
TeamEOS, ROM for the Oppo N1
Contributors
teameos, RaymanFX, anders3408
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Created 2014-05-22
Last Updated 2014-05-22

Lately we added a easy way to install drives. This makes the usually hidden partition on N1 visible as a cd drive on your windows computer.
Go to Settings ---> Storage ---> Menu ---> USB-Connection to Computer ---> mark Driver install (needs 2 clicks)
Then it should be visible on the computer. When done installing via the Setup.exe, switch to mtp or ptp, and it should work.

I'm downloading and following the oppoforum thread too.:good:

o-touch and o-click work well ?

cleonardo said:
o-touch and o-click work well ?
Click to expand...
Click to collapse
As far as I know they don't. Look in oppoforums.com for more info.
@anders3408 Is 8 second exposure working?

Please add Screenshots!

o-click , o-touch not work ? so sad

cleonardo said:
o-click , o-touch not work ? so sad
Click to expand...
Click to collapse
We do have both o-click and o-touch ?
for otouch : go to settings->more (under EOS)
for oclick : simply open oppo's oclick app, its preinstalled

cool ,let go , test right now.

hi
The Gapps link say
The file you requested was not found
Lets see if we can find that for you...
No search results were found...

We are getting closer having OTA support in. The base for the backend (server part) and the base for the app is running, but there is still several things todo before its ready for release.

[MOD][29 October] MultiROM v32b - the ultimate multiboot method! [EOL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM for the Samsung Galaxy S4 (Qualcomm variants)
Brought to you by AntaresOne
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S4. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel - Download the ZIP file and flash it in recovery or keep stock kernel (only for CM11-based ROMs after 6 August 2014 & CM12-based ROMs)
You current rom will not be erased by the installation.
Download links are in the third post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
3. Other systems (once ported to device)
Firefox OS and Sailfish OS are just another Android ROM under MultiROM's point of view, so add them as if it were Android.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Alucard Kernel w/ kexec-hardboot patch - https://github.com/Alucard24/Alucard-Kernel-jfltexx
Googy-Max3 kernel w/ kexec-hardboot patch - https://github.com/googyanas/Googy-Max3-Kernel
Hulk kernel w/ kexec-hardboot patch - https://github.com/Tkkg1994/Hulk-Kernel
Imperium kernel w/ kexec-hardboot patch - https://github.com/Slim80/Imperium_Kernel_TW_4.4.2
KT kernel w/ kexec-hardboot patch - https://github.com/ktoonsez/KT-SGS4
CM11 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-11.0
CM12 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.0
CM12.1 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.1
MultiROM device tree - https://github.com/AntaresOne/multirom_device_samsung_jflte
Big thanks to Tasssadar for this awesome utility.
Thanks a lot to @daveyannihilation for the S4 template.
XDA:DevDB Information
MultiROM, multiboot for Galaxy S4 (Qualcomm variants) (GRUB-like), Tool/Utility for the Samsung Galaxy S4
Contributors
AntaresOne
Version Information
Status: No Longer Updated
Current Stable Version: 20151029-v32b
Stable Release Date: 2014-09-01
Created 2014-09-01
Last Updated 2017-05-19

Changelog
15/6/2015 - v32a
Update after 6 months!! read post #669
Modified TWRP:
Base updated to 2.8.6.0
Sacrificed crypto and embedded SuperSU installer to get an image that fits 10.5MB recovery partition size
Detailed changes here
MultiROM:
Base update to v32
Added support for 5.1.x Lollipop ROMs
Better support for 5.0.x Lollipop ROMs
Detailed changes here
16/12/2014 - v30c
Modified TWRP:
Base updated to 2.8.2.0
Better support for primary/secondary Lollipop ROMs install/update
MultiROM:
Better support for Lollipop-based ROMs
Fixed the ghost update found in previous build
26/11/2014 - v30
Modified TWRP:
Add partial support for block_image_update in secondary ROMs ZIPs (Lollipop's default flashable zip format)
MultiROM:
Assume fstab version 2 by default
Fix klog saving and text size on emergency reboot screen
Write fstab for fw_mounter as version 2
12/11/2014
Device source:
Disable TWRP event logging
Modified TWRP:
Build an updated image without event logging
4/11/2014
Modified TWRP:
Add back "Share kernel" option (same behavior can be obtained by pressing "Remove boot.img" under MultiROM>List ROMs>*rom name*)
30/10/2014
Modified TWRP:
Update to v2.8.1.0
25/10/2014 - v29
MultiROM:
Minor updates
Full MultiROM Manager support (this fixes the ghost update)
Modified TWRP:
Full MultiROM Manager support
Uninstaller ZIP:
Add support for other jf variants
2/10/2014
Add support for MultiROM Manager app
1/10/2014 - v28c
Device source:
Add MicroSD Card to init devices
Fixed device autoboot in recovery after a reboot/shutdown
30/9/2014 - v28b
MultiROM:
ROM boot from external SD (MicroSD card) is now supported
TWRP Recovery:
General update (branch master)
Removed "Share kernel" option
ROM Installation to external SD (MicroSD card) is now supported
Uninstaller ZIP added back and now working
16/9/2014
TWRP Recovery:
Better MTP compatibility
12/9/2014
TWRP Recovery:
Merge twrp28 branch (now has MTP connection inside to transfer files between PC and device)
6/9/2014
Device source:
Clean and update init devices
Add volume keys init (now you can select ROM/tabs also with volume keys)
3/9/2014
Fixed installation on other jflte devices
1/9/2014 - v28
Device source:
add power button init (needed to reboot device when "an error occurred" and to exit from pong game, available by clicking on Miri)

Downloads
1. Main downloads
MultiROM EXT4 (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849558
MultiROM F2FS (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849563
Modified TWRP (20151029-v2.8.7.0): https://www.androidfilehost.com/?fid=24052804347849556
MultiROM Manager App: Google Play Store (by default it will install the EXT4 version!)
2. Kernels for primary ROM (Internal) based on Android 5.1.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.1 ROMs:
AOSP 5.1 & Optimized CyanogenMod 12.1 from JDCTeam: Alucard is embedded and always up to date
Alucard AOSPv2 5.1 v1.3ba
Stock CM12.1 kernel (included in ROM's zip)
3. Kernels for primary ROM (Internal) based on Android 5.0.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.0 ROMs:
Optimized CyanogenMod 12 from me and @alucard_24: Alucard is embedded and up to date
Alucard AOSPv2 5.0 v1.1a
Googy-Max3 v1.3.0
Hulk Kernel v1.3.1
KT-SGS4-LP5.0
Stock CM12 kernel (included in ROM's zip)
Kernel with kexec-hardboot patch for Google Edition 5.0 ROMs:
Alucard GE5 v1.1a
Hulk Kernel GE5 v1.3.1
Googy-Max3 GE5 v1.2.3c
Kernel with kexec-hardboot patch for TouchWiz 5.0.1 ROMs:
Hulk Kernel TW5 v1.3.1
Imperium LL v2.0
4. Kernels for primary ROM (Internal) based on Android 4.4.x KitKat
Kernel with kexec-hardboot patch for AOSP/CM 4.4 ROMs:
(builds up to 6 August, including CM11 M9)
Alucard AOSP v2.7.2a
(builds after 6 August, including CM11 M10)
Alucard AOSPv2 v1.4r
Googy-Max3 CM v1.2.5
KT-SGS4-KK
Stock CM11 kernel (included in ROM's ZIP) - All CM11-based ROMs after 6/08 with this android_kernel_samsung_jf source
Kernel with kexec-hardboot patch for Google Edition 4.4.x ROMs:
Alucard GE v2.4d
Googy-Max3 GE v1.2.8
Kernel with kexec-hardboot patch for TouchWiz 4.4.4 ROMs:
Googy-Max3 v1.3.0 TW 4.4.4
Hulk Kernel v1.2 TW 4.4.4
Imperium v1.14 TW 4.4.4
Kernel with kexec-hardboot patch for TouchWiz 4.4.2 ROMs:
Alucard TW v2.3ga
Googy-Max3 v1.3.0 TW 4.4.2
Hulk Kernel v1.2 TW 4.4.2
Imperium v1.14 TW 4.4.2
5. Uninstaller
MultiROM uninstaller ZIP: https://www.androidfilehost.com/?fid=95747613655050515
Just flash this to disable MultiROM and delete all secondary ROMs.
Alucard-PWR-CORE dev thread by @alucard_24: http://forum.xda-developers.com/showthread.php?t=2590246
Googy-Max3 dev thread by @googy_anas: http://forum.xda-developers.com/showthread.php?t=2741181
Hulk Kernel dev thread by @Tkkg1994: http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
Imperium dev thread by @slim80: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/kernel-imperium-kernel-v1-0-t2910801
KT-SGS4 dev thread by @ktoonsez: http://forum.xda-developers.com/showthread.php?t=2297379

Useful tips
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
What storage for ROMs is supported?
Internal memory (/data/media-/sdcard) is supported as well as MicroSD card (/external_sd).
How many ROMs can I have and where are stored?
You can have as many ROMs as you can fit in internal memory and MicroSD card. All the ROMs are stored in /data/media/0/multirom/roms (in case of internal memory) and /external_sd/multirom/roms (in case of MicroSD card) drive. These folders are unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
I'm a F2FS user. Can I still enjoy MultiROM?
Yes, you can. Just flash F2FS version of MultiROM zip. NOTE: it is compatible only with full F2FS (so cache, data and system both at once), if you use a custom layout like F2FS for cache/data and EXT4 for system just edit the mrom.fstab file inside the MultiROM zip before flashing the first time or after with reflashing.
Can I have different versions of Android working alongside?
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, systems are separated.
Can I flash TouchWiz-based ROMs as secondary ROMs?
You can, but it's strongly unrecommended and not all the TW ROMs work if installed as secondary, plus are very bigger than other ROMs. I suggest to flash them only as primary ROM.
Can I configure boot menu to be showed only when I want?
You can. Boot in TWRP recovery, go under Advanced>MultiROM>Settings>Configure autoboot and set Keypress-based, then select a ROM to autoboot. In this way, if you power on your device boot menu isn't showed and the ROM you choose to autoboot is booted, but if you power on and rightly when you see "Samsung Galaxy S4" bootlogo you press and keep pressed Vol+ or Vol- button, boot menu is showed.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.

Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!

nds850 said:
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
Click to expand...
Click to collapse
Alright I tried beanstalk like you mentioned and it rebooted into recovery the first time I tried booting in to it. It worked fine the 2nd time however. Currently have dirty unicorns, pa, and now bs. Sometimes when I click reboot on either one of these ROMs, it automatically reboots to recovery instead of multiboot. Don't know of this is a bug or not.

@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 256 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505

AntaresOne said:
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 128 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Cool. Thanks for the explanation. This multiboot is really awesome

I'm not sure I understand how you mean. I completely shut the phone off and wait for the RAM to reset. I then start the phone and in the MultiROM menu choose the ROM I want to use. The phone restarts and load to recovery. Does the RAM need to be cleared after choosing the ROM? If that is the case how do I do that?

sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?

BakaB said:
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
Click to expand...
Click to collapse
I would assume so. It should work on all jflte's. It works fine on my jflteusc.

@BakaB @bdog2015
Yes, it works on all jflte devices.
I337, I545, L720, M919, R970, I9505, I9507, I9508
Inviato dal mio GT-I9505

I have been trying to flash the MultiROM zip through TWRP Recovery and I keep getting the following errors:
Code:
assert failed: getprop("ro.product.device") == " jflte" | | getprop("ro.build.product") == " jflte "
But what's weird is that both the lines that script is looking for (ro.product.device & ro.build.product) both say jflte in my build.prop so I'm very confused. I'm running Alliance ROM v2.0 I9505XXUGNG2 with stock permissive kernel and TWRP 2.7.1.0
Any help/advice would be appreciated.

@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505

AntaresOne said:
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Ok MultiROM is installed. After installing MultiROM I flash TWRP_multirom_jflte_20140901.zip through TWRP and then reboot recovery. When TWRP reboots, I don't have any options under Advanced for MultiROM. Recovery is now showing 2.7.1 in the top left whereas before it was showing as 2.7.1.0 so I know that the recovery has changed.
Have I done something wrong? When I reboot the phone I get the MultiROM boot screen coming up asking me to either let it boot into the internal ROM or touch to change, but when I boot into recovery I have no options for MultiROM. I am happy to upload any logs that might help to decipher the issue I am having.
Thanks for your help mate.

@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505

AntaresOne said:
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Dude... I'm just an idiot. I had twrp holofied which wasn't showing the menus and buttons. This mod is AMAZING!!! Dude I have been looking for this forever, you are a king. I'm definitely gonna be using this from now on, thank you so very very much! [emoji4]
Alliance I9505

@daveyannihilation
Hahaha don't worry
Now just remember this
Inviato dal mio GT-I9505

Is the new build recommended or am I fine if everything is working for me?

bdog2015 said:
Is the new build recommended or am I fine if everything is working for me?
Click to expand...
Click to collapse
The only change in new build is the fixed installation on other jflte devices. If you installed the previous build without errors, no need to update [emoji1]
Inviato dal mio GT-I9505

[ROM] DivestOS 20.0 for cheeseburger/dumpling

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-cheeseburger, https://divestos.org/index.php?page=devices&base=LineageOS#device-dumpling
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#oneplus5
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_oneplus_msm8998-common, https://github.com/LineageOS/android_device_oneplus_cheeseburger, https://github.com/LineageOS/android_device_oneplus_dumpling
- Kernel: https://github.com/LineageOS/android_kernel_oneplus_msm8998
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...VE_Patchers/android_kernel_oneplus_msm8998.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

Thank you very much. Sounds like a great project, I will flash later.

DivestOS does *not* support the following:
- Google Apps = GREAT !
- DRM (Widevine) =
- alternative recoveries (TWRP) = wat ?
- root (Magisk) = maybe not for me
- runtime modification frameworks (Xposed or theme engines) = definitely not for me !

Added to the OnePlus 5 Index Thread here.

Great from the privacy prespective.
Jailed situation from 'people-who-want-to-do-what-they-want' prespective.

JohnWrick said:
Great from the privacy prespective.
Jailed situation from 'people-who-want-to-do-what-they-want' prespective.
Click to expand...
Click to collapse
Anything in particular you'd like to see?
fwiw there is a build guide: https://divestos.org/index.php?page=build

SkewedZeppelin said:
Anything in particular you'd like to see?
fwiw there is a build guide: https://divestos.org/index.php?page=build
Click to expand...
Click to collapse
I've been trying to build but keep running into errors. when I try to run patchWorkspace, gpg verification fails, and when I try to run buildDevice, it gives this error:
error: system/linkerconfig/Android.bp:17:1: "linkerconfig_defaults" depends on undefined module "libapexutil-deps"
Also, if I wanted to build it with full microg and no deblobbing, how would I do that?

rasputin_g said:
I've been trying to build but keep running into errors. when I try to run patchWorkspace, gpg verification fails, and when I try to run buildDevice, it gives this error:
error: system/linkerconfig/Android.bp:17:1: "linkerconfig_defaults" depends on undefined module "libapexutil-deps"
Also, if I wanted to build it with full microg and no deblobbing, how would I do that?
Click to expand...
Click to collapse
Interesting. It should've failed quicker then that.
To enable microG: set DOS_MICROG_INCLUDED to "FULL" in Scripts/init.sh
To disable the deblobber: comment Deblob.sh in Scripts/Lineage-18.1/Functions.sh
You should also set all the DOS_DEBLOBBER_REMOVE_* to false in Scripts/init.sh
GPG verification will likely fail if you haven't run importKeys from PrebuiltApps/update.sh
The linker error, I am not sure what you are missing. Not one I've seen. Maybe your repo sync failed?

I did have one error while running repo sync, but it was for the Samsung kernel so I didn't think anything of it. I'll try running repo sync again. Thanks! I love the ROM and having a locked BL but I would love to have GCM and working DRM which is why I wanted to build it myself.

SkewedZeppelin said:
Interesting. It should've failed quicker then that.
To enable microG: set DOS_MICROG_INCLUDED to "FULL" in Scripts/init.sh
To disable the deblobber: comment Deblob.sh in Scripts/Lineage-18.1/Functions.sh
You should also set all the DOS_DEBLOBBER_REMOVE_* to false in Scripts/init.sh
GPG verification will likely fail if you haven't run importKeys from PrebuiltApps/update.sh
The linker error, I am not sure what you are missing. Not one I've seen. Maybe your repo sync failed?
Click to expand...
Click to collapse
GPG verification still failed even after I ran importKeys. Any idea why? Also, what's the deal with the GPG signing on the ROM itself? Do I need to do something to set that up?

rasputin_g said:
GPG verification still failed even after I ran importKeys. Any idea why? Also, what's the deal with the GPG signing on the ROM itself? Do I need to do something to set that up?
Click to expand...
Click to collapse
You don't need to GPG sign your builds unless you want anyone you're distributing it to to be able to verify it is from you.
As for the verification error, can you post the error? Did you run: git submodule update --init --recursive ?

SkewedZeppelin said:
You don't need to GPG sign your builds unless you want anyone you're distributing it to to be able to verify it is from you.
As for the verification error, can you post the error? Did you run: git submodule update --init --recursive ?
Click to expand...
Click to collapse
Yeah I ran the git submodule command. Turns out I had forgotten to run downloadAllApps to update all of the apps that correspond to the newest signatures. No more gpg verification error.

rasputin_g said:
Yeah I ran the git submodule command. Turns out I had forgotten to run downloadAllApps to update all of the apps that correspond to the newest signatures. No more gpg verification error.
Click to expand...
Click to collapse
OH!
You shouldn't have to download them, you need git-lfs installed.

SkewedZeppelin said:
OH!
You shouldn't have to download them, you need git-lfs installed.
Click to expand...
Click to collapse
Ah, I see. Will it work with them just downloaded, or else how should I fix this?

rasputin_g said:
Ah, I see. Will it work with them just downloaded, or else how should I fix this?
Click to expand...
Click to collapse
It will work that way, but the following should get you in sync:
git add -A && git reset origin/master && git pull && git-lfs pull

SkewedZeppelin said:
It will work that way, but the following should get you in sync:
git add -A && git reset origin/master && git pull && git-lfs pull
Click to expand...
Click to collapse
Thanks. Even when I run that, it seems to work but at the end says git-lfs is not installed (it is). I'm building on up-to-date Arch Linux.

I was building for like 17 hours when the build suddenly failed with the error FAILED: ninja: '/home/build/DivestOS/Signing_Keys/4096pro/dumpling/releasekey.x509.pem', needed by 'out/target/product/dumpling/obj/ETC/otacerts.recovery_intermediates/otacerts.zip', missing and no known rule to make it. I assume this is because there was this error when I ran Generate_Signing_Keys.sh: Scripts/Generate_Signing_Keys.sh: line 45: /home/build/DivestOS/Build/LineageOS-18.1//out/host/linux-x86/bin/generate_verity_key: No such file or directory
What could be causing this?

rasputin_g said:
I was building for like 17 hours when the build suddenly failed with the error FAILED: ninja: '/home/build/DivestOS/Signing_Keys/4096pro/dumpling/releasekey.x509.pem', needed by 'out/target/product/dumpling/obj/ETC/otacerts.recovery_intermediates/otacerts.zip', missing and no known rule to make it. I assume this is because there was this error when I ran Generate_Signing_Keys.sh: Scripts/Generate_Signing_Keys.sh: line 45: /home/build/DivestOS/Build/LineageOS-18.1//out/host/linux-x86/bin/generate_verity_key: No such file or directory
What could be causing this?
Click to expand...
Click to collapse
You need to run the two commands on https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Generate_Signing_Keys.sh#L22
And mkdir that folder if it doesn't exist beforehand.

SkewedZeppelin said:
You need to run the two commands on https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Generate_Signing_Keys.sh#L22
And mkdir that folder if it doesn't exist beforehand.
Click to expand...
Click to collapse
I no longer have that error, but now I have this one:
FAILED: out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk
/bin/bash -c "(rm -f out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk ) && (cp \"vendor/fdroid_prebuilt/packages/FairEmail.apk\" \"out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk\" ) && (if (zipinfo out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk 'lib/*.so' 2>/dev/null | grep -v ' stor ' >/dev/null) ; then out/soong/host/linux-x86/bin/zip2zip -i out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk -o out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.tmp -0 'lib/**/*.so' && mv -f out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.tmp out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk ; fi ) && (if ! out/soong/host/linux-x86/bin/zipalign -c -p 4 out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk >/dev/null ; then mv out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.unaligned; out/soong/host/linux-x86/bin/zipalign -f -p 4 out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.unaligned out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.aligned; mv out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.aligned out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk; fi )"
Unable to open 'out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk' for verification
Unable to open 'out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.unaligned' as zip archive
mv: bad 'out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.aligned': No such file or directory
06:51:24 ninja failed with: exit status 1
#### failed to build some targets (10:13:27 (hh:mm:ss)) ####

rasputin_g said:
I no longer have that error, but now I have this one:
mv: bad 'out/target/product/dumpling/obj/APPS/FairEmail_intermediates/package.apk.aligned': No such file or directory
06:51:24 ninja failed with: exit status 1
#### failed to build some targets (10:13:27 (hh:mm:ss)) ####
Click to expand...
Click to collapse
Late response, that kind of looks like you maybe ran out of space? btrfs with compress=zstd:1 will help if it is the case.

[X00TD][ROM] PixelPlusUI 4.1 [Android 12][AOSP][OFFICIAL][16/01/2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."
PixelPlusUI is another aftermarket AOSP ROM Minimal UI & close to Stock Android ROM. What differentiates us from the rest, you ask? LET'S FIND OUT. It has additional localized and personalized functionality while preserving the stock Android look by adhering to Material Design guidelines. Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience using PixelPlusUI will be butter smooth with added convenience and features. The main aim of this form is to give the user a better experience without compromising the quality of the Android experience so that no one struggles with any kind of difficulties while using their device. PixelPlusUI brings a better UI/UX to Android with a seamless experience coupled with customizations and user security. In short, it's perfectly balanced between Great Performance, Security, Stability, Minimal UI & Awesome features including pixel goodies But this doesn't mean we aim to provide all the customization available on the planet. So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy PixelPlusUI on your respective devices!
- Kostya Maslennikov - Founder & lead Developer
- Saurav - Co-Founder & Co-lead
- Abhishek - Support Team
- And Also Our Hardworking Maintainers
Tap Here For Screenshots
NOTE: As its initial A12 source and we will keep updating source with time, so its hard to keep threads updated everytime everywhere so kindly visit our website or telegram group for latest changes and screenshots.
Tap Here For CHANGELOG
Code:
- Pure Pixel Goodies
- 3 finger Screenshot
- Monet Theme
- Themed Icons
- Double tap to sleep on statusbar
- Double tap to sleep on lockscreen
- Powermenu: advanced reboot toggle - android 12
- Add button to AppErrorDialog to upload crash information to katbin
- SystemUI: Add dual-tone light and dark themes for QS
- Unlimited Upload in Google Photos
- Most of the a12 Stuff
- Allow user to add/remove QS with one click
- Add option to scramble pin layout when unlocking
- Add switch for linked ring and media notification volumes
- Enabled charging ripple effect
- Add hotspot setting to allow VPN upstreams
- Optional haptic feedback on back gesture
- add option to enable AOD on charging only
- Add pocket lock mode
- Gestures: Add option to cycle through ringer modes
- Forward Port Volume Long Press Skip Tracks
- Forward port lockscreen quick unlock
- Forward port cm security settings
- Add option to scramble pin layout when unlocking
- Option to mute media with gesture
- SystemUI: Introduce DataSwitchTile
- Bluetooth battery level when available
- More Features & Changes Coming SOON
--------- SourceForge ! ---------
Note: You can check our Website for more details, guides , changelog etc related to build !
-- DEVICE UPDATE TELEGRAM CHANNEL --
-- SUPPORT/DISCUSSION TELEGRAM GROUP --
-- Visit our OFFICIAL Website --
-- DEVICE SUPPORT GROUP --
-- OUR OFFICIAL TWITTER HANDLE --
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH :
- Download the latest build
- Reboot to recovery.
- Take a backup.
- Flash the latest build
- Flash Fcrypt [If you want to decrypt else u can skip]
- Reboot
DIRTY FLASH :
- Download the latest build
- Reboot to recovery
- Flash the latest build
- Wipe Cache
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work?
Nothing yet
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Proton-AOSP
- AOSPA
- Others, I forgot to mention
PixelPlusUI XDA Templates credit goes to
- GOUSAL TONI
- Android OS version: 12.0
- Security patch: January 2022
- Build author/Device Maintainer : Harshhaa Reddy Pamarthi
- DEVICE: Asus Zenfone Max Pro M1
- DEVICE CODENAME: X00TD
Sources and Documentation
- ROM Source Code
- Kernel Source
- OFFICIAL DEVICES
---------- DONATION LINKS ----------
As you know build is free but building ROM needs a server. And Maintaining source and device stuff needs a server and it's pretty expensive for a student. It will be really helpful and appreciated if you donate or contribute to us. Also if you have any queries related to donation you can freely message -> Saurav (Co-Founder & Co-lead Dev)
PAYTM UPI ID : [email protected]
GPAY UPI ID: [email protected]
PAYPAL: https://www.paypal.me/uglykid24

It's the same link like for 4.0 version. It's not updated?

Glitch in the Matrix oh doctor fate

great job. downloading now. thank you.

Still no updated download link?

found the download link: https://download.ppui.site/eleven/X00TD/PixelPlusUI_4.1_X00TD-12.0-20220116-0531-OFFICIAL.zip
If someone can download load it, please mirror to gdrive or anything easier and faster to download

Installed, but no extra's and system update options on setting,
Please help

I am getting the below error. How to fix it? Please help..
Updater process ended with signal: 4
Error installing zip file '/sdcard/PixelPlusUI.....'
I tried editing the updater script. Removed first 12 lines and tried. Still same error.
Please help.
Removed these lines. But, no use
assert(getprop("ro.product.device") == "RMX2001" || getprop("ro.build.product") == "RMX2001" ||
getprop("ro.product.device") == "RMX2151" || getprop("ro.build.product") == "RMX2151" ||
getprop("ro.product.device") == "RMX2001L1" || getprop("ro.build.product") == "RMX2001L1" ||
getprop("ro.product.device") == "RMX2003L1" || getprop("ro.build.product") == "RMX2003L1" ||
getprop("ro.product.device") == "RMX2005L1" || getprop("ro.build.product") == "RMX2005L1" ||
getprop("ro.product.device") == "RMX2002L1" || getprop("ro.build.product") == "RMX2002L1" ||
getprop("ro.product.device") == "RMX2151L1" || getprop("ro.build.product") == "RMX2151L1" ||
getprop("ro.product.device") == "RMX2153L1" || getprop("ro.build.product") == "RMX2153L1" ||
getprop("ro.product.device") == "RMX2155L1" || getprop("ro.build.product") == "RMX2155L1" ||
getprop("ro.product.device") == "RMX2156L1" || getprop("ro.build.product") == "RMX2156L1" ||
getprop("ro.product.device") == "RMX2161L1" || getprop("ro.build.product") == "RMX2161L1" ||
getprop("ro.product.device") == "RMX2163L1" || getprop("ro.build.product") == "RMX2163L1" || abort("E3004: This package is for device: RMX2001,RMX2151,RMX2001L1,RMX2003L1,RMX2005L1,RMX2002L1,RMX2151L1,RMX2153L1,RMX2155L1,RMX2156L1,RMX2161L1,RMX2163L1; this device is " + getprop("ro.product.device") + ".");

Kish4nn said:
I am getting the below error. How to fix it? Please help..
Updater process ended with signal: 4
Error installing zip file '/sdcard/PixelPlusUI.....'
I tried editing the updater script. Removed first 12 lines and tried. Still same error.
Please help.
Removed these lines. But, no use
assert(getprop("ro.product.device") == "RMX2001" || getprop("ro.build.product") == "RMX2001" ||
getprop("ro.product.device") == "RMX2151" || getprop("ro.build.product") == "RMX2151" ||
getprop("ro.product.device") == "RMX2001L1" || getprop("ro.build.product") == "RMX2001L1" ||
getprop("ro.product.device") == "RMX2003L1" || getprop("ro.build.product") == "RMX2003L1" ||
getprop("ro.product.device") == "RMX2005L1" || getprop("ro.build.product") == "RMX2005L1" ||
getprop("ro.product.device") == "RMX2002L1" || getprop("ro.build.product") == "RMX2002L1" ||
getprop("ro.product.device") == "RMX2151L1" || getprop("ro.build.product") == "RMX2151L1" ||
getprop("ro.product.device") == "RMX2153L1" || getprop("ro.build.product") == "RMX2153L1" ||
getprop("ro.product.device") == "RMX2155L1" || getprop("ro.build.product") == "RMX2155L1" ||
getprop("ro.product.device") == "RMX2156L1" || getprop("ro.build.product") == "RMX2156L1" ||
getprop("ro.product.device") == "RMX2161L1" || getprop("ro.build.product") == "RMX2161L1" ||
getprop("ro.product.device") == "RMX2163L1" || getprop("ro.build.product") == "RMX2163L1" || abort("E3004: This package is for device: RMX2001,RMX2151,RMX2001L1,RMX2003L1,RMX2005L1,RMX2002L1,RMX2151L1,RMX2153L1,RMX2155L1,RMX2156L1,RMX2161L1,RMX2163L1; this device is " + getprop("ro.product.device") + ".");
View attachment 5517165
Click to expand...
Click to collapse
The Rom you installed is for realme 6 device, not from X00TD device,

mdhuma said:
The Rom you installed is for realme 6 device, not from X00TD device,
Click to expand...
Click to collapse
Did not check the file name correctly when downloading. My bad..

Kish4nn said:
Did not check the file name correctly when downloading. My bad..
Click to expand...
Click to collapse
.. Please post about ROM, for me it's like original ROM, too good and stable, banking apps working smooth,
Only thing irritating status bar icons, no update option in system settings.

hey I'm loving the room so far very responsive! the only thing is that some bank apps i use don't even open... saying that the device isn't supported, etc. and i am not having unlimited upload on Google photos ( and yes even going in the settings it doesn't show it)

How to get rid from this?

Develop Bugs

welcome