Here’s my build of LineageOS 15.1 for Raspberry Pi 3 Model B and Model B+ (bluetooth does not currently work on the new plus model). It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. This build currently uses Google’s SwiftShader software renderer so display performance is probably not what you’d expect. This build is not meant as a daily driver and it’s certainly not suitable for media device use.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://konstakang.com/devices/rpi3/LineageOS15.1/
lineage-15.1-20180706-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=5862345805528041370
md5:257ade2f567223cf792023e2d75e5b75
Sources:
lineage-rpi
Thanks:
Google for Android Things platform
peyo-hd and everyone who’s contributed to android-rpi
LineageOS team & everyone who’s been working on LineageOS 15.1
How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About phone -> Click ‘Build number’ several times
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: Settings -> Storage shows xx GB used by system. There’s unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. Settings app shows unallocated space as used by system which in reality it is not. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: You can execute the same script in TWRP terminal (Advanced->Terminal) if you have system partition mounted (Mount->System):
Code:
rpi3-recovery.sh boot
Or you can flash my recovery2boot zip in TWRP.
Q: How to install Google apps?
Download MindTheGapps-8.1.0-arm-XXXXXXXX_XXXXXX.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install MindTheGapps-8.1.0-arm-XXXXXXXX_XXXXXX.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)
Merged commits not mentioned in the changelog.
6.7. changelog:
update to Linux 4.14.53 kernel
add initial support for Pi 3 Model B+ (bluetooth does not currently work)
include TWRP 3.2.2-0 custom recovery (see FAQ how to boot)
build SwiftShader from source and update to master branch (improves graphics performance)
add support for encrypting the device
13.6. changelog:
update display drivers from Android Things 1.0
add support for USB webcams (UVC) with third party USB webcam apps
default to noop I/O scheduler
update to Linux 4.4.136 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2018 (merged)
7.3. changelog:
update display drivers from Android Things DP 7
update wifi firmware
update to Linux 4.4.120 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 March 2018 (merged)
3.3. changelog:
initial release
Previous builds:
AndroidFileHost
Wow thank you very much. gonna test this on the 3b plus
Does this build support RCA video out. ?
reversegear said:
Does this build support RCA video out. ?
Click to expand...
Click to collapse
Not sure, haven't tried and I don't even have a display with composite video in to test with. I'd say with LineageOS 14.1 and Linux 4.4 it's not supported (https://github.com/anholt/linux/issues/14). LineageOS 15.1 has a much newer kernel (4.14) but it doesn't even use the VC4 driver (Google's SwiftShader software renderer is used instead) so IDK.
You'd likely need to modify config.txt at least if you want to test this. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
On my 3B I'm not getting any HDMI video output. It just shows a black screen.
__init__ said:
On my 3B I'm not getting any HDMI video output. It just shows a black screen.
Click to expand...
Click to collapse
Some displays might require modifying config.txt. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
720p is the max resolution this build currently supports.
Pie on Pi! LineageOS 16 booted on Raspberry Pi3.
KonstaT said:
Some displays might require modifying config.txt. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
720p is the max resolution this build currently supports.
Click to expand...
Click to collapse
alright, so do I have to build myself? I don't have a screen that small
__init__ said:
alright, so do I have to build myself? I don't have a screen that small
Click to expand...
Click to collapse
No, config.txt is in the boot partition (FAT) so even Windows should mount it when you plug in the sdcard. You need to use a proper text editor, though.
KonstaT said:
No, config.txt is in the boot partition (FAT) so even Windows should mount it when you plug in the sdcard. You need to use a proper text editor, though.
Click to expand...
Click to collapse
All three partitions are EXT4 and even when I mount them using Ext2Fsd I don't see config.txt in any of them. (I don't see bootcode.bin or start.elf either.) :/
Edit: I found it - the boot partition wasn't mounted on my PC for some reason :/
---------- Post added at 12:49 AM ---------- Previous post was at 12:09 AM ----------
It's still not working... I changed hdmi_group to 2 and hdmi_mode to 46 (I also tried 48)
__init__ said:
All three partitions are EXT4 and even when I mount them using Ext2Fsd I don't see config.txt in any of them. (I don't see bootcode.bin or start.elf either.) :/
Edit: I found it - the boot partition wasn't mounted on my PC for some reason :/
---------- Post added at 12:49 AM ---------- Previous post was at 12:09 AM ----------
It's still not working... I changed hdmi_group to 2 and hdmi_mode to 46 (I also tried 48)
Click to expand...
Click to collapse
Like said 720p is maximum supported resolution with LineageOS 15.1 build. hdmi_mode 46 and 48 are 1440x900 so that's not going to work of course.
You can try with a different display or try LineageOS 14.1 build.
KonstaT said:
Pie on Pi! LineageOS 16 booted on Raspberry Pi3.
Click to expand...
Click to collapse
Is this just a tease, or are you maybe gonna make available, I hope.?
mrmazak said:
Is this just a tease, or are you maybe gonna make available, I hope.?
Click to expand...
Click to collapse
If/when it's ready and I feel like it otherwise. Audio, bluetooth (on Pi 3 B), ethernet, display, and wifi already working to LineageOS 15.1 standards. It only started week three after the AOSP source drop so everything is still in very early stages. There's no Lineage apps, no Lineage features, no root, etc, and there's still some very basic UI issues.
LineageOS 15.1 Raspberry B+
Thanks for your rom
I dont find script rpi-display.sh for touchscreen like in lineageOS 14.1 Its possible to use this script ?
ericimbert said:
Thanks for your rom
I dont find script rpi-display.sh for touchscreen like in lineageOS 14.1 Its possible to use this script ?
Click to expand...
Click to collapse
I don't have any display hardware so I haven't tested. Some people have reported that LineageOS 15.1 works with the original 7" display but I don't know if they've made any modifications.
LineageOS 14.1 script won't work as is at least. You can try this one instead (https://pastebin.com/A2kfGhrR). Push to /system/bin/, set correct permissions (755) and run. I think you also need to change ro.sf.lcd_density in /system/build.prop to match the resolution change (in LineageOS 14.1 as well) but no one has given any proper feedback on that either.
Can someone do support for bluetooth 4.2 (for Rpi3B+), please ?
This rom is the first non official rom i could boot on my pi 3 B+ !!!!
tkx
go on working on this way
display performance is really really too poor
Related
WARNING: When using custom kernels on the S7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
OKAY SO
This is Kali NetHunter 3.15.2 for the Galaxy S7.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.2 (stable, 2016-11-04)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930W8, SM-G930X: kernel-nethunter-herolte-*
SM-G930K, SM-G930L, SM-G930S: kernel-nethunter-heroltekor-*
S7 edge: You're in the wrong forum!
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
Samsung Smart Switch Mobile can be useful for this, and allows you to back up your apps to a location on an external SDcard.
Unfortunately it doesn't back up most app data.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
It's become apparent that there may be issues with the stock ROM and this kernel, and that it might run best on a Note 7 port.
FULL INSTALLATION STEPS
Install Team Win Recovery Project to your recovery partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC N930SKSU2BPID Note 7 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.44 (with dirtycow vulnerability patched)
SELinux permissive
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted data partition support
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption disabled (not supported by custom kernels at the moment)
Kernel module support, insert your own modules!
CIFS, NFS available through included kernel modules
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
Reboot after 60 seconds - Sometimes when you boot your device it could reboot after 60 seconds because of a Samsung secure service not responding. Unresolved, but rare, and only happens within 60 seconds of a boot.
DEVELOPMENT
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Galaxy S7 NetHunter kernel source: https://github.com/jcadduono/android_kernel_samsung_universal8890/tree/nethunter-6.0
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-11-04
Created 2016-10-06
Last Updated 2016-11-04
I cannot test this today, but i ****in love you !
saphirrot said:
I cannot test this today, but i ****in love you !
Click to expand...
Click to collapse
Yeah I just hope it's all working fine this time Last time I opened a thread for NetHunter on S7 it was a little embarrassing as I didn't own any recent Galaxy phones I had no idea they'd be such a challenge to get custom development going on.
I still haven't exactly tested this, but I do have the Note 7 now so I'm really hoping that everything done to make it work on the Note 7 makes it work on the S7 and S7 edge too... *crosses fingers*
We've got a few issues to fix before an actual release but they're all related to the apps.
1. The NetHunter Terminal app is quite buggy, so you might want to use JuiceSSH local terminal for now. (type su -c bootkali_login to enter Kali environment)
2. The NetHunter app's scripts are all hardcoded for armhf right now. I've actually completed arm64 support in the installer and we can build working arm64 rootfs and install it, just the NetHunter app can't see it yet so we're using armhf on arm64 instead for now.
Anyways, hope to hear some good news from ya! These remaining issues shouldn't take long for us to overcome...
For s7 edge do I have download the arm packages or arm64 packages?
Handeman707 said:
For s7 edge do I have download the arm packages or arm64 packages?
Click to expand...
Click to collapse
you're in the wrong forum, go to S7 edge forum
http://forum.xda-developers.com/s7-edge/development/kernel-kali-nethunter-galaxy-s7-edge-t3475413
this probably isn't something you want to play around with if you don't know if your phone is arm or arm64 :/
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
XanSama said:
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
Click to expand...
Click to collapse
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
jcadduono said:
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
Click to expand...
Click to collapse
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
XanSama said:
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
Click to expand...
Click to collapse
Used USB RO to install Windows 10 from boot the other day, but that was in UEFI mode
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
ahamed.rafi135 said:
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
Click to expand...
Click to collapse
Only tested on latest stock FXXU1BPI firmware
jcadduono said:
Only tested on latest stock FXXU1BPI firmware
Click to expand...
Click to collapse
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
ahamed.rafi135 said:
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
Click to expand...
Click to collapse
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
jcadduono said:
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
Click to expand...
Click to collapse
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
ahamed.rafi135 said:
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
Click to expand...
Click to collapse
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
i have attached the log
jcadduono said:
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
Click to expand...
Click to collapse
also which rom do you recommend?
ahamed.rafi135 said:
also which rom do you recommend?
Click to expand...
Click to collapse
the one that matches your boot image...
i will always recommend stock over anything else though
ok try a build from here instead:
http://build.nethunter.com/test-builds/
update: tested myself and it worked fine, posted new nightly build with changes
it will remove the firmware upgrade service from boot image, which is useless anyway as we can't take OTAs with custom kernels
Hi, I have flashed both of the lastest kernels (kernel-nethunter-herolte-marshmallow-3.15.2-20161024-2241) and (kernel-nethunter-herolte-marshmallow-3.15.2-20161023-0148) but they are still laggy and are having poor CPU performance in geekbench tests. Any fix?
Does it requires an external WiFi adapter to test my internet security or does the WiFi adapter of the S7 can do the job ?
Thank you
/*
* Your warranty is... still valid?
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Project Treble
Important!
Recommended for installation only for advanced users***What is Project Treble? ***
Project Treble allows to install - Generic System Images on our device with a minimum number of bugs.
Vendor - this is partition where proprietary files and drivers are stored, which are separate from the system.
***Userful Information***
Project Treble XDA Thread
Generic System Image (GSI) list
***Development and bugs***
Development has been started about 3 months. backwards During this time, dozens of errors were corrected and millions of nerve cells were lost.
Vendor is based on the stock firmware UOS273C with a large number of edits.
The kernel is used from vm03 with driver edits for working on Project Treble.
Bugs in Generic System Images:
On Oreo and Pie GSIs don't working SafetyNET.
My Magisk Module: Wileyfox Swift 2 SafetyNet Pass
Bugs in Vendor:
SELinux Permissive
For the fingerprint scanner to work correctly before being added to Settings, it is necessary to “poke” 5-6 times into it, for the driver to load correctly.
***Preparing device for support Project Treble***
Download TWRP Treble
Repartition script 16GB or 32GB
Download Treble Vendor
Download Treble Boot
Mirror on Google Drive
Mirror on Cloud Mail.ru
If you want get back default partition table just flash:
Download Revert - 16GB
Download Revert - 32GB
You need to copy all the necessary information to an external memory card or PC, since the internal memory will be formatted and devided into special partitions for Project Treble can work.
Install TWRP Treble in a convenient way for you.
Install Repartition script in TWRP. Depending on your internal memory size.
After installing repartition script, device will automatically reboot into Recovery, where you must do:
Format Data (Wipe > Format Data)
Wipe Vendor (Wipe > Advanced Wipe > Vendor)
After that necessarily to reboot the Recovery (Reboot > Recovery)
Flashing Treble Vendor (Just install zip archive)
Flashing Treble Boot (Select the option in the lower right corner Install Image, select Boot_Treble_new.img and flash it as Boot Image)
Install your favorite firmware (about this below). (Select the option in the lower right cornerInstall Image, than flash it as System Image)
***Installing Android Oreo or Android Pie GSIs***
Flash any GSi from Generic System Image (GSI) list or XDA Thread
always choose arm64 A-ONLY!
* If camera don't working on Pie flash:
Camera Pie GSI patch
* If the NFC item in the settings hangs, or the NFC does not turn on (this is usually the case in the old October GSI), flash:
NFC all GSI Patch
* Patch for fix fingerprint scanner on some Pie GSIs
Folder with patches
For ArrowOS GSI, HavocOS 2.0, AEX 6.1 fix not needed.
***Google Apps***
Install GApps only before the first launch of the ROM!
Open GApps Project
***Thanks***
Testing and moral support:
Kirill_MegaFon (4PDA)
xyzmean (4PDA)
Zent16 (4PDA)
backspace696 (4PDA)
Help in bug fixes and kernel sources:
vm03 (XDA)
Mirrors for download files:
anatoliy-is (4PDA)
Fingerprint overlay:
creativchic (4PDA)
XDA:DevDB Information
[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X, ROM for the Wileyfox Swift 2
Kernel Sourses
DevelopedInside
Contributors
fx-mod
ROM OS Version: Android 8.1.x and Android 9.x
Version Information
Status: Beta
Created 2018-09-30
Last Updated 2018-09-30
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
To return the phone to stock, just install Factory Firmware.
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
Done!
i installed treble according to your instruction and flashed a AOSP 8.1 image (system-arm64-aonly-gapps-su.img.xz) which should include gapps and su.
unfortunately the su-part wasnt available, so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
[edit]
installed another rom which had the option in developers to reboot directly into the recovery - that worked.
---------- Post added 5th October 2018 at 12:12 AM ---------- Previous post was 4th October 2018 at 11:43 PM ----------
Now i installed the latest Oreo Resurrection-Remix from https://downloads.resurrectionremix.com/arm64aonly/ and during startup:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another thing is, that on all GSI-Images i installed so far the system-fonts are very tiny - like it's using a too high screen-resolution.
fred0r said:
......so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
Click to expand...
Click to collapse
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
fred0r said:
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
Click to expand...
Click to collapse
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
xXxSAMIxXx said:
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
Click to expand...
Click to collapse
vendor miscmatch message is a warning. Not an error!
a great work ..soon i will get this device
I'd like to try out Android P. Has anyone tried this with a Swift 2 device and can recommend a GSI to use?
Edit: I couldn't get Pixel Experience (9.0) to boot succesfully but phhusson's AOSP 9.0 works. It's very barebones indeed. Someone made an overlay that makes adaptive brightness possible but I still can't adjust the LED for notifications. Not being able to turn off the charging/low-battery LED is a bummer. Otherwise it runs fine but I'll try a different GSI today.
Did you use the arm64 a-only image? I tried the arm a-only and that wouldn't boot but I'm (quite) happily buzzing along with the former.
fx-mod said:
* Patch for fix fingerprint scanner on some Pie GSIs
Phh AOSP 9 v106 [02/10/2018] only
ArrowOS 9 [23/09/2018] only
Pixel Experience P [20/09/2018] only
Click to expand...
Click to collapse
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
erasmuswill said:
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
Click to expand...
Click to collapse
it is done!
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
waver1967 said:
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
Click to expand...
Click to collapse
32 GB of course
failed to mount system
after doing all the steps twrp says no os installed
oeps my mistake..
forgot to unrar gsi file
Is it possible to patch at least one of Pie GSI's to work almost perfectly? Right now it is not possible to use any of GSI's for more than a week because every one have some annoying bugs
puszekkk said:
(
Click to expand...
Click to collapse
What does not suit you?
anatoliy-is said:
What does not suit you?
Click to expand...
Click to collapse
Broken hotspot, dumped fingerprints after reboot, broken wifi, broken audio routing :/
Thread depreciated. There won't be anymore official LOS 17 builds for this device.
Please jump to:
The official LineageOS 18.1 thread for z3 or dedicated thread for z3dual
if you are looking for new builds.
-------------------------------------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project (AOSP) and can be used without the need to have any Google application installed.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below. There are also inofficial TWRP recovery builds available - if you want to use TWRP you need to ensure that it is compatible with Android 10.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Detailed instructions:
Install LineageOS on z3
Downloads:
Final official build of 17.1 ROM for Z3:
Google Apps (optional): Open GApps (choose ARM as Platform and Android 10)
Changelog:
Changes for z3
Source Code
The source code of LineageOS is available here. If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The z3 device tree is available here.
The kernel source code for this device is available here. The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.
Bug reports:
How to submit a bug report - Please do not submit anymore bug reports for 17.1 - try 18.1 first please.
LineageOS GitLab
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
Thanksgiving
Thanks to everyone who ever contributed to the custom development for this device, especially:
@nailyk
@rcstar6696
@tomascus
@Diewi
@xkeita
@drakonizer
XDA:DevDB Information
LineageOS 17.1 for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12
Remarks, Questions & Answers
Known Major Issues
Official Lineage Recovery is currently broken. There are two options:
TWRP recovery (inofficial build, optional): TWRP
Unofficial Lineage Recovery build.
WiFi issues in some countries (e.g. Iran): low speed @ 5GHz, hotspot and connection issues. This topic is related to a dirty workaround. A solution is here but will not be integrated into our official Lineage kernel.
Disk Encryption: Disk Encryption is working, however not with the default password (no password). Workaround: Set password first, then start disk encryption, not the other way round! Solved
Bluetooth Low Power may create wakelocks in certain scenarios.* Solved
Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*
Reported size of adoptable storage seems to be wrong. However, remaining free space seems to be reported accurately.
Formating a SD card as internal storage may cause the card to be reported as "corrupted".
Screen rotation may not work after a while. Solved, to be integrated into builds from mid April 2021 onwards.
You tell us (with logs please)...
* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano). However I would be happy to be mistaken here and if sombody has a solution.
Further hints
This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.
If you need Google Apps we recommend the OpenGApps "nano" package, however, I personally use the "stock" package which works as well. The ROM also seems to work with MicroG and BiTGApps.
Magisk - see this post for issues with latest Magisk versions
If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:
Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
Follow this guide to partition your SD card. Note: all data on the card will be lost.
Restart your phone.
When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)
Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).
How to create logs:
Follow How To Logcat
When creating a log, can you make sure you run the command with the -b option to include kernel messages:
Code:
adb logcat -b all
If your device randomly reboots:
Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).
If your device crashes during boot and reboots to recovery:
Code:
adb pull /proc/last_kmsg
Please submit logs from clean systems without "Exposed" or similar modifications in place
Your feedback is wanted regarding the following topics
Please have a look at lineage-18.1!
A big THANK YOU also to @ronnay ryukay for having maintained the inofficial 17.1 thread!
Thank You.
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?
mer5ad said:
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?
Click to expand...
Click to collapse
TWRP and Lineage Recovery are different things. See Post #2 for details. Current TWRP version is 3.3.1.0 iirc.
Mr.Tom_Tom said:
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code:https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12
Click to expand...
Click to collapse
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_
dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing and b. i had to regrant permissions for most apps . but that was because i m using BitGapps instead of opengapps. i confirmed it after reading the BiTGapps post!!
[edit] the permission regranting problem of bitgapps has been fixed
nikapos said:
dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing but thats maybe because i m using mindthegapps instead of opengapps and b. i had to regrant permissions for most apps.
Click to expand...
Click to collapse
Hmm, ok, sounds good. Will try it. :good:
0LDST4R said:
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_
Click to expand...
Click to collapse
download D6603_23.5.A.1.29.ftf rom and use FLASHTOOl software.
Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...
kwasior500 said:
Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...
Click to expand...
Click to collapse
not supported by device hardware. be reasonable!
NOT 4k 120FPS, 4k OR 120FPS
Upgraded from 16 to 17 (dirty flash). Most things seem to work well. A few minor issues:
- Data connection occasionally stops working. Can't figure out why, but I think when I disable/enable wifi is connected. Need to dig deeper
- Smart lock with BT device stops working after a while. Have to remove the device and re-enable
Happy otherwise. Good job!
@Mr.Tom_Tom
how can mount System to boot with RW ?
dsp3 said:
Upgraded from 16 to 17 (dirty flash).
Click to expand...
Click to collapse
Thanks for this feedback, but please do NOT dirty flash. When installing official LOS17.1 the first time, do this with a clean setup.
WiFi 5GHz (Russia) does not work. Can you make changes to the kernel?
new update with working calendar widget. i also had to boot into recovery to reflash bitgapps fo the phone to boot normally.
---------- Post added at 06:08 PM ---------- Previous post was at 06:00 PM ----------
where is the update stored if downloaded from settings->system->update? i want to make sure it is promptly deleted after install.
[edit] ok, you have the option to delete the files after install. the option is found within the update settings.
Just tested Google Duo.
No audio issues. Finally. Thanks, thanks, thanks.
So i guess there are no probs in free hand mode too.
Amazing rom. All very smooth. Thanks a lot!
Unfortunately the back camera does not work for me.
First I was able to start it and a black picture came up. Yesterday I did the new OTA update, that didn't change the problem.
This morning I wanted to save logs about the problem and now the Camera App doesn't start anymore.
Logcat:
2020-09-20 10:59:54.035 8972-8972/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.lineageos.snap, PID: 8972
java.lang.RuntimeException: Unable to resume activity {org.lineageos.snap/com.android.camera.CameraLauncher}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4205)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.PhotoModule.initializeFocusManager(PhotoModule.java:2830)
at com.android.camera.PhotoModule.onResumeBeforeSuper(PhotoModule.java:2598)
at com.android.camera.CameraActivity.onResume(CameraActivity.java:1889)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
at android.app.Activity.performResume(Activity.java:7958)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4195)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)*
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)*
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)*
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)*
at android.os.Handler.dispatchMessage(Handler.java:107)*
at android.os.Looper.loop(Looper.java:214)*
at android.app.ActivityThread.main(ActivityThread.java:7356)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)*
By forcing stop and restart I was able to reproduce the original error. The log is too big to put it in the post, therefore in the attachment.
SageDroid said:
Unfortunately the back camera does not work for me.
Click to expand...
Click to collapse
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.
Mr.Tom_Tom said:
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.
Click to expand...
Click to collapse
Thanks for looking into it. Yes, I wiped them all. Even the internal storage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
reserved
reserved
Good job! Let's take first place
my safetynet fails, is there any way to make it pass? s10 exynos
To update the device (from your previous unofficial ROM) - are that the same steps as described here?
----
Some note about OTA update of this ROM. This is fairly easy (only italic steps below).
But I am using Magisk/microg - with that some additional steps are required - all is listed below. Don't be afraid, it is done in less than 5 minutes.
* Make sure your firewall allows the "Updater"
* If you uses Magisk, download the apk and rename it to zip and put it to SDcard (otherwise a PC is needed for sideload - see below)
* Go to Settings/System/Extended/Updater
* Search for update and download
* I recommend disable data traffic now until the FW-update is completed and microG/firewall is operational again, otherwise your system might be open for some time.
* start update
Device will boot into recovery and does the upgrade. It seems that the update is not completely finished in case of Magisk is installed. In this case force a restart by "Vol- + Power" for a few seconds if update hangs at around 95% (can bee roughly seen in the timeline)
* After update has finished: boot again to recovery
* Now Either
a) just do the update with already downloaded Magisk.zip (Apply Update/Update from SD_card) or
b) Enable ADB sideload by Apply Update/Apply from ADB and do an adb sideload from PC of Magisk.apk or zip (no matter here)
* boot into system
* in case of microG check (and give if required) microG give all the required permissions
* If all is set and done you can enable data connection again
On thing I was thinking about:
There are is one module needed for spoofing (spoof_AVDapi30). I found that an update of it is not required. Not sure whether this will be the case for other updates of 18.1 too, but keep an eye on it.
KiddoIce said:
my safetynet fails, is there any way to make it pass? s10 exynos
Click to expand...
Click to collapse
First you need to install magisk and then:
1) Enable settings MagiskHide
2) install MagiskHide Props Config(Magisk module)
3) Open the terminal
4) su
5) Type "props"
6) Edit 1 fingerprint of the device
7) Choose a certified fingerprint
8) 21 Oneplus
9) Find an Android 11 device (OnePlus 8T global 44)
10) Follow the instructions
11) Restart
12) Clear Google Play Store Data
13) Check SafetyNet (should pass)
14) Open MagiskHide (Magisk -> Tap on the Shield symbol)
15) Check all apps that do not require root privileges
J4son82 said:
First you need to install magisk and then:
1) Enable settings MagiskHide
2) install MagiskHide Props Config(Magisk module)
3) Open the terminal
4) su
5) Type "props"
6) Edit 1 fingerprint of the device
7) Choose a certified fingerprint
8) 21 Oneplus
9) Find an Android 11 device (OnePlus 8T global 44)
10) Follow the instructions
11) Restart
12) Clear Google Play Store Data
13) Check SafetyNet (should pass)
14) Open MagiskHide (Magisk -> Tap on the Shield symbol)
15) Check all apps that do not require root privileges
Click to expand...
Click to collapse
thanks man ill give this a shot
edit;; can confirm that this is working. thanks alot man!
linux4, its a great looking rom btw thanks for the hard work. During the first time i ran recovery, i saw there was an option to run an update through internal storage. but the second time i went to recovery it was gone. Does the update through internal storage work? and why did it disappear when i entered recovery for the second time.
Hello
What exactly is working and what does not work or do not act at highest quality? Can the camera be performed on maximum quality? I bought this cell phone (S10e) a short time ago, I'm waiting to arrive. The installation of the LineageOS can break his system? Well, as is my first Custom Room, I have some doubts.
Can someone confirm that the hotspot works (best S10+)?
KiddoIce said:
thanks man ill give this a shot
edit;; can confirm that this is working. thanks alot man!
linux4, its a great looking rom btw thanks for the hard work. During the first time i ran recovery, i saw there was an option to run an update through internal storage. but the second time i went to recovery it was gone. Does the update through internal storage work? and why did it disappear when i entered recovery for the second time.
Click to expand...
Click to collapse
/data is encrypted so no there's no way to install something from internal storage, either update via sideload, from external sdcard or OTG (If you're just talking about OS update you'll get them via OTA anyways, so what I said only applies to e.g magisk)
It has SElinux? If you could post what's working, what's not and what's not optimal, would be a great help. I'm just waiting to have a notion of things and test.
bym22028 said:
Can someone confirm that the hotspot works (best S10+)?
Click to expand...
Click to collapse
Hotspot is working on S10+ (and i think on other models too)
Works great so far. Seems I can even use bankings apps, after unrooting again. I initially rooted to restore backups using TitaniumBackup but then removed magisk using the internal uninstaller (checked "remove completely"). DKB, comdirekt and TK work so far.
EDIT: hotspot works on s10e
How to make Voice Match (OK Google hot word) working?
it is not available right now
s10e - August SP when? The current and only release in LOS was on 5th Aug but has July Security Patch!
Edit:
Aug SP was released on 2nd Aug https://source.android.com/security/bulletin
Can anyone test if android auto is wokring with the car ? Thanks in advance!
manderspaul said:
Can anyone test if android auto is wokring with the car ? Thanks in advance!
Click to expand...
Click to collapse
It is working fine.
Hi, is there a camera app in this rom that works wide, ultrawide, slowmo and portrait mode("all in one")? And a remap of the bixby button is possible? THX
choduram said:
t is working fine.
Click to expand...
Click to collapse
Also wireless android auto ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Xiaomi Mi 5 [Gemini]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wifi
Wifi hotspot
RIL
Mobile data
GPS
Sensors
Camera
Flashlight
Camcorder
Bluetooth
NFC/GPAY
Lights
Sound / vibration
Fingerprint
WiFi Display
VoLTE
Double Tap To Wake
Buttons swap
Google Voice Match
SELinux enforcing
Safetynet
DON'T FLASH GAPPS, ALREADY INCLUDED
Download standard version from Android File Host
Download PLUS version from Android File Host
Flashing Instructions:
Pre-installation:
Pixel Experience Recovery (Download from here)
First time installation:
Fastboot or flash recovery image
Reboot to new recovery
Click on Factory Reset --> Format data/factory reset
Click on apply update and sideload the zip file or install it using an USB OTG
Enjoy
About Camera App: default camera app is GCAM version SGCAM_8.4.400.42.XXX_STABLE_V35 by Shamim. Everything works fine except 240 fps (1/8) slow motion videos
mandayugana shared his config xml file, which add the specific noise model for Gemini with Shamim GCAM, dowload it from my Github (sgcam-8.4-v35-pe13.xml) or from his post, apply to GCAM following this tutorial and say thanks to him for his great work
XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Mi 5
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
ROM Firmware Required: MIUI V10.2.2.0.OAAMIXM as minimum target
Based On: AOSP
Source Kernel repo: Link
Gemini device tree repo: Link
Xiaomi msm8996-common repo: Link
Vendor repo: Link
Special thanks to
LineageOS
Pixel Experience
Shamim
xNombre
mandayugana
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
ademuhamad said:
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
Click to expand...
Click to collapse
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Echidna_Kawaii said:
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Click to expand...
Click to collapse
Check what process is eating your cpu in the background, i have no problems at all with cpu usage on screen and with deep sleep
and also this giving Random reboot here :/
Echidna_Kawaii said:
and also this giving Random reboot here :/
Click to expand...
Click to collapse
No one reported random reboots, i never had once in a week of usage. Logs or never happened
-+BB+- said:
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
Click to expand...
Click to collapse
ERROR:1 )l
暗夜很无语 said:
ERROR:1 )l
Click to expand...
Click to collapse
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
pretty much very stable rom... working everything very smothly...but one issue...after usung 1 or 2 shot with gcam its freeze the cam...and then can't open the gcam anymore...
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
İST1907 said:
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
Click to expand...
Click to collapse
Could you please post the log of the error during the flash?
mrinfinity0007 said:
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
Click to expand...
Click to collapse
1 and 5 are AOSP/PE bugs, hopefully will be fixed in QPR2 release
2 don't use Gcam for now, i've fixed hdr+ photos on recent Gcam version in my internal builds but it's still crashing causing a reboot after a minute, i had no time to inspect yet because i was focused on EAS and power HAL port
3 correct, no OTA update app on unofficial builds
4 i'm not 100% sure but if i remember well it's a feature of plus version
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
JackSlaterIV said:
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
Click to expand...
Click to collapse
Unfortunately Pixel Experience doesn't support natively TWRP compiling, and i don't have space on my NVME for another build enviroment. Also as far as i know they did not release yet an Android 13 recovery, they are working right now on it, but i don't know if works. Do you know if TWRP supports FBE on other devices? if TWRP supports FBE then best thing would be compile TWRP in an Android 12 build enviroment with a 4.4 kernel with FBE support. you can use my repos or los repos, it' the same. The only requested changes are a makefile with a basic conf for mi5 and convert the fstab in a compatible version for TWRP
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
-+BB+- said:
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
Click to expand...
Click to collapse
Let me try another TWRP version
-+BB+- said:
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
Click to expand...
Click to collapse
i don't root my phone? does it work without it?
JackSlaterIV said:
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
Click to expand...
Click to collapse
I will take a look this weekend and let you know because I don't remember where but I'm pretty sure that I read a tutorial for TWRP compiling some years ago
暗夜很无语 said:
Let me try another TWRP version
Click to expand...
Click to collapse
If your goal is to flash the ROM without format the internal memory won't work, you may be able to flash the zip but after the flash you'll be forced to format the internal memory without fbe support
mrinfinity0007 said:
i don't root my phone? does it work without it?
Click to expand...
Click to collapse
Yes it's a root shell, you have root permissions only with ADB, not in your phone. If you want to roll back to selinux enforcing and stop the rooted shell simply reboot the phone, that changes doesn't survive after the reboot
@JackSlaterIV found it, it's old and some things may be slightly different but this is a good tutorial.
Here's the link of the minimal manifest 12.1 is the correct branch but decryption is WIP at the moment, don' t think will work, unless you don't set a password/PIN/pattern, in that way should be fine
@mrinfinity0007 never mind, i've fixed It, Gcam was crashing because it was trying to use hexagon for HDR+, but SELinux was blocking it. Now it's wotking fine even in enforcing mode
PS: i've decided to upload the latest personal build i made, some thing may change because i'm still testing them, but more or less (on device side) this will be the next official release when PE devs will merge QPR2 changes and feb security patch.
Here's the direct link
And here's the changelog:
ROM:
- Synced code with latest PE changes
Kernel
- Ported EAS and set it as default scheduler
- Ported Stune Boost and use it as default
- Fixed almost all compiling warns
- Ported misc optimisations from infinity kernel
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
- Misc fixes from upstream
Recovery
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
Device Tree
- Ported EAS
- Move to EAS compatible power HAL
- QCOM audio HAL: add missing audio power hints support
- Fixed Google Camera crash when trying to use Hexagon
- Camera: move to Gcam Version MGC_8.1.101_A9_GV2b_ENG big thanks to BSG. Camera can be updated with all APKs released by BSG, just be sure to download the ENG version
- SELinux: fixed all denials
- Ported various improvements from my old 12.1 ROM
- Tuned ZRAM size for 3Gb devices
- Camera: improved camera HAL + misc fixes
- Configure SQLite to operate in MEMORY mode
- Set CFQ as default scheduler
- Added pixel animated wallpapers to build
For more detailed changes take a look at my repos
PS: i cannot test GPAY at the moment because i'm testing other things and i'm running in permissive mode, if someone decide to try the update and use GPAY please let me know if works, i made some changes to sepolicy and i want to be 100% sure that Google pay isn't broken before the official release.