Database Develop

Patching boot.img for BV6300 Pro (Helio P70 / MTK)

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!!!

M2004J19AG with boot loop. Want to install TWRP and custom ROM

Hello.
I tried to install TWRP but no luck, only managed to have a constant bootloop. I can enter the menus (vol+ and power pushed, vol- and power pushed).
I tried different roms, no luck.
I managed to install TWRP from this: {Mod edit}
I tried to install different roms:
{Mod edit}
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I installed vbmeta
[ROM][10.0][LANCELOT] PixelExperience [AOSP]
PixelExperience for Redmi 9 [lancelot] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
fastboot --disable-verity --disable-verification flash vbmeta vbmetaredmi9.img
I tried XiaoMiTool V2, unable to unbrick.
Now I have a brick. No TWRP. No ROM. Bootloop.
7 days waiting for bootloader unlocking? I'm very upset with Xiaomi, really.
ColdIce tried to help me. No luck.
Any hope? Any help? I always wipe partitions. I don't know what to do with this.

Something is happening
Tried flashing my favourite custom rom right now, same recovery,same rom, same kernel , same version,older miui version,same flashing steps
Gets stuck in bootloop now while it didnt before
Something actually bad is hapenning
have been stuck on this:
rom boots into setup
setup works partily
system reboots after getting into the set up
rom tries booting again but something prevents it from booting and just reboots
(i can see it finishes booting but doesnt start)
this seems to be a thing with all custom roms???
why is this happening now
might be the case with the stock rom also my god why the ****

What's happening?
I see there's MiFlashPro tool...
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com

I am ColdICe and i dont understand this?
Nothing changed, there shouldnt be anything stopping it from working, but it doesnt
work
This seems to be a problem with all custom roms and does not include stock roms
The custom roms i know worked couple of days ago, i truly dont know why this is
happening
I was able to reflash the stock rom through a "recovery rom" with no issues
seems like you will have suck it up and enjoy using stock miui
(other than the first boot being a bootloop)
I was using miui 11.0.4 before flashing a custom rom
If any of the guys that port the custom roms want to look into this i would be greatful
Ive tried using "eOS" which has a boot animation which says "my data is MY data" when it finishes booting, so you can tell when it boots
when i boot into the rom it works until i enter the set up , after i do it crashes into a bootloop, i can see that it boots (due to animation) , but just keeps rebooting
If anybody is willing to test this, because i am not anymore, try flashing the vanilla build of arrow OS (link) since it does not include a set up screen
Does this rom also bootloop?, since it seems to be related to a set-up screen (???)
Also do GSI ROMs also have the same issue? If you try theese, please post your findings in the comments
edit: formatting and a small remark

Whats your phone Redmi 9/9 prime/9 power/9T/9C/9A

MRBLYAT said:
Whats your phone Redmi 9/9 prime/9 power/9T/9C/9A
Click to expand...
Click to collapse
This is a thread about redmi 9 lancelot, we both have the same phone

Try this Recovery and modded vbmeta. Still can access fastboot or not????
MRBLYAT said:
Try this Recovery and modded vbmeta. Still can access fastboot or not????
Click to expand...
Click to collapse
while flasing vbmeta need --disable-verity and --disable-verification
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android

MRBLYAT said:
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android
Click to expand...
Click to collapse
Hello, sorry for the late post, however its detailed in the post that this was already done

MRBLYAT said:
Try this Recovery and modded vbmeta. Still can access fastboot or not????
Click to expand...
Click to collapse
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot

i
pleasehelpmeiamscared said:
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot
Click to expand...
Click to collapse
its ok it don't have any virus or ransomware

pleasehelpmeiamscared said:
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot
Click to expand...
Click to collapse
Hey how your phone, its good or not.....

MRBLYAT said:
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android
Click to expand...
Click to collapse
Hi I have a M2004J19AG and this does not work I still have the original recovery.

mispela said:
Hi I have a M2004J19AG and this does not work I still have the original recovery.
Click to expand...
Click to collapse
Are you use platform tools from android

MRBLYAT said:
Are you use platform tools from android
Click to expand...
Click to collapse
Yes I using fastboot and adp but I can flash my recovery but just allways for onces and after I reboot my phone its is gone again. Do u know maybe why this happens?

mispela said:
Yes I using fastboot and adp but I can flash my recovery but just allways for onces and after I reboot my phone its is gone again. Do u know maybe why this happens?
Click to expand...
Click to collapse
How like your recovery is return to stock recovery or no recovery

MRBLYAT said:
How like your recovery is return to stock recovery or no recovery
Click to expand...
Click to collapse
I have no idea how maybe it is just running on the RAM but I dont unterstand why because I flashed it like allways with "fastboot flash recovery".

