Database Users

Redmi 2 Prime "no network" after update to 8.5.1.0

Greetings to all.
I have a Redmi 2 Prime, I'm in Spain and I'm using Vodafone 4G network. Everything was working fine, but I couldn't use the Netflix app, so I had to update.
I used the Updater (that's the OTA update I think). It didn't install, so I downloaded the "fastboot" rom and installed it. After the install, the phone booted and it asked me for the PIN of the SIM card, then the configuration process started as if it was new (I chose clean install). The problem is that it doesn't connect to the Vodafone network.
I read similar problems in the past, so I though that going back to an older ROM will solve the problem, even if I couldn't use the Netflix app. So, I installed an old ROM V7.5.2.0.LHJMIDE. No luck neither.
Can you tell me how to solve this issue? What ROM should I install, even if it's and old one?
Thanks in advance.

Flash miui zip again try and send review

Exact model is: 2014813 TD-LTE
I've been trying for days now. I've got it running again but on an english ROM and my wife can't understand english. I can't find a Global ROM to install from fastboot, since OTA ROMs won't install. Need spanish language.
I had to change the modem file on the fastboot image. What a joke this Xiaomi updates...

****rumbo said:
Exact model is: 2014813 TD-LTE
I've been trying for days now. I've got it running again but on an english ROM and my wife can't understand english. I can't find a Global ROM to install from fastboot, since OTA ROMs won't install. Need spanish language.
I had to change the modem file on the fastboot image. What a joke this Xiaomi updates...
Click to expand...
Click to collapse
Yes, that device is china model. You cant install rom global version. Try flash 8.5.1.0 china rom.

Thanks for the comment.
Why would I install a chinese ROM if I won't understand anything?
I already solved the problem downloading a ROM from the Xiaomi.eu site and changing the modem file.
Such a crappy way to update a phone. 2 days (+10 hours) investigating and working on the phone to update it.

suggestion:
1)Backup all partitions via TWRP, in case anything goes wrong.
2)Go to page http://en.miui.com/a-234.html , download "☆ Redmi 2 Prime Latest Global Stable Version Fastboot File Download"
3)Go to page http://en.miui.com/download-261.html#441 , download full rom (stable rom, Redmi 2 Prime Global)
4)Go to page http://en.miui.com/download-261.html#442 , download full rom (stable rom, Redmi 2 Prime China)
5)"Extract files..." via 7zip the file downloaded in step 2. You'll get a folder named "wt88047_pro_global_images_V8.1.3.0.LHJMIDI_20161230.0000.00_5.1_global_23ac47dab8". Shorten the folder name. Inside the folder is another file "wt88047_pro_global_images_V8.1.3.0.LHJMIDI_20161230.0000.00_5.1_global_23ac47dab8.tar". "Extract files..." via 7zip this file. Shorten the folder name. Inside the folder is another folder named "wt88047_pro_global_images_V8.1.3.0.LHJMIDI_20161230.0000.00_5.1_global". Shorten the folder name. Inside this folder is your workplace. Copy your adb and fastboot files and folders here.
6). Copy the file downloaded in step 3 ("miui_HM2XWCProGlobal_V8.5.1.0.LHJMIED_447abeac98_5.1.zip") to your phone's external memory.
7) Extract the file downloaded in step 4 and go inside the folder named "firmware-update". Copy the file named "NON-HLOS.bin" into your workplace(remember?step5).
8)Get ready for the flashing job. Charge you battery. Ensure you have backed up all personal files from your internal storage. Ensure you have your apps data like Whatsapp media backed up. Take a cloud backup. Now get into your workplace, Shift+right-click and select "open command window here". Connect your phone in fastboot mode to the PC. type "flash_all"(without quotes) in the command prompt and press Enter. Let the job proceed. Lastly your phone will reboot. It'll take some time until setup screen is shown. Don't bother. Just skip all details and go to home screen. Go to updater and select updater package in your external memory(remember?step6). Your phone will go into recovery mode to apply the update and it'll reboot. Again wait a few minutes for setup screen to appear. Don't proceed. Switch off.
7)Swith on into fastboot mode. Open command window inside your workplace. Ensure your phone is connected to your PC. Type "fastboot flash modem NON-HLOS.bin" (without quotes). After the flashing has been done, type "fastboot reboot". That's it.
8) Any future updates as a zip file will replace the modem. You can only flash in fastboot mode (after replacing modem file). It is a difficult process to unpack a zip, change it and repack with proper signing and/or checksum so that the stock recovery accepts it.
9) I don't know whether other firmware files also need replacing, but I don't think so.

