Database Info

Lenovo A706 root

Hi, can anyone help me on rooting my lenovo A706. I have framaroot even the latest version (1.6.0) but still my devices isn't rooted yet. I think the problem was i have updated OTA twice before seeing instructions on how to root my device.
can anyone help me?
thanks in advance.

darksoul42 said:
Hi, can anyone help me on rooting my lenovo A706. I have framaroot even the latest version (1.6.0) but still my devices isn't rooted yet. I think the problem was i have updated OTA twice before seeing instructions on how to root my device.
can anyone help me?
thanks in advance.
Click to expand...
Click to collapse
This is my method how to root Lenovo A706 using Fastboot without flashing your recovery.
WARNING: It may void your phone's warranty. DO AT YOUR OWN RISK.
>>Step 1: Download CWM and flashable root zip file in this thread http://forum.xda-developers.com/show....php?t=2391801
>>Step 2: * Unzip the CWM and copy recovery.img in "platform-tools" folder in Android SDK if you have it.
* Copy the Flashable root zip file into your root of External SD Card
>>Step 3: In your phone, Enable USB Debugging. (Settings > Developer option > Switch on the the slider button of Developer option then check the USB debugging and Allow mock locations) then connect your phone in to your PC.
>>Step 4: SHIFT + Right click on "platform-tools" folder and then select "Open command window here".
>>Step 5: In command window, type adb reboot bootloader then your phone will reboot into fastboot mode.
>>Step 6: type fastboot devices. You can see your device in cmd "MSMXXXXXX fastboot mode" or whatever.
>>Step 7: type fastboot boot recovery.img. You can see that your phone is rebooted into CWM Chinese recovery.
>>Step 8: In the menu, choose the 2nd option. i cannot remember but if you see the option which have a word "SDCARD" or "SD", then that is what im talking about. hehehe
>>Step 9: Select the flashable root zip file then BOOM. Your phone is rooted. In CMD type adb reboot to reboot your phone then you will see the Superuser has already installed.
**************SORRY FOR MY BAD ENGLISH.. Base on my experience, i cannot reflash the CWM after updating my ROM. so i used this method and my phone now is already rooted.

can someone help me to find A706ROW_1_S_2_001_0021_130923 ?
i have version 13075 and i want this firmware to solve mic problems ...
if i make ota update i will have problems ( they told from there i buy it... )
some help please?
thank you

Reset lockscreen security on GoClever Tab r76.2

