yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
You didn't do anything wrong.

It will only work with touch on one slot, the one you didn't flash twrp.img to, so use that one. In your case, that would be slot A. Slot B still has the "temporary" twrp.img boot image on it, so it won't boot to Android and touch won't work in TWRP.

Also, no need to use mouse if you followed my instructions on page 9.

And yes, there is a bug that shifts it left. It will be fixed.

---------- Post added at 20:48 ---------- Previous post was at 20:46 ----------

Every time you flash or update your boot image (kernel) on your active slot, you will need to reinstall the TWRP installer zip from your inactive slot.

---------- Post added at 20:50 ---------- Previous post was at 20:48 ----------

You need to flash the stock boot image first. Then follow the instructions (including my modified ones on page 9) to install TWRP. Then lastly, you install Magisk.

Every time the boot image (kernel) is updated, you need to repeat all that.

The TWRP installer zip installs TWRP into your boot image. So if you flash the stock boot image over it, you are erasing TWRP. Magisk is also installed into your boot image. But TWRP must be installed before Magisk or the phone will continuously boot into TWRP.

So basically the only thing you messed up was flashing the stock boot image again after installing TWRP and before installing Magisk. Once you first flash the stock boot image to your active slot, then use my instructions on page 9 for installing TWRP, then simply install the magisk.zip from TWRP.

---------- Post added at 21:10 ---------- Previous post was at 20:50 ----------

Absolutely no need for that, taking the short way out, using someone else's generated boot image, and not actually learning what the install process is.

My instructions on page 9 will work for any past, present, or future firmware/ROM so best just to do it yourself once and learn. It's literally 2 adb commands in addition to the regular TWRP install instructions. That way if a newer version of the "temp" TWRP.img is released that fixes touch on the September update, but in October or November or a year from now, touch stops working on the "temporary" TWRP.img, someone will still be able to use those adb commands to use the TWRP installer zip and install TWRP (with working touch).

Just to be clear, the TWRP installer zip is compatible with any boot image (kernel), past, present, or future (very similar to the magisk.zip). The only trick is installing it if touch doesn't work in the "temporary" TWRP.img which was made from one specific boot image and the touch on it isn't guaranteed to work on other boot images. That's where my instructions on page 9 (which boils down to 2 additional adb commands) come in.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
What's wrong with that? It's nice when there are several solutions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Just saying it's not good to depend on others, and that solution isn't guaranteed to be available every month.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Osmatic:
Thanks for explanation, mate.

Yeah, current state is exactly as in your words - works good with slot A, but no touch + no OS boot on slot B.

Is there any way to make it fully functional on both slots + dual OS boot? I wanted to play with custom kernel at the second slot while keeping first untouched...:crying:
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Here are just some notes I have written down regarding TWRP and how to install ROMs alongside and whatnot. Hope this helps, and please correct me if I have anything wrong.

Useful Fastboot / ADB Commands:

• fastboot getvar current-slot

• fastboot set_active other

• adb shell getprop ro.boot.slot_suffix

• adb push rom.zip /sdcard/rom.zip

Flashing a boot.img:

Kernel -> TWRP Installer -> Magisk, in that order.

Flashing a ROM:

ROM -> TWRP Installer -> Boot ROM -> Recovery -> Magisk, in this order -- or, before Magisk, flash an alternative Kernel, then patch, finally Magisk.

Stock and basic shiz:

On stock, and some ROM installs (after booting it first.), find current slot, then flash TWRP to opposite slot. Once TWRP boots, select the Reboot option and select original current slot. Now you can flash your TWRP Installer zip, followed by Magisk.

Magisk of course is completely optional.
[Essential Phone ROMs, Kernels, Recoveries, & Other] envizion58:
does twrp persist between rom updates now or do i need to redo the twrp installation after each rom update?
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
While updating follow below

Boot TWRP

Flash ROM Zip

Flash TWRP Retain zip

Flash Magisk if you need root.

You have to flash TWRP retaining zip everytime you flash a kernel or ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] envizion58:
by twrp retain zip, do you mean the installer zip? i only see twrp image and installer zip on the download page.
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
Yup. Installer zip.

