Database Develop

Twrp 3.0 recovery

TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1

How do we go about to install this

jemmini said:
TWRP Recovery v.3.0 for BLU_VIVO_XL (gionee6753_65u_l1)
based on firmware version BLU_V0030UU_V07_GENERIC_5.1_20160126-1033 / Tue Jan 26 10:33:33 CST 2016 / Android 5.1
Click to expand...
Click to collapse
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.

ItGuyJax8430 said:
Is this confirmed to work? I tried flashing the TWRP for the Blu Pure XL and the phone boot looped. I was able to unlock the bootloader ADB but after flashing TWRP the phone bootlooped.
Click to expand...
Click to collapse
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.

jemmini said:
flash the original recovery (from fastboot mode).
loading recovery and system loading - are two different things...
p.s. recovery was tested.
Click to expand...
Click to collapse
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.

ItGuyJax8430 said:
10-4 ill give the recovery a go. I knew there was a difference, I was just giving extra info on my situation. I just got my replacement phone in today, ill give the recovery a go.
Click to expand...
Click to collapse
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...

It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.

During the loop, I get this message.

after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...

jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.

jemmini said:
after unlocking the bootloader you need for the first time to boot the system with the original recovery. and only after that to flash the TWRP...
Click to expand...
Click to collapse
Can you provide step by step instructions?
I imagine it would be something like this.
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit?
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
xdadev_user11 said:
jemmini, do you have a backup of the stock rom? If so, can you upload it? Thank you.
Click to expand...
Click to collapse
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus

emowing said:
Can you provide step by step instructions?
Click to expand...
Click to collapse
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.

jemmini said:
give me the boot.img and recovery.img files from your firmware. and the file /proc/emmc from the system
and I'll make TWRP for you...
Click to expand...
Click to collapse
I'm planning on trying out TWRP later today. Before I do that, what files should I grab (as a backup) and from where should I grab them? I'm happy to upload them for others, too.

So I will be able to root the phone with this? After unlocking bootloader and flashing twrp I flash supersu?

jemmini said:
1. Developer Options > Enable OEM Unlock
2. Enable USB Debugging
3. Reboot to bootloader
4. fastboot oem unlock
4.1. fastboot oem unlock confirm
5. fastboot reboot? (boot back into system) << i think this is where people are getting boot loop
6. reboot to bootloader
7. fastboot flash recovery (twrp recovery.img)
8. reboot to recovery
9. profit.
Click to expand...
Click to collapse
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.

emowing said:
@jemmini I've never heard of the command fastboot oem unlock confirm before. Is this a command to run or do you mean we should do a fastboot getvar all and check the bootloader unlock status for a yes? Sorry for the newbie question. I've never needed to do this with a nexus.
Click to expand...
Click to collapse
The confirmation he means is after you execute the unlock command, on the phone screen asks you to confirm by press volume up. That all.

[del]

xdadev_user11 said:
It works. Thank you jemmini!
Edit: It appears I spoke too soon. Recovery works, but now the phone is in a constant boot loop.
2nd update: By some miracle, I got the phone to stop looping and just stay on recovery by randomly pressing buttons.
Click to expand...
Click to collapse
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.

acotto said:
The same thing happened to me.
After I was able to get into recovery using your steps, I formated ONLY the /data partition and rebooted. The phone then booted up properly after that.
I then downloaded the SuperSU ZIP file and rooted my phone through recovery .
I hope this helps someone.
Click to expand...
Click to collapse
Nice find :good:. I'll try it when I get my phone.. it will be delivered today.

emowing said:
If you have no other option, you can try this.. http:// firmwarefile.com/gionee-s-plus
Click to expand...
Click to collapse
So I unlocked bootloader and also got the bootloop. I flashed this firmware to fix it, but I found out the radio included is not the same as the US version, so now the sim cards don't work.
The firmware image have a file called "MT6753_Android_scatter.txt" which determine what partition to flash. Base on this guide http://www.mtkroms.com/2015/03/how-to-restore-lost-imei-on-any.html, the "secro" partition being replaced may be what caused the issue, so looked like that's what I have unchecked before flashing.
jemmini said:
..
Click to expand...
Click to collapse
I just discovered that you can back the secro and many other partition within TWRP. I don't know if that alone will fix the sim problem. WRONG

