yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 4C] cobraplayer:
There is no need to have flashable zip. You can flash the recovery img through flashify app. Alternatively, if you already have an older twrp, use 'install image' feature to flash this one.
[Xiaomi Mi 4C] ketut.kumajaya:
I don't have a USB C converter to check it.
[Xiaomi Mi 4C] ketut.kumajaya:
Single recovery for both libra and aqua + working double tap to wake feature ready to download. If SD card support not working on aqua, please help me to debug it. In recovery "cat /proc/partitions" command output will be helpful.

EDIT: In TWRP double tap to wake patch: https://github.com/kumajaya/android...mmit/283ed9eded008a6f7e62c2ca53934754ae7f10ce
[Xiaomi Mi 4C] BlackXhorneT:
Awesome work yet again my friend :). DT2W working flawlessly which is really nice!

SD card is still a no as yet. I'll get you the log output tomorrow to see if we can get any headway on it.

Loving the unified rom/recovery system. Really clever and cool.

Big thumbs up!
[Xiaomi Mi 4C] KopiJahe:
DT2W is working on aqua, no sdcard. Here's the output from "cat /proc/partitions":

major minor #blocks name

179 0 61071360 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 8 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 128 mmcblk0p15
179 16 128 mmcblk0p16
179 17 1 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 1 mmcblk0p20
179 21 96 mmcblk0p21
179 22 512 mmcblk0p22
179 23 1 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1024 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 21636 mmcblk0p27
179 28 1536 mmcblk0p28
179 29 1536 mmcblk0p29
179 30 1 mmcblk0p30
179 31 29695 mmcblk0p31
259 0 32768 mmcblk0p32
259 1 1536 mmcblk0p33
259 2 31232 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 131072 mmcblk0p36
259 5 65536 mmcblk0p37
259 6 65536 mmcblk0p38
259 7 32768 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 1966080 mmcblk0p41
259 10 393216 mmcblk0p42
259 11 327680 mmcblk0p43
259 12 57860079 mmcblk0p44
179 32 4096 mmcblk0rpmb

Also, just in case you need the recovery.log.
[Xiaomi Mi 4C] ketut.kumajaya:
Strange, no mmcblk1 there. Please give me a complete dmesg output using "dmesg > /sdcard/dmesg.txt" command immediately after boot completed. Please check your own dmesg output, don't give me a garbage output.
[Xiaomi Mi 4C] KopiJahe:
Here is dmesg right after booting into TWRP. I'm sorry but I'm not quite sure yet if this "garbage-free" dmesg.
[Xiaomi Mi 4C] ketut.kumajaya:
Strange, mmc1 partition not get exposed in recovery. Please take a dmesg in normal boot. A complete dmesg + one with more specific output using "dmesg | grep mmc1 > /sdcard/dmesg_mmc1.txt". Remember, immediately after a boot completed.
[Xiaomi Mi 4C] KopiJahe:
Yeah, I did a manual search, this lines didn't appears in the TWRP's log:

[ 8.478508] mmc1: slot status change detected (0 -> 1), GPIO_ACTIVE_HIGH
[ 8.593841] mmc1: new ultra high speed SDR50 SDXC card at address 0001
[ 8.594804] mmcblk1: mmc1:0001 ASTC 59.5 GiB
[ 8.596791] mmcblk1: p1

I attached both logs you asked. I captured this on the latest cm13 build, if that matters.
[Xiaomi Mi 4C] ketut.kumajaya:
Now I remember, 4s uses SIM 2 slot as MMC slot. We must check it and trigger MMC insert on recovery boot but how?
[Xiaomi Mi 4C] KopiJahe:
Maybe this? here's a snippet. CMIIW.