You got to flash every time you flash ROM or boot/ kernel image.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Use TWRP to backup the boot image on the slot with TWRP working and the system booting (slot A in your case), click restart in TWRP (don't actually restart) and click the button at the bottom to switch to the other slot (slot B in your case), then restore the backup of the boot image using TWRP.

However, I highly recommend not doing this. This isn't the purpose of having 2 slots and not what they are intended for. The two slots are NOT for dual booting 2 ROMs because they share the same copy of /data (you could do it with 2 different kernels with the same ROM on both slots but still not recommended). If you try it with 2 different ROMs, you're going to corrupt /data and get nothing but a million force closes. Much better to backup the boot image (kernel) on slot A, install your custom kernel and TWRP to slot A, make a backup of it, and you can easily switch back and forth between kernels by restoring the backups while remaining on slot A the entire time.

If you are going to do this, make sure you have flashed the entire fastboot package from Essential's website on both slots. TWRP only backs up boot, data (without /sdcard), system, and vendor. It can't back up the dozen or so other firmware partitions that are included in the fastboot package download which are required to make the system work properly. And there are separate copies (and most likely different versions) of these firmware elements on each slot unless every month you flash the fastboot package download to both slots.

---------- Post added at 16:35 ---------- Previous post was at 16:22 ----------

Good list, but one update:

Depending on the version of adb/fastboot installed on your PC, some commands will not work. The one that has never worked for me is

fastboot set_active other

So instead, after you find your current slot, switch to the other slot using:

fastboot set_active _a

OR

fastboot set_active _b

Also, you don't have to select your active slot before installing the TWRP installer zip. It installs to both slots automatically. Safer to install it while on your inactive slot, reboot to bootloader, then change to your active slot, boot into TWRP which is now installed, and install Magisk.

---------- Post added at 16:42 ---------- Previous post was at 16:35 ----------

You forgot one step. If installing a completely fresh ROM (meaning you wiped data first), you need to boot into the ROM at least once before flashing Magisk.

And these instructions are only valid if TWRP has already been installed using the installer zip first.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Wow, this thread finally cooled down. Guess it won't heat up again until October comes out (use my instructions on page 9, just substitute the word October for September, and I highly recommend updating using the OTA download package, not the fastboot one) or until [MENTION=912474]Dees_Troy[/MENTION] releases the update he is working on on GitHub. Thanks again Dees for all the hard work and for making all these questions I've been answering possible ?. Small price to pay for an official TWRP version with the TWRP installer zip and working decryption for our Mata phone!
[Essential Phone ROMs, Kernels, Recoveries, & Other] SpectraFun:
Hi

I am on a fresh new PH1 with lastet PIE Update and dont have root or twrp. I have download your twrp. Whene i boot in this twrp, touch will work? And after first boot in twrp i can flash normal twrp from twrp site or need other twrp zip for september update?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Ok, so with a/b partition structure, recovery is in boot.img, FYI just make sure your on September update prior to flashing this.

His patched boot has magisk and twrp preinstalled, just flash it and go. No need for another twrp install on top.

1 stop shopping here
[Essential Phone ROMs, Kernels, Recoveries, & Other] SpectraFun:
Ok only flash this one file in fastboot and i can reboot to twrp every time without flashing twrp zip and i dont need magisk too?
[Essential Phone ROMs, Kernels, Recoveries, & Other] SpectraFun:
Working fine now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Hi [MENTION=912474]Dees_Troy[/MENTION], thanks for a finally working TWRP for our device, can I ask you to update it? We have a slight issue that we can't use TWRP on stock ROM due to firmware mismatch, however I found a way to fix it, here are commits that you will need to pick for kernel, it should work in both ROMs after that.

First one, second and third.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LoveScarGuitar:
I was able to use twrp on stock rom no problem. The only issue seems to be the touch being not too accurate, which the dev stated he has been working on.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
I could get touch to work on latest releases when flashed into /boot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
True, but if you flash the install zip (sideloaded in twrp) you will get touch once you back out or recovery and switch back to your active slot and boot back into twrp. Bit of a pain sure but it works. If you commits fix that procedure than I am sure DessTroy will have a look if he hasn't already.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
The only reason it doesn't work on the inactive slot is because you flashed TWRP.img to it first. And twrp.img is based on the August kernel. He already has a commit that fixes that (and many more including the screen offset) in his GitHub repo that he is testing.

And even once TWRP.img is updated with the September kernel so touch works on it (those 3 commits have absolutely nothing to do with fixing it), he's not going to rebuild it every month when a new kernel comes out (that's the entire point of the TWRP installer zip -- it works on any version kernel). So you would still need to use the install instructions you posted or you'd have an outdated kernel on your inactive slot if you plan on booting from it.