Nokia 8 won't boot to TWRP?

So, I wiped all data, system, cache, internal storage using TWRP and then I flash the system.img to System Image and boot.img to Boot into 2 slots (A & B). Consequently, I lose TWRP and root. I have gone back to May Security Patch Nokia 8 TA-1004. I have updated and updated up until October 2018 Patch.
Then, I tried to use "fastboot boot twrp.img", however it doesn't work. It is just stuck to POWERED BY ANDROID LOGO. Flashing twrp will break the wifi and I do not want that. Anybody has solutions for this? I can't get it to boot to TWRP. I use Android stock recovery and apply update in SD Card, not working as well.
I really want to have access root. All because of that stupid random restart occurs in this thread https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
Note: During flashing system.img which reverts back to stock one, I didn't use fastboot command. I use TWRP to revert back.

Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
Is this the latest stock boot image (october patch)?

For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot reboot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.

Topogigi said:
Is this the latest stock boot image (october patch)?
Click to expand...
Click to collapse
Um I think cuz Magisk took this backup right during the Install to Second Slot option

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
This is October patch? If it does, you are a lifesaver.
ValKyre said:
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot boot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Click to expand...
Click to collapse
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.

godofknife said:
This is October patch? If it does, you are a lifesaver.
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
Click to expand...
Click to collapse
Yup ... Sorry with my head not remember true command hehe

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
Click to expand...
Click to collapse
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img

Mo4o293 said:
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Click to expand...
Click to collapse
My bad I guess

ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
I wonder if some kind soul can offer some wisdom, I unlocked my bootloader and flashed twrp. All fine so far.
I then upgraded to Pie.
I then flashed Magisk.
I was getting some strange Magisk behaviour so uninstalled it but for some reason it did'nt restore stock boot and Play Store was misbehaving.
I then flashed this boot image ^^ and yes, very stupidly, I now have no wifi (my MAC address is screwed).
I can boot to OS but I have no File Manager, nor root and I don't really know what to try from here.
I cant get to recovery (twrp or stock), it just get stuck on the Powered by Android logo.
I have debugging enabled but adb just reports my device as offline.
I cant get in to fastboot mode either.
Really appreciate some help from a kind soul
Ta

Hello i unlocked bootloader and after working so hard i finally booted twrp img to my nokia 8 and from there i cant access to twrp it always opens stock recovery.pls help me.....
I tried 2 to 3 times but i cant access twrp the process was successful but cant access it

I would say if it does not boot to it, its not there. Just flash twrp again. Use the latest from their website to do it.

Problems with flashing TWRP

I have the bootloader unlocked and everything ready to go.
However, when I execute "fastboot flash recovry <recovery_file_name>.img" the first thing that pops up on the cmd is:
(bootloader) has_slot:recovery not found
(bootloader) is_logical:recovery not found
After this it continues the flashing process and finishes with the okay status
However, after rebooting using "fastboot reboot" when I go back into the bootloader and select the recovery option I end up with the droid on his back and an orange triangle with an exclamation mark over him and No Command written under him
Can anyone help with this issue? I really want to flash a new ROM onto my nexus and I also really really want TWRP to work
Thanks,
Danush

Have you tried spelling "recovery" with an "e"?
It may be that your file name isn't properly spelled. I either rename the image to "TWRP. img" or copy the file name in Explorer and paste it into the CMD window so that there is no possibility of mis-spelling.
And another thought - is the TWRP image in the same directory as the fastboot exe?

dahawthorne said:
Have you tried spelling "recovery" with an "e"?
Click to expand...
Click to collapse
Oh yeah that's just a typo in my post ?
Thanks for pointing it out.
I do spell the "recovery" with an "e" and yet I have these issues

