Related
Hello guys.
How can I root my device Oppo Reno?
Have you tried kingroot APK ?
Doesn't work
Possible root method
Anyone got a copy of boot.img for snapdragon 710 version as I have found a way to root
Do share with us.
Root
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked
I have it.
SjDU said:
I have it.
Click to expand...
Click to collapse
pm it to @jsmith20094
Boot.img
SjDU said:
I have it.
Click to expand...
Click to collapse
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS
jsmith20094 said:
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS
Click to expand...
Click to collapse
you have PM
jsmith20094 said:
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked
Click to expand...
Click to collapse
Isn't the bootloader locked and fastboot disabled? How would we be able to flash the new boot file?
wolfgart said:
you have PM
Click to expand...
Click to collapse
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?
jsmith20094 said:
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?
Click to expand...
Click to collapse
You were saying that in the same method someone gain root on Find X ?
Should be the same here
They did but I don't know how to unlock bootloader
jsmith20094 said:
They did but I don't know how to unlock bootloader
Click to expand...
Click to collapse
It seems that OPPO will release Deep Test for Reno too after 3 Months starting selling it in China ...
I don’t know what starts in the recovery. When you tap “Ver 1.2” for about 5 times. A pop up appears it say something like “ Test Case 1 .. it will cost about an hour”
Stock boot.img and patched magisk boot.img
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk
jsmith20094 said:
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk
Click to expand...
Click to collapse
do you have tested that ?
@jsmith20094
How to flash with locked bootloader as for now it's impossible to unlock? Thanks
At the moment we cant flash it but as soon as oppo launch the deep program for it you simply install there APK and it allows you to unlock fast boot . As soon as it launches I will post APK with instructions
I need help getting my phone unbricked, because its my only phone, it bricked and it boots into black screen and i can't boot into recovery mode and fast boot mode, is there anyone who can help me, it bricked when i flashed TWRP because my phone was updated into MIUI 12.5
Edited: it shows the logo and it turns on but it will back screen when it reaches the boot animation and does nothing.
I've searched my way into every pieces on the internet to find answers on my phone, and i got some information about how to restore redmi note 9 into stock, by using EDL mode in the phone, you can reset the phone into stock firmware, but the problem is i don't know anything about the redmi note 9 main board and i don't know which specific jumper i should touch, i might destroy the board if i shorted any jumpers, i hope get answers on what jumper i should touch to enter EDL mode in Redmi note 9
PM me... i'll guide u
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Click to expand...
Click to collapse
Thank you so much for the help bro, i unbricked my device but i still need help about downgrading MIUI, you have any guide to that? from preloader to every img?
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Click to expand...
Click to collapse
btw, i totaled my phone and it doesn't boot no more it just black screens and in computer, it shows mediatek comport, i installed the wrong vbmeta because i was planning to downgrade the phone, is there any fix on it?
briangwapo81 said:
Thank you so much for the help bro, i unbricked my device but i still need help about downgrading MIUI, you have any guide to that? from preloader to every img?
Click to expand...
Click to collapse
Choose your firmware and flash it as any other xiaomi. You can google about it.
briangwapo81 said:
btw, i totaled my phone and it doesn't boot no more it just black screens and in computer, it shows mediatek comport, i installed the wrong vbmeta because i was planning to downgrade the phone, is there any fix on it?
Click to expand...
Click to collapse
Read my post again: https://forum.xda-developers.com/t/my-phone-got-bricked.4224163/post-84373765
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Choose your firmware and flash it as any other xiaomi. You can google about it.
Read my post again: https://forum.xda-developers.com/t/my-phone-got-bricked.4224163/post-84373765
Click to expand...
Click to collapse
no bro, i meant that the phone does not boot anymore and just shows this, your fix worked but, i really totaled my phone because it didn't flash, it errored
briangwapo81 said:
no bro, i meant that the phone does not boot anymore and just shows this, your fix worked but, i really totaled my phone because it didn't flash, it errored
Click to expand...
Click to collapse
What caused this ?
Did you try to flash the patched vbmeta or original stock vbmeta ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
What caused this ?
Did you try to flash the patched vbmeta or original stock vbmeta ?
Click to expand...
Click to collapse
i flashed the wrong VBmeta version and the wrong recovery version
briangwapo81 said:
i flashed the wrong VBmeta version and the wrong recovery version
Click to expand...
Click to collapse
Did you flash the patched vbmeta or original stock vbmeta ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Did you flash the patched vbmeta or original stock vbmeta ?
Click to expand...
Click to collapse
the original one, but the thing is i installed the wrong version because my phone's miui is 12.5 but i installed vbmeta 11.5 original version
u want solution??
briangwapo81 said:
the original one, but the thing is i installed the wrong version because my phone's miui is 12.5 but i installed vbmeta 11.5 original version
Click to expand...
Click to collapse
Recovery partition is verified by vbmeta.
You need to disable verification in vbmeta.
Doesn't matter what version is, if vbmeta is disabled, it will not verify any partition.
If you flash any custom partition without disable verification on vbmeta (or change vbmeta version without disabled verification), it will keeps bricked until you flash original stock rom firmware.
If you are flashing anything, you are changing stock rom.
You can only change stock rom with unlocked bootloader.
If your bootloader is locked, it will keeps bricked until you flash stock rom and unlock bootloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Butterfly_Bites said:
u want solution??
Click to expand...
Click to collapse
Yes. Please, tell us your solution
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Butterfly_Bites said:
u want solution??
Click to expand...
Click to collapse
Will you please tell us?
briangwapo81 said:
Will you please tell us?
Click to expand...
Click to collapse
Obviously, he will try to sell you something.
Please, taken care.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Recovery partition is verified by vbmeta.
You need to disable verification in vbmeta.
Doesn't matter what version is, if vbmeta is disabled, it will not verify any partition.
If you flash any custom partition without disable verification on vbmeta (or change vbmeta version without disabled verification), it will keeps bricked until you flash original stock rom firmware.
If you are flashing anything, you are changing stock rom.
You can only change stock rom with unlocked bootloader.
If your bootloader is locked, it will keeps bricked until you flash stock rom and unlock bootloader.
Click to expand...
Click to collapse
yeah, i used the disable verification command on vbmeta, the bootloader is unlocked, but the issue is that i installed the wrong version of the vbmeta, and other things are that my device won't sow in mi flash or SP flash tool, but it shows up in platform tools when the phone was in fastboot mode
VD171 said:
Obviously, he will try to sell you something.
Please, taken care.
Click to expand...
Click to collapse
that's what i doubt too.
briangwapo81 said:
yeah, i used the disable verification command on vbmeta, the bootloader is unlocked, but the issue is that i installed the wrong version of the vbmeta, and other things are that my device won't sow in mi flash or SP flash tool, but it shows up in platform tools when the phone was in fastboot mode
Click to expand...
Click to collapse
Can you record your bootloop?
Please, read careful this FAQ and reply with your bootloop record in this thread: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
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.
I think I can be banned for getting fake unlimited google photos storage but im not sure
XDAC1234 said:
I think I can be banned for getting fake unlimited google photos storage but im not sure
Click to expand...
Click to collapse
No it will not be banned
thanks, I already flashed and unflashed pixel experience tho lol, it was kinda laggy
Manjotbenipal said:
No it will not be banned
Click to expand...
Click to collapse
Manjotbenipal said:
No it will not be banned
Click to expand...
Click to collapse
btw do u know if i should install magisk the zip flash way or the patched boot.img way?
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
XDAC1234 said:
thanks, I already flashed and unflashed pixel experience tho lol, it was kinda laggy
Click to expand...
Click to collapse
You can uninstall bloatware with adb once you root your mobile and then install an mtz theme.
You will not even feel like you are using miui after doing that.
Btw should I make a thread on uninstalling bloatware with adb?
Manjotbenipal said:
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
Click to expand...
Click to collapse
[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)
Preamble: After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85). The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG)...
forum.xda-developers.com
You can skip erasing userdata and cache coz it will reset your mobile.
But if you don't want to take any risk and decide to reset then REMEMBER THE PASSWORD OF YOUR MI ACCOUNT
after reset your phone will be locked until you verify your mi account.
Make sure to backup all the data on your phone before flashing
Manjotbenipal said:
You can uninstall bloatware with adb once you root your mobile and then install an mtz theme.
You will not even feel like you are using miui after doing that.
Btw should I make a thread on uninstalling bloatware with adb?
Click to expand...
Click to collapse
If you want to, that thread would be gladly appreciated, I couldnt get debloat (the magisk module) to work in the terminal emulator
Manjotbenipal said:
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
Click to expand...
Click to collapse
huh, I didnt flash vbmeta before and my phone was fine (I had it rooted before pixel experience)
btw im using miui 12.5.6.0 RJOEUXM
SymtaxError said:
huh, I didnt flash vbmeta before and my phone was fine (I had it rooted before pixel experience)
btw im using miui 12.5.6.0 RJOEUXM
Click to expand...
Click to collapse
Then you can try but be careful
Manjotbenipal said:
Then you can try but be careful
Click to expand...
Click to collapse
nah, better safe than sorry (that idiom makes no sense but whatever)
I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!