And just btw, the process you described doesn't take more than 45 seconds.

---------- Post added at 05:37 ---------- Previous post was at 05:27 ----------

Those 3 commits (which don't even work yet if you bothered to read their descriptions) have absolutely nothing to do with getting touch working on the "temporary" TWRP.img. The reason touch doesn't work on it is because it was built from the August kernel. And in September, Essential modified the hyp and rpm partitions. Once he rebuilds twrp.img from the September kernel (which is already on his Github along with many other fixes), touch will work on TWRP.img. Until then, just adb sideload the TWRP installer zip as I explained in post #86.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Oh well, at least I tried to get such basic thing as TWRP to work reliably in both ROMs. Glad I'm getting rid of this piece of junk soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Yeah, you tried so hard...and provided 3 commits (which if you read them say they don't even work yet) that have nothing to do with the situation. Maybe next time actually try reading the thread?

If you want it to work on both slots, take a TWRP backup of the boot image on your active slot and restore it to the inactive slot you want it on.

And I'm sorry to tell you, but every A/B device (meaning every device that launched with Oreo or newer), has the exact same steps for installing TWRP. So get your ungrateful and ignorant self out of this thread and the Essential forums.

Oh and lastly, the A/B slots are NOT meant for dual booting ROMs. Have fun corrupting /data each time you attempt to boot from each ROM at least once. Guess you'll blame Essential for that too.

You really need to study up on how the A/B slots work and what they are meant to be used for. Having 2 slots does NOT equal having MultiROM (which kept a separate /data partition for each ROM). The A/B slots are meant only for ROM updates. Therefore they share a common /data partition. It would like installing a new ROM without wiping /data.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
These are my commits, I am YaroST12 on GitHub) I know they work (now), even though one of them is marked as WIP/non-working,

what I propose is to check what ROM is installed before installing TWRP and then somehow patch cmdline accordingly, those patches provide way to make touchscreen work on old and new firmware. So it shouldn't be that hard to do, however I never actually worked on TWRP-s and thus don't really know if that's possible.

This has literally nothing to do with A/B or anything.

You are a bit out of touch with reality, I never said anything about multirom or having stock and custom installed at the same time, all I want is to have 1 installer and .img that will work with both FW versions. only thing I blame Essential for is putting a touchscreen that is meant for kids' toys into a 700$ phone (on release). I hopt [MENTION=912474]Dees_Troy[/MENTION] figures it out with or without my help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] KuranKaname:
Just as a thought, I'd rather not have that. Custom roms can be compiled as user and I'm going to do that soon. Rather make 2 builds or keep it working on custom roms as we need it more
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Build prop check can be used, it's fine. Patching cmdline is easy enough too, then just change code a little bit and YOLO.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
You still don't seem to grasp a very simple concept. The ONLY reason the touchscreen does not work in Twrp.img on September (and newer releases, not that there are any yet) is because Essential updated the hyp and rpm firmware partitions for the first time ever in the September release. Therefore, an updated kernel is needed. If you have the September update installed,and install the August kernel, your touchscreen won't work in Android.

So to get touch to work on the "temporary" TWRP.img, it simply needs to be built from the September kernel. DT built it from the August kernel. This has been discussed at great length and detail in this thread.

