Builds of LineageOS 13.0/14.1 kernel and TWRP recovery for fame (Lumia 520/1), glee (Lumia 525/6) and zeal (Lumia 720) devices, with support for third-party (unofficial) touchscreens.
This may or may not fix your touchscreen, give it a try and let me know the result.
Glee and zeal builds weren't tested. If they have any problem, please tell me.
Download TWRP Recovery:
Fame: https://drive.google.com/file/d/11q4yTy5bBt_eRvwAZRB3dxtPMHsKaQeO/view?usp=share_link
Glee: https://drive.google.com/file/d/1ecAx1NJrkczAu9oVPi2oUPRkduMI_gej/view?usp=share_link
Zeal: https://drive.google.com/file/d/16iACHry2fGHml0RBjYrcvDzfns8rbuDe/view?usp=share_link
Flash the recovery in fastboot with
fastboot flash recovery <file.img>
Click to expand...
Click to collapse
(Replace <file.img> with the recovery you downloaded)
Download kernel:
Fame: Kernel for LOS 14.1 | Kernel for LOS 13.0
Glee: Kernel for LOS 14.1 | Kernel for LOS 13.0
Zeal: Kernel for LOS 14.1 | Kernel for LOS 13.0
Flash the kernel via TWRP (Install -> Install Image -> Select the boot .img file -> Select boot -> Swipe to confirm flash)
Huge thanks to mattschwantes for helping me with this and the Android4Lumia team for working on this awesome project.
If you have any questions or issues, feel free to contact me or reply to this thread.
Source:
My kernel fork with the touchscreen fix
A4L kernel source code
Does this kernel support both unofficial and official touchscreens? Or only one of both?
MaicoLinuX said:
Does this kernel support both unofficial and official touchscreens? Or only one of both?
Click to expand...
Click to collapse
Only unofficial touchscreens.
Okey, TWRP and LOS13 kernel works as expected, but LOS14.1 kernel bootloops. Why it can be? I'll take a logcat whenever I can enable ADB form TWRP, but it would not work.
MaicoLinuX said:
Okey, TWRP and LOS13 kernel works as expected, but LOS14.1 kernel bootloops. Why it can be? I'll take a logcat whenever I can enable ADB form TWRP, but it would not work.
Click to expand...
Click to collapse
Fame, glee, or zeal?
Original kernel works
TBM 13 said:
Fame, glee, or zeal?
Click to expand...
Click to collapse
Fame. Also, flashing original LOS14 kernel makes it to boot, but obviously with non working touch. So it should be a kernel issue, but I'll do more research.
---------- Post added at 10:07 AM ---------- Previous post was at 10:03 AM ----------
OK, after flashing kernel from TWRP it booted and now works.
Maybe flashing it through fastboot (like I did all times before) doesn't work? IDK, but that was pretty strange.
MaicoLinuX said:
Fame. Also, flashing original LOS14 kernel makes it to boot, but obviously with non working touch. So it should be a kernel issue, but I'll do more research.
---------- Post added at 10:07 AM ---------- Previous post was at 10:03 AM ----------
OK, after flashing kernel from TWRP it booted and now works.
Maybe flashing it through fastboot (like I did all times before) doesn't work? IDK, but that was pretty strange.
Click to expand...
Click to collapse
I usually flash the kernel from fastboot, so it shouldn't be a problem.
That was weird. If you still have problems, tell me.
Works like a charm
Works absolutely fine in both TWRP and Lineage. Kudos to you sir!
My twrp not work touch
My twrp not work touch
i flashing kernel 13 and twrp work however rom 13 not work touch.
already kernel 14 not work twrp and rom bootloop .
what could I do??
leocoelho said:
My twrp not work touch
i flashing kernel 13 and twrp work however rom 13 not work touch.
already kernel 14 not work twrp and rom bootloop .
what could I do??
Click to expand...
Click to collapse
First, you need to flash the TWRP with fixed touchscreen for your device, then, flash the ROM and after that, flash LOS 13/14.1 kernel, depending on which LOS version you flashed.
TBM 13 said:
First, you need to flash the TWRP with fixed touchscreen for your device, then, flash the ROM and after that, flash LOS 13/14.1 kernel, depending on which LOS version you flashed.
Click to expand...
Click to collapse
I made it . Kernel 13 with rom 13 worked the touch, but after restarting the device, it gave the touch again bug.
Eu fiz isso . Kernel 13 com rom 13 funcionou o touch porém após reiniciar o aparelho voltou a dar bug o touch.
I am Brazilian
Multitouch
Hey, uh... i'm testing and i found that multitouch doesn't work... The screen only supports one finger touching and not two simultaneously
Anyway to fix this?
My device is Nokia lumia 520 Fame
IsaqueLNC said:
Hey, uh... i'm testing and i found that multitouch doesn't work... The screen only supports one finger touching and not two simultaneously
Anyway to fix this?
My device is Nokia lumia 520 Fame
Click to expand...
Click to collapse
Yeah, it doesn't support multitouch. Edit: The latest version now supports multitouch
Kernel links updated. Multitouch is now supported (two fingers).
"error opening external sd/los14-gee-touchscreen2.img" (I/O Error)
everything works, i'm stuck on this thing when i try installing the kernel through twrp
AlvinDmello said:
"error opening external sd/los14-gee-touchscreen2.img" (I/O Error)
everything works, i'm stuck on this thing when i try installing the kernel through twrp
Click to expand...
Click to collapse
Try moving the kernel to the internal storage instead. If that doesn't work, you can flash it through fastboot with this command: fastboot flash boot <boot.img>
TBM 13 said:
Try moving the kernel to the internal storage instead. If that doesn't work, you can flash it through fastboot with this command: fastboot flash boot <boot.img>
Click to expand...
Click to collapse
I did that... I tried moving over the files to internal storage...
I don't get the fastboot method, I tried it. It said 'no partition found' or smth similar to that.
OK LOL ANOTHER THING I TRIED FLASHING MY 620 WHICH HAD AN eMMC
GUESS WHAT? ITS FINE AS HELL. I HAVE TWO OF THE 730S
WAITING FOR THEIR NO. TO COME
How about lumia cyan? lumia 532
wikt0249 said:
How about lumia cyan? lumia 532
Click to expand...
Click to collapse
That phone isn't supported by the Android4Lumia project, so why'd you want a fix for unofficial touchscreens there?
TBM 13 said:
That phone isn't supported by the Android4Lumia project, so why'd you want a fix for unofficial touchscreens there?
Click to expand...
Click to collapse
idk how to find a rom to the lumia 532 its empty everywhere :/
Related
This is my version of TWRP built for the 2015 Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the downloads tab.
XDA:DevDB Information
TWRP, Tool/Utility for the Moto X Play
Contributors
vache, squid2
Source Code: https://github.com/sultanqasim/android_device_motorola_lux
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-09-05
Last Updated 2018-08-16
Reserved
2015-09-17 :
-Fix flashing custom zips
Gr8!!
Is this actually built for X Play? I know it sounds silly but there's no kernel source yet is there? Or do we not need that to build recovery?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Yes it's build for X Play, based on G 2015 device tree. I'm using MSM8916 generic kernel from Motorola, modded by @squid2 (https://github.com/sultanqasim/android_kernel_motorola_msm8916)
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
ephumuris said:
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Click to expand...
Click to collapse
Yes i think we'll have to wait for kernel sources to get a working custom.
Already build one (SOKP) but cannot get it to boot (with stock kernel or msm8916 kernel)
Shreps said:
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
Click to expand...
Click to collapse
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Thanks for this Vache! However, just to let you know this is still showing as Moto G 2015 when plugged into my PC whilst in recovery - not sure if that's normal or not?
skdubg said:
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Click to expand...
Click to collapse
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
Hopefully they have a XT1563 full backup soon as well. Cheers.
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
XMoDuLeSx said:
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
Click to expand...
Click to collapse
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Wow thanks for your great work. Soon, we'll be able to get custom kernel to go with the stock firmware. We will probably get better performance with a properly tuned CPU governor. I'd also love to see CM12 being ported but the Moto firmware is already really good. In fact, I'm not sure if I could live without the added feature like Moto Voice and Moto Assist.
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
@squid2 Did you used the lux_defconfig in ext_defconfig ?
Already tried with those addition, the phone boot but i have no RIL. (Stock ROM)
Ill post a new reco with this kernel.
EDIT : Published a new version, with the new kernel config, that fix brightness and vibration.
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
derelektrischemoench said:
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
Click to expand...
Click to collapse
Stock Recovery is also available on my backup.
And yes, if TWRP is working while booting it, should work also fine when flashing it.
Be sure to use the latest version by @vache
Ok thx.
And another thing, I made a backup of my recovery partition via ls -al /dev/block/platform/7824900.sdhci/by-name
followed by
dd if=/dev/block/mmcblk0p32 (the partition that had the name "recovery"assigned in the output of the first command)
and got a nice recovery.img written to my sdcard.
Now from my understanding, in case something goes wrong with TWRP i should be able to restore my stock recovery via fastboot flash recovery nameoftheimagethatidumped.img, is that correct?
Greetz DeM
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
Got it booting, my repack method was wrong. All seems to work fine now.
Now trying to build a custom ROM.
Code:
/*
* Your warranty is maybe still valid.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction:
TWRP for OnePlus X (onyx)
Here are a few points to consider:
This Recovery should only be used for flashing when you are on New Bootloader
This recovery MUST NOT be used to flash a ROM that is based on old bootloader
Using this recovery, you may break the OTA. So it is advised that you should not flash OTA with this. Rather, Download OTA zip and then flash (Only if you know what you are doing)
Also refer This Post too.Downloads & Flashing Instructions:
Official TWRP PageCREDITS:
* TWRP Team
* eng.stkFAQs:
Please Read This Post first
Q. I am on OOS 2.x/CM/AOSP based ROM, How do I use this?
A: Just Upgrade to OOS 3.x based ROM from TWRP. Then Flash this.
Q. Why Do I use this if i can just flash everything I need while updating to OOS 3.x ?
A: Well, There can be change of minds/plans. Also, OnePlus is close to releasing their sources for MM kernels. I saw no recovery to deal with custom kernels so I built it.
Great job
Just to know, what's the difference between this and eng.stk one ?
Yours is compiled from just released sources ?
I think, it could be usefull, as it was clear for a lot of people with BS V41, to add a disclaimer like :
- this is a TWRP to flash and use on OOS 3 only
- it can not be used to flash OOS 3 while you are on OOS2 or a custom ROM CM13, RR....
- it can not be use to flash custom Roms like CM, AOSP, RR.....
Am I right ?
Kéno40 said:
I think, it could be usefull, as it was clear for a lot of people with BS V41, to add a disclaimer like :
- this is a TWRP to flash and use on OOS 3 only
- it can not be used to flash OOS 3 while you are on OOS2
- it can not be use to flash custom Roms like CM, AOSP, RR.....
Am I right ?
Click to expand...
Click to collapse
Yes, Indeed. I'll add this to OP
dadaz007 said:
Just to know, what's the difference between this and eng.stk one ?
Yours is compiled from just released sources ?
Click to expand...
Click to collapse
Compiled from source, yes. latest. mm branch.
xdaHG said:
We are supposed to flash this when we are on OOS3 and not before, right?
And also, all subversions of OOS3?
Click to expand...
Click to collapse
Yep. Only for OOS 3.x and based ROMs. cannot be used to flash other ROMs. for that, use Official TWRP thats HERE
xdaHG said:
Also, what is the advantage of using this TWRP over the bluspark one?
Click to expand...
Click to collapse
Blu spark is to be used for flashing OOS 2.x/CM/AOSP/CAF based ROMs.
But this recovery is to be used to flash OOS 3.x based ROMs.
We are supposed to flash this when we are on OOS3 and not before, right?
And also, all subversions of OOS3?
---------- Post added at 01:34 PM ---------- Previous post was at 12:52 PM ----------
Also, what is the advantage of using this TWRP over the bluspark one?
Nachiket.Namjoshi said:
Blu spark is to be used for flashing OOS 2.x/CM/AOSP/CAF based ROMs.
But this recovery is to be used to flash OOS 3.x based ROMs.
Click to expand...
Click to collapse
I think he was speaking about the BS TWRP V41 spécial OOS 3 .
Can I flash the recovery using flashify? Or only through Fastboot?
sundhar88 said:
Can I flash the recovery using flashify? Or only through Fastboot?
Click to expand...
Click to collapse
Yes you can if your on OOS3.
twrp-3.0.2-0-onyx-OOS-stable.img
DOWNLOAD
twrp-3.0.2-0-onyx-OOS-stable.img - AFH
CHANGELOG:
Code:
[B]twrp-3.0.2-0-onyx-OOS-stable.img[/B]
* fixed kernel panic on usb attachment in recovery
I tried this one to flash H2OS 2.0 (MM) and get an error message said that my phone is ONE, and the H2OS zip file is for E1001. Then I tried bluspark twrp 3.0.2.0-2 v41 and I was able to flash the zip.
namquang93 said:
I tried this one to flash H2OS 2.0 (MM) and get an error message said that my phone is ONE, and the H2OS zip file is for E1001. Then I tried bluspark twrp 3.0.2.0-2 v41 and I was able to flash the zip.
Click to expand...
Click to collapse
Ah, I got this.. should be fixed in a jiffy.. next update
Nachiket.Namjoshi said:
twrp-3.0.2-0-onyx-OOS-stable.img
DOWNLOAD
twrp-3.0.2-0-onyx-OOS-stable.img - AFH
CHANGELOG:
Code:
[B]twrp-3.0.2-0-onyx-OOS-stable.img[/B]
* fixed kernel panic on usb attachment in recovery
Click to expand...
Click to collapse
Nice effort!
Found 2 issues though:
- double tap 2 wake doesn't work
- problems installing H2OS MM (error 7, this package is for bla..bla..) >> edit: same issue as previous post
Both are working in eng.stk version.
UPDATE!
Downloads:
twrp-3.0.2-0-onyx-stable-0.2.img - AFH
Changelog:
Code:
[B]twrp-3.0.2-0-onyx-stable-0.2.img[/B]
* Changed product name from ONE to OnePlus (Which fixes Flashing of Official OnePlus ROMs such as OOS, H2OS)
Hmm doesn't boot for me on oos 3 bootloader.
Just black screen and white led
Nachiket.Namjoshi said:
[*]This Recovery should only be used for flashing when you are on OOS 3.x (and ROMs based on it)
[*]This recovery MUST NOT be used to flash a normal ROM that you get in the forum. Example of which ROMs it is compatible with: OOS, H2OS
Click to expand...
Click to collapse
I flashed CM13 over OOS 3 and it boots.
dadaz007 said:
Hmm doesn't boot for me on oos 3 bootloader.
Just black screen and white led
Click to expand...
Click to collapse
Probably you flashed something sketchy or in a wrong/unintended way, nevertheless, I will look into it.
PS: If you could provide me with a log, it would be helpful...
Thanks.
tech_master said:
I flashed CM13 over OOS 3 and it boots.
Click to expand...
Click to collapse
yes, thats because of this
I've flashed via TWRP and via Flashify, Rashr.... always selecting recovery image.
Edit: I think I find why it wouldn't boot. I haven't seen but I was on bluspark twrp.
I flash your previous twrp version, rebbot to recovery and flash last version and it works now.
@Nachiket.Namjoshi usb otg cannot be mounted in the latest build.
Anyway thanks for your work.
matwaking said:
@Nachiket.Namjoshi usb otg cannot be mounted in the latest build.
Anyway thanks for your work.
Click to expand...
Click to collapse
Can confirm.
Also, DT2W doesn't work....
............ Xda has the authority to remove my post if my post is on the wrong place or without there permission ..
Mokee team has the authority to remove my post because they are the Dev of this .... And both of xda and mokee has all the rights to remove this ....
............... Disclaimer..............
This rom isn't belongs to me .. I'm not a Dev, not a maintainer, nothing ......
THIS ROM BELONGS TO MOKEE TEAM .
THEY are working for this rom..
Mokee os is giving nightly updates ...
................... warning.......
Mokee team, or me no one is responsible for dead sd card, nuclear war, for nothing that could be happen by installing this is .........
Installing this os is your own decision.......
Rom information.....
Based on aosp...
Status nightly...
Os version 9.0.
Kernel version 3.18.14.
Open gapps https://opengapps.org/
Optional gapps flame gapps
Tested on a520l
Download a5 2017 https://download.mokeedev.com/a5y17lte.html
Download a7 2017 https://download.mokeedev.com/a7y17lte.html
Read first
If you stuck on boot loop
Change gapps version (example ) if you got boot loop with latest gapps than flash the older gapps ..
Recommend gapps nano, micro ...
If
Screen shots
Hello, if there video call good? dont laggy? whatsapp ?
TheGunner22 said:
Hello, if there video call good? dont laggy? whatsapp ?
Click to expand...
Click to collapse
Try it and explore :laugh:
devil meru said:
Try it and explore :laugh:
Click to expand...
Click to collapse
now i'm goning to test
Post moved to guide news and discussion
devil meru said:
Post moved to guide news and discussion
Click to expand...
Click to collapse
have that here too , whatapp video call very very laggy.
i need video calls bec i'm deaf.
thanks anyway.
TheGunner22 said:
have that here too , whatapp video call very very laggy.
i need video calls bec i'm deaf.
thanks anyway.
Click to expand...
Click to collapse
I will suggest you to stay on stock if you want this ..
2nd try option58 a7 port for a5 best rom ever ...
Same as stock Samsung firmware try it
TheGunner22 said:
have that here too , whatapp video call very very laggy.
i need video calls bec i'm deaf.
thanks anyway.
Click to expand...
Click to collapse
As I said in the other thread, we're basically out of luck until it gets fixed in lineage. If it's not fixed in los 16, hopefully it is in los17.
SnowFuhrer said:
As I said in the other thread, we're basically out of luck until it gets fixed in lineage. If it's not fixed in los 16, hopefully it is in los17.
Click to expand...
Click to collapse
Right...
I'm still checking the rom. searching for bugs, thanks for this btw. good job!
Shiroyuki82 said:
I'm still checking the rom. searching for bugs, thanks for this btw. good job!
Click to expand...
Click to collapse
:good:
SnowFuhrer said:
As I said in the other thread, we're basically out of luck until it gets fixed in lineage. If it's not fixed in los 16, hopefully it is in los17.
Click to expand...
Click to collapse
i will hope.
---------- Post added at 14:12 ---------- Previous post was at 14:11 ----------
Shiroyuki82 said:
I'm still checking the rom. searching for bugs, thanks for this btw. good job!
Click to expand...
Click to collapse
you know that have bug with video calls right?
YouTube link
ok
please can you upload the twrp you used because I try to install but restart in the twrp and it doesn't boot
Blaster27 said:
please can you upload the twrp you used because I try to install but restart in the twrp and it doesn't boot
Click to expand...
Click to collapse
https://dl.twrp.me/a5y17lte/
Install latest twrp 3.3.1.1
Oem unlock ..
Goto download mode connect to odin
un check auto reboot
Flssh twrp .
Reboot into recovery (donot boot into system )
Format data ..
Flash rmm
Reboot to recovery again .
Flash the rom you wanna flash
ok
devil meru said:
Oem unlock ..
Goto download mode connect to odin
un check auto reboot
Flssh twrp .
Reboot into recovery (donot boot into system )
Format data ..
Flash rmm
Reboot to recovery again .
Flash the rom you wanna flash
Click to expand...
Click to collapse
I install the rom, but it doesn't start it stays in the logo and then reboots and stays in recovery
Twrp https://dl.twrp.me/a7y17lte/
Rom https://download.mokeedev.com/a7y17lte.html
Gapps https://opengapps.org/
Kernel https://androidfilehost.com/?fid=4349826312261646718
I have uploaded all files you need
Rom gapps kernel twrp .... Flash rom flash gapps reboot
If you stuck on boot loop goto trwp flash rom again gapps and flash kernel ..
If still you have boot loop than try lineage 16, crdroid , pixel ex,
And see if any of these rom successfully boot..
Than copy the kernel.img from the rom which is booted ..and flash mokee os gapps and that img file ..
Hope it will boot ....
Android 10 is here!
Took a while, but here's Lineage 17.1 builds, based on Android 10.
Everything should work AFAIK, but let me know if something doesn't.
If you run into problems installing Gapps, you might need an updated
TWRP build. It needed a change to support the new system-as-root
in Android 10. If the official TWRP builds doesn't have it yet, there's
links below of some builds I did.
For root, use Magisk: https://forum.xda-developers.com/apps/magisk
If you are doing backups of 17.1 with TWRP, and wants to restore one of these backups,
you need to flash this right after restoring, or otherwise the boot will hang: http://www.mediafire.com/file/a454nnpp8l7afbr/fix_rootfs_label.zip/file (Needed only for older TWRP, and not for the one linked to below)
Download:
GT-I9190: https://www.mediafire.com/file/ewdbbg757ujbc3r/lineage-17.1-20220816-UNOFFICIAL-serrano3gxx.zip/file
GT-I9192: https://www.mediafire.com/file/a0ya2fdcf0drjt1/lineage-17.1-20220817-UNOFFICIAL-serranodsdd.zip/file
GT-I9195: https://www.mediafire.com/file/3ky5...7.1-20220816-UNOFFICIAL-serranoltexx.zip/file
SPH-L520: https://www.mediafire.com/file/l0le....1-20220817-UNOFFICIAL-serranoltespr.zip/file
SCH-R890: https://www.mediafire.com/file/cqxl....1-20220817-UNOFFICIAL-serranolteusc.zip/file
Recovery (TWRP):
GT-I9190: https://www.mediafire.com/file/e42oml5716ekvk7/twrp-3.6.2_9-0-serrano3gxx.img/file
GT-I9192: https://www.mediafire.com/file/2plk5azmfxwsm5z/twrp-3.6.2_9-0-serranodsdd.img/file
GT-I9195: https://www.mediafire.com/file/wtsopyh3rmfoatf/twrp-3.6.2_9-0-serranoltexx.img/file
SPH-L520: https://www.mediafire.com/file/iw68mr671fgftnb/twrp-3.6.2_9-0-serranoltespr.img/file
SCH-R890: https://www.mediafire.com/file/417w6vp0m338fb0/twrp-3.6.2_9-0-serranolteusc.img/file
Link to all builds:
GT-I9190: http://www.mediafire.com/folder/4kjlyp6v2lfnh/lineage-17.1
GT-I9192: http://www.mediafire.com/folder/hw7l5hqe0fv1m/lineage-17.1
GT-I9195: http://www.mediafire.com/folder/3911mczazsvdt/lineage-17.1
Download Gapps: https://opengapps.org/?api=10.0&variant=pico
Sources:
https://github.com/LineageOS/android_kernel_samsung_msm8930-common
https://github.com/LineageOS/android_device_samsung_msm8930-common
https://github.com/LineageOS/android_device_samsung_serrano-common
https://github.com/LineageOS/android_device_samsung_serrano3gxx
https://github.com/LineageOS/android_device_samsung_serranodsdd
https://github.com/LineageOS/android_device_samsung_serranoltexx
https://github.com/arco/android_device_samsung_serranoltespr
https://github.com/arco/android_device_samsung_serranolteusc
Cellular not working on the 9192? Upgrade your baseband: https://forum.xda-developers.com/t/modem-odin-stopped-samsung-galaxy-s4-mini-duos-i9192.2768593/
Thanks arco <3
Thanks :good: arne everything working on I9192
Arslan140 said:
Thanks :good: arne everything working on I9192
Click to expand...
Click to collapse
Is it working for you???? because i try but failed... Recovery img dont work....he stoped and no recovery no boot rom...
khatir bahri said:
Is it working for you???? because i try but failed... Recovery img dont work....he stoped and no recovery no boot rom...
Click to expand...
Click to collapse
Both Rom and Recovery Works for me on my I9192
Maybe your download get corrupt
Root is not working though as arne said
i tried to patched boot.img for magisk but it did not work either
little things that i notice So far
1st when creating QR code or Scan QR code for wifi(Android 10 feature) Settings Got Crash
2nd conditions/Summaries that shown on the top section of the settings like turn on mobile data,your phone is on silent..etc There is no way to dismiss that on previous versions you can swype to dissmiss that
Everything seem to be working well in here
And here is some screenshots for ya
And another thing I installed the rom and the gapos with the latest official TWRP and not Arco's one
Hello,
thanks for your work.
Sadly there are some ugly and heavy bugs, escpecially regarding some hardware
related things.
Bluetooth Audio stutters and cause the whole system ui to get laggy and also
some force closes can happen. Audio streaming is not possible.
Wifi Direct is not working anymore.
Memory leaks appear.
And so on..
After some hours of intensive and frustrating testing i went back to stock rom
where i never encounter such issues.
Im using the phone at home without any simcard just for audio streaming from
my nas to my hometheatre-system.
Best regards.
Dear arco68 ! What about magisk ?
---------- Post added at 12:26 PM ---------- Previous post was at 11:54 AM ----------
It is not possible to send sms directly from the app ,you have to choose a sim to send sms in the "Network and Internet" settings"
Arslan140 said:
1st when creating QR code or Scan QR code for wifi(Android 10 feature) Settings Got Crash
Click to expand...
Click to collapse
Will be fixed in next build.
Jaroslav.100 said:
Dear arco68 ! What about magisk ?
Click to expand...
Click to collapse
Google magisk and system-as-root. It's not a straight forward thing in Android 10, due to the bootimage is not containing a real ramdisk anymore. As far as I could figure out, you have to patch the recoveryimage, and boot to recovery in order for magisk to load. When booting this patched recoveryimage, magisk will boot into the normal system unless you keep the hardware keys pressed all until recovery is loaded. It's all a bit messy, and I could not get this to work though. If anyones gonna mess with this, be sure you have backups, in case normal boot gets broken.
It is not possible to send sms directly from the app ,you have to choose a sim to send sms in the "Network and Internet" settings"
Click to expand...
Click to collapse
Dual SIM? Probably some stuff are not implemented yet for this.
Thank you arco, we will wait for your updates !
@arco68 is our devices can install the GSI roms or nah ?
Ala Ghanmi said:
@arco68 is our devices can install the GSI roms or nah ?
Click to expand...
Click to collapse
No
Ala Ghanmi said:
And another thing I installed the rom and the gapos with the latest official TWRP and not Arco's one
Click to expand...
Click to collapse
I've also got it right first time on my GT-I9195 with the official TWRP 3.3.1-0
Diresh said:
No
Click to expand...
Click to collapse
Okay get it
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
Claudio4780 said:
I've also got it right first time on my GT-I9195 with the official TWRP 3.3.1-0
Click to expand...
Click to collapse
That's nice
Is network is working fine for both sim , because previously linage os 16 have issue
omgitsavinash said:
Is network is working fine for both sim , because previously linage os 16 have issue
Click to expand...
Click to collapse
Both Sims are working fine
I installed this ROM on my test device. It all works very well. The only problem I noticed was like @franticfreddy said, the Bluetooth audio doesn't work right.
I'm not the creator, but want to start a discussion on that build!
I found the non-Compact build via Google search:
https://download.pixelexperience.org/g8341
https://download.pixelexperience.org/g8342
WARNING: Both builds are marked "stable", but are very buggy and should not be named "stable" at all!
Rooted_Ansh said:
They are just marked stable.. but they are beta release..
Click to expand...
Click to collapse
Rooted_Ansh said:
[The official build] is sodp (Sony open devices) and [Rooted_Ansh XZ1c build] has stock libs, drivers, and camera
Click to expand...
Click to collapse
How to flash:
shuang0922 said:
oem b? xz1 is A only.just need flash one img
How to flash Pixel Experience (PE) for yoshino platform (like XZ1):
boot twrp, flash pe zip, reboot fastboot, flash oem, then fastboot -w and reboot
Click to expand...
Click to collapse
Did any one give it a try ?
Sent from my G8342 using Tapatalk
sounds reaaaaly interesting!
could someone provide a full how-to guide?
thank you very much!!
BoZ
Just tried it and sadly it's not stable as this site said it's too slow many random restart Google camera stop working I'm back again to lineage 17
Sent from my GM1913 using Tapatalk
sorry mate, where did you find they say it's slow and has random reboots?
bozinsky73 said:
sorry mate, where did you find they say it's slow and has random reboots?
Click to expand...
Click to collapse
The hole system is unstable , while you navigate between apps also camera works only for the first time but after that it didn't work even i cleared it's cash and storage several times , sound also not working !!
This rom still needs a lot of work
Sent from my GM1913 using Tapatalk
SGH-i200 said:
XZ1c unofficial build by Rooted_Ansh (installation instruction for XZ1c, which is missing for XZ1!?):
https://forum.xda-developers.com/xp...el-experience-10-0-plus-update-t4071563/page7
Click to expand...
Click to collapse
What do you mean by the last line ? Installation instructions missing ?
---------- Post added at 12:26 AM ---------- Previous post was at 12:19 AM ----------
SGH-i200 said:
Same maintainer released this XZ1c official build:
https://download.pixelexperience.org/g8441
XZ1c unofficial build by Rooted_Ansh (installation instruction for XZ1c, which is missing for XZ1!?):
https://forum.xda-developers.com/xp...el-experience-10-0-plus-update-t4071563/page7
Click to expand...
Click to collapse
Also could you please remove unofficial xz1c links from here ?.. I have it's thread opened being a maintainer..
Hi, coming from LOS 17.1 I cannot follow instructions on official pixelexperiences site:
when I try to flash
fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_yoshino.img
over fresh stock it turns out with error: no such partition
same when flashing oem_b
is there a fix for that?
thank you very much!
bozinsky73 said:
Hi, coming from LOS 17.1 I cannot follow instructions on official pixelexperiences site:
when I try to flash
fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_yoshino.img
over fresh stock it turns out with error: no such partition
same when flashing oem_b
is there a fix for that?
thank you very much!
Click to expand...
Click to collapse
just type " fastboot flash oem oem.img " and flash the rom with twrp in Los17
bozinsky73 said:
Hi, coming from LOS 17.1 I cannot follow instructions on official pixelexperiences site:
when I try to flash
fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_yoshino.img
over fresh stock it turns out with error: no such partition
same when flashing oem_b
is there a fix for that?
thank you very much!
Click to expand...
Click to collapse
oem b? xz1 is A only.just need flash one img
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
bozinsky73 said:
Hi, coming from LOS 17.1 I cannot follow instructions on official pixelexperiences site:
when I try to flash
fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_yoshino.img
over fresh stock it turns out with error: no such partition
same when flashing oem_b
is there a fix for that?
thank you very much!
Click to expand...
Click to collapse
How to flash PE :
for yoshino platform : boot twrp, flash pe zip, reboot fastboot, flash oem, then fastboot -w and reboot
u can find these in telegram group
shuang0922 said:
oem b? xz1 is A only.just need flash one img
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
How to flash PE :
for yoshino platform : boot twrp, flash pe zip, reboot fastboot, flash oem, then fastboot -w and reboot
u can find these in telegram group
Click to expand...
Click to collapse
Thank you very much! I'm a totaly noob on xperia firmwares
Just to be sure: is oem.img the SW_BINARIES_FOR_XPERIA_ANDROID_10.0.7.1_R1_V5A_YOSHINO.img file?
BoZ
bozinsky73 said:
Thank you very much! I'm a totaly noob on xperia firmwares
Just to be sure: is oem.img the SW_BINARIES_FOR_XPERIA_ANDROID_10.0.7.1_R1_V5A_YOSHINO.img file?
BoZ
Click to expand...
Click to collapse
yes.xz1 is yoshino
u can c here
shuang0922 said:
yes.xz1 is yoshino
u can c here
Click to expand...
Click to collapse
and that oem means this
Has anyone managed to install this customrom?
I have tried installing it but it was repeated reboots
I find it hard to do according to the instructions given by the ROM provider and has installed the latest binary .
After I installed the OEM binary I flashed the ROM and it happened
I tried another way with flash again stock ROM but in newflasherv20 an error message popped up even though before I could install stock firmware v126 pie for Sov36 and what I want to install the firmware for Globa UK v228 doesn't suit me
now I have Rom SOV36 v126 Pie which I restore from twrp. but still want to try Pixel Experience Plus 10.0
There is the right method for this flash rom
as I said already Binary Flash and Pixel flash but so reboot repeatedly
Please make a tutorial step by step via notes or video to make it easier
shuang0922 said:
oem b? xz1 is A only.just need flash one img
How to flash Pixel Experience (PE) for yoshino platform:
boot twrp, flash pe zip, reboot fastboot, flash oem, then fastboot -w and reboot
Click to expand...
Click to collapse
Thanks for the hint. Will add that to the OP.
I found a few bugs in Rom PE
Battery charging is not stable
Advance boot not working
Sometimes it becomes slow after rebooting
Bug Camera
Bug Mic
Slow reboot even stuck
And somehow my TWRP suddenly disappeared after Vol - and Power TWRP didn't show up either
While I will use LoS17.1 because after installing OEM from Sony it is more stable
This is the worst rom for Sony xz1 i have ever tried
Sent from my G8342 using Tapatalk
hany ahmed79 said:
This is the worst rom for Sony xz1 i have ever tried
Sent from my G8342 using Tapatalk
Click to expand...
Click to collapse
I agree with you. Yes maybe there is something that works. But there are a lot of bugs in this Rom that make me disappointed as a holder of the G8341 because it is labeled Stable
But on the other hand the value of the OS itself is pretty good and the kernel also works well
Only in the Lib section that must be addressed again for developers
? There are things in this Rom that make me confused why I can't enter TWRP at all and I tried to flash again TWRP got failed results.
Now back to XperiaOS ( Stock Rom )
I agree with you also don't know why they marked it as stable release.
I'm now on lineage 17.1 unofficial build but it's way better and more stable.
Sent from my G8342 using Tapatalk
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
starvirus10 said:
I agree with you. Yes maybe there is something that works. But there are a lot of bugs in this Rom that make me disappointed as a holder of the G8341 because it is labeled Stable
But on the other hand the value of the OS itself is pretty good and the kernel also works well
Only in the Lib section that must be addressed again for developers
[emoji848] There are things in this Rom that make me confused why I can't enter TWRP at all and I tried to flash again TWRP got failed results.
Now back to XperiaOS ( Stock Rom )
Click to expand...
Click to collapse
I agree with you also don't know why they marked it as stable release.
I'm now on lineage 17.1 unofficial build but it's way better and more stable.
Sent from my G8342 using Tapatalk
SGH-i200 said:
Thanks for the hint. Will add that to the OP.
Click to expand...
Click to collapse
Hey..
Why haven't you written on 1st post that the official ones are still in beta ?.. I told you before right ?... The rom is marked stable not the build..
Do not provide incomplete information to users and ruin their expectations ... !!!
---------- Post added at 08:46 AM ---------- Previous post was at 08:43 AM ----------
starvirus10 said:
I found a few bugs in Rom PE
Battery charging is not stable
Advance boot not working
Sometimes it becomes slow after rebooting
Bug Camera
Bug Mic
Slow reboot even stuck
And somehow my TWRP suddenly disappeared after Vol - and Power TWRP didn't show up either
While I will use LoS17.1 because after installing OEM from Sony it is more stable
Click to expand...
Click to collapse
hany ahmed79 said:
This is the worst rom for Sony xz1 i have ever tried
Click to expand...
Click to collapse
starvirus10 said:
I agree with you. Yes maybe there is something that works. But there are a lot of bugs in this Rom that make me disappointed as a holder of the G8341 because it is labeled Stable
But on the other hand the value of the OS itself is pretty good and the kernel also works well
Only in the Lib section that must be addressed again for developers
? There are things in this Rom that make me confused why I can't enter TWRP at all and I tried to flash again TWRP got failed results.
Now back to XperiaOS ( Stock Rom )
Click to expand...
Click to collapse
hany ahmed79 said:
I agree with you also don't know why they marked it as stable release.
I'm now on lineage 17.1 unofficial build but it's way better and more stable.
Sent from my G8342 using Tapatalk
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
I agree with you also don't know why they marked it as stable release.
I'm now on lineage 17.1 unofficial build but it's way better and more stable.
Click to expand...
Click to collapse
It's written in the first post...
The ROM is marked as stable ... The build for this device and yoshino platform is still under beta ..
These are beta releases
To know and discuss more join : Pixel Experience Sony Group
https://t.me/PixelExperienceSony
PS : I am not the developer for official ones