Hello, I get just today a GoClever Tab r76.2 to reset the forgotten pin from the locksreen. Device was used mainly for Pou and Facebook, so there was no root, no usb debugging, my PC was not set as trusted device, just like from the store with PIN set. Installed system is Android 4.1
Because it took me whole morning and I found a lot of answers that "it cannot be done, you have to factory reset" I want to show you my steps to make this process easier for people in need. This method shouldn't erase any data from your device but always remember to have a backup
It is based on the following tutorial: http://forum.xda-developers.com/showthread.php?t=2601933 , but still it was not enough for me so I want to provide more details.
Step 1.
The very important thing is to install drivers for the device. To make this process the easiest I get my old, good Asus netbook with Windows XP installed. You can install it also on VirtualMachine, it is not very mandatory but my next steps will be based on this configuration.
There is a need for two types of drivers: Rockchip drivers to flash the memory and ADB Drivers.
1.1) Rockchip drivers can be found in the thread linked above, I am providing mirror at the bottom of this thread. Just doubleclick on the exe, accept the risk and install, that's all for now.
1.2 ADB drivers are provided in the second package attached. To install adb drivers go to recovery.
To switch tablet to the Recovery Mode you have to switch it off (not reboot), turn it on, just when the BootScreen will appear tap Vol+ until you will see opened Android Robot with exclamation mark. What's interesting, when you double click Vol+ this time you can switch to Android Recovery menu and factory reset the device
In device manager (Win+R, type: devmgmt.msc and press ENTER) install drivers for Tab r76 device manually, by providing direct location to the .ini file from the folder.
Leave tablet in Recovery.
Step 2.
People from some Russian Android forum prepared package with pre-configured adb for rockchip devices. Just download attachment 2.1, extract it, install, open Command Line and "cd" to directory with adb.exe, very useful.
Step 3.
Now we will root the device and install CWM. Download file from the attachment 3.1, unzip it and run "RK29Update.exe", don't click any button (especially the one called "Erase", it will brick your device), don't change any setting, your tablet will be not found at the moment. This package belongs to the author of the original tutorial.
Step 4.
In command line enter "adb devices" to check if your tablet is visible, you should see something like "0123456789ABCDEF recovery", if yes enter "adb reboot bootloader" and press enter. Tablet will reboot, the screen will remain black, system will install the Rockchip driver, RK29Update.exe will find the device (IF NOT just reboot to recovery again and reboot to bootloader from adb again, driver installation might interrupt this process), press Run button in the application it will flash the device with root patch and CWM, device will reboot to CWM recovery.
Step 5.
Download attachment nr 5.1 (original source: http://forum.xda-developers.com/showthread.php?t=2437946) and put the zip to the SD card (card has to be compatible with the device - most secure solution is having FAT32 filesystem), put it to the tablet, install zip from external source (not sdcard, it's internal memory).
After reboot of the device ("restart system now" option in main page of CWM) your device should welcome you without screen locked by any security possible and your settings should remain untouched.
From now everybody should be able to reset it's PIN in the easy way Have fun
CC: You are allowed to copy this tutorial anywhere, mirror the links also, but please leave a link to the original thread.

LG Aristo 2 ROOT (LM-X210[Build- X210MA10i])

===============================================================================
TUTORIAL REVISED AND WRITTEN BY @parcek
===============================================================================
FURTHER UPDATED FOR ROOTING NOOBS: 10 Steps
Two Methods: Windows and Linux
Originally posted by @brad2192: https://forum.xda-developers.com/android/development/lg-aristo-2-root-t3746425
Credit to @tecknight for updated files: https://forum.xda-developers.com/showpost.php?p=76837384&postcount=2
@brad2192: Updated Tutorial due to people using TWRP (the original tutorial was released before TWRP was released for this device)
1) Backup all apps and data using LG Backup phone apps
2) Enable USB debugging and Unlock OEM. There are two methods in which you will to accomplish this:
First Method: Smartphone GUI
A) On your Lg Aristo 2 Smartphone go into General Tab (If in Tab View), If in list view, scroll down towards System section
"System Settings > About Phone > Software Information > Click on "Build Number" 10 times.
Now go to "System Settings > About Phone > Developer Options > Enable OEM unlock."
and also "System Settings > About Phone > Developer Options > Enable USB debugging."
Second Method: Windows Command Prompt or Linux Terminal:
Windows:
B) Click and drag "adb" file into command prompt and type "reboot bootloader" after it. Press enter.
Click and drag "fastboot" file into command prompt and type "flashing unlock" after it. Press enter.
Linux:
C)Type in your terminal "adb reboot bootloader" and press enter.
Type in your terminal "fastboot flashing unlock."
NOTE: Below has the information which will teach you how to download ADB and FASTBOOT.
3) Download the following:
Updated - TWRP
Updated - Magisk
(Add this file into your phone's SD Card.)
Updated - boot image
Update: Windows:
B)This is how you download ADB and FASTBOOT for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4) Open Command Prompt. Then click and drag the adb file (from the latter download link a.k.a platform-tools) into command prompt then press space and type "reboot bootloader" after and then press enter OR power down phone and hold volume down while plugging in USB)
5) Open Command Prompt. Then click and drag the fastboot file (from the latter download link a.k.a platform-tools) into command prompt and then type "flash recovery" after it and then click and drag "newtwrp.img" into command prompt and press enter.)
6) Open Command Prompt. Then click and drag fastboot (from the latter download link a.k.a platform-tools) into command prompt and then type "flash boot" after it and then click and drag "bootimglistedabove.img" into the command prompt after and then press enter) then follow step 7).
Update: Linux:
C) Depending on kernel, for this sake we will use a debian based kernal.
This is how you download ADB and FASTBOOT for Linux: Open terminal and type: "Sudo apt-get install adb && sudo apt-get install fastboot"
4) Open terminal and type: adb reboot bootloader
5) Open terminal and type: fastboot flash recovery (and then click and drag newtwrp.img onto the terminal) and hit enter
6) Open terminal and type: fastboot flash boot (and then click and drag bootfilelistedabove.img onto the terminal) and hit enter
This applies towards both Windows and Linux: continuation after their last listed step written above.
Step 7) Remove battery from phone, in order to force a shut down.
8) Boot into Recovery-TWRP Mode.
How to boot into LG Aristo 2 TWRP Recovery:
a) The phone is off.
b) Hold the volume key and power key at the same time.
c) When the LG logo appears, let go of the power key (while still holding the volume down key) and then click and hold the power key once again.
d)You will be prompted to LG Aristo 2's stock recovery mode asking you if you are sure you would like to delete ur phone.
e) Go to the option "yes" and enter.
f) It will then warn you that can remove all data from your phone.
g) Go to the option "yes" and enter.
You will be in TWRP after this.
TWRP Mode:
9) In TWRP go to "Wipe > Format Data" and then type "yes" and confirm it. (Do not hit reboot, click back a few time and hit reboot > recovery)
10) In TWRP go to "Install > Select Storage" and select your SD Card. Then look for where you placed the "magisk" zip file. Install it.
Your phone is now rooted.
On TWRP menu: Reboot.
Restore your phone if you created an LG backup of your important files (like lets say contacts or applications).
-----------------------------------------------
If any mistakes were made and you phone becomes locked, here is how to go into download mode to repair your LG Aristo 2 into its default stock rom. Credit to @tecknight: https://forum.xda-developers.com/showpost.php?p=76837800&postcount=4
1) Power off phone.
2) connect usb to Lg Aristo 2 phone (without connecting the usb into the PC or laptop)
3) Hold volume up key and then connect USB into computer
4) download LG Bridge
5) detect phone
6) click on "Update Error Recovery"
Your LG Aristo 2 will be repaired and factory resetted.
-------------------------------------------------------------
What root means: In terms of PC language, Root means the superuser that has privileges to Add, Modify, and or Delete any kind of system files without prevention. Pretty much, it's like the actual Administrator account on a PC. Natively, whenever we buy a phone, it is as if to say, we are only using a guest account. Since the android OS is basically a Linux based computer (correct me if i am wrong) we can do anything we like... You want iOS emoji's on an android? A custom boot animation? Having root privileges allows you to go beyond your guest user restrictions because you then become the Admin.
Explaining the function of the provided Magisk app: It allows root privileges for programs intended for rooted phones.
There are other popular programs alternative of Magisk app, such as the SuperSU app: http://www.mediafire.com/file/2dljobq6yw93w76/UPDATE-SuperSU-v2.82-20170528234214.zip
--------------------------------
After being officially done setting up your rooted phone, make sure you disable OEM Unlock to avoid seeing the caution message before every boot.
--------------------------
How to backup your phone.
Also, using ADB, backup your phone.
Windows: Click and drag ADB file onto command prompt and paste " backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Linux: Open terminal and type " adb backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Update: For those who are encountering "Now unlock your phone and confirm operation" when typing the latter code, there is an alternative and much more easier and safer way to backup your phone.
Boot into TWRP and click on "backup" and then select what you would like to back up and then swipe to confirm the operation.
-----------------------------------------------------------------
Confirmed Successful rooting for LG Aristo 2 - June 2018
Thank You Brad and Tec!
Salam Aleykom.