And FYI, Chinese ROMs also have English language, what they don't have is gapps, and opengapps cannot be installed.

[TWRP] [ROMS] OpenWatch Project [Kingwear, Zeblaze, Lemfo, Diggro, Finow, Microwear]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
OpenWatch OS:
Project OpenWatch is the initiative undertaken by BLOCKS, who came into the limelight for their modular smartwatch. The goal of this is to make an AOSP based fully open source OS (OpenWatch OS) so any smartwatch that can have AOSP builds or be ported to AOSP can have a fully functional Watch OS. We are already working to convert 3 prominent traditional roms to be compatible with smartwatches and their smaller screens.
We also want to give as many smartwatches as possible a central location to get TWRP and information on their devices so instead of having to look everywhere on the internet for information its all under one umbrella.
Tools Required:
Standard MTK drivers installer
https://goo.gl/PraJuZ
SPFlash Tool
https://spflashtool.com/
Harmony
List of confirmed working devices:
Kingwear KW68, KW88, KW88 Pro, KW98, KW99, KW99 Pro
Blocks Watch
Look Watch
Zeblaze Thor, Thor S
IQ I2
Diggro DI01
AllCall W1, W2
TWRP Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
InHarmony
List of confirmed working devices:
Diggro DI06
Older Diggro DI07
Lemfo LES1
TWRP Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
AntiHarmony
List of confirmed working devices:
Newer Microwear H2
TWRP Download: Here
TWRP Image Installer Download: Here
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt kernel (For now)
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open spflash tool
4. In the "Scatter-loading File" box choose the "MT6580M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Plug your watch in and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Infinity
List of confirmed working devices:
Lemfo Lem7
Zeblaze Thor 4
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open the "SP_Flash_Tool_v5.1824_Win" folder and run "flash_tool.exe".
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Unity
List of confirmed working devices:
Kingwear KW06
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open spflash tool
4. In the "Scatter-loading File" box choose the "MT6580M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Plug your watch in and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Continuum
List of confirmed working devices:
Lemfo Lem5 Pro
Finow X5 Air
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Expanse
List of confirmed working devices:
Zeblaze Thor Pro
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Wisp
List of confirmed working devices:
* X02S MT6580
* X01S Plus MT6580
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
S99
List of confirmed working devices:
Zgpax S99
TWRP Download: Here
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp

Watch Bringup:
We are actively working on bringing up the following devices on aosp roms:
Harmony, InHarmony, antiharmony, s99, unity: Android 8.1
Infinity: Android 7.0
If anyone has a watch that would like to get a source built twrp on it please look at the contact us section. It must run full android aka not a mt2xxx
Timeline:
We don't have a timeline that is set in stone because this is all volunteer work but you can take a look at our current to-do/in-progress/done board here
The Team:
Carbon Rom:
@Myself5, @frap129
LineageOS:
@Alberto96, @jrior001, @forkbomb444 @deadman96385
Dirty Unicorns:
@jbats, @danjull
Independent devs:
@corvus, @CaptivateKing @iscle
Contact us:
We have a telegram support group for issues or if you would like to get your watch supported here
You can also PM here on xda if you don't/can't join the telegram

WWWWWWWWWWWWWOOOOOOOOOOOOOOOOOWWWWWWWWWWWWWWWW..! TWRP for watch..! Now that's coooooooool..!

