Database Info

Root and pixel gestures on your android P dp3

Here is correct way to root your android P developers preview builds for one plus 6 without bricking anything and also enable pixel navigation gestures.
This is video guide for tutorial for easy uder standing
https://youtu.be/fwwZXQ9cn1w
Download :
1) twrp 3.2.1.0 img file(poot it on any folder on computer and rename it to simple twrp. Img) donts use any version except this.
https://dl.twrp.me/enchilada/twrp-3.2.1-0-enchilada.img.html
2)download magisk 16.7 zip and twrp 3.2.1.0 installer zip and olace them on sd card of one plus 6( use only this magisk version)
https://forum.xda-developers.com/ap...systemless-t3473445/post77108384#post77108384
Now boot your phone in fastboot mode using volume up and power long press
Connect phone to computer
No click shift+mouse right click and select open command frompt here vua drop down menu
Then type these commands.
Fastboot devices enter
Fastboot boot twrp.img
Then your phone will boot in twrp in twrp flash twrp installer first then flash magisk 16.7
Then reboot.
2) enabling pixel gestures :
Fisrt enable usb debugging via developers option
Then connect device via cable to computer.
Then type and enter these commands
adb devices
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
Now reboot your phone
Go to button and gestures in setting and enable fixed navigation bar.
Thats it

After the command to enable the gestures my phone keeps telling me ''Oneplus launcher has stopped'' when trying to use it

tristanva said:
After the command to enable the gestures my phone keeps telling me ''Oneplus launcher has stopped'' when trying to use it
Click to expand...
Click to collapse
It it will happen for few sec then it works as normal. Or you can clear data for laungher and see

[Guide][EdXposed][GPay] Discussion

Get Edxposed, Magisk, and GPay to work together.
1. Install or make sure you are on latest Magisk Manger (7.5.1 or newer)
2. Install or make sure you are on latest Magisk (20.3 or newer)
3. Hide the following in Magisk Hide
-Google Pay
-Google Play services, only select the following
-com.google.android.gms
-com.google.android.gms.unstable​-Google Play Services for AR
-Google Play Store, select everything but com.android.vending
-Google Services Framework
-Nfc Service​
4. Install the following modules
-GPay SQLite Fix (Full Edition)
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176​-SQLite for Arm aarch64 devices via Magisk Manager
-hardwareoff by @Displax (Thanks to @Kris Chen for making me aware of it) or use MagiskHide Props to set check to basic and fingerprint to Pixel 3a​
5. Reboot
At this point make sure you have GPay working before installing edxposed. If for some reason you are unable to use GPay try deleting data for Google Play Services/Google Play Store/Google Pay
After you confirm that GPay is working then move on to installing edxposed
1. Download and install Riru - Core via Magisk Manager
2. Download Edxposed Manager (4.5.4 or newer) (Don't Install Yet!)
https://github.com/ElderDrivers/EdXposedManager/releases/​3. Download Edxposed (4563) (Don't Install Yet!)
I'm personally using the YAHFA version.
https://ci.appveyor.com/project/ElderDrivers/edxposed/history​
4. Once you have all these files downloaded turn on Airplane Mode and install the Edxposed Magisk Module (Magisk -> Modules and press the + sign, find the downloaded zip and select it, Magisk will install it) and Edxposed Manager APK and reboot
5. Once booted up remain in Airplane Mode
6. Open Edxposed Manger and go to Settings and turn on "App List mode"
7. Exit and reopen Edxposed Manager
8. Go to Applications on the side menu (should say "Black List" on top) and select the following apps
-Google Pay (may not be needed)
-com.android.nfc.auto_generated_rro_product_
-com.android.nfc.auto_generated_rro_vendor_
-Nfc Service
-pixelnfc (new in Android 11)​9. Go to Settings on the side menu, at the bottom of settings find and enabled "Pass SafetyNet"
10. Reboot and turn off Airplane Mode
11. Optional* Hide Magisk Manager
Note. Steps 4-9 should be done in Airplane Mode, this will keep anything tripping safety net during the setup process.

eg1122 said:
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Click to expand...
Click to collapse
Here are some screen shots of it working

Thanks for this @eg1122.
After soft-bricking on my first try, I've been wondering what the working version combination is.

The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Sent from my Pixel 4 XL using Tapatalk
View attachment 4858559

Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Sent from my Pixel 4 XL using Tapatalk

xdeslitx said:
Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Click to expand...
Click to collapse
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687

xdeslitx said:
The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Click to expand...
Click to collapse
Use the link I posted to get 0.4.5.5

eg1122 said:
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687
Click to expand...
Click to collapse
That looks pretty nice...thanks
Sent from my Pixel 4 XL using Tapatalk

eg1122 said:
I've been reading a lot of our forums and many are asking about Xposed. Decided to make this thread to try to keep all discussion in one place and make it easy to find information.
I am currently running Xposed and I'll lay out the steps I took to get it working.
1. In Magisk Manager find and install Riru - Core v19.5
2. Reboot
3. Download and install Riru - EdXposed v0.4.5.5_beta (YAHFA) via Magisk
https://github.com/ElderDrivers/EdXposed/pull/354
4. Install EdXposed Installer
https://github.com/solohsu/XposedIn...d_v2.2.5/EdXposedInstaller_v2.2.5-release.apk
5. Reboot
6. Enjoy
Click to expand...
Click to collapse
This won't trip Safety net right i assume?

varun.gid said:
This won't trip Safety net right i assume?
Click to expand...
Click to collapse
Nope

Disregard...

How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.

Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?

gettinwicked said:
How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.
Click to expand...
Click to collapse
I disable big modules like Xposed when I update. Then re-enable them once update is completed. I'll put a step by step here.
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557

tardis_42 said:
Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?
Click to expand...
Click to collapse
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up

eg1122 said:
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up
Click to expand...
Click to collapse
Clearing data did it, thanks!

How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.

madgooner2810 said:
How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.
Click to expand...
Click to collapse
In Magisk, go to Modules and press the + button, then find the zip and select it.

Thanks...
FYI, Riru - EdXposed v0.4.6.0_beta (YAHFA) via Magisk also works.

@eg1122 great instructions worked perfectly. Thanks!

ZTE Blade 10 prime root possible?

Is it possible to root the blade 10 prime?
I couldn't find a suitable forum thread for it, so sorry if this is the wrong place. If it's the wrong place, is there somewhere I should post this question instead?

https://forum.xda-developers.com/an...atek-armv8-t3922213/post82081703#post82081703
I will be trying this either this evening or Saturday. I can report back. If it works it won't let you do everything since no unlocked bootloader but will be good for many other things.

This worked for me:
1.) Download/Install App https://github.com/JunioJsv/mtk-e...v1.1.0.ap k
2.) Open app, toggle Run on boot, and Select Magisk zip (shouldn't matter which one; I went with 20.4).
3.) Wait a few seconds for it to install. When it asks you to reboot, do so.
4.) On reboot, open Magisk and update if asked.
5.) Once Magisk is fully installed, go back to MTK Easy Su app.
6.) Tap Activate Bootless Root.
Now I'm just looking for an ad blocker as adaway doesn't work.

