Related
[ROM][UNOFFICIAL][6.0.1][E6853/E6803] CyanogenMod 13 for the Sony Xperia Z5 Premium [ALPHA]
{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6853 and the E6803
Code:
*
* Your warranty may be voided !
*
* 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.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions (for the Xperia Z5 !)
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
E68XX_TWRP3_SD_recovery.img
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803, ROM for the Sony Xperia Z5 Premium
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
one
two
three
Previous ("legacy") threads,
by moonbutt74:
CM13 Z5P E6853 Beta -- Updated NegaSpork
[Rootable Kernel/ TWRP 3 - E6833/E6853/E6883 Marshsmellow ] [32.1.A.1.163] AU]
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
dominicstg2 said:
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
Click to expand...
Click to collapse
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
zacharias.maladroit said:
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
Click to expand...
Click to collapse
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
dominicstg2 said:
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
Click to expand...
Click to collapse
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
zacharias.maladroit said:
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
Click to expand...
Click to collapse
dominicstg2 said:
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
Click to expand...
Click to collapse
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Oh has other people had this problem?
zacharias.maladroit said:
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Click to expand...
Click to collapse
dominicstg2 said:
Oh has other people had this problem?
Click to expand...
Click to collapse
yeah, not sure if on Z5 compact,
but certainly on Z5 Premium and Z5
waitting for 6883 ^_^
Thanks Dev.
I join the testing!
Changelog
12.07.2016 == stable/testing/UNOFFICIAL update build
upstream ROM changes 6.0.1_r56 (Android security Patchlevel: 2016-07-01 / 2016-07-05)
ADB enabled by default for better error diagnosis, ADB over WiFi disabled
fingerprint scanner might work
NFC should work again
single SIM ONLY
.
other changes: YOU tell me
.
previous custom kernel (if used) should still work + NFC too, if you encounter issues with NFC please let me know
Click to expand...
Click to collapse
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
zacharias.maladroit said:
Changelog
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
Click to expand...
Click to collapse
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Don't ask for ETAs on XDA. It is rude.
Sent from my SGP311 using XDA Labs
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Work in progress,
please take a look at the CM13 thread for the Z5, will ya ?
there are several factors that influence access and working for
microSD, sim cards (both), fingerprint scanner and others
Hi. Just curious, is it possible if I use this on E6883 (Z5 Premium Dual) and flash Dual Enabler thereafter?
STOCK ROMS
ZUI 11.1.053
Target version: L78011_CN_OPEN_USER_Q00026.0_P_ZUI_11.1.053_ST_190731_qpst
basic version: ZUI_11.1.053
Size: 3.42gb
Link: https://mega.nz/file/YzwUTCwJ#j1v7lTO7Ivokgr2fkSnny5wB01nqCWm4TZu2hUK5xxE
ZUI 4.0.474
Target version: Lenovo_Z5_L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.474_ST_190118_QPST
basic version: ZUI_4.0.474
Size: 3.00gb
Link: https://drive.google.com/file/d/1F0VtbBfxoLdukGMytq8SslcWjqcsLABQ/view?usp=sharing
OFFICIAL ROMS & UPDATES
Target version: 10.5.306
basic version: 10.5.254
upgrade package size: 127.04 Mb & 3.36gb
View attachment 4773407
Applicable models: Lenovo Z5 (L78011)
Upgrade point of view
Support Unicom VoLTE;
Update Lenovo mobile phone customer service hotline number: 400-990-8888;
System Optimization
Fix the problem that the probability of the compass cannot be calibrated;
Fixed WeChat 7.0 avatar and received a message without a prompt tone;
Fix the problem that the HDR icon is also displayed under the HDR close finder frame;
Fix the problem of finding the mobile phone emergency contact does not support segment 166;
Fix the problem of flashback after clicking the QQ flashback after the end of the nighttime extreme power saving;
After the OTA upgrade is fixed, the default theme preview interface is different from other preview interfaces.
Fix the problem that the game volume function cannot be called up when the game voice function is enabled in the game interface;
Fix the problem that the three-letter X-Y-Z on the right side of the address book is manually clicked;
After repairing and unplugging the SD card formatted as internal storage, the "missing SD card device" notification cannot be clicked, causing the internal storage of the mobile phone to be unmounted;
Fix the different carrier card settings. After calling the main card, enter the contact - click any contact - long press the contact number to display the problem that the card 1 or card 2 operator call does not match the actual card location.
Precautions
Please make sure that the phone have a lot of power, power and storage space;
If you have problems with the upgrade, please go to the official Lenovo community for help.
The upgrade process may cause the phone to heat up or consume power for a short period of time. It is recommended that you restart the system again after the upgrade to obtain a stable experience.
DOWNLOAD LINK AFH Link : Chinese Web Link
Full ROM link (3.36GB):- Mega Drive
RETURN FROM CUSTOM to OFFICIAL ROM
Now returning to STOCK is possible
METHOD 1 (RESTORE TWRP BACKUP)
1. Download the TWRP back up of ZUI 4.0.474 from AFH & the Official ZUI 4.0.474
2. Unzip it (Its actually a 2.5 GB compressed file).
3. Now Boot into TWRP.
4. Now connect the mobile from PC and check the Root directory for TWRP>>BACKUPS
5. Make a new folder by name "cd6d6a03 ( change it with the name of your devices, can easily be checked via fastboot devices command) "
6. Put the extracted backup into that folder.
7. Wipe Dalvik,Cache and System.
8. Restore the backup. (Dont worry it will not BOOT your Z5)
9. Now POWER off the mobile.
10. Move to Qfill Mode (Press both VOLUME up+ Down and POwer button).
11. Connect to PC and Restore the Official Rom through QPST.
No more Sahara or Out of Memory error,........................ENJOY
METHOD 2 (TWRP FLASHABLE ROOTED ROM)
Download link: Mega Drive
Method to Flash this rom
Method 1:
1. Download the Zip package
2. Put it into SD Card
3. Boot into TWRP
4. Clear the Cache,Dalvik,Data & System.
5. Flash the package Normally
6. enjoy the Rooted Official PIE.
Method 2:
1. Download the package
2. Unzip it
3. Run the Flash.exe in given archive
4. Check the attachment to learn the Chinese exe meaning
5. enjoy the Rooted Official PIE.
{
"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"
}
METHOD 3 (FOR those who were on ZUI-10 & for going Back to ZUI 10)
Method back to Stock ZUI 10:
1: Flash Stock ZUI 10.5.254 via Qfil
2: Flash TWRP 10.5.254 via Fastboot
3: Flash this rom via Fastboot
Link: https://mirrors.lolinet.com/firmware/gsi/ZUI-AB-9-20190616-ErfanGSI.img.7z
4: Go to Twrp then wipe data. After wipe data choose Reboot System and wait 1 or 2 minutes.
(Your phone will stuck in Lenovo red logo).
5: Flash Stock ZUI 10.5.254 again via Qfil.
==you are completed back to ZUI 10.5.254==
OFFICIAL ROMS
10.5.254 [FINAL] for LENOVO Z5 Android P
ZUI version: 10.5.254
adapter model: L78011
Android version: 9.0
Brush type: QPST/DIRECT over 4.0.474
Compression package size: 3.36G
Package name: L78011_CN_OPEN_USER_Q00025.0_P_ZUI_10.5.254_ST_190404_qpst.zip
WHATS NEW
(fixed or changed issue with the previous one has been released Software comparison):
1. Add new application lock to support face unlocking mode;
2. Add U health camera to recognize calorie function;
3. New negative one-screen card display, support step counter / commute recommendation / fast payment, etc.;
4 New desktop editing mode, support more desktop layout, please press and hold on the desktop to enter the view;
5, the new control center and the notification bar are integrated, and support the desktop to slide out the global search;
6, the new U-touch gesture, Cut everything to turn on the flashlight and turn it around to turn on the camera, please check it in Settings->4D U-touch;
7. Fix the problem of background sound break of the game;
8. Fix the problem that the shutdown charge cannot be extinguished;
9. Repair the upgrade process phone stopped running problem of sporadic;
10, automatic optimization of backlight brightness curve, the backlight is too bright indoor solve the problem;
11, repair slip cut back on the desktop screen shot Small window interface stuck, unable to withdraw from the problem;
12, repair ultra-definition mode watching videos / landscape orientation games, even now question the status bar displays black bars;
13, is in the pocket repair mode, frequently light off screen calls Face Detecting problems that cause the phone to heat up;
14, repair power-saving mode / night power-saving open, even after a long standby, the APP can not access the Internet;
15, repair the call screen in the state of the call, press the power button to press the screen repeatedly, the caller animation does not display The problem;
16, repair even now through the fire line / gun warrior / stimulating the battlefield game interface screen brightness suddenly dimmed, the notification bar brightness adjustment is invalid.
Links credits to @ gfofanov
https://mega.nz/#!vuoA0SbJ!6HuGdtaNDV4XzNZbOeWB9fDiiP64kbcbo36_4j-8k-4
https://drive.google.com/file/d/10vJrO1-_-VdIV5rfhbYDuc6dUgxkoyjF/edit
New URLs:
https://mirrors.lolinet.com/firmware/lenovo/l78011/L78011_CN_OPEN_USER_Q00025.0_P_ZUI_10.5.254_ST_190404_qpst.zip
AND
https://office300-my.sharepoint.com/:u:/g/personal/fofanov_office300_onmicrosoft_com/EWzxvMBijR5Dk__iWz8RYuoB6rJ8jvNQjcdXts7J1UCQcg?e=pckW58
CUSTOM ROMS
MIUI
MIUI 10 [9.5.9] for LENOVO Z5 Android P Credits to Art Chen
Everything is working except Face Unlock
…….Images in attachment
https://mega.nz/#!YiB0XIJC!aykBuDqWxQWsbWc0kcNnBhtHy_5eqDO1Giw_avvj2WQ
MIUI 10 [9.3.14]17th March 2019 Update for LENOVO Z5 Android P Credits to Art Chen
his is already the third edition. @Art_Chen The author is still very diligent. Now I
have fixed the following problems:
Optimize the fluency of the system (the overall use is smoother, the gesture operation does not drop frames) to
improve the stability of the system (from Android 8.1 Upgraded to Android 9)
Fixed several bugs (fixed volte not available, aptX audio no sound, etc.)
https://drive.google.com/drive/folders/1NdveI-miKPs6RDf9yH9HIwDgJrkkWi5F
GDrive Link
MIUI 10 [9.2.21] for LENOVO Z5 Android P Credits to Art Chen
his is already the third edition. @Art_Chen The author is still very diligent. Now I
have fixed the following problems:
Optimize the fluency of the system (the overall use is smoother, the gesture operation does not drop frames) to
improve the stability of the system (from Android 8.1 Upgraded to Android 9)
Fixed several bugs (fixed volte not available, aptX audio no sound, etc.)
A small number of known bugs: fingerprint payment is not available (can be used with Tai Chi or Ed Xposed), there may be some bugs but I am temporarily
Didn't find Batterey Drain
Fix gps , theme , lockscreen wallpaper
If you are using miui, Update don't need to clear the data
DOWNLOAD:-
https://mega.nz/#!6rwQjA6B!z2xdnixiyCt5us6Cjeh9mIkgnqR4jnRLoiyZwt2Mink
BlueTooth Patch (Only if not working)
GDrive Link
MIUI 9.1.31 for LENOVO Z5 Android OREO Credits to Art Chen
Whats in this ZIP?
[attachment="15308074:miui.jpg"]
Download Link
Google Drive Link
BlueTooth Patch (Only if not working)
GDrive Link
BUGS:- No (If found Bluetooth issue use above given patch)
METHOD for FLASHING
1. Tools inside use them
2. OR use TWRP.
use at your own risk
Click to expand...
Click to collapse
PIXEL EXPERIENCE
* PE (10-05-2019): https://mega.nz/#!M65R0Qwa!OhxqBiOuU...cTXiQTTSIoGQdE
Bugs: Just Charging light else is clear
* PE (22-05-2019): https://mega.nz/#!9hxzBCjZ!QgoiTDZXOoAhHXDFWZ3GkBPrFPN2V7qlzLQt855ZLIw
Bugs: Just Charging light else is clear
* PE (06-06-2019): https://mega.nz/#!m3oVRaBY!KfFAG6mHiVsQCz2N1SixAHjg5GFaZbaRe-JO3Bz0CEg
Bugs: Just Charging light else is clear
* PE (18-06-2019): https://mega.nz/#!9xBD1AJB!atWWvl_0nXFXQxYT1gHjg9rzX6Kpqivtd7lawX_sEuw
Bugs: Just Charging light else is clear
************************************************************************
RESCRUSSION REMIX
* RR (16-04-2019): https://mega.nz/#!43hRxYJR!hwKWkOt3S...auq-EXSu7IrN8s
Bugs: Just Charging light else is clear
* RR (24-05-2019): https://www.androidfilehost.com/?fid=6006931924117883160
Bugs: Just Charging light else is clear
* RR (15-06-2019): https://drive.google.com/open?id=1p3d-itVhjkI4TdDZLzQSewHPAin6Y3R_
Bugs: Just Charging light else is clear
************************************************************************
HAVOC-OFFICIAL (No GApps)
Havoc-OS v2.6 Official Build (Credits to developer)
What's New (google translator):
* Added double tap for wake-up (must be supported by device / kernel)
* Added call recording to Dialer
* Added toggle switch for A -GPS
* Reduced minimum brightness
* Mi9 / Mi9SE fingerprints re-added to display (FOD)
* Added overlay (see OP) to enable cutout controller (hide label, ...)
* HAVOC (12-06-2019): Download Link
USEFUL BEFORE INSTLLATION
1. use 3.2.3 TWRP recovery for 4.0.474 (Link Here)
2. Flashed the same Boot Image on Partition A & B. (Boot + Vendor Image)
3. Than the Same Vendor Image.
FLASHING PROCEDURE
1 . Download TWR.img ( only single file now dont worry ) copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type adb devices
5. type fastboot boot twrp.img for temporary if you want permenant fastboot flash boot twrp.img
6. fastboot reboot
7. now wipe everything
8. now flash the rom
9. remeber if you are on slot a rom will install on slot b and press reboot to recovery again after installing rom and now switch to slot b and select reboot system now your phone boots to slot b
10. if you are on slot b rom will install on slot a and press reboot to recovery again after installing rom and now switch to slot a and select reboot system now your phone boots to slot a
11. congratulations .
OTHERS/BETAs
10.5.254 [BETA 5] for LENOVO Z5 still BETA Android P
Applicable models: Lenovo Z5 (L78011)
Target version: 10.5.254 or higher
Basic version: 4.0.474/10.5.223
Upgrade package size: 90 Mb almost
push status: Public
following is the update content of 253 version.
will share Later
Download Links:- G-Drive credits to @M.Z.F
10.5.248 [BETA 4] for LENOVO Z5 still BETA Android P
Applicable models: Lenovo Z5 (L78011)
Target version: 10.5.248 or higher
Basic version: 4.0.474/10.5.223
Upgrade package size: 140 Mb
push status: Grayscale push
following is the update content of 248 version.
Fix the problem of background sound break of the game;
fix the problem that the shutdown charge cannot be extinguished;
fix the problem that the occasional phone stops running during the upgrade process;
fix the post-upgrade settings -> display And the problem of no brightness mode;
fix the problem that the camera menu is hidden after the top of the screen is displayed;
optimize the automatic brightness backlight curve to solve the problem of over-brightness in the room;
repair the activation of the overseas Internet, prompt to select the data master Card problem;
fix super clear mode to watch video, horizontal screen game, occasional status bar shows black bar problem;
repair connection Bluetooth After the headset dials the WeChat voice/video call, both sides have silent problems;
fix the called call in the lock screen state, press the power button multiple times to turn off the screen, the caller animation does not display the problem.
Download Links:- CloudMail credits to @gfofanov
ZUI 10.5.23 [BETA 3] for LENOVO Z5 still BETA Android P
Applicable models: Lenovo Z5 (L78011)
Target version: 10.5.230 or higher
Basic version: 4.0.474/10.5.223
Upgrade package size: 1.49 Gb
push status: Grayscale push
Upgrade the point of view
Upgrade Android 9.0 system;
new face recognition solution, need to re-enter facial information in settings -> password, fingerprint and face recognition;
new ZUI10 design style, add 4D U-touch gestures, magic input box, small window broadcast Video and other functions;
system optimization
New nighttime extreme power saving;
new application lock to support face unlocking mode;
new U health camera recognition calorie function;
new negative one-screen card display, support for step/off-work advice/fast payment, etc. ;
new desktop editing mode, support more desktop layout, please see the press to enter the desktop long;
the new control center and notification bar integration, and support on the desktop slide to bring up the global search;
new U-touch gestures, cut everything open flashlight Turn the camera on and turn it around, check in Settings -> 4D U-touch.
Download Links:- CloudMail - : - Mega
ZUI 10 (ported) for LENOVO Z5 Android OREO Credits to Ketai
I understand from guglotransleyta (but it's not exact):
Launcher 5.0 http://4pda.ru/pages/go/?u=https://...LrMKEhvRh0DVNwjccXmsIS3sCBb_AOCAvE&e=81841256
launcher 10.0 http://4pda.ru/pages/go/?u=https://...Dcu3z8zrAdTFCAiIopeOpKnjyf70vI7wYw&e=81841256
Firmware 3.9.075 https%3A%2F%2Fyadi.sk%2Fd%2FHHqqn2P73Zkmpn&e=75597985 (Password for archive: w3bsit3-dns.com)
Firmware 5.0 http://4pda.ru/pages/go/?u=https://...0cO7LPUOMAgwBrhHEyl8ofGvCycokfHbZU&e=81841256
Firmware 10.0 http://4pda.ru/pages/go/?u=https://...0pyMvNo3ckYJSnNm5Hdyqtrwh2NDbF6FCg&e=81841256
As I understand it, there should be 075 with the unlocking bootloader.
Those. The boot-loader is unlocked, debugging is enabled, then into the fastboot and we sew, the batch file in Chinese is full.
Steps:
1. Flash 3.9.075 via QPST (if you already have 3.9.075 leave this step)
2. Unlock Bootloader.
3. Flash TWRP.
4. Flash ZUI 5.
5. Flash ZUI 10
DONE!
BUGS:- None till now
Everything is at your own risk, I did not set myself.
Some link was such a translate in
https: //club.lenovo.co...hread-5412231-1-1.html
MODS PLEASE MAKE NEW SECTION FOR LENOVO Z5 DEVELOPMENT AS OFFICIAL PIE IS ARRIVING SOON
How to FLASH MIUI/OTHER ROMS?
Always make a backup first. and copy the rom in your mobile
1. Boot into TWRP (means you must have bootloader unlocked and only 3.9.075 & 3.9.500 are capable to unlock bootloader)
2. Now in TWRP wipe the cache and dalvik with system
3. (a). Switch to IMG mode in TWRP.
(b). There are 3 image files in the downloaded ZIP folder named as images ( patched_boot,System & Vendor)
4. first flash System, than Vendor and last patch.
5. Done & REBOOT (it might said no ROM installed ignore it.
MIUI 10 is the only rom after flashing it you can go back to stock.
How to FLASH OFFICIAL ZUI 10.5.230?
1. Download
2. Upload to the root of the root memory
3. Rename the package to update.zip
4. Update it in 3 dots above in the official update application.
--------------------------------------------------------------------------------------------------------
wana GO BACK to STOCK from CUSTOM? Follow this post
TWRP for PIE? Follow this post
--------------------------------------------------------------------------------------------------------
Problems & There Solutions.
1. Have you ever get annoying thing like Insufficient storage to flash. Well today, for A/B device, we have got a the great guide for you!
http://oxygenosguide.lunarixus.party
* Notes that re-partitioning your device may cause the damages to your device. Do at your own risk!
* DO NOT TRY ON MOTO DEVICE!
Register your devices at this link to get the Z5 stable updates early than others
https://www.wjx.top/m/25027506.aspx
25-03-2019 : Update Official PIE ZUI 10.5.230 added
29-03-2019 : Update Official PIE ZUI 10.5.248 added
11-04-2019 : Update Official PIE ZUI 10.5.254 added
17-04-2019 : MIUI 10 [9.3.14] 17th March 2019 Update for LENOVO Z5 added
09-05-2019 : MIUI 10 [9.5.9] 9th May 2019 Update for LENOVO Z5 added
17-05-2019 : PE & RR [9.3.14] April & May updates Update for LENOVO Z5 added
19-05-2019 : Link for RETURNing FROM CUSTOM to OFFICIAL ROM added.
20-05-2019 : Link for backup of OFFCIAL ROM via TWRP added.
30-05-2019 : Link for RR update added.
08-06-2019 : Uploaded the official 10.5.306
14-06-2019 : Uploaded PE new Update.
15-06-2019 : Uploaded PE new Update.
16-06-2019 : Uploaded HAVOC OS official for Z5.
17-06-2019 : New Method for Returning to STOCK ZUI-10 added.(FOR those who were on ZUI-10 & for going Back to ZUI 10)
22-06-2019 : Uploaded 10.5.306 official full ROM for Z5.
23-06-2019 : Uploaded PixelExperience update for Z5.
30-05-2020 : Uploaded Stock Rom ZUI_4.0.4.74 update for Z5.
Miui
M.Z.F said:
Reserved
Click to expand...
Click to collapse
Miui rom is chinese rom. I wanna EU Rom. Please update EU Rom
1}
FLYME 7 for LENOVO Z5 Android OREO
will be posted later
.........
= When is FlyMe available?
2}
MODS PLEASE MAKE NEW SECTION FOR LENOVO Z5 DEVELOPMENT AS OFFICIAL PIE IS ARRIVING SOON.............
= How do you know this and When is it officialy coming out?
3}
Do you have some screenshots of this Zui 10?
xperia_bird said:
1}
FLYME 7 for LENOVO Z5 Android OREO
will be posted later
.........
= When is FlyMe available?
2}
MODS PLEASE MAKE NEW SECTION FOR LENOVO Z5 DEVELOPMENT AS OFFICIAL PIE IS ARRIVING SOON.............
= How do you know this and When is it officialy coming out?
3}
Do you have some screenshots of this Zui 10?
Click to expand...
Click to collapse
yes Flyme is vailable but very buggy thats why did not share over here.
xperia_bird said:
1}
MODS PLEASE MAKE NEW SECTION FOR LENOVO Z5 DEVELOPMENT AS OFFICIAL PIE IS ARRIVING SOON.............
= How do you know this and When is it officialy coming out?
Click to expand...
Click to collapse
Beta Testing is in progress for official 9.
M.Z.F said:
Beta Testing is in progress for official 9.
Click to expand...
Click to collapse
Thats great! Can you give a timeline?
This custom ROM, is it also valid for the Lenovo Z5s L78071?
Wait for final release Pie.
hi,
is miui rom multi language rom?
raccoon616 said:
This custom ROM, is it also valid for the Lenovo Z5s L78071?
Click to expand...
Click to collapse
Noo
xperia_bird said:
These are not flashable ZIP files, you need to flash this with Fastboot. Please put this in your post, at least how to flash the files in the right way. Also the batch file in the ZIP is not readable by cmd.
I tryed your flashing steps and now the phone is not booting.
Click to expand...
Click to collapse
check OP
erdogan69 said:
hi,
is miui rom multi language rom?
Click to expand...
Click to collapse
Only CHINESE & ENGLISH
this is awesome MZF, can i use your download links in this thread ? I need to create a tutorial for going back to stock.
https://forum.xda-developers.com/pr...-how-to-flash-android-8-1-9-0-t3840839/page87
rendroid15 said:
this is awesome MZF, can i use your download links in this thread ? I need to create a tutorial for going back to stock.
https://forum.xda-developers.com/pr...-how-to-flash-android-8-1-9-0-t3840839/page87
Click to expand...
Click to collapse
For sure
MIUI 10 is the only rom after flashing it you can go back to stock. (Personally tested)
M.Z.F said:
For sure
MIUI 10 is the only rom after flashing it you can go back to stock. (Personally tested)
Click to expand...
Click to collapse
thank you for your work.
i tested first with zui5 and then zui10 they both booted successfully, the only problem i am facing is that vendor and persist doesnt mount, hence mobile network and wifi is not available, and you cant move past the activation screen, so i am working on that
it looks like it is not being mounted because of encryption, so i am force mounting it by flashing it in twrp.
I can't copy MUIU file to internal storage, it says file limit larger than device limit ?
It's more than 4gb
I am on Pie 9. Is that true if i flash MIUI 10, then using QFIL to flash stock Rom, and i can go back to stock???
creedsbg said:
I can't copy MUIU file to internal storage, it says file limit larger than device limit ?
It's more than 4gb
Click to expand...
Click to collapse
Copy it on usb or mmc or format your device on NTFS format FAT file system dosbnot support larger files.
vosathanh said:
I am on Pie 9. Is that true if i flash MIUI 10, then using QFIL to flash stock Rom, and i can go back to stock???
Click to expand...
Click to collapse
i did it and i was a lucky man. :good:
#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk
Welcome to CyanogenMod 11
BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.
Nice Work Matty1993!!
You have been a busy bee :highfive:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol
DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source
Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash
I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
You could mention Treble support means "since XZ1" (unless hacks)
Hoping to carry this on here, since I own the 1 not the 5 In order to de-google my life, I've decided that I am ready for GSI!
A few notes from my flashing weekend;
Following these instructions, from an unlocked Xperia 1 running stock rom, worked for the following;
ExpressLuke's Havoc 3.0
LineageOS 17.x
Interesting thing. These both install to system in 3 parts (when watching the flash to system.
Any other that I tried (installing in 2 parts) did not seem to work.. but then I am new at this. It's entirely possible that some of these failed because I didn't re-flash stock first.
I was also using a patched boot / kernel with a specific magisk version, which might have played a part. Failed are also (obviously) Pie.
Failed flashes were;
PPH Treble AOSP 9
Havoc 2.9 Official
So far, I've been blown away with Havoc. Of the tons of things I've run in the last 24, I've seen the following issues;
1) Call volume on handset doesn't seem to do anything. (Bluetooth works fine)
2) I had one reboot last evening. Since then solid as a rock.
3) Selection of notification sound for fastmail app didn't take right away
I haven't worked up the courage to try setting up twrp yet, so no recovery. I may give magisk a shot later tonight. I need to back this stuff up somehow!
Thanks to @Miustone for replying and making things easier, and @thatguy222 for the info he provided in the Xperia 5 thread!
charlatan01 said:
Hoping to carry this on here, since I own the 1 not the 5 In order to de-google my life, I've decided that I am ready for GSI!
A few notes from my flashing weekend;
Following these instructions, from an unlocked Xperia 1 running stock rom, worked for the following;
ExpressLuke's Havoc 3.0
LineageOS 17.x
Interesting thing. These both install to system in 3 parts (when watching the flash to system.
Any other that I tried (installing in 2 parts) did not seem to work.. but then I am new at this. It's entirely possible that some of these failed because I didn't re-flash stock first.
I was also using a patched boot / kernel with a specific magisk version, which might have played a part. Failed are also (obviously) Pie.
Failed flashes were;
PPH Treble AOSP 9
Havoc 2.9 Official
So far, I've been blown away with Havoc. Of the tons of things I've run in the last 24, I've seen the following issues;
1) Call volume on handset doesn't seem to do anything. (Bluetooth works fine)
2) I had one reboot last evening. Since then solid as a rock.
3) Selection of notification sound for fastmail app didn't take right away
I haven't worked up the courage to try setting up twrp yet, so no recovery. I may give magisk a shot later tonight. I need to back this stuff up somehow!
Thanks to @Miustone for replying and making things easier, and @thatguy222 for the info he provided in the Xperia 5 thread!
Click to expand...
Click to collapse
Thanks for Your great Feedback! Glad i was able to help out Think i will add some stuff to the Guides soon. Wonder if i get Contributer Status now :silly:
Miustone said:
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Check with the manufacturer of the Android device for explicit flashing instructions. Use the following steps as a general guideline:
1. Ensure that the Device has the following:
Treblized
A method for unlocking devices (so they can be flashed using fastboot)
A method for disabling verify boot (for example, vboot 1.0 or AVB)
An unlocked state to make it flashable via fastboot (To ensure that you have the latest version of fastboot, build it from the Android source tree.)
2. Disable verify boot.
3. Erase the current system partition, then flash the GSI to the system partition.
4. Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions).
5. Reboot the device.
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Open up the Zip File and place the 2 Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC
Disable verify boot (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Erase and flash the GSI to the system partition:
Code:
fastboot erase system
fastboot flash system system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Click to expand...
Click to collapse
Please, try to install gcam in lineageos 17!
What happen with drm keys when you flash other roms? I love sound settings of sony ui and settings of display.
I haven't been confident in the gcam build for the 1, but I'm quite pleased with open camera thus far.
The only DRM issue I'm aware of is widevine level dropping. I'm perfectly happy with my unlocked 1.
charlatan01 said:
I haven't been confident in the gcam build for the 1, but I'm quite pleased with open camera thus far.
The only DRM issue I'm aware of is widevine level dropping. I'm perfectly happy with my unlocked 1.
Click to expand...
Click to collapse
Did you notice any degradation in photo / video quality on stock ROM with the bootloader unlocked?
I'm considering unlocking my X1, but I want to know if the consequences are as bad as they used to be a few years ago with the Z2 and Z3.
MeltdownSpectre said:
Did you notice any degradation in photo / video quality on stock ROM with the bootloader unlocked?
I'm considering unlocking my X1, but I want to know if the consequences are as bad as they used to be a few years ago with the Z2 and Z3.
Click to expand...
Click to collapse
As soon as I unlocked I went to a custom ROM, so I didn't test on stock. Sorry. I think there are some people in the ROM section that said pics looked good. They definitely confirmed there was no green or blue tint like there was with those other devices
Just finished flashing, thank you so much with the tutorial. At the -w step, it didn't seem to find the /userdata, and I tried to skip the part and just reboot. After what seems like a bootloop, it automatically rebooted to "Android Recovery" which I assume is a part of the gsi? It prompted me to wipe data and I did, and it booted!
So, a Generic System Image is just a generic version of Android? Essentially then, I could flash other ROMS - some of whom are listed in this thread (Havoc etc) and get a brand new experience? It doesn't say so here in the thread, but I'm guessing I need to unlock my bootloader - correct?
Chima2 said:
So, a Generic System Image is just a generic version of Android? Essentially then, I could flash other ROMS - some of whom are listed in this thread (Havoc etc) and get a brand new experience? It doesn't say so here in the thread, but I'm guessing I need to unlock my bootloader - correct?
Click to expand...
Click to collapse
Yes
does sd card still work?
Just curious, does auto brightness work out of the box for Xperia 1? Using havoc 3.5 on xz2, and autobrightness is the main thing not working for me.
Updated the Thread. No need for the vbmeta Image with Havoc 3.5 (Official GSI with GApps)! Means a more secure Device somehow...
I'm building Overlays for the Xperia 1 & 5 if anyone is willed to grab me the FrameworksResCommon.apk overlay from your device in /vendor/overlay
I need to decompile it, so You can do it anyways if You are willed to. I also need the build fingerprint from the build prop. It should say anything like:
ro.vendor.build.fingerprint=Sony......
The next step for GSIs on our Xperias! I will also look into a GCam Mod for our Devices! Installing Ubuntu 20.04 now...
Beetle84 said:
Just curious, does auto brightness work out of the box for Xperia 1? Using havoc 3.5 on xz2, and autobrightness is the main thing not working for me.
Click to expand...
Click to collapse
Yes bro never had an issue with that.
Thread updated with new Instructions. Added the flashing to A/B without changing the Slot. Added also the flashing of SONYs AOSP Vendors to A/B. Enjoy
PS: Did that as preparation for the MARS_SOM BETA2. Got stunning results with that SOM and PHH AOSP 10... Check it out <3
Can we use also Havoc OS 3.6 then bro and does it have bugs ?
Pandemic said:
Can we use also Havoc OS 3.6 then bro and does it have bugs ?
Click to expand...
Click to collapse
Works just fine like the latest PHH AOSP Versions with passing SafetyNet. I recommend using My latest Guide here to use it. Things that don't Work yet are:
-VoLTE
-Always on Display
-Camera Button
-HDR 4K native Video Playback in Apps
I recommend using Open Camera with CameraAPI2 enabled in the settings since we don't have GCam. Otherwise it's fine to use...
Miustone said:
Works just fine like the latest PHH AOSP Versions with passing SafetyNet. I recommend using My latest Guide here to use it. Things that don't Work yet are:
-VoLTE
-Always on Display
-Camera Button
-HDR 4K native Video Playback in Apps
I recommend using Open Camera with CameraAPI2 enabled in the settings since we don't have GCam. Otherwise it's fine to use...
Click to expand...
Click to collapse
@Miustone do you have telegram btw ? Sorry for OT
Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Installing GSI ROMs
Tutorial:
If you don't know what a GSI is or want to know more about it, see this, this and this
Don't try to flash GSI in custom recovery.
Note:- We can only flash GSIs having android version higher than or equal to stock rom android version. That is if your StockROM Android version is 10, then you can only flash GSIs of Android 10 or higher.
If you are flashing GSI with custom ROM installed, then flash stock ROM before flashing GSI. Since boot and vendor(may), get modified with custom ROM.
Step 1 - Pick your poison in the Treble Forums or from here!
Check below of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B ARM64 version (usually nicknamed (b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.
For example, I am downloading this
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Down) and link it to your PC.
Step 4 - Move the .img file and vbmeta.img you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
fastboot reboot fastboot // Recovery will appear with fastbootd mode
fastboot flash system system.img
fastboot reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w // Skip this if you are updating GSI
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
GSI bugs without having any possible fixes
These bugs are there in my device and I can't able to fix them
DoubleTapToWake with Q vendor
Lift to wake with R vendor
Fingerpirnt(egis) with R vendor
GSI bugs and possible fixes
VoLTE is fixed in Android 11(R) GSIs which are based on AOSP v300j for Q vendor and AOSP v312 for R vendor
we can get VoLTE working by following below
- Goto Settings => Phh Treble Settings => IMS features
- Now Select both Request IMS network && Force the presence of 4G Calling
- Now click Install IMS APK for Mediatek Q vendor.
- Let it complete download (check your notification panel).
It will show IMS installed You may now reboot! as a toast message
- Now click Create IMS APN (Nothing will happen)
- Reboot and Enjoy!
Play Protect not certified can be fixed by following below
- Download https://f-droid.org/en/packages/makeinfo.com.getid/
- Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign In and paste copied Value to it and register
- Reboot
Fix Low Brightness
- Go to Settings => Phh Treble Settings => Misc features
- Check Force alternative backlight scale
- Adjust brightness
Fix et512/egis fingerprint
- See https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/post-85451661
Fix wired ear phones not working
- Go to Settings => Phh Treble Settings => Misc features
- Check Use alternative way to detect headsets
- Reboot
Fix Bluetooth speakers/earphones not working (not tested because I don't have these)
- Go to Settings => Phh Treble Settings => Misc features
- Check Force-disable A2DP offload
- Reboot
Enable USB OTG
- Go to Settings => Phh Treble Settings => Oppo features
- Check Enable USB OTG
If there is no Oppo features in settings then simply run below command in Termux
Code:
su -c "setprop persist.sys.phh.oppo.usbotg 1"
/system partition is read-only
this is the default behaviour of non-vndklite GSIs from v300.j onwards, to get R/W access for /system use vndklite variant.
Click to expand...
Click to collapse
If you have any other issues, tell the developer with logs. See this to know about taking logs.
FAQ
I can't able to use Magisk because of inbuilt phh SuperUser
- To use Magisk, we have to remove inbuilt phh SuperUser first, to do so boot to TWRP and run below commands in PC
Code:
adb shell
mount /system_root
mount -o rw,remount /system_root
rm -rf /system_root/system/app/me.phh.superuser
rm -f /system_root/system/bin/phh-su
rm -f /system_root/system/etc/init/su.rc
rm -f /system_root/system/xbin/su
exit
Now you can able to use Magisk
I can't able to install GApps in vanilla variant
- Simple thing we have to do is to use GApps variant of GSI. If you don't want to use GApps variant for some reason or there is no such thing at all, we need to resize system to increase free space in /system partition. For this we need to use fastbootd mode
Code:
adb reboot fastboot // or fastboot reboot fastboot if your are in fastboot mode
fastboot resize-logical-partition system 4294967296 // 4 GiB
fastboot reboot recovery
Now you can flash GApps package
If your are using UI 2.0 (means R vendor), then you may can't resize system 4 GiB as shown above, to do so we have to remove some unnecessary partitions first, run these commands in PC
Code:
adb reboot fastboot // or fastboot reboot fastboot if your are in fastboot mode
fastboot erase my_heytap
fastboot resize-logical-partition my_heytap 4096
fastboot erase my_stock
fastboot resize-logical-partition my_stock 4096
fastboot erase my_preload
fastboot resize-logical-partition my_preload 4096
Note that instead of deleting those partitions I erased and resized to 4KiB because deleting will cause longer booting time.
Click to expand...
Click to collapse
Spoiler: GSI Recommendations
All my recommendation's latest releases contain fixes for our device.
Ordered by personal preference:
LOS mod (LineageOS GSI)
crDroid
CAOS
Flashing StockROM in TWRP
Note:- If you want to flash older version of stock rom than the one that is installed, then you need to be on GSI or custom ROM to do it.
- Search Software update - realme in Google and go to your region specific site
- Download and place stock .ozip in External storage
- Download and install TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Go to Settings and check Skip Treble Compatibility error
- Choose Wipe and then Format Data and type yes
- Now choose Install and select Micro SDCard in Select Storage that is located in bottom left
- Select Stock ROM .ozip and Swipe for Installation
- After 7 - 15 minutes flash will complete. Choose Wipe Dalvik/Cache
- Reboot
- Enjoy!
Downgrading StockROM using TWRP
- Download .ozip of specific version of Stock ROM that you need to downgrade
- Flash TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Enable 'Skip Treble Compatibility error' in settings
- Flash ozip
- Format Data and wipe cache
- Reboot
Flashing StockROM in Stock Recovery
Note:- If you want to flash older version of stock rom than the one that is installed, then you need to be on GSI or custom ROM to do it.
If you don't have a backup of stock recovery, then you can get one from A.83 which will work on all other versions of UI 1.0 ONLY from here
- Search Software update - realme in Google and go to your region specific site
- Download and place stock .ozip in External storage
- Boot to stock recovery
- Select Install from storage and select storage where .ozip is located
- Click on .ozip and click OK when prompted to Installation package
- After 7 - 15 minutes flash will complete. Click OK in Installation successful. Prompt
- Go back and select Wipe data, enter verification code and select Format data and click on Format
- Click OK in Wiped successfully prompt and it will automatically boot to stock rom
- Enjoy!
Thanks:-
To this
egis/et512 Fingerprint fix
* First check if you have egis/et512 fingerprint by using Device Info HW app and see 'General' => 'Fingerprint'. If you have egis/et512 then follow below
* This needs to have rooted with Magisk
* Flash below attached module in Magisk app to fix fingerprint
This module is only for Realme UI 1.0 Android 10 vendor with Android 11/12 custom ROM/GSI
Credits
- titidlancip
- dodyirawan85
I am just testing AOSP v313 vndklite vanilla to create an overlay for fixing battery stats, status bar height and to set notch cutout.
Overlay made so far is attached below.
To make the overlay work, just place it in /system/product/overlay/and reboot. See if status bar height is increased or not and after some usage battery stats will appear (Setting -> Battery -> 3-dot -> Battery usage). We can check if overlay is applied or not using below commands in Termux su -c "lsof | grep treble-overlay-realme-c12" it will output some lines if successfully applied.
HemanthJabalpuri said:
I am just testing AOSP v313 vndklite vanilla to create an overlay for fixing battery stats, status bar height and to set notch cutout.
Overlay made so far is attached below.
To make the overlay work, just place it in /system/product/overlay/and reboot. See if status bar height is increased or not and after some usage battery stats will appear (Setting -> Battery -> 3-dot -> Battery usage). We can check if overlay is applied or not using below commands in Termux su -c "lsof | grep treble-overlay-realme-c12" it will output some lines if successfully applied.
Click to expand...
Click to collapse
Wow was searching for this for like past 2-3 days, Thanks, man.
Can I use it on RMX2185?
and How to do it.
RoyTheBoy83 said:
Wow was searching for this for like past 2-3 days, Thanks, man.
Can I use it on RMX2185?
and How to do it.
Click to expand...
Click to collapse
for now the overlay that I made will only work on C12 RMX2189. I will check once there is some time
HemanthJabalpuri said:
egis/et512 Fingerprint fix
* First check if you have egis/et512 fingerprint by using Device Info HW app and see 'General' => 'Fingerprint'. If you have egis/et512 then follow below
* This needs to have rooted with Magisk
* Flash below attached module in Magisk app to fix fingerprint
This module is only for Realme UI 1.0 Android 10 vendor with Android 11/12 custom ROM/GSI
Credits
- titidlancip
- dodyirawan85
Click to expand...
Click to collapse
FIx for both relame ui 1 and 2