This project looks really promising!
I wish I owned one of these watches, so If could play around with this.

Damm i was hoping for IQI I4 Pro support. Will it be in near future. :good:

Inverted version for DIGGRO DI06 (and others that feature an inverted touchpanel): https://www.androidfilehost.com/?fid=5862345805528050107
Device Tree containing all required changes: https://github.com/GearLabs/twrp_device_mediatek_inharmony

Is it worth while mentioning here that I managed to port an older version of TWRP to the Finow X5 AIR / LEMFO LEM5 Pro a few weeks ago? It's the 2Gb RAM version of the watch. It's over at RASC if anyone wants to have a look. CF

deadman96385 said:
Mine just in case
Click to expand...
Click to collapse
Well done I am very excited to see custom roms for android wear devices in the future hopefully with extra customization like what is present in feature rich roms like Ressurection remix and Aosp Extended.

Finnaly its live for the community
Awesome, cheers

Tutorial
Could someone explain step by step what to do for dummies like me ?

This project spawned out of an idea I had while working at blocks that we should open source some of the work we are doing so the community could benefit from it. Releasing twrp for these devices is just the first step, the primary goal of Openwatch is to get aosp roms on these watches that have been optimized for the smaller screen to replace the normally crappy stock os's. I will admit that there was twrps for a lot of these watches scattered around xda/roundandroidwatches but trying to find them was not an easy task and none of them provided source code to recompile the twrp. So we decided to make this project to put them all under one umbrella. On the note of the 2 different screen types this is the first time we are seeing it all the devices we have tested on so far work fine so if we can get a tester for the other variant we would be more then willing to make a version that supports it. We chose xda rather than round android watch because we all have more experience with it and it's historically been the centre of android development for most devices. We would be more than willing to work with you/others that are on roundandroidwatch just let us know our dev team is primarily rom devs from various rom teams, but also a few app devs. I think our work is coming off as a surprise because its one of the first times full android watches have gotten a lot of attention from xda/press. So people are excited about it especially with source built customs roms being a reality in the near future which was never really a thing in the past.

Is it expected to support a smartwatch with Snapdragon in the future?

deadman96385 said:
This project spawned out of an idea I had while working at blocks that we should open source some of the work we are doing so the community could benefit from it. Releasing twrp for these devices is just the first step, the primary goal of Openwatch is to get aosp roms on these watches that have been optimized for the smaller screen to replace the normally crappy stock os's. I will admit that there was twrps for a lot of these watches scattered around xda/roundandroidwatches but trying to find them was not an easy task and none of them provided source code to recompile the twrp. So we decided to make this project to put them all under one umbrella. On the note of the 2 different screen types this is the first time we are seeing it all the devices we have tested on so far work fine so if we can get a tester for the other variant we would be more then willing to make a version that supports it. We chose xda rather than round android watch because we all have more experience with it and it's historically been the centre of android development for most devices. We would be more than willing to work with you/others that are on roundandroidwatch just let us know our dev team is primarily rom devs from various rom teams, but also a few app devs. I think our work is coming off as a surprise because its one of the first times full android watches have gotten a lot of attention from xda/press. So people are excited about it especially with source built customs roms being a reality in the near future which was never really a thing in the past.
Click to expand...
Click to collapse
Thanks for the PM and sorry for causing any issues with my earlier posts.
It was not my intention to be so reactive.
We all have the same goal so I am seeking a way for us to work together.
Again - apologies for the previous posts.
Cheers
Pablo

mega-samu said:
Is it expected to support a smartwatch with Snapdragon in the future?
Click to expand...
Click to collapse
The base support is there, any watch that can boot aosp roms can use the Openwatch code. So watches with snapdragon would need to be brought up like phones or any other device.

