Hi, I'm a newbie and I usually root my Pixel 4 on AT&T because I use a lot of tethering for my work which my carrier blocks.
Two weeks ago I had Android 10, unlocked and rooted. Life was good.
Phone automatically updated to Android 11 and I lost root.
Today I had some free time so I:
-Downloaded Android 11 factory img to my laptop
-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)
-Flashed the new patched img to my mobile
-Restarted
-Got stuck into the G with bar at the bottom eternally
-Couldn't get into ADB devices so I restarted to fastboot
-flashed the stock boot.img by: "fastboot flash boot boot.img"
-fastboot restart
-Now stuck on Fastboot Mode loop. Device Status "unlocked", boot slot a, enter reason: "reboot bootloader"
Now I don't know exactly what to do here and I do need my mobile to work. Sorry for the newbie question but what should I do? Ideally I would like to not lose my data given bootloader is already unlocked.
P.S. I ran stock image flash-all without the -w and I'm back to square 1. How should I root then?
Thank you so much!
luisbs said:
...-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)...
...How should I root then?
Thank you so much!
Click to expand...
Click to collapse
These Instructions might help:
First, you cannot root with the Stable Magisk Manager.
You can only root by using either the Beta or Canary Magisk Manager:
A. If Magisk Stable is installed:
1. Change the Update Channel to Beta or Canary
2. Install Beta or Canary Manager
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Uninstall all the modules
12. Uninstall Magisk - Restore images
13. Reboot
14. Goto D
B. If Beta or Canary Magisk Manager is installed:
1. Uninstall all modules
2 .Make sure the Update Channel is set to the version of the Manager installed.
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Goto D
C. If Magisk is not installed:
1. Download Beta or Canary Magisk Manager
2. Install Beta or Canary Magisk Manager
3. Make sure the Update Channel is set to the version of the Manager you installed.
4. patch the stock boot.img - tap Install next to Magisk
5. Select: Patch boot.image
6. Locate Stock boot.img you extracted from the current factory image.
7. Select it, tap the Checkmark (✓)
8. Tap Lets Go
9. Save log
10. Reboot
11. The magisk_patched.img size should be between 64-67 MB.
D. Flash magisk_patched.img:
1. Boot the phone into fastboot mode
(Power the phone Off ==> Press and hold the Power and Volumne down buttons until you see Start.)
2. Connect the phone to your Computer via a USB cable (A to B)
3. Open the Platform-tools folder and Right Click it.
(Make sure the magisk_patched.img is in this folder.)
Select Open Command prompt here. If you do not see Open a Command Prompt here. Click the folder icon on the left side of the address bar. The information in the address bar should be highlighted. Type cmd in the address bar and press Enter a Command Window should open. Type fastboot flash boot magisk_patched.img --slot all and press enter.
4. When it finishes, type fastboot reboot.
5. Disconnect your phone from the computer
6. Done! Your phone should be rooted
did it work on october update too?
my fastboot says: no valid slot to boot
Danieldergrosse said:
did it work on october update too?
my fastboot says: no valid slot to boot
Click to expand...
Click to collapse
Yes!
Than i am on Stock Boot lol
Danieldergrosse said:
Than i am on Stock Boot lol
Click to expand...
Click to collapse
Ok!
You dont Unserstand. My bootloader is unlocked. Why to flash the Stock boot.img Like you Said for d
Lol
Thats the Same as i Download factory extraxt and flash Boot. IMG
ITS the Same. So why you should get root with original Boot.img
Thats why i say loool
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?
I find a solution....i am Sure
Than i will Tell...
Danieldergrosse said:
You dont Unserstand...
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?...
Click to expand...
Click to collapse
Ok, I misunderstood your comments, I apologise.
No, I didn't rename the magisk_patched.img boot.img.
You dont understand what i mean....
If i flashed magisk patched it says No Slot to Boot. You Know.
Than i flash boot.img i am Back to Stock and it works....
My patched magisk doesnt Work....can you send me your patched magisk.img ?
Perhaps it works
Danieldergrosse said:
...My patched magisk doesnt Work...
Click to expand...
Click to collapse
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
Danieldergrosse said:
...I find a solution....i am Sure...
Click to expand...
Click to collapse
lol
??
Homeboy76 said:
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
lol
Click to expand...
Click to collapse
Don't know what's going wrong @Your side, but it works fine as ever
2WildFirE said:
Don't know what's going wrong @Your side, but it works fine as ever
Click to expand...
Click to collapse
I edited the post above to include Beta, thanks for the screenshot.
Danieldergrosse said:
??
Click to expand...
Click to collapse
Possible fix
Uploaded my patched boot.img for you: http://ul.to/utzm0kvc
Related
It would be nice to have step by step instructions for rooting.
Here's what I have thus far. The final root steps are not complete:
I. Enable Developer Options:
1. Go to your device Settings.2. Select “About phone” » tap seven times on “Build number”.3. This will enable Developer options under Settings.4. Go back to Settings » scroll down to Developer options5. Enable OEM Unlock: Open “Developer options” menu » enable OEM Unlock6. Enable USB Debugging: Open “Developer options” » scroll down to Debugging menu, enable “USB Debugging”
II. Unlock Bootloader - This will wipe your Pixel
1. Install ADB Installer 1.4.3 - http://downloadmirror.co/29Xn/adb-setup-1.4.3.exe2. Connect your Pixel device to the PC with a USB cable.3. Open a command window on your PC.4. Boot your Pixel device into bootloader mode using the following command:adb reboot bootloader[NOTE: You may get a request to authorize USB debugging on the device, accept it.]5. Once your dveice is in bootloader mode, issue the following command to unlock bootloader:fastboot flashing unlock6. You’ll get a confirmation screen on your Pixel device. Press Volume Up button to highlight Yes and press Power button to select it.7. You need to boot into system now, either press Power button to reboot OR issue the following command:fastboot reboot8. During reboot, your Pixel device will go through a factory reset and then finally boot into system.
[MISSING STEPS FROM THIS POINT ON]
III. ROOT
1. Download factory image for your model: https://developers.google.com/android/images- INSERT DESCRIPTION OF EACH - AT&T, Verizon, etc2. Extract the ZIP file3. Open the folder, locate the 2nd zip file, and extract it as well4.- Inside that folder, locate: boot.img and copy it to your Pixel 2
5. Download 2 Magisk filesMagisk Manager 5.4.1 APK- https://forum.xda-developers.com/attachment.php?attachmentid=4324973&d=1509987367Magisk 14.4 - https://forum.xda-developers.com/attachment.php?attachmentid=4324974&d=1509987379
6. Download a File Manager app from the Play Store, then find and install the Magisk APK???
7. Use Magisk to patch the boot.img file, which will then be found in /storage/emulated/0/MagiskManager/
Next steps??8. From command line to the ADB folder:adb reboot bootloaderfastboot flash boot patched_boot.imgPress power button to reboot
Click to expand...
Click to collapse
Wouldn't you have to copy patched_boot.img to your PC before you can fastboot flash it?
JimSmith94 said:
Wouldn't you have to copy patched_boot.img to your PC before you can fastboot flash it?
Click to expand...
Click to collapse
Yes, then recopy the APK back after the wipe.
Worked great. No issues. Nice work.
Bootloop?
So I get to the last step and flashed the patched_boot.img. The phone reboots, and I seem to be stuck at a perpetual "G" and progress bar. Looks like a boot loop. I waited 5 minutes hoping it would proceed with boot. I then tried to flash the stock boot.img. Still same apparent boot loop. I had to flash the stock restore image to get going again. Am I being impatient? Should it immediately boot up?
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
trixiejay said:
So I get to the last step and flashed the patched_boot.img. The phone reboots, and I seem to be stuck at a perpetual "G" and progress bar. Looks like a boot loop. I waited 5 minutes hoping it would proceed with boot. I then tried to flash the stock boot.img. Still same apparent boot loop. I had to flash the stock restore image to get going again. Am I being impatient? Should it immediately boot up?
Click to expand...
Click to collapse
Mine didn't take long at all to boot up. Pretty much like a regular restart.
---------- Post added at 02:15 AM ---------- Previous post was at 02:13 AM ----------
trim81 said:
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
Click to expand...
Click to collapse
I placed mine in the folder with my platform tools. With adb and fastboot.
trim81 said:
once magisk creates patched_boot.img ... do I need to copy this file and place it inside the ADB folder on the computer? if so, which folder do I drop this file in?
Click to expand...
Click to collapse
Platform tools folder. Then open a CMD prompt while you are inside that folder and put your phone in bootloader mode. Then fastboot flash boot patched_boot.img
shizat63 said:
It would be nice to have step by step instructions for rooting.
Here's what I have thus far. The final root steps are not complete:
Click to expand...
Click to collapse
The Magisk post in the section for ROMs , Kernels and other Development has full instructions on how to root with Magisk. It worked for me.
There's also another post in here where someone goes through steps to root, add a kernel, and get V4A running (to mixed success as normal), and although he uses steps different than the first post I referenced, it's working for him.
Magisk isn't producing out a boot.img
I'm using version 5.4.3
Once I select the boot.img. it just goes back to the magisk home screen and says "downloading magisk v14.zip"
What an Im I doing wrong
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?
Hey ! Today i will give you all the different ways/steps for root your Mi A2 easily.
+ How to manually create patched_boot.img for your version (beta...) without extrernal help.
Code:
Your warranty is now void.
We are not responsible for bricked devices, dead
SD cards... Please do some
research if you have any concerns about features
included in this GUIDE before using it! YOU are
choosing to make these modifications.
Summary
- Part 1 : Install drivers and unlock bootloader. Credit to @balazs312
- Part 2 : Root with 2 ways
- Bonus : Backup boot.img and make patched_boot.img
- Part 3 : OTA
Part 1 :
So, First you need to install drivers and unlock your phone bootloader. Skip to part 2 if already done.
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
Part 2 :
So there are currently two ways to root his phone. Let's start with the first.
Methode 1 : We will use the new temp twrp. Method by me.
1. Download files...
- Download this TWRP.
- Place it in your adb folder.
- Download Magisk-v17.2_a and Magisk-v17.2_b.
- Copy these 2 zips in your phone internal storage.
2. Check current-slot...
- Plugin your phone to you pc
- Navigate to your settigs on your phone.
- Open Developer settings
- Enable Usb Debugging
- A pop up should appear on your phone scren, hit and box and autorize the pc.
- on your pc, open fastboot command prompt, and type "adb reboot bootloader" , your device should reboot to fastboot
- type "fastboot getvar current-slot". Remember if the result is a or b.
3. Root using temporally twrp
- Reboot your phone in fastboot.
- On your pc, open fastboot command prompt, and type "fastboot boot twrp-3.2.3-jasmine-20181020.img"
- Your phone now reboot into twrp, it down't flash it, so after a reboot twrp will be gone.
- If twrp ask a password for decrypt data put your phone PIN and validate.
- Click on install and select Magisk-v17.2_a if the result in Step 2. is A, and Magisk-v17.2_b if result is B and swipe to install.
- Then select Reboot.
Now you have Magisk 17.2 installed on your phone, and twrp is gone after reboot. You can select beta in Magisk settings and update to 17.3 if you want.
Methode 2 : We will use patched_boot.img.
1. Where to find patched_boot.img ?
- Go here and check if there is your build version. If yes dowload the patched_boot.img file ( need to be on pc ) and skip to step 2. If not continue.
- If you can't find your correct build patched_boot.img (Because you are on the beta, and nobody share the file or something like that....) you can easily make your own using temp twrp. Go to Bonus part, make your patched_boot.img and continue.
2. Pepare files.
- Copy the patched_boot.img in your adb folder
- Be sure to rename it to "patched_boot.img"
- Download latest Magisk Manager apk here (currently v6.0.1)
- Copy the apk on your phone storage.
3. Install Magisk
- Reboot your phone in fastboot.
- Open a fastboot command prompt on your pc.
- Type "fastboot boot patched_boot.img"
- Your phone will reboot, put your pin....
- Go in your prefer file explorer and Install the magisk apk.
- Now open Magisk Manager app
- Click Install, direct install. Wait for the process
- And click reboot.
Now you have Magisk 17.2 installed on your phone. You can select beta in Magisk settings and update to 17.3 if you want.
Bonus
So, i will show you how to backup your current bot img. And how to make your own patched_boot.img, so people who are on Beta OTA can root there phone without any external help...
1. Backup the boot.img
- Download this TWRP.
- Place it in your adb folder.
- Reboot your phone in fastboot.
- On your pc, open fastboot command prompt, and type "fastboot boot twrp-3.2.3-jasmine-20181020.img"
- Your phone now reboot into twrp, it down't flash it, so after a reboot twrp will be gone.
- If twrp ask a password for decrypt data put your phone PIN and validate.
- In TWRP, click on "Advanced"
- Click "File Manager"
- Navigate to /dev/block/platform/soc/c0c4000.sdhci/by-name
- You will se a lot of files, and if you look you will see 3 important files, boot, boot_a and boot_b.
- Click on the "boot" file
- Click "Copy File"
- Navigate to /sdcard
- Click the blue arrow and swipe to confirm
- Click reboot
- Copy the file on your pc, and rename it to "boot.img" instead of "boot".
Now you have backup your stok boot.img you can use it for stock or whatever you want....
2. Create the patched_boot.img file
- Download latest Magisk Manager apk here (currently v6.0.1)
- Install the apk on your phone
- Open Magisk Manager
- Go to settings , click Update Channel and select Beta
- Return to home of Magisk Manager
- Click Install, then Boot image file patch ( don't know the correct typo because for me the app is in french, champion du monde !! xD ) and wait for the end of the process.
Done you now create your own patched_boot.img ! Enjoy !!
Part 3 :
So, now i will explain you how to install OTA when you have magisk.
- First, disable Automatic system updates in developer options, so it won't install OTAs without your acknowledgement.
- Open Magisk Manager, click Uninstall, then Restore Images. Don't reboot !
- Now Search for update and wait for the process. BUT do not press the "Restart now" or "Reboot" button !
- Open Magisk Manager, hit Install, then Install to inactive slot.
- Reboot when it's done.
If it don't work (strange) and ota failed, you can find your stock boot.img for your build version here, or backup your boot.img using the[ B]1.[/B] of the Bonus part and flash it using the command "fastboot flash boot_( your current slot) boot.img" (you can check your current slot with command "fastboot getvar current-slot).
If you have issues or something like that, here are some telegram group :
MiA2dev
MiA2OffTopic
HexKernel
Work perfect with october update
Thanks 4 your great work
nnexuss said:
Work perfect with october update
Thanks 4 your great work
Click to expand...
Click to collapse
Your wellcome, enjoy
Thx for your very, very good work. No Problems at all with October update. :good:
mahalo
yorkberliner said:
Thx for your very, very good work. No Problems at all with October update. :good:
mahalo
Click to expand...
Click to collapse
nice, enjoy
What to do when Magisk prompts that "Stock Image does not exist"?
Couldn't find a folder to put stock image.
0firuz said:
What to do when Magisk prompts that "Stock Image does not exist"?
Couldn't find a folder to put stock image.
Click to expand...
Click to collapse
can you explain which part you try to do, and on which steps you got this error? for more support you can join telegram groups from the bottom of the guide.
*edit* you can flash stock boot.img for future OTA. check the Part 3 : OTA
Hi
Right now im on OPM1.171019.011.V9.6.13.0ODIMIFE (5 sept 2018) rooted with magisk
I just want to update and re-root, the painless style. I dont want to flash a ****load of stuff to have a functionning phone.
Can anyone confirm that step 3 is ok? Thats the same method than for MI A1, and it was only half functionnal, i dont want to play with fire.
After having killed the IMEI numbers and the persist partition of the A1, it took me 2 weeks to repair, I dont want to **** up this one too. Hell no.
kaott said:
Hi
Right now im on OPM1.171019.011.V9.6.13.0ODIMIFE (5 sept 2018) rooted with magisk
I just want to update and re-root, the painless style. I dont want to flash a ****load of stuff to have a functionning phone.
Can anyone confirm that step 3 is ok? Thats the same method than for MI A1, and it was only half functionnal, i dont want to play with fire.
After having killed the IMEI numbers and the persist partition of the A1, it took me 2 weeks to repair, I dont want to **** up this one too. Hell no.
Click to expand...
Click to collapse
this is safe. but if you want to can just use patched boot method.
I used the method described in Step 3 to install the September OTA (V9.6.13.0) and re-install Magisk. It worked like a charm, but I am trying to repeat the method to install the October update without success. The OTA updater downloads the update, and starts installing it, but it fails miserably every time.
I have even completely uninstalled Magisk and flashed the img from here: https://sourceforge.net/projects/others/files/MiA2/
But It does not work, the OTA installer always fails.
I'm clueless, what can I do?
doragasu said:
I used the method described in Step 3 to install the September OTA (V9.6.13.0) and re-install Magisk. It worked like a charm, but I am trying to repeat the method to install the October update without success. The OTA updater downloads the update, and starts installing it, but it fails miserably every time.
I have even completely uninstalled Magisk and flashed the img from here: https://sourceforge.net/projects/others/files/MiA2/
But It does not work, the OTA installer always fails.
I'm clueless, what can I do?
Click to expand...
Click to collapse
it's because during the ota process, the current slot change. but you can back to stock September ROM, then update. and after that root using my second post https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/
Thread closed at OP request
tested and working
DP1 no wipe, run TWRP skip password if it asks, push latest magisk canary build to /mnt and flash
you will have root though i cant seem to update magisk.apk or zip through the app cheers guys
EDIT
Just uninstalled magisk that flashed with canary build from telegram chat and downloaded lastest apk from github canary. and working fine!!!
attached is an updated installer should work fine!!
Anyone?
ne0ns4l4m4nder said:
Anyone?
Click to expand...
Click to collapse
Yep can confirm that the latest canary build is working great. John Wu pulls through again in record time.
And just an extra disclaimer for the sake of clarity this is only working on the previous gen Pixels. The 3/3 XL are still a work in progress for the time being.
couldnt install says invalid zip format
mysara saad said:
couldnt install says invalid zip format
Click to expand...
Click to collapse
Yeah that zip has an extra folder inside of it for some reason. Just use the one from the magisk canary thread.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
I had to remove lock screen security first too since TWRP wasn't decrypting properly with it on. GL
You don't need to decrypt, just skip and push the magisk.zip to /mnt and install
Here's how I got to rooted q from the latest rooted stock p without wiping my internal memory. Please note that I do not have any passwords or patterns on my phone, so this works if you do not have encryption. Just make sure you back your phone up to your computer first just in case something goes wrong :
0. With your phone hooked to the computer, boot into bootloader and type "fastboot devices" to make sure your phone shows up. This is optional and just something I do to make sure everything is working as it should.
1. Download the factory image from here: https://developer.android.com/preview/download.html
2. Download and install the canary magisk manager from here: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337. Go to settings and change the update channel to canary. There will now be a new update, tap install but select "download only".
3. Unzip the factory image.
4. Open the "flash-all.bat" file in a text editor and remove the -w flag after the fastboot command near the bottom of the file.
5. Obtain the STOCK boot.img and dtbo.img of the system rom you are CURRENTLY running.
6. Type "adb devices" with your phone hooked up to the computer to make sure that you have a good connection and your phone has debugging on and authorized.
7. Reboot into TWRP and wipe Dalvik/ART cache, System, and Data.
8. Reboot into bootloader.
9. Take a command prompt to where your current stock boot.img and dtbo.img files are.
10. Command: fastboot flash boot {name_of_your_stock_boot.img}
11. Command: fastboot flash dtbo {name_of_your_stock_dtbo.img}
12. Now take your command prompt to where your unzipped q rom is.
13. Command: flash-all
14. When it's finished, your phone will reboot.
15. Download the latest twrp img and zip here: https://dl.twrp.me/taimen/
16. Once your phone is rebooted, go into settings and enable usb debugging.
17. Open a command prompt where you downloaded the twrp image.
17. Command: adb reboot bootloader
18. Command: fastboot boot {name_of_twrp_image_you_downloaded.img}
19. Flash the TWRP zip and the canary magisk zip you downloaded earlier and reboot.
19. uneseesery steps that dont work...
hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
That is exactly what I did to get on rooted q from rooted p, without losing anything on my internal storage, and it does work. If you can tell me any "uneseesery" steps here I'm all ears.
hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
I don't think so..I rooted through that step only..
My phone was rooted before updating to android 12. After updating I lost the root access. Bootloader is unlocked still. Now I want to root my device again but unfortunately didn't find any working recovery for flashing magisk zip.
Sakhawat_Hossain said:
My phone was rooted before updating to android 12. After updating I lost the root access. Bootloader is unlocked still. Now I want to root my device again but unfortunately didn't find any working recovery for flashing magisk zip.
Click to expand...
Click to collapse
I was in the same situation. Thankfully someone had shared the boot image.
-Fastboot boot from this image
-Install Magisk
-Choose "install"
-Select "direct install"
-Reboot
You're now rooted.
Xcaliber said:
I was in the same situation. Thankfully someone had shared the boot image.
-Fastboot boot from this image
-Install Magiske
-Choose "install"
-Select "direct install"
-Reboot
You're now rooted.
Click to expand...
Click to collapse
Tried but got stuck in the pink T-Mobile Screen.
Sakhawat_Hossain said:
Tried but got stuck in the pink T-Mobile Screen.
Click to expand...
Click to collapse
Try this:
-install magisk 26 https://github.com/topjohnwu/Magisk/releases
-patch the unpatched boot image with Magisk (attached as boot.img)
-fastboot boot new-patched-image
-open Magisk and select direct install
I also added my own patched image, maybe you can try something with that if the latter doesn't work.
I think my initial instructions were wrong. Follow the steps in my previous message.
Xcaliber said:
Try this:
-install magisk 26 https://github.com/topjohnwu/Magisk/releases
-patch the unpatched boot image with Magisk (attached as boot.img)
-fastboot boot new-patched-image
-open Magisk and select direct install
I also added my own patched image, maybe you can try something with that if the latter doesn't work.
Click to expand...
Click to collapse
Did everything but faced the same issue. (Got stuck in the pink T-Mobile screen.)
Sakhawat_Hossain said:
Did everything but faced the same issue. (Got stuck in the pink T-Mobile screen.)
Click to expand...
Click to collapse
What version are you running? Check in Settings > About Device > Version
The images I sent are for version 11_F.04
Xcaliber said:
What version are you running? Check in Settings > About Device > Version
The images I sent are for version 11_F.04
Click to expand...
Click to collapse