Jolla SailfishOS 3.2.0.12 linux
IT IS NO ANDROID!
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
The full install tested with Official ugglite 3.3.1 TWRP.
Download LineageOS 14.1 & SailfishOS.
NEED FREE INTERNAL STORAGE SPACE ~2GB!!!!!!
NEED UNSECURE EXT4 /data Partition!
Boot into recovery.
Wipe data, cache,system partitions.
(If your /data partition secured, you need format /data to ext4 if you want to use this ROM.)
Flash LineageOS 14.1 ugglite ROM in TWRP (sideload or copy any storage)
Reboot, start LineageOS 14.1 (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 2 minutes.
Restart to TWRP again.
Flash SailfishOS 3.2 ugglite in TWRP (sideload or copy any storage)
Reboot
First boot may take up to 1 minute.
ssh: [email protected] (change password: settings - developer menu)
Dual boot: flash with TWRP or 'fastboot boot' Lineage boot.img, or flash with TWRP or 'fastboot boot' hybris-boot.img, from zip files.
Sailfish OS workig from /data partition, if you wipe data, deleted Sailfish OS
BACKUP, before wipe data.
Bugs:
No bootsplash.
Boot time 50-60 sec. Power off charge animation ~50 sec. Reboot, and power off time 15-20 sec.
I could only create a Jolla account on a PC.
Some video types are not playable (Jolla license).
DOWNLOAD ROMS SF
DOWNLOAD ROMS AFH
Known issues: don't know
I'm not going to give you support for privat upgrades and other changes, fix it for yourself. Sorry.
*
Screenshots: LINK
ROM OS Version: 14.1 & 3.2.0.12
ROM Kernel: Linux 3.18-31-szancso & 3.18.140-szancso
ROM info: Lineage-14.1, system partition, Android quota no.
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 2020-03-08
Last Updated 2020-03-08
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
Test update and alien-dalvik Android support:
{
"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"
}
How to update ?
ByHorvyCZ said:
How to update ?
Click to expand...
Click to collapse
I do not support the update.
There may be a problem with WiFi, sounds, lights, etc.
If you want to upgrade, you have to solve it yourself, because if you can't upgrade it yourself, you can't fix problems.
Alien-dalvik is not going to be with upgrade, a separate thing, and to my knowledge warez. Anyway, it's almost uselessly bad. (At least the version I tried.)
I do not support this too. Sry.
Yes you're right. I tried to make a force update through the terminal.
Now Wifi doesn't work. Otherwise, I put it into operation.
I upgraded the system just to make sure other accounts were working.
Warning, do this at your own risk.
!!You can ruin the system or worse the whole phone !!
So, okey, open your terminal. :angel:
Code:
devel-su
Then you enter the root password, :good:
Code:
ssu release 3.2.1.20
This sets up what you want the system to update
Code:
version --dup
This will start the process of updating.
You should never close the terminal when you're running this command.
After all, restart phone, and you are done ! :silly:
Related
TWRP Alpha build for MT2-L05(LianTong) TeamWin Recovery Project
Not working:
Could not handle Internal Storage properly, i.e., Wipe data will wipe internal storage as well.
Most of the text and even the config/build itself is copied from Modding.MyMind work on US version MT2L03. Thanks, Modding.MyMind
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****
Please note, due the structure of this phone storage, the Internal Storage (/storage/emulated/0 size 12GB) is actually shared with /data partition, and the mount point is /data/share, this is not same as google recommended value /data/media, and current TWRP code could not handle this properly. Also Modding.MyMind has PM'ed me that he probably will spend less and less time on XDA/development work, and I really lack of expertise/time on this one, so This build didn't resolve this issue. That's why I labeled this as ALPHA version.
Internal Storage /data/share /storage/emulated/0 size 12GB
External SDcard: /mnt/media_rw/sdcard1/ An SDCard is required to use this TWRP build and recommended 32GB or bigger.
For more information about this issue, please check TWRP article http://teamw.in/DataMedia, and please noted that it mentioned "A stock AOSP recovery would format data including the "sdcard" but TWRP will use its regular factory reset setup that leaves the internal storage intact" is not working in this TWRP alpha build., i.e., This TWRP will wipe your internal storage when you wipe data.
So, using this TWRP recovery, fact is:
. The backup target must select External Storage.
. Backup /data will include the internal storage, and this partition size will be ~12GB if uncompressed.
. Restore /data will override internal storage area.
. Wipe data (Factory Reset) will wipe internal storage as well.
Please read above carefully, and understand the risk of using this alpha build.
Recommended approach:
In your daily usage of the phone, try to save everything to external SDCard, or manually backup internal storage to external SDCard frequently.
When using TWRP, back/restore following partition is safe:
/boot
/recovery
/system
And always take caution when backup-restore /data, also, it is recommended check the compress option when do the /data backup.
Again, Many application may save files into Internal Storage including the pictures you taken, and files/songs you downloaded. So be aware of the risk of using this TWRP that may wipe the internal storage. If you are not clear/comfortable of this risk, please do not install this TWRP.
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****END****
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
Steps for Backing up Stock Recovery:
within a terminal using dd (aka Data Destroyer);
Code:
su
dd if=/dev/block/mmcblk0p18 of=/mnt/media_rw/sdcard1/stockrecovery.img
TWRP for MT2-L05
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Installation (PC):
- You MUST have an unlocked Bootloader!
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
Download:
- TWRP 2.8.0.0
File name: TWRP_MT2L05_Alpha.img
File size: 11,040,768
md5sum: b8832fc6dfd5d6e47e63ba7f7e047518
CONTRIBUTORS
@Modding.MyMind
@xordos
And thanks @4L0M for the testing that is dangerous due to the nature of twrp
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel
- Stock Kernel
- TWRP source from Omnirom
- MT2-L05 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: ALPHA
- Created 2014-10-03
- Last Updated 2014-10-29
//reserved
Great work. If anyone could help finish this project off, I am more than happy to keep testing. If we can get this recovery fully working, then I think we would be far closer to understanding how to port kitkat to the MT2-L03 devices.
{
"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"
}
Yes, I do have an idea/workaround for this issue, and hopefully open this discussion thread can get more idea/evaluation going on.
The /data/share folder is treated as internal storage, but twrp is hard coded /data/media in many many places. So maybe we can rename 'share' to 'media' when boot into twrp, then rename back before reboot. But the 2nd part may not easy to guarantee. If it get into normal OS booting, it may cause confusion even damage.
So I am not like this workaround even myself.
disregard...
I think B606 breaks recovery. After I update to B606 and reinstall TWRP, it just hangs on splash screen every time I try to enter recovery.
Hi, i flashed the recovery using fastboot and then i tried to reboot into recovery but the phone just reboot after 1 try. here is my bootloader screen. Plz tell me how to root this phone. Its unlocked but i'm unable to root it.
{
"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"
}
Introduction
Hi to all dear Z3c users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git.
I hope you enjoy this.
How to install
Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot
Reboot your phone on fastboot mode.
Flash recovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via zip (You need a working recovery installed)
Download the zip and put it on your internal or external memory.
Reboot to recovery.
Flash the zip.
Via Official TWRP App (You need root)
Install the app from Google Play Store and download the zip.
Extract recovery.img and copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Download
TWRP
Thanks to
@GreyLeshy a lot of thanks for this great dev, he helped me a lot for make this possible, build this recovery and he had a lot of patience with this noob dev.
@Dees_Troy for TWRP.
omni Team for TWRP Minimal Source.
XDA:DevDB Information
TWRP for aries, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
ShadowElite, GreyLeshy
Source Code: https://github.com/ShadowElite117/android_sony_shinano_twrp/tree/aries
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2018-09-02
FAQs
Q. How boot on recovery?
A. With the device turned off, press power and vol- at same time until it vibrates.
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
neckronus said:
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
Click to expand...
Click to collapse
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
ShadowElite said:
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
Click to expand...
Click to collapse
Just tried flashing the latest Carbon and it worked for me. Haven't tested flashing stock ROMs myself though
Just tried to install the zip on my Z3 compact.
My phone has full encryption enabled (complete including the sd card).
Your build of TWRP is not able to decrypt the phone.
It always tells me "Password failed, please try again!" even though the given passsword is correct (I can start the system with the same one).
amazing
Installed on OMNI with TWRPapp, flahed Carbon and then RR.
All it was fine and, finally, no "Error 7".
Thank you for this!
I have a question, I have encrypted my device (CarbonRom cr6) and now when I try to access TWRP I draw my security pattern and I get a failed to decrypt message.
The pattern is the one I use on a daily basis to use my device so this is related to TWRP. Any suggestion?
Maybe this twrp has a problem with support encription?
Carbon ROM expects TWRP with ro.build.product or ro.product.device equal z3c (not aries) . Modified original image using this method https://forum.xda-developers.com/t/...because-of-empty-system.3554252/post-85881113
For Lineage (18.1), this (3.3.1) TWRP version is recommended, but it seems to have issues preserving the survival scripts (e.g. of Magisk) over OTAs. Unfortunately, the device isn't supported on twrp.me
Hi. I'm just wondering what this is that we flash before installing a new rom, why do we flash this, what does it do? Is it necessary to flash it?
Thanks
Just keep onething in mind before digging into this matter. Having a decrypted device is the same as having a stolen device. No security at all and the device gets extremely vulnerable and easy to be hacked. I don't really know why some people still decrypt their devices when we already got a TWRP which decrypts the device temporarily while booting on recovery (without actually decrypt your device permanently).
Disable Force Encryption (a.k.a DFE) is flashed during installing a custom rom to avoid the system encrypting /data partition when the devices boot for the first time.
DFE is not necessary but some custom recoveries (Official TWRP for example), needs the /data partition to be unencrypted to access the internal storage for you to flash something or to access /data and internal storage. (Except if you have SD Card, then DFE is no longer needed)
OrangeFox Recovery for example has its feature when installing custom recovery, flashing DFE is no longer needed because the recovery itself will patch the boot.img to avoid the system to encrypt data.
Final Verdict:
-If you want a secured device that has a lot of golden stuff inside, then do not flash DFE or disable the DFE on OrangeFox Recovery.
-If you want to access /data for your inconvenience, then flash DFE everytime you install a custom rom or enable DFE on OrangeFox Recovery.
Edit:
The unoffical TWRP that has data decryption patch doesn't works as new and updated vendor, boot.img, etc. comes in and the fix is useless. It only works on older system patches, e.g. MIUI 9.
If i decrypt the device. How to encrypt it again?
SamyakJ said:
If i decrypt the device. How to encrypt it again?
Click to expand...
Click to collapse
Security&Location > Encryption&credentials > Encrypt phone
I think it requires your phone to be at 100% charging to start the encryption.
---------- Post added at 08:36 AM ---------- Previous post was at 08:35 AM ----------
And I don't even know if it is stable or not after the encryption. I haven't tried encrypting the device via the Settings.
So this is where I am stuck since March 25th, oneplus 7 pro with oos 11 final and encrypted phone with a lot of precious data. All I need is root (not really need custom recovery).
Is there any way to get it rooted without data loss? I've tried to flash the patched boot image found in this thread but the phone keeps looping in boot until I force restart it then it boots normally. Tried that several times with no luck.
{
"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"
}
can't you just backup all the data? you don't exactly need root for backups
I continue the post with 2 questions
sorry for the banality of the questions and I searched online and on the forum before asking
1) So if I don't disable the forced encryption the only problem I can have is the appearance of the set warranty bit kernel written every time the phone is rebooted?
2) What is the difference between these? (1) Tabs3_oreo_forced + encryption_disabler (2) Disable_Dm-Verity_ForceEncrypt-master (3) no-verity-opt-encrypt- ?
and how can I check the compatibility of the phone?
Tks !!!
Darklouis said:
Disable Force Encryption (a.k.a DFE) is flashed during installing a custom rom to avoid the system encrypting /data partition when the devices boot for the first time.
DFE is not necessary but some custom recoveries (Official TWRP for example), needs the /data partition to be unencrypted to access the internal storage for you to flash something or to access /data and internal storage. (Except if you have SD Card, then DFE is no longer needed)
OrangeFox Recovery for example has its feature when installing custom recovery, flashing DFE is no longer needed because the recovery itself will patch the boot.img to avoid the system to encrypt data.
Final Verdict:
-If you want a secured device that has a lot of golden stuff inside, then do not flash DFE or disable the DFE on OrangeFox Recovery.
-If you want to access /data for your inconvenience, then flash DFE everytime you install a custom rom or enable DFE on OrangeFox Recovery.
Edit:
The unoffical TWRP that has data decryption patch doesn't works as new and updated vendor, boot.img, etc. comes in and the fix is useless. It only works on older system patches, e.g. MIUI 9.
Click to expand...
Click to collapse
Is DFE and avb2.0 same?
Coz I'm using shrp and unable to find close avb2.0 ?
Hello,
I need help for TWRP on my Samsung Galaxy A20e. My device is rooted for a while and TWRP is newly installed. But the problem is when I try to backup something, I got an error while creating the folder TWRP with the mension of operation not permited. I also have a problem when I touch the Install button, I see a list of folders with random generated names like in the photo. Can anybody help me to solve this problem? I can give more informations if needed.
Thanks for helping !
{
"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"
}
your device is encrypted. you must disable encryption and factory reset device in order to become TWRP functional, as TWRP cannot handle samsung encryption. or use other backup method such as Migrate.
Ok I tried what you wrote but it works only while I don't boot my device after factory reset it. If it happens, the encryption enables automatically and I can't backup anymore. Do you have a solution for this ?
you must disable encryption in /vendor/etc/fstab.samsungexynos7884
(can maybe done with zip)
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
How am I supposed to do that ? I tried everything with this file. There is a mount option for /data "filencryption=ice". I tried to delete this with a file editor in the stock system but when I reboot my phone it reappears. When I this this in TWRP the system can't boot.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
Click to expand...
Click to collapse
This link cannot help me because it is just a tutorial and when I do exactly like in i get the same results. I don't unerstand why my phone has this problem and not others. If you have other ideas i would be good
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
aIecxs said:
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
Click to expand...
Click to collapse
I tried installing this zip file from the SD card but it didn't boot (locked on samsung logo) so I did a factory reset with TWRP and after configuring, I got the same results than before.
- in TWRP double check your vendor partition is separate partition (or directory inside system partition)
- in TWRP terminal make sure partition is mounted rw
Code:
mount /system w
mount /vendor w
mount
- install Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
- in TWRP terminal double check fstab.samsungexynos7884 file fileencryption= flag is gone
Code:
cat /vendor/etc/fstab.*
- in TWRP - wipe - format data - type yes
Thanks for the instructions. It works perfectly ! I am just an idiot because I didn't wipe /data in TWRP but I just swiped to factory reset. Thank you a lot !
maybe I was misleading you with factory reset. might be that TWRP factory reset just behaves like simple wipe, where only files are deleted excluding /data/media
formatting whole partition is required for removing encryption.
edit: Please note if you're interested in undo the patch, you must restore vendor partition. you can of course add the fileencryption= flag back with text editor yourself. However that requires linux line endings (LF) so you can't use Windows text editor (CRLF) that's why you should use Notepad++ and enable view for invisible chars with (π) button. Do not simply copy file back into /vendor you will lose file permissions. Do not use sed you still would lose secontext. only copy content of file into old existing file like this.
Code:
cat /tmp/fstab.new > /vendor/etc/fstab.samsungexynos7884
Btw if you're running custom ROM (such as LineageOS) it's possible to break samsung encryption and use AOSP encryption as fallback by deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw. This way you can use TWRP on encrypted device.
crDroid 9.2 - Android 13
(EX: "PixelOS ROM Android 13 With GAPPS". ROM not deleted, downloadable: sourceforge)
(The first 7 comments were about the previous PixelOS, ignore them.)
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATAs before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery (or any recovery with FBE support). [I'm not using Fox recovery, I'm not going to give you advice.])
Unfortunately, the ROM turns on FBE encryption for the time being, I will try to solve it (maybe).
If you want to revert to another ROM, you may need to format the data partition!
twrp-3.7.0_Szancso.img is my work. Download link: with ROM.
(Previous version to TWRP not working, use 3.7, or any recovery with FBE support.)
Boot into recovery
Wipe system, vendor, data, cache partitions to clean install.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
(If you are upgrading from a previous version of this ROM, you do not need to wipe the /data, but you need to wipe the Dalvik and Cache. If previous version encrypted, maybe need format /data.)
Flash Rom in TWRP (sideload or copy any storage)
Flash (Nik)GApps (Optional) [I'm not using GAPPS, I'm not going to give you advice.] (NOT TESTED!)
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.] (NOT TESTED!)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to ~1-2 minutes.
I'm not using this ROM, I'm not going to give you advice, no support (or slow), sorry.
DOWNLOAD
Cool things:
-Include Midnight Commander (in adb)
-FM radio
-Smart Charging
-adb root
-22-24 days standby time (one charge)
-Enforced selinux
-Not encrypted
Known issues:
Not tested: VOLTE, Magisk, Gapps
Screenshoots: LINK (comment #9)
TWRP kernel is original TeamWin device: LINK
OS source: LINK
ROM OS Version: 13
ROM Kernel: Linux 4.9 Source
ROM info: 13, system_root partition, Android quota removed (easier to go back to earlier 7.x-12.x ROMs), NOT encrypted.
Created: 02-03-2023
Last Updated: -
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
Hello, thanks for your work, then WI-fi does not work for me on this firmware
Hellne said:
Hello, thanks for your work, then WI-fi does not work for me on this firmware
Click to expand...
Click to collapse
Hello!
Wi-Fi working fine for me. MEGA VIDEO LINK
BUG: Bluetooth not working for me. Pairing is good, but not connect to devices.
I messed up the first version (26-01-2023) a lot, the new version (29-01-2023) is much better. Sorry.
Update 01-02-2023: New release.
Cool, now I'll try to install and report if there are problems
UPD: Now wi-fi is working, I'm testing, according to the first sensations, android 13 is too much for this phone
everything ok thanks to dev.but selfie camera doesnt work.does anyoje know how to fix it?????
This PixelOS ROM is not recommended, I will remove it soon.
It will soon be replaced by crDroid 9.2 :
{
"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"
}
Modifyd post to crDroid 9.2.