Status update
So since we launched we have gotten quite a bit of activity from various developers and because of that, we have added support for a number of new devices. We are focusing on getting the changes to the OS done so we can start releasing alpha builds to the community.
Infinity:
List of confirmed working devices:
Lemfo Lem7
Zeblaze Thor 4
Source built twrp is up and running
Preliminary source built aosp is up and running
Tested by @iscle
Unity:
List of confirmed working devices:
Kingwear KW06
Source built twrp is up and running
Source built aosp has not been started
Tested by Yours truly
Continuum:
List of confirmed working devices:
Lemfo Lem5 Pro
Finow X5 Air
Source built twrp is up and running
Ported aosp up and running, will now work on source built
Tested by @CerebralFlex
Preview video of the ported rom on Continuum:

I would just like to say thank you all for doing this. Got a zeblaze Thor pro begging for a custom ROM

sephiroth555999 said:
I would just like to say thank you all for doing this. Got a zeblaze Thor pro begging for a custom ROM
Click to expand...
Click to collapse
Could you join the telegram group in the 2nd post, so we can see about supporting the zeblaze thor pro?

I will believe that open watch OS will support Bluetooth calling feature and steady connection.
What about supporting IOS IPhone devices I believe too.
Great idea look forward, I will support you guys

First...what a fantastic idea. Thank you!
I have been chatting to one of the admin over on Telegram, as I own a Smartwear H2 with MTK6580, 1GB Ram and 16GB storage. Unfortunately the Harmony/Inharmony TWRP does boot on the H2 and is correct orientation on the screen (unlike the one over on roundwatches) but the touch screen is unresponsive. The admin over on telegram tried to extract defconfig from the kernel for support, but has not found it possible at the moment. I have therefore emailed Microwear to see if they will provide this information/file.
By the way...the H2 TWRP Recovery over on roundwatches, the touch screen does work...but for some reason the screen and touch is inverted. Screen is upside down, and x/y axis reversed, so to press a button displayed at the bottom of the screen you have to press the top of the screen.
I have emailed Microwear about this too...as it could be they have changed components through production.
Good luck with the project! hopefully I can join the fun.

Yep, you need a recovery for the hehui screens.
We only have the early screen type so it has changed and no longer works.
I will supply the group with the HEHUI stock boot and recovery images for the H2.
Cheers
Pablo.
Sent from my BLA-L29 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:28 PM ----------
Here are the files that you need
https://goo.gl/i74K6F
Sent from my BLA-L29 using Tapatalk

[Treble] Android GSI on Kenzo/Kate. [SnapDragon]

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.

[GUIDE] Enabling LTE on China Telecom on Pixel XL (Android 10), rooted & no flashing

[GUIDE] Enabling LTE on China Telecom on Pixel XL (Android 10), rooted & no flashing
After reading and trying some of things suggested, I found a way to enable China Telecom on my Pixel XL (US unlocked - purchased direct from Google). Big thanks to sbjbs for the template and TEEEEEEEEED for writing the prior guide, which can be found here, as long as with many others over the years that I have used to learn. As always, do your own research as well and back everything up on an external storage with a clean factory image for those acts of God and soft bricks that may come.
The biggest win for me over the old method is, I no longer have to flash my phone and lose all my data every few months when the crack failed and without a modem.img in Android 10, the prior guide wasn't step by step anymore.
Using the Android 10 December release (QP1A.191005.007.A3) downloaded late April 2020. Flashed clean keeping user data by flashall without -w flag.
On my phone, I have the following apps: TWRP (not sure if this made a difference but I have it), Magsik 20.4 (rooting), Total commander (file explorer capable of root access to the file system)
1) You will need the One Plus 3T rom image. (For those in China, the HK page does NOT have the 3T image, switch to the US version to find the 3T image)
2) Unzip the download, we need the following file: OnePlus3TOxygen.../firmware_update/NON-HLOS.bin
3) Using a Linux environment (Linux subsystem on Windows 10 will NOT work; I used a VM on Windows 10 using VMware to use Ubuntu to accomplish this) we need to mount NON-HLOS.bin using the following code where our file is located:
Code:
mkdir oneplus
sudo mount -o loop NO-HLOS.bin oneplus
4) We want to extract the following folder from the image: oneplus/image/modem_pr/mcfg/configs/mcfg_sw/generic/china/ct (oneplus is the mount point, the first folder inside to navigate through is image.)
5) Once extracted, we want to copy this folder onto the phone, since we can't access the root folders directly from a computer.
6) From the root, navigate to /firmware/radio/modem_pr/mcfg/configs/mcfg_sw/generic Here we need to create a new folder, china (all lower case)
7) In this new folder, we will copy and paste the ct folder (with all the folders and files within it).
8) From the root, navigate to /firmware/verinfo and open ver_info.txt. In this file, we will see a string of numbers. Increasing the number by one is enough to make it work. (not sure if this required but was a step in the old flashing guide for Android 9, I kept it and it worked.)
9) Reboot and enjoy China Telecom LTE!
I have rebooted my phone a few times and seen the LTE stick. Using the Pixel XL over the last 2 and half years has been a ride of emotions in China (DIY screen replacement, battery, back glass plate, rear facing camera, and various LTE patches over the years.) Hopefully this works for you. These guides work as long as we provide success stories along with problems.

