Magisk
Magisk copied to clipboard
topjohnwu
Secure Check Fail recovery.img while rooting Samsung galaxy Tab A 8.0 LTE [SM-T295]
Device:Samsung Galaxy Tab A 8.0 LTE SM-T295 Android version:11 Magisk version name:8dfb30fe Magisk version code:24313
![image] (https://user-images.githubusercontent.com/64535064/170646405-2a59f54f-36e2-4f29-b5a3-3bb30772ca88.jpg)
Patch the boot.img only and flash a disabled vbmeta.img
It wont work bcz magisk says ramdisk No
https://topjohnwu.github.io/Magisk/boot.html
Is there a way to check in which type [1,2,3,4]category does my device belongs to
your ram disk is located in your recovery and not in the boot img file 2019, samsung devices same as mine sm-n975u but i digress Download the firmware select the AP file and patch the ap.tar.md5 file using magisk app you will get a patched.tar file use that patched file in the ap slot
XDA has more info search multi disabler for more info
your ram disk is located in your recovery and not in the boot img file 2019, samsung devices same as mine sm-n975u but i digress Download the firmware select the AP file and patch the ap.tar.md5 file using magisk app you will get a patched.tar file use that patched file in the ap slot
XDA has more info search multi disabler for more info
After that my device get stuck in "Secure check fail recovery.img" And it doesnt boot back to system from there
https://topjohnwu.github.io/Magisk/boot.html
Is there a way to check in which type [1,2,3,4]category does my device belongs to
Type III (A-only legacy SAR) in John's doc.
I posted XDA workaround here: https://github.com/topjohnwu/Magisk/issues/5854#issuecomment-1136450313
This also allows Magisk in boot to work...
It would be good to see a proper (integrated) fix however...
https://topjohnwu.github.io/Magisk/boot.html
Is there a way to check in which type [1,2,3,4]category does my device belongs to
Type III (A-only legacy SAR) in John's doc.
I posted XDA workaround here: #5854 (comment)
This also allows Magisk in boot to work...
It would be good to see a proper (integrated) fix however...
In XDA the guide is not for my device i agree same model but different region and on android 11 with one ui 3.1 but it for android 10 Edit : I already seen that before posting issue here
In XDA the guide is not for my device i agree same model but different region and on android 11 with one ui 3.1 but it for android 10...
Sorry, how is it not for your device?... Didn't you upgrade thru One UI 2.x, Android 10?
https://topjohnwu.github.io/Magisk/boot.html
Is there a way to check in which type [1,2,3,4]category does my device belongs to
Type III (A-only legacy SAR) in John's doc. I posted XDA workaround here: #5854 (comment) This also allows Magisk in boot to work... It would be good to see a proper (integrated) fix however...
In XDA the guide is not for my device i agree same model but different region and on android 11 with one ui 3.1 but it for android 10 Edit : I already seen that before posting issue here
Sorry, how is it not for your device?... Didn't you upgrade thru One UI 3.1, Android 10?
My device currently running Android 11 with one ui 3.1 and 1 Nov 2021 -android security patch
Ok, so johnt1989 and I are both saying Magisk in boot can work on your device despite no OEM ramdisk in boot... I'm guessing that w/ Android 11, BL v4 and anti-rollback may prevent you from using that solution however... I wasn't suggesting you settle for that workaround/hack in any case... As I said,
It would be good to see a proper (integrated) fix however...
Ok, so johnt1989 and I are both saying Magisk in boot can work on your device despite no OEM ramdisk in boot... I'm guessing that w/ Android 11, BL v4 and anti-rollback may prevent you from using that solution however... I wasn't suggesting you settle for that workaround/hack in any case... As I said,
It would be good to see a proper (integrated) fix however...
Ok i will wait for the fix
Ok, so johnt1989 and I are both saying Magisk in boot can work on your device despite no OEM ramdisk in boot... I'm guessing that w/ Android 11, BL v4 and anti-rollback may prevent you from using that solution however... I wasn't suggesting you settle for that workaround/hack in any case... As I said,
It would be good to see a proper (integrated) fix however...
Ok i will wait for the fix
removed the screen sbot and re added it due to battery icon wasnt nice
Ok, so johnt1989 and I are both saying Magisk in boot can work on your device despite no OEM ramdisk in boot... I'm guessing that w/ Android 11, BL v4 and anti-rollback may prevent you from using that solution however... I wasn't suggesting you settle for that workaround/hack in any case... As I said,
It would be good to see a proper (integrated) fix however...
Ok i will wait for the fix
removed the screen sbot and re added it due to battery icon wasnt nice
Your device binary is U7 mine is U4 and also it gives the warning after flashing it
if you flashed a unlock token to unlock the bootloader do not update the bootloader bit number
if you flashed a unlock token to unlock the bootloader do not update the bootloader bit number
What is unlock token and Bootloader bit number?
contact me on discord Slug#4106 i feel this topic has went offtopic
Ok i will be there in 2 minutes
Still waiting for an update on the U4 bootloader. Still with the secure check fail error.
According to #6226 removing vbmeta.img from AP.tar before patching/flashing might help. Have you tried that?