460cidpower said:
This worked for me:
1.) Download/Install App https://github.com/JunioJsv/mtk-e...v1.1.0.ap k
2.) Open app, toggle Run on boot, and Select Magisk zip (shouldn't matter which one; I went with 20.4).
3.) Wait a few seconds for it to install. When it asks you to reboot, do so.
4.) On reboot, open Magisk and update if asked.
5.) Once Magisk is fully installed, go back to MTK Easy Su app.
6.) Tap Activate Bootless Root.
Now I'm just looking for an ad blocker as adaway doesn't work.
Click to expand...
Click to collapse
Oh nice. I'll try this method later then. Also, have you tried Energized Protection on Magisk?

460cidpower said:
This worked for me:
1.) Download/Install App https://github.com/JunioJsv/mtk-e...v1.1.0.ap k
2.) Open app, toggle Run on boot, and Select Magisk zip (shouldn't matter which one; I went with 20.4).
3.) Wait a few seconds for it to install. When it asks you to reboot, do so.
4.) On reboot, open Magisk and update if asked.
5.) Once Magisk is fully installed, go back to MTK Easy Su app.
6.) Tap Activate Bootless Root.
Now I'm just looking for an ad blocker as adaway doesn't work.
Click to expand...
Click to collapse
Got my root working and got Adaway and AFWall+ running. Make sure in Magisk you have enable Systemless hosts under Magisk Manager settings. Then in Adaway make sure you go into preferences and check Enable systemless mode.

That worked for me! Thanks a lot!