That's so good :good::good::good:

[ROM] CrDroid from MI A3 working on CC9e

Hey guys !, I have testing the system.img of the CrDroid Rom from Mi A3 and it works great, everything works on our CC9e (I have been using it for some days and works very well)
You need an unlocked bootloader , a TWRP working on your device, you must be on xiaomi.eu miui 12 (in order to get android 10 vendor) and some files listed below:
1- Crdroid Rom from Mi A3
2- Payload dumper
3- Magisk 20.x
If you wanna test it follow the next steps:
A) Extract the payload dumper.zip you will get a payload imput folder, payload output folder and payload.exe file
B) Open the Crdroid rom. zip with 7zip or similar and copy the payload.bin file to payload_imput folder
C) Open the payload_dumper.exe file and wait until the window close automatically, then copy the system.img file from the payload_output folder to a otg device, internal memory or sd card
D) Enter to twrp format data, then go to wipe option, slide to wipe data and cache partition, then go to install option and flash the system.img file in the system partition (the file that you copy to device in the step C)
E) Once the system.img is installed, don't reboot , just go back to install option in twrp and install magisk 20 zip, once it is installed just reboot and enjoy crdroid rom
Credits from the MI A3 CrDroid ROM:
@Harukey - device sources
@oddlyspaced - recovery
@charliespencerchaplin
@prakaship78
@nullbytepl
@Baraach95
@lapotinval
@Golbinex
 @Rj saiful for the first testing of system image

Where is my credit
I had testing 1st this system.img from crdroid A3, I showed you on telegram group... And you wirte you did.... Give credit bro

fer15 said:
Hey guys !, I have testing the system.img of the CrDroid Rom from Mi A3 and it works great, everything works on our CC9e (I have been using it for some days and works very well)
You need an unlocked bootloader , a TWRP working on your device, you must be on xiaomi.eu miui 12 (in order to get android 10 vendor) and some files listed below:
1- Crdroid Rom from Mi A3
2- Payload dumper
3- Magisk 20.x
If you wanna test it follow the next steps:
A) Extract the payload dumper.zip you will get a payload imput folder, payload output folder and payload.exe file
B) Open the Crdroid rom. zip with 7zip or similar and copy the payload.bin file to payload_imput folder
C) Open the payload_dumper.exe file and wait until the window close automatically, then copy the system.img file from the payload_output folder to a otg device, internal memory or sd card
D) Enter to twrp format data, then go to wipe option, slide to wipe data and cache partition, then go to install option and flash the system.img file in the system partition (the file that you copy to device in the step C)
E) Once the system.img is installed, don't reboot , just go back to install option in twrp and install magisk 20 zip, once it is installed just reboot and enjoy crdroid rom
Credits from the MI A3 CrDroid ROM:
@Harukey - device sources
@oddlyspaced - recovery
@charliespencerchaplin
@prakaship78
@nullbytepl
@Baraach95
@lapotinval
@Golbinex
Click to expand...
Click to collapse
You are great.

