Related
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
SafetyNet will always fail if your device is rooted, even with systemless mode.
SuicideFlasher said:
SafetyNet will always fail if your device is rooted, even with systemless mode.
Click to expand...
Click to collapse
anyway to bypass this with another super user tool?
No way aside from unrooting.
[email protected] said:
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
Click to expand...
Click to collapse
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
ndarkside93 said:
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
Click to expand...
Click to collapse
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
josephcsible said:
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
Click to expand...
Click to collapse
Yes magisk will pass, but SuperSU will always fail. It's not looking for the packages installed for magisk, but does look for the packages installed by SuperSU. And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
ndarkside93 said:
And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
Click to expand...
Click to collapse
I can pass SafetyNet without a custom kernel (running stock M4B30X).
josephcsible said:
I can pass SafetyNet without a custom kernel (running stock M4B30X).
Click to expand...
Click to collapse
Yes, and stock was last updated to October patch set. It became universal in the November patches
ndarkside93 said:
Yes, and stock was last updated to October patch set. It became universal in the November patches
Click to expand...
Click to collapse
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
josephcsible said:
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
Click to expand...
Click to collapse
I suppose that is true.
ndarkside93 said:
I suppose that is true.
Click to expand...
Click to collapse
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Fif_ said:
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Click to expand...
Click to collapse
SafetyNet itself will be, but to detect an unlocked bootloader, it relies on the bootloader to pass a kernel parameter that it looks at. The Nexus 5 bootloader doesn't pass any such parameter, and a bootloader update (of which there are no more) would be required for it to start.
Did anyone get this new update? I wonder what's this about. It's just around 63 MB.
FYI I've previously updated to the latest December 1 2017 patch 2 weeks ago.
skroder said:
Did anyone get this new update? I wonder what's this about. It's just around 63 MB.
FYI I've previously updated to the latest December 1 2017 patch 2 weeks ago.
Click to expand...
Click to collapse
Yep. Another small update.
Build number: N2G47H.7.12.19
Displax said:
Yep. Another small update.
Build number: N2G47H.7.12.19
Click to expand...
Click to collapse
No glaring bugs so far?
Installed. And again, no changelog. Only God knows what they've done
Enviado do meu Mi A1 através de Tapatalk
amithiel said:
Installed. And again, no changelog. Only God knows what they've done
Enviado do meu Mi A1 através de Tapatalk
Click to expand...
Click to collapse
Same here. New update with 0 info
Still with 1 December security patch level.
Any changes in the kernel ?
Yash67 said:
Any changes in the kernel ?
Click to expand...
Click to collapse
Recieved this update, cant figure out what it changed? May be getting ready for O?
Guys i recieved the updated but is stuck información step 2 (installing), what should i do??
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Bluexmorningx said:
Guys i recieved the updated but is stuck información step 2 (installing), what should i do??
Click to expand...
Click to collapse
Just wait, it took time on mine but completed eventually.
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Micka84 said:
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Click to expand...
Click to collapse
mine is 7 december
goofball2k said:
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Click to expand...
Click to collapse
Can u tell me how u restored boot image?
goofball2k said:
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Click to expand...
Click to collapse
Can you please describe what you have done? Would also be interesting for me. I tried to restore stock boot image via Magisk Unistaller (Magisk-uninstaller-20171222.zip) in booted (not installed) TWRP. And also directly with fastboot from fastboot ROM image with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Both attemps ended with a bootlop. After i installed Magisk via TWRP again, the bootloop was gone and system booted as before (but i cannot install the update via updater then). Thanks!
Can anyone on N check if a /dsp partition is mounted?
If it is, it confirms that this update is a preparatory one for O.
ur0 said:
Can anyone on N check if a /dsp partition is mounted?
If it is, it confirms that this update is a preparatory one for O.
Click to expand...
Click to collapse
Today Update
I updated directly from October to December (not the new patch, the first December one) without problems using the OTA updater & I'm rooted with Magisk.
First I unlocked the bootloader, temp booted TWRP using fastboot boot and flashed Magisk 14.5 using that. This way recovery is not modified & I can still root - did not allow system modifications in TWRP. No data was wiped and it worked fine.
For updating I used the instructions here (restore stock boot > step 1 OTA > Install Magisk to 2nd slot in app > step 2 OTA > Done. kept root and did OTA successfully.
Hope this helps people stuck with OTAs, it worked for me.
Micka84 said:
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Click to expand...
Click to collapse
Same Here.
I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
aditsubrata said:
I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
Click to expand...
Click to collapse
you must wait until several hours or days again
Sent from my Mi A1 using Tapatalk
aditsubrata said:
I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
Click to expand...
Click to collapse
If u can't wait u can flash a pre rooted stable oreo
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
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