Root Ulefone Armor 12 - Android General

It is same as root Armor 10.
The usual disclaimers apply; Do this at your own risk, I'm not responsible if you brick or damage your device, or void your warranty, etc. I'm also going to condense the instructions a bit, on the assumption anyone who's serious about rooting already knows the basics.
How do it.
1. You must download original ROM, you need boot.img from this ROM. And download ADB to your PC.
2. Copy boot.img from ROM to your phone (or differnd android phone).
3. Donload and open the Magisk app.
4. Next, tick "Install"-"Install Magisk".-'Select and patch a file." Select the 'boot.img" file you transferred to the phone's local storage Magisk will write a root-patched copy, named "magisk_patched_xxxxx.img," to donwload directory.
5. Copy patched file to PC.
6. On phone enable developer option (Go to "Settings", then tap "About device" or "About phone". 2 Scroll down, then tap "Build number" 7x ).
7. On developer menu click "Unlock Bootloader" and activation USB debug.
8. Transfer the patched image file to the ADB tools directory on your PC.
9. Connect phone to PC and Open a command prompt window, on your PC, in the directory your ADB tools are installed(or go to this direction by cd.. and cd command).
10. Reboot the phone to via ADB "adb reboot bootloader" to fastboot mode.
11. Type "fastboot devices" to make sure the system sees your phone.
12. Type "fastboot flashing unlock" and uce button on phone to do it . YOUR PHONE DELETE ALL USER DATA
13. Reboot phone again to fastbootmode and type: "fastboot flash vbmeta vbmeta_null.img" and hit enter.
14. Next, type "fastboot flash boot magisk_patched_xxxxx.img" (naturally, replace the X's with whatever string of characters Magisk supplied or change name).
15. Type 'fastboot reboot' and hit enter.
Your Armor 12 should now be rooted. Enjoy!
I use vbmeta_null (for ulefone armor 10) from this : https://forum.xda-developers.com/t/systemless-root-on-ulefone-armor-10-5g-how-i-did-it.4243161/

In official ROM missing good batery statistic - I use GSam Battery Monitor. Its possible configure to acces by adb or use in root phone. Now I see time to charge and time to off .
Next step for me Is change power off menu or remaping power buton to google assistant.

Related

Flashing stock recovery for those who Stuck at boot screen ninja A87

Download recovery - recovery.img
1. Make sure you have ADB or the SDK installed.
If you have rooted your phone successfully then you must have it installed.
2. Download the files from this link : platform-tools.rar
3. Extract the downloaded file to a location of your choice
for example - D:\SDK
4. Now go the folder, press the shift button and right click. You would see an option 'Open command prompt here' - click that to open command prompt.
5. Connect your phone switched off to the pc and press the volume down button and the power button for 10 seconds. You should see the micromax logo.
6. In command prompt type "fastboot devices" without quotes and hit enter.
7. you should see something like
List of devices attached
M7------ device
8. Now copy the recovery.img to the same folder you had extracted the files earlier.
9. In the command prompt window, type "fastboot flash recovery recovery.img" without quotes and hit enter
10. After you get a confirmation that flash is successful.
11. Remove the phone and boot into recovery.
Very Simple N Easy way

[Q] weird problem on Nexus S - please assist

This is going to be pretty long and have had the problem for months so please bear with me, read and see if you could assist.
Borrowed a friends Nexus S a while back. Used it for a few days, turned it on one day and it stays on the black google screen with the open padlock at the bottom
I am able to enter Fastboot mode is shown in image 2; lock state is unlocked.
I followed the instructions as in post 2 on the following thread
HTML:
http://forum.xda-developers.com/showthread.php?t=1787169
and as copied below but when i got to the part where i needed to mount my sdcard i get the error " unable to write to ums lunfile (no such file)".
Originally Posted by SamuelDebruyn View Post
Ok, you'll need a Windows computer to fix this. Linux should work too but if you're using Linux I guess you could figure out what would be the instructions for Linux yourself. Mac would work too but I don't know how.
Download and install the Android SDK on your computer from http://developer.android.com/sdk/index.html
Open the SDK Manager (there should be a shortcut in your start menu) and install "Android SDK Tools" and "Android SDK Platform-tools" and "Google USB Driver" (it's in Extra).
Turn your phone off, take the battery out, look at the bottom of the phone and write down the model number.
Now go to https://developers.google.com/android/nexus/images and download the factory image for your model for version 4.0.4.
You'll need something like 7-Zip (http://www.7-zip.org/) to open it.
Copy image-so....zip, radio-crespo...img and bootloader-crespo...img from the factory image to the platform-tools directory (on most computers it will be C:\Program Files (x86)\Android\android-sdk\platform-tools and you'll need Administrator rights).
Now open the platform-tools directory from the Android SDK and right click on an empty space while holding the SHIFT button and select "Open command prompt here".
Put the battery back in your phone and press Power while holding the Volume-Up button so it will boot into fastboot mode. Then connect it to your pc.
If Windows starts complaining about drivers then point it your SDK installation directory (include subfolders) or use 7-Zip to unpack http://www.mediafire.com/?5a7gou9droidi53 and point Windows to the directory where you unpacked it. More info on http://www.sevenforums.com/tutorials...e-manager.html
When you type "fastboot devices" and press Enter in the command prompt you opened before it should list one device (being your phone).
If you haven't unlocked your phone before type "fastboot oem unlock" and press Enter. Follow the instructions on the screen on your phone to complete the unlock.
Next type "fastboot flash bootloader bootloader-crespo...img" (you can press TAB to auto-complete) and press Enter. (THIS IS THE MOST IMPORTANT STEP, IF THIS GOES WRONG YOUR PHONE IS SCREWED. Don't continue if another step didn't succeed. If this works, then you can do anything with it.)
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next type "fastboot flash radio radio-crespo...img" (you can press TAB to auto-complete) and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next type "fastboot -w update image-....zip" and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Next download http://download2.clockworkmod.com/re...0.7-crespo.img and also put it in the platform-tools directory.
Then type "fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img" and press Enter.
Now type "fastboot reboot-bootloader" and press Enter and wait for your phone to reboot into fastboot mode.
Now use the volume keys on your phone to navigate to the word Recovery and press the Power button to boot into recovery.
You're now in CWM Recovery, use the volume keys and the power button to go to Mounts & Storage > Mount USB Storage (you might have to scroll down). Now it will come up on your pc and you can transfer the update file for Jelly Bean to your phone. You can find it here: http://forum.xda-developers.com/show...68&postcount=1 (use the one for your model for IMM76D).
Unmount the usb storage, go back to the main menu and go to Install Zip from sdcard > Choose zip from sdcard and open the update file you just transferred to your phone.
You can now go back to the main menu and choose "reboot system now". It will ask you if you want to remove the auto recovery installation, do that.
That's all, you now have a clean and working Jelly Bean installation.
Someone else wrote down the same instructions if mine are not clear enough: http://forum.xda-developers.com/show....php?t=1785672
Click to expand...
Click to collapse
This prevented me from putting the stock image on the sdcard for flashing via CWM.
is there another way i can get this working, maybe via fastboot or via ODIN so i can return my friends phone.
Thank you.
Hi I had this problem to, mine was from a bad flash / bad firmware.
First I suggest http://forum.xda-developers.com/showthread.php?t=2284670 better recovery.
After from recovery
select factory reset, wipe cache, and from advance wipe dalvic cache.
then select mount usb, copy to card slim bean 3.1.0 http://www.slimroms.net/index.php/downloads/dlsearch/viewdownload/465-crespo/2505-slim-ns-3-1-0-official plus gaps http://www.slimroms.net/index.php/downloads/dlsearch/viewdownload/461-addonsfullpackages-412/2501-aio-addons, flash them in this order.
After first boot and config u can use http://www.wugfresh.com/nrt/ to write the OEM firmware.
Sorry this didn't work because nothing can be written to system and the sdcard is still not able to mount
Sent from my GT-N7100 using xda app-developers app

Installing a custom Recovery and rooting most Nokia Devices (Android)

DISCLAIMER: This is in no way advertising, it is merely providing sources for readers and have no connection with me, the writer. If required the link may and will be removed. I (the writer) have no responsibility no matter what happens to your device.
NOTE: IF YOU WANT TO KEEP YOUR WARRANTY DO NOT DO THIS.
Perquisites:
A Nokia Device - (2, 2.1, 5, 6 , 6.1, 7, 7 Plus, 8) and a data transfer cable
A PC - Linux, Chromebook, Mac, Windows (Any computer that supports Android SDK) - Must have access to command line
Android SDK (See other tutorials on how to install)
Access to Developer Options (About Phone > Tap build number loads of times)
Nokia OST with Patch.
TWRP for your Nokia Version (Look on XDA)
Magisk Manager and Magisk v16+
SafetyPatcher for Magisk by Hackintosh5
An Unlock.bin that can be obtained from here [URL removed]. Note: It costs $5.00 but unfortunately is the only way to get it currently as Nokia is not supporting the unlocking of bootloaders.
Method:
0a. Install OST with the patch
1. Enter Developer Options, and ensure USB Debugging and OEM Unlocking are enabled.
2. After installing ADB and plugging in your phone, make sure your laptop has USB Debugging permissions.
3. Goto the OST LA Directory (DRIVE:\Program Files (x86)\OST LA) and CTRL+Shift+Right Click and open command window here.
4. Ensure your device is recognised by your PC Using "adb devices". If your device is recognised, continue onto 5, if not refer to 4b.
4b. If your device is not recognised, make sure USB Debugging is enabled and re plug in your phone, unlock the phone, and click allow when prompted for USB Debugging permission. To make things easier down the line, if it is your PC tick "Always allow".
5. Enter "adb reboot bootloader" and submit the command.
6. Wait for your device to restart and say download mode in the bottom left corner.
7. Once it has finished loading, enter "fastboot flash unlock path" where path is the path to the unlock.bin file you would have been sent by email after filling in the form. For Example: "fastboot flash unlock C:\Users\XDAForums\Downloads\unlock.bin".
8. Once this finishes, proceed with the command "fastboot oem unlock-go". Follow phone screen instructions, if it just restarts, that is also fine.
9. Your data will be reset so you will have to set the phone up again. Therefore, you will also have to go through the steps of USB Debugging, however, the OEM Unlocking should be greyed out. If it is not, please repeat the steps from 5. Whilst you are doing this, please install Magisk Manager onto your device aswell.
10. Back to your PC, enter "adb reboot bootloader".
11. Once it says download mode, enter "fastboot boot path" where path is the path of the TWRP image.
12. It should boot into TWRP. If it does, your are successful until now.
13. If it asks your to allow modifications, allow it and swipe. Do not reboot the phone yet.
14. Open file explorer in your PC and copy over the TWRP image file and the magisk v16.0+ zip file to the SD CARD of the phone, which can if inserted into the phone can be seen in the file explorer, or one can install it using the pc card reader.
15. In TWRP click Install. And click install image. Select "Select Storage" and choose your SD Card. Find the TWRP image you copied to your SD Card and click on it to install it. (Swipe the bar)
16. Reboot to system.
17. Install the official TWRP App and create a backup of the Recovery Partition.
18. Open Magisk Manager and Tap the "Tap to start safetynet check". If it fails, that is fine.
19. On your phone, open up and download this
. Open up Magisk Manager, goto modules, click the plus and click the safetypatcher.zip you would have just downloaded.
20. Try the safetynet check again, then if it is fine, then not only does it work, you will still be able to use Netflix and Android Pay!
After this, Your HMD Nokia device should be rooted. Should a custom ROM be developed, once can flash it using TWRP!
Has anyone tried this successfully on the Nokia 7 Plus and would I be able to install a Custom ROM through this recovery process if that is even a thing? I sometimes misunderstand the processes and what they are actually accomplishing?
Thank you in advance

Ulefone Power 6 Root

Hello. Has anyone rooted the Ulefone Power 6 yet? Im looking to have TWRP installed onto my new Power 6. My goal is to figure out a way to add user profiles, as it currently does not have them activated. I read online that you could edit the .prop to have any android activate the user profiles, but i cannot do this without my phone being rooted. Thanks in advance.
Start Here
Dvalin21 said:
Start Here
Click to expand...
Click to collapse
Sorry, This is for the original Ulefone Power, not the Power 6. Different phones. The instructions didn't lead me to anything useful. I have since update my phone to the latest firmware via the stock update app. I still haven't found a successful way to root the Power 6. There is this thread (https://www.getdroidtips.com/root-ulefone-power-6/), but the ADB commands to not work, and does not fastboot my phone to install the patched image. But either way, the instructions do not include a TWRP, so Im back to square one. HELP!
How to root Ulefone Power 6 (Build Power_6_SF1_V07) Updated 9/22/2019
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
Pre-Requirements:
Device battery charged up to 50%.
Developer Options enabled with OEM Unlocking and USB Debugging enabled
Remember to take a full backup of device data (Internal Storage, SMS), it will get formatted.
A Windows or Mac PC/Laptop is necessary to flash Magisk
A USB cable to connect your device with your PC
Download Links:
Download Minimal ADB Fastboot 1.4.3 (Portable). Extract it to your desktop.
It's best to give administrator privileges to the tools before you use them. To give them admin privileges:
Right click on adb.exe and select "Properties" at the bottom of the menu. Click on the "Compatability" Tab and check the "Run this program as an Administrator" box. Click on the "Apply" button and then the "OK" button to close the properties window.
Repeat the same process for the "cmd-here.exe" and the "fastboot.exe" files.
Ulefone USB Drivers. Extract it to your desktop and make sure you install the drivers.
MTK USB Drivers. Extract it to your desktop and make sure you install the drivers.
Latest Ulefone Power 6 Stock ROM. Or you could make a back up yourself. (latest rom as of 2/25/20 is GQ3081SF1_M860B1_Ulefone_20190921_V07(Non-EU) ).Extract it to your desktop.
MTK SP Multi Port Download Tool. This will be used to flash the most recent Ulefone rom on your device. Extract it to your desktop.
Download Magisk Manager
After downloading the Stock ROM (will be a .ZIP file), extract it to your PC.
Connect your device via USB cable
Find the "boot.img" file inside the Stock Rom folder you just extracted and copy only the "boot.img" file to your devices storage.
Copy Magisk Manager.apk to your devices storage
Using your device, install Magisk Manager
Open the Magisk Manager on your device.
Select "Install" from the first option next to "Magisk is not installed" and again select install.
Now, tap on "Select and Patch a File".
Go to your devices storage where you have copied the "boot.img" file earlier and select it.
Magisk will start patching the boot image.
Once the boot image is patched, Magisk will save the image on your "Download" folder located on your devices storage.
Locate the patched image (magisk_patched.img) and copy the "magisk_patched.img" to your PC. Make sure the patched image (magisk_patched.img) is inside the same folder as the extracted ADB and Fastboot tool folder on your desktop.
Open/run MTK SP Multi Port Download Tool
Click on File from the Menu located at the top right and select "Open Download Agent File"
Locate and select "MTK_ALLInOne_DA.bin", located in the same folder as the MTK SP Multi Port Download Tool folder.
Press the "Open buton" to select the file and close the window.
Now, click on the "Scatter File" button located at the top left.
Locate and select the XXXXXXXX_scatter.txt file located inside the extracted Ulefone Power 6 Stock Rom folder.
Press the "Open buton" to select the file and close the window.
Now, tick the "BootRom+PreLoader COM Sel All" check box located under the "scatter file" button.
Now, Click on the "Scan" button located at the bottom right.
Select Yes from the pop up window
Now, power off you device and disconnect your device from your PC by removing the USB cable from your device.
Now, reconnect the USB cable to your device while it is powered off.
MTK SP Multi Port Download Tool should detect your device and a green bar should appear confirming the connection with the words "Scan Success!" to the left of the green bar.
Press the "Stop all" button located at the bottom right
Disconnect and reconnect your device from your PC
Uncheck the "BootRom+PreLoader COM Sel All" box and check only the line with the green bar.
Click on the tiny "Start" button located to the right of the green bar.
You can confirm the flash was successful when the words "PASS" is visible to the right of the tiny "Start" & "Stop" buttons
Once the flashing is complete, you can close MTK SP Multi Port Download Tool and power on your device.
Configure your device to get to the home screen (skipping as many options as you can. You will have to format one more time) and enable Developer Options, OEM Unlocking and USB Debugging again.
Make sure your device is connected to your PC.
Now, you need to open up a command window (cmd window) inside the Minimal ADB Fastboot 1.4.3 (Portable) folder. To do this, open the "cmd-here.exe" file.
Next, enter the following command in the cmd window:
adb devices
(this command will confirm your device is connected to your PC via ADB )
Your device will show a pop up window asking for permission to connect via ADB. Click on the "Always Trust This Device" and Accept the connection
If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
adb reboot-bootloader
(This command will boot your device into fastboot/bootloader mode. It will turn off and the device will have a black lit screen)
Check that your device is connected to your pc by entering the following command:
fastboot devices
(this command will confirm your device is connected to your PC via fastboot/bootloader mode ) If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
fastboot flashing unlock
(if nothing happens, press the Volume up+ on your phone to start the unlocking of the bootloader)
(this will unlock your bootloader)
Next, enter the following command:
fastboot getvar unlocked
(this will confirm you have unlocked your bootloader. It will say "unlocked: yes")
Next, enter the following command:
fastboot flash boot magisk_patched.img
(This will replace your stock image with the patched image you created using Magisk Manager)
Next, enter the following command to reboot your phone:
fastboot reboot
Install magisk manager using your file manager. Make sure to follow directions when it asks you to give special permissions to install.
Open Magisk Manager and click on "OK" when it starts up and asks you for "additional setup".
Congratulations! Your device is rooted.
Extra notes:
If you come across a red watermark with the Chinese words and "Tee Keys" and/or "Google Keys" on the top right of your devices screen, this is how you fix it.
make sure your device is turned on and connected to your PC.
Open "cmd-here.exe" located in the Minimal ADB Fastboot 1.4.3 (Portable) folder.
Next, enter the following command:
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
(This command will not do anything at the moment, but will remove the watermark after you reboot your device)
Next, enter the following command to reboot your device:
adb reboot
The watermark should be removed when your device restarts again.
ENJOY!
19Henry83 said:
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
. . . . .
. . . . . . . . . . .
. . . . . . . . . . . . . . .
ENJOY!
Click to expand...
Click to collapse
Thanks a heap for all these instructions, would not have been able to do this without them.
Just a few extra pieces of information for anyone else caryring out the above steps:
- If you your stock ROM doesn't have a file manager in order to open/execute the MagiskManager APK file then using Chrome to download the APK file will allow you to execute it.
- in the SP Multi Port Tool, after checking the line with the green bar and clicking start you'll notice the time in seconds counting next to the start button. At this point you may need to unplug your USB cable and replug it in order for the SP Multi Port Tool to detect the devices and actually start properly
- If the SP Multi Port Tool requires a checksum.ini file you can follow the instructions on the hovatek site (Google 'checksum.ini generatemediatek hovatek' I'm a new user so can't post links):
Note there is a download link for the CheckSum_Gen.zip file which will require you to register for an account on the hovatek website. You can create a junk/throw away account with a fake email as it doesn't require email confirmation. Also all of the files inside the CheckSum_Gen.zip folder need to be placed inside of the stock ROM folder where the scatter file is located.
- The watermark can only be removed after the MagiskManager carries out its additional setup and after root access is complete.
Still hoping to find a compatible TWRP recovery. If anyone builds one please let us know!
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
I Need help please ,, I need the TWRP Recovery, Tool / Utility for the Ulefone Power 6, I have looked for it in many web pages and I cannot find it, all the ones I find have the same name "3.3.1 Power 6" and not It works for me when I install them, I get the same recovery that I had when I try to enter
jiroscop said:
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
Click to expand...
Click to collapse
Hello Jiroscop. I had the same problem and only noticed after i read your post. Now, a couple months later, i managed to use an IMEI changer to insert my IMEI found on my original box where my phone came in. It should have two IMEIs. I don't know if i can explain on this forum. Try researching it on your own and get back to me if you cannot find a way to fix your phone.
NOTE: you will need your original IMEI's, changing the IMEI's with anything other than the original ones will brick your phone.

[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!

Categories

Resources