I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- video record
Links
1. 20200229: initial build: https://drive.google.com/file/d/1_JE8xGHpAqd9JQ-Trd4p3TazqLGWZ83k/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Official version is too old and will not work with latest lineage builds (theoretically you can remove first 2 lines from "\META-INF\com\google\android\updater-script" and install using official). I made repack of more fresh twrp recovery. Only one problem here: after turn-off screen, it cannt turn-on again. Hold volume up + power + home combination untill you back to recovery. Or you can in recovery in settings disable screen timeout.
for recovery: https://drive.google.com/file/d/1eIrN8byqXx5qSfQ2iXTVXbTKSe11eWM5/view?usp=sharing
for odin: https://drive.google.com/file/d/1uezAZWPp9G5EIiuQZYveZY8465UYCBKw/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte
Thanks
Thanks to LineageOS team
Just updated from lineage-13.0-20190417. Everything I use daily seems to work. (I don't use phone/LTE, BT or Camera). Extra bonus: The capacitive buttons lit up for the first time in years.
The only issue I've found so far is that auto-rotate sometimes stops working.
Huge thanks to @Valera1978 for keeping our device alive!
deleted
Awesome. Is there a way, to get this on t520 too?
Gesendet von meinem SM-T520 mit Tapatalk
ChilliBo said:
Awesome. Is there a way, to get this on t520 too?
Click to expand...
Click to collapse
Not very likely. T320, T325 and T525 have Qualcomm Snapdragon SoC's inside, so most of the codebase can be shared between them. T520 has Exynos which is a totally different beast.
And, yes, it's a brilliant ROM. Been my daily driver since my first post to this thread despite the problems with auto-rotation. I'm using the "Rotation Control" app, which makes it just a minor annoyance.
Unbelievable! Thank you very very much! Everything works. Feels like a new tablet!
Are you also working on Android 10?
Thanks a lot for this ROM!!! I just have a problem with Skype: in every call the other person doesn`t hear me. Sound recording - however - works. What can I do?
elcampesino said:
Skype: in every call the other person doesn`t hear me. Sound recording - however - works. What can I do?
Click to expand...
Click to collapse
This fix posted in the LOS16 for T320/T325 thread might work:
https://forum.xda-developers.com/showpost.php?p=82325901&postcount=176
M0lle said:
This fix posted in the LOS16 for T320/T325 thread might work:
https://forum.xda-developers.com/showpost.php?p=82325901&postcount=176
Click to expand...
Click to collapse
Thanks for your hint. Unfortunately, it didnt work for me. However the reason might be, that I am really a beginner on LineageOS and patching Android devices.
I copied the file (mixer_paths.xml) and edited the build.prop with "build.prob.editor".
Result is, that there is no sound at all any more, what remains even after restoring the old data.
Can someone help me?
deleted
elcampesino said:
Thanks for your hint. Unfortunately, it didnt work for me. However the reason might be, that I am really a beginner on LineageOS and patching Android devices.
I copied the file (mixer_paths.xml) and edited the build.prop with "build.prob.editor".
Result is, that there is no sound at all any more, what remains even after restoring the old data.
Can someone help me?
Click to expand...
Click to collapse
Ok, I managed to fix it.
Just change in /system/build.prop the value from vendor.dedicated.device.for.voip=true
to vendor.dedicated.device.for.voip=false.
And then Skype works with microphone!
Best regards!
Installed today, works like a charm, even SD card is detected on startup.
Thank you for giving my 3 devices (T320, T325, T525) a new life!
elcampesino said:
Ok, I managed to fix it.
Just change in /system/build.prop the value from vendor.dedicated.device.for.voip=true
to vendor.dedicated.device.for.voip=false.
And then Skype works with microphone!
Best regards!
Click to expand...
Click to collapse
this advice helped. thank you author
[email protected] said:
this advice helped. thank you author
Click to expand...
Click to collapse
Does someone use mobile Internet on this firmware? For unknown reasons, the sim card is lost. On the drain this was not. helps (not always) switching to airplane mode and subsequent reboot
deleted
Thank you for this ROM. It's quite stable.
However, auto rotation is not always working.
Looking forward to the Android 10 ROM for T525 ?
Abb4d0n said:
However, auto rotation is not always working.
Click to expand...
Click to collapse
That's the only small issue I have with this ROM. With Rotation Control, though, it's more than manageable.
Hi
I have a T525 which was running android 4.4 . I am a newbie and manage to change the TWRP and install the above version of LineageOS however I am struggling to find a version of GApps that works. Can anyone point me in the right direction.
Thanks
Rob
rob46 said:
I am struggling to find a version of GApps that works.
Click to expand...
Click to collapse
Open GApps Pico has worked very well for me with both 16.0 and 17.1.
Platform: ARM
Android: 9.0
Variant: Pico
Nano should be ok as well. Just avoid any variant which installs the Pixel Launcher. I had huge problems with it when I initially flashed Stock GApps with 16.0. Since then I've gone with Pico with zero problems.
P.S. Why would you want to install 16.0 when 17.1 is available with frequent (= monthly) updates? I'm fairly sure @Valera1978 won't be pushing out another version of 16.0. The latest available version is from February.
I have a question, it's more convenient install this build or the android q build? which one of theese will be much supported?
Related
As was my plan all along, kltevzw official support for AOSP roms is picking up. Please see this thread for official downloads and support:
http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
My builds will cease.
-- Begin copy-pasta template from my CM13.0 build thread... please let me know if I miss updating something --
Note: I don't run this ROM personally, I really just built it. It shouldn't, but it may eat your cat.
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your
phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: When/how often are these built?
A: Less often than my CM13.0 build, but at least every week. Unlike my CM13.0 build, I don't use this ROM so I won't be doing a "does it boot" check before uploading. Please tell the entire thread if one day's build doesn't work properly.
Q: Can I get help with something?
A: I have a full-time job and travel a lot. I'll try to jump in and answer some questions, but there is a lot of info out there for you to learn on your own. Aside from you having a vzw-variant, most of the details are standard KLTE. Please see the normal Resurrection Remix KLTE thread for standard ROM help.
Click to expand...
Click to collapse
Recovery:
The standard KLTE TWRP 3.1.0-0 should mostly work, but MTP doesn't work for any klte* variant using it.
I prefer KToonsez's 2.8.6-based Recovery. It's older, but MTP works.
There are Unofficial 3.*.0-* recoveries available by @jcadduono. I find that these don't support decryption properly, which I find to be mandatory.
Like many other devices, the .zip files can be flashed in a recovery. The .tar.md5 files can be flashed in ODIN. The .img files can be flashed using Flashify, a TWRP recovery. You can even get an .img file from a .zip or .tar.md5 if you just open it up.
If you use adopted storage then things get odd. The latest recovery by @jcadduono MAY support adopted storage if you don't encrypt userdata (I personally know that TWRP handles adopted storage for jflte and d2), but I do use encryption so I don't use that recovery. It may be that you only see /data/media/0 -- if so, I find that using Flashify for each nightly is the most straightforward way to update, but you could always manually copy to /data/media/0 before rebooting to recovery. This is a standard Marshmallow and TWRP thing.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. Please note that some have reported that you cannot flash these after the aboot unlock; If you cannot flash the PB1 modem/non-hlos it shouldn't cause any big problems.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
Resurrection Remix recommends SlimGapps or OpenGapps. See their thread for discussion of pros/cons and what those users tend to use. If you use OpenGapps, make sure to use an 6.0 version for ARM architecture.
OpenGapps
SlimGapps
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
I'll build at least once per week, at least until the RR team picks up the torch. Once the build is complete, I upload it to my AFH account.
ResurrectionRemix-M v5.6.X KLTEVZW weekly-ish
Click to expand...
Click to collapse
Does/Doesn't Work:
Everyone that gives it a shot needs to let the thread know. See the Unified Resurrection Remix thread for discussion of what generally does/doesn't work with the ROM.
forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
Click to expand...
Click to collapse
Thanks:
Everyone on the Resurrection Remix and CM teams. This is 99% of their stuff with just a couple tweaks to make it build, (hopefully) boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r22 (prior to 20160406 build)
Android Version: 6.0.1_r24 (20160406-present build)
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
In order of importance:
Resurrection Remix github: https://github.com/ResurrectionRemix
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
tbclandot said:
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
Click to expand...
Click to collapse
Someone needs to be the guinea pig. I know how much a pain it can be setting a ROM up from a clean install, but if CM feels just a bit too vanilla then I'd say jump into the pool.
Alright going to download and flash it now and I will report back to you thanks for your hard work!
---------- Post added at 01:06 AM ---------- Previous post was at 12:35 AM ----------
Hagg flashed the rom and everything seems to be working so far I can make calls and receive texts I prefer RR to CM13 for the features! Just wish there was a way to get my Gear S to connect to non Touchwiz roms but oh well I'll just use it as a regular watch or maybe get an AW watch lol
Running CM13, what's different?
Hmmm extra features to be honest I like CM13 but it's so boring and as a guy that actually likes Touchwiz RR is nice because of the added customization!
So I've for RR installed. Few things I noticed right away: Built in ad-away, nice! Uses super-su. I personally have no issue with the built in root, but whatever. Other than that, it's very close to CM13 in terms of speed and look/feel.
Edit: One weird glitch I've run into on both this and CM13 is that the camera app gives and error "gallery has stopped working" when launched from the icon. If i used the double power button though, then the icon starts working. Any ideas?
Edit2 : It seems to be the default camera icon that is on the home screen in both ROMS. I noticed the graphic is slightly different from the dock as it is in the app window. Deleted bad icon and replaced with app windows one and it works fine. Probably an easy fix!
No glitches, no forced closes. Everything works, and works smooth. Very nice. My new daily driver.
Unlocked and loaded RR with OpenGApps..
No issues...running great!!
Thanks!!
Will try later, thanks haggertk for your work...
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
drewcu said:
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
Click to expand...
Click to collapse
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
tbclandot said:
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
Click to expand...
Click to collapse
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
drewcu said:
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
Click to expand...
Click to collapse
No idea on the speaker as I don't mess with it usually use headphones and I don't really use T backup but I don't see why you should have problems but you'll probably want to clean wipe when installing
drewcu
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
Not that i notice
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
6.01
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
Work great
4) Does Xposed work?
Yes
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
I advice to flash PB1 firmware no botloader
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
Yes, system, data, cache and dalvik, but dont restore system apps nor system settings
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
Dont know
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
At this time not yet
Every time I attempt to download, it fails after 55kb.....
amaury48 said:
Every time I attempt to download, it fails after 55kb.....
Click to expand...
Click to collapse
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
haggertk said:
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
Click to expand...
Click to collapse
Finally got it by switching browsers.....
Would one of you on RR be so kind as to send me the mixer_paths.xml (if that's what it's still called in MM) in your System > Etc folder (assuming folder structure is the same in MM also)? I would like to compare it to the surround sound modded file I installed in KK as per the following link: http://www.naldotech.com/enable-stereo-surround-sound-speakers-galaxy-s5. I am probably not technically capable of making the same thing possible in MM with the S5 front speaker, but it's entirely possible the same modded file I have will work in MM and it's possible a comparison will reveal only a few lines of code to modify that I could do.
Thanks in advance!
XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. No USB tethering
2. Wifi sometimes fails to turn on
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.1
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][O][8.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2018-01-14
Last Updated 2018-11-03
Awesome!! Thank you very much, I'll be trying this out immediately!
oshmoun said:
XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
Click to expand...
Click to collapse
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
@oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
levone1 said:
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
@oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
Click to expand...
Click to collapse
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
I can register new fingerprints, but i cant use them to unlock my phone or to login on apps.
I installed TWRP https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
OmniROM work greatly on my device, I'm using since 14 Jan without any problem! Really Thanks!
coderex96 said:
I installed TWRP https://forum.xda-developers.com/x-...ecovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
Click to expand...
Click to collapse
Here only. With logs if possible.
farfetch said:
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Click to expand...
Click to collapse
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
levone1 said:
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
Click to expand...
Click to collapse
seems to be caused by installing afwall? could you please try without it?
oshmoun said:
seems to be caused by installing afwall? could you please try without it?
Click to expand...
Click to collapse
I am testing now. I haven't checked it enough to saying it's a rom issue; just wondering if anyone else has had it. It worked find with AfWall yesterday, but now in and out. I remember the same issue with AfWall on certain CM 12 roms...
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
OpenDelta
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
edit: forgot to mention I of course also had to update gapps to an 8.1 supporting version. I downloaded an unofficial pico opengapps from here
drstefankrank said:
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
Click to expand...
Click to collapse
cds0 said:
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
Click to expand...
Click to collapse
harryharryharry said:
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
Click to expand...
Click to collapse
Good to know flashing the odm image helps when updating from 7.1
About opendelta, i don't have much control over it to filter out the 8.1 build. It's all done automatically.
Besides, it did do its job well. It notified about the new version.
The requirement to flash a seperate ODM image is similar to how it's needed to flash a vendor image, and not just system and boot images, on Google devices. Guess that's new for Sony devices, hence this confusion.
@oshmoun - how about kcal support? Here's my tests with kppd - https://forum.xda-developers.com/showpost.php?p=75200267&postcount=64 (and forward)
@oshmoun: Yeah I was kind of surprised to see 8.1 was available through opendelta, and I didn't think it would work. So I backed up everything before upgrading. Which is probably what people should do before upgrading anyway
Flashing the oem partition was a relatively easy fix, so it's all good.
Thanks again for your great work! It's much appreciated as the number of custom roms for kugo is really slim pickings.
Latest stock ftf compatible is 34.3.A.0.252, right?
EDIT: It seems so. Flashed it and this build works great with it, so far.
I've performed a clean install after full wipe and also don't have mobile data working. Wi-Fi works, though.
Strange issue I have is the lack of sound over bluetooth ONLY in calls. Playing music/video works otherwise. It's quite baffling. This was working as expected on 7.1.
XC/KUGO/F5321 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device crashes and reboots (mostly happens on demanding tasks)
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-06-16
Last Updated 2019-06-16
so are the micro lags fixed or still happening? there were slow downs and microlags on on games like clash royale etc... not as smooth as stock
This is excellent news! For those of us coming from 8.1 should we dirty flash (along with dsp-label-fixer) or is full data wipe required?
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Bluestar01 said:
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Click to expand...
Click to collapse
yes
official builds are signed and hence not really compatible with homemade
oshmoun said:
yes
official builds are signed and hence not really compatible with homemade
Click to expand...
Click to collapse
thank you, clean flash and is working
Great work! thanks for taking time to upgrade this ROM to Pie.
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
EDIT: GPS works
EDIT 2: GPS has a mind of its own and will not work except for the time when it does, currently investigating (probably something wrong with my phone)
ardylemon said:
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
Click to expand...
Click to collapse
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
droncheg said:
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
Click to expand...
Click to collapse
Thank you, I also got it to work after waiting a while, enabling mobile data as well as derping around with A-GPS settings in the process appears to have worked (not sure which, though). For future reference, my phone locked in after detecting at least 8 satellites with ~20% signal.
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
I've not this problem, for me all is working well and smooth (the only problem is quickswitch magisk module not working).
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
The Unofficial version of OmniROM by HarryHarryHarry had a similar issue, the fix was to first flash the latest stock ftf image (ends with .118), flash twrp and do a clean install of the rom. I would think this fix is going to work for this version too.
I'm currently running the Omnirom 8.1, and I just got a pushed message from OpenDelta on the phone itself:
Update ready to download
omni-9-20190616-kugo-WEEKLY
Click to expand...
Click to collapse
Can I update to Omnirom 9 from the phone itself by running that? Or must I download the rom on my computer and install it the normal way?
Great I will try this very soon!
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
In regards to the device crashing/rebooting issue. Does underclocking help at all?
lapucelle2 said:
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
Click to expand...
Click to collapse
Did that work? I've got the same issue
After updating to the latest weekly today, some apps got uninstalled again. I dad this behaviour also with the test builds before.
can't find stock rom yet i gave up upgrade to 9.0
Mietjelan said:
Did that work? I've got the same issue
Click to expand...
Click to collapse
can't find stock rom yet i gave up upgrade to 9.0
lapucelle2 said:
can't find stock rom yet i gave up upgrade to 9.0
Click to expand...
Click to collapse
I can't find how to install it either, all that flashtool crap isn't working...
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)
Hello everyone,
I am creating this post because I would like to know if someone has already installed Ressurection Remix on a Galaxy A8 ?
I saw some tutorials that are explaining this is possible,but when I go to the Ressurection Remix official download page, I cannot find which file is specific to the galaxy A8. Actually, I have some difficulties to understand the files names : Raphael, Sakura, Jason,... Are theses names code names for différents phones ?
I may add that the bootloader of my phone is unlocked, and I am using TWRP to flash zip files.
I didn't treblelize my phone thought.
If you have some other custom rom suggestions, please do not hesitate to advise me.
You can install RR through GSI, by this link
You will have to trebelize your device
Because it's a gsi android 10, you can use vendor quack
Treble Guide
Vendor Quack
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse
Treblizing the phone itself does not cause any problem rather it enables you to install different GSIs. Regarding GSIs, each have there own bugs and you have to find them on the GSI thread if available or if they have telegram or github support.
Hey, just made an account to respond to this as I just discovered there are per-device pages on these forums and saw this post, I have done exactly that and been running it for 2+ years now, so far I have had no majour problems wih it, the only majour caviat is that after trebblimg it and installing resurrection remix It seems to freeze when trying to display the charging animation if the phone is off and it plugged in, it still charges without any problems, tho to boot it when in this situation you need to force shut it down using the volume_down + lock buttons and then immidiately after use volume_up + lock buttons to boot into recovery, then you can boot to the normal system from there, I have a TWRP recovery but I think the stock one also allows to resume booting the normal system.
In these last months I had a few weird bugs like the screen brightness beeing locked to automatic but that went away after a reboot and only happened 1 time.
I also installed magisk and a few other small tweaks and things and everything works great, also all resurrection remix customization options.
Actually in the last few months something broke because the safetynet checks fail for the ctsProfile, (most apps like my banking app tho still work fine by using magisk hide (i think it's because the safetynet basicIntegrity check still succeds) and the update page seems also broken (tho no idea about when this broke exactly as I haven't checked it in years), everything else is still fine tho, I might try re-flashing it to update to the new majour resurrection remix when i have time and the will to backup and move everything, something could have corrupted or maybe an update broke it, no idea.
My phone reports resurrection remix 7.0.2 and Android 9.
Hope this is still helpful.
Quentief said:
Thanks for your reply. Yes I saw that it was possible to treblelize the phone, to install other rom like the very famous lineage os.
But I am little bit hesitant about this procedure : is everything working well with the phone after a treblelization ? Has anyone tried this method?
Click to expand...
Click to collapse