Develop Bugs

[DEV][WIP][MM]CyanogenMod 13 Port For Le 1 Pro X800 US/IN [09/29/16]

[I'm not responsible for bricked devices. Please read the steps!]​
LeEco probably won't provide new source code for their phones anytime soon, so i got really lucky by getting this to work just modifying kernel and updating some binaries.
There's still a lot of modifications to do and I'll update it as frequently as i can, even though i don't have a lot of free time, but bear in mind that this might also be as far as we can get without proper source from LeEco.
As of now the bugs are so many that i can't check them all.
Requirements:
. TWRP 3.0.2
. Brief knowledge of updating through TWRP(Backup/Wipe/Install)
. Le 1 Pro or Max (X800/X900) not CN.
Not working:
Flash/Torch
Speakers
GPS(Partially, doesn't seem to lock location)
Video Playback in Gallery App
Mute Switch
Skype
Battery Percentage
USB
...
Although it's not ready for daily use, most critical functions are working such as:
Microphone
Phone Calls
Cellular Data (3G/LTE/HSPA tested)
Back camera
Front Camera
HDR
HW acceleration
Bluetooth
How to install:
1. Download ROM -> Link to v0.2(Current)
2. Wipe Data / Factory Reset
3. Install ROM
4. Install GApps 6.0 (Link below)
5. Reboot
6. Wait 20~25 Minutes (Booting)
GApps -> http://opengapps.org/ -> Select ARM64 - 6.0 of your preference
Changelog:
v0.1 [09/19/16] - Pre-Alpha - initial release
v0.2 [09/29/16] - Pre-Alpha - Now based on Flour_mo Cm13 best for everyday use ROM; Fixed problem with META-INF and any possible bricking.
Please report every other bug, post your logcats with the indicated bug as well otherwise it'll be useless.
This rom should work with all international versions of Le 1 Pro and Le Max.
Screenshots

Thanks for the effort mate

v6ser said:
[Currently in Pre-Alpha, please read everything]
I'm able to boot CM13 Marshmallow, on the Letv Le 1 Pro after some modifications to the stock kernel.
As of now the bugs are so many that i can't check them all, but here are some.
Not working:
Flash/Torch
Speakers
GPS(Partially, doesn't seem to lock location)
Video Playback
Mute Switch
Skype
Battery(Doesn't seem to be recognized)
...
How to install:
1. Download ROM -> Link coming soon
2. Reboot Recovery
3. Wipe Data / Factory Reset
4. Install ROM
5. Reboot
6. Wait 20~25 Minutes (Booting)
Please report every other bug.
This rom should work with all international versions of Le 1 Pro and Le Max.
Screenshots(Coming soon).
Click to expand...
Click to collapse
Thanks a lot. You've made the first step. It's a shame for LeEco developers. When You arrive beta stadium I'll try Your work. For now I'm not able because my X800 is in daily use.

v6ser said:
[Currently in Pre-Alpha, please read everything]
I'm able to boot CM13 Marshmallow, on the Letv Le 1 Pro after some modifications to the stock kernel.
As of now the bugs are so many that i can't check them all, but here are some.
Not working:
Flash/Torch
Speakers
GPS(Partially, doesn't seem to lock location)
Video Playback
Mute Switch
Skype
Battery(Doesn't seem to be recognized)
...
How to install:
1. Download ROM -> Link coming soon
2. Reboot Recovery
3. Wipe Data / Factory Reset
4. Install ROM
5. Reboot
6. Wait 20~25 Minutes (Booting)
Please report every other bug.
This rom should work with all international versions of Le 1 Pro and Le Max.
Screenshots(Coming soon).
Click to expand...
Click to collapse
Very promising...
Gesendet von meinem LeTv 1 Pro mit Tapatalk

Link is up, enjoy

v6ser said:
Link is up, enjoy
Click to expand...
Click to collapse
Bricked my LeTV One Pro US like all other CM13 ROMs. So still a lot todo.
I had to use QFIL 429 to recover. Reflashed my C12.1 ROM again.
cheers
BetaHydri

BetaHydri said:
Bricked my LeTV One Pro US like all other CM13 ROMs. So still a lot todo.
I had to use QFIL 429 to recover. Reflashed my C12.1 ROM again.
cheers
Betaydri
Click to expand...
Click to collapse
Will send a fix in no time. Just wait a minute or so.
Error is in META-INF so it'll be a small download, sorry for the inconvenience and thanks for reporting
EDIT: Hotfix added to OP http://www88.zippyshare.com/v/513XLCMB/file.html

Thx @v6ser !

thanks for the effort
leEco dev are so bad!

Got this error when I follow the steps and try to install it..

Bjarnie said:
Got this error when I follow the steps and try to install it..
Click to expand...
Click to collapse
Can you see META-INF folder after you zipped it with hotfix? From the screenshot i get that the files are not there. This error only happens if the files are not there indeed lol
Thanks for reporting.

v6ser said:
Can you see META-INF folder after you zipped it with hotfix? From the screenshot i get that the files are not there. This error only happens if the files are not there indeed lol
Thanks for reporting.
Click to expand...
Click to collapse
lol. yes there is a meta inf folder.. haha I'm not that stupid:angel:

If someone managed to flash this ROM on US version?

I'm uploading a new version based on a different chinese CM13 rom.
It's less bloated and of course, it works without a hotfix since some people had problems with that before
EDIT: Link is up!

v6ser said:
I'm uploading a new version based on a different chinese CM13 rom.
It's less bloated and of course, it works without a hotfix since some people had problems with that before
EDIT: Link is up!
Click to expand...
Click to collapse
US or CN ROM?

US

v6ser said:
[I'm not responsible for bricked devices. Please read the steps!]​
LeEco probably won't provide new source code for their phones anytime soon, so i got really lucky by getting this to work just modifying kernel and updating some binaries.
There's still a lot of modifications to do and I'll update it as frequently as i can, even though i don't have a lot of free time, but bear in mind that this might also be as far as we can get without proper source from LeEco.
As of now the bugs are so many that i can't check them all.
Requirements:
. TWRP 3.0.2
. Brief knowledge of updating through TWRP(Backup/Wipe/Install)
. Le 1 Pro or Max (X800/X900) not CN.
Not working:
Flash/Torch
Speakers
GPS(Partially, doesn't seem to lock location)
Video Playback in Gallery App
Mute Switch
Skype
Battery Percentage
USB
...
Although it's not ready for daily use, most critical functions are working such as:
Microphone
Phone Calls
Cellular Data (3G/LTE/HSPA tested)
Back camera
Front Camera
HDR
HW acceleration
Bluetooth
How to install:
1. Download ROM -> Link to v0.2(Current)
2. Wipe Data / Factory Reset
3. Install ROM
4. Install GApps 6.0 (Link below)
5. Reboot
6. Wait 20~25 Minutes (Booting)
GApps -> http://opengapps.org/ -> Select ARM64 - 6.0 of your preference
Changelog:
v0.1 [09/19/16] - Pre-Alpha - initial release
v0.2 [09/29/16] - Pre-Alpha - Now based on Flour_mo Cm13 best for everyday use ROM; Fixed problem with META-INF and any possible bricking.
Please report every other bug, post your logcats with the indicated bug as well otherwise it'll be useless.
This rom should work with all international versions of Le 1 Pro and Le Max.
Screenshots
Click to expand...
Click to collapse
So there is hope to get a working CM13 for daily use. This phone with its nice hardware has deserved cm13. Nougat also would be nice, but cm 13 is an important step.

Windows does not recognize the terminal

the battery percentage is ok in TWRP mode

v6ser said:
[I'm not responsible for bricked devices. Please read the steps!]​
LeEco probably won't provide new source code for their phones anytime soon, so i got really lucky by getting this to work just modifying kernel and updating some binaries.
There's still a lot of modifications to do and I'll update it as frequently as i can, even though i don't have a lot of free time, but bear in mind that this might also be as far as we can get without proper source from LeEco.
As of now the bugs are so many that i can't check them all.
Requirements:
. TWRP 3.0.2
. Brief knowledge of updating through TWRP(Backup/Wipe/Install)
. Le 1 Pro or Max (X800/X900) not CN.
Not working:
Flash/Torch
Speakers
GPS(Partially, doesn't seem to lock location)
Video Playback in Gallery App
Mute Switch
Skype
Battery Percentage
USB
...
Although it's not ready for daily use, most critical functions are working such as:
Microphone
Phone Calls
Cellular Data (3G/LTE/HSPA tested)
Back camera
Front Camera
HDR
HW acceleration
Bluetooth
How to install:
1. Download ROM -> Link to v0.2(Current)
2. Wipe Data / Factory Reset
3. Install ROM
4. Install GApps 6.0 (Link below)
5. Reboot
6. Wait 20~25 Minutes (Booting)
GApps -> http://opengapps.org/ -> Select ARM64 - 6.0 of your preference
Changelog:
v0.1 [09/19/16] - Pre-Alpha - initial release
v0.2 [09/29/16] - Pre-Alpha - Now based on Flour_mo Cm13 best for everyday use ROM; Fixed problem with META-INF and any possible bricking.
Please report every other bug, post your logcats with the indicated bug as well otherwise it'll be useless.
This rom should work with all international versions of Le 1 Pro and Le Max.
Screenshots
Click to expand...
Click to collapse
Is there any chance we can get the source of this rom ?

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

[ROM][ALPHA] Unofficial Lineageos15.1

LINEAGE OS
This is an Alpha build of lineageos15.1
Working:
-RIL
-Bluetooth
-Camera (at least 1 of them)
Not Working:
-Probably selinux (did not try enforcing kernel yet)
-Probably encryption (logcat says it works...)
-Wlan (maybe bcs some files from vendor/vendor_system in /system are missing)
-2nd camera (fix could be to use micamera app)
-Probably more
Instructions:
-Download V9.6.11.0.ODLMIFF_8.1 original rom
-go to V9.6.11.0.ODLMIFF/images
-Replace boot.img, with boot.img
-Replace system.img and system_other.img with system.img
-use the flash_all script. THIS WILL WIPE ALL YOUR DATA, EVERYTHING! if you want to go back now (or later) just put the original images back again and use flash_all_except_storage
-Directly after the device reboots by itself, press vol up + power (u might have to hold it until device reboots again) to enter los recovery
-"factory reset--> wipe data"
-If you want TWRP "advanced-->reboot bootloader" and flash TWRP accordingly to thread, then u can flash gapps/mods.
-reboot
-give it time to boot
Source:
ROM
Device branch "los15"
msm8953-device
Kernel
To finish, I WON'T CONTINUE THIS ROM the trees are working, P vendor is there, an adaption to los16 should be possible based on that. Also, i prefer OMNIROM (which i will try to build next).
Thanks goes to:
-Google for the search engine as well as for the source code
-Cozzmi13 for taking some time to show me the basics.
-Lineageos
-Github
-ada12 for offering his help

thankssss

im wait until wlan fix, but thanks for your effort

CreateYourDream said:
im wait until wlan fix, but thanks for your effort
Click to expand...
Click to collapse
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works

It would be nice to have logs, then I could help.

If you ever need help with your omnirom build i would love to help out with everything that i can. Daisy really needs more support to be a very good device.

hi!
anyone know, is this build of LOS 15.1 support correct notch area?
and what about Onmi build?
i want give possible help if need)

Thanks for your work, I hope soon More roms for this great device

ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.

wertus33333 said:
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
Click to expand...
Click to collapse
not worked
and usb-tethering too

eremitein said:
sometimes after tapping screen blink with red border
Click to expand...
Click to collapse
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also

Can anyone give me the logs for the bugs?

Is this Rom abandoned?

ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
Yup. This phone is abandoned in general, which is a shame

eremitein said:
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
Click to expand...
Click to collapse
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Nice to know: The blinking red borders show layout updates, they flash in all eng (=developer) builds. If changing the build variant to userdebug (debuging enabled) or user (oem/production builds with few debuging enabled) they vanish.

ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
kftX said:
Yup. This phone is abandoned in general, which is a shame
Click to expand...
Click to collapse
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience. Also, all of us do this in our spare time and therefore it can take time. If you want to speed up the build, supply logs (clean install rom, install adb on pc, execute
Code:
adb bugreport > bugreportDATE.txt
or
Code:
adb logcat > logcatDATE.txt
, share the reports), error descriptions (like @eremitein) and/or read on how to build a rom for a device yourself.
eremitein said:
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Click to expand...
Click to collapse
oh, you already saw this xD

wertus33333 said:
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience.
Click to expand...
Click to collapse
Editing this out of respect even though none was shown.
Also, I would love to help but with the lack of a proper working TWRP (encryption, restore backup issues) I really can't give it the time needed with all the stuff I'd have to reinstall every time, since I need my phone up and working nearly 100% of the time. If a decent version TWRP is released, I'll gladly help.
Glad you're still working on this though, just don't act like we should've known that you still where when the thread was dead for months. Good luck.

wertus33333 said:
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Click to expand...
Click to collapse
successful build, always happy to help

is there any reason you build los 15.1 instead of 16?

skyline91 said:
is there any reason you build los 15.1 instead of 16?
Click to expand...
Click to collapse
At the time i built the rom only 8.1 vendor (8.1 official rom) was avaiable. as i'm not really experienced with android it was easier to build 8.1 rom instead of trying to port vendor to 9.0 (while 9.0 vendor would have defenitely be officially out in a month or 2 ) and build los16. porting the device tree from 15.1 to 16.0 should be easy. Also, i don't like los, i want omni .

[ROM][A515F/DS][OneUI 3.1 - S20 Port] Just4Fun v1

HELLo everyone...
After several weeks, months and before Android 12 released, i decided to share this ROM to this A51 community. Hopefully you guys enjoy it and don't offend me if the ROM is bad, so....let's get it ON.
Things to do before flashing:
1. Make sure you're on binary 5 (this ROM tested and using binary 5 vendor, so to avoid any broken or whatever error flash your device with latest firmware).
2. Backup your IMEI (highly recommended).
Flashing:
1. Clean flash is recommended. Flash kernel, flash J4F vendor and system.img, flash multy disabler (if necessary) then full wipe and also you can perform "typing YES" format. Reboot to recovery again, then flash as usual you guys always do (Magisk etc.).
ROM Features from S20 and Note 20 line up:
1. Samsung Dex (not full features coz need fix at kernel level).
2. Flagship live blur
3. Flagship edge lighting style
4. AirCommand (S pen)
5. LiveDrawing
6. Multy screen resolutions (HD+ - FHD+ - WQHD+)
7. 1000++ system fonts
8. Flagship sound quality and effects
9. Camera features unlocked (pro video etc.)
10. All original A51 features
11. Common tweaks here and there and so many possibility to unlock another S20 features
Bugs:
Minor glitch in pro mode video, and not really remember and deep testing everything, but hopefully still acceptable (hopefully ) but yeah..nothing's perfect, if you found one let's discuss together in A51 telegram group: https://t.me/samsunga51
Hall of Fame:
@MrWaehere for his awesome CRB kitchen
@VDavid003 and his rom TreeUI for my inspiration and countless help
@Yillié and his OFox recovery and also countless help and advise and ideas
@BlassGO and his Dynamic Installer, patches, advise and countless contributions (thanks for making AirCommand even greater lol)
@manudinath and his projects.
@Winb33 for fonts mod
@topjohnwu for Magisk
@ianmacd for multy disabler and TWRP
Stock Kernel Source
PM me if i forgot to mention someone.
Advise and Tips:
- It's normal during first boot if lags occurs, give the ROM some times to settle, finish your setup, update your apps and you good to go..
- It's better to avoid update in Galaxy store related to system app, such as MDE Service Framework, Samsung Core Services etc. It might causing conflict due to mixed up firmware. But anyway it's up to you.
- Please do not complain regarding app missing (getting debloated) and related to debloat. Because it's very hard to acomodate every person's taste. Bloatware is very Objective and absurd for each person and I know it's supposed to be using Aroma installer or any script but i don't have time that much to do that.
Download link:
**when you click this link and downloading, that's mean you're agree to all the consequences and i'm not responsible to anything - do with your own risk**
LINK

Pero peeps. Sorry for not being able to test all the stuff properly xD.

Yillié said:
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Click to expand...
Click to collapse
nah, you have doing so great/ thank you s much for everything.

Testing .

perro

Ole its already, nice

Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.

@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50

BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
Ia possible wirh This vendor run fingerprint perfectly in havoc

Badger50 said:
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
Click to expand...
Click to collapse
If run for You send details my friend

Someone knows how to pass CTSprofile in magisk with this rom?

gobblefunk said:
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
Click to expand...
Click to collapse
system and vendor.

BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
mhm...thanks for everything

jagpanzer said:
system and vendor.
Click to expand...
Click to collapse
Kernel 11 support this ROM?

Magisk 23.1
Download Magisk 706a4922 alpha apk
Download File Magisk 706a4922 alpha apk
apkadmin.com

Changelog magisk 23.1
DOWNLOAD VERSion ALPHA:
Magisk v23.1 (706a4922-alpha)
Changelog:
• Switch to zygisk to execute the deny list,
• Magiskhide has been completely removed
• Denylist Added
• Restart to take effect after changing the switch state of zygisk
• Major changes, some problems may occur, temporarily not pushed to the update channel
Others changes in APK:
[General] supports pure 64-bit devices
-[General] Support Android 12 emulator
-[Zygisk] code injection framework
-[General] Remove MagiskHide
-[General] Support simulator loading module
-[MagiskBoot] supports zImage format
-[MagiskBoot] Add zopfli encoder
-[MagiskInit] supports boot configuration
-[App] Repair installation function will now check whether the script under /data/adb/magisk/ is not updated
-[MagiskInit] supports some Meizu devices
-[MagiskSU] If supported by the kernel, use isolated devpts
-[MagiskSU] Fix pts configuration code, no additional sepolicy rules are now required
-[MagiskBoot] supports v4 boot image header format
-[MagiskInit] Support some OnePlus and Opal devices Oplus.fstab
-[App] The update module needs to be restarted, mark deletion is not allowed
-[App] Delete online warehouse
-[App] Add mount information to the saved log file
-[App] Adapt to Android 12 API level
-[App] Display running waiting pop-up window when hiding/resuming the application
-[Stub] Open source obfuscation function
-[Script] View and display the sepolicy rule folder of the module
-【App】Hide the screen overlay when you need to pop up the window. Android 12+
-[App] Delete the floating bottom bar and change it to a general bottom operation bar
-[General] Support compilation cache
-[General] Added rejection list function
-[App] Delete DoH
-[App] Delete SafetyNet

Can you please also make this rom for M30s ??
Because both have similar specs and same soc !

Bluetooth connect error

hacker812c said:
Kernel 11 support this ROM?
Click to expand...
Click to collapse
during testing i only test with BF2. you can try
Arya1999 said:
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Click to expand...
Click to collapse
sorry, no time.
Inomjon6940🇺🇿 said:
Bluetooth connect error
Click to expand...
Click to collapse
last time i try with old BT 4.0 earphone was fine and also BT call. will test again, on last build i've made changes and could be broke something

[ARM32] [9.0] [GSI PORT] Havoc OS 2.9

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 !