Project treble for Xperia X Performance
Based on Sony Open Devices
If you end up with a HARD BRICK. Nobody can help you.
Features:
1. Gcam Support
2. Higher performance than SODP default.
Stable Version:
V4.2
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
Required files:
V1.0~V5.1: Link With:SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_tone.img
TWRP: Link
OEM: Link
Sony offcial link
How to flash:
Read README.txt in the zip file please.
GSI:
I tested Descendant.
Different GSI have different compatibility with our treble blob, try more GSI, you will solve all the issues you met.
Gcam:
Gcam must work with Google play services.
I prefer releases from ARNOVA8G2,(Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk)
Download: Link
Enable this settings under fix
•Raw Format to Raw10
•Viewfinder Format to YUV_420_888
If you want to set Raw Format to Raw Sensor
Please enable: Buffer Fix to Fix viewfinder lags.
Update and known BUG:
V5.1:
1. Optimize EAS, more stable.
2. Support dual sim cards.
V5.0:
1. Stable EAS support.
2. I/O speed up.
V4.2:
I forget what's the updates.
V4.1:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back.
3. F2FS support for cache(Qnovo) and userdata partitions.
V4.0:
1. Performance and stability improve.
2. A lot of Fixes of SODP.
V3.1:
1.Update: Performance improve.
V3.0:
1.Update: EAS supported.
TWRP V2.0:
1.Update: Fix userdata can't be read.
V2.0:
1.Update: Performance improve.
V1.0:
1.BUG: Not found.
Source
Sources Code
XDA:DevDB Information
Treble, ROM for the Sony Xperia X Performance
Contributors
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2019-07-11
Last Updated 2019-08-23
Hello,
thank you for your hard work.
Do I understand correctly that you've user 9.0.0_r10 branch of local_manifests when you built it?
Or did you actually checked out the latest one (i.e., 9.0.0_r44)?
hn40cn said:
Hello,
thank you for your hard work.
Do I understand correctly that you've user 9.0.0_r10 branch of local_manifests when you built it?
Or did you actually checked out the latest one (i.e., 9.0.0_r44)?
Click to expand...
Click to collapse
Based on lastest 9.0.0_r44.
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Sjll Back at treble in Xperia x again!
Performance edition this time
thaneekl said:
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Click to expand...
Click to collapse
You need to try different GSI, some GSI don't suit for our treble build.
I tested Pixel Experience.
I will try sim card. I noticed there is IMEI in about phone, so I think sim card should works fine.
thaneekl said:
I follow readme.txt and got bootloop. I wonder what have I done wrong.
edit: It's finally works!! I've to install Magisk, gapps right after install GSI roms. I don't know which one made it boot.
edit2: It just works so far. Sim card didn't work. Some GSI roms throw me to bootloop no matter what I've done. I would love to wait more clearly instraction and example of GSI that works perfectly
Click to expand...
Click to collapse
After I tested, on some GSI sim works, it's not related with our treble build. Please try this GSI.
https://github.com/Descendant/InOps...tZero/Descendant_ThreeDotZero_arm64_aonly.zip
Homepage:
https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
2.0 stable
Havoc-OS 2019-07-12
So far so good. stable so far. But overheat is no joke.
edit:20/7/2019 Heat issued solved. I use this to tame down Snapdragon820. That's just cpu profile so it's will work on any device anyway.
Download the APK, install and grant root permission. No need to flash the zip file. I select Balanced >> Ghostpepper profile.
Omnirom Unofficial 15-07-2019
Best of the best. Not even had heat issues. Is that black magic?
3.1
Now It's work perfectly on my F8132. Thanks a lot.
edit: Yeah It's works. But have issues about random reboot while launching random app or perform random action. Might be rom or overheat isssue. Descendant 3.1.1
edit2: on 3.1
Sjll said:
You need to try different GSI, some GSI don't suit for our treble build.
I tested Pixel Experience.
I will try sim card. I noticed there is IMEI in about phone, so I think sim card should works fine.
Click to expand...
Click to collapse
Any bug on pixel experience gsi? Sorry for my bad english. And thanks for your hard work
Ralvindo said:
Any bug on pixel experience gsi? Sorry for my bad english. And thanks for your hard work
Click to expand...
Click to collapse
So....i dont own an xperia x performance BUT a normal xperia x
And on there the only Problem is that there is an annoying message at Boot
But except that everything is fine
Some random said:
So....i dont own an xperia x performance BUT a normal xperia x
And on there the only Problem is that there is an annoying message at Boot
But except that everything is fine
Click to expand...
Click to collapse
Ok i'll try and give a review here ?
Ralvindo said:
Ok i'll try and give a review here ?
Click to expand...
Click to collapse
:good:
I've got bootloop on latest version.
thaneekl said:
I've got bootloop on latest version.
Click to expand...
Click to collapse
Could you please test the new boot.img with old vendor.img and new vendor.img with old boot.img ?
I need to find the reason.
Sjll said:
Could you please test the new boot.img with old vendor.img and new vendor.img with old boot.img ?
I need to find the reason.
Click to expand...
Click to collapse
It's boot now. Maybe the issues is on my side since my device refuse to boot on any kernel even patched stock kernel at the time
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
thaneekl said:
It's boot now. Maybe the issues is on my side since my device refuse to boot on any kernel even patched stock kernel at the time
Click to expand...
Click to collapse
OK.
plombir0032 said:
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
Click to expand...
Click to collapse
I written "need test". It works on XZP.
plombir0032 said:
You tried run Erfans's Android Q GSI ? I have endless bootanimation after boot. What i doing wrong?
Click to expand...
Click to collapse
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
Why i can't change the minimum frequency in kernel aduitor? Cores always at high frequency, minimum not applied.
SO-04H
hi
is this work on so-04h docomo ?
Related
Project Treble [Pie] For XZ Premium
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards.
请中文用户遵守XDA规则，使用双语留言
Required files:
[Non-Tested]
[Tested]
V1.06-Patch:Link
You can replace the same file in /system/vendor/etc with V1.06-Patch, this patch could improve the performance a lot.
V1.05:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V1.0:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V0.95:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.zip
V0.93:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_yoshino.zip
V0.85:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.zip
EDIT: AEX 6.2 and Magisk works fine with V0.85, with Disable ForceEncrypt @LSS4181
V0.8:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.zip
V0.3:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_YOSHINO.ZIP
V0.2:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_YOSHINO.ZIP
V0.1:Link With: SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V3_YOSHINO.ZIP
Twrp:Link
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < DIR of recovery.img >
Second: flash Treble-xzp-VX.X.zip in Twrp .
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < DIR of OEM.img >
Fourth: Flash a GSI compatible System image and boot!
Update and known BUG:
V1.05:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back.
3. F2FS support for cache(Qnovo) and userdata partitions.
V1.0:
Fix:
1. Source code update.
2. Cancel 90Hz.
3. Support Erfans's Android Q GSI.
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
Bugs:
Need to feedback.
V0.95:
Fix:
1. Source code update.
2. 90Hz Screen frame rate.
Bugs:
Need to feedback.
V0.85:
Fix:
1. Revert to HMP to get better performance.
2. Magisk Fix.
Bugs:
Need to feedback.
V0.8:
New feature:
1. Kernel EAS support.
2. Camera HAL3 support
3. Crosshatch HAL.
Fix:
1. Sleep dead bug totally fixed.
2. Camera disconnect bug fixed.
Bugs:
1. Magisk FC.
V0.3:
Fix:
1.Sleep dead bug should be fixed, tested on PE 9.0 GSI.
Bugs:
1.Camera disconnect after screen-off.
V0.2:
Bugs:
1. May sleep dead.
2.Camera disconnect after screen-off.
V0.1:
Bugs:
1. Wifi is broken(Only G8142).
2. USB connection is broken.
3. May sleep dead.
XDA:DevDB Information
Treble For XZP, ROM for the Sony Xperia XZ Premium
Source Codes
Link
Contributors
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2018-12-20
Last Updated 2019-08-12
wow awesome I will definitely look into this, im pretty curious about how did you did it and also this could be something big for our devices thanks!!
酷安来的支持大佬！！??
Awesome job thanks!
It's like a Christmas present
用这么多the显得不自然啊（#滑稽）
leiersai said:
用这么多the显得不自然啊（#滑稽）
Click to expand...
Click to collapse
发的时候太匆忙了，没有来得及润色（笑）。
leiersai said:
用这么多the显得不自然啊（#滑稽）
Click to expand...
Click to collapse
大佬牛逼，666
---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------
ddwf said:
大佬牛逼，666
Click to expand...
Click to collapse
回错人了，哈哈……
Awesome! You Made me very Happy. Now can i fully Focus on Treble Development! I will Support You with Feedback and maybe some possible Bug fixes. Keep Up the Work, you did a great start for now!
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Beetle84 said:
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Click to expand...
Click to collapse
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Miustone said:
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Click to expand...
Click to collapse
AEX is working nicely so far for me, this is a gamechanger for the XZP, I was beginning to look at new handsets but not for a while now.
WiFi working fine for me on G8141.
Miustone said:
AEX (AOSP Extended) and other Official GSIs are the best Images You can get for now (No big Bugs). Only one unofficial GSI was running good for Me and that was Pixel Expierence from XDA. I really have to find a way to edit the Vendor Content of our XZPs to gain more Features and stuff Like that. There are just many things i miss on my Xperia which are available on My AMOLED Axon 7 after editing the Vendor/OEM Image manually with Root... But no Wonder, the OEM Images are directly from SONY... But i'm looking Forward. Treble is the best what happend to Android in all this Years
Click to expand...
Click to collapse
is it possible to port dsee-hx and noise canceling on other ROMs?
Beetle84 said:
AEX is working nicely so far for me, this is a gamechanger for the XZP, I was beginning to look at new handsets but not for a while now.
WiFi working fine for me on G8141.
Click to expand...
Click to collapse
Same here in all Points. What a nice Gift to the Holidays My XZ Premium feels like a actual Device again. Think i'll get one for My GF too. The Prices are low atm and it's just a Solid Piece of Hardware combined with Treble. Was thinking about Xiaomi for her but the G8141 plays Out the Most actual Devices in the Price Range (~300€). Only real Upgrade for me could be a XZ3 but looks like that has to wait now...
Edit. Think the XZ Premium has the better Design and Speaker Layout. But damn, i would Like to have a 1440p OLED SONY ?
@OP
Could You add the Vendor Partition to the Wipe Menu ,and System and OEM/Vendor Options in the Image Flash Menu from TWRP? I have that Options on My Axon 7 (OKI Labs TWRP Mod from XDA). I'm also unsure if the AROMA TWRP Patch Out of this Forum is already included. The TWRP Versions we use is a bit older i think (3.1.xxxx).
Everything besides Bluetooth is working really Well. Performance is a lot better compared to My Axon 7 and more will be possible after playing around with the Vendor Content. Great Base to Play with!
Thanks again! I'll spent a Coffee next Year!
Just modified the source codes and complied it.
@Miustone how's the camera in our XZP with AEX? Is it still as 'grumpy' as it was on Oreo?
I remember you working on enhancing the camera for AOSP.
ricardo99831390 said:
wow awesome I will definitely look into this, im pretty curious about how did you did it and also this could be something big for our devices thanks!!
Click to expand...
Click to collapse
Just modified source codes, and compile it.
Beetle84 said:
@Sjll
Thanks heaps mate, hugely appreciated, downloading a few different GSI's now
@Miustone
Any recommendations? Im downloading aosp extended and lineage 16.0 images now.
Click to expand...
Click to collapse
Hope you can enjoy it.
Miustone said:
Awesome! You Made me very Happy. Now can i fully Focus on Treble Development! I will Support You with Feedback and maybe some possible Bug fixes. Keep Up the Work, you did a great start for now!
Click to expand...
Click to collapse
The SODP team has done a lot of work on Pie GSI compatibility. I just use the existed partitions and modified source code to make treble works on XZP.
william84 said:
@Miustone how's the camera in our XZP with AEX? Is it still as 'grumpy' as it was on Oreo?
I remember you working on enhancing the camera for AOSP.
Click to expand...
Click to collapse
It is much better right now. Full Camera 2 API Support including RAW and with the right APP like Open Camera do You have full Control of everything. The Sleep Dead Bug is with AEX no problem btw. Just enable the Always on Display Option and it will never sleep. Battery is pretty good and i get over the whole day with LTE+, Wifi and 4hrs+ Display usage. The Treble Kernel is really good and with some fine tuning with Kernel Adiutor is everything even better
I'm playing right now with the Vendor Partition eg. the build.prop and gained already some nice optimizations like better responding Ok Google Commands and better Noise Reduction. I think there will come soon some good stuff to Treble on our Xperias :fingers-crossed:
Miustone said:
It is much better right now. Full Camera 2 API Support including RAW and with the right APP like Open Camera do You have full Control of everything. The Sleep Dead Bug is with AEX no problem btw. Just enable the Always on Display Option and it will never sleep. Battery is pretty good and i get over the whole day with LTE+, Wifi and 4hrs+ Display usage. The Treble Kernel is really good and with some fine tuning with Kernel Adiutor is everything even better
I'm playing right now with the Vendor Partition eg. the build.prop and gained already some nice optimizations like better responding Ok Google Commands and better Noise Reduction. I think there will come soon some good stuff to Treble on our Xperias :fingers-crossed:
Click to expand...
Click to collapse
Cheers for the always on display tip, aex will be my daily driver now.
Kang kernel
By Sjll
Notice: Beware of bricking device!
This a new kernel for stock 10. It's aim to optimize the kernel and provide better user experience.
I had cherry-picked some commits from other SDM845 devices like M i8 and Oneplus 6T. So it's a fusion kernel, though I don't know whether these commits could improve our performance.
I share the source codes, so you could tweak the kernel by yourself. Ok, don't forget to share your work with us.
Download: Github
Note:
1. For XZ2, boot.img already included Magisk.
2 Internal problem is normal, ignore it.
CAF Version: LA.UM.8.3.r1-07600-sdm845.0.
Linux Version:4.9.206-r25-rel
Recommand to use EX kernel Manager
Feature:
1. GPU OC to 835 Mhz.
2. Thanks: Hide unlocked state from @j4nn
3. Qcacld wlan driver.
4. Remove useless drivers.
5. zram to lz4.
6. Increase priority of RT thread.
7. AVB flag removed.
8. WireGuard support.
9. Disabled some logs in kernel.
10. Newer CAF buff and Linux version.
11. Cpufreq and drm drivers optimization.
12. Schedutil optimization.
13. Energy model improved.
14. New I/O governor (Maple & Zen)
15. Blu_schedutil CPU governor( More Powersave ) Need to enable manually
16. IOsched optimization.
17. DTS eagle driver.
18. KLAPSE Color manager. Need EX kernel Manager
19. boeffla_wl_blocker supported.
20. adrenoboost supported, disable it by default.
21. etc..
How to flash:
HTML:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Vbmeta.img see Attach Files
If there is a dtbo.img, then:
HTML:
fastboot flash dtbo dtbo.img
I provide a new thermal configuration, see Attach Files, download it and replacing the same file in vendor/etc. You will get the full performance of SDM845.
Source code: Github
ROM OS Version: 10.0
ROM Kernel: Linux 4.9
Contributors
Sjll
Created 2020-02-26
FIRST! Muahahaha
Thank you like always.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Is it possible to port it on aosp10/los17 with osmosis anykernel?
thanks! can I flash on xz2 compact h8314?
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
It's the stock kernel
Completely incompatible with the SODP project
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
No, this kernel is only for stock, not SODP.
nikkdib said:
thanks! can I flash on xz2 compact h8314?
Click to expand...
Click to collapse
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Faruk.ErdaL said:
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
Click to expand...
Click to collapse
Thanks, if there is any bugs, feedback to me please. I will try to solve it.
Sjll said:
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
Click to expand...
Click to collapse
Yay
Nice, I wanted to look into TWRP at weekend
You could try to set
ro.debuggable=1
ro.adb.secure=0
Or build an -eng TWRP.
Sjll said:
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Click to expand...
Click to collapse
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
nikkdib said:
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
Click to expand...
Click to collapse
Done, try it and feedback, thanks.
Sjll said:
Done, try it and feedback, thanks.
Click to expand...
Click to collapse
i need to patch with magisk manager first if i want root yes?
nikkdib said:
i need to patch with magisk manager first if i want root yes?
Click to expand...
Click to collapse
Yes, you can. It should work fine with Magisk.
Sjll said:
Yes, you can. It should work fine with Magisk.
Click to expand...
Click to collapse
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
nikkdib said:
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
Click to expand...
Click to collapse
Done, try V1.5 please.
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
After first crash files in /sys/fs/pstore giving you the crash reason
MartinX3 said:
After first crash files in /sys/fs/pstore giving you the crash reason
Click to expand...
Click to collapse
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Faruk.ErdaL said:
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Click to expand...
Click to collapse
After crash go into Fastboot mode and flash the working kernel back (with magisk)
Then the device boots and you get the files
Just don't boot one time too much or the pstore will be wiped.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
For XZ2, it already included Magisk. Internal problem is normal, just ignore it. All works fine for me.
Provide your phone type please.
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...
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021
Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5
Has anyone tried it yet?
DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.
Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.
How does Resurrection Remix compare to CrDroid?
asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.
hockeymikey said:
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.
Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere
Before you get started,
i am not responsible for bricking device, dead sdcards,
muted alarm, or even thermonuclear war.
YOU chose to do this modification,
IF you point your finger to me to brick your device,
i will laugh at you.
This is GSI port from Official Havoc OS 2.9 by @vince31fr
Supported Devices
J701X
J730X
J600X
J530X
Details
Debloated /system 1037MB to 754MB
Pixel Launcher instead of Lawnchair
Includes SF-VENDOR 3.0 (Changelogs few days later)
Added M10 Fingerprint
Build.prop tweaks
No Gapps included, flash Open GApps ARM, 9.0, Pico
0.9GB /System with GApps Pico
Credits
Me for SF-VENDOR and Editing.
@vince31fr XDA for GSI
@ananjaser1211 for Cronos Kernel
Installation steps
You need Latest TWRP 3.4.0 or higher, or OFox 11.0
Flash Exynos7870_CreateVendor_2.0.zip
Flash HAVOC_REPARTITIONER.zip
Reboot recovery
Format data, Wipe Dalvik, Cache, System, Vendor, Data, Internal storage
And Flash Havoc-OS_2.9_J6-J5_J730_J701.zip
(Optional) Flash OpenGapps (Needed for Google Apps)
Reboot and Enjoy!
Bugs
HW Keys (Use NavBar instead)
Stretched Camera in J701 (Use 720p camera to fix this)
Downloads
GDrive
Mega
Telegram Support;
SF-GROUP
Everything Allowed but; Respect others. No NSFW/ Instant ban. No Ads. Enjoy
t.me
Contributors
@ichbinahmet
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 2.9
YY-DD-MM
Created 2021-30-09
Last Updated 2021-20-10
reserved
Thank you, but I've got bootloop. SM-J730F
Spargatorul said:
Thank you, but I've got bootloop. SM-J730F
Click to expand...
Click to collapse
Do you have /vendor partition?
You should flash Create Vendor from Project Spaget.
Im using same device, stable.
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
You using wrong recovery.
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Use TWRP 3.5.0
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Btw, ROM updated, read description, also use lastest TWRP .
Enjoy!
ichbinahmet said:
You using wrong recovery.
Click to expand...
Click to collapse
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Spargatorul said:
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Click to expand...
Click to collapse
Yes, inthread download links updated.
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
how to fix no audio?, j701f
Spargatorul said:
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
Click to expand...
Click to collapse
Probably you using custom kernel Kraken.
Flash latest from Magisk github
ichbinahmet said:
Probably you using custom kernel Kraken.
Flash latest from Magisk github
Click to expand...
Click to collapse
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Spargatorul said:
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Click to expand...
Click to collapse
Yes KRAKEN kernel breaks ROM on magisk flash, so you need to use Cronos kernel
Im trying to fix that broken loudspeaker bug.
Thanks for reporting
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
So7urno said:
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
Click to expand...
Click to collapse
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
ichbinahmet said:
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
Click to expand...
Click to collapse
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
So7urno said:
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
Click to expand...
Click to collapse
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
ichbinahmet said:
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
Click to expand...
Click to collapse
That fixed the problem! Thanks!
It seems I was using a wrong TWRP....
Most of the bugs I mentioned before are gone\fixed (loudspeaker, whatsapp keypad, sdcard).
except the video recording with the "opencamera" app (recorded videos are unplayable with messed up time lapse),
I tried also "HD camera" app from playstore with same problem.
But if I record video directly through whatsapp videos are ok.
Everything else seems working fine thought, stable and fast !
are you planning to work\fix the "(HW Keys (Use NavBar instead)" bug?
I Will keep using this rom for now, great job @ichbinahmet !