You are a lifesaver my friend

Senorhamburgler said:
You are a lifesaver my friend
Click to expand...
Click to collapse
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?

tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.

tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Senorhamburgler said:
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
Click to expand...
Click to collapse
Root is the only thing needed, not a custom recovery. Apps like Magisk Manager can flash custom images. The reason there is no ROMs built for this device, I can tell you in my opinion there is no need for a Custom ROM. Magisk Manager has plenty of customizations available as well as many other root apps. Basically, custom recoveries are obsolete, it is not needed for gaining root access nor flashing files. Magisk can do it as well as Flashfire.

I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...

MinaSaotome said:
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
Click to expand...
Click to collapse
Hey man, I would press the Windows Key+R and type" "cmd"
Then, as long as your adb is located at C:\adb type: "cd C:\adb"
Then use adb, I hate how Windows 10 forces it on users!

Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
---------- Post added at 01:15 AM ---------- Previous post was at 01:01 AM ----------
4btn said:
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
Click to expand...
Click to collapse
Okay, after messing around with it a few, I found that once it goes off into fastboot... my computer can't recognize it anymore?

brad2192 said:
Hey guys, spent a few hours figuring out how to root. Pretty Simple!
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
For those skeptical, proof of root here.
X-210 Stock .KDZ Backup HERE (Should not be needed.)
Click to expand...
Click to collapse
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?

