Database Info

Cubot King Kong custom ROM or Android go?

Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.

Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.

does anyone have a scatter file or custom recovery for this phone? how did you root?

CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip

aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms

Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s

What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img

i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied

Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16

Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result

LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?

Use an app from google play called Device Info HW

Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)

Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).

Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.

In gt1x its because of this:

So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.

And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.

aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance

please do a read back for boot.img and recovery.img with SP Flash Tool

[Guide] Root Pixel 4 XL Android 10 (Q)

Root Pixel 4 XL Android 10 (Q) Unlock/Lock Bootloader + Systemless ROOT
Android Security Buletin-August 2020
Pixel Update Bulletin—August 2020​
Introduction
This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 4 XL'.
This Guide also works for Pixel 4 owners: If, they download the Pixel 4 files.
NEW
Gpay not working? Try this.
Tulsadiver's ADB Magisk Module Mod Installer has a LINUX instaler.
The best instuctions on how to Pass SafetyNet, i've ever read.
Update(s)
Factory/OTA Images - 08/05
Magisk Stable - Magisk-22.0 02/23
Magisk Beta - Magisk-22.0 02/23
Magisk Canary - Magisk-22001
TWRP - twrp-3.5.0_10-1-coral.img/zip 01/02
SafetyNet - SafetyNetFix v1.1.1 01/16
SDK Platform-tools - r31.0.0 03/01
Custom Kernels
No Updated Kernels
Custom ROMs
Waiting
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 4 XL phone with an unlocked bootloader.
The latest Android 10 (Q) Factory or OTA Image: "coral" for Pixel 4 XL
Factory Image
10.0.0 (QQ3A.200805.001, Aug 2020)
OTA Image
10.0.0 (QQ3A.200805.001, Aug 2020)
Computer - With the latest SDK Platform-Tools: r31.0.0 installed.
Important: Update Platform Tools, regularly, for optimal performance.
Other Guides
[Guide] Root Pixel 4 XL Android 11 (R)
Credits/Thanks/Recognitions
@topjohnwu - Magisk Canary
Those I may have, inadvertently, forgotten.
Index
(NOTE: Numbers 1-13 are not steps, they are individual sets of instructions).
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: You will see this warning until, you relock the bootloader.
Return Phone to Stock
Important: Do not relock your bootloader until you have returned the device to Stock..
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader (Google Pixel 4 XL)
Return the phone to Stock before Locking the bootloader!
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep or wipe data
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4 XL - coral.
If your phone is rooted and you have Modules installed and you want to 'Keep Data', remove them before you install the Factory Image:
Why? Some Modules need to be updated before use with a new Factory/OTA image because (sometime) Google makes changes to Factory/OTA images that break the Modules.
How to remove Magisk: Open Magisk App ==> Tap Uninstall == Tap Restore Images.
If you get an error: when flashing the Factory image, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord to one that doesn't have the blue color head or use a USB C to C cable.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 4 XL - coral to your Computer.
Extract the factory Image to a folder.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e. Notepad. Remove -w from this command: fastboot -w update image-coral-aa9a.999999.999.zip
Note: If you do not remove the -w your data and internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-coral-....img
flash-all.bat
image-coral-....zip
radio-coral-....img
Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
System will reboot when flashing is complete.
Do #7 or #8 to root/reroot.
Wipe Data
Open the folder you extracted the Factory Image to and View the flash-all.bat file with a file editor i.e. Notepad. Verify the file has the -w in this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
Note: This will wipe your data and internal storage.
Copy/Move these files to the Platform-tools folder:
bootloader-coral-....img
flash-all.bat
image-coral-....zip
radio-coral-....img
Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
System will reboot when flashing is complete.
Do #7 or #8 to root/reroot.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery - TWRP
Important notes:
Charge your device.
Enable USB Debugging on your phone.
Install the latest version of SDK Platform-tools on your computer.
Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
Connect your device to your computer using a USB cable.
Boot T.W.R.P.
T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
When T.W.R.P boots tap Advanced ==> ADB Sideload.
✓ the wipe Dalvik cache box
Swipe to start
On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
You will see the progress of the sideloaded file.
When the file finishes sidloading, reboot your device.
Done!
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (coral-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image file' to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
Reboot
Install T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important Note(s):
Set Pin before installing TWRP: Settings > Security & location >Screen lock > Pin
Backup your data
Download files - The listed files are used with #7, and #8.
T.W.R.P
twrp-3.5.0_10-1-coral.img - Download to your computer
twrp-installer-3.5.0_10-1-coral.zip - Download to your phone
Magisk - Download to your phone
The latest Magisk Beta/Stable zip. - Download to your phone
The latest Magisk Canary - Download to your phone
Custom Kernels - Download to your phone
No Updated Custom Kernels
Kernel Manager - Download to your phone
EX Kernel Manager
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0_10-1-coral.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect the phone from computer.
If requested, swipe to allow modifications.
Tap Install select twrp-installer-3.5.0_10-1-coral.zip, Swipe Slider to install
Reboot Recovery
Root/Reroot
Note(s):
If you are rerooting, tap Install, select Magisk's uninstaller.zip, Swipe the slider to install.
Some Custom Kernels can be updated by flashing via Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
With Custom Kernel (Optional)
No Updated Custom Kernels
Without Custom Kernel
Tap Install, select Magisk-Beta/Canary/Stable zip.
Swipe Slider to Install
Reboot System
Install Modules (Optional)
Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Backup your data
Download files - See #7 - Skip the twrp-installer
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0_10-1-coral.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect the phone from computer.
If requested, swipe to allow modifications.
Root/Reroot
Note: If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, Swipe the slider to install.
With Custom Kernel (Optional)
No Updated Kernels
Without Custom Kernel
Tap Install, select Magisk-Beta/Canary/Stable zip.
Swipe Slider to Install
Reboot System
Install Modules (Optional)
Root/Reroot with Magisk and Pass SafetyNet.
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
To root use Magisk App Beta, Canary or Stable App to patch the Stock boot.img.
Download files:
Magisk App - Download to your phone
Magisk Beta/Stable App
Magisk Canary App
Custom kernels - Download to your phone - install with Kernel Manager
No updated Kernels
Kernel Manager - Download to your phone
EX Kernel Manager
Patching the boot.img
Do #6 - Extract boot.img
Install Magisk (Beta or Canary) App
Open Magisk App
Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img) and stored in the download folder.
The phone will reboot.
Copy the magisk_patched.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode (See #1B)
Connect the phone to the Computer with USB cord.
Open a Command Prompt (See #1A) in the folder you copied the magisk_patched.img to.
Type fastboot flash boot magisk_patched.img at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes: If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass SafetyNet: #12 Apps/Mods/Scripts/Tethering/Themes
OTA Installation - Keep Root -- No Computer Needed
OTA Installation
Set Magisk App Update Chanel/Update Magisk
Set Magisk App Update Chanel
Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Tap, Reboot
Done!
Custom ROMs for Pixel 4 XL
Need help with a Custom ROM?
Follow the Installation Instructions of the Developer of the Custom ROM you are trying to install.
If you have a problem Installing the ROM, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Custom ROMS
Alpha/Beta
Waiting...
Official
Waiting...
Unofficial
Waiting...
Apps/Mods/Scripts/Tethering/Themes
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
T.W.R.P. 3.5.0_10-1 Backup/Restore
https://forum.xda-developers.com/t/twrp-coral-official.4111017/post-82764097

Great write up...as always. Is there an way to update security patches and keep root?

State.of.mind said:
Great write up...as always. Is there an way to update security patches and keep root?
Click to expand...
Click to collapse
Not really if you use factory images.
https://forum.xda-developers.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067

Edit: nevermind

Badger50 said:
Not really if you use factory images.
https://forum.xda-developers.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067
Click to expand...
Click to collapse
I guess it depends on what Factory Image information is needed.

State.of.mind said:
Great write up...as always. Is there an way to update security patches and keep root?
Click to expand...
Click to collapse
Thank you!
No, but look at # 9C

How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
State.of.mind said:
How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
Click to expand...
Click to collapse
Never mind. I used this link to figure it out: https://support.google.com/pixelphone/thread/18553639?hl=en Hopefully it helps someone else

So this may be a dumb question but, does accepting an OTA relock the boot loader?

fredgar75 said:
So this may be a dumb question but, does accepting an OTA relock the boot loader?
Click to expand...
Click to collapse
No, but you must be Stock to accept the OTA, unless you do the Magisk OTA Installation.

State.of.mind said:
How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
Never mind. I used this link to figure it out: https://support.google.com/pixelphone/thread/18553639?hl=en Hopefully it helps someone else
Click to expand...
Click to collapse
I guess you didn't see the description of the Factory/OTA at the end of the download Factory/OTA links in 'Prerequisites'.

Will this work on the Verizon Pixel 4 XL??

SAMCR02018 said:
Will this work on the Verizon Pixel 4 XL??
Click to expand...
Click to collapse
If the bootloader is unlocked, it will work.

Homeboy76 said:
If the bootloader is unlocked, it will work.
Click to expand...
Click to collapse
That I know ok can the Verizon version get the BL unlocked?

SAMCR02018 said:
That I know ok can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
AFIK there is no method of unlocking the bootloader of a Verizon Pixel 4 XL after you activate it.
This thread suggest a possibility of unlocking A Verizon Pixel 4 XL bootloader if done before you activate it.
https://forum.xda-developers.com/pixel-4-xl/how-to/root-instructions-verizon-pixel-4-xl-t3990767

[deleted]

Factory/OTA Images - Dec 2019

Does someone have December boot.img? Ater updating got into bootloop, flashing previous magisk boot image with fastboot didn't worked

Can anyone definitively tell me whether re-locking the bootloader will wipe any data on the Pixel 4 XL? Thanks in advance!

fronc said:
Can anyone definitively tell me whether re-locking the bootloader will wipe any data on the Pixel 4 XL? Thanks in advance!
Click to expand...
Click to collapse
Yes....it definitely will! All of it!

Factory images are up. Does anyone know which one is for which?

[Error][fix][Solution][Guide]Errors in flashing custom rom in Lenovo A2016a40 and ways to tackle/fix them

CASE: After flashing lineageOs 14.1 on my Lenovo A2016a40 (chipset: MT6735M) using TWRP, I lost my IMEI and Baseband version which made my phone just like a screen with no calls, no connection, no internet. so, basically I had no option than to flashing the stock ROM (eventually I need that custom ROM as that is an upgraded one). I flashed only secro.img on the custom rom using SP Flash Tool that caused a bootloop ( I again had to took help of the stock rom ).
Now, the question is:
1. Can I flash secro.img on that custom Rom, if yes, how?
2. If not, how can I get back my baseband version?

today I flashed ressurection remix 5.8.4 on the mentioned device and that caused the exact same problem as mentioned.

Well, today I succeed after 2 weeks of sleepless nights in search of a solution that elaborates how to flash a custom rom successfully on the mentioned device(i.e. Lenovo A2016a40 (also known as Lenovo vibe B)). Now, as I felt the frustration of seeing the phone without network and everything else, I want to mention the whole process I've gone through.
Here is the step-wise guide on how to flash a custom ROM on Lenovo A2016a40 (Hope it works with other devices too)
NOTE: Here in this tutorial I'm not asking you to try a custom rom, it's upon u to use custom rom or not. this tutorial is to guide those who has already stepped into the process and get into an error or so(hope not so). any damage to your device is solely your responsibility, try in your own risk if you want.
GOOD LUCK
BEFORE FLASHING:
1. Take your normally functioning device.
2. Root that device.
For Lenovo A2016a40 I've followed this neat and clean page and found it helpfull.
Here is the summary of that really clean page (the page is a bit outdated follow my paths for updated method (as in December 2020) ).
a) Download and install Magisk Manager app on your andrid device.
b) Launch the app and tap on "install" that is on the same slide as the logo, and then choose to patch boot image by tapping on "Patch Boot Image File" after which the patching process will start which will create a image file called "magisk_patched.img".
c) Transfer that magisk patched image file on your PC.
d) Connect your device to your pc where you have stored magisk patched image.
e) Now enable "USB Debugging" and "Enable OEM unlock" from Settings>Developer's option (or, Settings>About Phone>7x tap on Build Number>Settings Home> Developer's option)
e) (Assuming you have ADB and Fastboot installed, if not follow whatever google says.) Now, open cmd on the folder where you have kept that magisk pathced image by
Code:
Shift+Right Click
and selecting "Open Command window Here" and check for your device's connectivity by typing
Code:
adb devices
in cmd, and after confirmation(seeing device's serial number) type
Code:
adb reboot bootloader
to enter fastboot mode (Fastboot Mode written on screen), confirm connectivity by
Code:
fastboot devices
, being confirmed type
Code:
fastboot oem unlock
to unlock bootloader and then do press
Code:
Volume up
button to unlock bootloader.After seeing "Okay " on command window, type
Code:
fastboot flash boot magisk_patched.img
and finally
Code:
fastboot reboot
and then press and hold
Code:
power + volume 'up'
buttons of your phone for about 10 seconds and then navigate to 'Normal mode' by using
Code:
volume up
button and confirm by using
Code:
volume down
button and wait for device to start.
f) Check Root status using Root Checker like apps
2. Backup some important system files.
This step is essentially important. I got into this from this thread.
a) Install Root Manager or similar apps and grant them root permisions.
b) Head to /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
c) Copy the mentioned files into a safe place(generally in external sd card) or newly created folder.
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
d) Now, head to /data/nvram/md/NVRAM/NVD_IMEI and copy the file named
Code:
MP0B_001
to another safe place generally in external sd card.
NOTE: All the above mentioned files are important for your device's network functioning.
e) Now, backup or replace whatever you want to keep (personal things).
FLASHING:
1. Download your preferred custom rom(.zip file) strictly for your device and transfer them into the inserted sd card or phone internal memory.
2. Install a custom reecovery.
Download your preferred custom recovery. I've used TWRP custom recovery and going to describe processes for that only.
a) Connect your device to pc and confirm connect by above mentioned method from the downloaded folder and then unlock bootloader the same way as mentioned above.
b) After unlocking bootloader run the commands as mentioned below (press "Enter" after each line)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
c) Now, enter the menu containing "Normal mode" option by the same mentioned method and this time select "Recovery mode" and you will get into TWRP custom recovery.
NOTE: Critical error can occur if you do pull out the battery and power off the device by any other means.
NOTE. After entering TWRP you can face an error saying
Code:
/data not mounting
or something like that, in that case head toward wipe section, select "Advanced wipe", select 'Data' and select 'Repair File system', then change partition style to "ext2" and then back into "ext4" and this solves the problem.
3. Backup your system and whatever you like. (generally "secro" "nvram" & "nvdata")
4. Free space for new custom rom by entering Wipe section and selecting the following
Code:
Dalvik/ART
system
Data
Cache
Internal Stoage (if you want to or optional)
5. Install your custom rom (with Gapps and Root if you want).
Enter "Install" section select and install .zip files for custom rom, gapps and root one by one or at once, whatever you want.
AFTER FLASHING:
Welcome to your literally new phone.
while you are expecting to celebrate it, you will find some of the most frustrating errors like Unknown Basband, Null IMEI.
Now to solve those errors follow the below mentioned points one by one
1. install root manager like app and grant root permission.
2. copy and paste the 7 files that you have copied earlier (expdb, proinfo, protect1, protect2, nvdata, nvram, secro ) to the path as " /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name", if prompted select "Overwrite", then select the files and provide them all 9 permissions you will get in permission section for those files.
3. Reboot Device.
4. now, delete the folder named "nvram" in path "/data/nvram" to get your baseband version back, as mentioned in this thread, and it worked for me, you may have to try deleting it 3-4 times continuously.
5. Reboot device.
6.Now, copy and paste the copied 'MP0B_001' file to the path as "/data/nvram/md/NVRAM/NVD_IMEI" and similarly assign all the 9 permissions asked in permission window.
7. Set APN if needed. follow this tutorial and you may not be able to save changes (hope not), if so, try putting some random name in the 'Name' field like "avghbejugcbjnsjckln".
8.Reboot Device.
Enjoy the fresh new customization.
NOTE: Keep your device's stock firmware and sp flash tool with you. it will help you get your device back from a bricking type error. try in your own risk.