&sdhc_2 {
vdd-supply = <&pm8994_l21>;
qcom,vdd-voltage-level = <2950000 2950000>;
qcom,vdd-current-level = <200 800000>;

vdd-io-supply = <&pm8994_l13>;
qcom,vdd-io-voltage-level = <1800000 2950000>;
qcom,vdd-io-current-level = <200 22000>;

#address-cells = <0>;
interrupt-parent = <&sdhc_2>;
interrupts = <0 1 2>;
#interrupt-cells = <1>;
interrupt-map-mask = <0xffffffff>;
interrupt-map = <0 &intc 0 125 0
1 &intc 0 221 0
2 &pm8994_gpios 8 0x3>;
interrupt-names = "hc_irq", "pwr_irq", "status_irq";
cd-gpios = <&pm8994_gpios 8 0x0>;

pinctrl-names = "active", "sleep";
pinctrl-0 = <&sdc2_clk_on &sdc2_cmd_on &sdc2_data_on>;
pinctrl-1 = <&sdc2_clk_off &sdc2_cmd_off &sdc2_data_off>;

qcom,clk-rates = <400000 20000000 25000000 50000000 100000000 200000000>;
qcom,bus-speed-mode = "SDR12", "SDR25", "SDR50", "DDR50", "SDR104";
status = "ok";
};
[Xiaomi Mi 4C] ketut.kumajaya:
Please give me "cat /sys/kernel/debug/gpio" output from recovery and normal boot.
[Xiaomi Mi 4C] ketut.kumajaya:
Ah, debugfs not mounted in recovery. Mount it first using "mount -t debugfs none /sys/kernel/debug" command.
[Xiaomi Mi 4C] KopiJahe:
looks like gpio 872, in android it's read as hi, but in twrp it is on lo

GPIOs 543-574, platform/qcom,smp2pgpio-ssr-smp2p-1-out.16, master-kernel:

GPIOs 575-606, platform/qcom,smp2pgpio-ssr-smp2p-1-in.15, slave-kernel:

GPIOs 607-638, platform/qcom,smp2pgpio-ssr-smp2p-2-out.14, master-kernel:

GPIOs 639-670, platform/qcom,smp2pgpio-ssr-smp2p-2-in.13, slave-kernel:

GPIOs 671-702, platform/qcom,smp2pgpio-smp2p-2-out.11, smp2p:

GPIOs 703-734, platform/qcom,smp2pgpio-smp2p-2-in.9, smp2p:

GPIOs 735-766, platform/qcom,smp2pgpio-smp2p-1-out.7, smp2p:

GPIOs 767-798, platform/qcom,smp2pgpio-smp2p-1-in.5, smp2p:

GPIOs 799-830, platform/qcom,smp2pgpio-smp2p-7-out.3, smp2p:

GPIOs 831-862, platform/qcom,smp2pgpio-smp2p-7-in.1, smp2p:

GPIOs 863-863, spmi/qpnp-pin-ffffffc0c4a4ec00, pmi8994-mpp:

GPIOs 864-864, spmi/qpnp-pin-ffffffc0c4a4e800, pmi8994-gpio:
gpio-864 (usb_otg_vreg ) out lo

GPIOs 865-866, spmi/qpnp-pin-ffffffc0c4a4ac00, pm8994-mpp:

GPIOs 867-877, spmi/qpnp-pin-ffffffc0c4a4a800, pm8994-gpio:
gpio-867 (tp1v8_vreg ) out hi
gpio-868 (volume_up ) in hi
[B][COLOR="Red"] gpio-872 (f98a4900.sdhci cd ) in lo[/COLOR][/B]
gpio-873 (bt_vreg ) out lo

GPIOs 878-1023, platform/fd510000.pinctrl, msm_tlmm_gpio:
gpio-887 (silabs_fm_int_n ) in lo
gpio-889 (silabs_fm_stat_n ) in lo
gpio-899 (vibrator_en ) in lo
gpio-912 (lid_back ) in hi
gpio-913 (perst-gpio ) out lo
gpio-915 (wake-gpio ) in hi
gpio-920 (st_hub_gpio_wakeup ) out lo
gpio-931 (wlan-bootstrap-gpio ) out hi
gpio-932 (wlan-bootstrap-gpio ) out hi
gpio-935 (vibrator_vreg ) out hi
gpio-938 (mxt_reset_gpio ) out hi
gpio-939 (mxt_irq_gpio ) in hi
gpio-940 (fm_rst_gpio_n ) in lo
gpio-952 (st_hub_gpio_reset ) out hi
gpio-973 (lid_front ) in hi
gpio-974 (tpwdn_vreg ) out hi
gpio-988 (ts_vreg ) out hi
gpio-990 (wlan-bootstrap-gpio ) out hi
gpio-991 (wlan-en-gpio ) out lo
gpio-993 (fpc,gpio_irq ) in hi
gpio-994 (fpc,gpio_rst ) in hi
[Xiaomi Mi 4C] ketut.kumajaya:
Now, please check SDHC2 power supply status in normal boot and recovery:

