Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons
Related
So as the official bootloader unlock broadened the audience of this from tinkerers/developers to basically everyone I thought this guide might me helpful for some...
PREREQUISITES:
- Unlocked bootloader (official or unofficial)
- latest magisk manager installed on phone (https://github.com/topjohnwu/Magisk/releases)
- latest fastboot and adb binaries from google(https://developer.android.com/studio/releases/platform-tools)
- latest twrp.img to boot (NOT FLASH), zip not needed (https://eu.dl.twrp.me/NB1/)
- Fully stock partitions (if you do not have this reflash latest stock via ostla), as OTA updates will do a integrity check.
- PC with WIN/OSX/LINUX with USB port^^ (on windows you might have to add .exe to the commands)
- disable automatic system updates in developer options, as you will still have to manually root the updated partition, so this makes sure you don't miss it. You still get notifications on available updates and can apply them easily(as you will see)
SETUP_STEPS:
1. Go into Magisk manager and "just download" the latest zip
2.1 Run
Code:
adb reboot bootloader
or reboot into download/fastboot mode via other means
2.2 Run
Code:
fastboot boot twrp-3.2.3-1-NB1.img
(change this when your version of twrp differs)
2.3 Flash the .zip magisk downloaded in 1.)
2.4 Reboot.
Congratulations you now have root!
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
ALTERNATIVE GUIDE (without twrp, using prerooted boot.img)
(works for newest patch level, where twrp isn't working yet)
this guide works on newest patches as long as someone provides a prerooted boot.img.
So basically you either need a boot.img available or twrp...
Hopefully this helps until TWRP is compatible with September Security Patch
LINKS:
stock boot.img: (may to october patches)
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
prerooted boot.img: (may to october patches)
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
PREREQUISITES:
- same as above minus twrp
- patched/prerooted boot image (either create it yourself or use link provided here)
STEPS_TO_ROOT:
0.
Code:
adb reboot bootloader
or get into download mode otherwise
1.
Code:
fastboot boot NB1_prerooted_boot.img
1.1. The phone will boot into an temporarily rooted state,
2. Use magisk manager-> Install -> "Direct Install" to persist the root.
3. Reboot
Congrats you now have root even on versions where twrp isn't working yet....
Edit1:
Added link to all stock boot images from may to october security
Edit2:
Did the same for magisk prerooted
Edit3:
Added November images thanks to @czupyt
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Trissi said:
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Click to expand...
Click to collapse
That would be much appreciated. Alot of people who just unlocked bootloader cant root and the maintainer of our TWRP will take a couple of days
indeed
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
LoaderFabi said:
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
Click to expand...
Click to collapse
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
ironman38102 said:
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
Click to expand...
Click to collapse
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
LoaderFabi said:
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
Click to expand...
Click to collapse
No I get that but its just that I forget cuz this is my first phone with a/b partition. Anyway I got the phone to latest patch rooted so I'll see if I can get the untouched img
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
eric194 said:
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
Click to expand...
Click to collapse
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Trissi said:
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Click to expand...
Click to collapse
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
So did the prerooted Image Boot?
If so it basically has to be your boot/system partition(I had mine compromised too and couldn't fix it with just flashing boot.img had to reflash everything via ostla)
If even the prerooted Image didnt boot im sorry i don't really know how to help, as I have working root with Magisk on September patch and the Image boots just fine for me....
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Trissi said:
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Click to expand...
Click to collapse
Ok I will try that hope it'll work
Edit : thanks dude it worked
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Xayar said:
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Click to expand...
Click to collapse
Flash the full Stock build (i think its even may patch), via ostla (https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487), then follow this guide then reapply all updates by following the update steps...
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Xayar said:
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Click to expand...
Click to collapse
Are you trying to use OST LA 6.1.2? Cuz that doesnt work
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
These files are to install Magisk. Please only flash it if you are already on March update. This is not March OTA!
Link courtesy of @i5lee8bit; March OTA patched with Magisk 20.4 https://www.androidfilehost.com/?w=files&flid=306923
Dear Mushtafa, great thanks to you! I've been looking for this all day. Thank you!
mushtafa said:
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
Click to expand...
Click to collapse
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
onlyguynamedniles said:
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
Click to expand...
Click to collapse
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
mushtafa said:
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
Click to expand...
Click to collapse
No I'm still on January, I never got the Feb OTA and didn't bother to try manually since it didn't seem significant enough but I wanted this March update because of the new Pixel drop feature set.
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
mushtafa said:
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
Click to expand...
Click to collapse
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
otrobruno said:
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
Click to expand...
Click to collapse
You flashed the March boot.img on your February firmware? Why?
mushtafa said:
You flashed the March boot.img on your February firmware? Why?
Click to expand...
Click to collapse
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
otrobruno said:
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
Click to expand...
Click to collapse
If you're not getting the March OTA, you need to download it from Google and sideload it. https://developers.google.com/android/ota
There is a thread here somewhere which shows how to do this.
The boot.img I shared above is for people who need it for Magisk and saves them downloading the ~2GB factory file.
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
wonderlander17 said:
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
Click to expand...
Click to collapse
Affirmative :good:
dang is it that hard to understand . if youre build number does not look exactly like this QQ2A.200305.003 then do not use these boot.img's
its that simple this is not to upgrade you to the march sec patch with root this is for people already on the march sec patch to use to gain root
FIXED IT!! After taking the March update I flashed this patched img the phone boots up to a black screen. If you use the power button it brings up a White menu with "power off" "restart". So then I turn the phone off and load fastboot and flash the stock boot img and everything works again. Any ideas? Figured it out.... Magisk modules that were running.
Can you flash any of them without the use of a computer?
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Nope. TWRP or any other recovery is not yet compatible.
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Yes with ex kernel manager it's possible
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
i5lee8bit said:
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
Click to expand...
Click to collapse
Added to OP, cheers
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Thank you :fingers-crossed:
I'm still on Android 8.1 and waiting stable Android 10
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
ony89 said:
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
Click to expand...
Click to collapse
If you have a locked bootloader, you can't do anything.
Magisk and root is separate to TWRP on this phone. This image will help you get Magisk installed.
Instructions here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Thank you!
wassupjg said:
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Click to expand...
Click to collapse
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
a1291762 said:
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
Click to expand...
Click to collapse
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
wassupjg said:
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
Click to expand...
Click to collapse
I'm not totally sure...
There are links to the OTA zips around. A thread about Android 10 showed how to install one using the stock recovery... I guess the same works for 10.0.20.0?
As a Linux user I would be inclined to try and use command line tools to install the OTA zip... But I don't even know if that's a thing
wassupjg said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Click to expand...
Click to collapse
Thanks dude, I did find it here in the posts, I guess the OP isn't updated anymore, I've just had too many problems with Q, it sucks imo, once I back up everything I'll give it a go, by any chance do you know any good app and general backup apps that make things easy?
wassupjg said:
by any chance do you know any good app and general backup apps that make things easy?
Click to expand...
Click to collapse
I bought titanium backup pro a long time ago and still use it. Back in the day, the free version was annoying for whole device restore. But it's let me move across 5 devices and saved me from losing data on many occasions so I consider it money well spent.
I backup and then rsync /sdcard to a computer daily (CLI tools from cron). For restore I copy the files back (if needed) and then restore.
I only backup user apps, call history and SMS. System apps don't restore properly these days.
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
ViruuZ said:
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
Click to expand...
Click to collapse
You need to patch the new boot.img.
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
Thanks for reply! So i extract my current boot.img, but how to patch it?
ViruuZ said:
Thanks for reply! So i extract my current boot.img, but how to patch it?
Click to expand...
Click to collapse
Open Magisk manager app
Select install magisk
Select and Patch a File
Copy new patched boot.img to pc
Flash
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Found my current firmware, will extract it there. Thanks anyway!
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Normally you have to go to google firmware page and download it.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Are you guys having the SafetyNet passed?
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
No you don't. You only have to repatch the new boot image when a new major Android revision comes out. For example going from Android 11 to 12. I've updated my Pixel 5 every month a new update comes out. And I've always used the same boot.image file. No need to keep wasting your time patching that file. When you look through the OTA files you'll notice that none of those files in the zip file are a boot.image file. Meaning it doesn't touch it when it's doing the OTA.
xT29c said:
You only have to repatch the new boot image when a new major Android revision comes out.
Click to expand...
Click to collapse
That is kind of useful, thank you for sharing. Can someone confirm this?
@hanni2301 Have you succeeded in getting root back ? I got the same problem today....
Why do you ask me?
I always patch the actual boot.img out of the monthly factory image with magisk (beta or Canary) first and flash then the factory image, reboot, flash boot boot.img and afterwards the custom kernel.
@xT29c said that you can reuse ure patched boot.img from last month, as it changes only between different mayor Versions.
So you can save some time, but the process is still the same.
IMO, yes, you should always patch the new boot.img from each months new factory image in Magisk when re-rooting.
Do you need to? i suppose that's up to you. However I think you should want to.
Essentially, you're missing out on any code changes/fixes, etc that Google may have added to the new months kernel.
~ Maybe an idea for a new thread to upload the Pixel 5 stock boot.img from each months new OTA, along with a Magisk patched boot.img. ~
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
leveleyed said:
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
Click to expand...
Click to collapse
I am not sure, but this may be because Magisk Manager is no longer..
get v22
New v22.0 update merges Magisk and Magisk Manager app
Samsung's Galaxy S21 series is now supported too
www.androidpolice.com
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img