[ROM][11.0][4.9][AOSP][SUZU] Explosive Lobster

[lubik1]

[ROM][11.0][4.9][AOSP][SUZU] Explosive Lobster
SUZU F5121 and F5122

Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X (will never die)
Many Thanks for development @Cubbins

I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.

This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.

How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.

Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.

Features:

Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
- Encrypting Data

Not Working:
You tell me

Sources:

build ROM sources:
github.com/ExplosiveLobster

kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9

bug reports:
github.com/ExplosiveLobster/bug_tracker/issues

Screenshots:


Download:
Google Drive

Explosive Lobster - Google Drive

drive.google.com

Mega

3.11 GB folder on MEGA

12 files and 3 subfolders

mega.nz

 

[twain55]

Great work!

 

[GOrMHATRe]

Nice work dude. I am yet to flash but I appreciate your efforts. But I am using a custom rom already. Do I need to reflash stock rom before flashing your rom ? Is there any way to flash without sd card by using adb?

 

[lubik1]

Do I need to reflash stock rom before flashing your rom ? Is there any way to flash without sd card by using adb?

No, you don't. You can try flash from internal storage, but you can't flash rom with adb

 

[pitfallykmr]

@lubik It looks like there is an issue with calls. I can't hear a companion and companion can't hear me. Microphone and speakers work correctly if you try Google search...

 

[lubik1]

@lubik It looks like there is an issue with calls. I can't hear a companion and companion can't hear me. Microphone and speakers work correctly if you try Google search...

Tomorrow I will build a new version with a fix, latest sources and kernel security patch.

 

[lubik1]

Updated.

Changelog:
1) Fixed Calling
2) Fixed Music Playing
3) Fixed recovery (bug with AOSP recovery installing after reboot)
4) Latest Sources and security patch

 

[ak47kdk]

Awesome work dude, never thought android R making it's way to xperia X..

 

[danidarklord]

Amazing, I never thought I will ever experience android 11 on this device. Thank you

 

[Cubbins]

Good job guys! Thank you!

 

[tamisoft]

I would be coming from Q TWRP 3.3.1, but selecting the zip to install gives E1001: failed to update system image. Is there something I am forgetting? (it already has the ODM partition flashed for Q)

 

[pitfallykmr]

You can try TWRP 3.4. It works fine for me.

 

[tamisoft]

You can try TWRP 3.4. It works fine for me.

Thank you it works with that.

 

[tamisoft]

Which gapps do you recommend? I tried NikGapps full but fingerprint unlock seems to be missing, also I couldn't encrypt the phone. It fails to mount userdata on next boot, and causes a bootloop on zygote. Also I have noticed a changed behavior with the new ODM partition, if the charger is connected it comes up on reboot in some factory flashing mode (just reports android in usb descriptor, and there is no fastboot or adb, and nothing on the screen)

Update: Fingerprint just works slightly differently, but works OK. Encrypt is the next to tackle.

Update2: So interestingly fingerprint unlock works, but use biometry option is missing from the apps. Is it related the device not being encrypted?

 

[pitfallykmr]

Which gapps do you recommend? I tried NikGapps full but fingerprint unlock seems to be missing, also I couldn't encrypt the phone. It fails to mount userdata on next boot, and causes a bootloop on zygote. Also I have noticed a changed behavior with the new ODM partition, if the charger is connected it comes up on reboot in some factory flashing mode (just reports android in usb descriptor, and there is no fastboot or adb, and nothing on the screen)

You can try Flamegapps.

 

[lubik1]

New build is up!

Changelog:

1) Added Calculator as system app
2) Fixed offline charging and wake up when charging in offline mode
3) Added F5122 variant on download repository

On next build:

1) Fix userdata earlymount (changed to late mount state)
2) Fix for Data Encrypting/Decrypting (same on TWRP)
3) Support EL for Kugo device
4) Support for old TWRP's
5) GPS upgrade

 

[MichaBit]

On next build:
1) Fix userdata earlymount (changed to late mount state)
2) Fix for Data Encrypting/Decrypting (same on TWRP)

What do you think about everyday usage and battery drain?
I ask that because switching from Omnirom 7 to 8, battery sucking was a disaster.

Will this update solve my recovery 3.3.1 error 1 problem?
Twrp 3.4 doesn't work for me, I guess because I bought my device with Android 7 and the bootloader from 8 is required?
Or to put it another way: Will installing stock android 8 first solve my problem?

 

[lubik1]

What do you think about everyday usage and battery drain?

It's not a SODP-based ROM, it's a clean AOSP build. Any another custom ROM on this forum based on SODP or on the Stock fw, thats why it's a unical ROM with low battery consumption (like on a stock 8.0, maybe 5-15% more becouse of Android version and more optimisation by Sony's developers)

Will this update solve my recovery 3.3.1 error 1 problem?

Yep, next update of this ROM will be compatible with old versions of TWRP recovery, becouse Pavel @Cubbins did a trick with symlinking new bootloader location with "ln" command to old bootloader path: /dev/block/bootdevice/by-name.

Twrp 3.4 doesn't work for me, I guess because I bought my device with Android 7 and the bootloader from 8 is required?

Yes you right. For any new ROM (begining from 9 Android) you need new bootloader on your device. It will be automaticaly update if you flash a stock 8.0 ROM with Emma or FlashTool

Or to put it another way: Will installing stock android 8 first solve my problem?

Yes it did.

 

[zaqm]

Hello @lubik1 . Does your rom suffer from the kernel panics that cause the random reboot problems or since it's pure Aosp it doesn't have it?
Thanks for your hard work!

 

[Cubbins]

Hello @lubik1 . Does your rom suffer from the kernel panics that cause the random reboot problems or since it's pure Aosp it doesn't have it?
Thanks for your hard work!

Sometimes you can get kernel panic when you turn on the device. But while using android, I didn't observe kernel panic, but I have not run any stability tests yet, so everything is possible. I'm working on it.