Database Info

Infinix Zero 5/Zero 5 pro (X603) TWRP Recovery 3.1.1 With OTA Support

Touch is Working Now. (Finally) with OTA Support only for zero5 indian varient
Join Telegram group for further development : https://telegram.me/infinixzero5
This is Ported TWRP Recovery from a same Mt6757 chipset model. which i used to port it for our Infinix X603.
Thanx @topjhonwu for magisk.
Thanx for @majorkid for making OTA supportable
TWRP for non indian and global version for necessary changes. (Need to test)
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Unlocking Bootloader
- Make sure your Bootloader is Unlocked. If already unlocked jump to how to flash.
Process to unlocking.
1. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
2. go to developer option turn on usb debugging and OEM unlocking.
3. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
4. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
5. Click it, A cmd or power shell window will open.
type "adb devices" - it show some no of your device just give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
type "fastboot oem unlock" follow onscreen instruction on phone, press volume + to confirm. thats it but it will erase all your data.
Reboot phone by pressing power button for 10 sec. setup it as temporarily.
Flashing of TWRP
1. Download the Latest TWRP Recovery Image and extract it (Attached). Use correct version for your device for OTA support.
For India (Indian) For Global (Global)
(Insert a SD card in your phone to take stock boot.img backup it will required for OTA in Future.)
2. Go in adb fastboot folder which is copied to C. copy twrp_recovery.img here then press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
3. Click it, A cmd or power shell window will open.
4. Flash it via fastboot cmd (fastboot flash recovery Twrp_recovery.img) don’t use bracket.
It will flash recovery on your phone. Now type fastboot reboot in cmd window and press and hold vol+ button and hit enter.
Phone will reboot in twrp recovery.
Note : After flashing first time it will ask for password due to phone is encrypted.
a. just cancel it and allow to modify system by swiping arrow at down and select 2nd last option at right side then select globe icon on right and chose your language English.
(First take Boot.img backup Via backup option in TWRP in SD Card. (bcz internal storage shows 0 mb here at this movement.) It will use for OTA so save it.
b. then flash magisk manager.zip file attached here. (it will remove dm-verity and force encryption from boot.img) and give root access.
c. then go to Wipe and select format Data it will erase all data on your internal storage. remember it will erase your data in ext4 format so go to wipe advance select data and change file system to f2fs. Ext4 data not supported by kernel so you got loop to recovery so It must to repair data in f2fs.
d. Done Reboot to recovery and you got mounted storage.
Another Method.
- Flash it via SP flash tool. (use version 5.1744 recommended)
How to use SP flash tool :
Install Vcom media tek driver on your pc.
More detail and download available on following link
https://spflashtool.com/
IF ANYONE GOT LOOP IN BETWEEN TO RECOVERY MEANS PROCESS NOT FOLLOWED PROPERLY.NOT BOOTING PHONE JUST FLASH STOCK RECOVERY. YOUR PHONE WILL BOOT THEN DO PROCESS AGAIN.
OTA-
1. When ota available just download it. Don’t start flashing.
2. Location of OTA downloaded file in Root so use any root file explorer.
3. File can be found in :-
a. Root/cache/update.zip
b. Root/data/data/com.google.android.gms/app_download/update.zip
4. Copy file name is update.zip to your sd card or phone memory.
5. Reboot to recovery and flash first stock boot.img which you already taken backup and saved before when flashing twrp.
6. now flash update.zip via TWRP (dont reboot after flashing otherwise you will currept your system)
7. After flashing update.zip, first again take backup of your boot.img for future ota update.
8. After taking backup of boot.img flash magisk.zip and reboot. (If you did not flash magisk then your data again encrypted and u lose all data)
6. Done you are on latest version.
Note:- Always remember to flash magisk.zip at last before reboot.
OTA SUPPORTABLE TWRP Link for zero 5 global varient by @majorkid -
https://androidfilehost.com/?fid=890129502657578792
OTA SUPPORTABLE TWRP Link for zero 5 pro global varient by [MENTION=7078341]majorkid[/
https://androidfilehost.com/?fid=890129502657578807
Update: Last updated on 27/01/2018 (With almost all stock stuff with OTA support)

Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)

XDAdeveeloopers said:
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
Click to expand...
Click to collapse
flip screen was old but i updated it with working twrp. is it showing vernee mix 2 name on top?
can you send screen shot.
its working perfectly.
just match the zip size which you downloaded (if it is 13.23 mb then it is old)
download current version attached above is 15.31 mb in size.
Screen Shot is also updated
Let me know your success.............................

flipped screen fixed !
Ok, now it's not flipped but the touch is still disabled
again, thank you for your efforts. I've attached the screenshots. it tells me to enter the password but the touch is disabled and i couldn't type anything.

At this stage only cancle button will work. Dont type anything just press cancle button.
It shows next screen.
I chek if issue is there.

Cancle is not working too

XDAdeveeloopers said:
Cancle is not working too
Click to expand...
Click to collapse
just use it as temp. bcz after flash touch not working.
Touch is disabled in kernel for recovery partation by infinix.
for temp use cmd.
fastboot boot recovery.img
will update soon..........

when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?

XDAdeveeloopers said:
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
Click to expand...
Click to collapse
Read OP carefully. You need to format data partition completly first time and need to patch boot img via lazy flasher.
Showing 0mb bcz it is encrypted. You can use memory card.
If you want root then go for magisk root till recovery updated.

OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work (extracting ramdisk failure aborting) , isn't there any way to install supersu in order to get apps working correctly?

XDAdeveeloopers said:
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work, isn't there any way to install supersu in order to get apps working correctly?
Click to expand...
Click to collapse
which busybox your trying and what error.
currently supersu have some error with new devices. which version you tried it should be 2.82 or above.

I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk

XDAdeveeloopers said:
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
Click to expand...
Click to collapse
Use busybox form playstore stericson.

I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.

Finally the Touch is updated and working now.
I enabled touch in kernel which is disabled for recovery partition.

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
System is encrypted.
Use magiskmanager beta 14.5 or flash lazyflasher via twrp then one time you need to wipe data partition.
Always remember when you flash orignal boot.img you need to flash lazyflasher or magisk otherwise your system will become encrypted again.

Thank you, now touch is working perfectly <3

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
you can use ndk busybox from magisk app there is option download module.
But currently there is problem with module with this phone. the data partition is in F2FS format and its kernel is not handling f2fs properly.
TWO option for use magisk module.
1. wait for kernel update via infinix. or
2. format data partition as Ext4 from twrp.
Super su does not work correctly with f2fs currently.

But when I format data partition it resets my phone

XDAdeveeloopers said:
But when I format data partition it resets my phone
Click to expand...
Click to collapse
yes formatting data will reset it.

[Guide][TWRP] Lets make Blackphone 2 great again

IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...

Nice work.
Does this stop the phone checking update servers?

loaded2107 said:
Nice work.
Does this stop the phone checking update servers?
Click to expand...
Click to collapse
Yeah It removes all blackphone apps, but you can modify the script

great work although I have encountered a problem in the pixel laucher that gives me error

script not ok
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot

But how is the phone?
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!

carlosinf said:
great work although I have encountered a problem in the pixel laucher that gives me error
Click to expand...
Click to collapse
Hi, I actually move to another phone, I had Lawnchair installed on bp2
Enviado desde mi PRO 5 mediante Tapatalk

notelinos said:
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
Click to expand...
Click to collapse
Hello, that's a big problem. You must flash files from SD card instead of internal, if you flash from internal storage youll get boot loop and I don't know how to solve that
Enviado desde mi PRO 5 mediante Tapatalk

storkinsj said:
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
Click to expand...
Click to collapse
Sorry mate but I don't know, I'm not a dev. I only posted this to help.
Enviado desde mi PRO 5 mediante Tapatalk

chape199 said:
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Click to expand...
Click to collapse
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks

dgc1 said:
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
Click to expand...
Click to collapse
Hi, i dont use the bp2 anymore since past year but i remember that you have to flash the zips from external sdcard, never use twrp to flash files trough internal. Maybe thats the problem. Hope ive helped you.

Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF

kenfalco_14 said:
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
Click to expand...
Click to collapse
To unlock the bootloader I suppose, but how?

kenfalco_14 said:
To unlock the bootloader I suppose, but how?
Click to expand...
Click to collapse
settings
developer options
oem unlocking - on
restart phone
hold volume down (bootloader mode)
connect usb and do command from PC:
fastboot oem unlock-go
## Your DATA will be DELETED ### make backup

I personally have another problem. I can't see TWRP.
Just black screen.
So i'm trying to fight with it using adb shell...
If I have a root and run all scripts mentioned here, I will explain it here later...

BP2 boot to TWRP
Hi All,
I have read several thread and web pages on how to root, install twrp, rom etc and I can not get it to work.
I was able to update the BP2 to 3.0.14 from .9
All I want to do is change to a custom rom.
I did the following:
-enable USB debugging
-enable oem unlock
-installed platform tools on PC
-adb reboot bootloader
-fastboot devices - phone is there
-fastboot oem unlock-go
-reboot - phone appears to be unlocked
-fastboot flash recovery twrp.img
>Sending 'boot.img' (17392 KB) OKAY [ 0.545s]
>Booting OKAY [ 0.040s]
>Finished. Total time: 0.596s
-fastboot reboot
reboots to blank screen
Do over, and when fastboot reboot, I hold down Volume+
still get blank screen
Any ideas?

David_h99 said:
Hi All,
still get blank screen
Any ideas?
Click to expand...
Click to collapse
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.

speed_boy said:
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
Click to expand...
Click to collapse
Thanks for response.
When I do fastboot devices, it shows thone
Once i do the fastboot.exe boot twrp-3.4.0-0-bp2.img command, it reboots and blank screen.
When I do adb shell, i get "adb.exe: no devices/emulators found"
I do adb devices, and it shows no devices attached
I do have installed "Google Nexus ADB interface" device installed

David_h99 said:
I do have installed "Google Nexus ADB interface" device installed
Click to expand...
Click to collapse
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.

speed_boy said:
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
Click to expand...
Click to collapse
I am not able to find where to change this to "adb interface"
do you know how I can change this?

[How-To][Guide] Root Pixel 3 XL with Magisk 18.1 [pre-patched boot.img] - Feb

Updates
Updated to March (.002) based on Magisk 18.1. Please update to the latest adb/fastboot files provided by Google (found in "Useful Links") the latest is "platform-tools_r28.0.2-windows.zip"
As a little plus, I've but putting the stock boots up also since we started. Below in "Useful Links" is a link to my Android File Host where you can find the stock and patched boot images.
Preface
Magisk has been updated include support for Pixel XL 3 (crosshatch) and Pixel 3 (blueline) but I figured I would patch the boot.img and upload it to here for those who want to save a small amount of time or who are lazy like myself. Mishaal Rahman has put out a guide on the XDA Portal that directly inspired this guide and I give full credit to him and topjohnwu
HOWEVER, If you are new the the root/dev/command-line scene I HIGHLY recommend that you follow Mishaal's post on the XDA Portal. He goes into a lot of further detail than I will, tells you how to unlock your bootloader if you haven't already, walks you through the installation of Magisk and has suggestions of what to do with root.
I'm going to try to make this as clean and straight to the point as possible for those of us who know the ropes but also clear and concise enough for any newcomers. All credit is being given, if I overlooked where someone deserves credit, please let me know! Well, let us get to it ya'll!
Pre-Recs IMPORTANT
Unlocked Bootloader (this means no root for Verizon Pixel 3/XL owners) If you do not know how to unlock the bootloader, follow Mishaal's "Part 1" of his post and I recommend following his entire guide for those new to this
Correctly installed and up-to-date adb/fastboot and device drivers (see below for links)
This How-To is written for Windows 10
How-To
Rooting March update (.002) Links to patched_boot.March.002img AndroidFileHost | Google Drive
Make sure you are already on the March update (ending in .002)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date (latest are platform-tools_r28.0.2 for windows)
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting February update
Links to patched_boot.001.feb.img AndroidFileHost | Google Drive
Make sure you are already on the February update (ending in .001)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting January Update
[Links to Patched_boot.img Jan.004 AndroidFileHost | Google Drive
Make sure you are already on the January update (ending in .004)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting December Update
[Links to Patched_boot.img December.006.Magisk18 AndroidFileHost | Google Drive
Make sure you are already on the December update (ending in .006)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting November Update (Patched_boot.img does not work on this method so you have to do it the long way...)
November update is a bit different and we cant seem to get patched_boot.img method to work. So I will outline the process that works for rooting November below. Any guide below requires that you have the latest adb/fastboot installed and that you have an unlocked Bootloader.
If coming from rooted Sept software use this guide:
Uninstall all Magisk Modules then reboot.
Download the stock factory images for Nov.
Extract and find the "flashall.bat" .bat file
Right click > Edit
In the .bat find "-w" and DELETE it
Safe the file
After removing "-w" put phone into fastboot, plug it in, and run "flashall.bat"
Wait for it to get done and reboot
boot to system > go to settings > security and remove any pin or password or pattern
Download the latest Magisk Beta (17.3 as of writing this) and transfer to device internal storage
Now, head over to the TWRP thread and download the twrp_boot.img
Return to fastboot and open cmd in its download location
run "fastboot boot twrp-3.2.3-1-crosshatch.img" and give your device a minute or two to boot into TWRP
Once there, find and flash the magisk beta on the internal storage
reboot and test to make sure it says you're rooted
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
Rooting Sept software and software that shipped with the device
[Patched_boot.img for Sept Drive | AndroidFileHost]
Download the above zip and extract to desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Useful links
Magisk Thread
Link to my AndroidFileHost were all stock and patched boot images are
Direct Link to platform-tools for windows, mac and lunix from Google
Refrence for Pixel 3 XL information (factory images/vendor files/KST)
->This is the one I recommend for quick setup and newcomers 15-second adb for auto install that includes system-wide (got to post #1347 for the most upto date installer)
Manually install adb & fastboot doot drivers for WIndows 10 system wide
Installing for Lunix, MacOS and Windows thanks to the XDA Portal and Aurthor Doug Lynch
Credits
@topjohnwu (link to Magisk thread) He does amazing work; if you can donate to him
@MishaalRahman (link to his amazing instuctions on XDA Portal)
@doughLynch
and
@jlee08517
@ridobe
For being OGs and being here from the begining

This is a evolving and being updated post lol Sorry for the strange layout and poor instuctions at first

it is working now. I think you had to flashed both boot slots in order for it to work. Thank you for the post. It saved me

Thank you eqbirvin. I tried my own boot image from the factory image and tried the other boot image from another thread. (of course they both needed to be patched) I followed the directions to a "T" and kept getting stuck on the bootloader screen. I forgot word for word what it said lolol but something like cannot find secure boot slot. I used your pre patched boot image and worked the first time. Thank you again.

Does this factory reset your phone?

DarkPhoenix said:
Does this factory reset your phone?
Click to expand...
Click to collapse
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.

jrac86 said:
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.
Click to expand...
Click to collapse
Yeah that was a stupid question, I realized that I already knew the answer after I asked it lol.

i am getting a bootloop. my pixel 3 xl starts up to the google logo screen and does the animations but right before it displays the lock screen it crashes and restarts. i am on 030 version of pie and using the boot image that came with the factory images to root with magisk. if i flash just boot_a then i get the error no slot to boot. i have to flash both boot_a and boot_b to get to the logo screen. anyone come across this and have a fix?
also anyone notice the patched image is much smaller than the stock image?
edit: i got it to work. i had to change the patched_boot.img name to boot.img for it to work. also i used the canary build of magisk. this also works for the verizon version 031. 031 boot.img file is the one i patched. i took it from the factory images.

Got approved by androidfilehost so adding another mirror

PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"

Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
Did you flash to both slots or just one? also, follow the guide again and make sure that your downloaded and patched boot.imgs are both completely downloaded AND transfered to device correctly

Is there any way to get Magisk 17.3 installed now? I didn't get it done before John Wu took down 17.3 and now magisk manager will only find 17.2 to install.

Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
I keep getting the same error

I think that this has something to do with Magisk installing 17.2 and not 17.3

State.of.mind said:
I think that this has something to do with Magisk installing 17.2 and not 17.3
Click to expand...
Click to collapse
17.3 has been pulled for some bugs.

jlee08517 said:
17.3 has been pulled for some bugs.
Click to expand...
Click to collapse
So until there is an update
.. No root

State.of.mind said:
So until there is an update
.. No root
Click to expand...
Click to collapse
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.

jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
I've tried the pre patched method and for some reason I can't get that to work

My method should work using my patched boot. It was patched with 17.3. However, If he pulled it because of bugs, I recommend holding off until he updates again to fix the bugs. I will update my patched_boot as soon as I get word that he pushes an update.

jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
Tried the Canary build and I still get boot loops

[GUIDE] Unlocking, rooting & Pixel OS install guide for Pocophone F1

There are already many guides explaining how to unlock, root and install a custom ROM on your Pocophone F1.
But even following the guides, I met multiple issues (access denied to data partitions, boot loops, ADB recovery stopped working ...).
Here is the full procedure that worked for me.
You will need a computer running under Windows for unlocking your phone because Xiaomi only provides a Windows version of its unlocking tool.
I performed the Fastboot and ADB steps under Linux (Ubuntu) because the installation of the tools under Linux is straightforward whereas I had hard times installing ADB under Windows. Moreover, my ADB client sometimes fails to connect under Windows whereas I have no issues under Linux.
Windows steps
-------------------
1/ backup all your personal information (pictures, videos, docs ...) because unlocking will erase all your data.
2/ you have to create a MIUI account from the stock ROM:
- fill in your email address
- set your phone number otherwise Xiaomi won't let you unlock your phone​
3/ Xiaomi constrains you to wait for 72 hours after your MIUI account is created before you're able to unlock.
You have no choice but waiting (users reported that the classical fastboot oem unlock does not work).
The delay may differ from one user to another. Some users even reported a ridiculously long unlocking delay of 720 hours (~ 30 days).
It may depend on your country, phone operator etc ...
4/ download the official Xiaomi unlock tool:
miflash_unlock-en-3.3.827.31.zip
MD5: 8812104e1f6859087f1a9d66481ce9e5
SHA256: 4644878fcaa794d8c0bee67900df80efb28b0d8bd63669d943c043412b06790d​
5/ run miflash_unlock.exe while connected to Internet.
The Internet connection is required because the tool performs a user permission checking before allowing you to unlock your phone.
- fill in again your email address & password
- accept all the annoying Xiaomi disclaimers​
6/ finally you will get a screen with 3 green checkboxes telling you that your phone was successfully unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Linux steps
--------------
7/ install ADB and Fastboot on your Ubuntu system as superuser:
$ sudo apt-get install android-tools-adb android-tools-fastboot​
This simple command is enough for installing all the ADB stuff. Unlike with Windows, you don't need to spend time installing multiple drivers and waste time trying to understand why it doesn't work.
I recommend that all the 'adb' commands are launched as superuser using 'sudo'.
Indeed, some ADB commands will only work as superuser.
Most likely, the ADB path is not set in the superuser environment.
Consequently, you will have to locate the 'adb' path with the 'which' command then launch 'adb' with its absolute file path:
Example with ADB installed under /usr/share/android-sdk/platform-tools
Find 'adb' location:
$ which adb
/usr/share/android-sdk/platform-tools/adb​Launch 'adb' using the found path:
$ sudo /usr/share/android-sdk/platform-tools/adb devices
​
8/ download the following packages and store them all in a new directory called 'adb':
twrp-3.2.3-2-beryllium.img
This is the latest TWRP recovery for the Pocophone F1.
MD5: 3fbf82042f5ea4e332c24cffc6ac1a4b
SHA256: 71a2fb92813fc7c77e7caf2e4b6716dda6cd688d175c56ec6dcdf34a458223b5
beryllium-9.1.24-9.0-vendor-firmware.zip
Under recent versions of Android, the vendor now provides a unified hardware abstraction layer.
Android now relies on this HAL so it can now be released independently from the hardware layer. This new architecture is also called 'Trebble'. The PixelExperience 9.0 released by jhenrique09 on 05/02/2019 relies on the Pocophone Pie 9.1 vendor firmware which must be installed first.
MD5: e931fb719c86f54b12ab4b91857335af
SHA256: 35cd48bab31755287a742ce7dfba4b75343daece2dcf31a27e1a650851e46ae9
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip
This version requires that the Pie 9.1 vendor firmware is installed on the phone.
If you don't, you won't be able to go further and will get the Updater process ended with ERROR: 7 error when trying to flash.
MD5: 804305f334dcb6c1a41b9b2ab91a0ce6
SHA256: 0b8ae9f849971ea14d12065d82fa86fe0051d9570ad08e1008c095757b1fab55
DisableForceEncryption_Treble.zip
This tool will disable automatic encryption which occurs at first OS initialization.
This package includes Magisk 16.7 which will be installed by the script.
This is not the latest Magisk version so we will upgrade it later with the latest Magisk 18.1.
MD5: bb2b91c92aa9d441f41a325438d4a081
SHA256: ba0d9de4474594f01837eebf06edac1daa38775cfa78840cd885c28c5032fae2
Magisk-v18.1.zip
Magisk will allow applications to gain root access to your phone. It does quite the same as SuperSU but it does it better. Magisk pass the SafetyNet test whereas SuperSU generally doesn't. It can also hide itself from apps so they will run as on a stock phone.
MD5: 3ab4d455e6f27f0098c1a723705c6ea1
SHA256: eb06176ea1a2a564a82167902e8159fab13af330f3224c725f04b653232bb527
Magisk-uninstaller-20190204.zip
We will use the uninstaller later to uninstall Magisk 16.7 properly before installing Magisk 18.1.
MD5: 34745c7f3c0d13dbeb5f4223ad887b7b
SHA256: ac80eb0131983c8810fab23d092342e07d1b69b2d91035c027cb7a34ed18f9eb​
Personally, I chose the PixelExperience ROM because it is surprisingly stable and fast for one of the first custom Pocophone F1 ROM.
Moreover and specially if you disable auto-encryption, the phone runs much faster than the stock ROM.
The basic Google Apps are included in the ROM so you don't have to install them separately like you have to do with LineageOS.
Finally, the Pixel interface is very ergonomic and much pleasant to use than MIUI.
Before this, I tried LineageOS 15 then 16 but none of them worked for me. I got some boot loops and it even corrupted my bootloader (look at the troubleshooting section here if you meet the same issue).
9/ if present, remove the SD Card because the system can mess up between the apps installed on the internal storage vs external sdcard.
10/ open a terminal shell
11/ change directory to your 'adb' directory created for storing your packages
12/ with phone unplugged, power off then hold Volume Down & Power to enter FASTBOOT mode
13/ connect your phone to computer using your USB cable
14/ run fastboot devices as superuser to check if your phone is correctly connected:
$ sudo fastboot devices
ad5e3f6 fastboot​
If you see your device listed like here then everything worked fine.
15/ flash the TWRP 3.2.3-2 bootloader:
$ sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
target reported max download size of 536870912 bytes
sending 'recovery' (31004 KB)...
OKAY [ *1.251s]
writing 'recovery'...
OKAY [ *0.312s]
finished. total time: 1.563s​
The flash command will reply 'OKAY' twice if flashing is successful.
16/ you now have to reboot to recovery directly from FASTBOOT mode otherwise your recovery will be overwritten by stock ROM if you reboot to system. This is performed by invoking fastboot with the boot argument.
$ sudo fastboot boot twrp-3.2.3-2-beryllium.img
downloading 'boot.img'...
OKAY [ *1.216s]
booting...
OKAY [ *0.064s]
finished. total time: 1.280s ​
The TWRP splash screen should now show up.
17/ TWRP 3.2.3-2 handles decryption but I chose to work without encryption for several reasons:
- you might be unable to use your external SD card outside your phone because of encryption,
- your phone will run faster,
- certificates could probably be revoked remotely by manufacturers or Google so you can lose access to your phone and data.
If your partitions are encrypted (which is the case if you're coming from MIUI), you should format your data partition to restart from an unencrypted partition. Formatting will erase all your data so check you're backed up before doing it.
18/ you now have to reset your phone to perform a clean install.
As far as I am concerned, I advise wiping everything to start from a fresh brand new system.
To do so, tap Wipe, tap Advanced Wipe then check:
* Dalvik / ART Cache
* Cache
* System
* Data
* Internal Storage​Finally, swipe to wipe.
19/ tap Back arrow then Reboot and finally Recovery
20/ plug your phone with USB cable to your computer.
21/ first of all, kill any running ADB daemon. We do it to be sure ADB daemon is started as superuser.
Indeed, some ADB commands won't work if not superuser.
$ sudo adb kill-server
​Then check that ADB is working from recovery by typing the command:
$ sudo adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ad5e3f6 recovery ​
The 'daemon started successfully' output notifies you that ADB daemon just started.
If your device is listed then everything is fine.
22/ go to your 'adb' directory then type the following command to copy all the packages to the /sdcard phone directory:
$ sudo adb push beryllium-9.1.24-9.0-vendor-firmware.zip /sdcard
beryllium-9.1.24-9.0-vendor-firmware.zip: 1 file pushed. 21.5 MB/s (442907715 bytes in 19.651s)
$ sudo adb push PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip /sdcard
PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip: 1 file pushed. 21.4 MB/s (1065939977 bytes in 47.478s)
$ sudo adb push DisableForceEncryption_Treble.zip /sdcard
DisableForceEncryption_Treble.zip: 1 file pushed. 21.3 MB/s (4447302 bytes in 0.199s)
$ sudo adb push Magisk-v18.1.zip /sdcard
Magisk-v18.1.zip: 1 file pushed. 21.4 MB/s (4362466 bytes in 0.194s)
$ sudo adb push Magisk-uninstaller-20190204.zip /sdcard
Magisk-uninstaller-20190204.zip: 1 file pushed. 21.2 MB/s (2290127 bytes in 0.103s)​23/ go to main TWRP main menu then tap Install then tap beryllium-9.1.24-9.0-vendor-firmware.zip to install.
The vendor firmware must be installed prior to the ROM which relies on it.
If you forget this step, you will get a Updater process ended with ERROR: 7 error when trying to flash the ROM.
24/ go to main TWRP main menu then tap Install then tap PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL.zip to install.
25/ go to main TWRP menu then tap Install then tap DisableForceEncryption_Treble.zip to install.
DisableForceEncryption_Treble will prevent the ROM from auto encrypting your phone upon first initialization. It also install Magisk which will give you root access.
Note that you can skip this step if you want to keep your phone encrypted.
26/ go to main TWRP menu then tap Install then tap Magisk-uninstaller-20190204.zip to uninstall any existing version of Magisk. The DisableForceEncryption_Treble also installs Magisk 16.7 so this step is required for a proper removal.
27/ go to main TWRP menu then tap Install then tap Magisk-v18.1.zip to install.
28/ now, boot to System.
29/ If you installed DisableForceEncryption_Treble then your phone will initialize without encryption.
30/ you now have to link your Pixel OS phone to your Google account and install your apps.
YOU ARE ALL DONE
Congratulations !!! you now have a Pixel OS and rooted system installed on your Pocophone F1.
TROUBLESHOOTING
-------------------------
Before installing Pixel OS, I had hard times trying to flash LineageOS on my Pocophone F1.
For a reason, it corrupted the bootloader and ADB server stopped communicating with my computer.
I thought I bricked my phone but I successfully restored everything by following those steps:
1/ boot to TWRP by holding Volume Up & Power
2/ tap Wipe
3/ tap Advanced wipe
4/ check everything except USB-OTG then swipe to wipe all.
5/ hold Power button for a long time, the phone will then try to boot to System but fall back to FASTBOOT because we just erased the system partition at the previous step.
I advise that you follow exactly this procedure. I can't explain why but I first reboot to FASTBOOT from the TWRP menu but doing like this did not fix the ADB recovery server which still kept unresponsive after reflash.
6/ reflash TWRP by running again sudo fastboot flash recovery twrp-3.2.3-2-beryllium.img
7/ hold Volume Up & Power buttons to boot again to TWRP recovery.
8/ connect your phone to computer with USB cable.
9/ type adb devices and you will see your device again.

Cristobal2018 said:
$ adb push beryllium-8.11.7-9.0-vendor-firmware.zip /sdcard
beryllium-8.11.7-9.0-vendor-firmware.zip: 1 file pushed. 22.3 MB/s (402068528 bytes in 17.164s)​
Click to expand...
Click to collapse
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?​

kousarali said:
@Cristobal2018 After pushing the vendor-firmware zip to the sd card, we have to flash this zip in twrp before flashing the rom zip right?
Click to expand...
Click to collapse
You're absolutely right.
If you forget flashing the vendor firmware before PE, you'll get a system error 7 when trying to flash the PE ROM.
Many people encountered this error when this ROM was released.
I updated the tutorial.
Thanks!

Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy

neoonwheels said:
Do you have link for: beryllium-8.11.7-9.0-vendor-firmware.zip
Click to expand...
Click to collapse
The other way to find the link is searching Google for the MD5 or SHA256 signature.

Cristobal2018 said:
The other way to find the link is searching Google for the MD5 or SHA256 signature.
Click to expand...
Click to collapse
akashkyh said:
https://downloads.akhilnarang.me/MIUI/beryllium/
Enjoy
Click to expand...
Click to collapse
Thanks a lot guys.

I updated the guide with the official links to the packages.
The package names are now all clickable.

if i already installed disable force encryption zip during rooting procedure do i need to flash it again in step 27

Hi, even though i have flashed the vendor firmware, i got error 7 for pixel rom. I dont know what is the problem. I do wipe for all and flash vendor zip. But got error7 in pe Rom

Question
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance

Antidote03 said:
Guys should i flash vendor image
beryllium-8.11.7-9.0-vendor-firmware.zip
or
beryllium-V10.1.3.0-9.0-vendor-firmware.zip
device pocophone f1 unlocked rooted with magisk stock tell now
thanks in advance
Click to expand...
Click to collapse
I just tried to flash the latest PixelExperience_beryllium-9.0-20190205-2051-OFFICIAL and it raises a system error 7 complaining for the missing vendor 9.1 firmware.
According to the https://downloads.akhilnarang.me/MIUI/beryllium/ download page, you will notice that akhilnarang released vendor beryllium V10.1.3.0-9.0 vendor firmware a long time ago (december 2018).
Consequently, for flashing the latest PixelExperience ROM (20190205), I would advise to first flash vendor 9.1 available here: beryllium-9.1.24-9.0-vendor-firmware.zip

Is it really necessary to flash DFE (step 27)? Thank you.

Thank you so much for the comprehensive guide. I got my Poco F1 yesterday and I have a good idea what I need to do, but there's always some uncertainty.
DFE being the one question I have, but you explained it etc, so it looks like at this point it is recommended, but not necessary as such - if I understand.
Vendor firmware is another question mark for me, but it makes a bit more sense.
Right now, I am just going to look at rooting my phone, once I'm done with that I will start looking at custom ROMS.
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
I almost think that if it's just rooting via magisk you don't need to swipe right. since I don't think magisk touches system (but not sure).
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).

autisticarvin said:
Is it really necessary to flash DFE (step 27)? Thank you.
Click to expand...
Click to collapse
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.

Cristobal2018 said:
I suppose it is not necessary anymore with the latest official TWRP release.
I did it myself for 2 reasons : the 1st one is your phone runs much faster without encryption.
The 2nd one is I was not confident in the first TWRP releases which had issues with decryption.
I you root with encryption (~ with no DFE), I would be glad to have your feedback.
Click to expand...
Click to collapse
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.

autisticarvin said:
I have no plans in rooting my phone. Changing roms is enough for me. Btw, thank you.
Click to expand...
Click to collapse
Of course, I should have written 'flash' instead of 'root'

d.casper.b said:
One question, which I've not really seemed to find a concrete answer is regarding TWRP. Do you swipe right to allow system modifications?
Click to expand...
Click to collapse
Rooting allows the applications to run as root so the only requirements for doing it is having the root permissions. In recovery mode, TWRP already has the root permission so it should be enough.
I can't tell for sure because I did not test it but I would say as long as you don't require to write to the system partition, you don't have to swipe right. Magisk is not installed on the system partition so swiping should not be required.
d.casper.b said:
I was thinking to just boot TWRP and flash magisk (and not install TWRP). Then to uninstall root, boot TWRP and flash uninstall zip (maybe that will allow for easy OTA updates if on stock ROM?).
Click to expand...
Click to collapse
Installing TWRP while leaving the stock ROM installed is not a good idea.
Indeed, the stock MIUI performs an integrity test at boot time and it restores the stock ROM if a different one is found (like TWRP). At reboot, your TWRP will be overwritten with the stock one.

Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!

CobraStrike said:
Thanks for putting together such a comprehensive tutorial! I'm planning to do this with my Pocophone as soon as it comes in.
I'm a total newbie to this stuff, though... I noticed that half of your walk-through involves you using the Linux shell... If I only have access to Windows, can I use the same commands in the Windows Command Prompt or would that not get me anywhere?
Appreciate your work!
Click to expand...
Click to collapse
You can do this by using the ADB tools for Windows

[ROM][GSI] How to install Android 12 GSI with GApps

EDIT: Andy Yan updated his ROM to include GApps which makes this a lot easier.
ROM link: https://sourceforge.net/projects/andyyan-gsi/files/Testing/lineage-19.0-20211109-UNOFFICIAL-treble_arm64_bgS-personal.img.xz/download
Just follow this guide: https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/
Then skip to step 10 and continue in order to be able to use play store.
Sorry in advance for the confusing nature of this guide. I had no idea what was going on half the time. This is the result of me trying to get Android 12 to work for around 12 hours (mostly time spent reflashing system images after screwing something up).
I probably won’t link every single tool and define every term as I’m just trying to outline what to do and why. There are probably some unnecessary steps in here, but I have no idea which ones are unnecessary..
For the Android 12 GSI, I used Andy Yan’s (he’s a LineageOS Contributor) Lineage 19 personal build found here: https://sourceforge.net/projects/an...IAL-treble_arm64_bvS-personal.img.xz/download
Edit: that version has been deleted now and replaced with a version that doesn't work for me at least...
If you don’t care for installing gapps, this whole thing becomes a lot easier, just follow the instructions here (https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/) except with the above ROM.
If you do want to install gapps, there are quite a few extra steps. (Or maybe I’ve been doing it wrong the whole time)
Known bugs:
I keep getting a push notification that says “android system intelligence has stopped” but everything else works fine
Disabling app in settings fixes this
Carrier voice calls and SMS do not work (Google Voice/Whatsapp work fine)
Background:
The touchscreen in TWRP stopped working after the September 2018 software update, if you have an OTG adapter, you can still use a mouse.
TWRP is useful in expanding the system partition and installing gapps
the PH1 uses an A/B slots, we can keep an old August 2018 version on the B slot to work with TWRP and the new Android 12 GSI on the A slot
Step 1: Flash the August 2018 ROM onto the B slot
This ROM allows for TWRP to work with touch.
Download: https://sourceforge.net/projects/ma...st/PQ1A.190105.112-BACK-TO-STOCk.zip/download
Extract the folder, right click the file called “flashallwipe.bat” and edit it. Delete any lines with “fastboot flash” followed by something “_a” for example “fastboot flash nvdef_a nvdef” so that the only things remaining are the ones with “_b”s.
Once you’ve done that save the file.
Reboot your phone to the bootloader (hold power button + volume down or run “adb reboot bootloader” in the command prompt).
With your phone plugged in, run the edited “flashallwipe.bat” and wait
Step 2: Flash the October 2019 ROM onto the A slot:
This step might not be necessary, depending on what your current ROM is, however, if you have an older ROM, for example, the August 2018 ROM on the A slot, your touchscreen will stop working on the GSI, so its probably better just to do this just in case.
Download:
https://sourceforge.net/projects/ma...er/QP1A.190711.148-BACK-TO-STOCK.zip/download
Extract the file and do the same thing as the last step, except deleting the lines in “flashallwipe.bat” containing “_b” instead of “_a”.
Save the file, run it and wait.
Step 3: Flash stock AOSP onto the A slot:
The next thing you have to do is flash a stock AOSP ROM in order to disable verity.
Follow steps 1-6 of this guide: https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/
Step 4: Flash the Android 12 GSI onto the A slot:
Download and extract this: https://sourceforge.net/projects/an...IAL-treble_arm64_bvS-personal.img.xz/download
Edit: that version has been deleted now and replaced with a version that doesn't work for me at least...
and run
Code:
fastboot flash system_a lineage-19.0-20211029-UNOFFICIAL-treble_arm64_bvS-personal.img
fastboot format userdata
Step 5: Install TWRP onto the B slot:
Download: https://dl.twrp.me/mata/twrp-3.2.3-0-mata.img.html
Run:
Code:
fastboot set_active b
fastboot flash boot_b twrp-3.2.3-0-mata.img && fastboot reboot
Step 6: Switch slots within TWRP:
At this point you should have TWRP open. Press the “Reboot button” and at the bottom of the new page, click the “Slot A” button. Let it run. Do NOT reboot but go back to the home page.
Step 7: Expand System Partition within TWRP:
By default, the system partition is not large enough to install gapps.
Go to the “Wipe” button in TWRP, “Advanced wipe”, select “System”, then “Repair or change filesystem,” then finally, “resize filesystem”
Step 8: Install GAPPS
Right now, one of the only gapps packages available is NikGapps, downloadable here: https://nikgapps.com/downloads
Choose whichever package you want and download it.
Run: (replacing the zip file with ur filename)
Code:
adb push NikGapps-xxxx-xxxxx-xx-xxxxxxxx-signed.zip /sdcard
Within TWRP, click “Install” then your package, then slide to install.
Step 9: Boot into Android 12
Click the “Reboot” button in TWRP, then “System”
This is a part where I’m not 100% sure what happens. You might be able to directly go into Android 12, or it might make you factory wipe the data from your phone (doesn’t affect anything cause you don’t have anything on your phone yet). If it asks you to factory wipe, do that.
Edit: I think doing a standard cache/data wipe in TWRP after installing Gapps prevents bootlooping.
Step 10: Install Magisk
Once you get into Android 12, you pretty much won’t be able to do anything since, by default, the ROM is not Play Protect certified.
You will need to install Magisk and a few modules just do anything.
As of 11/6/21, you need the Canary version of Magisk to support Android 12
Download: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Open the app, install Magisk by patching the boot.img which was flashed in step 3, and flash the new boot image onto your A slot with:
Code:
fastboot flash boot_a magisk_patched-xxxxx_xxxx.img
Step 11: Configure Magisk
In order to have Google believe you are using a certified device, you have do make a few changes.
Open the Magisk App, and go to settings (top right), then scroll down and enable “Zygisk”
Go out of settings into modules and install MagiskHide Props Config
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases/tag/v6.1.1
SafetyNet doesn’t work yet (as of 11/6/21), the Universal SafetyNet Fix team is working on it with module v2.2.0 which is Patreon only right now.
Step 12: Configure props
Connect your phone to your computer, run
Code:
adb shell
su
Accept the prompt on your phone, then run
Code:
props
to set up the rest
Do “Edit device fingerprint” and maybe also “Force BASIC key attestation”
Setting both to Essential Phone PH-1 (Android 10) works fine.
Step 13: Certify your ROM
Follow the instructions on this page:
https://www.google.com/android/uncertified/
Step 14: Reboot and hopefully everything works!
If there are any extra steps which don’t need to be done or missing steps, please tell me in a comment!

Quantizr said:
EDIT: Andy Yan updated his ROM to include GApps which makes this a lot easier.
ROM link: https://sourceforge.net/projects/andyyan-gsi/files/Testing/lineage-19.0-20211109-UNOFFICIAL-treble_arm64_bgS-personal.img.xz/download
Just follow this guide: https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/
Then skip to step 10 and continue in order to be able to use play store.
Sorry in advance for the confusing nature of this guide. I had no idea what was going on half the time. This is the result of me trying to get Android 12 to work for around 12 hours (mostly time spent reflashing system images after screwing something up).
I probably won’t link every single tool and define every term as I’m just trying to outline what to do and why. There are probably some unnecessary steps in here, but I have no idea which ones are unnecessary..
For the Android 12 GSI, I used Andy Yan’s (he’s a LineageOS Contributor) Lineage 19 personal build found here: https://sourceforge.net/projects/an...IAL-treble_arm64_bvS-personal.img.xz/download
Edit: that version has been deleted now and replaced with a version that doesn't work for me at least...
If you don’t care for installing gapps, this whole thing becomes a lot easier, just follow the instructions here (https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/) except with the above ROM.
If you do want to install gapps, there are quite a few extra steps. (Or maybe I’ve been doing it wrong the whole time)
Known bugs:
I keep getting a push notification that says “android system intelligence has stopped” but everything else works fine
Disabling app in settings fixes this
Carrier voice calls and SMS do not work (Google Voice/Whatsapp work fine)
Background:
The touchscreen in TWRP stopped working after the September 2018 software update, if you have an OTG adapter, you can still use a mouse.
TWRP is useful in expanding the system partition and installing gapps
the PH1 uses an A/B slots, we can keep an old August 2018 version on the B slot to work with TWRP and the new Android 12 GSI on the A slot
Step 1: Flash the August 2018 ROM onto the B slot
This ROM allows for TWRP to work with touch.
Download: https://sourceforge.net/projects/ma...st/PQ1A.190105.112-BACK-TO-STOCk.zip/download
Extract the folder, right click the file called “flashallwipe.bat” and edit it. Delete any lines with “fastboot flash” followed by something “_a” for example “fastboot flash nvdef_a nvdef” so that the only things remaining are the ones with “_b”s.
Once you’ve done that save the file.
Reboot your phone to the bootloader (hold power button + volume down or run “adb reboot bootloader” in the command prompt).
With your phone plugged in, run the edited “flashallwipe.bat” and wait
Step 2: Flash the October 2019 ROM onto the A slot:
This step might not be necessary, depending on what your current ROM is, however, if you have an older ROM, for example, the August 2018 ROM on the A slot, your touchscreen will stop working on the GSI, so its probably better just to do this just in case.
Download:
https://sourceforge.net/projects/ma...er/QP1A.190711.148-BACK-TO-STOCK.zip/download
Extract the file and do the same thing as the last step, except deleting the lines in “flashallwipe.bat” containing “_b” instead of “_a”.
Save the file, run it and wait.
Step 3: Flash stock AOSP onto the A slot:
The next thing you have to do is flash a stock AOSP ROM in order to disable verity.
Follow steps 1-6 of this guide: https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/
Step 4: Flash the Android 12 GSI onto the A slot:
Download and extract this: https://sourceforge.net/projects/an...IAL-treble_arm64_bvS-personal.img.xz/download
Edit: that version has been deleted now and replaced with a version that doesn't work for me at least...
and run
Code:
fastboot flash system_a lineage-19.0-20211029-UNOFFICIAL-treble_arm64_bvS-personal.img
fastboot format userdata
Step 5: Install TWRP onto the B slot:
Download: https://dl.twrp.me/mata/twrp-3.2.3-0-mata.img.html
Run:
Code:
fastboot set_active b
fastboot flash boot_b twrp-3.2.3-0-mata.img && fastboot reboot
Step 6: Switch slots within TWRP:
At this point you should have TWRP open. Press the “Reboot button” and at the bottom of the new page, click the “Slot A” button. Let it run. Do NOT reboot but go back to the home page.
Step 7: Expand System Partition within TWRP:
By default, the system partition is not large enough to install gapps.
Go to the “Wipe” button in TWRP, “Advanced wipe”, select “System”, then “Repair or change filesystem,” then finally, “resize filesystem”
Step 8: Install GAPPS
Right now, one of the only gapps packages available is NikGapps, downloadable here: https://nikgapps.com/downloads
Choose whichever package you want and download it.
Run: (replacing the zip file with ur filename)
Code:
adb push NikGapps-xxxx-xxxxx-xx-xxxxxxxx-signed.zip /sdcard
Within TWRP, click “Install” then your package, then slide to install.
Step 9: Boot into Android 12
Click the “Reboot” button in TWRP, then “System”
This is a part where I’m not 100% sure what happens. You might be able to directly go into Android 12, or it might make you factory wipe the data from your phone (doesn’t affect anything cause you don’t have anything on your phone yet). If it asks you to factory wipe, do that.
Edit: I think doing a standard cache/data wipe in TWRP after installing Gapps prevents bootlooping.
Step 10: Install Magisk
Once you get into Android 12, you pretty much won’t be able to do anything since, by default, the ROM is not Play Protect certified.
You will need to install Magisk and a few modules just do anything.
As of 11/6/21, you need the Canary version of Magisk to support Android 12
Download: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Open the app, install Magisk by patching the boot.img which was flashed in step 3, and flash the new boot image onto your A slot with:
Code:
fastboot flash boot_a magisk_patched-xxxxx_xxxx.img
Step 11: Configure Magisk
In order to have Google believe you are using a certified device, you have do make a few changes.
Open the Magisk App, and go to settings (top right), then scroll down and enable “Zygisk”
Go out of settings into modules and install MagiskHide Props Config
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases/tag/v6.1.1
SafetyNet doesn’t work yet (as of 11/6/21), the Universal SafetyNet Fix team is working on it with module v2.2.0 which is Patreon only right now.
Step 12: Configure props
Connect your phone to your computer, run
Code:
adb shell
su
Accept the prompt on your phone, then run
Code:
props
to set up the rest
Do “Edit device fingerprint” and maybe also “Force BASIC key attestation”
Setting both to Essential Phone PH-1 (Android 10) works fine.
Step 13: Certify your ROM
Follow the instructions on this page:
https://www.google.com/android/uncertified/
Step 14: Reboot and hopefully everything works!
If there are any extra steps which don’t need to be done or missing steps, please tell me in a comment!
Click to expand...
Click to collapse
wILL THIS WORK WITH twrp? my device has download mode not have fastboot