[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] smeroni68:
FAQ Section...

This is the FAQ (Frequently Asked Questions).

Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!

If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!​

​

Q1:Fingerprint wake/home button works?

A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)

Q2: How can I revert back from treble to custom ROM whenever required?

A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.

Q3: If I revert to a Custom rom, what I need to do to restore treble support?

A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...

Q4: Phh GSI rom is quite poor in functionality. Why?

A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.

This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.

The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.

In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.

Q5: If a new version of treble support is out, did I need to flash it or not?

A: Our project is on the way. This means that

if is available a new update from us, it is for sure an enhancement with more support of feature or fixes

.

In case you will need to install a GSI rom, check always here if there is any new version and get it.

In case you are running a custom rom without treble support, DO NOT update with treble flash

, because most probably you will break your current installation.

Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!

Q6: How to get ROOT on phh gsi?

A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.

Q7: Where I can find the GSI images available?

A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page

Q8: Everytime I entered the password, it says Decryption Unsuccessful!

A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a

FORMAT DATA

from TWRP to "destroy" the encryption and "free your phone from it"!

Q9: Is Google Camera working on Gsi?

A: Yes. But remember you need to install gapps package to let gcam works as it should.

We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the

Settings

->

Fix

->and enable the fix for

Front Camera

and

reboot

. For SlowMotion, set

120fps

.

Q10: Why can't flash a micro gapps and only pico is flashable?

A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:

Flash the SYSTEM.IMG you wanna use (

select a Vanilla based one

)

Reboot to RECOVERY

MOUNT the SYSTEM partition

Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM

select RESIZE FILE SYSTEM

than SWIPE to execute the command...

in case of error (you will see in red), repeat the RESIZE until it goes completed (

Resizing... Done

)

After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)

before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)

Now you can flash the micro gapps without problem.

Q11: Is there any Magisk version working on Treble gsi?

A: Yes, you need to get v18.1 version or newer with treble support (check around).

Q12: VoLTE is working[/B]?

A: Yes. Install this ims.apk to use it!

Q13: ADB Logs are needed in case of Issue reporting...

A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)

prepare a PC (with adb package to support debug via usb connection)

flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)

reboot the phone

connect the usb cable

after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised

go in a command window and type:

--> adb devices (if the phone is connected, you will see the code written after the command executed)

--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)

--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.

send attached to the issue description post the

bootlog.txt

...let's dev check what's happening by reading the logcat.

... list will be updated...