tge101 said:
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
Click to expand...
Click to collapse
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.

brad2192 said:
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
Click to expand...
Click to collapse
Just wanted to make sure but does it wipe it?

tge101 said:
Just wanted to make sure but does it wipe it?
Click to expand...
Click to collapse
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.

brad2192 said:
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
Click to expand...
Click to collapse
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?

tge101 said:
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
Click to expand...
Click to collapse
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.

brad2192 said:
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
Click to expand...
Click to collapse
All good, if I lose it I lose it. Is there a thread for the TWRP development?

I posted a test twrp on my blog for aristo 2

cannot open root_boot.img
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it

tge101 said:
All good, if I lose it I lose it. Is there a thread for the TWRP development?
Click to expand...
Click to collapse
Update: TWRP HERE

TJ-yesthelegend said:
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
Click to expand...
Click to collapse
What are you typing into ADB to get that error?

Do you have to de-encrypt the phone for root? I am thinking of getting an Aristo2, currently using the MotoE4 (which I hate!), and rooting that requires de-encryption (I love encryption!). This is the MetroPCS version your talking about? Thank you...

[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT

Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).

This worked great for me - thank you for the post!

Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?

I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....

Moto_Fan said:
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
Click to expand...
Click to collapse
Yes, that should supposedly work the same, although not personally tested.
Moto_Fan said:
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Click to expand...
Click to collapse
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/

nor-ric said:
Yes, that should supposedly work the same, although not personally tested.
TESTED AND WORKED PERFECTLY!!!
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
Click to expand...
Click to collapse
Yea, I already found out about the module, and it did indeed work and passed safety net after cts profile failed.
Now on too Pixel 4a #2 ON android 12 PDP1, too ROOT or NOT to ROOT??? We'll find out soon enough i guess???

nor-ric said:
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
Click to expand...
Click to collapse
Would like to go this route for reasons you have stated above. Have a few questions:
1: If you use normally use Linux why did you use a Windows VM rather than simply do all operations in a Linux terminal?
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
3: Will SuperSuperuser be installed under this environment?
I have rooted several devices in the past using varied methods and things seem to have changed drastically since my previous Nexus 6p
Thanks

CarlInMO said:
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
Click to expand...
Click to collapse
I did the above steps and titanium backup, root explorer and other root apps work great.
CarlInMO said:
3: Will SuperSuperuser be installed under this environment?
Click to expand...
Click to collapse
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.

JohnC said:
I did the above steps and titanium backup, root explorer and other root apps work great.
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
Click to expand...
Click to collapse
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?

CarlInMO said:
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
Click to expand...
Click to collapse
Using stock android 10 image from google because TWRP and Edxposed are stable with android 10, not 11.

And what happens to root & TWRP after upgrade back to Android 11. I assume installed apps continue to operate OK

TWRP has now been modded and is working with A11! Details in the TWRP thread!

