[OFFICIAL][9.0.0_r46][ASB_2019-11][grus] XenonHD 9.0 (14-11-2019)

[elpaablo]

Sorry about that. It was a direct link to a well known app and I didn't even think it could break any rule.

 

[elpaablo]

For whoever is interested, I'm using vendor V10.3.9.0.PFBEUXM (and firmware) without (adicional) issues. Tested on XenonHD and MoKee.

 

[briandarrel]

For whoever is interested, I'm using vendor V10.3.9.0.PFBEUXM (and firmware) without (adicional) issues. Tested on XenonHD and MoKee.

Does it offer any improvement over 9.7.4?

 

[guitarbite]

The automatic WiFi connection is a deal breaker for me in this rom and all AOSP ROMs... Wish that was fixed as all other like fingerprint snappiness is not as important...

 

[briandarrel]

The automatic WiFi connection is a deal breaker for me in this rom and all AOSP ROMs... Wish that was fixed as all other like fingerprint snappiness is not as important...

WiFi connects automatically works for me in PE...

 

[Humpfrey]

WiFi connects automatically works for me in PE...

No problems on mokee too :silly:

 

[elpaablo]

Does it offer any improvement over 9.7.4?

None that I've noticed. But you'll keep your vendor updated in your treble enabled device. I was able to install Q GSI and come back to Pie AOSP, without changing vendor.

No problems on mokee too :silly:

And no problems on crDroid. The only ROM having this annoying issue is XenonHD.

 

[CherryLime]

For whoever is interested, I'm using vendor V10.3.9.0.PFBEUXM (and firmware) without (adicional) issues. Tested on XenonHD and MoKee.

i tried to flash the ROM with vendor V10.3.9.0.PFBEUXM but it gave me always Error 7. I can't find vendor V10.3.4.0.PFBEUXM, so maybe someone can give me a link for it?

 

[Talkrabb]

i tried to flash the ROM with vendor V10.3.9.0.PFBEUXM but it gave me always Error 7. I can't find vendor V10.3.4.0.PFBEUXM, so maybe someone can give me a link for it?

You find it here:
https://bigota.d.miui.com/V10.3.4.0.PFBEUXM/miui_GRUSEEAGlobal_V10.3.4.0.PFBEUXM_409f6dbb6f_9.0.zip

 

[elpaablo]

i tried to flash the ROM with vendor V10.3.9.0.PFBEUXM but it gave me always Error 7. I can't find vendor V10.3.4.0.PFBEUXM, so maybe someone can give me a link for it?

It's probably a verification from the updater-script. I've used vendor 10.3.9 (and firmware) with this ROM and I had no issues. But if course it's always good practice to use the recommended vendor. So I guess you can install the recovery ROM from the link above and then install XenonHD on top if it.

 

[rp158]

@CherryLime
1. standard solution for error 7: dive into zip-file to META-INF/com/google/android/updater-script and delete the 1st assert-line.
2. Vendors from here.

 

[elpaablo]

@CherryLime
1. standard solution for error 7: dive into zip-file to META-INF/com/google/android/updater-script and delete the 1st assert-line.
2. Vendors from here.

It's actually the second line (first one verifies phone model). You can also edit the updater-script from xiaomifirmwareupdater.com vendor/firmware zip file and comment (or delete) that annoying line that flashes vbmeta, avoiding a trip to fastboot mode to reflash vbmeta with --disable-verity --disable-verification parameters.

 

[Talkrabb]

Just noticed that XenonHD-191018-Official-grus is available for download.

 

[Talkrabb]

Installed the update and it works fine as the version before.

Unfortunately the Wi-Fi reconnect bug is still present.

Here are the logs:
http://aw6.de/grus/2019-10-19_12.39.zip
(Was connected to my Wi-Fi, turned flight mode on and off -> did not reconnect. Had to select my Wi-Fi by hand to get access again.)

My configuration:
twrp-3.3.1-9-Mi9SE.img
XenonHD-191018-Official-grus.zip
Okitavera-kernel-8.3_R3-Mi9SE.zip
Magisk 20.0
magisk-goodix-fod-wakeup-1.3.zip

Android security level 1.August 2019
Manufacturer safety patch level 5.August 2019

By the way:
Is there a way to get a newer security patch than August?

 

[okitavera]

Installed the update and it works fine as the version before.

Unfortunately the Wi-Fi reconnect bug is still present.

