[RECOVERY][TWRP 3.0.x][4c - libra][4s - aqua] Recovery built from source

awaaas · Jun 6, 2016

ketut.kumajaya said:
@awaaas 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!

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:

Code:

<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....

ketut.kumajaya · Jun 7, 2016 at 2:39 AM

BlackXhorneT said:
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!!!

awaaas said:
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:

Code:

<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....

Great :good:
@awaaas Please check if https://github.com/CyanogenMod/android_vendor_cm available locally. No report from emfox if he experienced any build errors.

awaaas · Jun 8, 2016 at 3:15 AM

ketut.kumajaya said:
Great :good:

@awaaas Please check if https://github.com/CyanogenMod/android_vendor_cm available locally. No report from emfox if he experienced any build errors.

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).

ketut.kumajaya · Jun 8, 2016 at 6:17 AM

awaaas said:
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).

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.

awaaas · Jun 8, 2016 at 8:34 AM

ketut.kumajaya said:
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.

Yeah, nothing wrong from your side mate. Something is broken on my computer ._.

awaaas · Jun 9, 2016 at 1:44 PM

@ketut.kumajaya 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.

ketut.kumajaya · Jun 9, 2016 at 3:44 PM

awaaas said:
@ketut.kumajaya 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.

Now, you ready to contribute to CM

dedycx · Jun 11, 2016 at 7:22 PM

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

cobraplayer · Jun 12, 2016 at 3:28 AM

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.

BlackXhorneT · Jun 12, 2016 at 11:33 AM

ahaider7 said:
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.

Worth noting that they do work fine on aqua. Might be worth having these separate rather than unified if it creates issues for libra

Sent from my Mi-4s using XDA-Developers mobile app

ketut.kumajaya · Jun 12, 2016 at 12:55 PM

BlackXhorneT said:
Worth noting that they do work fine on aqua. Might be worth having these separate rather than unified if it creates issues for libra

Sent from my Mi-4s using XDA-Developers mobile app

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.

BlackXhorneT · Jun 12, 2016 at 4:46 PM

ketut.kumajaya said:
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.

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.

dedycx · Jun 12, 2016 at 7:36 PM

ahaider7 said:
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.

yes, I too

ketut.kumajaya · Jun 12, 2016 at 7:41 PM

BlackXhorneT said:
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.

Time to switch to Ubuntu :laugh:

New build 20160612 available, touch delay on boot have fixed.

smartseck · Sep 15, 2009 61 3 0

ketut.kumajaya said:
Time to switch to Ubuntu :laugh:

New build 20160612 available, touch delay on boot have fixed.

awesome :good::good::good:

tested on libra

BlackXhorneT · Jun 13, 2016 at 10:41 AM

Tested on aqua, works great as before

still shows up as G4 rather than Mi-4S but not a big deal

Sent from my Mi-4s using XDA-Developers mobile app

kurokuroninja · Jun 14, 2016 at 6:49 AM

Tested build 20160612 on libra and no touch delay..
Thank ketut.kumajaya

ketut.kumajaya · Jun 14, 2016 at 7:09 AM

kurokuroninja said:
Tested build 20160612 on libra and no touch delay..
Thank ketut.kumajaya

And I give you one thanks for free :laugh:

Defforest · Jul 5, 2016 at 8:11 AM

ketut.kumajaya said:
And I give you one thanks for free :laugh:

Hey bro, i send you PM please check :fingers-crossed:

sanzNya · Jul 9, 2016 at 11:44 PM

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)

[RECOVERY][TWRP 3.0.x][4c - libra][4s - aqua] Recovery built from source

Senior Member

Attachments

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member