[OFFICIAL][libra] TWRP 3.1

[Sebbo06]

After some dtb repacking and testing I think that this is caused by touchscreen firmware updating in first boot. In second it should work normally.

Wysłane z mojego Mi-4c przy użyciu Tapatalka

I tried this method, but it still doesn*t work for me.
I rebootet the phone three times after updating via flashify.

 

[kevinnol]

Flashed it and had the touchscreen issue for a few minutes, after that nothing. No problems at all
Appreciate your work

*I deleted the twrp folder and used fastboot erase recovery just in case

 

[Sebbo06]

Flashed it and had the touchscreen issue for a few minutes, after that nothing. No problems at all
Appreciate your work

*I deleted the twrp folder and used fastboot erase recovery just in case

Yes it worked now
I did the following:
1. Install [TOOL]Minimal ADB and Fastboot [8-28-15]6 and put the twrp.img from here in that folder
2. Run the Phone in fathboot mode
3. Open Minimal ADB and Fastboot
4. Type in: fastboot erase recovery
5. Type in: fastboot flash twrp.img
6. Reboot the phone by holding the power button for some seconds
7. Reboot into recovery and wait 3-5 minutes
8. Done

PS. Next reboot into recovery will be without any delay

Update: Delay is back, you have to wait about 1 min to be able to unlock the touch screen.

 

[msdx123]

Could you push your device to Github plz?
I'm working on TWRP 3.0 too, but I face some problems with SElinux.
THX.

 

[AndropaX]

I using alterbang device tree without any big changes.

Wysłane z mojego Mi-4c przy użyciu Tapatalka

 

[Sebbo06]

I using alterbang device tree without any big changes.

Wysłane z mojego Mi-4c przy użyciu Tapatalka

Please check this out:
http://en.miui.com/forum.php?mod=viewthread&tid=228966&highlight=twrp

This worked for me without any bugs, no delay or something.
Just flash it via flashify.

 

[AndropaX]

I updated kernel and dtb from newest mirecovery. This should fix that. Let' see for how long...

 

[ermacwins]

http://www.teamsuperluminal.org/ts-twrp-3-0-0-0-recovery-for-xiaomi-mi4c/

I haven't tried it yet

 

[msdx123]

I using alterbang device tree without any big changes.

Wysłane z mojego Mi-4c przy użyciu Tapatalka

Did you change anything about SElinux?
Cz in alterbang's device tree SElinux is disabled
But your recovery set SElinux to permissive.
Once I set SElinux to permissive, my TWRP could not boot.

 

[mendocino_610]

I try a many many twrp build everytime touchscreen problem. this version too long touchscreen problem....

 

[AndropaX]

If you have newest dev miui r2 version should normally work.

Wysłane z mojego Mi-4c przy użyciu Tapatalka

 

[mendocino_610]

No still touch problem

Mi-4c cihazımdan Tapatalk kullanılarak gönderildi

 

[fays91]

Hello always touch problem
The only recovery that does not have this problem and that of TS TEAM Version 2.8.7.3
their version 3.0.0.2 Touch prblème
why not this based on this 3.0.0.2 version fixed the bug

 

[anandmore]

@AndropaX
Added to [INDEX] Xiaomi Mi 4C

 

[cy-rock]

Perfect with CM12.1 and flashed using flashable zip from previous recovery 2.8

 

[ketut.kumajaya]

@AndropaX I confirm touchscreen firmware "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization. Replace your TWRP kernel with my own normal boot kernel fix this issue.

 

[AndropaX]

About which kernel do you say?

Wysłane z mojego Mi-4c przy użyciu Tapatalka

 

[ketut.kumajaya]

My kernel version:

# cat /proc/version                                               
Linux version 3.10.49-perf-gbd5d555-03937-g649baf6 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Dec 3 23:41:23 CST 2015

from miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip

 

[Brunnys]

@AndropaX @ketut.kumajaya
So it is possible to have a TWRP 3.0 without touch problems? How can we make it?

 

[ketut.kumajaya]

@AndropaX @ketut.kumajaya
So it is possible to have a TWRP 3.0 without touch problems? How can we make it?

Not sure, this TWRP in-kernel touchscreen firmware known different to my normal boot firmware, touchscreen lag on boot because initial firmware flashing process. Two possible solution, change touchscreen driver probe order early or prevent touchscreen driver to flash a firmware update on recovery boot.

No TWRP problem for me, my normal boot and recovery boot will be always use same kernel, same in-kernel touchscreen firmware, no boot delay because of touchscreen firmware flashing process.