460cidpower said:
This worked for me:
1.) Download/Install App https://github.com/JunioJsv/mtk-e...v1.1.0.ap k
2.) Open app, toggle Run on boot, and Select Magisk zip (shouldn't matter which one; I went with 20.4).
3.) Wait a few seconds for it to install. When it asks you to reboot, do so.
4.) On reboot, open Magisk and update if asked.
5.) Once Magisk is fully installed, go back to MTK Easy Su app.
6.) Tap Activate Bootless Root.
Now I'm just looking for an ad blocker as adaway doesn't work.
Click to expand...
Click to collapse
460cidpower said:
That worked for me! Thanks a lot!
Click to expand...
Click to collapse
No problem. Thanks for sharing that easy root method. If this Blade Prime 10 ever somehow gets full root or bootloader unlock it'll be an amazing phone. Already pretty great, especially since I got it for $25.

I know it's old thread but you can unlock the bootloader and root it with magisk via rom2box.
How to Root ZTE Blade 11 Prime - ROM-Provider
step by step guide to root ZTE Blade 11 Prime, after rooting the phone you can install any custom rom like lineage OS
romprovider.com
Follow the rom2box ZTE blaze 11 prime except from flashing both magisk patched boot.img (blade 10 prime have a/b slots) and vbmeta,.img (rom2box can't find it) . If you do flash magisk batch boot.img, it will prevent the phone from booting up (can't verify). Just flash the stock boot.img from rom2box output folder. and reboot
To bypass the boot verification, you need to unlock the bootloader. You need to go back into rom2box, mediatek>service! tab and try each buttons (format first, unlock method 1, method 2). This will unlock bootloader and now you can flash the patched magisk via rom2box firmware flashers. You might need to reboot it into edl multiple times to completely flash the boot.img.

[Tutorial] Unlock Bootloader, get root and valid Safetynet