- "cat /sys/kernel/debug/regulator/pm8994_l13/enable"

- "cat /sys/kernel/debug/regulator/pm8994_l21/enable"
[Xiaomi Mi 4C] KopiJahe:
recovery:

~ # cat /sys/kernel/debug/regulator/pm8994_l13/enable
[B]0[/B]

~ # cat /sys/kernel/debug/regulator/pm8994_l21/enable
[B]0[/B]

android (sdcard):

shell@libra:/ $ cat /sys/kernel/debug/regulator/pm8994_l13/enable
[B]0[/B]

shell@libra:/ $ cat /sys/kernel/debug/regulator/pm8994_l21/enable
[B][COLOR="Red"]1[/COLOR][/B]

android (no sdcard):

shell@libra:/ $ cat /sys/kernel/debug/regulator/pm8994_l13/enable
[B]0[/B]

shell@libra:/ $ cat /sys/kernel/debug/regulator/pm8994_l21/enable
[B]0[/B]
[Xiaomi Mi 4C] ketut.kumajaya:
Now in recovery, how if you enable SDHC2 VDD power supply "echo 1 > /sys/kernel/debug/regulator/pm8994_l21/enable" and then check dmesg output "dmesg | grep mmc1".
[Xiaomi Mi 4C] KopiJahe:
"dmesg | grep mmc1" output:

<6>[ 3.309503] mmc1: no vqmmc regulator found
<6>[ 3.309526] mmc1: no vmmc regulator found
<6>[ 3.309807] mmc1: SDHCI controller on f98a4900.sdhci [f98a4900.sdhci] using 32-bit ADMA

If you need it, full dmesg attached below.
[Xiaomi Mi 4C] ketut.kumajaya:
D*mn, no progress! Please also enable pm8994_l13.
[Xiaomi Mi 4C] KopiJahe:
Still the same as above. Attached full dmesg below.

The full thing I did, right after booting TWRP

~ # mount -t debugfs none /sys/kernel/debug
~ # echo 1 > /sys/kernel/debug/regulator/pm8994_l21/enable
~ # echo 1 > /sys/kernel/debug/regulator/pm8994_l13/enable
~ # cat /sys/kernel/debug/regulator/pm8994_l13/enable
1
~ # cat /sys/kernel/debug/regulator/pm8994_l21/enable
1
~ # dmesg | grep mmc1
<6>[ 2.705553] mmc1: no vqmmc regulator found
<6>[ 2.705576] mmc1: no vmmc regulator found
<6>[ 2.705865] mmc1: SDHCI controller on f98a4900.sdhci [f98a4900.sdhci] using 32-bit ADMA
[Xiaomi Mi 4C] KopiJahe:
[MENTION=4021423]ketut.kumajaya[/MENTION]

So, I digged around, there's "consumers" file under each folder. Here's a comparison of what inside of them:

1. SDHC1 (lm8994_l20 & lm8994_s4)

~ # cat /sys/kernel/debug/regulator/pm8994_l20/enable
0
~ # cat /sys/kernel/debug/regulator/pm8994_l20/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
f9824900.sdhci-vdd	N	2950000	2950000	0
pm8994_l20	N	0	0	0

~ # [6ncat /sys/kernel/debug/regulator/pm8994_s4/enable
1
~ # [6ncat /sys/kernel/debug/regulator/pm8994_s4/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
5-0011-vdd	N	0	0	0
qcom,cnss.32-vdd-wlan-io	N	1800000	1800000	0
7-0060-prox-int	Y	0	0	0
[B][COLOR="Red"]f9824900.sdhci-vdd-io	Y	1800000	1800000	325000[/COLOR][/B]
pm8994_s4	N	0	0	0

2. SDHC2

~ # cat /sys/kernel/debug/regulator/pm8994_l21/enable
0
~ # cat /sys/kernel/debug/regulator/pm8994_l21/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
f98a4900.sdhci-vdd	N	2950000	2950000	0
pm8994_l21	N	0	0	0

~ # cat /sys/kernel/debug/regulator/pm8994_l13/enable
0
~ # cat /sys/kernel/debug/regulator/pm8994_l13/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
[B][COLOR="red"]f98a4900.sdhci-vdd-io	N	1800000	2950000	0[/COLOR][/B]
pm8994_l13	N	0	0	0

