What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
S-Pen Basics
Call Recording
HWC
Signal Indicator
GPS
HDMI
NFC
MTP
What's not working:
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Bugs:
S-Pen/Mouse will cause small graphical glitches during button animations sometimes.
Instructions:
Make sure TWRP has been installed and functional
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the latest build (then gapps and magisk if needed)
Reboot
THE VENDOR.IMG IS PROVIDED AS PART OF THE ROM. FLASHING ANOTHER VENDOR WILL CAUSE A BOOTLOOP.
How to update builds?
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk, vendor etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Galaxy Note 9 Exynos (N960F): https://mega.nz/#!P6gT1KrZ!qMh3yx9EI2vipcISnfm19LulRZT73Ns-N2oISlM0H5s
Google Apps: https://opengapps.org/
Changelog:
28/01/2020
January Patch
SELinux Enforcing
Apex Enabled
Kernel upstreamed to 210
New WiFi Firmware
OTA enabled
Q friendly partition mounts
New ramdisk
GPS Locking more reliable
New bluetooth HAL
Offline charging fixed
New Lights HAL to stop max brightness bug
08/01/2020
MTP/USB should be a bit more stable
Fixed NFC (Requires factory reset if on earlier build)
WiFi **should** behave a bit more.
23/12/2019
Hardware decoding of UHD video no longer lags/stutters
Bluetooth call audio working
UHD video recording with the camera app fixed
Built against LOS december sources
20/12/2019
Wireless hotspot now enables
Kernel upstreamed to 4.9.206
19/12/2019
DRM protected content will no longer crash the device (YouTube, Spotify, Netflix, etc)
SFingerprint scanner now works properly
18/12/2019
GPS is now able to get a more accurate location
Sensors work (gyro, light sensor, etc)
Fixed issue with Gapps causes bootloop after installing an update
16/12/2019
First Build
Telegram Group:
[N960F][LineageOS 17.0][UNOFFICIAL]
Paypal:
abtekk
Source Code: https://github.com/LineageOS/
Kernel: https://github.com/evilexecutable/android_kernel_samsung_universal9810-crown/tree/lineage-17.0
ROM OS Version: 10 (Q)
ROM Kernel: Linux 4.9.197
XDA:DevDB Information
Lineage-17.0, ROM for the Samsung Galaxy Note 9
Contributors
abtekk
Source Code: https://github.com/evilexecutable/android_kernel_samsung_universal9810-crown/tree/lineage-17.0
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Stable Release Date: 2020-01-28
Beta Release Date: 2019-12-16
Created 2019-12-16
Last Updated 2020-01-29
Camera is not working right now. To fix:
adb shell
mount -o rw,remount /vendor
cd /vendor/lib
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so.1
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so.1.1
cd /vendor/lib64
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so.1
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so.1.1
Then reboot, then camera will work.
It will be fixed really soon.
Edit: Its fixed. Redownload it.
Super tempting... Thanks for this
Good job
Well done , happy to see progress :highfive:
Sent from my Samsung Galaxy S9+ using XDA Labs
Vodes said:
Camera is not working right now. To fix:
adb shell
mount -o rw,remount /vendor
cd /vendor/lib
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so.1
ln -s /vendor/lib/egl/libGLES_mali.so libOpenCL.so.1.1
cd /vendor/lib64
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so.1
ln -s /vendor/lib64/egl/libGLES_mali.so libOpenCL.so.1.1
Then reboot, then camera will work.
It will be fixed really soon.
Click to expand...
Click to collapse
As of this message, this is no longer necessary. If you downloaded a build earlier, please redownload it from the link in the thread.
Will try this on next update
The only apps downloadable from OpenGapps.com are for version 9.0 or older. The version 10 download is grayed out. It says, "Version 10.0 requires a patched ROM for proper WebView Support".
That said, I'm trying the ROM out anyway.
BRB
_________
Installer doesn't work. TWRP says:
Updater process ended with ERROR: 7
Error installing zip file '........(etc)'
E3004: This package is for device: crownltexx, this device is starlte.
Starting LOS 16 restore now.....
crhylove said:
The only apps downloadable from OpenGapps.com are for version 9.0 or older. The version 10 download is grayed out. It says, "Version 10.0 requires a patched ROM for proper WebView Support".
That said, I'm trying the ROM out anyway.
BRB
_________
Installer doesn't work. TWRP says:
Updater process ended with ERROR: 7
Error installing zip file '........(etc)'
E3004: This package is for device: crownltexx, this device is starlte.
Starting LOS 16 restore now.....
Click to expand...
Click to collapse
Well the rom is for the note 9 only right now. You tried to flash it on a S9.
Yep. I'm an idiot.
crhylove said:
Yep. I'm an idiot.
Click to expand...
Click to collapse
S9/+ released here
https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
New build uploaded
Changelog:
18/12/2019
GPS is now able to get a more accurate location
Sensors work (gyro, light sensor, etc)
Fixed issue with Gapps causes bootloop after installing an update
abtekk said:
New build uploaded
Changelog:
18/12/2019
GPS is now able to get a more accurate location
Sensors work (gyro, light sensor, etc)
Fixed issue with Gapps causes bootloop after installing an update
Click to expand...
Click to collapse
This is it :laugh:
So battery life/performance? smoothness? Comments in general?
Changelog:
19/12/2019
DRM protected content will no longer crash the device (YouTube, Spotify, Netflix, etc)
Fingerprint scanner now works properly
Temp fix for MTP
To make MTP working go to system/system/build.prop and change
persist.sys.usb.config=adb,mtp
To
persist.sys.usb.config=mtp
and reboot
New Note 9 build uploaded
- Wireless hotspot now enables
- Kernel upstreamed to 4.9.206
There is no need to flash additional Vendor.zip package. Is this correct?
---------- Post added at 10:47 PM ---------- Previous post was at 10:38 PM ----------
crhylove said:
The only apps downloadable from OpenGapps.com are for version 9.0 or older. The version 10 download is grayed out. It says, "Version 10.0 requires a patched ROM for proper WebView Support".
That said, I'm trying the ROM out anyway.
BRB
_________
Installer doesn't work. TWRP says:
Updater process ended with ERROR: 7
Error installing zip file '........(etc)'
E3004: This package is for device: crownltexx, this device is starlte.
Starting LOS 16 restore now.....
Click to expand...
Click to collapse
Are we to use Opengapps version 9.0 then?
Gandicela said:
There is no need to flash additional Vendor.zip package. Is this correct?
---------- Post added at 10:47 PM ---------- Previous post was at 10:38 PM ----------
Are we to use Opengapps version 9.0 then?
Click to expand...
Click to collapse
No, there's a version 10 somewhere.... just not on the opengapps site. I got it from telegram I think.....
https://web.telegram.org/#/[email protected]
New Note 9 Build uploaded
23/12/2019
- Hardware decoding of UHD video no longer lags/stutters
- Bluetooth call audio working
- UHD video recording with the camera app fixed
- Built against LOS december sources
Related
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attempting since monday tonight.
I'll explain more and I'll give more shots on working.
My issue now is to build the boot, recovery image to flash and boot it. The jolla sailfishos as a GUI operating system on Galaxy S3 I9300 model.
FIY : filename = sfa-i9300-ea-1.0.8.19-my1.tar.bz2
Instructions for chroot co,pilation on ubuntu amd64 x86_64 bit:
Code:
sudo mkdir -p /srv/mer/
mkdir -p $HOME/mer/
nano .bashrc
export $MER_ROOT=/srv/mer/
export $MER_ROOT=$HOME/mer/
ctrl +x to save and y
but type sudo apt-get install -y curl
for do the downloading file.
next do the following commands on terminal:
export $MER_ROOT=/srv/mer/
cd $HOME; curl -k -O https://img.merproject.org/images/mer-sdk/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
sudo mkdir -p $MER_ROOT/sdks/sdk ;
cd $MER_ROOT/sdks/sdk ;
sudo tar --numeric-owner -p -xjf $HOME/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
echo "export MER_ROOT=$MER_ROOT" >> ~/.bashrc
echo 'alias sdk=$MER_ROOT/sdks/sdk/mer-sdk-chroot' >> ~/.bashrc ; exec bash ;
echo 'PS1="MerSDK $PS1"' >> ~/.mersdk.profile ;
sdk
Now, do the following instructions:
$HOST>
nano $HOME/.hadk.env
export MER_ROOT="[/home/$user]"
export ANDROID_ROOT="$MER_ROOT/android/droid"
export VENDOR="[samsung]"
export DEVICE="[i9300]"
ctrl +x and y for save it.
nano $HOME/.mersdkubu.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
export PS1="HABUILD_SDK [\${DEVICE}] $PS1"
hadk
save it again
nano $HOME/.mersdk.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
hadk
now save this file.
Now in ctrl + alt + x, it will show a terminal:
type this:
sdk
type your password
hadk
TARBALL=ubuntu-quantal-android-rootfs.tar.bz2
curl -O http://img.merproject.org/images/mer-hybris/ubu/$TARBALL
UBUNTU_CHROOT=/parentroot/$MER_ROOT/sdks/ubuntu
sudo mkdir -p $UBUNTU_CHROOT
sudo tar --numeric-owner -xvjf $TARBALL -C $UBUNTU_CHROOT
hadk
ubu-chroot -r /parentroot/$MER_ROOT/sdks/ubuntu
exit
git config --global user.name "Your Name"
git config --global user.email "Your email"
back again for
hadk
cd $HOME
mkdir -p $HOME/mer/android/droid
repo init -u git://github.com/mer-hybris/android.git -b hybris-10.1
repo sync
after this, you will have HABUILD_SDK
DEVICE=i9300
export $DEVICE
source build/envsetup.sh
breakfast $DEVICE
now type
make hybris-hal
But now as a ota file for flashing on i9300, in this last 2 days in my laptop core2Duo Extreme I'm facing overheating.
So, everyone can test it.
Code:
A little change on mount fixups.
Go to the directory hybris/hybris-boot
nano mount-fixups on i9305| encore)
put the "i9305" | "encore" | "i9300")
Script for booting sailfishingos on an android terminal. This script is to mount the binds folders and for fixing for preventing the /dev/null issue when we all boot the chroot sailfishos.
name of the script : sailfishos.sh - made it on the /extsdCard/ folder.
1) nano /extSdCard/sailfishos.sh and copy the following code
2) ctrl +x to save it
3) bash sailfishos.sh
Code:
su
mount -o bind /dev /data/.stowaways/sailfishos/dev
mount -o bind /proc /data/.stowaways/sailfishos/proc
mount -o bind /sys/ /data/.stowaways/sailfishos/sys
chroot /data/.stowaways/sailfishos/ /bin/su -
echo "nameserver 8.8.8.8" > /etc/resolv.conf
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
See folders on it.
PS: I'll give more shots also more instructions very soon. Thanx.
Another PS: I'll give more news about Jolla sailfish os very soon.
But I need to tell this, I've got i9300 defconfig kernel for Jolla sailfishos very similar to defconfig i9305 kernel and I got it compiled with very success on hadk Ubuntu chroot on mine Ubuntu 14.04 LTS version.
astronfestmon said:
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attemptinh since yesterday tonight.
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
sees folders on it.
Click to expand...
Click to collapse
Screenshots?
Sent from my SM-G900F using XDA Free mobile app
Fantastic... I'll give a try. Plz provide some more details, screenshots & new features from your currently running sailfish os. Thanx for sharing
i fed with adb commands & not able to flash
Uhm ... I gonna wait for this ...
Sent from my SM-G900F using XDA Free mobile app
how to install ?
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
astronfestmon said:
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
Click to expand...
Click to collapse
any update on this?
I followed the above procedure and I can see the Sailfish version and the files list from adb. What next?
EDIT: Just saw your PS in OP
In the end of the week probably I'll release the boot kernel working on.
astronfestmon said:
In the end of the week probably I'll release the boot kernel working on.
Click to expand...
Click to collapse
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
astronfestmon said:
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
Click to expand...
Click to collapse
It would be great if you could make it to boot.
I will try to compile the kernel with CONFIG_CMDLINE="console=tty0" . I'm hoping that would direct kernel panic message to the screen so we could idenfity what the problem is with booting hybris-boot.img
So... Any development?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
astronfestmon said:
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
Click to expand...
Click to collapse
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
redrum781 said:
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Click to expand...
Click to collapse
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
rusty88 said:
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
Click to expand...
Click to collapse
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
MaxAndroided said:
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
Click to expand...
Click to collapse
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
msri3here said:
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
Click to expand...
Click to collapse
yes @msri3here technically that is what i'm doing, its using RIL lib based on cm10.1.3 that was working fine before I flash sailfish, but on sailfish the log that RIL daemon dumps is really a mess and haven't figure out why is failing. One thing that I've notice is that RILD (one of its child process) creates the socket at /dev/socket/rild but it's killed afterwards, the sockets disappear and the process restarts all over again
Stracing RILD is not helping either as it seems that everything is Ok.
I'm trying to buy a new smartphone for day to day use so I can dedicate more time to debug on my i9300.
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
tried your rom but stuck on "samsung galaxy s 3 gt-i9300" screen nothing is happening plus if i touch the screen i get a response from the capacitive buttons but thats all
Does anybody know current stage Lineage 15.1 for x2? Is it usable after compiling as is, or some fixes are still needed to get it bootable and usable?
There is already a LOS 15.1 thread and please delete this thread from here.
giaur said:
Does anybody know current stage Lineage 15.1 for x2? Is it usable after compiling as is, or some fixes are still needed to get it bootable and usable?
Click to expand...
Click to collapse
Heyyo, it was bootable yes but right meow I'm currently having issues and attempting to synchronize from scratch again. Not sure if I changed something or if a repo sync is causing issues.
Currently moto999999 and I are the only people trying to fix bugs on the x2 for lineage-15.1... So any extra help is appreciated.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
[email protected] said:
There is already a LOS 15.1 thread and please delete this thread from here.
Click to expand...
Click to collapse
If you're taking about the LineageOS 15.1 blue thread I don't think luchetto was using official lineage-15.1 sources so his build would never be official. It's just a build he was working on.
The official lineage-15.1 is currently only being worked on by moto999999 and I... Hence me saying if anyone wanted to help fix bugs with us the assistance would be appreciated.
I haven't bothered making a thread about it since there's still a bit of work to be done.
Or if you're taking about the Lineage-15.0 thread by andr68rus? It has been long since discontinued and he no longer develops for the Le Max 2 as he now owns a Xiaomi Mi Mix 2 (and a smexy device it is).
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
@giaur I forgot to mention but here is my local manifest and my build scripts if you wish to help or if anyone else wants to help.
https://github.com/lineage-o-x2/local_manifests
For now I am unable to compile Lineage 15.1 sources. Do you have any working build?
giaur said:
For now I am unable to compile Lineage 15.1 sources. Do you have any working build?
Click to expand...
Click to collapse
Heyyo, sorry for late reply. Please check the github link in my previous post.
Do you have telegram? We use that for LeEco devs to communicate
ThE_MarD said:
Heyyo, sorry for late reply. Please check the github link in my previous post.
Do you have telegram? We use that for LeEco devs to communicate
Click to expand...
Click to collapse
Thanks for info. I'm planning to launch daily builds, as soon as I manage to compile sources. I will try your manifest tomorrow, mine contains TheMuppets only. I own already set server +script to automatically upload builds to mega.nz.
I don't have Telegram, but I can create account
Almost there... something happened with Jack, but I'm not sure what exactly - the same config was working to compile Nougat:
Code:
[ 83% 81888/98073] Building with Jack: /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack
FAILED: /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack
/bin/bash -c "(rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack ) && (rm -rf /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc ) && (mkdir -p /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/ ) && (mkdir -p /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc ) && (rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (touch /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (if [ -d \"/home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/src\" ]; then find /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/src -name '*.java' >> /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list; fi ) && (tr ' ' '\\n' < /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list | build/tools/normalize_path.py | sort -u > /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq ) && (if [ -s /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq ] ; then export tmpEcjArg=\"@/home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq\"; else export tmpEcjArg=\"\"; fi; JACK_VERSION=4.32.CANDIDATE /home/michal/lineage15/out/host/linux-x86/bin/jack @build/core/jack-default.args -g -D jack.java.source.version=1.7 --classpath /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/sdk_v21_intermediates/classes.jack -D jack.import.resource.policy=keep-first -D jack.import.type.policy=keep-first -D jack.android.min-api-level=21 --output-jack /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack \$tmpEcjArg || ( rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/classes.jack ; exit 41 ) ) && (rm -f /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list ) && (mv /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc/java-source-list-uniq /home/michal/lineage15/out/target/common/obj/JAVA_LIBRARIES/org.apache.http.legacy_intermediates/jack-rsc.java-source-list )"
Connection to the Jack server timeout, retrying with debug
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 8076 (#0)
ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /root/.jack-server/server.pem
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* Operation timed out after 150000 milliseconds with 0 out of 0 bytes received
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
Machine has only 8 GB RAM, so I was forced to increase Jack cheap memory, like this:
Code:
JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"
This was enough to compile Nougat, maybe I will should try with larger value.
why r u opening seperate thread for asking it @giaur
shivatejapeddi said:
why r u opening seperate thread for asking it @giaur
Click to expand...
Click to collapse
Beceause there is no existing one? This thread is about issues with Lineage 15.1 compilation.
@ThE_MarD your manifest giving me error message:
Code:
fatal: duplicate path device/leeco/x2 in /home/michal/lineage15/.repo/manifest.xml
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
@ThE_MarD your manifest giving me error message:
Code:
fatal: duplicate path device/leeco/x2 in /home/michal/lineage15/.repo/manifest.xml
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
giaur said:
@ThE_MarD your manifest giving me error message:
With my previous manifest I had TheMuppets only included, build won't boot at all. Now I'm trying with your manifest, we'll see.
Click to expand...
Click to collapse
Hmm that's not my manifest amigo. I don't have a manifest.xml. I'd recommend reviewing that XML file or deleting it if there's nothing in there you need.
my manifest is local_manifest.xml
ThE_MarD said:
Hmm that's not my manifest amigo. I don't have a manifest.xml. I'd recommend reviewing that XML file or deleting it if there's nothing in there you need.
my manifest is local_manifest.xml
Click to expand...
Click to collapse
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
giaur said:
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
Click to expand...
Click to collapse
Downloaded, will test and report back.
---------- Post added at 10:16 AM ---------- Previous post was at 09:56 AM ----------
giaur said:
Of course, I mean "local_manifest", after applying it I got that error message. Anyway, compilation has been succeded, if anybody wish to try:
https://mega.nz/#!LV1HVBDC!q---2tIplvLJUFbVv4VKr-V_JHVpiJrXPykR-AwXKUU
Md5:
https://mega.nz/#!yUFnmDzL!OrNT-rpaLFagY3BJwZ_vyTKQcBcjs5kr39mMnYUpeCY
I hope no bootloop this time.
Click to expand...
Click to collapse
Well, No error in installation, but not boot.
With GAPPS they enter on boot animation but still there forever, without they not pass the boot logo.
Beackman said:
Downloaded, will test and report back.
---------- Post added at 10:16 AM ---------- Previous post was at 09:56 AM ----------
Well, No error in installation, but not boot.
With GAPPS they enter on boot animation but still there forever, without they not pass the boot logo.
Click to expand...
Click to collapse
Yes, I can confirm. I'm going to make new, fresh build. Probably Lineage bug, already fixed: https://github.com/LineageOS/android_device_leeco_x2/commit/fd453e976c4f9ff828bf83310c2bab6563491f96 we'll see.
ThE_MarD said:
Heyyo, it was bootable yes but right meow I'm currently having issues and attempting to synchronize from scratch again. Not sure if I changed something or if a repo sync is causing issues.
Currently moto999999 and I are the only people trying to fix bugs on the x2 for lineage-15.1... So any extra help is appreciated.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
If you're taking about the LineageOS 15.1 blue thread I don't think luchetto was using official lineage-15.1 sources so his build would never be official. It's just a build he was working on.
The official lineage-15.1 is currently only being worked on by moto999999 and I... Hence me saying if anyone wanted to help fix bugs with us the assistance would be appreciated.
I haven't bothered making a thread about it since there's still a bit of work to be done.
Or if you're taking about the Lineage-15.0 thread by andr68rus? It has been long since discontinued and he no longer develops for the Le Max 2 as he now owns a Xiaomi Mi Mix 2 (and a smexy device it is).
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
@giaur I forgot to mention but here is my local manifest and my build scripts if you wish to help or if anyone else wants to help.
https://github.com/lineage-o-x2/local_manifests
Click to expand...
Click to collapse
Thank you. I have LineageOS 15.1 sources already downloaded. I will sync x2 sources and try to help
Awesome! Glad to hear more people are jumping on board to help
If you have Telegram then please pm me I we have a developer chat group which is a little faster than these forums
New build up: https://mega.nz/#!fc9BmBQa!1u-Jv4nrLzAyCgPb8NcsGhz2tQ1gMtvvgjXRW31YIho
I'm confused. I'm pretty sure it booted, but after flashing it again only blue led and black screen. Or I just flashed different zip first time (so it booted). I am able to clean install rom I was before though. Totally confused. I've tried then 2 times to clean flash my build, not booting. Strange.
You can test and tell me if it works for you.
giaur said:
New build up: https://mega.nz/#!fc9BmBQa!1u-Jv4nrLzAyCgPb8NcsGhz2tQ1gMtvvgjXRW31YIho
I'm confused. I'm pretty sure it booted, but after flashing it again only blue led and black screen. Or I just flashed different zip first time (so it booted). I am able to clean install rom I was before though. Totally confused. I've tried then 2 times to clean flash my build, not booting. Strange.
You can test and tell me if it works for you.
Click to expand...
Click to collapse
Booted fine, now is OK.
Beackman said:
Booted fine, now is OK.
Click to expand...
Click to collapse
Strange
PREREQUISITE
- adb enabled [developer options]
- root [Magisk/SU]
- original /vendor partition [flashed with official update/firmware]
- File/Root Explorer
- adb for Windows [Minimal ADB and Fastboot, provided]
- UKA [Unpacker Kitchen for Android] - Send me a PM
- USB cable always connected
Reserved
You can do the same steps for the other logical partitions [system & product]
At the end you do :
System
tune2fs -L / /data/local/UnpackerSystem/system.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/system.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/system.new.img
adb shell
su
dd if=/sdcard/system.img of=/dev/block/dm-2
(just copy/past to avoid errors !)
Reboot your phone right away !
Product
must be renamed vendor because the Magisk Module still doesn't support this name yet ... just rename it vendor.img before taking any action ... and after creating your image, do :
tune2fs -L product /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/vendor.new.img
NOW you can rename it product.img
adb shell
su
dd if=/sdcard/product.img of=/dev/block/dm-0
Reboot your phone right away !
"Houston, we have problem!"
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
jeryll said:
"Houston, we have problem!"
View attachment 5232079
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
Click to expand...
Click to collapse
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Yes, you can do that for the 3 logical partitions ... this tutorial is for all devices with dynamic paritition aka super.img (not limited to poco x3 nfc !!!)
I will put a clean vendor.img later (with RW enabled and AVB-Verity Disabled)
I will put a modded version of Magisk 20.4 too if someone would use it (like me)
janhammer504 said:
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Click to expand...
Click to collapse
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
jeryll said:
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
Click to expand...
Click to collapse
Hi, flash an official MIUI for your device.
Do the dirty job and save your vendor.img
Reflash your rom !
(i have already uploaded a clean vendor.img here)
I close this thread too since a lot of features have been added to this work ... and since there are many disrespectful developers-like around who steal my work and give no credit !
Check my custom vendor thread to learn more about this work !
If you have any question, send me a PM, i will check first if you are not a troll : if you get no answer from me, then understand by yourself !
@janhammer504 Hi. For the sake of the community it's always sad to see someone taking their work from XDA.
If you've got issues with other people using your work without credit here on XDA you can always reach out to someone on the moderator team for help. Or better yet, one of us on the Developer Relations team. We can help you solve any disputes and make sure you get proper credit.
You can find a list of moderators here:
https://docs.google.com/document/d/1lK5rP103OL3StU3q9iqwX9LU_k8XABeSQIAT3EHCqgM/pub
PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD
RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch
the image you made is for enable rw or not?
my phone is poco x3 nfc surya
janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image
aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !
janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom :
updater process ended with error 7
pls help
aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk
Hello! After many years without development, today I'm sharing a new kernel with ZRAM and swap support for this device.
The kernel is based upon weritos' Cyanogenmod 13 kernel source code and should work on both rev. 1 and rev. 2 devices.
Installation procedure is as follows:
1. Download the latest TWRP, kernel build and modules.
2. Install the kernel and TWRP from ADB shell (the device must be booted into Android) or a terminal app:
Bash:
su (from a terminal app; not required from ADB shell)
cat </path/to/TWRP_image> > /dev/block/mmcblk0p13
cat </path/to/kernel_image> > /dev/block/mmcblk0p8
reboot recovery
3. Install the kernel modules:
Bash:
mount /dev/block/mmcblk0p21 /system
unzip -o </path/to/modules.zip> -d /system/lib/modules
4. Done! Reboot into Android.
NOTE: The < and > symbols should never be issued within the commands!
Version Information
Status: Beta (Bluetooth, camera recording and screen recording do not work.)
Created: 2021-05-11
Last Updated: 2021-05-12 (Import and enable Ultra KSM driver.)
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
@Krush206 it's saying can't open zip file on the last step, how to fix??
SerjSX said:
@Krush206 it's saying can't open zip file on the last step, how to fix??
Click to expand...
Click to collapse
fixed it, I was supposed to write:
Code:
unzip -o /sdcard/modules.zip -d /system/lib/modules
instead of:
Code:
unzip -o /storage/emulated/0/modules.zip -d /system/lib/modules
in TWRP terminal.
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not. @Krush206
not working
Turkish developers said:
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
Click to expand...
Click to collapse
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
SerjSX said:
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not.
Click to expand...
Click to collapse
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Krush206 said:
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Click to expand...
Click to collapse
Hi, thanks for your response. Just did i and looks like it worked, 59 total swap, used 58, and free 541.
Are you sure you checked the correct line? The total should be 255 (256), not 59.
can you compile a kernel for overclocking in stock room or cm 11 please our quttro needs it now
overclock kernel pls
Sorry for the delay. The battery of my device has swollen, so I cannot really check whether overclocking is possible or not.
However, though overclocking may be possible, it may cause system instability and crashes.
I could probably have a look at the code and see how to get it done, but I cannot post results and would not recommend overclocking.
The battery in my device was swollen, I found a battery and the best software for this device is 4.1.2. I want to try overclocking for this version. Bide 4.1.2 also does not play hd videos in the original software. Is there a code or a mod for this?
1.5 Ghz overclock pls
any update?
If you two, @Fever070720, @Turkish developers, are still looking into overclocking, please, send the output of the following command:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq