Related
Hey here I will share OTA for our NB1 to flash with stock recovery and sdcard method.
If I'm right it will work.
Pls try and report.
Download zip file,
Copy to external sdcard
Reboot to recovery,
Choose update from SD and press power button.
I will start with June security patch.
https://drive.google.com/file/d/1G0qg1b0ZbWjvWi3_WnimY3oy0xexRyXh/view?usp=drivesdk
Powered by View 10
Will work with sideload too, right?
hi
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Unluckily it errors when installing on an unlocked phone....I unrooted it fully, rebooted to recovery and it errors always. Should I relock the bootloader to install OTAs?
No, you do not need to block the boot loader. You need to flash the previous full update 4.88B. And then upgrade to OTA.
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Topogigi said:
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Click to expand...
Click to collapse
It won't if this is block-based OTA as Magisk modifies boot partition (with Android kernel and in A/B case recovery too). Quote from Android official documentation: "block OTA handles the entire partition as one file and computes a single binary patch".
Sure, but I uninstalled magisk thus restoring original boot partition before trying to apply OTA...
dark ghost1988 said:
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Click to expand...
Click to collapse
Thanks for reporting [emoji1360]
Powered by View 10
support
does this firmware are support for Nokia 8 TA-1004 dual sim...??
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
Ok, I assume that noone had problems in updating to the june security patches with an unlocked bootloader, so there must be a problem with my device......
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
No news about July security patch?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
confirmed ..
thats what happened to me
after i unlocked my bootloader ,rooted mgdisk
after July's OTA
i cant fastboot to june stock firmware
i even tried to sideload the june OTA and it said
that i cant downgrade from July to june
Topogigi said:
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
Click to expand...
Click to collapse
Thanks Topogigi
How did you do it ?
im kinda stuck here
im considering OST LA ?
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
why666me said:
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
have you tried switching slots? it sure wont solve the issue stated but it may restore the usability of your expensive brick :laugh:
Code:
If you are currently on slot A, type this: fastboot --set-active=_b
Or on slot B type this: fastboot --set-active=_a
No Switch with locked bootloader ?
Nothing work on fastboot with locked bootloader....
issue solved using OST LA 6.0.4
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
As the title says, Magisk crashes when I try to patch the boot.img after installing the latest March security patch on my Pixel 3a.
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
biontx said:
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
Click to expand...
Click to collapse
Thanks for letting me know, should've checked the Magisk Canary thread first ^^
However, I get into a bootloop when I try to downgrade back to the February patch. Guess I'll just wait it out...
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
NinjaCoool said:
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
Click to expand...
Click to collapse
That's weird. How did you update? Magisk OTA, sideload OTA or flashing March factory image?
In any case, would you mind sharing your patched boot.img? I'm not sure I want to live without root until they fix it ^^
EDIT: Scratch that, it seems that flashing a prepatched boot.img causes a bootloop. They probably changed something in the files, that causes the issues when flashing the factory image.
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
AndDiSa said:
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
Click to expand...
Click to collapse
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Velcorn said:
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
Click to expand...
Click to collapse
If I remember correctly versions before 19.1 /7.3.x didn't support Android 10. For me 7.5.1 worked flawlessly.
yaconsult said:
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Click to expand...
Click to collapse
Weird, thanks for letting me know. I manually updated through flashing the March factory image and when I patch the boot.img through MM 7.5.1 I just get into a bootloop.
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
dkryder said:
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
Click to expand...
Click to collapse
Could you upload your patched boot.img please?
It said file too large when I tried. It's about 30MB. Not sure what's up with that.
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
biontx said:
Could you upload your patched boot.img please?
Click to expand...
Click to collapse
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobootpatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Super, tx
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Velcorn said:
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Click to expand...
Click to collapse
Sorry it didn't help, thanks for letting me know though, but I'm out of ideas now
MeowDotEXE said:
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
Click to expand...
Click to collapse
Me too. It's the first time now with the March update.
"cts profile: false"
Made an account to say I had the same problem with Pixel 3XL and I did what captain sideways posted. I went to the github for magisk, took the apk from the latest zip file release and installed that. I was able to patch my boot image afterwards. Root works fine. I flashed the patched boot image to both slots. However, the ctsProfile does fail like mentioned above.
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