Here are the logs:
http://aw6.de/grus/2019-10-19_12.39.zip
(Was connected to my Wi-Fi, turned flight mode on and off -> did not reconnect. Had to select my Wi-Fi by hand to get access again.)

My configuration:
twrp-3.3.1-9-Mi9SE.img
XenonHD-191018-Official-grus.zip
Okitavera-kernel-8.3_R3-Mi9SE.zip
Magisk 20.0
magisk-goodix-fod-wakeup-1.3.zip

Android security level 1.August 2019
Manufacturer safety patch level 5.August 2019

By the way:
Is there a way to get a newer security patch than August?

The ROM itself is actually uses October patches. it just the platform security patch string
And you can't report anything when you have a modded system (e.g : custom kernel, magisk modules, etc).

 

[elpaablo]

Incoming calls issue seems to be solved. Wifi auto-connect and live display still don't work.

 

[ashus]

As I spent my fair share of time trying to get this ROM working the other day, I'd like to share my final verified steps to successfully flash this ROM:

• backup everything you want to your PC or say goodbye to your data
• flash twrp-3.3.1-10-Mi9SE.img by redispade using fastboot (this one is required as the other one has broken encryption)
• flash vbmeta.img using `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img` still in fastboot
• boot to TWRP, flash fw-vendor_grus_miui_GRUSEEAGlobal_V10.3.9.0.PFBEUXM
• clear system, data, cache, dalvik
• if coming from another TWRP recovery, you also need to format internal storage filesystem as encryption might not be ready and you could end up with bootloops (this will delete all user data)
• somewhere in the process of flashing below you might get an error. In that case just unmount system and leave only data and cache mounted. No need to reboot.
• flash XenonHD-191018-Official-grus.zip (modified to skip vendor asserts)
• flash Open GApps arm64 9.0 (nano or your favourite flavour)
• flash Okitavera-kernel-8.4-Mi9SE.zip
• flash Magisk-v20.0.zip
• reboot to system
• install ANXCameraUnity_152.InsubstantialThinFieldspaniel.zip as module using Magisk

If you keep restarting to fastboot, you need vbmeta.
If you keep seeing bootloop with Mi logo and "unlocked" over and over again, you might need to format internal storage. I spent hours and tried many guides from this thread before I figured this one out.
Also I needed OTG USB flash drive with files above as I cound't get MTP working in my Windows 10.


Now I'm happy with this new ROM coming from deprecated Pixel Experience. This ROM looks very clean and close to LineageOS. UI was kept finely tuned and not many more customizations were made (eg. crDroid has many more switches, but I couldn't get light grey font over white screen of NFC read tag changed).

I'd like to thank krasCGQ and other contributors for the hard work they've done, I like this ROM and I chose to use it daily.

Here are my remarks:

1. The vendor assert is just wrong, please remove it. Currently I tried to follow guides, but mentioned vendors are nowhere to be found. Also the flashing guide was too generic and could not be followed properly.
2. I also experience the wi-fi reconnection problem, please look into it. To me it looks like the accesspoint list is not updated frequently enough. I put my phone away, went to another area (10min) and when I turned it on, I saw the old SSIDs for another 30s. Too deep sleep?
3. I can't send SMS messages. I can receive them though. Has anyone here even tried that nowadays? My phone is GLOBAL variant and I'm not sure vendor EU version couldn't be the cause.

 

[okitavera]

The vendor assert is just wrong, please remove it. Currently I tried to follow guides, but mentioned vendors are nowhere to be found. Also the flashing guide was too generic and could not be followed properly.

The vendor assert is right, it because the ROM are meant to be used on top of the Stable vendor to get rid of any unexpected behavior from using Beta vendor.

 

[krasCGQ]

flash twrp-3.3.1-10-Mi9SE.img by redispade using fastboot (this one is required as the other one has broken encryption)

What do you mean by "broken encryption" in other TWRPs? If you previously came from Android 10-based MIUI, yes, currently not supported for most.

The vendor assert is just wrong, please remove it. Currently I tried to follow guides, but mentioned vendors are nowhere to be found.

No. Mentioned vendors: here.

August China developer vendors are known cause issues currently.

I can't send SMS messages. I can receive them though. Has anyone here even tried that nowadays?

Works just fine here.
(see attached screenshot, but ignore the language)

Sent from my MI 9 SE using XDA Labs

 

[chinke]

Best battery life with okita kernel.