Related
Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool
Update
Resize Apps Partition
WARNING! This can BRICK your phone if done incorrectly.
PLEASE FOLLOW ALL STEPS CORRECTLY.
Please make a backup of all your important stuff.
Make a backup in the recovery.Make 100% sure the backup completes without any errors
Reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select Backup and Restore
2.Select Backup and Confirm(Proceed)
Once the backup is complete,the backup is located in "clockworkmod" folder on SD Card
You have to factory reset device,so be prepared to reinstall apps/games (You are going to lose data)
If you are fine with all of the above,The following mod increases the App Partition size from 1GB to 2GB.It rewrites the Internal Storage to 513MB(Used for videos/pictures,which is fine since we use our Micro SD cards for that)
If you are happy with all of the above,you can proceed with the next step :
Firstly,Download all files required and copy to SD Card
2 GB for apps_Jellybean_4.zip (232.63 KB)
Mega Link - http://goo.gl/ao3NFO
or
Media Fire Link - http://goo.gl/3j9RWm
AND
MTK_Nvram_Tool.zip (2.9MB)
Mega Link - http://goo.gl/Z2Chpx
or
Media Fire Link - http://goo.gl/sjah8X
Once on SD Card,reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select "Install Zip"
2.Select "Choose zip Sdcard"
3.Choose "MTK_Nvram_Tool.zip"
4.Select "Yes - Install MTK_Nvram_Tool.zip"
5.Click Next
6.Select "I Agree with this Terms and Conditions" and click Next
7.Click Next again
9.Choose 'Nvram Backup"
Once its done it should say "Backup Completed"
Under that it should say "Nvram Backup Successfully Completed"
It give the location for that backup,always keep that file (Copy to the PC Later)
10.Click OK
11.Click Exit
12.Click Yes
Now you are back at the install update from zip file screen.
13.Select "Install Zip"
14.Select "Choose zip Sdcard"
15.Choose "2 GB for apps_Jellybean_4.zip"
16.Select "Yes - Install 2 GB for apps_Jellybean_4.zip"
17.Go back to main menu
18.Choose Wipe menu
19.Choose Wipe Data (Factory Reset) -THIS WILL ERASE YOUR DATA
20.Wipe Cache
21.Wipe Dalvik Cache
22.Go back to main menu and reboot phone
The phone should reboot.If you get a message saying you have to format phone storage,click yes to format.
Go to Settings,Storage and See Total space is now 1.97GB
If the phone wont boot,power down,then hold up key and turn on to get into recovery mode.
1.Select Backup and Restore
2.Select Restore and Confirm(Proceed)
Restore the backup you made earlier.
This should let the system load when you reboot again,even if it asks you to format the phone again.
Copy NVRAM Backup to PC for safe keeping.
If you want to return to original/stock
Follow the same procedure as above but use the following file instead of the 2GB File
Stock Partition_Jellybean_4.zip (232.63KB)
Mega Link - http://goo.gl/pMn0ea
or
Media Fire - http://goo.gl/KJfRF7
Credits to :
AnoopKumar - MTK Nvram Tool
Andalitez said:
Hi Guys
Just an update.I downloaded the update from the website again,used winRAR and replaced the modem file in the system.
Everything works great now
Click to expand...
Click to collapse
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too
Replied
BlaqueDroid said:
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too
Click to expand...
Click to collapse
Hey man.
Sent you a PM.Currently working on a rom,will only be able to upload it for you in afew hours
ZTE
ztedevices.com/search.html?keyword=blade l2 look on there for the firmware for your device , push via adb sideloading and you should be set
noob problem...
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...
No Sim Detected
eochi18jhae said:
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...
Click to expand...
Click to collapse
Okay,you have to download the firmware version for your country,and have custom recovery installed on the phone.
So if you in UK,download the rom for your phone from UK provider.(doesnt matter if its JB or KK)
http://www.ztedevices.com/support/index.html
Once you have the rom,Use winRAR to do the following:
1.open the rom from your country in winrar so you can see the contents.
2.Open system folder (dont extract,just navigate into the folders in winrar)
3.Open "etc" folder
4.Open Firmware folder
5.Select "modem_1_wg_n.img" and extract it(i just drag and drop on desktop)
6.Open the Kitkat firmware you've downloaded using winRAR
7.Open System folder
8.Open "etc" folder
9.Open Firmware folder
10. Copy the "modem_1_wg_n.img" into that location(drag and drop from desktop)
11.winRAR asks if you want to :Add/Replace file/s? Select Yes or OK to allow it to
12.copy entire firmware to phone and reflash it on the phone from the SD card
I dont know if you can just replace the modem file after having loaded the firmware.I didnt try or test it.it may or may not work.
I am working on Custom Firmware for this phone though.
latest achievement was i managed to get the phone to see the SD card as phone storage thanks to various xda guides.this will be built in
FIrmware should be ready in a few days after testing.if anybody is interested in trying it out,let me know
problem solved...
Thank you sir...problem solved...it's really hard to be a noob...have to understand a lot of things now....I'm willing to try your firmware on my phone...upload it when done...keep up the good work...sorry for my english...
Post has been updated
I need to talk to you.... Go read my PM
installation is always aborted.. PLEASE HELP
Replied
Thanks
The thread is so useful... Keep up the good work, I don't have patience to try the new ROM!
Is there any chance for kernel supporting overclocking and undervoltage, also with more Gvernor and I/O Sheduler options?
Also Would be gorgeous if there's tap screen to wake option, this would need custom kernel too...
I'm now using DeviRSilva's kernel, which is doing great! Man, don't be afraid to relese it and continue tweaks
Still I'm a noob and maybe half of theese wishes are impossible, but would be so cool if they're possible to develop!
PD: I saw a site promoting Lollipop ROM for our L2 is that real?
PD2: Sorry for my awful English and probably stupid requests and questions...
helpppp
I have probelm, phone do not show sim card, on official site there is no serbia rom please how to fix it?
Andalitez said:
Replied
Click to expand...
Click to collapse
It fails to flash the ROM with the updated radio file. Just stops at Can't open... file.zip '(bad)'. Installation aborted.
How to fix?
Hi how do i unroot the zte blade l2?
And how to I remove costum recovery and reinstall stock recovery and stock rom?
Thanks just asking in case of sending it back for repairing.
Just noticed that the download link has been remoded.
Can someone provide a link for this rom?
Thanks.
Does this ROM have Greek language installed ???
no links are working
I need a copy of carliv recovery and backup of stock recovery as u think although my mobile mainly working I think the recovery is corrupt and has screwed my sound thanks in advance as I am taking a giant leap and biting bullet to try this recovery hope it can flash the legit kit kat if ever released by zte or virgin UK thanks
Andalitez said:
Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool
Click to expand...
Click to collapse
any news on the kitkat rom yet? super excited to try this out!
is the link for the rom gone?
i dont see it
Only valid for Moto G 2014!
Hello, forum mates. I have spent few days with this great device, I gave it meanwhile to my sister as present.
ATM, there are barely any custom ROMs, so I will list here few good things to do right after unlocking its bootloader and obtaining root access :angel:
So here you can read my little checklist and do whatever you prefer:
DISCLAIMER:
Code:
[I]your warranty is now void. All you do
with your phone is on your own risk!
Partitions info is valid for XT1068
international GSM dual-SIM only! Workflow
is tested only on KitKat factory image![/I]
Click to expand...
Click to collapse
Unlocking Bootloader: Motorola's website
Removing startup screen with warning of unlocked bootloader: flash attached zip in custom recovery
(I can confirm that the attached zip works, it will restore the white original Motorola splash screen)
1. Boot custom recovery without flashing it:
Copy and paste custom recovery (file format: img) into your SDK/platform-tools folder, I recommend here TWRP_2.8.0.1_Titan_v2 that I have successfully tested myself. Until this point the latest Motorola USB driver must be installed on your Windows PC, USB debugging (under "developer options") on your phone must be enabled. However, I generally recommend using Linux instead of Windows. You can check in my short guide for Ubuntu users how to install fastboot and ADB in Ubuntu. I have no clue about Mac iOS, sorry.
Here we go:
Navigate in CMD line into the directory where your adb.exe is saved. Example on my PC, it is in the folder "AndroidSDK", and there in the folder "platform-tools". So my commands would be:
Typing on keyboard Win+R
Enter cmd
the command line appears after that
Code:
cd c:\androidsdk\sdk\platform-tools
Now I'm in my desired folder. The next command is checking the USB driver / ADB connection:
Connect the phone to with your PC via USB cable and enter in cmd:
Code:
adb devices
Correct response:
HTML:
xxx(serial No)xxx device
If you don't see serial No of your Moto G, check if USB debugging is enabled. If serial No is there but "offline" instead of "device" appears, you will only have to confirm the promt on your phone's screen to allow USB debugging. If nothing appears, try to update your USB driver (don't go any further without working ADB connection!)
Now we will boot into bootloader mode and check there if fastboot connection is also working:
Code:
fastboot devices
Correct response:
HTML:
xxx(serial No)xxx fastboot
If the response looks like that, we can now boot into the custom recovery without flashing it onto device. The recovery.img will be booted directly from "platform-tools" folder, while stock recovery still remains installed on the phone. My recovery.img file's name is for example "TWRP-Titan", so after I've previously saved it in my "platform-tools" I will now enter in cmd:
Code:
fastboot boot TWRP-Titan.img
The phone will boot into the beautiful touch-recovery TWRP. Blue screen is there? Yesssss!! :good:
Now we can start with backups of our still 100% stock firmware in the next chapture.
Click to expand...
Click to collapse
2. Backup your stock firmware:
While still in the TWRP, simply create backup of all your partitions. It is strongly recommended to save backup on the external SD card, as many modifications or next unlocking of the bootloader (if relocked) will every time blow all your data from the internal memory.
Now still in TWRP, install SuperSU.zip
Reboot into the system
Now we will backup stock recovery, that we can later flash at any point back:
Code:
adb shell (enter)
su (enter)
Look at this point on the screen of your phone, SuperSU will promt you to allow SU access for shell, You should confirm that.
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
It will save the "recovery.img" file in your /sdcard folder on your phone's internal memory. It is strongly recommended to create the new folder on your external SD card where you can move all backup img files. To move the files, use any root file browser like for example Root Browser. When you open Root Browser for the first time, it will prompt oyu to install few utilities (busybox, unrar etc) which you should allow.
At this point, your entire stock firmware has been saved as backup.
Click to expand...
Click to collapse
3. Backup all partitions of your factory image / firmware:
Just the same way as you have previously created backup of your "recovery.img" you can
create "img" backup files of all your partitions. Check the attached screenshots and simply replace in the adb shell command the number of the mmcblk0p block No with the one you desire to backup and change "recovery" to the proper partition names, just like in the screenshots:
Click to expand...
Click to collapse
4. Restore to 100% stock firmware:
To return to 100% stock, you simply need to flash (or only boot) again TWRP 2.8.0.1, to restore your nandroid backup of your stock firmware and -if custom recovery was flashed- to flash in bootloader mode your stock recovery back. Paste your (stock) "recovery.img" file into "platform-tools" folder and execute in bootloader mode:
Code:
fastboot flash recovery recovery.img
After that simply restore your TWRP backup of stock and flash in bootloader mode your stock recovery back. To unroot permanently, open SuperSU app and choose the option "Full unroot" under "settings".
To relock the bootloader again: reboot to bootloader mode and execute in cmd:
Code:
fastboot oem lock
Your Moto G should be now again 100% stock.
Click to expand...
Click to collapse
If you benefit from this guide, show me your love and please hit "THANKS" button.
Credits also to all guys who have created linked guides (please hit there "thanks" also)
EASY MODS (Moto G 2014 stock firmware)
I am myself very big fan of SlimRoms (I was AlphaBeta SlimKat tester on few devices), so I was desperately missing the "Real Dark Slim" mode (and several other mods) on the Moto G 2014 factory image 4.4.4
I had to darken my Moto G 2014, so here I share now quite easy way how to get dark UI on many apps:
Click to expand...
Click to collapse
DARK UI APPS:
On the attached screenshots is an example of the "normal" Play Store (light UI) YouTube app vs the modified, dark UI YouTube app.
Luckily, the Team BlackOut consisting out of some great developers and contributors has darkened out whole bunch of apps. Please visit their website or please visit their thread where you can get more info and download directly the app TBO updater (ver.5.0.0 is up to date ATM, it is a lot better than the v.3 which was suffering of regular FCs on many devices).
With the TBO app you will find also boot animations, wallpapers etc and info how to install, the most important to avoid data loss and crying is: don't forget to create nandroid backup before modifying!
List of modified apps by the TBO available in dark UI (choice, uncomplete list):
Apollo music
Calendar
Chromecast
Drive
DropBox
Ebay
ES File Explorer
Facebook
Google now
Google+
Gmail
Hangouts
Instagram
Keep
MMS (AOSP)
Netflix
PayPal
PlayStore
WhatsApp
Skype
Spotify
Translate
Twitter
YouTube
etc.
Small tipps for the flawless un/installation of the system apps:
Regarding the fact that issues could occur when replacing the system apps (probably caused by smaller scripts which might remain as "corpses" after removing the apps) here is quite reliable way to go:
gain root access (flash SuperSU zip in custom recovery)
backup all apps that should be replaced with the darkened ones (recommended: Titanium Backup to create backup, or SD Maid to create *apk file)
now uninstall the respective apps (also with TB or SD Maid)
Open Play Store, install again and uninstall respective apps (that will remove reliably all rests)
Install the darkened apps (apk files or flashable zips that you have downloaded with TBO Updater)
Enjoy dark apps!
TROUBLESHOOTING: If anything goes wrong (bootloop, dark app FCs etc) delete darkened app and restore your app backup. I have never faced bootloop, but some apps simply might not work and will FC. Even if somebody would face bootloop, restoring the nandroid backup will revert all changes.
For normally installed apps (non-system apps): simply uninstall them through Play Store and install darkened ones instead. If TBO apps don't work, uninstall them and install again from the Play Store normal versions.
Click to expand...
Click to collapse
All credits here go to @djdarkknight96, @B_Boytm, @Gunthermic, @dafoxs, @train, @darkknight and our beloved SlimGapps maintainer, @dankoman :highfive:
Sorry, if I forgot to mention someone- remind me please!
(please if you use their modified apps, don't forget to find some posts of those guys here on forum and hit several times "thanks" button!)
Xposed frameworks
Add hunderds of mods, change functions of your hardware buttons, add double-tap-to-sleep, make your phone to fly etc, endless mods possibilities with Xposed frameworks (main thread)
Little guide for people who never used Xposed frameworks before:
download Xposed installer apk (v. 2.7 experimental is my recommendation for 4.3 and newer firmwares)
download also Xposed-Disabler-Recovery.zip from the main thread (if anything goes wrong)
create nandroid backup!
install Xposed installer app
open the app and Install/Update framework
reboot
if anything goes wrong, you end up with bootloop or so, reboot recovery and flash Xposed-Disabler-Recovery.zip (if even that doesn't help, restore nandroid backup)
if the phone reboots fine (it should) download modules you desire to use and install them
reboot
enjoy your new, customized firmware
If you find this post useful, please hit "THANKS" and honour my time spent to share this with you. Please also hit thanks to all devs and contributors whose work brought you benefits.
Click to expand...
Click to collapse
Hope to see soon more tweaks from you
Gerriitw said:
Hope to see soon more tweaks from you
Click to expand...
Click to collapse
I will post in the second post few more ideas with smaller mods on the stock firmware like using dark UI apps, some useful little frameworks modules, debloating etc.
This thread is actually not so interesting for experienced users, it's all quite common stuff.
tetakpatalked from Nexus 7 flo
Very helpful for newbies....U have done great job...hope to see more...
Second post updated (mods of stock 4.4.4 firmware)
UPDATE - Pixel Experience Official is out for Kenzo. Link attached below. Ongoing support for GSI users though.
https://forum.xda-developers.com/redmi-note-3/development/rom-pixel-experience-t3835648
-------------------------------------------
Disclaimer: I'm not responsible for bricked devices, flash at your own risk. I might be able to help with restoring your device though.
This is a guide to installing Android GSI on Redmi Note 3 (Kenzo)
---------------------------------------------------
What works-
RIL
GPS
Camera
Pretty much everything
What doesn't work-
Bluetooth
Hotspot
VoLTE(I couldn't test)
(NOTE - Bugs vary GSI to GSI)
---------------------------------------------------
Required files -
Grab these files first, and keep them on your SD card
TWRP Treble - https://androidfilehost.com/?fid=5862345805528059847
Android GSI(USE ARM64 A-ONLY) - for this tutorial, I'm using Phhusson's AOSP Pie GSI found here - https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
List of GSI's - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Pie GApps (If using Pie GSI) - https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141
Vendor Image - https://androidfilehost.com/?fid=1322778262903993757
Permissive SELinux Enabler - https://drive.google.com/file/d/1KFdPH2JGtvkXwt2emxPb-k7zdv2pLd-F/view?usp=drivesdk
Magisk 16.7 (minimum 16.7, you can use 17 as well)- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Latest Firmware - https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361/page176
Optional - Digital Well-being (ONLY FOR PIE)
Digital Well-being apk (Download latest version) - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
Digital Well-being Magisk Module - https://drive.google.com/file/d/1AAFMWbAAK-febiP9h4iZMJONEHXopmEU/view?usp=drivesdk
--------------------------------------------
Assuming you have an unlocked bootloader, and know your way in and around Android, let's begin!
How to install -
1. First, flash the Treble enabled TWRP.
2. Reboot to recovery.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file and immediately flash the Permissive SELinux Enabler.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
8. Reboot to System.
9. Reboot to recovery.
10. Perform a factory data reset, and flash GApps
11. Reboot to System, and complete setup.
12. After completing setup, reboot to recovery and flash Magisk 16.7
13. Reboot to System
14 Reboot to recovery and flash firmware.
15. Profit!
If you want Digital Well-being (ONLY FOR PIE) -
16. Install Digital Well-being apk
17. Flash Digital Well-being Magisk Module through Magisk Manager
18. Reboot
19. Profit!
-------------------------------------------------------
Tested on Snapdragon version, don't know if it works on MTK.
Screenshots are attached.
Fixes -
If you have the QS toggles moving out of the header like the screenshot attached in #1, do the following steps
1. Enable Developer Settings,
2. Find Smallest Width setting
3. Increase the value by 20. (If it's 360, make it 380)
4. Profit!
------------------------------------------
Google Camera + Face Unlock fix.
If Google Camera/Face Unlock doesn't work for you, do the following -
1. Reboot to recovery
2. Mount system
3. Flash the zip file (download link below)
4. Clear cache
5. Reboot to system
This should make Face Unlock work again, and GCam work as well.
Download patch - https://drive.google.com/file/d/17OUBxhsfeK0625_pYe8aRNr5L6doKdAK/view?usp=drivesdk
------------------------------------------
Can't find Smart Lock in settings?
1. Go to Settings < Security and Location.
2. Scroll down and click Advanced.
3. Click Trust Agents.
4. Switch on Trust Agent for Smart Lock.
You should now have Smart Lock option below Fingerprint.
-------------------++++++++++++++++-----------------------
For Changing accent colours -
Download this file - https://t.me/kenzousersglobal/1169
1. Flash it in recovery
2. Reboot to system
3. Go to Settings - Display - Advanced. Scroll down to find "Colour Theme"
4. Select colour theme and select colour of your choice.
5. Profit!
---------------------------------
Custom kernels that currently work
Radon - https://drive.google.com/file/d/1LYggpHDVph1fvWctIKY4FqQwtRb6Svh0/view
---------------------------------
Review - after extensive testing, I found this to be daily driver material, with the only exception being Bluetooth, Hotspot, and VoLTE(I couldn't test it myself)
Special thanks to - @corkiejp
Is it possible to get an Overlay Patch for Mi 8?
NielsvdS said:
Is it possible to get an Overlay Patch for Mi 8?
Click to expand...
Click to collapse
I honestly have no clue. I have only gathered all the patches and files for Kenzo and made them into one guide.
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Work on kate devices?
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
sharan565 said:
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
Click to expand...
Click to collapse
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
corkiejp said:
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
Click to expand...
Click to collapse
Thanks man I will try
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
Click to expand...
Click to collapse
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
wxtester said:
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
Click to expand...
Click to collapse
1. You just need to make sure that all partitions are mounted.
2. You can restore the backup through Treble TWRP.
Happy flashing!
Hexvessel1992 said:
Work on kate devices?
Click to expand...
Click to collapse
I don't know, I need someone to test it. It should work, since the Vendor for Kenzo and Kate are the same.
corkiejp said:
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Click to expand...
Click to collapse
I'll update the thread with the right link
I think it is possible to dirty flash Open Gapps, but it might give bugs, always go for a clean flash
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
srishant said:
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
Click to expand...
Click to collapse
I had to forage through 4 complex guides, scourge through XDA and Telegram for all the patches, and hence could make such a simple guide. Apparently, devs on the Telegram channel are working on the Bluetooth and VoLTE fix I'll update once that happens!
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
amog787 said:
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
Click to expand...
Click to collapse
I did see that, but when I flashed it, it messed upy system and I had to reinstall the GSI. I don't know how to modify it for Treble, could you do it? I'm happy to test. I believe that fix is for Flashavle ZIPs, not for Treble GSIs.
Possible Gcam and stock working patch!
Posted this in AOSP Pie Rom thread, may also work for the GSI?
corkiejp said:
I found Gcam Pie Fix for another device in this thread.
Link to Gcam Pie Fix: - https://drive.google.com/file/d/1D5qvlA-QbQu6xoWpsLPyWquMkS3hxXi3/view
Gcam that I'm using: - https://androidfilehost.com/?fid=673956719939833577
^^^ From this thread, maybe newer versions available.
I was able to setup face unlock after flashing the above fix, you may also need to enable Smart Lock (Google) as a trusted agent.
It is buggy and the face option may not always trigger, plus you need to hold the phone far from you and swipe when the lock symbol appears (no fast unlock options xposed).
Another benefit of flashing another Camera (V 2.0.002) Started working as well. (Don't know if that is the default AOSP camera or something I restored from backup? Could be Snap Camera from LOS).
Click to expand...
Click to collapse
corkiejp said:
Posted this in AOSP Pie Rom thread, may also work for the GSI?
Click to expand...
Click to collapse
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Sid127 said:
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Click to expand...
Click to collapse
Not that I'm aware of, but this just places/replaces some Lib and Lib64 in system partition.
If your worried about it, back up your system partition, flash the this patch and wipe caches.
If you experience problems, just restore your system partition.
It was reported working by someone else here.
Before following this guide, you'll want to grab the MSM unbricking tool, specifically for this device (not the global or other Oneplus 8 versions). Use it if you brick yourself.
Here's how I got microG to work on my Visible Oneplus 8 running Oxygen OS 11:
Unlock the boot loader and flash Lineage's instantnoodle recovery (The small recovery image ~96MB, not the large rom file)
Reboot into recovery and adb sideload the Magisk zip file, from the recovery's 'Apply Update'.
Follow this guide to enable signature spoofing, but with the following few changes:
Place this specialized hook services file ( 11-hook-services-OxygenOS.jar.dex ) in the same folder as 11-hook-services.jar.dex.
When you get to the `java -jar` command in the guide, do this instead:
Code:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services-OxygenOS.jar.dex 11core-services.jar.dex
Do not install the microG provided in the guide! But go ahead and install your `spoof_AVDapi30.zip` through magisk as the guide says.
Confirm that signature spoofing is working (you can download Signature Spoofing Checker from F-droid)
Inside the magisk app, search for and install the plugin "microG installer Revived". Reboot.
Grant microG all the permisisons that you can in microG settings' Self-Check.
Tap and install GmsCore.apk located at '/system/priv-app/GmsCore/". You need to do this step even though its already installed because until you do this, it will only be installed as a system app. Doing this installs it as a user app, which fixes the location permission issue (somehow this issue is encountered). If it doesn't fix it right away you may need to reboot.
Open the microG settings again, and give yourself the location settings (and SMS if still needed)
I hope this helps someone. I know I had a lot of frustration because so much that works for other instantnoodles simply doesn't work on this device. Instantnoodle custom roms like lineageOS (as of writing this) and automated patchers like smali and nanodroid don't work, so at least we have this one option.
Ciao @Calebdvn
Trying to apply this fix on OP6 OOS11.1.2.2 but nothing happends
trying the standard method I were stuck at bootlogo, using this file the system volta, but, signature spoofing Is not working
Caould you kindly support me ?
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI
mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.
Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...
Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release
tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.
yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp
I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)
I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.