Related
Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Do i need a computer for this ?
techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.
mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx
techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img
cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread
Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?
jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk
Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.
i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you
Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha
Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?
Any solution for this, or any suggestions to try??
Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.
You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!
First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.
We must unlock the bootloader with fastboot mode or we can do it through developer options??
black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.
-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!
I just received my Galaxy Ultra SM-G998B. Anyone had successfully root your gs21 using magisk? How's the safety net?
Like to hear any feedback before rooting my phone.
Tnx
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Try magisk canary
I tried rooting the regular S21 but without success yet ( https://forum.xda-developers.com/t/...e-links-and-flashing-discussion-here.4220563/ )
Try magisk canary
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Ziomus said:
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Click to expand...
Click to collapse
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
rodrigofd said:
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
Click to expand...
Click to collapse
thanks for your reply, i updated my OP with all the infos
peterkoarl said:
thanks for your reply, i updated my OP with all the infos
Click to expand...
Click to collapse
Couple things:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
rodrigofd said:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
Click to expand...
Click to collapse
i used CSC, not HOME_CSC - i thought that would mean that data gets wiped?
i did not manually do anything in regards to formatting. what .. could i do?
rodrigofd said:
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
Click to expand...
Click to collapse
yeah i remember that as well from older devices; i let it sit for at least 10 minutes on the initial flash to make sure, so im pretty sure its stuck.
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
peterkoarl said:
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
Click to expand...
Click to collapse
Have you tried patching just the raw boot.img file? (Not tar'ed)
You need to uncompress the boot.img.lz4 file first, so you get a boot.img, copy that file to the phone, and select it with Magisk app.
Then get back the patched *.img file into the PC, rename it back to boot img, put it in a TAR, and flash that TAR with Odin.
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Patch the extracted the boot.img first and rename the patched boot to "boot.img" BEFORE (not after) compressing it to tar.
Also ensure to enable OEM unlocking in Developer options before flashing the patched boot tar
thanks for all the replies.
i tried the "boot.img only" approach first; makes no difference. magisk says it patched it fine, renamed it back to boot.img, tar'ed it into boot.img.tar, flashed that via odin without autoreboot. cant even get into recovery after restarting.
EDIT: i WAS able to enter stock recovery now; i realized that since i need to have the pc/usb cable connected to be able to enter download mode, maybe i need the same for recovery - and yes, volup+power while cable is connected does drop me into recovery. however, even after factory reset there, it wont boot.
EDIT2: yes my bootloader is unlocked, oem option in dev is greyed out.
EDIT3: i re-did the boot.img-only approach and made sure that i got into recovery IMMEDIATELY after odin this time; did a factory reset and cache wipe. hit power off. powered the phone back on. stuck on samsung logo. this does not seem to be going anywhere.
i didnt know anything about vbmeta before, starting to google it now.
DaReDeViL said:
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
Click to expand...
Click to collapse
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
peterkoarl said:
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
Click to expand...
Click to collapse
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
DaReDeViL said:
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
Click to expand...
Click to collapse
thanks, tried, no difference
looking closer at your img, it seems to hold keys for the SM-G981B (Galaxy S20).
i *guess* i need the same thing for my model - my research into how this is done has unfortunately so far been unfruitful....
some more info; when unpacking stock AP, i get the following files:
24/01/2021 14:22 19.864.283 boot.img.lz4
24/01/2021 14:22 658.262 dtbo.img.lz4
24/01/2021 14:25 1.130 metadata.img.lz4
24/01/2021 14:22 2.769 misc.bin.lz4
24/01/2021 14:22 45.072.126 recovery.img.lz4
24/01/2021 14:25 6.207.213.323 super.img.lz4
24/01/2021 14:25 734.568.963 userdata.img.lz4
24/01/2021 14:25 3.751 vbmeta.img.lz4
24/01/2021 14:25 2.815 vbmeta_system.img.lz4
24/01/2021 14:22 12.136.709 vendor_boot.img.lz4
is it possible that this vendor_boot.img is interfering with magisk?
do i need to touch vbmeta_system somehow?
are any of these "new", as in, magisk cannot handle that stuff (yet)?
Try following this guide for the S20 series as it should be the same theoretically. I'm gonna try it as soon as I get my s21 ultra
We got our first recovery for Samsung M40 (SM-M405F). This one is ported using Samsung Auto TWRP recovery porter by Team Hovatek
Please try and let everyone know if it works for you or not.
(If you want to do it yourself for any other Android OS version, you can refer to the original Hovatek post.)
You must disable dm_verity before flashing TWRP.
TWRP based on version: 3.5.*
Details of base recovery used for porting:
Source: Extracted from downloaded firmware
Version: Android 11
Build Date: Mon, 12 Apr 2021 07:54:43 +0000
Security Patch Level: 2021-04-01
Product code: INS
PDA: M405FDDU2CUD2
CSC: M405FODM2CUD2
If this works for you, please post here so everyone will know.
If something goes wrong you need and any stock img/file let me know, I will share that too.
Update 1 =>
NOTE: Unfortunately, I can not test this recovery for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Update 2 =>
Instructions for NON-Rooted and Bootloader locked device-
Unlocking Bootloader:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Disable DM_Verity (Android Verified Boot):
Copy the vbmeta.img (download from attachments) into your adb and fastboot folder
You can now flash the vbmeta.img using fastboot to remove dm_verity from your device
// Enable USB Debugging and enter following commands in CMD/Terminal after connecting device to computer.
adb devices
// You should see your device listed
adb reboot-bootloader
// Device should reboot to bootloader
fastboot devices
// You should see your device listed
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
// OR if the command above doesn't work, try below
fastboot flash vbmeta vbmeta.img
// DONE
////////////////////////////////++++++++++++++++++++++++++////////////////////////////////
Note: For Magisk Rooted devices above steps are not required, as Magisk already patches vbmeta.img and disabled dm_verity (Android Verified Boot)
Flash TWRP with/without Root using Odin
1. Download and install Odin on your PC
2. Download the attached recovery.img, convert it into .tar
3. Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
4. Select recovery.tar under AP_ and Uncheck “Auto Reboot” in Options!
5. Flash the device
6. Now do not power on to System, enter into Recovery/TWRP mode using key combination.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
*DONE*
Enjoy TWRP!
Can you tell step by step procedure for flashing twrp in m40.
How to disable dm-verity?
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Shashvatsawar said:
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Click to expand...
Click to collapse
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
did you already tested it on your device??
rohitrss said:
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
Click to expand...
Click to collapse
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
deadinside322 said:
did you already tested it on your device??
Click to expand...
Click to collapse
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Thread title and note updated.
Shashvatsawar said:
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
rohitrss said:
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
Click to expand...
Click to collapse
I tried it But I am not able to boot into recovery then.
It just reboots.
Shashvatsawar said:
I tried it But I am not able to boot into recovery then.
It just reboots.
Click to expand...
Click to collapse
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Akhil137 said:
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
rohitrss said:
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
Click to expand...
Click to collapse
I followed this thread to root my device
https://forum.xda-developers.com/t/root-sm-m405f-galaxy-m40.3951491/
There was no option of dm verity while patching stock rom using magisk.
Though My phone was successfully rooted.
I can't use fastboot as it's not showing my device in devices list ( tried a lot).
Finally I flashed your recovery using odin but after going to recovery mode it rebooted only. For recovery mode I tried key combination first and then a root app after device booted.
Updated post with detailed flashing instructions.
rohitrss said:
Updated post with detailed flashing instructions.
Click to expand...
Click to collapse
did the recovery work for you?
Is there any update?
When i try to go to bootloader, my device always go to download mode. how can i fix this???
rohitrss said:
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Click to expand...
Click to collapse
Bro, I am going to use twrp in my main phone M40.
And I don't care if it gets bricked :>
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?