Rooting the Motorola one 5G ace

How to root the Motorola One 5G Ace on Windows 10
Android Instructions * Windows 10 Instructions​
On the phone: Main Menu > Settings > About > tap Build Number 7 times until Developer Mode is unlocked.
Back out from About phone and go to System > Advanced > Developer Options > USB Debugging set on.
On Windows 10: Download the latest Android Platform Tools and extract to C:/​
Click Start and type 'cmd' then click 'Run as administrator.'​
Run 'cd C:/platform-tools'.
Run 'adb devices'.​
Authorize USB Debugging on the phone.​
Run 'adb reboot bootloader'​
After phone has restarted type 'fastboot devices'.​
Run 'fastboot oem get_unlock_data'​
Copy the lines of text with (Bootloader) next to them.​
Internet: Register and Login to Motorola's Unlock Bootloader Code Exchange​
Paste the lines of code into the box but before, remove (Bootloader) and the spaces between each line of code.​
Accept the terms if you do to receive an email with an unlock code which you copy.​
Command Prompt: Run 'fastboot oem unlock UNIQUE_KEY' twice.​
Run 'fastboot reboot' then unlock phone/ enable File Transfer in notification box.​
Download this(1) and this(2).​
From (1): extract boot.img, copying it to the phone's Download folder.​
Copy (2) to the phone's Download folder as well.
Main Menu > Downloads > tap 'magisk-manager....'
Tap 'Settings' and toggle the switch to allow then tap back then 'install'
Main menu > Magisk Manager > App: Update >Settings > Allow toggle > Back > Install
Open Magisk Manager > Magisk: Install > Select and Patch a file > Downloads > Select boot.img
After: Copy modified boot.img(magisk_patched...) from phone to PC to 'C:/platform-tools/'.
Run 'adb reboot bootloader'.
Run 'fastboot flash boot ___________' (Blank being the modded boot.img known as 'magisk_patched....')
Any clue? Mine didn't work. Used LMSA with patched boot.img renamed from magisk_patched... in the downloaded firmware in LMSA. Then fastboot flash boot boot.img after after the rescue had failed and said it was still running. Fluked it to work....

WatchGod said:
How to root the Motorola One 5G Ace on Windows 10
Android Instructions * Windows 10 Instructions​
On the phone: Main Menu > Settings > About > tap Build Number 7 times until Developer Mode is unlocked.
Back out from About phone and go to System > Advanced > Developer Options > USB Debugging set on.
On Windows 10: Download the latest Android Platform Tools and extract to C:/​
Click Start and type 'cmd' then click 'Run as administrator.'​
Run 'cd C:/platform-tools'.
Run 'adb devices'.​
Authorize USB Debugging on the phone.​
Run 'adb reboot bootloader'​
After phone has restarted type 'fastboot devices'.​
Run 'fastboot oem get_unlock_data'​
Copy the lines of text with (Bootloader) next to them.​
Internet: Register and Login to Motorola's Unlock Bootloader Code Exchange​
Paste the lines of code into the box but before, remove (Bootloader) and the spaces between each line of code.​
Accept the terms if you do to receive an email with an unlock code which you copy.​
Command Prompt: Run 'fastboot oem unlock UNIQUE_KEY' twice.​
Run 'fastboot reboot' then unlock phone/ enable File Transfer in notification box.​
Download this(1) and this(2).​
From (1): extract boot.img, copying it to the phone's Download folder.​
Copy (2) to the phone's Download folder as well.
Main Menu > Downloads > tap 'magisk-manager....'
Tap 'Settings' and toggle the switch to allow then tap back then 'install'
Main menu > Magisk Manager > App: Update >Settings > Allow toggle > Back > Install
Open Magisk Manager > Magisk: Install > Select and Patch a file > Downloads > Select boot.img
After: Copy modified boot.img(magisk_patched...) from phone to PC to 'C:/platform-tools/'.
Run 'adb reboot bootloader'.
Run 'fastboot flash boot ___________' (Blank being the modded boot.img known as 'magisk_patched....')
Any clue? Mine didn't work. Used LMSA with patched boot.img renamed from magisk_patched... in the downloaded firmware in LMSA. Then fastboot flash boot boot.img after after the rescue had failed and said it was still running. Fluked it to work....
Click to expand...
Click to collapse
You are going to have to flash the stock rom via fastboot (see my guide about that) and then patch magisk from the boot.img in the version you pick from the repo. I have root, but root with Android 10 will not make the system R/W, so while you get to see the back end files you won't be able to mod them, and any of your explorers like Root Explorers may or may not work either.

