Ancient OS 6.4 ROM 26-01-2023
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.])
TWRP_SZANCSO.img is my work, included 4.9 kernel, included Midnight Commander (mc), fixed many factory bugs, working USB storage mode, and DT2W. Download link: ROM.
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 6.4, you do not need to wipe the /data, but you need to wipe the Dalvik and Cache.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (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.
Update 01-02-2023: switching to Weeabo version, fixing Bluetooth-calling issue
DOWNLOAD
Known issues: -
Not tested: VOLTE, GAPPS, Magisk
Screenshots: maybe soon...
TWRP kernel source: LINK
OS source: LINK
ROM OS Version: 12.1/L
ROM Kernel: Linux 4.9 Source
ROM info: 12L, system_root partition, Android quota removed (easier to go back to earlier 7.x-11.x ROMs), NOT encrypted.
Created: 26-01-2023 6.4 version
Last Updated: 01-02-2023 6.4 Weeabo version
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.
Update 01-02-2023: switching to Weeabo version, fixing Bluetooth-calling issue
Related
I want to upgrade to the latest build from an existing CM11 build.
I want to update because the camera still isn't taking photos, though scanning does work, sort of.
I do not want to wipe my existing data.
Got information from xda-developers as well as the Cyanogenmod site.
Currently using CyanogenMod version: 11-20140209-Sultan-venturi with these zips:
cm-11-20140209-Sultan-venturi.zip
Sultan-kernel-Venturi-USA-r8.zip
pa_gapps-modular-mini-4.4.2-20140412-signed.zip
I plan to install:
ROM: cm-11-20140414-UNOFFICIAL-venturi.zip (edited)
Kernel: USA-Kernel-venturi-Apr-16.zip - 6.27 MB
GAPPS: pa_gapps-modular-mini-4.4.2-20140426a-signed.zip
Recipe for manual update:
Sideload or upload data (zip files) to external SD card.
Reboot into recovery mode.
Backup data (optional)
Wipe Dalvik cache.
Install zips in this order: ROM, Kernel, GAPPS.
Reboot.
Wait for Dalvik cache to repopulate from installed apps.
Device is ready for use.
I don't want to blow it. Please confirm for me whether I have the order of operations right for a manual update.
Confirmed.
I figured I would give it a try. At worst, I'd have to reinstall the entire system.
The above recipe worked from going from one version of KitKat to another.
Hey people,
this shall mainly be a fast way to navigate users to necessary steps for diverse situations.
Instead of repeating the procedures over and over in each thread, this can be cited.
I will suggest you what I always do, and what I find safe and what I have good experiences with.
Still, you do everything at your own risk! So don’t complain to me if you mess something up by following my steps.
This well known phrase also counts here: “YOU are choosing to make these modifications”.
*********************
Preparations
Recovery
Make sure you are on the latest TWRP version.
Currently this is 3.2.3-0.
Backups
Before any of these procedures you should make a backup of every partition and save it at an external place – an usb stick, your PC, but not on your phone! Also copy the content of your entire internal storage at such an external place.
This will not always be needed and I will add more details of what you will surely lose when applying each method, but sometimes things just go wrong and suddenly your whole storage may be lost out of nowhere (happened to me more than once already).
A nice app that helps you restoring your apps and app data in a very quick way is Titanium Backup (get it from the Play Store). If you use the Pro version, you can restore everything basically with one click, so think about this way of backing up things as well (external copies are also advised here for obvious reasons).
Firmware
Make sure you are on adequate firmware for your ROM. Which firmware that is, must be taken from the respective ROM thread.
Adequate firmware needs to be present at any time before the actual ROM installation,
otherwise installation will fail, as the ROM expects a certain minimum to be present.
You will not need to always flash firmware again, when installing other ROMs or ROM versions.
The one you flashed last time sticks until you flash another.
A nice alternative to always flashing whole MIUI Developer versions are the zips offered by the firmware updater tool (just search through the xda topics).
*********************
So here we go with methods you should know:
***************
* Dirty Flash *
***************
Note that:
This is not recommended if the ROM maintainer or developer suggested a clean flash
If you wanna solve weird issues, you may try this first, but a Clean Flash or a Complete Formatting will probably help better
Use-cases:
You wanna install an update for a ROM you are momentarily on
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik and Cache
Flash ROM zip right on top of existing installation
(Optionally) Re-/flash root (re-flashing is not necessary for Magisk most of the time if you installed it before)
****************
* Clean Flash *
****************
Note that:
You will lose Gapps, settings, apps and app-data
Also recommended from time to time, even when a dirty flash would be sufficient
Some developers always prefer this method over a dirty flash
Use-cases:
You wanna flash a ROM from the same Android generation (e.g. both ROMs are from generation Nougat 7.1.2) you are currently on
You are experiencing issues after dirty flashing a ROM
Benefits:
Clean way of installation
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
***************************
* Complete Formatting *
***************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
You wanna flash a ROM of a different Android generation (e.g. switch from Nougat to Oreo)
You are experiencing weird issues, even a clean flash doesn’t solve
Benefits:
Clean way of installation
Good problem solver
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Format data (the one where you need to type “yes”)
Reboot to recovery to access the Data partition correctly again
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
****************************************
* Solve unable to mount Data error *
****************************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
TWRP suddenly shows the above error and even a Complete Formatting doesn’t help (or work)
Procedure:
Re-flash latest TWRP via fastboot (not from within TWRP)
Perform a Complete Formatting
********************
* Gapps Re-flash *
********************
Use-cases:
You want to change your current Gapps setup, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache and System
Flash ROM zip
Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Re-/flash root
********************
* Kernel Change *
********************
Note that:
This works for almost every kernel, but if the developer suggests another method, follow his
Use-cases:
You want to change the kernel, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
Reboot to System and let everything cool down for a minute or two
Reboot to TWRP
Flash new kernel
(Optionally) Re-/flash root
Wipe Dalvik and Cache
*******************************
* Stock Kernel Restoration *
*******************************
Use-cases:
You're on a custom kernel and want to switch back to stock one
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
(Optionally) Re-/flash root
Wipe Dalvik and Cache
********************************
* Splash Screen Restoration *
********************************
Note that:
A clean flash will not solve this
Use-cases:
Some kernel's or ROM's splash screen sticks and you wanna get rid of it.
Benefits:
Only takes a minute
You will not lose anything on your phone (except the splash screen ; ) )
Procedure:
Just re-flash your current firmware
*I usually go for Pico Gapps from opengapps.org, as they don't include anything I don't need or like, and add a couple of things from deltadroid by flashing them right after the Pico Gapps package. Some stock apps can be overwritten this way, so you don't have two for the same purpose (e.g. stock calendar and google calendar) and it results in a nice minimal Gapps configuration.
I’m open for corrections, questions or doubts! Please leave a comment in these cases!
last updated: 2018-08-20
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
HelpMeruth said:
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
Click to expand...
Click to collapse
Thanks!
And thanks for the info. So were these issues Magisk related only?
Phil_Smith said:
Thanks!
And thanks for the info. So were these issues Magisk related only?
Click to expand...
Click to collapse
iirc yes(there were SQL issues on the Magisk app), but I don't really follow superSU anymore since its been sold to some random company.
This is a very good guide.. Thanks mate
Hi there,
I may be being stupid here I want to move from Lineage OS to crDroid. Im currently on the latest 01/01/2019 LOS build, with 8.12.24 vendor firmware. I didnt flash the disable encryption patch so my device is encrypted. Im guessing I need to remove any security off the lock screen? Im using the unofficial TWRP build - 12/12/2018.
So to make the switch, do i need to wipe my data, or can I migrate over?
And when I go to flash, which wipes do I need to do before installing the ROM?
Im just worried about flashing and then locking my phone with the encryption because I've missed a step This is my first phone that uses android 9.0, and im not used to the forced encryption stuff.
If someone could give me a lil list of steps, that would be much appreciated!
Thanks!
That I do is:
-wipe system, data, cache, Dalvik
-flash new rom, flash gapps
**Flash any custom kernel if you want
Now here is the differences
1) if I want keep the encryption but format the internal storage I just do a factory reset or format data or internal storage, all are the same and reboot in the system
2) if I don't want keep the encryption, I reboot into recovery, later format data, then flash the zip to keep the phone unencrypted (FDE? I don't remember the name exactly but it is in a post on the guide section), and last flash magisk, then reboot system
3) if you have the phone without encryption and you want keep it in that way, just do the wipe to the system,data,cache,dalvik then flash system, gapps, any kernel at your choice, magisk and reboot into system
PD: remember if you flash a vendor zip, the phone will be encrypt
PS:I hope that I don't get wrong in something
GooglecrDroid ROM 14-01-2020
FULL last openG(OOGLE)APPS included! (v.12-01-2020)
Last stable crDroid 6.2 based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe data, cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
I don't use this ROM, help each other who use it. Thnx.
DOWNLOAD SF
DOWNLOAD AF
Updates, previous and all ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage 17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
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 14-01-2020 V0 version
Last Updated 14-01-2020
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.
I'd like to get feedback on whether VOLTE is working? Thanks.
wow thanks i'm gonna test now
---------- Post added at 07:26 AM ---------- Previous post was at 07:11 AM ----------
can you share device tree, kernel, vendor for android 10??
szanalmas said:
GoogleDroid ROM 2019-12-27
FULL open GOOGLE APPS included!
Last stable crDroid based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
DOWNLOAD ROM
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-27 V0 version
Last Updated 2019-12-27
Click to expand...
Click to collapse
Thanks for you great rom again, @szanalmas :good:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
I cant install magisk
please make a original TWRP 3.3.1 like 3.2.1
GonzaloxCOM said:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
Click to expand...
Click to collapse
Unfortunately, I can't test VOLTE, Hungarian Telekom is filtering phone model the use of VOLTE...
DT2W works for me, no need to fix it. (I built it into /vendor.)
Your welcome!
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Use Canary: LINK
(But i haven't tested Magisk yet.)
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
cpglbitm said:
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
Click to expand...
Click to collapse
I can't install this version either. It always ends with error 1.
Endys111 said:
I can't install this version either. It always ends with error 1.
Click to expand...
Click to collapse
Use orangefox recovery.
cpglbitm said:
Use orangefox recovery.
Click to expand...
Click to collapse
Thanks, already installed.
Can I flash this rom in Redmi Y1
arvind787 said:
Can I flash this rom in Redmi Y1
Click to expand...
Click to collapse
I do not think so.
Y1 Q10 vendor image and Y1 kernel would be nice.
But I don't know for sure.
If the kernel starts, it is possible. If the LCD and touchscreen match, then the cameras are in question.
But I know that the kernel does not have msm8940 support and Y1 uses 8940 as far as I know.
So you probably won't boot the kernel.
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
1.) Can I go from 14.1 to 16.0, or is there a reason 15.1 should be flashed first?
2.) Will any version ≥ TWRP 3.2.x.x official or unofficial work for both Oreo and Pie?
3.) Is this a correct order of operations:
a.) Boot into FOTA recovery
b.) Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage (also, is there a difference between Format Data and Advanced Wipe > Internal Storage?)
c.) Install .zip for LoS from external SD card (or should I sideload via adb?)
4.) Installing gapps is listed as optional, so I can skip installing an opengapps .zip?
5.) Installing addonsu .zip can be done later?
Thank you!
remi_kamahl said:
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
Click to expand...
Click to collapse
Hello!
1. Yes, you can.
2. For Oreo and Pie 3.2.x.x and 3.3.x.x are optimal.
3a. Check FOTA recovery version, if <3.2.x.x i suggest updating first.
3b. The difference is, that formatting data doesn't wipe internal storage (as far as i remember).
3c. External SD is better (though it's your choice).
4. If you don't GAPPS you can skip it.
5. Yes it can be done later, but i see no reason to not installing it in 3c.
Also think of root management solution, suitable best for you. Will it be internal root manager of LOS (with the help of addonsu binary) or you will use Magisk, which is more complex and has it's benefits too.
Good luck with flashing!
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
This is specifically what I did:
1. Pushed lineage-16.0-20200511-UNOFFICIAL-pollux.zip & twrp-3.3.1-0-pollux.img to external_sd via adb root
2. adb reboot recovery; verified md5sums via terminal
3. In terminal: # dd if=/external_sd/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
4. Reboot into FOTA recovery; made sure the version = 3.3.1-0
5. Wipe: Format Data
6. Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage
7. Install the lineage .zip
8. Wipe Cache/Dalvik and reboot system
After the "Sony Xperia" logo pops up, the Lineage boot animation runs for about 2.5 minutes, then the tablet drops into TWRP (RescueParty).
I can restore a 14.1 backup I made before flashing, and the tablet will boot again successfully.
Not sure where to go from here/not sure which specific log file would be necessary—or even available—to diagnose the problem (dmesg, logcat, Console-ramoops).
remi_kamahl said:
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
Click to expand...
Click to collapse
This happens sometimes. Try to wipe everything ones again and flash LOS via TWRP.
FYI lineage-16.0-20200609-UNOFFICIAL-pollux.zip build is available.