Let see what happen if I toggle the vdd-io for SDHC2:

~ # echo 1 > /sys/kernel/debug/regulator/pm8994_l13/enable
~ # cat /sys/kernel/debug/regulator/pm8994_l13/enable
1
~ # cat /sys/kernel/debug/regulator/pm8994_l13/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
[B][COLOR="red"]f98a4900.sdhci-vdd-io	N	1800000	2950000	0[/COLOR][/B]
pm8994_l13	Y	0	0	0

the vdd-io doesn't get ENabled, instead the pm8994_l13 got enabled, which isn't the case the lm8994_s4

For comparison, here it is under android:

shell@libra:/ $ cat /sys/kernel/debug/regulator/pm8994_l13/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
[B][COLOR="Red"]f98a4900.sdhci-vdd-io	Y	1800000	1800000	22000[/COLOR][/B]
pm8994_l13	N	0	0	0
[Xiaomi Mi 4C] ketut.kumajaya:
So, what trigger MMC insertion?

[ 8.887496] mmc1: slot status change detected (0 -> 1), GPIO_ACTIVE_HIGH
[ 9.008889] mmc1: new ultra high speed SDR50 SDXC card at address 0001
[ 9.009910] mmcblk1: mmc1:0001 ASTC 59.5 GiB
[ 9.013376] mmcblk1: p1

How if we set SDHC2 vdd-io to always on in recovery? https://github.com/kumajaya/android...boot/dts/qcom/libra/a10-msm8992-mtp.dtsi#L155
[Xiaomi Mi 4C] KopiJahe:
Yeah, let's try that. I'll try to download the sources tonight...
[Xiaomi Mi 4C] KopiJahe:
I don't know why I can't compile this, tried 2 different linux distro (bbqlinux and ubuntu 16.04), always getting this error:

/home/awaaas/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/awaaas/android/system/out/target/product/libra/obj/ETC/sepolicy_intermediates/policy.conf
device/xiaomi/libra/sepolicy/sysinit.te:3:ERROR 'unknown type sysinit' at token ';' on line 16462:
allow sysinit proc_touchscreen:dir search;
# For touchscreen proc files
checkpolicy: error(s) encountered while parsing configuration
external/sepolicy/Android.mk:85: recipe for target '/home/awaaas/android/system/out/target/product/libra/obj/ETC/sepolicy_intermediates/sepolicy' failed

[MENTION=4021423]ketut.kumajaya[/MENTION], can you try to compile it? i'll test it for you....
[Xiaomi Mi 4C] csolanol:
Could you edit the file device/xiaomi/libra/sepolicy/sysinit.te and post its contents?
[Xiaomi Mi 4C] KopiJahe:
I didn't change anything, so the content is the same as ketut.kumajaya's:

# For touchscreen proc files
allow sysinit proc_touchscreen:dir search;
allow sysinit proc_touchscreen:file { write open };
[Xiaomi Mi 4C] KopiJahe:
I finished the compile, did some stuff to do that (commented out SEPOLICY_DIRS, also disabling F2FS). But yeah, I still cannot find mmc1 ._.

Here's some output:

~ # cat /sys/kernel/debug/regulator/pm8994_l13/enable
1
~ # cat /sys/kernel/debug/regulator/pm8994_l21/enable
0
~ # cat /sys/kernel/debug/regulator/pm8994_l21/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
f98a4900.sdhci-vdd	N	2950000 2950000	0
pm8994_l21	N	0	0	0
~ # cat /sys/kernel/debug/regulator/pm8994_l13/consumers
Device-Supply	EN	Min_uV	Max_uV	load_uA
[B][COLOR="Red"]f98a4900.sdhci-vdd-io	Y	1800000	1800000	22000[/COLOR][/B]
pm8994_l13	N	0	0	0
~ # dmesg | grep mmc1
<6>[ 3.922269] mmc1: no vqmmc regulator found
<6>[ 3.922287] mmc1: no vmmc regulator found
<6>[ 3.922552] mmc1: SDHCI controller on f98a4900.sdhci [f98a4900.sdhci] using 32-bit ADMA

The changes on the lines did change the status of vdd-io to enabled, but still no mmc1.

