[Kernel][Oreo][ Kernel for LineageOS 15.1 - BEETHOVEN] - Huawei Mediapad M3 ROMs, Kernels, Recoveries, & Ot

Hi !
This kernel is only for BTV (Beethoven) devices that use LineageOS Oreo 15.1 !
This kernel is quite stable for everyday use but still has many shortcomings - which will be fixed/added in time .
Whenever you have trouble with LineageOS 15.1 ( means random reboots, crashing applications or something like that ) it is worth trying this kernel to bring your device into a stable operating state.
This kernel is based to Android Kernel Linux 4.3.0 .
Downloads:
For All LTE/4G devices : boot_lte_4.3.0.img
For All Only Wi-Fi devices : boot_wifi_4.3.0.img
Installations:
- via fastboot/bootloader mode : [ fastboot flash boot boot_lte_4.3.0.img ]
- via TWRP, by choosing to install image into Boot partition
Source code :
kernel_huawei_btv

surdu_petru said:
Hi !
This kernel is only for BTV (Beethoven) devices that use LineageOS Oreo 15.1 !
This kernel is quite stable for everyday use but still has many shortcomings - which will be fixed/added in time .
Whenever you have trouble with LineageOS 15.1 ( means random reboots, crashing applications or something like that ) it is worth trying this kernel to bring your device into a stable operating state.
This kernel is based to Android Kernel Linux 4.3.0 .
Downloads:
For All LTE/4G devices : boot_lte_4.3.0.img
For All Only Wi-Fi devices : boot_wifi_4.3.0.img
Installations:
- via fastboot/bootloader mode : [ fastboot flash boot boot_lte_4.3.0.img ]
- via TWRP, by choosing to install image into Boot partition
Source code :
kernel_huawei_btv
Click to expand...
Click to collapse
Flashed wifi version with TWRP; errors out a few seconds after starting Linage, then errors out and boots to EMUI screen.

friedsonjm said:
Flashed wifi version with TWRP; errors out a few seconds after starting Linage, then errors out and boots to EMUI screen.
Click to expand...
Click to collapse
I already tested on DL09 ( LTE device ) and I guess it's working as well on Wi-Fi devices .... please try to reinstall the last update of LOS 15.1, and flash this kernel before to exit from TWRP . Thanks !
EDIT: I guess you need to do a full wipe on TWRP if you have some error on boot with this new boot.img ... that's why it's better to flash LOS 15.1 on clean, install gapps and also this new boot.img before to exit from TWRP !

Thanks. It's working well on my BTV-W09

sergio_sant said:
Thanks. It's working well on my BTV-W09
Click to expand...
Click to collapse
Ok, at the moment it is a step back, but I hope that in a few days I'll come back with a new kernel update to 4.4.11 ... I have only one major problem here to fix before it is published ( something to do with charging the battery )

anyone tested plex with this?

orangpelupa said:
anyone tested plex with this?
Click to expand...
Click to collapse
Installed this kernel a few days ago and have no issues with Plex. The tablet has been completely stable with the latest LOS 15.1 build (2020-08-22).
Thanks again serdu_petru

orangpelupa said:
anyone tested plex with this?
Click to expand...
Click to collapse
thunderz1 said:
Installed this kernel a few days ago and have no issues with Plex. The tablet has been completely stable with the latest LOS 15.1 build (2020-08-22).
Thanks again serdu_petru
Click to expand...
Click to collapse
Yes, Plex and all app will working well with this kernel !
Unfortunately it is a step back in updating the kernel, but this problem has already been fixed and the new LOS 15.1 update will come with a new kernel, this time more stable and based on Android Linux Kernel 4.4.11 or 4.4.12

Related

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30
Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse
Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)
Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I
Thanks, I hope you don't forget dsds variant.
It is a pleasure to have SunKernel in LineageOS.
Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.
Flashing lineage and kernel, looking forward to try it
Thanks for upload
s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install
zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.
L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks
zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

[ROM][Unofficial][8.1.0][deprecated] Lineage OS 15.1 for Xperia Z1 compact 29.12.18

This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18
Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.
Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.
With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!
Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?
The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk
Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:
Great to see this rom realy! This rom have stock camera?
munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.
munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.
Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?
ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.

GSIs fixed builds for hi6250 (emui8)

Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX

[EOL][SODP][ROM][LineageOS][XZ2, XZ2C, XZ3] LineageOS 17.1 [STABLE][UNofficial]

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.

[RECOVERY][Android 10/11][Stock/SODP][XZ2/C/P/3] TWRP [UNofficial]

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...

Categories

Resources