Database Info

[Recovery][Unofficial] TWRP 3.0.2-C [r7plusf]

This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full Source: Github.​Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.

...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.

Major Props ! Great job and you actually fulfilled a request of mine ! Thanks

I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?

midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.

It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks

Small update - read OP.

teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.

celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis

teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.

celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well

teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?

celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.

Is there any chance that this would be updated.?

kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.

x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........

celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?

kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
​
Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​
​
XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[10] LineageOS 17.1 for z3c

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04

OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!

I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/

hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out

NIce, thank you

hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/

NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/

hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.

NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation

Can this ROM be installed on top of LineageOS 16 without wape?

Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...

NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy

hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)

Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse

@NeoArian Any chance for a screen recording of how it runs?

JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.

[ROM][UNOFFICIAL][matisse][millet] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Installation instructions :
Be sure to have installed latest TWRP recovery (you can find it in downloads) and latest Android Lollipop (5.0.2 for matisse, 5.1.1 for millet) firmware
Download the latest build and GApps (ARM, 9.0, I advice pico package) - if you'll go to wipe even internal storage, put them on a microSD or an USB OTG, or copy them after wiping it
Boot to recovery mode
Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. When it finishes, go to home page
Install > select ROM zip file > swipe to flash and, when it finished, go to home page
Do the same thing to flash GApps
Reboot > System
Update instructions :
Be sure to have installed latest TWRP build
Download the latest build
Boot to recovery mode
Install > select ROM zip file > swipe to flash and, when it finished, go to home page
Reboot > System
Known issues :
Magnetic cover doesn't trigger magnetic sensor (it works, but it's too little sensible).
Some randomic minor issues with YouTube app (sometimes, after skipping ads in a video, you'll get just a grey screen - close and reopen video to fix the issue)
Some randomic issues with bluetooth MAC address (bluetooth app crashes always). To fix this, you need to get (take note!) the address by going to stock ROM and getting that from Settings > About tablet menu. Then, come back to LineageOS 16 and rewrite the file /efs/bluetooth/bt_addr by using root permissions and a root file explorer, or by using adb push/pull, better in TWRP.
In all millet, camera crashes when trying to take pictures and can't zoom
5 GHz WiFi networks between channels 149 and 161 are invisible to the Tab
In matisse3g and millet3g SIM isn't working
Downloads :
All models (from 2022-12 build): https://github.com/matteo0026/OTA/releases
Mirror for all models: https://t.me/tab4los
matisse (10.1) devices (until 2022-09 build): https://androidfilehost.com/?w=files&flid=304073
millet (8.0) devices (until 2022-09 build): https://androidfilehost.com/?w=files&flid=304074
TWRP recovery: https://forum.xda-developers.com/tab-4/development/recovery-twrp-recovery-matisse-millet-t4019831
GApps: https://opengapps.org/ (ARM, 9.0, I advice pico package)
Contributors
matteo0026, DJABHipHop, Alastor89, All the S3NEO devs that provided the base for developing Pie on Tab 4
Source Code:
https://github.com/lineageos for samsung msm8226 common device and kernel source, with some patches coming from Gerrit for device source
https://github.com/s3neo for matisse and millet and specific variants device and vendor source

Failed to flash
Hi I am running into an issue flashing your rom in recovery. I have TWRP 3.0 flashed and when I flash your rom I get the following error:
E: unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file /sdcard/lineage-16.0.20200108-UNOFFICIAL-milletwifi.zip
I have redownloaded the rom multiple times to verify that the zip isn't broken. I am flashing it on a SM-T230NU that is rooted as well.

Flash latest TWRP
---------- Post added at 08:14 AM ---------- Previous post was at 07:38 AM ----------
judgemstr said:
Hi I am running into an issue flashing your rom in recovery. I have TWRP 3.0 flashed and when I flash your rom I get the following error:
E: unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file /sdcard/lineage-16.0.20200108-UNOFFICIAL-milletwifi.zip
I have redownloaded the rom multiple times to verify that the zip isn't broken. I am flashing it on a SM-T230NU that is rooted as well.
Click to expand...
Click to collapse
But your device is neither millet (t33* series) or matisse (t53* series) so it is not compatible

SM-T335 / Tab4 8.0 LTE / milletlte
Thanks a lot for the ROM! 1st was trying to get the LightningFastRom running but ended up in a bootloop to recovery with the Lineage 16 versions.
Then got to the Telegram channels and saw there that you opened that thread @xda here and gave it a shot.
After a clean install I am really happy especially because the phone part works!
Not tested Skype yet and Camera is not really the burner anyways
Even so, any idea if there is a working Google Camera Mod available?
One thing I figured out: the tablet does not go to sleep/shuts down the display anymore if I close my cover (magnetic one). Any idea how to solve that?
Again thank you very much!!!

Everytime I try to install it with gapps I get a booloop in T530. I'm flashing ARM 9.0 Nano, is this correct?
Edit: NVM, just took longer to boot. Working flawlessly.

Nice dude!
Wow even though the tablet is old you actually made it happen! My tablet is now pretty useless so i can test this for you Good job dude

Great work first off...
I have reflashed a number of times:
1. os, 2. reboot to recovery, 3. flash gapps, 4a. flash su enabler for lineageOS (was not compiled with ‘export WITH_SU=true’) or 4b. even magisk.
Reboot, setup - enable root for apps/adb via developers tools. Works : but something stops it from going forward and 'sticking' then the app reverts to non-SU state and says Root not available.
I have searched, I have found little on this... any help would be appreciated. If there is an 'easy' way then great but many things are not ever so easy.
Thanks in advance...
*Edit*
It has something to do with more than just the ROM or flashing, on any 7.1.1 it is the same... not sure where to go from here.
SU can be installed and openly visible, even works for seconds and then KNOX? or Some other protection brings it back to unavailable.
**Final Edit**
Sorry everybody, I have not rooted since Gingerbread... I was getting rusty.
All is good, I only needed to mount /system as RW to copy my hosts file into place. I feel a bit silly.
@matteo0026:
Really great work, this tablet is doing GREAT with your ROM and TWRP. Thank you for taking the initiative!
Keep up the Community Love!

Thank you very much for supporting 6 years old devices... Please keep your work.

Has anyone had a problem with the milletlte/tmoT337T or T335 going directly into safemode after installation. It happened to me on LOS 14, 16 and the latest 20200110 build.
Thanks.

how do media apps work on the rom.any issues.also do plan on using the rom on the device as i have no longer bought tablets in a while.most of these devices have been phone as they have better performance then the mid ranged priced tablets.

donj001 said:
Has anyone had a problem with the milletlte/tmoT337T or T335 going directly into safemode after installation. It happened to me on LOS 14, 16 and the latest 20200110 build.
Thanks.
Click to expand...
Click to collapse
Are you sure that you installed latest firmware before installing this ROM?
mrk2815 said:
how do media apps work on the rom.any issues.also do plan on using the rom on the device as i have no longer bought tablets in a while.most of these devices have been phone as they have better performance then the mid ranged priced tablets.
Click to expand...
Click to collapse
What do you mean by media apps? Make practical examples, please.
Anyway, I'm going to build and upload new builds with security patches updated to February 2020. So, new builds start from today, 21st February. I can't build and upload all the builds fast because I'm using a medium-range laptop and an ADSL connection at 1 Mbps in upload.

matteo0026 said:
Are you sure that you installed latest firmware before installing this ROM?[/QUOTE
I'm on the last 5.1.1 that TMobile released for that Tab 4. But I'm glad for the response and I'll give the new builds a try. Thank you.
Click to expand...
Click to collapse

donj001 said:
matteo0026 said:
Are you sure that you installed latest firmware before installing this ROM?
Click to expand...
Click to collapse
I'm on the last 5.1.1 that TMobile released for that Tab 4. But I'm glad for the response and I'll give the new builds a try. Thank you.
Click to expand...
Click to collapse
Oh now I saw that I forgot to build and upload the version for milletltetmo! Sorry! When it'll be uploaded, I'll tell you.

* Last firmware update 12/2016
* TWRP milletltetmo image
* Magisk v20
* Full wipe
* No errors on install
Flashed the latest 16 build.
Bootloops every time.
Could not get logcat
I am very happy to test the ltetmo builds. I'm not sure anyone but me is using it.
Thanks

matteo0026, thanks for build these roms for tab4 tablet.i have another tablet which devs don't even want to develop for which is stuck on android 7.1.2.at least the tab 4 has multi development love even though both tablets are from the same time frame of 2014. a tab 4 which i got from a family member and plan on using it asa good tablet .wwill you anounce hwen you have new builds here.thanks again. the media apps that i was talking about playing wer netflix, youtube and apps like that . i know that apps like tune in , and i heart radio fm usa will probably work for streaming audio i was jsut asking about video playback. .

any plans to keep teh project going with monthly security updates or maybe think about a lineage 17.1 build to android 10 for the devices.just wondering. i have flashed and kept alot of devices alive through either official or unofficial builds of cm 12-14, to lineage 14.1 to 16.0 from all the way from samsung galaxy s2 to all the way up to nexus 6p and pixel XL. so i dont mind doing the work and learning. .

mrk2815 said:
matteo0026, thanks for build these roms for tab4 tablet.i have another tablet which devs don't even want to develop for which is stuck on android 7.1.2.at least the tab 4 has multi development love even though both tablets are from the same time frame of 2014. a tab 4 which i got from a family member and plan on using it asa good tablet .wwill you anounce hwen you have new builds here.thanks again. the media apps that i was talking about playing wer netflix, youtube and apps like that . i know that apps like tune in , and i heart radio fm usa will probably work for streaming audio i was jsut asking about video playback. .
Click to expand...
Click to collapse
Don't do 2 messages. We are in a forum, so you have all the time to edit the old post.
Anyway, I don't think Netflix works, as other feedbacks told me (app can't be found on play store because of problems with safetynet I guess), but YouTube yes, of course.
mrk2815 said:
any plans to keep teh project going with monthly security updates or maybe think about a lineage 17.1 build to android 10 for the devices.just wondering. i have flashed and kept alot of devices alive through either official or unofficial builds of cm 12-14, to lineage 14.1 to 16.0 from all the way from samsung galaxy s2 to all the way up to nexus 6p and pixel XL. so i dont mind doing the work and learning. .
Click to expand...
Click to collapse
I'll keep this build with security patches. Unfortunately, I haven't a good computer to build them and a good Internet connection to upload them, but I'll try to do all I can do.
Lineage 17.1 is already on the way (look at the LightningFastRom 17.1 by DJabHipHop), but it isn't as stable as lineage 16.0. Another thing is that I have a matissewifi, but I can't use it because the mobo is broken and probably requires a work of microsoldering. So, I can't test personally the builds...

Hi,
I´ve installed this rom on my Tab 4 10.1 wifi a few days ago and I´m really impressed. Thank you for your great work!
The rom is working smooth and stable in general. But there´s a problem with the Xiaomi Home app. I'm using this app to control my Roborock S5. Starting the app works fine. It´s even possible to log in or create a Xiaomi Account etc. But when I try to open the control panel of the Roborock S5, the whole system crashes while the app is downloading the map from the Roborock S5. The system reboots completely without any warning. This happens every time at the same moment. On other devices (Tablets, Phones) the app works without any problems. I had the same issue with another app that´s installed on the Tab 4 but it only happened once. I think, there´s some kind of a bug in the system. Is it possible to find and fix it?
As far as I can tell, everything else (accept the dark rear camera) is working fine.
EDIT: My Roborock S5 got an firmware update yesterday and now the app/Tab 4 doesn´t crash anymore.

heres my question with this one.do you have to format internal storage to decrypt as i dont know if theis device is encrypted. Before wiping and installing rom and gaps.just wondering as i had to do that to another device in order to install the rom an dnot to have twrp pass word screen come up an for the lineage rom to boot to lineage set up screen. jus want the exact steps so tha icna havea correct installation. as i am only going to do this once to this device.
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
here's my question.with the installation of the rom. do you have to format internal storage an then wipe and install rom and gapps . what is the exact correct process that i need toperform to have a correct installation of the rom.i cant provide development but i can provide testing of your builds.

mrk2815 said:
heres my question with this one.do you have to format internal storage to decrypt as i dont know if theis device is encrypted. Before wiping and installing rom and gaps.just wondering as i had to do that to another device in order to install the rom an dnot to have twrp pass word screen come up an for the lineage rom to boot to lineage set up screen. jus want the exact steps so tha icna havea correct installation. as i am only going to do this once to this device.
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
here's my question.with the installation of the rom. do you have to format internal storage an then wipe and install rom and gapps . what is the exact correct process that i need toperform to have a correct installation of the rom.i cant provide development but i can provide testing of your builds.
Click to expand...
Click to collapse
Encryption isn't supported in my build of TWRP, so don't try to do that with LineageOS.

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

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
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
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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz

So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.

mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now

lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !

[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo

Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.

Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"

Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/

I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.

mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?

@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.

@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse

&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.

betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.

@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?

Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.

betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD

Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build