GPIOs 867-877, spmi/qpnp-pin-ffffffc0c4a4a800, pm8994-gpio:
gpio-867 (tp1v8_vreg ) out hi
gpio-868 (volume_up ) in hi
[B][COLOR="Red"] gpio-872 (f98a4900.sdhci cd ) in lo[/COLOR][/B]
gpio-873 (bt_vreg ) out lo

gpio-872 is still read as lo.

Attached full dmesg below.
[Xiaomi Mi 4C] ketut.kumajaya:
I'll disable GPIO interrupt card detection, force enable polling mode in the next build. Let's see if that method working for aqua SD card support in recovery.
[Xiaomi Mi 4C] ketut.kumajaya:
You can try yourself, remove https://github.com/kumajaya/android...boot/dts/qcom/libra/a10-msm8992-mtp.dtsi#L187
[Xiaomi Mi 4C] ketut.kumajaya:
[MENTION=2689045]awaaas[/MENTION] TWRP built just finished, without any errors! That's seems you partial sync Android source for TWRP build only. My own built ready for download and test. Good luck!
[Xiaomi Mi 4C] BlackXhorneT:
It works! Full read/write access and nicely tested by flashing yesterdays build as my test candidate from the SD. Works perfectly. Awesome job guys! We're a fingerprint sensor away from a totally complete recovery and ROM! Amazing!!!
[Xiaomi Mi 4C] KopiJahe:
But I did a full CM 13 + TWRP + your repos sync that's why I said "I didn't understand why I can't compile this" ._.

Anyway, the SDCard can be read in this release. Good job there :highfive: , here's the output of dmesg:

<6>[ 3.720244] mmc1: no vqmmc regulator found
<6>[ 3.720266] mmc1: no vmmc regulator found
<6>[ 3.720550] mmc1: SDHCI controller on f98a4900.sdhci [f98a4900.sdhci] using 32-bit ADMA
<6>[ 4.092094] mmc1: new ultra high speed SDR50 SDXC card at address 0001
<6>[ 4.092408] mmcblk1: mmc1:0001 ASTC 59.5 GiB

Here's some screenshots too....
[Xiaomi Mi 4C] ketut.kumajaya:
Great :good:

[MENTION=2689045]awaaas[/MENTION] Please check if https://github.com/CyanogenMod/android_vendor_cm available locally. No report from emfox if he experienced any build errors.
[Xiaomi Mi 4C] KopiJahe:
Yes, it is available locally (it is part of the default manifest from cm). Anyway, I've succeeded in building TWRP now, by deleting sysinit.te for now. Already contacted emfox, and still waiting for the answer.

By now, I've downloaded 2 separate ubuntu releases (14.04 and 16.04), and three times repo re-download (just in case the file I downloaded is corrupted).
[Xiaomi Mi 4C] ketut.kumajaya:
https://github.com/kumajaya/android_device_xiaomi_libra/blob/cm-13.0/sepolicy/sysinit.te inherited https://github.com/CyanogenMod/android_vendor_cm/blob/cm-13.0/sepolicy/sysinit.te Nothing wrong from my side.
[Xiaomi Mi 4C] KopiJahe:
Yeah, nothing wrong from your side mate. Something is broken on my computer ._.
[Xiaomi Mi 4C] KopiJahe:
[MENTION=4021423]ketut.kumajaya[/MENTION] I've found the reason why I can't compile this earlier. It was because I used lunch command, not breakfast (this page made me thinking that I should use lunch, since this device wasn't in the official list).

Thanks to forkbomb @ cm's irc for helping me figuring this out.
[Xiaomi Mi 4C] ketut.kumajaya:
Now, you ready to contribute to CM :D
[Xiaomi Mi 4C] dedycx:
I think the build 0606 is no better than build 0519, I experienced a frozen screen on my Mi4c.

I use MIUI 7.3.2.0 stable, while using build 0519 screen freeze only a few seconds. and build the most experienced screen freeze for a few minutes
[Xiaomi Mi 4C] cobraplayer:
I can confirm the same behavior on my libra. 19 May build is fine. Newer builds have the same old non-responsive touch screen problem.
[Xiaomi Mi 4C] BlackXhorneT:
Worth noting that they do work fine on aqua. Might be worth having these separate rather than unified if it creates issues for libra
[Xiaomi Mi 4C] ketut.kumajaya:
No. Aqua use different touchscreen driver from atmel. This is purely synaptic issue, let's see what I can do for it, what I have done that trigger this issue back.
[Xiaomi Mi 4C] BlackXhorneT:
In the interest of perfecting this, my Mi4S is still displaying as a "G4" when in TWRP connected to a PC/Mac. Looking on the MIUI forums, other users of this TWRP build are experiencing the same thing. It works a treat so it's not a concern to me, but just so you're aware incase its easily resolved.
[Xiaomi Mi 4C] dedycx:
yes, I too :D
[Xiaomi Mi 4C] ketut.kumajaya:
Time to switch to Ubuntu :laugh:

New build 20160612 available, touch delay on boot have fixed.
[Xiaomi Mi 4C] smartseck:
awesome :good::good::good:

tested on libra
[Xiaomi Mi 4C] BlackXhorneT:
Tested on aqua, works great as before :) still shows up as G4 rather than Mi-4S but not a big deal
[Xiaomi Mi 4C] kurokuroninja:
Tested build 20160612 on libra and no touch delay..