mispela said:
I have no idea how maybe it is just running on the RAM but I dont unterstand why because I flashed it like allways with "fastboot flash recovery".
Click to expand...
Click to collapse
You can try this
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com

Moderator Announcement
I've removed all references to Telegram from this thread. As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to this thread. Please refrain from sharing of social media in future. Thanks for your cooperation!
Additionally, unless you already know Telegram is not accepted on XDA as a filehost because a download of a ROM would require a registration on Telegram.
Regards
Oswald Boelcke
Senior Moderator

Ozip links for Realme 6 (RMX2001)

OZIP's FOR RMX2001​​«Android 10»​ㅤㅤ ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ Click Here
«Android 11»​*Team Drive Gone Will Find And Update
​Need Help?
Contact Me On Telegram
-GROUP LINK-

Awesome!! Can I dirty flash ui2?

Android 11 update (C12 Global) failed, why?

Not flashing ui 2

Ferbir88 said:
Android 11 update (C12 Global) failed, why?
Click to expand...
Click to collapse
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group

xdriv3r said:
Not flashing ui 2
Click to expand...
Click to collapse
u cant flash it by stock recovery read other comment reply

unique_sandesh said:
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
Click to expand...
Click to collapse
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery

Ferbir88 said:
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Click to expand...
Click to collapse
tell meyour all process sir , and they also need format

unique_sandesh said:
unique_sandesh said:
tell meyour all process sir , and they also need format
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

unique_sandesh said:
tell meyour all process sir , and they also need format
Click to expand...
Click to collapse
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop

ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata

unique_sandesh said:
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.

Ferbir88 said:
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Click to expand...
Click to collapse
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg

unique_sandesh said:
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
Click to expand...
Click to collapse
Thank you very much!

Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply

Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
were the same situation and i dont know what to do. Please help us.

which is the process 4 install? im on rui 1.0

Kodize said:
which is the process 4 install? im on rui 1.0
Click to expand...
Click to collapse
using custom recovery
Rollback With Custom Recovery
This Method Only For Realme 6/6i(indian)/6s _____________________ RMUI2.0 TO RMUI 1.0____________________________________________ This Method For Downgrading From F2Fs Based Custom Roms ⓿ Flash Latest TWRP (Gofaraway One) ❶ Go to manage partitions And Select...
telegra.ph

Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7

unique_sandesh said:
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
Click to expand...
Click to collapse
Hi guys, did someone do this ? i'm in the same situation after rolling back to B55 using stock recovery, now stuck on B65, no update coming.
Bootloader is unlocked, when i flash a C18 firmware with SPF phone bootloop in fastboot mode.
Only flashing a B65 firmware with SPF to get phone boot corretly.
I just need to known if this method is tested with the given C19 firmware ?
Many thx.

Question Can't Roll Back

I updated to MIUI 13 from miui.EU and now I can not go back to an older ROM even with full data formatting. I am seemingly stuck on this ROM. I really don't like it. Is there any way to go back?

Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot

I just back to MIUI 12.5 EU from MIUI 13 EU, and I don't have problem

Hpotersept2 said:
Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot
Click to expand...
Click to collapse
Will this work? It gave me an anti roll back notice before

[email protected] said:
I just back to MIUI 12.5 EU from MIUI 13 EU, and I don't have problem
Click to expand...
Click to collapse
I think OrangeFox was my problem I used it on the first install. I went back to TWRP but the damage was done.

Hpotersept2 said:
Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot
Click to expand...
Click to collapse
I tried it. It won't flash.

What if I try a non Mi ROM first? Will that fix it?

Supermatt01 said:
What if I try a non Mi ROM first? Will that fix it?
Click to expand...
Click to collapse
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom

Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
I'll try it that way.

Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
I'm trying to find the vendor and fw

Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
No good.

Supermatt01 said:
I tried it. It won't flash.
Click to expand...
Click to collapse
Of course it won't, because the flash_all.bat has a couple lines in the beginning that have anti-rollback, you have to modify it with notepad, just open with notepad and delete those lines, then save it and flash normally.

Hpotersept2 said:
Of course it won't, because the flash_all.bat has a couple lines in the beginning that have anti-rollback, you have to modify it with notepad, just open with notepad and delete those lines, then save it and flash normally.
Click to expand...
Click to collapse
Which lines? When I tried that, it would not start.

I did it, it won't work.

I think I fixed it I took the fastboot script out of the miui 13 update and put it in the folder for the miui 12 fastboot. It stared the old boot logo. It is started now. I hope it is stable. Thank you all for the help and suggestions.

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything