Android Pie libra by @Kenga
- Thread starter cacafaruq
- Start date
I have the same problem. Right now I'm using 3.1.1-0 on lollipop bootloader. If I update to a 3.2 recovery version I can't boot to it.
The new version of LineageOS 16.0 has been released: https://androidfilehost.com/?fid=11410963190603889118 
The new version of LineageOS 16.0 has been released: https://androidfilehost.com/?fid=11410963190603889118
How about the problem ?
Is it good ? Is TRUST disable after magisk installed ?
Random error like 1st build ?
Did you find a fix?
I never had so much trouble getting TWRP to work
I did the same upgrade to new TWRP and PIE with a Redmi 4 Prime (Markw) and it took me 5 min to succeed. But when I tried with updating TWRP on my Mi4C (Libre) it would not boot into new TWRP. I have spend hours with no luck. I tried several offical and non-official versions of TWRP for Libre. They all show success when flashing TWRP both from within TWRP and with adb/fastboot. But then won't boot to recovery, but hangs at Mi logo. I originally came from twrp cofface from Teamsuperluminal, which I believe was around version 2.8.
I tried flashing all newest officiel from AndropaX (twrp-3.1.1-1-libra.img, twrp-3.1.1-0-libra.img)
then from other developers and lastly:
twrp-3.2.1-0.img (Vovan77)
TWRP+3.2.3-0_libra.img (Vovan77)
TWRP+3.2.2-0_libra.img (Vovan77)
As mentioned all succeeded with no errors, but then would not boot. However from fastboot/adb I could flash, but not run fastboot boot <img file name>. It would give me the error: FAILED (remote: dtb not found).
I did manage to get TWRP 3.1.0.0 (twrp-20170815-0837.img from Cozzmy13) to boot with no issues, but when inside TWRP it gave me error 7 when flashing. I then tried to remove the first lines starting with assert from the custom rom and TWRP was then able to flash the ROM with no errors. However now the ROM did not boot Tried with both PixelExperience_libra-8.1.0-20180825-0823-STABLE & lineage-16.0-20190102-UNOFFICIAL-libra)
I checked my bootloader and it is not locked and I was still able to restore my nandroid with TWRP 3.1.0.0.
Really want to upgrade to PIE and don't want to give up. Hope someone found the fix.
At the moment my last guess is that I new to update my bootloader somehow - indicating from the errors I received. I believe the current was marshmellow. To do this I need to flash latest miui? Meanwhile I'll try to flash xiaomi.eu_multi_MI4c_V10.1.1.0.NXKCNFI_v10-7.0.zip and see if it updates the bootloader.
I never had so much trouble getting TWRP to work
I did the same upgrade to new TWRP and PIE with a Redmi 4 Prime (Markw) and it took me 5 min to succeed. But when I tried with updating TWRP on my Mi4C (Libre) it would not boot into new TWRP. I have spend hours with no luck. I tried several offical and non-official versions of TWRP for Libre. They all show success when flashing TWRP both from within TWRP and with adb/fastboot. But then won't boot to recovery, but hangs at Mi logo. I originally came from twrp cofface from Teamsuperluminal, which I believe was around version 2.8.
I tried flashing all newest officiel from AndropaX (twrp-3.1.1-1-libra.img, twrp-3.1.1-0-libra.img)
then from other developers and lastly:
twrp-3.2.1-0.img (Vovan77)
TWRP+3.2.3-0_libra.img (Vovan77)
TWRP+3.2.2-0_libra.img (Vovan77)
As mentioned all succeeded with no errors, but then would not boot. However from fastboot/adb I could flash, but not run fastboot boot <img file name>. It would give me the error: FAILED (remote: dtb not found).
I did manage to get TWRP 3.1.0.0 (twrp-20170815-0837.img from Cozzmy13) to boot with no issues, but when inside TWRP it gave me error 7 when flashing. I then tried to remove the first lines starting with assert from the custom rom and TWRP was then able to flash the ROM with no errors. However now the ROM did not boot
Tried with both PixelExperience_libra-8.1.0-20180825-0823-STABLE & lineage-16.0-20190102-UNOFFICIAL-libra)I checked my bootloader and it is not locked and I was still able to restore my nandroid with TWRP 3.1.0.0.
Really want to upgrade to PIE and don't want to give up. Hope someone found the fix.
At the moment my last guess is that I new to update my bootloader somehow - indicating from the errors I received. I believe the current was marshmellow. To do this I need to flash latest miui? Meanwhile I'll try to flash xiaomi.eu_multi_MI4c_V10.1.1.0.NXKCNFI_v10-7.0.zip and see if it updates the bootloader.
Unfortunately no, I don't found a fix for it. I'm staying with Oreo for now.Did you find a fix?
I never had so much trouble getting TWRP to work
I did the same upgrade to new TWRP and PIE with a Redmi 4 Prime (Markw) and it took me 5 min to succeed. But when I tried with updating TWRP on my Mi4C (Libre) it would not boot into new TWRP. I have spend hours with no luck. I tried several offical and non-official versions of TWRP for Libre. They all show success when flashing TWRP both from within TWRP and with adb/fastboot. But then won't boot to recovery, but hangs at Mi logo. I originally came from twrp cofface from Teamsuperluminal, which I believe was around version 2.8.
I tried flashing all newest officiel from AndropaX (twrp-3.1.1-1-libra.img, twrp-3.1.1-0-libra.img)
then from other developers and lastly:
twrp-3.2.1-0.img (Vovan77)
TWRP+3.2.3-0_libra.img (Vovan77)
TWRP+3.2.2-0_libra.img (Vovan77)
As mentioned all succeeded with no errors, but then would not boot. However from fastboot/adb I could flash, but not run fastboot boot <img file name>. It would give me the error: FAILED (remote: dtb not found).
I did manage to get TWRP 3.1.0.0 (twrp-20170815-0837.img from Cozzmy13) to boot with no issues, but when inside TWRP it gave me error 7 when flashing. I then tried to remove the first lines starting with assert from the custom rom and TWRP was then able to flash the ROM with no errors. However now the ROM did not boot
I checked my bootloader and it is not locked and I was still able to restore my nandroid with TWRP 3.1.0.0.
Really want to upgrade to PIE and don't want to give up. Hope someone found the fix.
At the moment my last guess is that I new to update my bootloader somehow - indicating from the errors I received. I believe the current was marshmellow. To do this I need to flash latest miui? Meanwhile I'll try to flash xiaomi.eu_multi_MI4c_V10.1.1.0.NXKCNFI_v10-7.0.zip and see if it updates the bootloader.
I don't want to update to MIUI just to only update the bootloader and have to unlock it again. That's it the last option.
Yes, when installing magisk, you will see 'detect stock boot image...' log etc..
I installed twrp to miui 10 , without magisk it won't boot. When i changed this rom, no need magisk to boot, maybe 'Magisk already patch the boot image '
("dt2w" "network traffic" not working in this rom)
I had installed Oreo rom on Lollipop bootloader with this method. "twrp-20180106-1033.img" has touch screen freeze bug for me. Need to wait about 5mins and then, it work normally.
Did you find a fix?
I never had so much trouble getting TWRP to work
I did the same upgrade to new TWRP and PIE with a Redmi 4 Prime (Markw) and it took me 5 min to succeed. But when I tried with updating TWRP on my Mi4C (Libre) it would not boot into new TWRP. I have spend hours with no luck. I tried several offical and non-official versions of TWRP for Libre. They all show success when flashing TWRP both from within TWRP and with adb/fastboot. But then won't boot to recovery, but hangs at Mi logo. I originally came from twrp cofface from Teamsuperluminal, which I believe was around version 2.8.
I tried flashing all newest officiel from AndropaX (twrp-3.1.1-1-libra.img, twrp-3.1.1-0-libra.img)
then from other developers and lastly:
twrp-3.2.1-0.img (Vovan77)
TWRP+3.2.3-0_libra.img (Vovan77)
TWRP+3.2.2-0_libra.img (Vovan77)
As mentioned all succeeded with no errors, but then would not boot. However from fastboot/adb I could flash, but not run fastboot boot <img file name>. It would give me the error: FAILED (remote: dtb not found).
I did manage to get TWRP 3.1.0.0 (twrp-20170815-0837.img from Cozzmy13) to boot with no issues, but when inside TWRP it gave me error 7 when flashing. I then tried to remove the first lines starting with assert from the custom rom and TWRP was then able to flash the ROM with no errors. However now the ROM did not boot
I checked my bootloader and it is not locked and I was still able to restore my nandroid with TWRP 3.1.0.0.
Really want to upgrade to PIE and don't want to give up. Hope someone found the fix.
At the moment my last guess is that I new to update my bootloader somehow - indicating from the errors I received. I believe the current was marshmellow. To do this I need to flash latest miui? Meanwhile I'll try to flash xiaomi.eu_multi_MI4c_V10.1.1.0.NXKCNFI_v10-7.0.zip and see if it updates the bootloader.
Link for xiaomi.eu_multi_MI4c_V10.1.1.0.NXKCNFI_v10-7.0.zip ?
Hey guys,
I have 100% the same issue as jones321 has. I'm not able to flash any Pie ROM and most of the OREO Roms to mi4c. I have unlocked bootloader (old method - lollipop) an using 3.1.1.0 TWRP an [OFFICIAL][7.1.2] LineageOS 14.1 for libra/aqua ROM. I suspect that I have to install official miui Nougat ROM and ask to unlock bootloader again with official method... I tried several times & with several Miui 10/9 stable roms but I could not add my verified XIAOMI account to Unlock OEM Status via Developer setting with various errors : 90001 Cant add error or Try again later error. So it seems I'm stuck unless someone explain to me why it is not possible to flash PIE or most OREO ROMS (all with error 7 or after deleting assert lines in updater-script with infinite bootloop).
My questions are:
- do we need to unlock nougat 7 bootloader official way to use OREO/PIE Roms?
- or we just need proper boot img/kernel to be flashed before trying to install OREO/PIE Roms?
If someone knows the answer, please let us know. It would be greatly appreciated.
I have 100% the same issue as jones321 has. I'm not able to flash any Pie ROM and most of the OREO Roms to mi4c. I have unlocked bootloader (old method - lollipop) an using 3.1.1.0 TWRP an [OFFICIAL][7.1.2] LineageOS 14.1 for libra/aqua ROM. I suspect that I have to install official miui Nougat ROM and ask to unlock bootloader again with official method... I tried several times & with several Miui 10/9 stable roms but I could not add my verified XIAOMI account to Unlock OEM Status via Developer setting with various errors : 90001 Cant add error or Try again later error. So it seems I'm stuck unless someone explain to me why it is not possible to flash PIE or most OREO ROMS (all with error 7 or after deleting assert lines in updater-script with infinite bootloop).
My questions are:
- do we need to unlock nougat 7 bootloader official way to use OREO/PIE Roms?
- or we just need proper boot img/kernel to be flashed before trying to install OREO/PIE Roms?
If someone knows the answer, please let us know. It would be greatly appreciated.
IMO, yes. I'm using official unlock bootloader and then flash with official twrp. In pie rom, u can't using official twrp because it's old ver (3.1.1-1).
After that, i flashed new twrp from vovan77 (3.2.3.0). It worked well.
I don't understand about old method lollipop ? What is it ?
OK. I thought you had to have unlocked nougat official way...because you managed to install the new 3.2.3.0 TWRP and we can not. I unlocked the bootloader the old way without official xiaomi unlocking service back in 2015. You just had to flash some of the old official Lollipop ROMS ...after that you could unlock bootloader via fastboot command
I t seems that Nougat / 7.0, the bootloader is locked again, with a different bit. The lock bit used up to 5.1 can be unlocked via downgrading to 6.1.7, but the lock bit used since 7.0 can only be unlocked via the official Mi Unlock procedure.
My question is if there is any way how to install Kengas PIE ROM or any other PIE ROM without officially unlocked Nougat / 7.0, the bootloader???
I was able to install Nitrogen OS Oreo 8.1 ROM which seems to be somehow compatible with [OFFICIAL][7.1.2] LineageOS 14.1 for libra/aqua. Other OREO Roms does not work for me unfortunately (bootloop)
I wish...I've tried several times & with several Miui 10/9 stable roms but I simply could not add my verified XIAOMI account to Unlock OEM Status via Developer setting with various errors :
90001 Cant add error or
Try again later error.
So it seems I'm stuck unless someone explain to me how to flash PIE ROM with unlocked bootloader (unofficial) and TWRP 3.1.1.0
If there someone who is able to flash PIE under above mentioned condidtion...please share your experience.
Thanks.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12https://androidfilehost.com/?fid=11410963190603852543
Here latest rom by @kenga
Give our support :highfive::good:4Yes i have the same problem . When try to install gapps error 70.
I am very disappointed for this , the Play Store with ROM don't working , and is a live - dead pie ROM. I 'll try to install Play Store from Aptoide but nothing happen...
I come back to Kenga ROM and i pray to find a pie ROM who work well. Or i think so it's time to buy a new mobile and RIP Mi4C
---------- Post added at 04:58 AM ---------- Previous post was at 04:57 AM ----------
How to install app uninstaller ap without play store ?
That's beacuse the free space in "/system" is almost used up in the lineage-16.0 builds. I decided to make "/system" full of use since I built the lineage-15.1 roms, but didn't save enough space for GAPPs (mostly because Google is still blocked in China).
It's simple to solve this problem by removing something in "/system". Just delete /system/fonts/NotoSerifCJK-*.ttc (totally 2 files, 48MB), then you could install the pico version of GAPPs. If you also removed /system/fonts/NotoSansCJK-*.ttc (not recommend, 109MB), you could install a much bigger one.
The extra space this rom uses in /system is mainly from dex2oat and full-weight Noto fonts.
For the first one: The filter flags of dex2oat is set to "speed" for better performance, which takes more time and space when building the rom but will improve the performance and boot-up speed on the first boot. It will also takes more time when you install your APKs, but you'll get better performance for the first start-up on the app you install. In most roms with default configs, all the free space that "dex2oat" used at last (eg. when you charging your phone and don't use it) will appear in "/data" (exactly, /data/dalvik-cache/). The APK installing speed is faster, but it need to be compiled again as "speed" filter at last and cause poor performance until this procedure fully completed. So I use a more aggressive way for such cases, which sets "speed" filter as default values. This part should not be removed.
For the second one: In android pie, Google add full weight Noto fonts for English only, and other languages like Chinese/Japanese/Korean (CJK) do not have full-weight fonts at all (only regular and bold fonts). So I complete the NotoCJK fonts family and the visual experience becomes much better after that, which is also at the cost of free space in "/system". This part could be directly removed if C/J/K are not your main languages.44Ok I've just managed to get PIE working on mi4c. Here are the steps for those who cannnot unlock their phone officially or for those who just dont want to wait if Xiaomi allows them to unlock their Nougat 7 bootloader.
1. Unlock the bootloader the old way by using MiFlash application (phone in fastboot EDL mode) and flashing old version of miui dev china with unlocked bootloader libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz (if you already have unlocked bootloader you may skip obviously)
2. Install with fastboot universal TWRP (works on both lollipop and nougat bootloader) twrp-20180106-1033.img
3. In TWRP (without rebooting!!!) install via adb sideload in batch firmware patch libra_miui_fw_patch_MI4c_V9.5.1.0.NXKCNFA.zip, install ROM RR-O-v6.1.0-20180627-libra-Unofficial.zip, Gapps (in this case PixelMod_Gapps_arm64_Oreo_libra_universal_27.06.18.zip) and finally Magisk-latest_version.zip
4. Restart to the system
5. After that I was able to copy twrp-3.2.1-0.img to sdcard and install this image to upgrade TWRP (This way you can upgrade also to TWRP+3.2.3-0_libra.img)
After this you have a locked bootloader but it is working with latest TWRP and you can install PIE ROMs and updates, but always remember to install Magisk !!!
All files mentioned except the the dev ROM are accessible at Vovan77 https://androidfilehost.com/?w=files&flid=256671
Unlocked dev ROM can be found here: https://xdaforums.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
All credits goes to Vovan77 and his work...thanks mate for updating mi4c for PIE...much appreciated!!!
original thread found here: http://en.miui.com/thread-3111433-1-1.html
Not sure yet if the PIE is worth to upgrade but the first impression is good. And last crDroidAndroid-v5.0 was updated 2 days ago by Vovan77!
