{
"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"
}
What is Project Treble?
Everything is explained here!
What's working:
Boots
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
GPS
RIL
VoLTE
What's not working:
Selinux is permissive
You tell me
Generic System Images:
Here
How to flash:
Use a TWRP with /vendor support
Wipe cache, dalvik-cache, system, vendor and data
Flash the required firmware
Flash the treble_lithium-xxxxxxxx-xxxx.zip
Select "Flash Image"
Flash a Generic System Image in system partition (arm64, A only)
Reboot
Special thanks:
Tranquilitysmile for testing and debugging
XDA:DevDB Information
Project Treble for the Xiaomi Mi Mix
Contributors
Psy_Man
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.8.30
Based On: AOSP
Version Information
Status: Stable
Created 2018-05-01
Last Updated 2018-09-12
Screenshots:
Excellent looking forward to this
Add this line to build prop to enable navbar
Code:
qemu.hw.mainkeys=0
Great job, thanks
02.05.2018 build:
- Forced enable navigation bar (thanks @EvangelineDEV for pointing this out)
- Moved listen_platform_info.xml to /vendor
- Merged changes from LineageOS
Download build
This is awesome!
Thanks Pepsy!!!
Earphone does not work, is it a common problem ?
Great work!
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
doumer said:
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
Click to expand...
Click to collapse
I believe factory reset and wiping system and data are still needed between GSI's... But it should be tried...
Twrp by raupe-lunden.... Find it linked in most oreo roms threads op's I think.
For flashing generic procedure the instructions are linked right here in Psy_Man's OP
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Fusionist said:
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Click to expand...
Click to collapse
I cannot see logcat here. Ignored.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
I still dont know how people want us to solve these problems , if they dont provide logcat we cannot make magic and say OH this is!!!!!!! lol . Thanks Psy_Man for your treble work.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Yup.
I also couldn't boot RR or AOKP... Will try and get logcats from the bootloop and share here a pastebin or the likes.
This treble advances for lithium I believe are awesome and undoubtedly the way to go.
Thanks again Psy_Man.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Fusionist said:
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Click to expand...
Click to collapse
If I recall correctly, running
Code:
adb -d logcat>mylogfile.txt
before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
NLivingstonAP said:
If I recall correctly, running before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
Click to expand...
Click to collapse
Many thanks ! I'll try it again
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
billyliem said:
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
Click to expand...
Click to collapse
You flash the treble compatible and then any GSI out there, that are cooked and usable for any treble enabled device. You don't need an aokp (or any other) cooked specifically for lithium.
Related
Project Treble Guide for Samsung Galaxy A8
{
"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"
}
Just to make it clear I'm not responsible for whatever damage this could possibly cause to your device.
Treble is everywhere, so why shouldn't we join it?
I'm proud to announce that Galaxy A8 [SM-A530F/SM-A530W] will now fully support project treble . Exciting right ?
You just need to follow the instructions mentioned and your device should get Treble ready for future roms.
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
What is Treble?
If you want to know more about that visit here : https://source.android.com/devices/architecture/
Requirements
1) Device SM-A530F or SM-A530W
2) Odin Tool and Samsung Drivers ( If you choose PC method )
Downloads
TWRP 3.3.0
TWRP-3.3.0-jackpotlte-Treble.img
TWRP 3.2.3
TWRP-3.2.3-jackpotlte-Treble.img
TrebleCreator-A530F.zip
TrebleCreator-A530W.zip
**Important: Instructions are absolutely clear, so please carefully follow the steps as written below. You do this on your own risk.
Instructions
1) Boot the device in current TWRP Recovery Mode
2) Wipe system/cache/data
3) Copy the TrebleCreator.zip(of your variant) and TWRP-jackpotlte-Treble.img to your Internal/SDcard
4) Flash the TrebleCreator.zip through TWRP recovery
5) After completing your device will reboot to RECOVERY
6) Now touch INSTALL > Select Image > Locate TWRP-jackpotlte-Treble.img
7) Flash TWRP-jackpotlte-Treble.img to recovery
8) Reboot your device to recovery
9) Once TWRP is booted you first need to Mount > your /system, /vendor, /cache, and /data partition
10) Wipe system, cache, vendor, dalvik cache and data.
Bingo! You have successfully trebelized your A8 (SM-A530F)/(SM-A530W)
Credits:
- @corsicanu for partition Guide
- @somadsul for scripting the guide
- @BlackMesa123 for official TWRP
- @lzzy12 , @Griffin98, @TaifAljaloo for alot of help and contribution
- @saboorTheCool for testing out the recovery
Sources:
Kernel Source Code: https://github.com/prashantpaddune/universal7885
Device Tree (jackpotlte): https://github.com/prashantpaddune/android_device_samsung_jackpotlte
XDA:DevDB Information
Project Treble Guide for the Samsung Galaxy A8 (2018)
Contributors
prashantp01, corsicanu, somadsul
Version Information
Status: Testing
Created 2019-01-29
Last Updated 2019-01-29
reserved
Looking forward for al the good non samsung stuff coming for our device
Has anyone tried it yet? When flashing will it make the vendor (2nd) partition? Can it be reverted if one changes its mind about it?
ECOTV said:
Has anyone tried it yet? When flashing will it make the vendor (2nd) partition? Can it be reverted if one changes its mind about it?
Click to expand...
Click to collapse
Yesterday, I tried, it worked, except that none of the firmware from treble does not start, had to roll back so before all manipulations, do not forget to do a backup
How can we un-trebleize the phone if we want to (for some reason)?
VDavid003 said:
How can we un-trebleize the phone if we want to (for some reason)?
Click to expand...
Click to collapse
try flash firmware from odin, AP, CSC, not HOME_CSC, or just CSC if you're in stock rom and not treble rom
Okay, so anyone trying it: At least for me, the vendor partition is empty, so nothing will really boot unless you make a treble vendor.
Edit: nvm
VDavid003 said:
Okay, so anyone trying it: At least for me, the vendor partition is empty, so nothing will really boot unless you make a treble vendor.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...elopment/rom-project-treble-rom-v1-0-t3895086
flash that rom, that rom has the vendor partition
I'm kinda new to this Treble stuff so don't mind me asking, right now the Project Treble ROM on this subforum is the only one we can install on this device right now or should be able to experiment with more generic ROMs?
OverLineMusic said:
I'm kinda new to this Treble stuff so don't mind me asking, right now the Project Treble ROM on this subforum is the only one we can install on this device right now or should be able to experiment with more generic ROMs?
Click to expand...
Click to collapse
you have to flash that project treble rom on this subforum before flashing any generic ROMs (GSIs) because that rom contains the vendor partition contents
587.saboor said:
you have to flash that project treble rom on this subforum before flashing any generic ROMs (GSIs) because that rom contains the vendor partition contents
Click to expand...
Click to collapse
Thanks for clarifying, just one more thing, how should i check if this device has partition A or A/B? So i can get it clear for the future
OverLineMusic said:
Thanks for clarifying, just one more thing, how should i check if this device has partition A or A/B? So i can get it clear for the future
Click to expand...
Click to collapse
""
A
I had trouble understanding what are GSI rom so I googled it and I found a nice tutorial explaining everything about it:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
After seeing this, I'm more excited about my device than when I first bought it. Installing Lineage OS (aka the new CyanogenMOD) could be as straightforward as flashing a treble-LOS image. Since I use my phone as a "daily driver", I'll just wait until everything has been tested and tried.
Also, can anyone tell me if the Exynos SOC, in the Galaxy A8 is ARM 64A or ARM64A/B?
Nico3d3 said:
I had trouble understanding what are GSI rom so I googled it and I found a nice tutorial explaining everything about it:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
After seeing this, I'm more excited about my device than when I first bought it. Installing Lineage OS (aka the new CyanogenMOD) could be as straightforward as flashing a treble-LOS image. Since I use my phone as a "daily driver", I'll just wait until everything has been tested and tried.
Also, can anyone tell me if the Exynos SOC, in the Galaxy A8 is ARM 64A or ARM64A/B?
Click to expand...
Click to collapse
A
also heres a list of pie GSIs that work and dont for some reason
NOTICE: THE LIST BELOW ONLY SAYS IF IT BOOTS, IT DOESNT MEAN THAT THE GSI IS FULLY BUGLESS
Avoid these GSIs:
ViperOS
Pixel Dust
PixelExperience
Resurrection Remix
HavocOS
Liquid Remix
MIUI
GSIs that work:
Phh-Treble
AOSP Extended
AOSiP
Descendant
Click to expand...
Click to collapse
587.saboor said:
A
also heres a list of pie GSIs that work and dont for some reason
Click to expand...
Click to collapse
Damn you're saving me right now, casually i've been trying for hours all the GSI's that don't work, trying AOSP Extended right now, gonna see if i can finally go to sleep with a ROM booted
OverLineMusic said:
Damn you're saving me right now, casually i've been trying for hours all the GSI's that don't work, trying AOSP Extended right now, gonna see if i can finally go to sleep with a ROM booted
Click to expand...
Click to collapse
lmao thank my fast af wifi
587.saboor said:
lmao thank my fast af wifi
Click to expand...
Click to collapse
Can confirm AOSP Extended has booted just after 8 minutes of installing, gonna stick with this one for a while and try Descendant in a future, i was losing my mind waiting 35 minutes for Pixel Experience to boot and not seeing it pass the G logo
OverLineMusic said:
Can confirm AOSP Extended has booted just after 8 minutes of installing, gonna stick with this one for a while and try Descendant in a future, i was losing my mind waiting 35 minutes for Pixel Experience to boot and not seeing it pass the G logo
Click to expand...
Click to collapse
lmao i recommend AOSiP, it has more features (AOSiP is in A only category of the treble subforum)
OverLineMusic said:
I'm kinda new to this Treble stuff so don't mind me asking, right now the Project Treble ROM on this subforum is the only one we can install on this device right now or should be able to experiment with more generic ROMs?
Click to expand...
Click to collapse
U can flash Non treble roms too....
I'm not responsible for whatever damage this could possibly cause to your device.
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to GSI For Galaxy M20 ONLY FOR M205F/M205G
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
Make sure you install TWRP : https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
If any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide Guide that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
All Sensors
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"
- STEPS FOR INSTALLING GAPPS
Download the appropriate OpenGapps.org
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- FOR INSTALLING FIXES:
Camera Fix (Flash only on NON Working GSIs)
- KNOWN BUGS:
Fingerprint
Bluetooth calls are broken
No Network bars (Calls/data works)
May be more, Let me know
Downloads. F.A.Qs below
XDA:DevDB Information
Guide on How to flash GSI, ROM for the Samsung Galaxy M20
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Current Stable Version: v1
Created 2019-03-05
Last Updated 2019-03-05
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Generic System Image (GSI) : Github
Treble folder : Gdrive
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
amazing.
Awesome Bro. Nic work. Keep it up.
VoLTE is not working
harsinghal said:
VoLTE is not working
Click to expand...
Click to collapse
It will not work on any gsi
It work with m205fn?
kofa01 said:
It work with m205fn?
Click to expand...
Click to collapse
yes, it should work
prashantp01 said:
yes, it should work
Click to expand...
Click to collapse
it doesn't work, in TWRP i pres flash img and chosse system.img GSI but TWRP failed with errot 255...
maybe i doing wrong?
kofa01 said:
it doesn't work, in TWRP i pres flash img and chosse system.img GSI but TWRP failed with errot 255...
maybe i doing wrong?
Click to expand...
Click to collapse
On which gsi?
prashantp01 said:
On which gsi?
Click to expand...
Click to collapse
This is a problem with ROM. I tried to put the Pixel Experience, it started without problems.
But not work NFC.
On which ROM the NFC will work?
kofa01 said:
This is a problem with ROM. I tried to put the Pixel Experience, it started without problems.
But not work NFC.
On which ROM the NFC will work?
Click to expand...
Click to collapse
report it to pixel experience developer, with proper logs
T
This work on sm-m205g ?
isnu harajuku said:
This work on sm-m205g ?
Click to expand...
Click to collapse
yes it should work
AOSP and treble both did not work in the m205f version. It gets stuck in blootloder
My phone is stuck in boot screen after flashing the rom, can someone help me fix this issue? I flashed Phh-Treble 9.0
My phone model No. M205F
lifehacker03 said:
AOSP and treble both did not work in the m205f version. It gets stuck in blootloder
Click to expand...
Click to collapse
your M20 is already a trebled device
rafsun.khan said:
My phone is stuck in boot screen after flashing the rom, can someone help me fix this issue? I flashed Phh-Treble 9.0
My phone model No. M205F
Click to expand...
Click to collapse
take logcats and report to phh-treble developer
prashantp01 said:
take logcats and report to phh-treble developer
Click to expand...
Click to collapse
Any guide to get a logcat when the device is stuck at the android boot logo? Nothing shows up when I "adb devices" from PC.
Thanks but its official update original for m20
I'm mean wait to comes out the originally Android 9...
Or not coming.
Or update This Help me
Did someone sucsessfully install gsi rom on m20 ?
I tryed a couple of roms, allways bootloop
CLOSED PER OP REQUEST
{
"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:
DOWNLOAD Official
DOWNLOAD oos camera
Kernel source:
Source
Selinux Status:
Enforcing
MAJOR BUGS:
VoWifi
flash on your own risk.
FLASHING
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE SUPPORTED by US, But flash what you want)
reboot (if you still have trouble with understanding a/b just repeat whole procedure once again).
If phone doesnt boot format userdata.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
OOS camera work with portrait mode, 60fps, all 3 cams, etc.
Android auto works fine.
If you dont mess with magisk, rom will always pass safety net out of the box.
Device Maintainers
@vache, @darkobas,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: [url]https://github.com/omnirom/[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.5.11
Version Information
Status: Stable
Created 2019-07-19
Last Updated 2019-07-28
reserved
nice!
any plans to support 5g variant?
Nekromantik said:
nice!
any plans to support 5g variant?
Click to expand...
Click to collapse
probably not before q..... even then we would need a experienced tester if we wanted to make things work as no1 in team has a 5g. dunno even what the current issues with it are
group
Is there a telegram group?
Yes! Thank you! Hopefully will have time to flash today.
darkobas said:
probably not before q..... even then we would need a experienced tester if we wanted to make things work as no1 in team has a 5g. dunno even what the current issues with it are
Click to expand...
Click to collapse
The hardware is identical apart from Modem so things like vendor and modem files will be different.
I flashed AOSiP with 5g supported kernel and it boots and camera bluetooth etc works. Just no SIM detected.
Before people ask yes when it boots up it is on 60 fps mode. To change go to settings --> omni gears---> display modes and put it on 3120x1440 90.0000. The 1080p mode seems to break fingerprint and gives you a weird screen off animation.
---------- Post added at 02:39 PM ---------- Previous post was at 02:38 PM ----------
joemossjr said:
Before people ask yes when it boots up it is on 60 fps mode. To change go to settings --> omni gears---> display modes and put it on 3120x1440 90.0000. The 1080p mode seems to break fingerprint and gives you a weird screen off animation.
Click to expand...
Click to collapse
Edit. Also fingerprint seemed to be pretty hard to setup. Had to press pretty hard to get it to recognise. Works fine now.
Rom working well so far! 90hz initially wasn't working but switching to 60hz then back to 90hz fixed it for me. I can't seem to get UnifiedNlp working with MicroG though. I already removed com.qualcomm.location as the NanoDroid wiki says it could conflict, but to no avail. Could it maybe be that the rom doesn't look for com.google.android.gms as a location provider?
gigatex said:
Rom working well so far! 90hz initially wasn't working but switching to 60hz then back to 90hz fixed it for me. I can't seem to get UnifiedNlp working with MicroG though. I already removed com.qualcomm.location as the NanoDroid wiki says it could conflict, but to no avail. Could it maybe be that the rom doesn't look for com.google.android.gms as a location provider?
Click to expand...
Click to collapse
Just dont remove qcom location and location will work fine
Love the ability for custom fingerprint Icons
joemossjr said:
Love the ability for custom fingerprint Icons
Click to expand...
Click to collapse
If anyone's wants some hit me up and I'll see what I can do
joemossjr said:
If anyone's wants some hit me up and I'll see what I can do
Click to expand...
Click to collapse
Could you create a zip of them all and make a theme post for it? Or drop it here since i think this is the only rom right now with custom icon ability.
So if coming from another ROM do we format data boot back to TWRP wipe but don't wipe internal, system are vender then flash ROM bla bla bla done ?
Hunter3U said:
Could you create a zip of them all and make a theme post for it? Or drop it here since i think this is the only rom right now with custom icon ability.
Click to expand...
Click to collapse
You can find some files here : https://t.me/s/OP_fps
Here's a zip of ones I made
I m on 9.5.10 with magisk and unlocked bootloader..what should be flashing method?should I go with method said in op( oos-omni-reboot to b/l-twrp-oos-omni method)or any other method?
punit1708 said:
I m on 9.5.10 with magisk and unlocked bootloader..what should be flashing method?should I go with method said in op( oos-omni-reboot to b/l-twrp-oos-omni method)or any other method?
Click to expand...
Click to collapse
I used the same method as op6 and op7pro in previous roms works perfectly and I formatted data prior and same wipe method as previous roms
joemossjr said:
Here's a zip of ones I made
Click to expand...
Click to collapse
How to use the zip. I am on OOS renovate rom
Edit.. Found it
Dbj.Dhaval said:
How to use the zip. I am on OOS renovate rom
Click to expand...
Click to collapse
Try using same method as you woruld with other real roms not gsi mess search xda read up one post
{
"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 10, 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.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/mermaid
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][mermaid][10] LineageOS 17.1, ROM for the Sony Xperia X10 Plus
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-02-16
Last Updated 2020-04-01
oh btw you might want to use this TWRP for flashing my builds.
Just bootlop
Great performance and smoothness.
reintal said:
Just bootlop
Click to expand...
Click to collapse
Did you format data? If that didn't help, mind sending me a msg on irc?
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev
NFC does not work
reintal said:
NFC does not work
Click to expand...
Click to collapse
Works here? I just tried Android Beam.
LuK1337 said:
Works here? I just tried Android Beam.
Click to expand...
Click to collapse
He works with some issues, sometimes i can't read nfc cards and use android beam. I assume this is an application problem.
LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
easyt said:
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
Click to expand...
Click to collapse
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
I re-flashed the official firmware, and then flash twrp again, it's right!
thank you
Two sim
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
Two sim does not work when an SD card is inserted
Stezko said:
Two sim does not work when an SD card is inserted
Click to expand...
Click to collapse
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
LuK1337 said:
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
Click to expand...
Click to collapse
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
I don't really care whether your english is perfect or not. I just need you to test that for me...
I can't say much about magisk tho, I don't use it.
EDIT: I guess that was too much to ask for... If there's anyone with dsds device who wants to be helpful, please msg me. I would prefer to release something tested rather than hope for the best.
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
Everything works without problems https://imgur.com/a/ij094yH
Camera2api
Hello!
I'm using this build for daily use! I can say it's really smooth and, no issues at all!
My only question is if enabling camera2api is possible, and then install a working version of gcam...
Any help will be appreciated!
I'm also willing to provide feedback and make my mobile a Guinea pig to make this work!:fingers-crossed:
Lineage is running stable with semc addons, Gapps, tai chi, and root with magisk 20.3.
fastboot boot boot.img and reboot to recovery ramdisk worked best.
After failing to successfully root flashing magisk.zip, I got a boot image
from a twrp backup. I renamed boot.emmc.win to boot.img and patched
with Magisk. Flashed the new boot.img, magisk.zip, and had root on startup.
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
aeppacher said:
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
Click to expand...
Click to collapse
Did you even format data?
LuK1337 said:
Did you even format data?
Click to expand...
Click to collapse
Did a full format before installation and then after lineage install. Tried factory reset after gapps installation and tried 3 different dates for gapps in case it was a new bug. Are you suggesting to do an installation, gapps, then full format?
{
"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 10, 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.
Instructions:
Unlock your bootloader
Backup strongly advised, including the "persist" partition
Download the latest build
Reboot bootloader
$ fastboot -w (This wipes your data!)
Download and boot TWRP for instantnoodle Important: Do not flash anything using the built-in recovery for now, it will severely brick your device.
Flash LOS zip
Reboot
Downloads:
https://drive.google.com/drive/folders/1BGTV9LD_PLAR5p0o3fUdKqR3IWxUGJPV
Known issues:
Weak vibrator
Displays "Charging slowly" when it's actually not
Flashing anything using built-in recovery bricks the device, factory reset and wipe should be safe though
Probably loads of untested things
Build signed with public keys for now
GApps not flashable yet
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][10] LineageOS 17.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Device Tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle + https://github.com/luk1337/android_device_oneplus_sm8250-common
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Most of the work just consisted in adapting LuK1337's fantastic work on the OP8 Pro (instantnoodlep), all credits should actually go to him.
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-07-11
Last Updated 2020-07-11
Noice! ?
Awesome, so glad to see ROMs development starting up for this phone!
I retract my post. Thank you.
---------- Post added at 08:22 PM ---------- Previous post was at 07:40 PM ----------
I can't flash any custom rom. For some reason it just won't flash it. Always get a generic error code. Tis frustrating. I'm not sure what to do about it. I really wanted to try this too.
same. got it to flash via the fastboot method from Luks post in the 8 pro but it reboots as soon as it boots.
gerguter said:
I retract my post. Thank you.
---------- Post added at 08:22 PM ---------- Previous post was at 07:40 PM ----------
I can't flash any custom rom. For some reason it just won't flash it. Always get a generic error code. Tis frustrating. I'm not sure what to do about it. I really wanted to try this too.
Click to expand...
Click to collapse
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
joemossjr said:
same. got it to flash via the fastboot method from Luks post in the 8 pro but it reboots as soon as it boots.
Click to expand...
Click to collapse
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
KennyG9 said:
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
Click to expand...
Click to collapse
It just says that it can't flash the zip. Nothing else. I'll try again later and see what happens.
gerguter said:
It just says that it can't flash the zip. Nothing else. I'll try again later and see what happens.
Click to expand...
Click to collapse
While you're at it, have a look at what "/tmp/recovery.log" says after trying to flash.
No windows mobile 8? lol
KennyG9 said:
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
Click to expand...
Click to collapse
sorry what i mean is. I extracted the payload.bin then saw luks page on the 8pro and took the commands he did to flash the rom and applied them here. The rom infact boots but as soon as i see the welcome screen it pops up a screen that says shutting down. also i was able to get past that once by formatting in los recovery. but after that it was a no go. Cant get gapps to flash so couldnt get that. Magisk did flash tho and seemed to work? Other then those things I would just make images for flashing in fastboot instead of zips. twrp is super borked lmao
KennyG9 said:
While you're at it, have a look at what "/tmp/recovery.log" says after trying to flash.
Click to expand...
Click to collapse
Will do.
i can flash and use it just fine no problem at all only NO GMS and i can't install it because error 70 not sufficient partition space please fix it
Is there any group for testing and reporting bugs?
Thank you for your good work! By the way, do you know how to change the screen refresh rate to 90hz on LineageOS? I'm stuck at 60hz now
Is a kernel required to flash this? I can't get this rom to flash in twrp or to work by flashing the extracted payload files
Any news on being able to flash google play?
gerguter, can you update us? currently experiencing the same issue and unsure of how to get around it.
Any telegram channel for op8 los ROM?
Any updates? Last build is still dated from July.
TheCybrid said:
Any updates? Last build is still dated from July.
Click to expand...
Click to collapse
The one for the op8 pro works on the op8 but the fingerprint sensor is in the wrong spot on the screen but if you don't mind that it works fine.