04/09/21 v2​Just install this Module via magisk manager:
https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/
which is mentioned by this thread:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
You need it + safetynetfix from kdrag0n then you have valid safetynet.
04/09/21​For the last two days there has been an update on Google's site that causes Safetynet to fail on your phone. It didn't work on my phone and a colleague's phone, but it worked on another colleague's phone with no problems. So it may or may not fail on your end.
If you have the problem with safetynet failing. First update magisk to v.23 and the manager to the latest version.
Then we need lsposed with a separate module for lsposed. You can use edxposed, but for most users it laggs much more than lsposed.
If you don't have lsposed. You need to install the following two Magisk modules in the order described.
1. riru
2. riru - LSposed
Otherwise you will get an installation error because the core is missing.
After the installation, restart the phone.
Then the LSposed manager should be visible in your launcher. If not, download the full zip package from here:
Releases · LSPosed/LSPosed
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Extract the manager.apk from it and install it.
Inside the manager, you should get a green message with "activated". If not, you have not installed the module.
Inside the Lsposed manager, install the XprivacyLua module from the repo. The search function is located at the bottom.
Go to Modules and click on XprivacyLua. And tick the two items for the recommended applications:
System Framework
settings storage
Then click on the 3 dots at the top right.
There, uncheck the item in "Hide -> System apps".
Now you can search in the app list for
Google play Services and set the hook.
Then click on the gear icon on the top right and the app XprivacyLua will open.
In it, search for Google play Services again and set the checkmark next to the gear icon so that each sub-checkmark is set.
Now we need to hide the Magisk Manager. To do this, open the Magisk Manager.
Click on the gear icon at the top right of the main menu. Then click on hide magisk manager. Enter the desired name and wait until the Magisk Manager opens again.
If you have not installed the Safetynet fix from kdrag0n, you can download it here:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Then install it from the "modules" menu in magisk manager using the "install module from storage" function.
Once you have installed the Safetynet Fix module, restart the phone.
Then open the Settings app and navigate to the Apps section. Then search for Google Play Services, open it and in the storage option, use the function to clear the cache memory.
Now you can check Safetynet again in Magisk and it should be valid.
19/04/21:​There is currently a problem with magisk checking safetynet. When you check safetynet in magisk, you get a safetynet API error. Either use an alternative Safetynet app e.g. Safetynet Test or install the magisk canary app. I heard it was fixed there, but don't know for sure.​
SafetyNet Test - Apps on Google Play
SafetyNet device compatibility test
play.google.com
I wrote this entire tutorial already in this Thread, but I think it should be separated, so everyone can find it easier:
https://forum.xda-developers.com/showpost.php?p=83736713&postcount=89
This Tutorial descripes 3 Points:
Unlock Bootloader - which is necessary for root
Get root via Magisk
Valid Safetynet
Enable Developer mode in settings
Open Settings App
Move to About The Phone
7 Taps on the Build-Number
Enable OEM-Unlock in settings
Go back to Main Menu of Settings
move to system
Unfold Extended
Open Developer options
Enable OEM-Unlock
If you go further, you should either have a clean phone or backup your data. Because if you unlock the bootloader, the entire phone will be wiped.
Reboot Phone in Fastboot
Turn off Phone with long press on Power Button and click turn off
Press Power Button + Lower Volume together for some seconds and you are in fastboot mode
Use Fastboot to unlock Phone
If you don't have it download at first the needed adb and fastboot files for your system:
https://developer.android.com/studio/releases/platform-tools
Extract it to a path where you want it.
Connect your P5 with your PC with an USB cable
Open the path where you have extracted the adb tools.
On Windows press Shift + Right click and in the context menu click on open commandline Window
If you enter the following console command you should see an listed device about it's serial number:
Code:
fastboot devices
If you get an empty result, you have to check if P5 is correct connected via usb and p5 is in fastboot mode (you see it onscreen)
It could be that you have to install the usb drivers at first for recognizing it via fastboot.
If a Serial was listed in the Previous step, go further.
Enter the following command to start to unlocking your phone
Code:
fastboot flashing unlock
On your Phone you see a message to "not unlock your phone", with volume up you switch it to "unlock your phone". With the Power Button you accept it.
It will reboot now and at this moment it wipes the entire phone, so you start again from scratch to configure the p5.
if you have a Pixel 5 without the KDDI Version, you can use the following boot image, which is already a prepatched boot image including magisk 21 (Build 21005).
Download it at first:
http://www.mediafire.com/file/8ll4mlzt3l9njph/magisk_patched+Build+21005.img/file
KDDI variant: http://www.mediafire.com/file/widag4w5s02itq5/magisk_patched+KDDI.img/file
Copy the img-file to the path where you had extracted the adb files.
After you have configured your phone so you can use it, turn off p5 again and go again into fastboot mode.
Ensure your phone is connected via usb to the PC.
In the opened command line Window enter the following command:
Code:
fastboot flash boot "magisk_patched Build 21005.img"
For windows powershell Users check this out, if the above command failed:
cubandanger05 said:
A suggestion, please add that those having issues with the flash command failing to WRITE can try putting ./ before the command and that should work.
morpheus620 said:
hm not working for me. P5 is unlocked.
C:\>fastboot flash boot "magisk_patched Build 21005.img"
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.419s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.500s
Click to expand...
Click to collapse
Do:
./fastboot flash boot "magisk_patched Build 21005.img"
Click to expand...
Click to collapse
After it finished you can reboot your phone into android system and you will see the magisk manager logo.
Open it and you should see magisk 21005 is installed, then you know root access is granted.
For Safetynet you have to do the following steps
In Magisk Manager open settings gear.
under Magisk enable MagiskHide
Above MagiskHide is a menupoint called "Hide Magisk Manager", click on it, give the magisk manager a new name, click ok and wait until it's reopend.
Go to main menu of the magisk manager. On bottom is a "shield icon" open it.
Go to "MagiskHide"
On Top is the item "Google Play Services" unfold it and set every hook on it.
It's recommended to set the hook on every google Service you find.
Go Back to main menu of magisk manager
Download the latest universal safetynet fix for your P5:
Release v2.4.0 · kdrag0n/safetynet-fix
Highlights Play Integrity bypass without breaking device checks or causing other issues Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109) Other changes Updated instruc...
github.com
Then in magisk manager under modules click on the "Install from memory" button and then select the zip file you just downloaded and magisk manager will then install the module.
After finished installation reboot your P5.
After reboot check safetynet state in Magisk Manger, it should be OK.
Now you have a rooted phone and a valid safetynet.

This post describes how to patch magisk to a new firmware as long as no twrp recovery is available:
At first download the specific rom:
https://developers.google.com/android/images
You need only the "Link". Flash is only for flashing the rom over an chromium browser.
After downloaded the zip file open it, and you find another zip file. This zip file has to be extracted.
Into the extracted zip is the file boot.img, extract it.
Copy the boot.img to your p5 by usb.
Install the last magisk manager Canary version on your p5:
https://github.com/topjohnwu/Magisk
Open magisk manager. In main menu click on install. In the new menu click on "select a file and patch it". Search for the copied boot.img on your p5 and select it.
Wait for flash completion. And check if it's successful.
Copy the file /sdcard/download/magisk_patched.img to your pc in the adb files directory.
If you on the step to flash the boot image, you have to use the new file name.

