I did flash the full image. I caught the "-w" tag and realized I wasn't going to delete any of my data.
I guess next, I can try with the OTA file, but I don't know how that's going to be any better.
Question Magisk/Root procedure for 5a 5G?
- Thread starter Ehikes
- Start date
I did flash the full image. I caught the "-w" tag and realized I wasn't going to delete any of my data.
I guess next, I can try with the OTA file, but I don't know how that's going to be any better.
I followed the steps a user posted at the bottom of page 1 of this thread:
Also I got safetynet and google pay working with MagiskHide Props - force basic attestation with default Nexus 5 value.
your steps are a bit out of order. You shouldn't patch your boot img until after you've updated (flash-all)
after you have done a normal update, then you can patch your image with magisk, pull it and flash it with fastboot. after you reboot you should be rooted, although you probably won't pass safetynet.
I'm new to gaining root by way of image patching; came from an LG V30 where direct install method was used. When i try to select the file and patch, I get the error when attempting to patch the Bootloader file; Unsupported/Unknown Image Format.
I'm on the September update, rd2a.210905.002. Process was:
Unlock bootloader
Enabled USB debugging on phone after reset
Download factor image (verified SHA sum)
Extracted bootloader img file and pushed to Download folder on phone by adb
Install Magisk from GitHub site
Open Magisk, select install using Select and Patch a File
I've attempted this with Stable, Beta, adn Canary builds of Magisk all with the same result.
I've looked through some bug reports on older builds of Magisk but it seems like the problem may have been resolved. Any assistance would be appreciated.
I'm on the September update, rd2a.210905.002. Process was:
Unlock bootloader
Enabled USB debugging on phone after reset
Download factor image (verified SHA sum)
Extracted bootloader img file and pushed to Download folder on phone by adb
Install Magisk from GitHub site
Open Magisk, select install using Select and Patch a File
I've attempted this with Stable, Beta, adn Canary builds of Magisk all with the same result.
I've looked through some bug reports on older builds of Magisk but it seems like the problem may have been resolved. Any assistance would be appreciated.
When I try flashing from fastboot, this is my output - it fails flashing the bootloader, and the boot portions.
Fastbootd allows me to flash the bootloader.img, and I can flash my patched boot file to boot_a & boot_b, but not to the boot section.
Kinda stumped, because I had no issues rooting it with Magisk.
Fastbootd allows me to flash the bootloader.img, and I can flash my patched boot file to boot_a & boot_b, but not to the boot section.
Code:
5a\barbet-rd2a.210905.003> .\flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader' (8754 KB)...
OKAY [ 0.036s]
writing 'bootloader'...
FAILED (remote: No such file or directory)
finished. total time: 0.043s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 268435456 bytes
sending 'radio' (149780 KB)...
OKAY [ 0.685s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g7250-00132-210427-B-7316661
(bootloader) Flashing partition modem_a
OKAY [ 0.558s]
finished. total time: 1.245s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: b9-0.4-7265224
Baseband Version.....: g7250-00132-210427-B-7316661
Serial Number........: 17211JECB11850
--------------------------------------------
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.930s
Press any key to exit...[Kinda stumped, because I had no issues rooting it with Magisk.
You don't want to patch the 'bootloader-barbet-b9<snip>.img file, you want to open the image-barbet-rda<snip>.ZIP, and extract just the boot.img file.
Or did I misread your post?
Nope, you read it right and that was exactly my problem. Can't believe I confused bootloader image with boot image. Thanks for straightening me out!
Hello everyone, I just upgraded to LineageOS 19.1 with MicroG for Pixel 5a (barbet) and I can't seem to get Magisk to work. I followed the official Magisk install instructions but when I flash magisk_patched.img it goes into a boot loop. Anybody know how to install root on 19.1?
If you are on LineageOs 19.1 you may be able to simply adb sideload magisk.zip from recovery wher it says apply update from adb. This worked for me on PE-Plus-barbet-12.1 for the last 6 months. Now I am testing android 13 stock and rooted it with patched boot, just look on youtube if you need step by step help, or search google for the article titled How to root pixel devices running android 13 via magisk, by droidwin, as that is the one I used to root my android 13 stock device.
Did you do what LineageOS recommended? See https://wiki.lineageos.org/devices/barbet/install . Look at item 6 under "Installing LineageOS from recovery" for their ADB sideload method.
I tried flashing Magisk-v25.2.zip via adb sideload and that method also results in a bootloop. However, I was able to recover from that by flashing boot.img from the LineageOS official zip
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
3I have a Pixel 2 XL. It's rooted on Android 10 still. I never even upgraded to Android 11 because by the time it came out I was already sick of dealing with the rooting updates. I don't care what anybody here says it's always a pain in the ass. It takes 3 to 4 hours to get everything set back up right after rooting. The time to back up everything before you start has to be considered. And when things go wrong you spend a whole weekend making them right. I don't have time for it anymore.
I most enjoy my EX kernels ability that allows me to sweep to sleep the display. I love this because it's handy and makes it so my screen off button (power button) is basically never used. It never fails this way. This means I never have to tear my phone apart to replace mechanical components.
I enjoy adaway. I enjoy YouTube vanced. I enjoy viper for Android. I enjoy substratum. I enjoy button mapper. I really, really enjoy Tulsa divers pixel launcher mods that allow me to make the buttons on the screen smaller to give me more screen real estate, but I think that hasn't been available since Android 11. You can no longer modify button icons from what I understand. I don't know if this is still true. I know there are rootless versions of substratum and the YouTube advanced, but when I last read about them years ago they were limited as compared to the root versions.
I leaned towards root being basically worthless, not worth the time, and more of a pain in the ass for a basic user who's not a developer. If I get the Pixel 5a or the Pixel 6 is rooting still worth it in 2021? Are there any rootless versions of the things I've mentioned here that would satisfy all my likes and needs I've mentioned here on Android 12 on a Pixel 5A or Pixel 6?2
Go to Settings -> About Phone. At the bottom is your build number. Go to https://developers.google.com/android/images and download the image that matches your version, probably .007.
Extract boot.img from it and adb push it to /sdcard. Have magisk patch that and save it. adb pull that patched boot.img and make sure you have OEM Unlock enabled in Developer Options. After confirming that, reboot to fastboot and run 'fastboot flashing unlock'. This will likely wipe your phone. Once that's done, reboot back into fastboot and run 'fastboot flash boot <local path to patched boot.img>' Now you have magisk installed. You can also install LSPosed and XPrivacyLua if you want to tinker with that or the Universal SafetyNet Fix at: https://github.com/kdrag0n/safetynet-fix/releases. Just download 1.2.0 and adb push it to your phone and have magisk install it.2
Yes. I use magisk, and that's exactly what I did. I have yet to (never will on this phone anymore) update to android 11 because I KNEW such a big OS change would leave my phone broken for days. One of the big things I like on my phone is Tulsa divers modified button bar icons and making the bar a lot smaller, so it uses less screen real estate. When 11 came out I read that the icons couldn't be modified. Not sure if that's correct. It's been too long. Regardless, I just stopped updating because of the potential for a bad couple days, and even when things went well I never wanted to spend the 3-4 hrs to back the phone up and get everything just like it was before after booting back up into the new update.
It's easier to update and root now than it was when I had to download the update, open it, remove "-w" from the flashall.bat file, flash twrp, flash magisk, and then re-install all the modules or the ones that were messed up or inactive from the update?2
It's full possible to be rooted via magisk and pass cts/safetynet... and also have full usage of Google Pay/Netflix/etc.. There are zero guides so far, so I've been debating making one...1
Nope, you read it right and that was exactly my problem. Can't believe I confused bootloader image with boot image. Thanks for straightening me out!
