Related
Hi!
Xperia ZXP was running the official Firmware fine. Then, I just decided to root. I followed this video:
Got my phone properly rooted.
Now I keep getting notification of an update that I had before but cannot install it. Also, I cannot setup my company work profile as it detects root.
I mainly wanted to use Cheat Engine that why I rooted.
How do I apply latest update?
How do I hide root status?
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Is there a place/page here that lists all these tools?
Fix after root effects
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Here is how I'm going step by step:
Download Flashtool - Done
latest version of Xperifirm - Done
Find latest firmware with Xperifirm. Should end in .107 - Done
-- Download it - Done
-- decrypt it with Flashtool - Stuck
Download Newflasher - Done
-- Unzip Newflasher into the folder you have the decrypted files
Plug your phone into your computer
-- Make sure you have the correct driver - Done
-- Developer option and usb debugging enabled on your phone - Done
Put phone into flash mode and hit newflasher.exe
-- choose "n" for the first two choices and let it run
-- That will give you the latest and final update for this phone
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Doomer D. Great said:
Here is how I'm going step by step:
• Download Flashtool - Done
• latest version of Xperifirm - Done
• Find latest firmware with Xperifirm. Should end in .107 - Done
○ Download it - Done
○ decrypt it with Flashtool - Stuck
• Download Newflasher - Done
○ Unzip Newflasher into the folder you have the decrypted files
• Plug your phone into your computer
○ Make sure you have the correct driver - Done
○ Developer option and usb debugging enabled on your phone - Done
• Put phone into flash mode and hit newflasher.exe
○ choose "n" for the first two choices and let it run
○ That will give you the latest and final update for this phone.
• Now use twrp to install the latest Magisk version(search online)
○ also have Magisk manager app(Play Store) on your phone
• Once that's done and you've rebooted phone
• open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
• If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Click to expand...
Click to collapse
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
bobsright said:
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
Click to expand...
Click to collapse
The latets Xperifirm also extract right after downloading so the decrypt step is not needed.
I'm flashing a I write. I'll be dealing with the next part now:
Now use twrp to install the latest Magisk version(search online)
also have Magisk manager app(Play Store) on your phone
Once that's done and you've rebooted phone
open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything
TWRP has to be flashed or installed from store?
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
bobsright said:
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
Click to expand...
Click to collapse
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Doomer D. Great said:
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Click to expand...
Click to collapse
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
bobsright said:
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
Click to expand...
Click to collapse
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Doomer D. Great said:
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Click to expand...
Click to collapse
So Cheat Engine doesn't detect root with Magisk?
bobsright said:
So Cheat Engine doesn't detect root with Magisk?
Click to expand...
Click to collapse
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Doomer D. Great said:
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Click to expand...
Click to collapse
Oh well, at least you got it updated and working. Maybe it'll take some searching somewhere else to get that other stuff worked out.
Just a side note; I used to work for Sheikh Hamdan bin Rashid Al Maktoum at his Throughbred operation in Lexington.
Excuse me, does anyone know how to root xz premium docomo ubl no ??? Now on Android 9 Pie, please help.
I believe the Japan market version can't have the bootloader unlocked, thus, no root.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ1A.210205.004, Feb 2021"!
Magisk v21.4 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145727319
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145727317
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145727318
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.210105.003, Jan 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.210105.003-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145709335
coral-rq1a.210105.003-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145709334
February 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq1a.210205.004-8fe8685c.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.210105.003-factory-boot.img
3. fastboot flash dtbo coral-rq1a.210105.003-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq1a.210205.004-8fe8685c.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq1a.210205.004-magisk_patched-21.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
** As of newer Magisk builds, you can just try booting up in safe mode, which should disable Magisk and allow you to disable whatever needs to be disabled. Haven't needed to try it yet, so I can't go into more detail, but I would recommend trying that instead.
thank you for prompt updates! I use your guide and files every time
Used your files and it worked without a problem. Thank you very much
this method no longer works after i use a new windows installation. All seems normal except phone gets stuck in "Phone is starting" and i have to format userdata for it to work again.
It was working previously and i use the same magisk modules. Ill try from ubuntu next month
Maybe someone could know whats causing the issue because i did not missflash anything and all files were downloaded properly. Im pretty sure its windows but who knows lol
fuarkgl3 said:
this method no longer works after i use a new windows installation. All seems normal except phone gets stuck in "Phone is starting" and i have to format userdata for it to work again.
It was working previously and i use the same magisk modules. Ill try from ubuntu next month
Maybe someone could know whats causing the issue because i did not missflash anything and all files were downloaded properly. Im pretty sure its windows but who knows lol
Click to expand...
Click to collapse
I would check that you're using latest adb / fastboot (Google's Android SDK platform tools) and Google USB drivers, and that when your phone is in bootloader mode and plugged in, Windows' Device Manager shows it as the correct type of device (Portable Devices -> Pixel 4 XL). You may need to update drivers and manually install the Google USB driver package over that device.
Also, maybe bad download, try another cable, etc the usual stuff. And sorry for the late response. =)
edit: oh, and also you can get conflicts if you have other adb / fastboot sets installed. For example, the "minimal adb fastboot" package, or HTC Sync Manager, they may install their own adb / fastboot binaries and set their paths into your environment variables. I know you said new Windows installation, but I figured it was worth mentioning anyway.
So I can do all this just fine, my issue is I can't pass safetynet and I feel like I'm missing something simple. Anyone care to writeup or point me in the direction explaining to a 5 year old (well, one born 40 years ago) how to do the magiskhide deal today? My bank apps and everything work - except for hulu (so even just a modded apk would do.
No need for MagiskHidePropsConfig anymore. Just flash this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.1.1
If you have Xposed installed, you'll have to make sure to enable pass safetynet mode (basically just blacklists certain Google apps from Xposed hooking).
Thanks again @i5lee8bit for this guide!
I updated to the latest February patch alllll the way from Android 10, August 2020 security patch!
It took a couple of hours but everything went smoothly.
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
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.
So I've had the oneplus 7 pro 5g for over 2 years now, stuck on android 10. Here in the UK, EE dropped support for the phone so no updates past what I've got installed. I understand that non-5g variant roms can't be flashed to the 5g version. I came across YAAP on telegram but there were no proper installation instructions for the 5g version so I decided against trying to install it.
Are there ROMs available for this variant? Or is there anyone that can link me to a proper guide to installing YAAP?
Thanks in advance.
the instructions are in the chat
Before starting, download these files on your computer to save time
Download your custom rom choice from #5g-custom-roms-latest
Download the latest EU5G OTA from here (https://otafsg-cost.h2os.com/OnePlu....E.31_OTA_031_all_2111271509_64912a56fefe.zip)
Have drivers and ADB/fastboot (platform-tools) (https://developer.android.com/studio/releases/platform-tools) ready (#drivers if you don't have them)
1. Use MSMDownloadTool to convert to EU5G firmware. (If you’re on Sprint, I would use EU5G due to the ease of unlocking bootloader and local upgrading)
2. Set up the device on Android 9, and move the EU5G OTA zip file from your computer onto your phone (do not put it in a folder, just in internal storage)
3. Go to System Updater, click the gear icon, and local upgrade to the latest EU5G version (Start here if you’re already on EU5G, but on OOS 9)
4. Once you boot back into system, go back to the System Updater, and local upgrade to the same version again (this is because the 7 Pro 5G uses A/B and has 2 slots for updates. You need OOS 10 on both before flashing a rom) (start here if you’re on EU5G OOS 10)
5. Once you reboot back into system tick OEM Unlocking in Developer Options, reboot into bootloader by typing adb reboot bootloader (if USB debugging enabled) or powering off the device and pressing both volume and turning the device on. Now you can unlock the boot loader by typing fastboot oem unlock. Once it’s unlocked and reset, you can reboot back into boot loader and continue.
YAAP/YAAP Vanilla Flash
6. Get boot.img from @yaapop7 with the command #dumped_images (use guacS latest image)
7. In bootloader, fastboot flash boot boot.img (boot.img being guacamoles boot.img) (you can drag in the YAAP file into the terminal/CMD window and it'll auto populate file location)
8. On your device, use volume buttons to reboot to recovery, then once in YAAP recovery, select "Apply Update from ADB" or something related to ADB
9. On your PC, type ADB sideload YAAP.zip (yaap.zip being YAAP zip file) (you can drag in the YAAP file into the terminal/CMD window and it'll auto populate file location)
10. Once that finishes, format in recovery and reboot.
You should be done!
KOSP/Flamingo Flash
6. On your terminal window with fastboot, type fastboot update --skip-reboot rom.zip (rom.zip is the KOSP img release, you can drag the file into the window and it’ll auto fill the location)
7. Once this finishes, on your phone use the volume keys to reboot to recovery
8. Once in recovery, wipe data and reboot.
You should be done!
If you want Magisk
1. Setup your rom
2. Download Magisk.apk from the Magisk GitHub (https://github.com/topjohnwu/Magisk)
3. Move the boot.img from your rom of choice into your phone's internal storage (the YAAP one is the same one you used to install, the KOSP one is linked in the rom posts in @op7pro5gupdates)
4. In the Magisk app, hit install under Magisk and select “Select and patch a file”, then select the boot.img
5. The Magisk patched boot.img will be in your phone’s Downloads folder, so move it to your PC
6. Now back in your fastboot terminal window, type fastboot flash boot magiskboot.img (magiskboot.img is whatever it’s named, you can drag the file into the window and it’ll auto fill the location)
Passing SafetyNet with Magisk (and possibly some apps that detect root)
1. Once you have Magisk installed, and are back into the system, open Magisk, and if it prompts you to reboot for additional setup, do so.
2. Click the gear icon in the top right corner, then enable “Zygisk” and click on “Hide the Magisk app” (this will change the Magisk app icon and package name to “Settings” if you kept it at default)
3. Reopen Magisk, hit “Enforce DenyList” and “Configure DenyList”
4. Hit the 3 dots in the top right corner and “Show System Apps”
5. Search for “Google P” and click on the Google Play services app (not the check mark), hit com.google.android.gms and com.google.android.gms.unstable. Also click on the Play Store.
6. If you have any apps that detect root, select those as well (like Google Pay, Pokemon GO, and some banking apps), otherwise, you are done!
Some apps will still detect root!
Refer to #l1 for Netflix
OnePlus 7 Pro 5G - GM1925/GM1920
The OnePlus 7 Pro 5G (GM1920 and GM1925) chatroom!
t.me
if you have the GM1920 than I'm pretty sure you need to downgrade to OOS9, bootloader unlock, than flash YAAP feel free to ask any questions on telegram, also they would know more about the GM1920. I have the GM1925, I'll be happy to help