Thank ketut.kumajaya
[Xiaomi Mi 4C] ketut.kumajaya:
And I give you one thanks for free :laugh:
[Xiaomi Mi 4C] Defforest:
Hey bro, i send you PM please check :fingers-crossed:
[Xiaomi Mi 4C] sanzNya:
Its safe to flash the aqua-libra files on xiaomi eu miui 8 mi4s (aqua)? I want to use twrp 302. Now im on v2.8.7 (cmiw version)
[Xiaomi Mi 4C] ketut.kumajaya:
Should be safe but not sure about compatibility to stock ROM, I have created this for CyanogenMod.
[Xiaomi Mi 4C] sanzNya:
So. There's CM13 for aqua with fingerprint fixed? Im lil'bit confused. Mi4s dnt have own forum and it is so bad..
[Xiaomi Mi 4C] BlackXhorneT:
Not yet :(
[Xiaomi Mi 4C] Defforest:
Hey bro, finally i have new device :D

Is your latest TWRP version support for Miui based or another like CM roms? or just like official twrp compatibility based for 5.1/6.0 android.

Because I think your twrp build much more better than any other.
[Xiaomi Mi 4C] ketut.kumajaya:
No feedback so far and not really care about it.
[Xiaomi Mi 4C] kevinnol:
Been flashing between CM and MIUI all the time using ketuts TWRP

MIUI atm no problems so far
[Xiaomi Mi 4C] Defforest:
Hi there, I have feedback about loop issue after flashing twrp

Some of user tell me that they have this problem, its solved after restoring boot.img from default miui rom which before flashing they make backup and maybe you can take look for "boot verify patch"

Look img attached below
[Xiaomi Mi 4C] mendocino_610:
hello kumajaya. I try last build and finaly perfect twrp. no touch delay no bug thank you.

What was the cause of the problem?
[Xiaomi Mi 4C] h4waii:
FYI, while encryption "works", this build is unable to mount p44 to /data -- so it doesn't really work.
[Xiaomi Mi 4C] bo_cah:
Thanks broo, this twrp doesn't has touch problem
[Xiaomi Mi 4C] hansip87:
Hey OP thanks for the effort :) but umm.. can i have the img file to use from anybody who have tried this? i'm noob about compiling things :) Thanks a lot.
[Xiaomi Mi 4C] bibihub:
Hi ! Go to post n°3. You'll find the download link :)
[Xiaomi Mi 4C] ketut.kumajaya:
Today build available:

- Source sync

- Kernel update

- Proper USB vendor and product ID
[Xiaomi Mi 4C] ridman31:
Thanks OP for this wonderfull works .... confirmed working on miui 8.1 by xiaomi.eu build 6.10.20 ... no touch problem when entering twrp recovery for the first time and after :fingers-crossed::good:
[Xiaomi Mi 4C] Noobsi:
To use latest, Just Flash img with twrp?
[Xiaomi Mi 4C] ridman31:
Yep flash as usual
[Xiaomi Mi 4C] verntechguy:
It works fine with my Mi 4c. No touch issues whatsoever. I'm on MoKee 6.0.1 release build.

Just want to inform you as well that you're work is shared on MIUI english forum with no proper credits.

Here's the link of the thread:

