Related
let me explain my problem, i've created a .ftf (kernel for xperia x8) and it is boot up but i missed some files inside the ramdisk, so now i need to repack my new ramdisk folder into ramdisk file and i don't know how to do that .
Read my guide on how to compile and put together a custom kernel for the X8: http://forum.xda-developers.com/showthread.php?t=1923240
The method (whatever it is) you are following is not correct for any Android phone.
Oops. I guess it isn't mentioned there.
Basically what you have to do is open up a Terminal in Ubuntu. Navigate to your ramdisk folder (the one that contains the init.rc, init.usb.rc etc.). Then issue this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk
Grab the ramdisk from one directory above your ramdisk folder.
Sorry for the confusion.
sgt. meow said:
Read my guide on how to compile and put together a custom kernel for the X8: http://forum.xda-developers.com/showthread.php?t=1923240
The method (whatever it is) you are following is not correct for any Android phone.
Click to expand...
Click to collapse
i don't understund one thing, when i'm getting the ramdisk file? when compiling the rom?or the kernel?
i've compiled cm10.1 rom and i need to change the bootclasspath
You have to unpack a working kernel with DooMLorD's kernel.sin unpacker. You'll get the ramdisk. Then edit the BOOTCALSSPATH in init.rc.
sgt. meow said:
Read my guide on how to compile and put together a custom kernel for the X8: http://forum.xda-developers.com/showthread.php?t=1923240
The method (whatever it is) you are following is not correct for any Android phone.
Oops. I guess it isn't mentioned there.
Basically what you have to do is open up a Terminal in Ubuntu. Navigate to your ramdisk folder (the one that contains the init.rc, init.usb.rc etc.). Then issue this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk
Grab the ramdisk from one directory above your ramdisk folder.
Sorry for the confusion.
Click to expand...
Click to collapse
when i run the i get this error
bash: ../ramdisk: Is a directory
Name the folder that has the ramdisk contents something like "XYZ" and put it in another folder named "ABC". Then issue this command.
So basically the structure would be:
/ABC/XYZ/* /*ramdisk contents have been denoted by * */
And after issuing the command grab the ramdisk from ABC folder.
sgt. meow said:
Name the folder that has the ramdisk contents something like "XYZ" and put it in another folder named "ABC". Then issue this command.
So basically the structure would be:
/ABC/XYZ/* /*ramdisk contents have been denoted by * */
And after issuing the command grab the ramdisk from ABC folder.
Click to expand...
Click to collapse
yeah thank you now it's working but i think something is missing , can you help me in developed kernel for cm10.1 ?
i already compiled the rom but now i'm struggling with the kernel part , i can send you all the files for the ramdisk and if you can put together a working kernel it will be great and i can move on and fix the problems with the rom itself
Look man. I can download the source and help you compile the kernel and the ramdisk. But as Daveee10 has said, even if you get it booting, there are tons of things that need to be backported (which is extremely hard) for it to work properly. So it's almost like choosing a route that you know will lead to a dead-end. But I'll help anyway.
PM me.
Has anyone tried rebuilding Safestrap for the bionic?
Source is here:
https://github.com/Hashcode/android_bootable_recovery
The readme.md points you to the TWRP build thread:
http://forum.xda-developers.com/showthread.php?t=1943625
I have CM10.1 installed in ~/android/system. I've been building and loading it on my bionic, and that's working fine. Per TWRP instructions, I also rebuilt CWM recovery without error (make clean && make recoveryimage).
Reading through the TWRP instructions, it calls for replacing your bootable/recovery CWM image with the TWRP build tree. Rather than do this, I instead wanted to pull down SafeStrap's git repo into its own dir seperate from the CM10.1 build tree (for my own sanity), and use a symlink to make it look like I had.
I cloned the safestrap repo into ~/android/safestrap/android_bootable_recovery.
I renamed my ~/android/system/bootable/recovery directory (to recovery.orig) and symlink'd so that ~/android/system/bootable/recovery maps to ~/android/safestrap/android_bootable_recovery).
When I try to build (make clean && make recoveryimage), I get a couple of errors right away:
bootable/recovery/Android.mk:18: bootable/recovery/../../external/safestrap/safestrap.mk: No such file or directory
build/core/base_rules.mk:123: *** bootable/recovery: LOCAL_BUILT_MODULE and LOCAL_INSTALLED_MODULE must not be defined by component makefiles. Stop.
There is no ~/android/system/external/safestrap directory for that safestrap.mk. A find command shows that safestrap.mk doesn't exist in either ~/android/system/external, or in the SafeStrap source.
I have been assuming that CM10.1 targa branch was safestrap friendly, but I don't see any of the TWRP switches in any of the BoardConfig.mk files or anywhere else for that matter.
Is there a special CM10.1 branch that includes these TWRP-friendly tweaks, or are they sitting in someone's working copy...? If so, anyone care to share them?
In return, I'll write up a good build summary and perhaps we can get hashofcodes to add it to the readme.md...?
Thanks,
- Josh.
For SM-T285 users that want to build Lineage OS for their own device I have posted a complete build guide here:
https://github.com/lineage-gtexslte/build_guide
jedld said:
For SM-T285 users that want to build Lineage OS for their own device I have posted a complete build guide here:
https://github.com/lineage-gtexslte/build_guide
Click to expand...
Click to collapse
Thanks for the ROM update!
I started from scratch and when I compiled, I got this error:
fixdep: error opening config file: ../../../../../../kernel/samsung/gtexslte/scripts/genksyms/parse.tab.c: No such file or directory
I have had this error before and had to copy the file from another folder, but I should not have to do this.
So, I copied the file to folder where it was missing.
New error:
target Prebuilt: am (/home/gcrutchr/taba/out/target/product/gtexslte/obj/EXECUTABLES/am_intermediates/am)
Symlink: /home/gcrutchr/taba/out/target/product/gtexslte/system/bin/app_process -> app_process32
clang++: error: unable to execute command: Aborted (core dumped)
clang++: error: linker command failed due to signal (use -v to see invocation)
gcrutchr said:
Thanks for the ROM update!
I started from scratch and when I compiled, I got this error:
fixdep: error opening config file: ../../../../../../kernel/samsung/gtexslte/scripts/genksyms/parse.tab.c: No such file or directory
I have had this error before and had to copy the file from another folder, but I should not have to do this.
So, I copied the file to folder where it was missing.
New error:
target Prebuilt: am (/home/gcrutchr/taba/out/target/product/gtexslte/obj/EXECUTABLES/am_intermediates/am)
Symlink: /home/gcrutchr/taba/out/target/product/gtexslte/system/bin/app_process -> app_process32
clang++: error: unable to execute command: Aborted (core dumped)
clang++: error: linker command failed due to signal (use -v to see invocation)
Click to expand...
Click to collapse
What's your gcc version? might need to use gcc 6
jedld said:
What's your gcc version? might need to use gcc 6
Click to expand...
Click to collapse
gcc version 8.1.1 20180712 (Red Hat 8.1.1-5) (GCC)
gcrutchr said:
gcc version 8.1.1 20180712 (Red Hat 8.1.1-5) (GCC)
Click to expand...
Click to collapse
later versions of gcc may not work with lineage 14.1, I had to downgrade mine, though for another project.
you can do:
Code:
sudo apt-get install gcc-6 g++-6 g++-6-multilib
sudo update-alternatives --install
inform me if this works and I'll update my guide. Might consider making a docker based build if issues like this happen often.
jedld said:
later versions of gcc may not work with lineage 14.1, I had to downgrade mine, though for another project.
you can do:
Code:
sudo apt-get install gcc-6 g++-6 g++-6-multilib
sudo update-alternatives --install
inform me if this works and I'll update my guide. Might consider making a docker based build if issues like this happen often.
Click to expand...
Click to collapse
Actually, I am on Fedora Linux (uses less resources) and have been using gcc 8xx for some time. I compile LineageOS 14.1 for Note 3 (ha3g) and the Note Pro 12.3 (v1a3g) and have no problems. But, I will investigate further.
Ok...so I had issues building the kernel...could not find some include files.
So...I decided to use build_kernel.sh script to to make boot.img. The resultant file is about 1.4 MB smaller, there is no init file in the ramdisk folder and the boot.img-ramdisk.cpio.gz in the split_img folder is about 1/2 the size of your recent boot.img file.
Not sure when to go from here.
Okay, so I followed the instructions - after upgrading Fedora to v29 - but, this time I used Docker. Had to make some script changes for Fedora, but got most everything installed. The "work" directory is empty. I was able to make a working system.img that installed with the built .zip file. The kernel would not boot - hung on the logo screen. I restored the 10/17 boot.img and the system booted up. Now, I will work on the boot.img file. I did notice this time that the boot.img file was about the same size as the 10/17 boot.img file I downloaded. So, that's an improvement. I just finished modifying the build_kernel.sh file. So, I installed the kernel I made and it still hung on the logo screen. So, back to square 1 regarding the kernel.
gcrutchr said:
Okay, so I followed the instructions - after upgrading Fedora to v29 - but, this time I used Docker. Had to make some script changes for Fedora, but got most everything installed. The "work" directory is empty. I was able to make a working system.img that installed with the built .zip file. The kernel would not boot - hung on the logo screen. I restored the 10/17 boot.img and the system booted up. Now, I will work on the boot.img file. I did notice this time that the boot.img file was about the same size as the 10/17 boot.img file I downloaded. So, that's an improvement. I just finished modifying the build_kernel.sh file. So, I installed the kernel I made and it still hung on the logo screen. So, back to square 1 regarding the kernel.
Click to expand...
Click to collapse
Were you able to obtain a logcat with the failed boot? Possible issue is that the external kernel modules did not get compiled
jedld said:
Were you able to obtain a logcat with the failed boot? Possible issue is that the external kernel modules did not get compiled
Click to expand...
Click to collapse
Actually, not sure how I got it to compile. Having problems with docker. Cannot run python or any other dev command. Stuck as root user. So am trying to learn about docker. I do not think I was in docker when it compiled. Will get back to you after I figure this whole mess out.
27 October 2018
After reading the Docker documentation and playing with Docker, I removed it from Fedora. It is just too complicated to use even though it sounds simple. After removing Docker, I did a make clean and a make mrproper in the kernel folder. I ran 'brunch gtexslte'. The compile completed after I copied mkbootimg to the out folder - for some reason it is not getting copied there during the make process. This time the boot.img was over 9mb. It still will not boot. I will get log files today. I will also check to make sure the system files work with the good boot.img.
Question how do I update the system folder to the latest builds of lineage 14.1?
Your repo xml file restricts the source to your repo.
Okay!
Fixed boot.img not booting.
If you unpack boot.img, the file 'boot.img-imgtype' has an invalid image type. In the file, it says 'AOSP-PXA'.
It should say 'AOSP'.
I do not know where this is getting added. I have done a grep and could not find it.
As a side note, I used the build_kernel.sh script to make the kernel.
Question: How do I apply the security updates without manually following the (-) (+) in the diff file?
I am now able to do a complete make and install using the generated .zip file.
Here are the steps:
1. Setup your environment - I am using Fedora, but these instructions will work for any flavor of linux
2. Make sure you have the linaro gcc toolchain (32-bit) installed, and you have modified kernel/samsung/gtexslte/build_kernel.sh
3. Run: build/envsetup.sh, then brunch gtexslte
4. If the brunch stops near the end, copy mkbootimg from system/core/mkbootimg to out/host/linux-x86/bin
......or you can write a shell script to copy the file, as I did, before starting the build
5. After the build completes, cd into kernel/samsung/gtexslte
6. Run make mrproper, to clean the kernel folders
7. Run build_kernel.sh
8. After the kernel (zImage) is built, you need to make the boot.img
9. @jedld has posted how to do this in his build instructions
10. Now that you have a boot.img, you need to modify it.
11. Unpack boot.img
12. In the file 'boot.img-imgtype' , you need to change 'AOSP-PXA' to 'AOSP' - without the quotes
13. Repack boot.img
14. Replace boot.img in the lineage*.zip file with the one you just modified
15. Copy the lineage*.zip to you Tab-A, reboot into recovery and install it.
Here is my script for copying the mkbootimg file into the out folder, BEFORE I run brunch gtexslte:
if [ ! -d "out/host" ]; then
mkdir out/host
mkdir out/host/linux-x86
mkdir out/host/linux-x86/bin
fi
cp system/core/mkbootimg/mkbootimg out/host/linux-x86/bin
@jedld
Update on normal kernel build:
The reason the boot.img - when building via brunch gtexslte - will not boot is a bad zImage. If I replace the zImage from a bootable boot.img, the bad boot.img will boot okay.
Now I need to figure out what the problem is.
you can get the incremental diffs from linux.org
jedld said:
you can get the incremental diffs from linux.org
Click to expand...
Click to collapse
Is this for kernel changes or security patches?
gcrutchr said:
Is this for kernel changes or security patches?
Click to expand...
Click to collapse
My mistake, I meant kernel.org not linux.org. The incremental diffs contain changes to the mainline kernel which can contain security fixes and/or bug fixes. This is different from android specific patches which google releases separately as kernel patches. The kernel started out from the stock sources provided by samsung on 5.1.1 and then I added google's N and Oreo patches on it (patches related to selinux and oreo binder enhancements). I also added incremental diffs from kernel.org, it started out at 3.10.58 and then I applied incremental diffs until I got to 3.10.107. Unfortunately 3.10 is EOL now, upgrading the kernel to the 4.10 series will take a lot of work.
The SM-T285 Lineage OS is excellent. Is it possible to get the FM radio working? I have tried everything but can't get it to work. I would appreciate your help.
akasarf said:
The SM-T285 Lineage OS is excellent. Is it possible to get the FM radio working? I have tried everything but can't get it to work. I would appreciate your help.
Click to expand...
Click to collapse
It's probably not implemented in the kernel.
Just downloaded Radio FM from PlayStore and installed it. It works!!
I meant if there is a working FM radio tuner app that works without the internet on Lineage
gcrutchr said:
It's probably not implemented in the kernel.
Just downloaded Radio FM from PlayStore and installed it. It works!!
Click to expand...
Click to collapse
[Ubuntu Touch Rolex]
Requirment:
-PC/Laptop with linux os(installed adb fastboot and python)
-Format Data(so backup ur data)
Whats Working:
-Ril
-Wifi
-Vibration
-sdcard
-led
-notification
-sound
-phone
-gps
-other
whats not working:
-bluetooth(module not compile missing header issue)
-some GUI app cant open(apparmor issue)
-you tell me
Download Links:
Rootfs:
https://ci.ubports.com/job/xenial-h...-touch-hybris-xenial-edge-arm64-rootfs.tar.gz
halium-boot:
Deleted because new update will pushed
halium-system.img:
Deleted because new update will pushed
How to install(is different with normal rom install)
-firts download offcial twrp https://dl.twrp.me/rolex/twrp-3.3.1-0-rolex.img.html
-then flash official twrp
-and then reboot into fastboot mode
-in computer exe command "fastboot flash boot halium-boot"
-after flash reboot into recovery and mount data partition
-in computer terminal execute "git clone https://gitlab.com/JBBgameich/halium-install.git && cd halium-install"
-then execute "./halium-install -p ut "path to rootfs" "path to halium system.img""
-The script will copy and extract the files to their proper places, then allow you to set the phablet user’s password.
-then after install complete reboot your phone
Build by @DarknesShiddenorg
sorry for my bad english
DTANDKERNELSOURCE:
https://github.com/areyoudeveloper1/
Credit:
Halium grub and ubport grub and muralivijay for dt and kernel sources
NOTE:
normally ubuntu touch not support hw or sw navigation used only full gesture navigation
This is not android
This Preview only many bugs here
[Ubuntu Touch Update Pushed]
Requirment:
-PC/Laptop with linux os(installed adb fastboot and python)
-Format Data(so backup ur data)
What's new:
-fixed Bluetooth but not perfectly (if cant enabled restart ur device)
-Fixed media server now multimedia app and camera can open
-added mtp(not working)
-added anbox support (untested)
-and many fixing I forgot
-rebased kernel
Bugs:
Mtp
Front camera and flashlight
Video Recorder
Download Links:
Rootfs:
Romoved because update will upload
How to install(is different with normal rom install)
-firts download offcial twrp https://dl.twrp.me/rolex/twrp-3.3.1-0-rolex.img.html
-then flash official twrp
-and then reboot into fastboot mode
-in computer exe command "fastboot flash boot halium-boot"
-after flash reboot into recovery and mount data partition
-in computer terminal execute "git clone https://gitlab.com/JBBgameich/halium-install.git && cd halium-install"
-then execute "./halium-install -p ut "path to rootfs" "path to halium system.img""
-The script will copy and extract the files to their proper places, then allow you to set the phablet user’s password.
-then after install complete reboot your phone
For Other Basic info:
http://docs.ubports.com/en/latest/porting/installing-16-04.html
Build by @DarknesShiddenorg
sorry for my bad english
DTANDKERNELSOURCE:
https://github.com/areyoudeveloper1/
Credit:
Halium grub and ubport grub
Nick for kernel
Murali for dt
NOTE:
normally ubuntu touch not support hw or sw navigation used only full gesture navigation
If apt-get error or openapp error
You must open terminal and execute "sudo mount -o remount,rw /"
This is not android
This Preview only many bugs here
I installed UT , and tryed to install anbox,but this not supported (rolex not supported (yet))
bius88 said:
I installed UT , and tryed to install anbox,but this not supported (rolex not supported (yet))
Click to expand...
Click to collapse
Absolutely u need edit anbox-install(locate at /use/bin/anbox-install)(in device check (get build prop info )) (don't ask me about that ) may will fix in next update
Twrp installer version released!
Download links:
Will update
How to install:
1.format data
2.install it
3.reboot
4.enjoy
Changes:
Revert added mtp fix
Note:
Default password is 123
If twrp say no os installed skip that because UT installed in data partition
Why can't I install Ubuntu on a system partition?
RotelyFars said:
Why can't I install Ubuntu on a system partition?
Click to expand...
Click to collapse
Ubuntu touch only installed in data partition
Dear developer, i tried ti install: fomatted data partition, twrp latest, but no boot: the device is stopped at mi logo.
I have the same problem. I just extracted archive, and pushed system.img, and rootfs.img to /data manually,and flashed hybris-boot.img
---------- Post added at 06:36 PM ---------- Previous post was at 06:26 PM ----------
I have dualboot Android(/system),Ubuntu(/data), and I swich the OS with reflashing the boot(android kernel/hibris-boot).
bius88 said:
I have the same problem. I just extracted archive, and pushed system.img, and rootfs.img to /data manually,and flashed hybris-boot.img
And Is It working, following this procedure? Thank you
Click to expand...
Click to collapse
Yes, I extracted archive, and inside i founded archive a.zip with to files inside(system,rootfs).
bius88 said:
Yes, I extracted archive, and inside i founded archive a.zip with to files inside(system,rootfs).
Click to expand...
Click to collapse
Thank you! The OS booted, now, following your steps. It Is really awesome OS .
bius88 said:
Yes, I extracted archive, and inside i founded archive a.zip with to files inside(system,rootfs).
Click to expand...
Click to collapse
Maybe some recovery not have unzip binary so a.zip can't extracted
Is libertine supported? If not, are you going to add this later?
vitalyavolyn said:
Is libertine supported? If not, are you going to add this later?
Click to expand...
Click to collapse
Already
Update Pushed
Changes:
Fix Mtp
Added mtp-enable
Added anbox-installer
Some fix
Download Links:
https://drive.google.com/file/d/1-1S-fLcEpH56gCvPS4CqhwrfNTa2qJVv/view?usp=drivesdk
How to install:
1.Format data (if ur device encrypted and no storage left)
2.just flash with twrp
3.reboot
Optional:
For Dualboot need replace recovery and recommend for 32 gb variant
Patch link:
https://drive.google.com/file/d/1--1rLHPVBo4hyLRE5P-prSGh2-iP9xpG/view?usp=drivesdk
How to Use:
Just flash with twrp
Some Notes:
MTP:
Q:how to enable Mtp
A:execute this command "sudo mtp-enable or mtp-enable"
Anbox:
Q:how to install anbox
A: 1."mount -o remount,rw /"
2.."apt update"
3."anbox-installer" if not work use sudo
Mtp works and Anbox works for me.
Functional keys doesn't seem to work
Everything mentioned above works, but i can't use my functional keys (Menu/Home/Back)
is there any fix?
sTiKyt said:
Everything mentioned above works, but i can't use my functional keys (Menu/Home/Back)
is there any fix?
Click to expand...
Click to collapse
Ubuntu Touch not support hw navigation just full gesture navigation
libertine-container-manager create --id vivid --name default
Enter password for your user in the Libertine container or leave blank for no password:
Password: (left blank)
libertine-container-manager:123: ERROR: create(): Failed to create container: 'No module named 'libertine.LxcContainer''
Cannot add container in libertine settings either...
Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Which GApps would you suggest?
I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.
Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.
I've set the state of the development to BETA due to quite good overall performance.
After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.
I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0
I'll take a look into it asap. Please be patient.
I can't find any reason for the crash; I'm sorry.
New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.
New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2
Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.
New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022
Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?
kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?
Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check
Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..
Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.