Thanks you so much!!! I am so glad you give a credit

t Thanks! Thank you so much, I've been looking for a tutorial for a long time and finally found it! I finally successfully installed crdroid's Android 10 for cc9e just now! Is Android 11 also installed with a tutorial like yours?

Good news!!
The same way can install the crDroid 8.8, Android 12.
Everything works fine except the speaker

Nofated said:
View attachment 5704085
Good news!!
The same way can install the crDroid 8.8, Android 12.
Everything works fine except the speaker
Click to expand...
Click to collapse
what vendor do u use?

nkson20789 said:
what vendor do u use?
Click to expand...
Click to collapse
The Vendor from the MIUI 12.5 by xiaomi.eu, which is based on Andorid 10.
Seems that the way I installed the Crdroid can't load the driver correctly. I tried to install the Evolution x which is based on Android 13, the audio module still can't run correctly.
ps. I tried to flash the vendor.img from evolution x. The CC 9e can't load the system successfully. It stuck on the loading screen of evolution x, which appears after the Mi Logo.
I will try to install Evolution which is based on Andorid 10 soon. Hope everything will work well.

is there any error or bugs in this rom?

Nofated said:
The Vendor from the MIUI 12.5 by xiaomi.eu, which is based on Andorid 10.
Seems that the way I installed the Crdroid can't load the driver correctly. I tried to install the Evolution x which is based on Android 13, the audio module still can't run correctly.
ps. I tried to flash the vendor.img from evolution x. The CC 9e can't load the system successfully. It stuck on the loading screen of evolution x, which appears after the Mi Logo.
I will try to install Evolution which is based on Andorid 10 soon. Hope everything will work well.
Click to expand...
Click to collapse
Why I can't use my In-Screen Fingerprint or Always On Display but my speakers are work fine
I use the vendor from xiaomi.eu MIUI12.5.5

Nofated said:
The Vendor from the MIUI 12.5 by xiaomi.eu, which is based on Andorid 10.
Seems that the way I installed the Crdroid can't load the driver correctly. I tried to install the Evolution x which is based on Android 13, the audio module still can't run correctly.
ps. I tried to flash the vendor.img from evolution x. The CC 9e can't load the system successfully. It stuck on the loading screen of evolution x, which appears after the Mi Logo.
I will try to install Evolution which is based on Andorid 10 soon. Hope everything will work well.
Click to expand...
Click to collapse
I have an Evolution X rom based on Android 10,it works

RyanLin_ said:
Why I can't use my In-Screen Fingerprint or Always On Display but my speakers are work fine
I use the vendor from xiaomi.eu MIUI12.5.5
Click to expand...
Click to collapse
You sure? I have tested the latest version of Evolution X which is based on Android 13. My speaker and Fingerprint couldn't work.

RyanLin_ said:
I have an Evolution X rom based on Android 10,it works
Click to expand...
Click to collapse
Would you like to provide the forum or links of the rom?
I have tested the evo 4.6 and it couldn't boot. But the CrDroid Rom runs correctly.

Nofated said:
Would you like to provide the forum or links of the rom?
I have tested the evo 4.6 and it couldn't boot. But the CrDroid Rom runs correctly.
Click to expand...
Click to collapse
I have a link from the telegram group. micc9e

nkson20789 said:
I have a link from the telegram group. micc9e
Click to expand...
Click to collapse
I'd like to try the rom later.
And I will try to install the vendor from MIUI 13(Android 11) and retry the Evolution which was based on the Android 13.
I will stay on the A13 if the speaker works well.

So,do you need the link of evolution x right now?
Nofated said:
I'd like to try the rom later.
And I will try to install the vendor from MIUI 13(Android 11) and retry the Evolution which was based on the Android 13.
I will stay on the A13 if the speaker works well.
Click to expand...
Click to collapse