http://en.miui.com/forum.php?mod=viewthread&tid=339034&extra=&highlight=mi%2B4c%2Btwrp%2B3.0.2&page=1
[Xiaomi Mi 4C] waingro808:
EDIT: nevermind. got it working!
[Xiaomi Mi 4C] Tr4sHCr4fT:
works great, touchscreen becomes responsible almost instantly, no waiting for minutes anymore!
[Xiaomi Mi 4C] Urcik:
Good afternoon, do you plan to collect twrp for Nougat?

Your assembly is considered to be the best.
[Xiaomi Mi 4C] aluk4rd:
pls trwp for noughat on aqua. had the newest biuld flashed,but the twrp isnt working on it.
[Xiaomi Mi 4C] Tr4sHCr4fT:
is there any build which has no touchscreen delay at all?

this isn't so bad as others i tried, but still annoying (~10s)
[Xiaomi Mi 4C] ViTAMiNCHEG:
For me on aqua working fine. I can see no problem at all
[Xiaomi Mi 4C] sultanbrunei:
Hi,

What are the differences between this recovery and TWRP 3.1.0.0 libra recovery ?
[Xiaomi Mi 4C] saeedh1997:
Hi,

I tried to install twrp by cmd but it didn't find my device bootloader and showed error "bootloader not found" how can i fix it!?!

My device is unlocked and all Required drives are installed
[G2 General] SandyKick:
LG has released a LG Home 4.0 launcher for LG G5 for the missing app drawer. this is purely based on (UX 4.0)

Currently uploaded to LG Smartworld, but im not able to access in our G2. Can any one make it working on our G2 ?

http://us.lgworld.com/store/webview...roductDetail.dev?c=US&l=EN&id=000001176671142
[G2 General] 60nine:
according to apkmirror description - it's only for MM...

http://www.apkmirror.com/apk/lgelec.../homeux-4-0-4-80-4-android-apk-download/#file

Min: Android 6.0 (Marshmallow, API 23)

Target: Android 6.0 (Marshmallow, API 23)
[G2 General] SandyKick:
Yeah Dude ! forgotten that it's base of Marshmallow :) thanks for the reminder :good:
[Verizon Samsung Galaxy S 4] sdstc:
After phone restarted all apps gives stopped working error and screen is black, touch and lights are working. i only can open power menu.

is there a way to fix this or i'll format phone that is i dont want to do
[Verizon Samsung Galaxy S 4] sdstc:
galaxy s4 i9515

kitkat;

2015-04-06	United Arab Emirates	4.4.2	I9515XXU1ANL1	I9515OJV1AOB2

rooted (apps: greenify,supersu only)
[Verizon Samsung Galaxy S 4] sdstc:
upgraded to lollipop problem is solved.
[Verizon Samsung Galaxy S 4] Airsoftjunky:
Boot to recovery, factory reset, and reroot. If nothing is responding, this is my only solution.
[AT&T Samsung Galaxy Note II] RetroRev:
Like the title says. I've got a Note 2 on Cyanogen 12 that won't let me turn on Bluetooth or WiFi and when the screen locks it reboots the ROM. I've tried RR, Carbon, Cyanogen and PAC, all had the same problems. All done with clean installs. I used to be able to get the WiFi and Bluetooth to turn on by going into performance and changing to PegasusQ, then going to Dev Options, Dev tools, Connectivity and disabling the WiFi then smashing the enable a few hundred times. Then randomly it started rebooting the ROM whenever the screen would lock and then even my little work around stopped working.

I'm assuming it's a hardware issue, but figured I'd ask before reflowing the MoBo.

Thanks for any advice!

-Retro
[Non-Touchscreen Windows Mobile Other] sandro.bertini:
Hi there,

I recently sold my Dash to get a Dopod C730 (Cavalier or HTC S630).

I am really loving the device, the powerful processor makes everything snappier and I found an unexpected benefit, the wi-fi, despite being similar in specs is vastly superior to the one in the Dash, specially at a distance or with a weak signal (the connection is fast and rock solid in places at my home where my Dash couldn't hold a connection for more than 30 seconds).

The problem is, I would like to do a lot of customizations in the registry (specially cause the device comes with a Chinese traditional ROM and many parameters are somehow optimized for these language).

The problem is, the phone is Carrier unlocked but is Application Locked. I searched around in the forums and on the Internet but found nothing (maybe because the device is somewhat new).

Someone know of a service or tool I can use to app unlock this phone?

Thanks,

Sandro