Shouldn't this thread be moved to the "Guides" section? I almost thought phone was unrootable because I looked here first...

WatchGod said:
How to root the Motorola One 5G Ace on Windows 10
Android Instructions * Windows 10 Instructions​
On the phone: Main Menu > Settings > About > tap Build Number 7 times until Developer Mode is unlocked.
Back out from About phone and go to System > Advanced > Developer Options > USB Debugging set on.
On Windows 10: Download the latest Android Platform Tools and extract to C:/​
Click Start and type 'cmd' then click 'Run as administrator.'​
Run 'cd C:/platform-tools'.
Run 'adb devices'.​
Authorize USB Debugging on the phone.​
Run 'adb reboot bootloader'​
After phone has restarted type 'fastboot devices'.​
Run 'fastboot oem get_unlock_data'​
Copy the lines of text with (Bootloader) next to them.​
Internet: Register and Login to Motorola's Unlock Bootloader Code Exchange​
Paste the lines of code into the box but before, remove (Bootloader) and the spaces between each line of code.​
Accept the terms if you do to receive an email with an unlock code which you copy.​
Command Prompt: Run 'fastboot oem unlock UNIQUE_KEY' twice.​
Run 'fastboot reboot' then unlock phone/ enable File Transfer in notification box.​
Download this(1) and this(2).​
From (1): extract boot.img, copying it to the phone's Download folder.​
Copy (2) to the phone's Download folder as well.
Main Menu > Downloads > tap 'magisk-manager....'
Tap 'Settings' and toggle the switch to allow then tap back then 'install'
Main menu > Magisk Manager > App: Update >Settings > Allow toggle > Back > Install
Open Magisk Manager > Magisk: Install > Select and Patch a file > Downloads > Select boot.img
After: Copy modified boot.img(magisk_patched...) from phone to PC to 'C:/platform-tools/'.
Run 'adb reboot bootloader'.
Run 'fastboot flash boot ___________' (Blank being the modded boot.img known as 'magisk_patched....')
Any clue? Mine didn't work. Used LMSA with patched boot.img renamed from magisk_patched... in the downloaded firmware in LMSA. Then fastboot flash boot boot.img after after the rescue had failed and said it was still running. Fluked it to work....
Click to expand...
Click to collapse
Thanks for the guide.it looks like root is either not possible or very difficult and dangerous. If Magisk did what it was supposed to do at step 23, I don't understand the need for the other steps. Please note that I come from 8-9 years of Samsung and Odin so adb and fastboot are essentially new to me.

RETIEF said:
Thanks for the guide.it looks like root is either not possible or very difficult and dangerous. If Magisk did what it was supposed to do at step 23, I don't understand the need for the other steps. Please note that I come from 8-9 years of Samsung and Odin so adb and fastboot are essentially new to me.
Click to expand...
Click to collapse
Root IS possible and do-able. I have it on my phone and it isn't as difficult as you think. I'll write you a noob guide.

Articul8Madness said:
Root IS possible and do-able. I have it on my phone and it isn't as difficult as you think. I'll write you a noob guide.
Click to expand...
Click to collapse
Thanks

RETIEF said:
Thanks
Click to expand...
Click to collapse
Here's your noob guide. Should work the same on Windows 10. Don't be intimidated by all the steps, it's a hand holding guide. https://forum.xda-developers.com/t/...o-one-5g-ace-xt2113-qualcomm-variant.4255113/