Great write up, It will help many. As for me, it will make a nice reference to ADB.
Sent from my Pixel 3a XL using Tapatalk

flashing img doesn't work
Hi,
I tried it exactly as written here:
In the opened command line Window enter the following command:
Code:
fastboot flash boot "magisk_patched Build 21005.img"
After it finished you can reboot your phone into android system and you will see the magisk manager logo.
Somehow flashing the img does not work for me.
Terminal output:
❯ fastboot flash boot "boot.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.480s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 1.152s
Even though the output on the terminal looks fine. At least it doesn't give me an error.
Tried installing magisk manually and flashing the img through the app, but that gave me an error:
!installation failed
-repacking boot image
!Unable to repack boot image
Ahh and btw I'm based in germany so I guess I have to use the non KDDI version.
Appreciate the help
Cina

What is the KDDI-Version?
Thanks for your tutorial

Thanks alot for this!!! This will be the first thing I do when I get my Pixel 5

Sh0X31 said:
What is the KDDI-Version?
Thanks for your tutorial
Click to expand...
Click to collapse
As far as I understood it, it's the japanese version...

Yup KDDI its a Japanese telecoms company, and that version is specially built for them.

I tried it exactly as written here:
In the opened command line Window enter the following command:
Code:
fastboot flash boot "magisk_patched Build 21005.img"
After it finished you can reboot your phone into android system and you will see the magisk manager logo.
Somehow flashing the img does not work for me.
Terminal output:
❯ fastboot flash boot "boot.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.480s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 1.152s
Even though the output on the terminal looks fine. At least it doesn't give me an error.
Click to expand...
Click to collapse
Same here
I tried all ways thrice and then again
It is not that difficult, usually.
But Magisk Manager says Installed N/A
Thanks for any idea
edit:
I set up everything again on another computer.
Patched the boot.img myself with the MM Canary version
and then it worked.
Looks like my other PC has an unknown problem

Thanks <3
But will it be possible to have the phone identified as P5 instead of P3a in the future?
A bit scared of doing this.

Frost Storm said:
Same here
I tried all ways thrice and then again
It is not that difficult, usually.
But Magisk Manager says Installed N/A
Thanks for any idea
Click to expand...
Click to collapse
Are you sure you are on the correct boot.img ? i have a pixel 5 from a french carrier and the build number is the same as the "KDDI" version but i'm pretty sure my phone has nothing to do with japanese telecoms.

Great! thanks

SOSODU13016 said:
Are you sure you are on the correct boot.img ? i have a pixel 5 from a french carrier and the build number is the same as the "KDDI" version but i'm pretty sure my phone has nothing to do with japanese telecoms.
Click to expand...
Click to collapse
Yes, I can second this. Looks like a lot of devices shipped to Europe are indeed preloaded with the KDDI version. I contacted Google support about this to better understand, awaiting their response.

Hecke92 said:
Thanks <3
But will it be possible to have the phone identified as P5 instead of P3a in the future?
A bit scared of doing this.
Click to expand...
Click to collapse
I went back and done it again and changed it to original and now got Nexus 5 and still works Nexus is better then 3a lol

jaythenut said:
I went back and done it again and changed it to original and now got Nexus 5 and still works Nexus is better then 3a lol
Click to expand...
Click to collapse
You can have issues on Playstore ( no compatibel apps on your device) by using Nexus

cultofluna said:
You can have issues on Playstore ( no compatibel apps on your device) by using Nexus
Click to expand...
Click to collapse
All good so far but will keep my eye on it thanks

cultofluna said:
You can have issues on Playstore ( no compatibel apps on your device) by using Nexus
Click to expand...
Click to collapse
Is it possible to have this fixed in the future? So that we don't have to change the identity?

Hecke92 said:
Is it possible to have this fixed in the future? So that we don't have to change the identity?
Click to expand...
Click to collapse
I won't think so if we can use the p5 fingerprint to get valid safety net. Because we have to switch from basic authentication to hardware key. AFAIK if the hardware method is used, the hardware sensor can check if bootloader is unlocked and give the results to the safety net validator. And you will get automatically false cts profile if the hardware sensor detect that your bootloader is open.
This is a very interesting question about rooting and using custom roms in the future when no other device with newer android version use basic authentication.