How To Guide [Unofficial] Unlocking the bootloader, rooting, and installing TWRP on Nokia 2.2 with Android 11

to moderators: this is my first thread ever, and thought a complete guide like this really has to be done. if it's not right or not in the right place, do what is right
Click to expand...
Click to collapse
Since there are only 3 useful guides about modifying this specific phone, and some really don't answer a few barriers placed in our way by HMD Global and its ridiculous OEM unlocking restrictions (-_-), and also Google probably dropped making OTA updates for it (which was very important to me, because Android 9 and 10 had bugs), I decided to mix them all up (I will give credits, obv) and add some more info I found and create a thread which will work on Android 11, which worked on my phone, not tested on another Nokia 2.2.
Hope it helps y'all!!
Part 0: Preparations
WARNING: Your storage will be wiped completely!! so make sure to back everything you need up before doing anything. Unless you have bricked/soft locked your phone, then in that case you can use MTK Client app to backup userdata.bin (more info on Part 1-2, marked with a )
Requirements:
A good computer
Obviously a network connection on your computer for downloading files, and on your phone if you wanna update thru OTA
USB cable, capable of transferring data, and without any annoying repeated disconnections or "has to be put in the right angle and position". Just use a fresh one
VCOM and adb drivers, which can be a little annoying getting them to work. Best option is to install 15 seconds minimal ADB and make sure you say Yes when it asks if you want to install device drivers.
Android SDK Platform tools, which can be downloaded from here (NOTE: You have to use Platform tools. minimal adb will NOT work with fastboot on this device. So go to C:\adb and delete everything in there, then extract platform tools in that folder instead)
and the most important of them all: MTK Client by Bkerler which can be downloaded from here. Follow the installation instructions in the link, install Git and Python and also usbdk installer featured in the Github instructions for MTK Client
All done? Great! moving to the next part
Part 1: Unlocking the bootloader
The most annoying part. Thanks to hikari_calyx for their awesome guide on how to unlock the bootloader for this phone. We will follow it step by step until we reach step 6, where we are about to flash all those backed up img's back using mtk-su. Here's the problem, you can use mtk-su only on Android 9. it doesn't work on Android 11 sadly. so we just make sure we have unlocked sec1.img and seccfg.img in a safe place, then install a fresh stock Android 9 rom om our phone with any method we are most comfortable with, like SP Flash tool like in the guide, or booting into recovery and sideloading thru adb or from sdcard. just search the net and I'm sure you will find a loooot of sites explaining how you can flash a stock android on your phone. Just make sure you won't mess IMEI and Serial Number up!!!
**There is a "unlock bootloader" option in the flash tools tab of MTK Client. haven't tried it out myself but you can give it a try**
Extra: Booting into stock recovery
There is another detailed guide on how to enter recovery mode, by foobar1123321 which you can see in here. You might need it to apply updates to your phone
After flashing and updating your OS to latest version of Android 11, it's time for Unlocking the bootloader again. but sadly, Unlocked OEM doesn't let OTA updates to be received, and trying to flash sec1.img and seccfg.img on Android 11 is not possible without root, and root is not possible without OEM unlocking :\
So here comes the neat part, MTK Client
Part 1-2: Unlocking the bootloader again
Go to the folder where you installed MTK Client (hopefully you know how git works and got it cloned and working, if no, then read Installation instructions carefully in their Github page), and open a CMD window there by typing in cmd in the address bar. then write python mtk_gui and hit enter. Do not use mtk_gui.bat since it will close the cmd and not work. Do NOT close this cmd tab. After a while, the app will start and asks you to connect your phone.
Shut down the phone, and after 5 seconds, press and hold both volume up and down keys (without the power button) and connect the phone to your computer via cable while still holding the volume buttons. If you have installed the drivers successfully, then you'll see some texts generate in the cmd window, and will (probably) wait for the Preloader VCOM.
you can let go of the volume keys.... but not for so long. Disconnect the USB cable, hold volume keys, and connect the phone again and you'll see that MTK Client successfully gets access to your phon. YAAAY!!
now you can let go of the volume keys
Go to "Read partitions" tab, and select Boot_a, Boot_b, sec1, and seccfg (make sure you wouldn't mistake them with unlocked sec1 and seccfg)
And then click on Read partitions button in the right side, and choose a location to save these partitions
You can also check userdata, if you have bricked/soft locked your phone and wanna backup your Internal storage data. You can flash it again with this app after you have fixed your phone. and if the problem wasn't caused by your data, you can use them again like you never wiped your phone
After everything is backed up, go to "Write partitions" tab, and find sec1 and seccfg, click on "set", browse and select the respective unlocked partitions we got in Part 1 (you may need to change their extension from .img to .bin for them to show up)
Click on "Write partitions", and done! You have unlocked your OEM on Android 11!! and if everything is done correctly, you'll see
Orange state Your device is unlocked and cannot be trusted Your device will boot in 5 seconds...
Click to expand...
Click to collapse
or something like this when powering it on, congrats!!
Part 2: Installing TWRP
from the official TRWP page for Nokia 2.2, download the latest TWRP image file and move it to c:\adb on your computer and rename it to twrp.img
you will also need to download a stock vbmeta image, which can be found here or simply by reading it from your phone via MTK Client (there will be two A/B partitions, any of them works) and rename the downloaded/grabbed file into vbmeta.img and move it to c:\adb
power off your phone, then boot into fastboot by holding Volume down + Power for a few seconds, until it says FASTBOOT MODE => then connect the phone to a PC, and write:
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
and then
fastboot flash boot twrp.img
Click to expand...
Click to collapse
Now we have the latest TWRP on our Nokia 2.2 , but seems like accessing TWRP is only possible by either rebooting to recovery when the phone is powered on, via Magisk, Termux, or any other app with power options (after rooting the phone), or writing this when the phone is in fastboot mode:
fastboot reboot recovery
Click to expand...
Click to collapse
You can use TWRP and all of its awesome features now, except for MTP, backup, reading userdata partition, etc. to fix that, you gotta wipe internal storage, so make a backup of your files before processing.
**IMPORTANT: Do not flash TWRP after rooting the phone or it will unroot it**
Part 3: Rooting via Magisk
I'm gonna use Magisk because... it's better than other SU apps. Get it from here and install it on your phone. Now that you have your OEM unlocked and boot partitions too, you just have to copy the partitions we got via MTK Client on your device, launch Magisk app, select Install Magisk, then choose a file, which is gonna be Boot_a.
Wait until patching is finished, and after it's done, go into downloads folder and rename it to Boot_a or you will get confused later
After that you can choose Boot_b to be patched, and after it's done, rename it to Boot_b too
Copy them both to C:\adb from your phone to your pc, and power off your phone
after you get sure device is not connected to the computer via cable, and is powered off, hold down the volume down key with power button, until your phone boots into fastboot mode
Now open a cmd in C:\adb, and write
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_b.img
Click to expand...
Click to collapse
when done, disconnect your device, and restart. You can check the Magisk app, and realize you now have superuser permissions!!!
**UPDATE** Part 3-2: Hiding Magisk
Hiding Magisk and bypassing SafetyNet is another challenging problem on this phone. Cause when you try to Hide the Magisk app, you'll come to a simple "Failed!" error which is most probably caused by SELinux status. To fix this we gotta install some modules
First of all, install Busybox from Google Play or any other source. It's not necessary, but it's good to have. simply just install it, no need to restart
Then we need to install a module called SELinux permissive (wow, how unique ;w; ) by evdenis, which can be found here. download the zip in your phone, open the Magisk app, and in the modules tab browse for our newly downloaded zip and wait until the operation is done. Reboot your phone, and you are now able to hide Magisk app without any problem.
So do so, open Magisk -> settings -> hide the Magisk app. Choose a name (settings by default) and wait until app launches itself, asking you to add a shortcut to your home screen (optional). This way, your Magisk app now has a random package name and signature and can't be detected by other apps. Now moving to the next part
Bypassing the SafetyNet:
First, in Magisk settings, enable Systemless hosts. it will add its module to the modules tab. check if it's enabled
Then toggle Zygisk in Magisk settings, and restart your phone again (2 restarts? alright no problem)
Once your phone booted up, on the main screen of Magisk, check if it says Yes in front of Zygisk. if yes, than congrats! we are not down yet tho
Go to Magisk settings and toggle Enforce DenyList, don't reboot for now (yes, there is a 3rd one coming ), but go to Configure DenyList and choose the following apps
Google Play Service
Google Play Store
Google Service Framework
Google Play Protect Service (which is probably not present, but wrote it just in case it is on your phone)
Click to expand...
Click to collapse
and also you can choose your banking apps, or any app that prevents you from using them like Netflix or some games. Now you gotta restart (third time is the charm )
Now we gotta install another module which is Universal SafetyNet fix by kdrag0n which can be found here. Download it to your phone, choose it in Magisk module browser, wait for it to finish, and restart (I'm losing my control!!! Hmph!)
Now that we did all this, we have to clear data of apps in our DenyList so they would never remember if we ever had root or no
Go to settings (the actual settings, not our now hidden Magisk app) -> Apps -> all apps -> tap the 3 dots on top -> show system apps, then find all the apps you added to your DenyList and clear their data (not cache, data itself)
Now that this is down, restart your phone ((╯°□°)╯︵ ┻━┻) it's the last time, so you can stop raging now (┬─┬ノ( º _ ºノ))
Now we can install an app like YASNAC and run SafetyNet attestation, if the results showed two pass checks, Congratulations, you bypassed SafetyNet!!!
Totally worth the restarts. (Thanks to Droidwin for their article)
And that's it!! Hope you enjoy your now rooted Nokia 2.2 phone with Android 11

Great guide, and yes mtkclients unlock will work but it may put Ur device into verity eio mode

¿Can I use the Part 3-2 to hide Magisk in Android 9 instead of 11?, I find stock Android 11 very laggy and unstable on my phone (using the camera on any app can take from 1 to 3 or 4 tries to get it working, for example), and Android 9 has served me waaaaay better. However, my banking app refuses to work with root.

How To Guide [All-in-One] Xiaomi 13 (fuxi): Unlock Bootloader, Root, Flash TWRP, Flash ROM

[All-in-One] Xiaomi 13 (fuxi): Unlock Bootloader, Root, Flash TWRP, Flash ROM
Dear Xiaomi 13 user,
I'm not responsible if anything happens to your device. If you execute these AiO procedures properly then you shouldn't face any problems. Before you proceed please back up all your important data and make sure that your phone battery is charged >80%!
A. Prerequisites:
1. Install ADB and Fastboot tools with drivers on Windows
How to do this please read here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Restart your computer.
2. Enable "OEM unlocking" and "USB debugging" in your device
a. Enable Developer Options in: Settings/About Phone/MIUI version. Click on MIUI version 7 or 8 times
b. Now go to: Settings/Additional Settings/Developer Options and check "OEM unlocking" and "USB debugging"
3. Create a Mi Account
If you don’t have a Mi Account, then create one here: https://account.xiaomi.com
4. Connect your Mi Account to your device
Go to: Settings/Additional Settings/Developer Options/Mi Unlock status and check "Add account and device"
B: Unlock the Bootloader
Unlocking the bootloader will erase all your data! So please back up your data before you unlock the bootloader!
1. You must enable "OEM unlocking" and "USB debugging" as per point A.2.
2. You must connect your Mi Account with your device as per point A.4.
3. Download Mi Unlock Tool here: https://en.miui.com/unlock/index.html
4. Enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable)
5. Start the Mi Unlock Tool
6. Enter your eMail and your password of your Mi Account (the same account which you added to your device - Point A.4.)
7. Connect you device to your computer and start the unlock procedure
8. Follow the unlock tool instructions until the unlock procedure is finished
9. Reboot your device
C: Root Your MIUI ROM without TWRP
1. Your Bootloader must be unlocked (see Point B)
2. You must enable "OEM unlocking" and "USB debugging" as per point A.2.
3. Download the fastboot ROM (the same ROM currently installed in your device) from here: https://xiaomifirmwareupdater.com/miui/fuxi/ and unzip it.
4. Open the file and extract the "init_boot.img" on to your computer.
5. Transfer the “init_boot.img” from your computer on to your device
6. Download the latest Magisk manager App from here: https://github.com/topjohnwu/Magisk and install it on to your device.
7. Open Magisk App and click install, and then "select and patch a file" (of course you select “init_boot.img”)
8. Transfer the patched boot.img file from your device’s download folder on to the “ADB and Fastboot” folder in your computer. In the computer rename the patched file into: “patched_boot.img”
9. Switch off your device. Now enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer
10. Go to “ADB and Fastboot” folder in your computer and open a command window inside that folder.
Enter the terminal command in command line: >>fastboot boot patched_boot.img<< and hit enter. Now the device will restart.
Attention your device is now only temporary rooted, so don’t restart your device just yet. Find Magisk app in your device, open it, click “install” and then check “direct install”, then press “let’s go”. Magisk will now install and make the root permanent. Now click “reboot” and the device will restart.
If this procedure doesn't work with the file “init_boot.img”, then use the file “boot.img” instead and follow the same procedure.
D: Install A Xiaomi.eu ROM
1. Your Bootloader must be unlocked (see Point B)
2. You must enable "OEM unlocking" and "USB debugging" as per point A.2.
3. Download and put onto your computer the Xiaomi.eu ROM (please select fuxi) from here: https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv14/ and unzip it.
4. Switch off your device. Now enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer.
5. In your computer (in the Xiaomi.eu ROM folder) please click the file: “windows_fastboot_first_install_with_data_firmat.bat" (if you’re using windows, or press the proper file if you’re using mac or linux) and computer will do the rest. The device will restart.
E: Root Your Xiaomi.eu ROM without TWRP
1. Your Bootloader must be unlocked (see Point B)
2. You must enable "OEM unlocking" and "USB debugging" as per point A.2.
3. Pls find in your computer the downloaded and unzipped hybrid Xiaomi.eu ROM from Point D.2.
4. Find the file “init_boot.img” and transfer it on to your device
5. Download the latest Magisk manager App from here: https://github.com/topjohnwu/Magisk and install it on to your device.
6. Open Magisk App and click install, and then "select and patch a file" (of course you select “init_boot.img”)
7. Transfer the patched “init_boot.img” file from your device’s download folder on to the “ADB and Fastboot” folder in your computer. In the computer rename the patched file into: “patched_boot.img”
8. Switch off your device. Now enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer
9. Go to “ADB and Fastboot” folder in your computer and open a command window inside that folder.
Enter the terminal command in command line: >>fastboot boot patched_boot.img<< and hit enter. Now the device will restart.
Attention your device is now only temporary rooted, so don’t restart your device just yet. Find Magisk app in your device, open it, click “install” and then check “direct install”, then click “let’s go”. Magisk will now install and make the root permanent. Now click “reboot” and the device will restart.
If this procedure doesn't work with the file “init_boot.img”, then use the file “boot.img” instead and follow the same procedure.
F: Install TWRP
To be updated once the official TWRP for this device is available.
G: Install A Custom ROM
To be updated once official custom ROMs (Lineage etc.) for this device are available.
H: Return To MIUI
1. Your Bootloader must be unlocked (see Point B)
2. You must enable "OEM unlocking" and "USB debugging" as per point A.2.
3. Download and put onto your computer the latest fastboot ROM from here: https://xiaomifirmwareupdater.com/miui/fuxi/ and unzip it.
4. Switch off your device. Now enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer.
5. In your computer (in the folder where you have put your ROM) please click the file:
a. “flash_all.bat" (if you want to make a clean install but keep the bootloader unlocked).
b. “flash_all_except_storage" (if you want to make a clean install but keep your data and maintain the bootloader unlocked).
c. “flash_all_lock" (if you want to make a clean install and lock the bootloader).
In all three cases (a., b., c.) when flashing is finished, restart your device.
If my guide helped you, please click "thanks" and enjoy your phone.

Frequently Asked Questions (FAQ):
1. Waiting time to unlock the bootloader
Q. If I receive the message: "unlocking can be done after 72h or 168h or 360h etc.". Is there a way to skip this waiting time?
A: Unfortunately you have to wait for that time to pass. There’s no way around it (that I know of). It seems like new and never used (to unlock bootloader) accounts receive a shorter waiting time.
2. Unlock procedure stops at 99%
Q: If my unlock procedure stops at 99%, what could be the problem?
A: Most problay you're using two different Xiaomi accounts. You have to use the same account that you have added into the device also in the unlock tool otherwise it will not work.
3. Recommended ad-blocker (for rooted devices)
Q: I want to block the advertisement in all apps, what app can you recommend?
A: If you decide to root your device, then you can install AdAway from here: https://adaway.org/. In order for AdAway to work properly please add in the Magisk App the Systemless Hosts (Magisk/Settings/Systemless Hosts).
4. Retaining the root after ROM update
Q: If I root my device as per point C, E of the AiO and I install a system update in my device, is the root still available?
A: Unfortunately root will be removed after the system update. So you have to repeat the procedure in point C, E.

I need to correct you, sorry. After manny tries, unlocking xiaomi 13 is:
you mod boot.img and init_boot.img with magisk
fastboot flash init_boot *init_boot_moded.img*
fastboot flash boot_ab *boot_moded.img*
fastboot reboot
Unfortunately root has no full access, no access to /system so android auto, even if moded to system app not working. build.prop also not editable by any way
I got stock builds from https://xiaomistockrom.com/xiaomi-13
tried on 14.0.4 and 14.0.9
At some point something went wrong and phone went in fastboot loop reboot. Susccesfully flashed using MiFlash20220218

me_Alex said:
I need to correct you, sorry. After manny tries, unlocking xiaomi 13 is:
you mod boot.img and init_boot.img with magisk
fastboot flash init_boot *init_bootmoded.img*
fastboot flash boot_ab *bootmoded.img*
fastboot reboot
Unfortunately root has no full access, no access to /system so android auto, even if moded to system app not working. build.prop also not editable by any way
Click to expand...
Click to collapse
With A13 the system remains in read only.

Twrp unofficial released

huntersun said:
Twrp unofficial released
Click to expand...
Click to collapse
Where?

NOSS8 said:
Where?
Click to expand...
Click to collapse
Xiaomi13-TWRP_3.7.0-A13.img
drive.google.com
NOSS8 said:
Where?
Click to expand...
Click to collapse
fastboot flash recovery_ab Xiaomi13-TWRP_3.7.0-A13.img

huntersun said:
fastboot flash recovery_ab Xiaomi13-TWRP_3.7.0-A13.img
Click to expand...
Click to collapse
If the link does not lead to the download and requires a subscription to TG, you must edit your post and delete the link. XDA rules.
But you can put it online via a cloud.

NOSS8 said:
If the link does not lead to the download and requires a subscription to TG, you must edit your post and delete the link. XDA rules.
But you can put it online via a cloud.
Click to expand...
Click to collapse
Already fixed

me_Alex said:
I need to correct you, sorry. After manny tries, unlocking xiaomi 13 is:
you mod boot.img and init_boot.img with magisk
fastboot flash init_boot *init_boot_moded.img*
fastboot flash boot_ab *boot_moded.img*
fastboot reboot
Unfortunately root has no full access, no access to /system so android auto, even if moded to system app not working. build.prop also not editable by any way
I got stock builds from https://xiaomistockrom.com/xiaomi-13
tried on 14.0.4 and 14.0.9
At some point something went wrong and phone went in fastboot loop reboot. Susccesfully flashed using MiFlash20220218
Click to expand...
Click to collapse
The reason behind the system partition being unreadable is that Xiaomi is using the new EROFS filesystem, instead of the old ext4. EROFS provides way faster reading and writing speeds, as well as saving space by compressing files dynamically. EROFS stands for Enhanced Read Only File System, so as the name suggests, there's no workaround to edit system files unless you have magisk.
More on EROFS:
EROFS - Wikipedia
en.wikipedia.org

huntersun said:
Twrp unofficial released
Click to expand...
Click to collapse
Do you have the device tree for TWRP? I want to build some ROMs for fuxi.

mnitpro said:
Do you have the device tree for TWRP? I want to build some ROMs for fuxi.
Click to expand...
Click to collapse
Please ask YuKongA, he have device tree, kernel,... But he was hide the gits.
YuKongA/kernel_xiaomi_fuxi
Contribute to YuKongA/kernel_xiaomi_fuxi development by creating an account on GitHub.
github.com

huntersun said:
Please ask YuKongA, he have device tree, kernel,... But he was hide the gits.
YuKongA/kernel_xiaomi_fuxi
Contribute to YuKongA/kernel_xiaomi_fuxi development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks a lot for sharing. I'll reach out to him.

mnitpro said:
Do you have the device tree for TWRP? I want to build some ROMs for fuxi.
Click to expand...
Click to collapse
Hey bro, does your build plan include pixel experience? I would love to experience it on Mi 13.

TWRP for FUXI
https://forum.xda-developers.com/t/shared-twrp-by-skkk.4549573/

Whats Xiaomis current policy about root and warranty, i remember they used to be "friendly" about it.

Wish they shortened the unlock waiting time to couple of hours, i'd consider another Xiaomi again. Last one was Xiaomi 9, I had to wait 2 weeks while phone being unused (not rooted = insecure).

Dumb question:
If i unlocked bootloader, flashed another rom (like global or EU) , can i relock it ?
And later, if i want to unlock it again, do i have to wait another 7 days?

Dark Hunter said:
Dumb question:
If i unlocked bootloader, flashed another rom (like global or EU) , can i relock it ?
And later, if i want to unlock it again, do i have to wait another 7 days?
Click to expand...
Click to collapse
You can lock the bootloader only with stock roms.
Chinese model, locking possible only with a CN rom.
Global model, all roms except CN.
No 7 day waiting period if you use the same account.

senerex said:
[All-in-One] Xiaomi 13 (fuxi): Unlock Bootloader, Root, Flash TWRP, Flash ROM
...
E. Install A Custom ROM
To be updated once official custom ROMs (Lineage etc.) for this device are available.
Click to expand...
Click to collapse
I'm holding off on buying a global device for if/when AOSP custom ROMs come out.
Thanks for the thread!