RETIEF said:
Thanks for the guide.it looks like root is either not possible or very difficult and dangerous. If Magisk did what it was supposed to do at step 23, I don't understand the need for the other steps. Please note that I come from 8-9 years of Samsung and Odin so adb and fastboot are essentially new to me.
Click to expand...
Click to collapse
Magisk has to patch the boot image in order to achieve root. It doesn't rewrite the image but modifies it in such a way to give ownership to us to have access to the root system files. If you mess up my guide should ease all fears. Keep in mind Magisk has been doing root like that since version 7. Its just now they don't use Magisk Manager. It's a less evasive process than the old school TowelRoot.
This is actually less hard than Odin. I've had a Moto E4, E5, G7Power and Now this phone. It's been the same process damn near for all of them except the E4 - Nougat and KitKat were different file systems than this sparsechunk crap they started with Pie.

Rooted.
Bought this phone adding a line to metro and phone was 89.99. Oem unlock was able to enable no problem. Rooted no problem..I also flashed retus firmware over metro software/bloat.. everything works,, dolby/ viper for droid works.. waiting on custom Roms now...

Currently, there is no point in rooting this smartphone.
Even if you get root, most of the folders and files are r/o and we can't do anything with them.

I'm looking forward to possibly having Lineage OS on this device once we have TWRP recovery installed.

Wow this phone has 128 gb storage and 6gb of ram.
Sadly the stock software takes over 3gb of ram.
Once a custom rom is built will see more ram hopefully...

jhjhjhjhjhjh said:
Wow this phone has 128 gb storage and 6gb of ram.
Sadly the stock software takes over 3gb of ram.
Once a custom rom is built will see more ram hopefully...
Click to expand...
Click to collapse
Yeah I've noticed that when using Device Info HW. The system takes up half the ram usually 54% so hopefully a new custom rom would be built soon once we finally have TWRP compiled for this device to eliminate any ram hogging files and apps that take most of the ram up

Anyone actively developing TWRP or custom ROMs for this? Currently have a OnePlus Nord N105G on Metro and OEM unlocking is tied to sim unlocking. Looking for a change.

Txdude35 said:
Anyone actively developing TWRP or custom ROMs for this? Currently have a OnePlus Nord N105G on Metro and OEM unlocking is tied to sim unlocking. Looking for a change.
Click to expand...
Click to collapse
Sadly I don't because I don't know how to create TWRP. As for right now there's an experimental port going on so I'm actively waiting for a recovery image for my phone and I'll finally start posting a debloated rom by any chance if it were possible. Luckily we have a kernel for the ace so custom roms may roll out faster depending on the developers themselves over at Lineage OS owning this device just for the purpose of unlocking.

The twrp created by the porting tool does not have a functioning touch panel on some devices.
To make the touch panel work, you need to build it from source.
I don't know how to do it.
There is little hope.

PEACH-PIT said:
Currently, there is no point in rooting this smartphone.
Even if you get root, most of the folders and files are r/o and we can't do anything with them.
Click to expand...
Click to collapse
Bypassing Carrier Hotspot Limit and Installing Screen2Auto Android Auto mod ARE the two reasons I want to buy and root this phone! Worked great on my G Stylus with Android 10, the 5g T-Mobile Speed would be nice where I live.

jhjhjhjhjhjh said:
Wow this phone has 128 gb storage and 6gb of ram.
Sadly the stock software takes over 3gb of ram.
Once a custom rom is built will see more ram hopefully...
Click to expand...
Click to collapse
Use my debloat guide. Cleans the crap right out without a custom rom.

Articul8Madness said:
Use my debloat guide. Cleans the crap right out without a custom rom.
Click to expand...
Click to collapse
What did you use to debloat? I usually use Titanium Backup, but it says the apk file can't be found.

RETIEF said:
What did you use to debloat? I usually use Titanium Backup, but it says the apk file can't be found.
Click to expand...
Click to collapse
I used CMD prompt and did it manually. Check my debloat guide. Titanium Backup will NOT work.