2 + Enter
f + Enter
7 + Enter
20 + Enter
y + Enter
y + Enter
Click to expand...
Click to collapse
This I type in adb shell or terminal on Android. But what they do?

Sh0X31 said:
This I type in adb shell or terminal on Android. But what they do?
Click to expand...
Click to collapse
If you had entered "props" in adb shell you see a menu which is navigated by key inputs. The code section you mentioned are for navigating through the props menu to get the specific p3a fingerprint on basic authentication activated on your phone including reboot.

Question Trying to root my Moto Stylus 5G XT2131-1 without TWRP, how did you guys root this phone? How did you get the boot.img file?

I have seen some of you guys successfully rooted this phone. How did you do that since TWRP doesn't have this model yet. I heard that I need to have the boot.img file but I don't even know where to get that. Please help me in getting that. Thank you.

First unlock your bootloader, I don't remember the exact procedure but there's a toggle in developer options, and a website you have to use, this also requires resetting your phone unfortunately
After that, get the Motorola (Lenovo) smart assistant from support.motorola.com, and "rescue" your device,
This is done for a few reasons, 1. It downloads the boot.img you need, and 2. it updates your phone, this is important because you can't do system updates anymore.
Once it's "rescued", install the magisk apk, copy the boot.img from C:\ProgramData\RSA\ROM Files\etc to your phone, use the magisk app to patch it, and it will create a patched file
Then download and extract the android sdk platform tools (fastboot/adb), and copy the patched boot.img to that folder
Plug your phone in and put it in bootloader mode (same as the rescue required, Vol - & plug in)
Then "fastboot flash boot patched_boot.img"
This is possible without all of this, using some third party website that collects firmware files, but I prefer this way because I want to make sure I have the latest updates, having an update popup every time I turn my screen on is very annoying.
Also a tip, when you set your phone up, make sure you turn off any auto updating when it asks you, and turn it off in developer options too, if you never check for updates automatically or manually it will never know there's updates to apply and never annoy you, to update you'd have to do another rescue and patch/flash
Smart assistant is also how you unbrick, if you happen to do that like I did with some random commands for a different phone

ShayBox said:
First unlock your bootloader, I don't remember the exact procedure but there's a toggle in developer options, and a website you have to use, this also requires resetting your phone unfortunately
After that, get the Motorola (Lenovo) smart assistant from support.motorola.com, and "rescue" your device,
This is done for a few reasons, 1. It downloads the boot.img you need, and 2. it updates your phone, this is important because you can't do system updates anymore.
Once it's "rescued", install the magisk apk, copy the boot.img from C:\ProgramData\RSA\ROM Files\etc to your phone, use the magisk app to patch it, and it will create a patched file
Then download and extract the android sdk platform tools (fastboot/adb), and copy the patched boot.img to that folder
Plug your phone in and put it in bootloader mode (same as the rescue required, Vol - & plug in)
Then "fastboot flash boot patched_boot.img"
This is possible without all of this, using some third party website that collects firmware files, but I prefer this way because I want to make sure I have the latest updates, having an update popup every time I turn my screen on is very annoying.
Also a tip, when you set your phone up, make sure you turn off any auto updating when it asks you, and turn it off in developer options too, if you never check for updates automatically or manually it will never know there's updates to apply and never annoy you, to update you'd have to do another rescue and patch/flash
Click to expand...
Click to collapse
Thank you for that detailed response. I was reading some posts on here and some people are saying that rooting this phone isn't a full root since they are not able to go Read/Write, is that true? Should I just wait indefinitely for a TWRP root?

cwgzz said:
Thank you for that detailed response. I was reading some posts on here and some people are saying that rooting this phone isn't a full root since they are not able to go Read/Write, is that true? Should I just wait indefinitely for a TWRP root?
Click to expand...
Click to collapse
This is true, and depending on what you want to do with root that may be a deal breaker, but I don't care for changing boot animation and stuff, I haven't run into any problems with read only system, root still works just fine, magisk modules work, etc

ShayBox said:
This is true, and depending on what you want to do with root that may be a deal breaker, but I don't care for changing boot animation and stuff, I haven't run into any problems with read only system, root still works just fine, magisk modules work, etc
Click to expand...
Click to collapse
What exactly is that though? To be able to Read/Write? I basically want to root my device so I can change the language of certain apps and not all apps and I need Xposed or something in order to do that. Also, I want to be able to change my location withouth having to use "mock location" under the developer settings.