And again, if you look at Dees' Essential TWRP GitHub, you'll see he made a gigantic commit on September 14th I believe that updated TWRP.img to the September kernel (to fix touch), made some changes to try to get the screen aligned correctly, and literally dozens of other things. This just came out for the first time on September 10th I believe. And it works perfectly and the touchscreen works fine if you install the TWRP installer zip from TWRP.img using the adb sideload commands. So why don't you give me a break, and more importantly, give Dees a break?! He's been doing this a very long time and doesn't need "help" from someone who doesn't even comprehend the issue.

Edit; And very lastly, the TWRP installer zip works on all kernels, firmwares, ROMs, etc, past, present, and future (with the touch screen working). The only "trick" is installing it using the adb sideload commands while booted into the TWRP.img where touch may not work.

And the MultiROM and A/B comments were directed at the person I quoted, not you. If I quoted you by mistake, I'm sorry.

MOD EDIT
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Watch your language, smart boy.

Commits I sent make it work on both, old and new firmware.

From us 3 you have the least idea what's going on and how to fix it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
I've been helping people in this thread since day one. You appeared yesterday with an attitude, acted like you had the magic fix for all the problems in the universe, and called the Essential a piece of crap that you were getting rid of.

So why are you still here?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
I mean, I have it, but it can't be used as is in TWRP. My kernel works in AICP and stock September release, so with old and new firmware. All with one kernel image :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Here, had to improvise a little bit with stock in order to show full kernel version.
[Essential Phone ROMs, Kernels, Recoveries, & Other] starcms:
Considering the hyp and rpm partitions have only been updated once in a year (and Pie had nothing to do with it), within a couple weeks, all custom ROMs such as AICP will be updated to work with the new versions of hyp and rpm.

But if you are in such a rush, and don't appreciate what [MENTION=912474]Dees_Troy[/MENTION] is doing for us, why don't you just take your giant brain and build your own version of the "temporary" TWRP.img that works on both? It's all open source on GitHub so why not stop being an ungrateful and whiny know-it-all and just fix, build, and distribute it yourself?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
But they are not updated yet. See this one commit? https://github.com/YaroST12/MATA_Kernel/commit/7422088e53e13c8c2dea747de87fead4c70ad4bb, it breaks touchscreen on AICP because it's not updated yet, however, stock has it and requires it for touchscreen to work. Check Kuran's kernel repo, he doesn't have it applied yet.
[Android Head-Units] satcluj:
hello there ,

i have this unit

View attachment 4593128

Rezolution HD 1024X600

Procesor Intel Atom X3 Quad-Core 1,2 Ghz x 4 Core

Procesor Grafic Mali - 450MP4

DDR III 2GB - Samsung

Memory internal 16GB - Toshiba, Japan EMMC5.0

i updated to joying software now it says wrong mcu file , no sound no usb no no thing .

all i got before updating was .

View attachment 4593124

View attachment 4593127

i can't reset the unit. tried RST+ power , no recovery menu , just logo and the boot to bad update.

only saved two files mcuallupdate.bin and txt size about 12 mb .

can someone please help me recover my android?
[Samsung Galaxy S9+ Questions & Answers] HeatOfLisboa67:
Paid £769 for this really enjoying it so far can it be rooted? G965FXXU2BRGA
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rama982:
GENOM KERNEL REWORKS

/*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*
*/

Support for MIUI OREO rom

Works in both AOSP/LineageOS(Oreo & Pie) treble based ROMs

Always up-to-date with

Linux Upstream | Latest CAF Tag | Latest Prima Tag
​

Features:

Pie CAF & Prima Tag : LA.UM.7.6.r1-3900-89xx.0 (kernel.lnx.3.18.r34-rel & wlan-driver.lnx.1.0.r30-rel)

Oreo CAF & Prima Tag : LA.UM.6.6.r1-10500-89xx.0 (kernel.lnx.3.18.r33-rel & wlan-driver.lnx.1.0.r23-rel)

Linux Upstream 3.18.131

KCAL color control