I added more comments while you were replying.
Try this:
https://forum.xda-developers.com/showpost.php?p=73648849&postcount=6

Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Thanks so much for all the help!! After you mentioned it, it kinda hit me that yeah maybe that is what is happening since I used to reboot the device so maybe it was replacing TWRP with the stock recovery.

Hi,
My problem with Redmi Note 4 Snapdragon 625 2,02 GHz and unlocked trying to flash TWRP is like this (phone is in fastboot mode):
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot devices
55050ae09804 fastboot
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot flash recovery
fastboot: error: ANDROID_PRODUCT_OUT not set
How can I solve it? Please, help!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Don't reboot after flashing? Like when i try it says img unsigned or corrupted, and when i try to then boot into recovery via "fastboot boot recovery" i get sent to the normal Android OS, so what im getting from this is that i somehow have to manually get into the "no command" error window and then power+volume up and that just works? Ill test that, would be really awesome if it does.
Oh yea and booting into the twrp image with "fastboot boot twrp.img" sends to normal os aswell btw.

[OOS] 10.0.11.HD01AA [Patched boot.img]

Extracted stock boot.img from latest Global Stable 10.0.11 and patched with latest Magisk Manager 8.0.0
https://www.androidfilehost.com/?w=files&flid=318127

Any chance of one patched in Magisk Manager 8.0.0 and Magisk v21.0?
Edit: If I could get the Stock Boot IMG that would be great too.

digidude512 said:
Any chance of one patched in Magisk Manager 8.0.0 and Magisk v21.0?
Edit: If I could get the Stock Boot IMG that would be great too.
Click to expand...
Click to collapse
Done! Check OP link

Rooted I bootloop but Stock I boot fine.
I hate when this happens.

digidude512 said:
Rooted I bootloop but Stock I boot fine.
I hate when this happens.
Click to expand...
Click to collapse
It's not .img problem, all good here.

FSadino said:
It's not .img problem, all good here.
Click to expand...
Click to collapse
I know, Just venting and hoping someone can tell what I'm doing wrong.

digidude512 said:
I know, Just venting and hoping someone can tell what I'm doing wrong.
Click to expand...
Click to collapse
What were exactly your steps to flash patched.img?

FSadino said:
What were exactly your steps to flash patched.img?
Click to expand...
Click to collapse
I tried both
adb reboot bootloader
fastboot boot 10.0.11.HD01AA_Patched.img
fastboot reboot
and
adb reboot bootloader
adb flash boot 10.0.11.HD01AA_Patched.img
fastboot reboot
But I'm stuck at the spinning OnePlus logo but adb devices shows the phone.

digidude512 said:
I tried both
adb reboot bootloader
fastboot boot 10.0.11.HD01AA_Patched.img
fastboot reboot
and
adb reboot bootloader
adb flash boot 10.0.11.HD01AA_Patched.img
fastboot reboot
But I'm stuck at the spinning OnePlus logo but adb devices shows the phone.
Click to expand...
Click to collapse
I can't help you with booting without flashing because I never did. What i always do and never fails to me is:
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot patched_boot.img
fastboot reboot

FSadino said:
I can't help you with booting without flashing because I never did. What i always do and never fails to me is:
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried that, Also tried removing Magisk Modules via ADB but I'm still on the spinning white dots but ADB shows the device.
So it's a bit weird.
Also when flashing stock I lose Wi-Fi and it force restarts randomly unless I flash the Update ZIP again.

digidude512 said:
Tried that, Also tried removing Magisk Modules via ADB but I'm still on the spinning white dots but ADB shows the device.
So it's a bit weird.
Also when flashing stock I lose Wi-Fi and it force restarts randomly unless I flash the Update ZIP again.
Click to expand...
Click to collapse
My advice is to clean flash OOS and repeat all steps

I'm an idiot...HD01BA not HD01AA....

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