cwgzz said:
What exactly is that though? To be able to Read/Write? I basically want to root my device so I can change the language of certain apps and not all apps and I need Xposed or something in order to do that. Also, I want to be able to change my location withouth having to use "mock location" under the developer settings.
Click to expand...
Click to collapse
I don't know anything about fake locations, I've only ever used mock location a couple times
To get xposed afaik you get the Riru and Riru - LSPosed magisk modules, reboot and you get an LSPosed shortcut, which is your xposed control that lets you manage your xposed modules
For adblock, adaway works great, for theming you can get substratum (not substratum lite) from the playstore, and themes from the playstore, that works off a substratum magisk module and will theme the entire UI
If you need busybox for anything get the magisk module and app because of the read only system, you have to use the magisk module that loads it every boot

ShayBox said:
I don't know anything about fake locations, I've only ever used mock location a couple times
To get xposed afaik you get the Riru and Riru - LSPosed magisk modules, reboot and you get an LSPosed shortcut, which is your xposed control that lets you manage your xposed modules
For adblock, adaway works great, for theming you can get substratum (not substratum lite) from the playstore, and themes from the playstore, that works off a substratum magisk module and will theme the entire UI
If you need busybox for anything get the magisk module and app because of the read only system, you have to use the magisk module that loads it every boot
Click to expand...
Click to collapse
Thank you again, hey, I don't understand one of the steps that you said.
"Then download and extract the android sdk platform tools (fastboot/adb), and copy the patched boot.img to that folder"
I have the platform tools folder on my computer already, do you mean put the patched file in the entire platform tools folder?

cwgzz said:
Thank you again, hey, I don't understand one of the steps that you said.
"Then download and extract the android sdk platform tools (fastboot/adb), and copy the patched boot.img to that folder"
I have the platform tools folder on my computer already, do you mean put the patched file in the entire platform tools folder?
Click to expand...
Click to collapse
Yes, it can be anywhere but you'll have to provide the path to it in the fastboot flash command
such as "fastboot flash boot patched_boot.img" or "fastboot flash boot C:\Users\Admin\Desktop\patched_boot.img"
putting it in the folder makes it easier to type

ShayBox said:
Yes, it can be anywhere but you'll have to provide the path to it in the fastboot flash command
such as "fastboot flash boot patched_boot.img" or "fastboot flash boot C:\Users\Admin\Desktop\patched_boot.img"
putting it in the folder makes it easier to type
Click to expand...
Click to collapse
Okay I am not finding how the phone will find the file when I am recovery mode... I patched the rom now and I can't figure out how to load the patched rom. The only options I have is reboot to bootloader, enter fastboot, apply update from adb/sd card, wide data, mount system,
Going into fastboot, the only options are reboot system now, enter recovery, reboot to bootloader, power off

Download the Android SDK Platform Tools from Google here https://developer.android.com/studio/releases/platform-tools
Extract that, then copy the patched boot img to that extracted folder
Turn off your phone, then hold volume down and plug it into your computer, this should boot it into bootloader mode
Then open a command prompt, powershell, or windows terminal inside the extracted folder
This is most easily done by holding shift and rightclicking in the empty area of the folder, and a new option will show in the rightclick menu for a command prompt, powershell, or windows terminal (depending on your version of windows)
Once you have that open, type "fastboot" and press tab, it should autocomplete the .exe part, which means you have the correct window open and it's in the correct folder
after that, add "flash boot <filename_patched_boot.img>", the file name may start with magisk, or you can rename it to something easier to type like "boot.img"
Press enter and it should start flashing it to the phone, if there's any problems please post a screenshot of the window

ShayBox said:
Download the Android SDK Platform Tools from Google here https://developer.android.com/studio/releases/platform-tools
Extract that, then copy the patched boot img to that extracted folder
Turn off your phone, then hold volume down and plug it into your computer, this should boot it into bootloader mode
Then open a command prompt, powershell, or windows terminal inside the extracted folder
This is most easily done by holding shift and rightclicking in the empty area of the folder, and a new option will show in the rightclick menu for a command prompt, powershell, or windows terminal (depending on your version of windows)
Once you have that open, type "fastboot" and press tab, it should autocomplete the .exe part, which means you have the correct window open and it's in the correct folder
after that, add "flash boot <filename_patched_boot.img>", the file name may start with magisk, or you can rename it to something easier to type like "boot.img"
Press enter and it should start flashing it to the phone, if there's any problems please post a screenshot of the window
Click to expand...
Click to collapse
It keeps saying fastboot: usage: no command (This is so complicated...)