EAS Governor : Schedutil, Electroutil, Darkutil, Pwrutilx (MIUI Only)

Sound control

Vibration intensity control

exFAT Support

Boeffla wakelocker

Wireguard VPN Support

TCP congestion algorithm : cubic, reno, westwood

CPU Hotplug

Download :

Github Release

Installations :

Backup boot.img if you want to go back

Backup /system/lib/modules folder for MIUI

Flash Zip file with any twrp recovery

reboot and forget

Enjoy :)

TELEGRAM NIGHTLY BUILD :

Genom Kernel CI

XDA:DevDB Information

Genom Kernel for vince, Kernel for the Xiaomi Redmi Note 5 / 5 Plus

Contributors

rama982, mdeejay, blacksuan19, raphielscape, LuizPauloDamaceno

Source Code: [url]https://github.com/GenomProject-redmi5plus/android_kernel_xiaomi_vince-caf[/URL]

Kernel Special Features:

Version Information

Status: Stable

Stable Release Date: 2018-11-11

Created 2018-09-10

Last Updated 2019-01-05
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rama982:
Reworked thing, so not much features on it yet. And only MIUI for now

All changelog from before reworks is deleted.

Changelogs -:

MIUI / 2019-01-05

» kernel & wlan: Merge CAF tag 'LA.UM.6.6.r1-10500-89xx.0'

» Changed dts to decompiled dtb from latest miui 9.1.1 china beta

AOSP, MIUI / 2018-12-22

» Release AOSP kernel too

» New base from leaked oreo kernel source

» Merged linux 3.18.131

» Merged google aosp branch (Only AOSP kernel)

» Revert OC on MIUI kernel

MIUI / 2018-11-13

» Fully reworking dts changes for vince

» Re-adding Novatek ts(panel still broke) and Ebbg ts synaptics on dtsi

» Re-adding Fingerprint Boost

» Re-adding AutoSMP Hotplug + MSM Hotplug

» Re-adding Wireguard

MIUI / 2018-11-11

» Reworked and rebased to latest CAF tag LA.UM.6.6.r1-10100-89xx.0 for oreo

» Merged latest kernel stable 3.18.125

» No more bootloop / kernel panic issue :)
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] laststandrighthere:
Nice, have been waiting for this xd
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Mordar:
Does This means we will start seeing Pie ROMS :D?
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rama982:
Well, some dev saying pie rom for vince will booting in one week.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] honezty:
Ah so you're the one that ported AOSP-Pie to vince,kudos to you for doing that.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] ibbi.ir7:
[MENTION=8484128]rama982[/MENTION] your rom Mcaosp PIE is damn great with all extra features looking forward for official release on xda, will try this kernel :svetius:
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] ekowanz:
yes your port of mcaosp pie with this kernel already makes me so happy this month. Stable kernel you hav here..
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] AndroBuddy007:
Ugh... Sorry to disturb, which mcaosp ROM are you guys talking about? Searched xda but no clue.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] ibbi.ir7:
Its not available on xda by the way links are below

Mc-Aosp Pie build 2018.09.04 vince update

~Ported by [MENTION=8484128]rama982[/MENTION]

Changelog from 2019.08.29 build:

- Update builtin kernel to Genom Pie 2018.09.09

ROM

(Translated from russian with google)

-Number of switches in the shutter

-Ability to hide the navigation bar

-Added the ability to edit buttons

-Tiles of the screenshot (by area) and hide the navigation bar

-Expanding ring volume

-Ability to remove a warning at the bottom of the Quick Settings toolbar

-Ability to change the grid of the quick settings panel

- Weather on the lock screen

- Some changes that not included on changelogs

ATTENTION

- VOLTE still not fix

ROM: http://bit.ly/mcaosp-vince-port-20180904

PATCH: http://bit.ly/patch-v2-uni (must install)

GAPPS: https://opengapps.org/

MAGISK: http://bit.ly/magisk-pie
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] AndroBuddy007:
Thanks for informing!

Shall I forward this message to others, make it available for users on xda or do I keep it as it is?
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Rayquaza:
Deleted~