Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
Great, thanks for the update
jerpelea said:
Sony Mobile is committed
Click to expand...
Click to collapse
Thanks for that. Using your project few days, but can't make fingerprint work, any help for this issues would be great. Thanks.
P.S. read you bug tracker. This issues can be fixed only with vendor v11, yes? When it will be released?
Sent from my Sony Xperia XZ1 Compact (AOSP) using XDA Labs
russel5 said:
Thanks for that. Using your project few days, but can't make fingerprint work, any help for this issues would be great. Thanks.
P.S. read you bug tracker. This issues can be fixed only with vendor v11, yes? When it will be released?
Sent from my Sony Xperia XZ1 Compact (AOSP) using XDA Labs
Click to expand...
Click to collapse
FPC is still buggy but will start to work from v11
The release for v11 is planned for today.
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
Hi @jerpelea,
I compiled successfully everything for the 8.1 version, flashed everything successfully, but I'm stuck in bootloop. Flashed stock with Emma, flashed AOSP images, still nothing. The only thing that works is the AOSP recovery, system either bootloops or gets stuck at android logo. Any help here, please?
Thank you
solymir said:
Hi @jerpelea,
I compiled successfully everything for the 8.1 version, flashed everything successfully, but I'm stuck in bootloop. Flashed stock with Emma, flashed AOSP images, still nothing. The only thing that works is the AOSP recovery, system either bootloops or gets stuck at android logo. Any help here, please?
Thank you
Click to expand...
Click to collapse
Have you flashed the oem partition with the vendor binaries?
Regards
J
Yep. All 5 images, I respected the Sony tutorial to the letter.
I tried the same with the February security patch, with the same result, but I thought it was due to recovery ( I kept twrp, now I didn't)
Sent from my G8441 using Tapatalk
solymir said:
Yep. All 5 images, I respected the Sony tutorial to the letter.
I tried the same with the February security patch, with the same result, but I thought it was due to recovery ( I kept twrp, now I didn't)
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
Hi,
did you flash all those partitions?
boot
recovery (optional)
system
vendor
oem
userdata
Regards
J
Well, since then, vendor.img showed up ( I even got a compile error that said certain things had to be deleted from system ). Fixed that, I flahed again and boots exactly ONCE only if I format data from TWRP. If I flash compiled recovery it will never boot.
I suspect this is because of data partition encryption; it boots once after data is formatted, it shows in settings that data is not encrypted. Works perfectly, until first reboot when it bootloops. There are other AOSP versions on this forum, I have the same problem with all of them.
Only AOSP-ish ROM that works for me is Lineage 15.1, courtesy of @modpunk and rooted stock. Yes, both of them seem to be encrypted by default.
For user security dm-verity and File Based Encryption are enabled by default
Please keep them enabled for all user builds
Regards
J
solymir said:
Well, since then, vendor.img showed up ( I even got a compile error that said certain things had to be deleted from system ). Fixed that, I flahed again and boots exactly ONCE only if I format data from TWRP. If I flash compiled recovery it will never boot.
I suspect this is because of data partition encryption; it boots once after data is formatted, it shows in settings that data is not encrypted. Works perfectly, until first reboot when it bootloops. There are other AOSP versions on this forum, I have the same problem with all of them.
Only AOSP-ish ROM that works for me is Lineage 15.1, courtesy of @modpunk and rooted stock. Yes, both of them seem to be encrypted by default.
Click to expand...
Click to collapse
Hi,
since I use the AOSP as my DD and i dont have the userdata issue i would suspect that something went wrong with your customisation
Rregards
J
I am a regular user. Sometimes I want to try AOSP, but I don't have a powerful computer to build. Why does Sony provide a build tutorial instead of a file that has already been built to download.
Is Android P Will come?
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
Related
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Click to expand...
Click to collapse
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB
shoey63 said:
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB [emoji14]
Click to expand...
Click to collapse
Anyway, if Sony would mean it seriously with security restrictions in Concept, then we have to go on at least with custom kernels. As soon as Z3 will be in Open devices, majority of problems like fish-eye camera problem may disappear. I think unified kernel sources for 3.10 are already online.
Sent from my D6603 using Tapatalk
Built it, flashed it, bootloops on kernel splash screen
shoey63 said:
Built it, flashed it, bootloops on kernel splash screen
Click to expand...
Click to collapse
With which fw you use it?
Sent from my D6603 using Tapatalk
Flashed back to pure stock. Version doesn't matter I think. Fastbooted the images and got stuck in an hypnotic bootloop. Kernel splash screen over and over...
Sent from my C6603 using XDA Free mobile app
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
recovery is intened for unlocked bootlaoder and custom roms only
br
J
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
i will update build guide for m-preview1 and publish new zip soon
the old blobs from m-preview are incompatible with new m-preview1!
br
J
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
LeParkour012 said:
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
jerpelea said:
recovery is intened for unlocked bootlaoder and custom roms only
br
J
Click to expand...
Click to collapse
Hi, I would paraphrase the Apollo 13 - "It is not important what it is intended for, but what it actually can do"
ondrejvaroscak said:
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
LeParkour012 said:
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
Click to expand...
Click to collapse
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
ondrejvaroscak said:
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
Click to expand...
Click to collapse
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
LeParkour012 said:
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
ondrejvaroscak said:
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
Click to expand...
Click to collapse
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
LeParkour012 said:
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
Sony releases support files for building AOSP, and yes, if you build from Sony sources, you will get pure Sony AOSP. However, the main intention of AOSP is customization, it is not intended as general purpose daiy use system.
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.
Central project page
https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
11.06.2020
Switch to TWRP 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.A.2.1
Now both twrp should work without a ROM being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse
13.06.2020
Thanks to the fixes in 3.4.0 we got now a TWRP with the following enhancements for STOCK and SODP:
- This TWRP will work with future 10.0 ROMs, you don't need a new build matching the security patch level of your ROM.
- You can install this TWRP again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
Please test and report back if you got any touch / decryption problems.
MartinX3 said:
13.06.2020
Please test and report back if you got any touch / decryption problems.
Click to expand...
Click to collapse
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
TacoLoco said:
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
Click to expand...
Click to collapse
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
MartinX3 said:
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
Click to expand...
Click to collapse
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
TacoLoco said:
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
Click to expand...
Click to collapse
Aaaand added!
Nice to hear and thank you for your report!
MartinX3 said:
Aaaand added!
Nice to hear and thank you for your report!
Click to expand...
Click to collapse
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
cd /tmp/repackorig/ && /sbin/magiskboot hexpatch kernel 77616E745F696E697472616D667300
736B69705F696E697472616D667300 process endet with ERROR: 1
Error patching kernel.
Click to expand...
Click to collapse
It boots me to TWRP every time, I think this is related..
TacoLoco said:
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
It boots me to TWRP every time, I think this is related..
Click to expand...
Click to collapse
What happens if you reboot the twrp and try it again?
Or if you flash magisk and try to boot?
Do you use a modified kernel?
Did you "fastboot flash boot twrp.img" by accident?
14.06.2020
Reuploaded the stock TWRP with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse
Hi there,
what is 'sodp' please ?
moltes74 said:
Hi there,
what is 'sodp' please ?
Click to expand...
Click to collapse
It's described on the first page of the central project thread.
MartinX3, thanks for all your work!
I have a xz2c dual and, thanks to your guides, backed up the TA partition and flashed the latest Unofficial TWRP recovery with the up to date stock image.
My experience is that the problem with some boots not having the touchscreen working is still there. Fortunately, after rebooting you get a new chance ... and sometimes it actually works.
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
tanty0 said:
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
Click to expand...
Click to collapse
Answering myself back. Yes, this is known and you have already stated that you plan to look at this whenever you find the time: https://forum.xda-developers.com/showpost.php?p=83172223&postcount=345 , and below ...
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
02.03.2021
Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.
Click to expand...
Click to collapse
CHEIb00 said:
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
Click to expand...
Click to collapse
It is currently not compatible with the official LOS 17.1 due to technical limitations by google.
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
levone1 said:
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
Click to expand...
Click to collapse
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
MartinX3 said:
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
Click to expand...
Click to collapse
Max brightness as set in settings is very dim...