I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Make sure you have the latest USB drivers: https://developer.android.com/studio/run/win-usb
and the latest platform tools: https://developer.android.com/studio/releases/platform-tools.html
NOTICE: The latest version (34) gave me this error when updating: "FAILED (Sparce file is too large or invalid)". When updating again with version 33 everything went fine.
Some Magisk modules may cause bootloops so it's best to disable them and to reboot before updating.
Unhide Magisk.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/images#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while, and sometimes it even fails the first time. Don't worry and try again.
In the extracted folder there is another zip file. Extract this too.
Now inside the extracted folder, look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file, and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and now rooted device!
Code:
fastboot reboot
Now can can turn back on your Magisk modules and hide it.
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
Perfect, Thank you, would you please to do another guide of how to enable 5G and Volte
mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
This works perfectly! Thank you for sharing this method! Worked flawlessly on my bramble to get it to the February security update! Very amazing!
drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
_______________________
I figured it out... I need to update my adb folder on my comp, thankssssss worked well.
kazemitsui said:
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
Click to expand...
Click to collapse
Did you pick the right version?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
drdionysius said:
Did you pick the right version?
View attachment 5216649
Click to expand...
Click to collapse
Yea I figured it out, I needed to update my adb folder on my computer!
I'm having a problem myself with patching the boot.img through Magisk Manager. It says "installation failed".
-update-
Solved. I had to update Magisk Manager Canary.
mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good
ggkameleon said:
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good
Click to expand...
Click to collapse
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it did not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!
3dcantaloupe said:
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it didd not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!
Click to expand...
Click to collapse
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks
ggkameleon said:
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks
Click to expand...
Click to collapse
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks
3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
I'm curious, are you running the current March update?
ggkameleon said:
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks
Click to expand...
Click to collapse
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".
DJBhardwaj said:
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".
Click to expand...
Click to collapse
Ok thanks thank you.
I test it. Have a good day
3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp
artlan said:
I'm curious, are you running the current March update?
Click to expand...
Click to collapse
yes, I am running RQ2A.210305.006
ggkameleon said:
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp
Click to expand...
Click to collapse
Not that they don't want twrp, but no one is taking the initiative to fork it over to our device yet. It will eventually make it I bet! Using the hardware buttons as DJBharadwaj stated did not work, and I had to instead I had to wait for the phone to boot, then I longpressed restart to boot into safe mode.
Hi ! And it's possible to flash the magisk mod Center Clock ? Or make bootloop ?
Related
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...
ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.
otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same
trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:
v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources used: link
1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should you fail.
2. Enable Developer mode and adb from Developer settings again.
3 Download the appropriate Fastboot files for your device . See the About section in your phone's settings to know what you are currently running.
4. Download latest Magisk-vXX.Y.apk and install it on your device. Magisk developer only provides files from Github, do not download it from anywhere else.
5. Extract(Install 7-zip if needed) the fastboot .tgz archive and copy the boot.img from it to your phone's sdcard through adb (or other means):
Code:
adb push psyche_eea_global_images_V13.0.3.0.SLDEUXM/images/boot.img /sdcard/
6. Open up Magisk on your phone, press Install and use the patch option to navigate to the boot.img you just copied. Select that, next next next.
7. Read the output to see where the patched boot.img got saved. Pull that.
Code:
adb pull /sdcard/Download/magisk_patched-24300_D2K9V.img
8. Reboot phone to fastboot.
Code:
adb reboot fastboot
9. Flash the modified boot image
Code:
fastboot flash boot recoveryxy.img
10. Flash dtbo (found inside rom zip)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Say your prayers and reboot, your device should now have functional root with Magisk
Code:
fastboot reboot
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
weggy101 said:
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
Click to expand...
Click to collapse
im sorry forgot step 10. flash vbmeta image. updated guide.
nofx161 said:
im sorry forgot step 10. flash vbmeta image. updated guide.
Click to expand...
Click to collapse
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5.0.SLDCNXM/miui-blockota-psyche-V13.0.4.0.SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
I think it worked here, I patched the boot.img from the EEA ROM I'm running (V13.0.3.0.SLDEUXM_20220528.0000.00_12.0_eea) and the Magisk App says it's installed. The only problem is that I'm not able to edit files and/or paste new ones in the root/system folder.
I'm trying to edit build.prop but it says there's not enough space to complete the operation (using SolidExplorer), I tried to disable my nav buttons with FNG too, but that also won't work.
hey you can use my boot image which is rooted with magisk 25.0
magisk_patched-25000_WA0wW.img
drive.google.com
also the original boot if you messed up
boot.img
drive.google.com
Did anyone solved CTS profile ?
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
bjs339 said:
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
Click to expand...
Click to collapse
What ROM do you use? Stock or xiaomi EU or which one? Which modules have you tried? Thanks!
I'm on the stock rom and really haven't done much with it yet, so not much to report at this point.
An alternative way for installing magisk is to install twrp ( https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/ ) and then choose "install twrp" from the advanced menu in twrp. Then restart system and tap on the magisk button. The magisk manager will be loaded from web and your good to go with root.
shortek said:
Did anyone solved CTS profile ?
Click to expand...
Click to collapse
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
bjs339 said:
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
Click to expand...
Click to collapse
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
bjs339 said:
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Click to expand...
Click to collapse
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
HikL said:
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
Click to expand...
Click to collapse
Looks like it if I'm reading that right.
bjs339 said:
View attachment 5699583
Looks like it if I'm reading that right.
Click to expand...
Click to collapse
Great news! Thank you!
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
boot.img
drive.google.com
kiknalex said:
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
Click to expand...
Click to collapse
I patched boot.img with another phone (huawei or smth) repeated all steps and now it's just stuck in fastboot bootloop...
I tried this
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5....SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
But my Mi PC Suite doesn't detect phone when I plug cable, although the icon on phone shows that it's plugged in. Please help me...
Edit: issue was fixed in this thread
Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.
Hello. I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/ only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available...
forum.xda-developers.com
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Voodoojonny said:
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Click to expand...
Click to collapse
Thank you for your answer. I already fixed issue in another thread, will edit my comment.
Hiya folks.
Well that was a fun brick - And I still don't really know what I did wrong.
I have a T-Mobile LE2127 and it was on Android 12 - I don't need to use it yet, so I am happy to play with it. Bootloader and SIM are unlocked, I can fastboot boot magisk_patched-25200_JdBlm.img to get root, and I can fastboot twrp-3.6.2_11-0-lemonadep
In TWRP-3.6.2 I used dd to grab the boot.img dd if=/dev/block/bootdevice/by-name/boot of=/usbdrive/boot.img and I patched that with the latest Magisk (1)
I tested to see if that would boot up with a fastboot boot and it worked fine - Sooo, I decided to "fastboot flash boot" it and then everything went very wrong.
The boot told me: "Qualcomm CrashDump Mode / da-verity device corrupted / verify_ctr" -- And then it went into an infinite bootloader loop which wouldn't let me into EDL mode (2)
When I was in the infinite loop, I couldn't "fastboot boot" anything, it told me it wouldn't load anything with: error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Eventually, I used the very useful MSM/lemonadept_22_O.04_210409 package to recover it and now it's working again. (3)
So - What did I do wrong? -- I suspect it may have patched my boot to slot B but I am not sure that should have mattered too much, I popped one back into Slot A as well.
I see a thread on using "adb reboot "dm-verity enforcing" but I didn't have to do that with things I booted from rather than flashed... And I couldn't get into adb at that point anyway. Does this mean my patched boot.img will not do what I want it to anyway?
Anyway, I should stop speculating and ask the experts!
Thanks.
(1) https://www.droidwin.com/extract-boot-img-directly-from-device-without-downloading-firmware/
(2) https://www.droidwin.com/boot-oneplus-9-pro-9r-9rt-to-edl-mode-5-methods/
(3) https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/ -- [No instructions, but just run it as admin, connect phone and it does it all].
What I do is in bootloader mode, fastboot boot twrp, in twrp I install magisk.zip, then reboot system and tap on magisk app and follow prompts. Done
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
kjslabber said:
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
Click to expand...
Click to collapse
Ah! That worked and was very simple, thanks... For some reason in my head, I was thinking that Magisk would only patch the booted image, which would be pointless; but it patched the real phone one.
I assume I'll just have to do the same every update.
Thanks!