Related
CyanogenMod is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system.
Code:
/* Your warranty is now void.
/* I am not responsible for bricked devices, dead SD cards,
/* or you getting fired because the alarm app failed.
/* If you have any concerns about features
/* included in this ROM, ask before flashing it!
Information
I present you with Android 6.0.1/CM13 for the Sprint Galaxy S4. This is a WIP, I try to work on it when ever I get a bit of free time.
I will try to post a new weekly build once a week or sooner.
The newest build will be at the top of the downloads list.
Prior to Installation
1) I recommend using and/or upgrading to TWRP 3.0.0 (Install version via 2.8.4 zip, then flash 3.0.0 img to upgrade)
2) Make a complete full backup! I cannot stress this enough! Boot, System, Data, Cache, everything. If for some reason this build doesn't work out for you, no biggie go restore.
3) Full wipe of the system is required (Dalvik/ART Cache, System, Data, Internal Storage, Cache). CM13 is based off android 6.0.1 and is a completely new version requiring a complete new install.
4) Download and have ready in the device's sim card Gapps Version "Arm, 6.0, Pico". (Other variants may work, I have not tested them all)
5) Download and have ready in the device's sim card the new jfltespr CM13 Rom (download below).
Installation
After wipe is fully properly completed...
Reboot in to recovery and go to "Install".
Search for the new Rom.zip where you stored it in the sim and select, DO NOT "Swipe to confirm Flash" at this time, we have to install Gapps first.
BEFORE you swipe, select "Add more Zips" and search for your GappsVersion "Arm, 6.0, Pico" and select.
If you flash the Gapps after the CM install, you will have an error loop so flash during initial install is a necessity.
Now proceed to "Swipe to confirm Flash" and Reboot.
First boot takes some time, but shouldn't take more then 10-15 mins total and progress shouldn't be stalled at any point past 5 mins.
Downloads
cm-13.0-20160321-UNOFFICIAL-jfltespr.zip
cm-13.0-20160321-UNOFFICIAL-jfltespr.zip.md5sum
cm-13.0-20160311-UNOFFICIAL-jfltespr.zip
cm-13.0-20160311-UNOFFICIAL-jfltespr.zip.md5sum
Version Information
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.4.x
Status: Beta
ROM Firmware Test Phone: OK3
Android Security Patch Level : March 1, 2016
XDA:DevDB Information
CM13 jfltespr, ROM for the Sprint Samsung Galaxy S4
Contributors
Novus (aka ThomasJoseph315)
Source Code: https://github.com/CyanogenMod
Build Notes
I've noticed that the APN settings are hard to modify. This may change at a later date, but for now it is what it is. If you use an MVNO like do, you will need to flash the APN settings during the rom flash process just like Gapps. I personally have boost mobile and Moped_Ryder has made a very well Boost Mobile zip, though I had to modify slightly with the settings to get LTE working consistently. If you need a zip for your carrier, download the Boost Mobile Zip Ver-2.2 and use notepad++ to edit it to suit your needs.
If you have LTE, but are still having sms issues, install Chomp SMS, it worked right out of the box for me, but you can also set apns manually within the app itself if needed.
Possible bug with Gapps. On my first boot, I installed Gapps Mini and was getting download errors from the play market. I re-flashed with Pico, seems to be working.
Looks dope! Going to have to test it out! Also, I would recommend you add screenshots!
Thanks, I'm expecting my Sprint S4 soon to use on Ringplus. Is there a zip made for R+ or do I not need one?
New Rom Freshly built. Also don't forget to read the build notes about the connection optimizer
GSM Doesnt Work
GSM doesnt work anyone CM 13. What can I do?
Emergency Calls Fail
Emergency Calls cause the device to Lockup and require a reboot, Unable to make emergency calls at all. Other than that GIANT problem, I love the build!
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. Install latest mm stock ROM to update them
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONNote1: if you are on SM-A500FU you don't have to follow this section. Just follow the "How to install" one
NOTE2: some device requires some modifications in blobs and/or in device tree in order to get RIL worling
How to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Install the zip of lineageos rom
2) Install RIL fix zip from this thread's attachements
3) Flash gapps (optional but better)
4) Reboot and enjoy
For people running multirom with lineage as secondary ROM:
1) Install the zip of lineageos rom
2) Install gapps (optional but better)
3) Download (from this thread's attachements) and open RIL fix zip for your device
4) Open (inside the zip) /META-INF/com/google/android/updater-script
5) Remove these two lines:
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
6) Save the new file and close
7) Go in twrp "Advanced"->"Terminal" and run this command:
ln -s /sdcard/multirom/roms/ROMNAME/system /system
Note: if the output of ln command is "File exists" you made a typo, so, re-run the command without making typos (tab helps); if it gives no output, you typed it correctly, so, you can proceed to the 8th step
8) Flash RIL fix zip
9) Reboot and enjoy
NOTE: If you don't find the RIL fix from your variant and you have RIL problems like sim card not detected, read the section for people with RIL problems and follow the instructions
Knowing Bugs
None for now
Report bugs here, or at https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
F2FS Guide
If you want to use F2FS, first you need a twrp that supports F2FS partitions formatting like mine:
https://www.androidfilehost.com/?fid=817550096634793304
Then, reboot in twrp, go in "Wipe"->"Advanced Wipe"->Select "System" box->"Repair or Change File System"->"Change File System"->"F2FS"
Do this also for "Data" and "Cache" partitions
NOTE: Everything in the partitions you turn into F2FS will be deleted!!!
NOTE: If you turn userdata partition (/data), everything in /data/media/0 (/sdcard) will be deleted!!!
Now, open the zip of lineage os and change:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
to
mount("f2fs", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
Read this if you are having problems with RIL
If you have issue with RIL, post a zip with these libs taken from stock rom, and I'll create a flashable zip:
Code:
/system/lib/libsec-ril.so
/system/lib/libsec-ril-dsds.so (for dual sim variants only)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.1
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.1
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.0
Telegram group: @GalaxyA5dev
Telegram channel for project updates: @ds01news
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-02-17
Last Updated 2017-02-17
CHANGELOGFifth release (07/09/2017):
Support calls through LTE (VoLTE)
Fix touchscreen freezes on wakeup
Fix GPS: Now it takes about 10 seconds outdoor and 20 seconds outdoor to get the position (these values may change a bit)
Remove NFC button and everything related to NFC. Since it always stucked on turning on, his crashes were slowing down the system a lot
Fourth release (22/08/2017):
Add button to switch data to LTE for variants that support it
Bring CPU core 1 online (active) (improves performance)
Fix touchkey lights
Update some things in ramdisk
Add screencast to record screen
Third release (17/08/2017):
Fix in-call audio
Fix FM radio
Fix LTE (for variants that support it)
Add OMS support for substratum themes (You can download them from google play. See screenshot's dark theme as example)
Add kernel driver to stop touchkey vibration when device is suspended (replaced InputDisabler)
Upgrade kernel to 3.10.106
Lot of other kernel updates and upgrade to LA.BR.1.2.9_rb1.23 (caf)
Upgrade blobs to A500FUXXU1CPG1 (marshmallow)
Add F2FS formatted /data,/system,/cache support. To do it you also need my twrp 3.1.1. (download in first post) or a twrp that supports f2fs formatting
Improved battery life on suspend (fixed doze)
Remove "ANDROID IS NOT SEANDROID ENFORCING" warning on samsung splash screen
Obviously compile ROM on latest lineage sources
Second Release (17/02/2017):
Fix camera that couldn't take videos
Add touch screen gestures
Minor updates to kernel and device tree (see github commits)
First Release (18/01/2017):
Fixed Screen Rotation
Fixed Cellular Data
Lots of minor updates in kernel, device config (see github commits)
NOTE: You can see all changes (github commits) here: https://github.com/DeadSquirrel01/android_device_samsung_a5-common/commits/cm-14.0
and here:https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx/commits/cm-14.0
And for kernel here: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916/commits/cm-14.1
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Or have you misplaced it here and it belongs there?:
https://forum.xda-developers.com/samsung-a-series
saintsimon said:
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Is this clutter supposed to look clever? Or have you misplaced it here and it belongs there:
https://forum.xda-developers.com/samsung-a-series
Click to expand...
Click to collapse
Damn, I will ask to a moderator to move it
Good work my friend keeping an eye closely on this thread and wating penalty for audio fix to use it as daily driver
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
unimke said:
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
Click to expand...
Click to collapse
Please read the thread and follow it:
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
Click to expand...
Click to collapse
Ok
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
aryan1997 said:
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
Click to expand...
Click to collapse
Its only for a500fu variant only...waiting for another variant..cheers man..
leviz0689 said:
Its only for a500fu variant only...waiting for another variant..cheers man..
Click to expand...
Click to collapse
Doh, still don't know why people don't read the full thread (or at least first 4-5 lines also wit "NOTE" in bold) and then cry if it doesn't work
Anyway that's not only for a500fu, when i have time I'll upload A500XX version, too
Sorry man..im only answer that comment too...
leviz0689 said:
Sorry man..im only answer that comment too...
Click to expand...
Click to collapse
You should ignore those comments
leviz0689 said:
Sorry man..im only answer that comment too...[/QUOTE
Dude, if you want to developers continued to work on a project, stop the ETA, wait for a stable version. The developers are people too, they have their own lives, and they do not have to answer stupid questions everyday The Developers works very hard, be patient.
Sorry, if you understand me, i don't speak English. )
Click to expand...
Click to collapse
DeadSquirrel01 said:
You should ignore those comments
Click to expand...
Click to collapse
Sorry, If I offended you in any way. I know that you work very hard and I really appreciate your work. Thanks for all of it.
Its just that there was a section in the post on how to install the Lineage OS on A500xx devices.
So, I just wanted to know that if there is an error or did I do something wrong.
I did not wanted to be rude or anything. Once again SORRY !!!!!!
DeadSquirrel01 said:
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. you can download them HERE (for A500FU only) thanks to @jimbomodder that has uploaded them or you can easily extract them in stock firmware
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONHow to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Download the sm-a500xx cm-14.1 zip on "Downloads" section"
2) For make "port" process a bit easier do as following:
_1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
2_a) If your device is dualsim, go to stock rom and copy /system/lib/libsecril.so and /system/lib/libsecril-dsds.so in the zip in system/lib/ Then open the system/build.prop in the zip and add:
persist.radio.multisim.config=dsds
3) Flash it and enjoy lineageos on you SM-A500XX variant!!
Knowing Bugs:
_Camera cannot take videos
_Audio during calls bug
Segnale other bugs if u find in bugs section or here https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.0
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.0
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.1
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-01-18
Last Updated 2017-01-18
Click to expand...
Click to collapse
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
ian0326 said:
LineageOS 14.1 for Galaxy A5 A500xx
You've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
Click to expand...
Click to collapse
you take /firmware/image and /firmware-modem/image from your stock rom and put them in /system/etc/firmware in the zip
hit thanks if it helped
You can post screenshots of what exactly the device would look like after installing the rom ?
Cannot install on samsung A500F updator error 7
carlossennin56 said:
You can post screenshots of what exactly the device would look like after installing the rom ?
Click to expand...
Click to collapse
Now i have rr on my device, maybe I'll add them later, but they are basically the same as cm14.1
Code:
/*
* Your (probably expired) warranty is now void.
*
* 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.
*/
LineageOS 16.0 for Samsung Note N7000
Beware, you are about to enter a dangerous zone!
ABOUT
This is an unofficial Pie build for the Galaxy Note (N7000) based on LineageOS 16.0.
Read the sections below carefully to understand the status of this ROM and how to prepare your device for installation.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION FROM STOCK
Follow these steps if you are coming from stock. You will need access to a PC.
1. Prepare Odin, Samsung USB Drivers, PhilZ CWM Odin Flashable, and your phone with a stable USB connection.
2. Install the Samsung USB Drivers and fire up Odin.
3. Select AP and choose the PhilZ CWM Odin Flashable package.
4. Proceed to flash. Once done, reboot your device into recovery.
5. You should be in CWM recovery now. Flash this zip to get TWRP IsoRec: 20210209-boot_n7000-twrp_i9100_3311.zip
6. Reboot recovery. You should now enter TWRP IsoRec recovery. Proceed to the installation steps below, except for step 2.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration:
- Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip - Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card (only in Android 7).This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired, or boot_magisk.img if you need Magisk support.
8. Prepare a coffee or tea and sit back on your couch. Click to reboot system, BUT DO NOT SWIPE TO INSTALL TWRP APP or you will end up in a bootloop!
9. Remember to install Magisk Manager if you need Magisk support.
DOWNLOAD
Google Drive
SOURCE
GitHub - leewp14/local_manifests at lineage-16.0
Contribute to leewp14/local_manifests development by creating an account on GitHub.
github.com
GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000) - GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
github.com
LineageOS 16.0
LATEST BUILD
lineage-16.0-20210211-UNOFFICIAL-n7000
kernel-e604934cd028ba34c8a52d6898658a2e6053ad8e (hikuii597)
magisk-v21.4
NOT WORKING/UNTESTED
- GPS/AGPS: untested, A-GPS not working
- DRM: untested
- IPv6: no connectivity
- Bluetooth: in-call audio not working
- WiFi: extremely reluctant to auto-connect
- Kernel: app requires restart to use storage after granting storage permission
- Kernel: random reboot freeze at offline charging
- Kernel: requires toggle MagiskHide on each reboot to enable MagiskHide
BUILD-SPECIFIC NOTES
- PowerHAL has been removed to provide flexibility in adjusting CPU governor.
INSTALLATION NOTES
- When prompted in TWRP, do not install TWRP Updater app as it will cause softbrick.
- To pass SafetyNet, you must use boot_magisk.img and toggle MagiskHide on every boot.
- Do not update Magisk! Always stick to the version that the build provides.
Changelog
20210211
- general: upstream updates, ASB 2021-02
- kernel: enable RPFILTER (fixes tethering)
- kernel: switch back to PegasusQ governor with hotplug enabled
- kernel: restore mali400 to stock configuration (166/266MHz)
OLD CHANGELOG
minors 20200809
- device: revert lineage-17.1 configuration changes
- device/kernel: enable zram at 384MB with dual stream compression
- kernel: revert lineage-17.1 binder changes
20200928
- general: upstream updates, ASB 2020-09
- frameworks/base: upstream updates
- kernel: revert lineage-17.1 changes, enabled swap (thanks to @goodwu for notifying)
20200809
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali- device-related: merge lineage-17.1 changes from @rINanDO
20200614
- general: upstream updates, ASB 2020-06-05
- device: merge lineage-17.1 changes- device: remove PowerHAL- hardware: default video buffer size to 1080p- kernel: mali400 reconfiguration, use 133Mhz, 160MHz, 266MHz.- kernel: lock mali to 160MHz during 1080p playback- kernel: disable CPU hotplug- kernel: use interactive CPU governor- kernel: use 500MHz as base CPU frequency- kernel: reconfigure thermal throttling, refer commit- kernel: add TriangleAway support, refer commit- kernel: remove a whole big bunch of logging that your grandpa never check on it
20200417
- galaxys2-common: bring back PowerHAL
- kernel/galaxys2-common: added Lineage Trust USB Restrict support (untested)- kernel: cherry-picked Syncthing-Fork "NAT transversal" fix (credits to @TheNatureOne)- kernel: switch to autosuspend (full credits to @rINanDO and @ChronoMonochrome)
20200407
- n7000: update GPS configuration
- n7000: update build fingerprint- n7000/kernel: add TriangleAway support- galaxys2-common: reconfigure wifi configuration- galaxys2-common: user configurable SWAP- galaxys2-common: actually fix in-call audio control- galaxys2-common: kernel modules to system- galaxys2-common: add Magisk build support (credits to @rINanDO)- galaxys2-common/kernel: bring over LOS 17.1 commits (credits to @rINanDO)- kernel: implement charge current control (credits to @TALUAtXDA)- kernel: prevent LCD lock busfreq- kernel: reconfigure ASV/DVFS for BUS/GPU- kernel: remove inbuilt recovery- kernel: bring back PegasusQ, adapted from Perseus-S3 (credits to @AndreiLux)- kernel: raised safefreq to 1.4GHz- kernel: bluetooth stack update (credits to @TALUAtXDA)
20200205
- kernel: cherry-pick mali400-r3p2-rel4 (don't expect anything from this!)
- kernel: disable modules support, KSM, LZ4 ZRAM and many other unnecessary stuffs- kernel: added GCC optimization flags, build kernel with -Ofast- kernel: a whole lot bunch of changes which is too much to be listed here- kernel: default CPU governor to OnDemand- kernel: modify CPU frequency steps back to 6steps- kernel: modify GPU (mali400) to 2steps, 190MHz and 267MHz- kernel: increase lowest busfreq from 160MHz to 190MHz- kernel: increase display frequency from 57Hz to 59.94Hz- kernel: decrease video engine clock from 267MHz to 190MHz- kernel: decrease shared GPU memory from 512MB to 256MB, increase GPU low-level memory to 24MB- kernel: slightly-slightly tune throttling configs, first throttle to 1200MHz, second throttle to 1000MHz- kernel: bring back FB_BLANK- kernel: adjust CONFIG_HZ to 300- kernel: add/enable exFAT, NTFS support- galaxys2-common: remove PowerHAL- galaxys2-common: revert use low-end video codecs- galaxys2-common: update whole bunch of framework configs- galaxys2-common: disable wifi adapter debug- galaxys2-common: more platform specific gcc optimization flags- galaxys2-common: fix USB info configuration- galaxys2-common: build libsecril-client- galaxys2-common: decrease ZRAM to 128MB- galaxys2-common: enable AOD (Always-On Display)- galaxys2-common: actually make macloader works- galaxys2-common: modify healthd to blank screen first before power off or reboot attempt in offline charging mode- n7000: rework GPS configuration (don't expect anything from this!)- vendor/samsung: add prebuilt si4709 FM driver- general: upstream source updates, security patch 2020-02-05
20191009
- kernel: panel brightness optimization from i9300
- kernel: adjust unified memory allocation size- kernel: disable logging- kernel: disable pegasusq core lock- kernel: switch to ZEN I/O scheduler- kernel: fix tuning table for Q1 (credits to rINanDO)- kernel: misc source updates from rINanDO, ChronoMonochrome, ComicoTeam- galaxys2-common: remove SamsungDoze- galaxys2-common: use low-end video codecs (credits to ChronoMonochrome)- galaxys2-common: make sure burn-in protection is enabled- galaxys2-common: wifi hotspot channel 1-11 instead of 1,6,11 only- galaxys2-common: platform specific gcc optimization flags- galaxys2-common: lower haptic feedback intensity- galaxys2-common: dual-speaker output implementation (back speaker + earpice speaker)- galaxys2-common: fix RIL PIN unlock (credits to rINanDO)- galaxys2-common: misc source updates from rINanDO- n7000: increase minimum adjustable brightness threshold- n7000: fake vendor security patch level- n7000: conditionally reset max17041 fuel gauge on boot- hardware/samsung: added missing OUI mapping [SEMCO - 50:cc:f8] (credits to J..J)- general: upstream source updates, security patch 2019-09-05
20190522
- Removed LTE network option in Settings
- Fixed GPS and RIL functionality- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)- New cursor icon for stylus (thanks to ComicoTeam)- Added xt_hl support in kernel
20190505
- Initial build
- Exclude RIL and GPS blobs due to non-working RIL and GPS
Hello,
We will have Android Pie on N7000 !!!!
Great and thank you !!!
I will buy a new battery for my Note I think.
Oh my god!
Got my N7000 out of the closet and charging it right now! Gonna flash this right away!
Thank you, @lee.wp14
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
[email protected] said:
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
Click to expand...
Click to collapse
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
lee.wp14 said:
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
Click to expand...
Click to collapse
I see, thank you for this information.
I will try repartitioning in the next build.
Right now, the ROM is working great!
GREAT! I am eager to try it as soon the RIL works! (still using this ancient phone as a backup)
Release 20190522
CHANGELOG
20190522
- Removed unused LTE network option in Settings
- Fixed GPS and RIL functionality
- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)
- New cursor icon for stylus (thanks to ComicoTeam)
- Added xt_hl support in kernel
Notes:
- Be patient when the phone is booting up, if you have a sim lock, wait a while before entering the PIN because telephony stuffs might still be loading. You will get SIM unlock failed error if the telephony stuffs are not loaded finish yet. We are using a 2018/2019 Android on a 2011 phone, be patient
- GPS is tested OK personally by me prior to this release. If you can't get a fix or detect any satellites, make sure your GPS antenna connection is ok.
- Due to upstream changes, we are currently using Autosleep driver to let the phone enter a suspend state (doze). A shorter standby time should be expected.
- Builds are not SafetyNet OK and also not pre-rooted. If you want root, you may flash the addonsu package from LineageOS's website.
- Builds have signature spoofing enabled by default (thanks to rINanDO), you may take advantage of this to replace GAPPS with MicroG.
- This build is tested OK with GAPPS (pico ARM 9.0), please expect a longer boot time if GAPPS is installed.
- I'm not sure why, but earlier before this after I made some changes in the sources, the USB dialog won't show in Notifications panel anymore. To change USB operating mode, go to Settings > Connected Devices > USB
Quote:
1. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.
2. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)
Unquote
That means I need to flash TWRP twice from stock recovery?
John Moore said:
That means I need to flash TWRP twice from stock recovery?
Click to expand...
Click to collapse
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
lee.wp14 said:
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
Click to expand...
Click to collapse
Thanks very much, Lee.
I Can't boot to twrp 3.1.0 EMU Migtation
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Zin Bo said:
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Click to expand...
Click to collapse
Can you reconfirm the situation and possibly list out your procedures?
lee.wp14 said:
Can you reconfirm the situation and possibly list out your procedures?
Click to expand...
Click to collapse
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Zin Bo said:
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Click to expand...
Click to collapse
Can you flash back to stock to make sure everything is still OK and repeat the procedures again and stop before the step of flashing the twrp emu isorec.
Instead, extract the boot.img from the rom zip and copy to phone (you can do it using TWRP usb mtp) or sdcard, inside TWRP choose inage flash mode, and flash the boot.img to Boot partition.
Next restart to TWRP again. If you can go into twrp then you may try flashing the twrp emu isorec. See if it works this time.
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
dclou said:
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
Click to expand...
Click to collapse
Galaxys2/n7000 won't support magisk as our kernel 3.0.101 does not support namespace, which is required for magisk to operate.
Is this ROM Treble based?
Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01
Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!
Reserved
Great work.
Sent from my Mi A1 using Tapatalk
Thanks ??
Nice. Bro you carried legacy ?
nice work waiting for shrp version of this ??
Noice :good:
Sent from my Mi A1 using XDA Labs
This is an update of TWRP Comic Dan?
manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Great job dude ?
Awesome work!
Thank you so much for this.
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.
Where is the survival checkbox??
What is this "inject twrp" does ?
oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option
Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?
Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Instructions for installing Treble-firmware Android 9 based on the vendor from 11/12/2019 for EUI markup.
1. Install Recovery specifying the vendor section.
1.1 Download: "TWRP_VENDOR1".
1.2 We go into our Recovery - Installation - Installing img - Select the downloaded file - Install as Recovery.
1.3 Reboot in Recovery.
2. Installing a patch that changes the markup and creates a Vendor section.
2.1 Downloading: "repart_vendor".
2.2 Install the patch through Recovery - Reboot in Recovery.
2.3 Go to Cleaning - Selective cleaning - everything is selected except Device memory and cleaning.
3. Restore Vendor and Boot.
3.1 Download the "boot_vendor".
3.2 In the archive from the folder BACKUPS\9ba6452 we take the Folder 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d and put it in TWRP\BACKUP\Folder with tricky code\
3.3 Recovery - Select backup 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d - restore - Boot and Vendor must be checked.
4. Select the desired firmware (type ARM64 A (or A only)) in any available place Link Link2
4.1 If the downloaded firmware is in the archive, unpack it to img.
4.2 Installing img - select the downloaded file and install it as System image.
4.3 Reboot in Recovery (May write that the system is not installed, do not pay attention).
4.4 Install the patch "fix_gsi_r1".
4.5 Install Gapps if needed.
4.6 Reboot into the system.
4.7 If there is no sound - put a patch "sound+treble+final".
4.8 If there is no network, reboot into recovery and repeat step 4.4 again.
4.9 If you don't like the color saturation in Gcam - put a patch "video_play6".
• This manual is designed for installation using a PC, if you do not have a computer, download all the files in advance.
• Format data is not necessary, all data will be saved.
• Not all gsi are equally useful and bug-free.
• This instruction is not suitable for installing ported GSIs such as Miui, Flyme, ColorOS, etc.
Patch for rollback, for the 6th markup "restore_6"
The new kernel is based on 11 sources, in an attempt to run 10-11 gsi: "image-new"
10-11 gsi hang on a bootlogo, maybe someone can fix it.
You do everything at your own peril and risk. I am not responsible for bricks.
Source code
Discussion
Big Thanks:
Ampir-nn