ShayBox said:
Download the Android SDK Platform Tools from Google here https://developer.android.com/studio/releases/platform-tools
Extract that, then copy the patched boot img to that extracted folder
Turn off your phone, then hold volume down and plug it into your computer, this should boot it into bootloader mode
Then open a command prompt, powershell, or windows terminal inside the extracted folder
This is most easily done by holding shift and rightclicking in the empty area of the folder, and a new option will show in the rightclick menu for a command prompt, powershell, or windows terminal (depending on your version of windows)
Once you have that open, type "fastboot" and press tab, it should autocomplete the .exe part, which means you have the correct window open and it's in the correct folder
after that, add "flash boot <filename_patched_boot.img>", the file name may start with magisk, or you can rename it to something easier to type like "boot.img"
Press enter and it should start flashing it to the phone, if there's any problems please post a screenshot of the window
Click to expand...
Click to collapse
Okay I understand what you mean. Now it is saying cannot load boot.img, no such file or directory. It did autocomplete to .exe like you said.

cwgzz said:
It keeps saying fastboot: usage: no command (This is so complicated...)
Click to expand...
Click to collapse
cwgzz said:
Okay I understand what you mean. Now it is saying cannot load boot.img, no such file or directory. It did autocomplete to .exe like you said.
Click to expand...
Click to collapse
You're missing the end of the filename (.img)

ShayBox said:
You're missing the end of the filename (.img)
Click to expand...
Click to collapse
Oh... duh... what an idiot... hahah thank you so much for spending your time helping me out, I sincerely appreciate it so much. Alright so it's done flashing, am I good to turn on my phone and it's now rooted?

Yes you're now rooted, you can check with any root checker app or any app that uses root
Inside the magisk app settings make sure to click the "Hide Magisk app" button, then install this safetynet fix magisk module
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
This is the direct link to the version you need https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.2/safetynet-fix-v2.1.2.zip
This requires the Riru magisk module, available in the magisk app, and then you can install this zip in the magisk app on the same page
After both Riru and Safetynet fix are installed and you reboot, the safetynet check button in magisk should pass and be blue
For xposed support also install the Riru - LSPosed magisk module, or the older Riru - EdXposed magisk module (I recommend LSPosed)

ShayBox said:
Yes you're now rooted, you can check with any root checker app or any app that uses root
Inside the magisk app settings make sure to click the "Hide Magisk app" button, then install this safetynet fix magisk module
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
This is the direct link to the version you need https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.2/safetynet-fix-v2.1.2.zip
This requires the Riru magisk module, available in the magisk app, and then you can install this zip in the magisk app on the same page
After both Riru and Safetynet fix are installed and you reboot the safetynet check button in magisk should pass and be green
For xposed support also install the Riru - LSPosed magisk module, or the older Riru - EdXposed magisk module (I recommend LSPosed)
Click to expand...
Click to collapse
Man you are so helpful, thank you so much for all of your help!!! Do I do all of this on my phone? Do I still need to use my computer?

You shouldn't need your computer anymore, everything is done, you just have to install all your apps now
Hopefully this helps other people in the future

ShayBox said:
Yes you're now rooted, you can check with any root checker app or any app that uses root
Inside the magisk app settings make sure to click the "Hide Magisk app" button, then install this safetynet fix magisk module
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
This is the direct link to the version you need https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.2/safetynet-fix-v2.1.2.zip
This requires the Riru magisk module, available in the magisk app, and then you can install this zip in the magisk app on the same page
After both Riru and Safetynet fix are installed and you reboot, the safetynet check button in magisk should pass and be blue
For xposed support also install the Riru - LSPosed magisk module, or the older Riru - EdXposed magisk module (I recommend LSPosed)
Click to expand...
Click to collapse
It shows that safetynet is installed, I don't see the blue, lol what exactly is safetynet?

cwgzz said:
It shows that safetynet is installed, I don't see the blue, lol what exactly is safetynet?
Click to expand...
Click to collapse
There's apps that google will mark as "not compatible" if you have root, such as all nintendo games like mario run, this is for that I believe, what does the checker say for the 3 sections

ShayBox said:
There's apps that google will mark as "not compatible" if you have root, such as all nintendo games like mario run, this is for that I believe, what does the checker say for the 3 sections
Click to expand...
Click to collapse
Oh wow, would this also fix banking apps as well? I know my bank checks for root and won't work. And I am sorry, I don't know what you mean about the checker and 3 sections.