Related
Im reading how to mod this Mi A2, I've modded a lot of Android Phones (till Samsung Galaxy S I..), but Im reading that this Xiaomi Mi A2 isnt too simply to mod, for example: unlock bl, flash recovery, flash rom/gapps/root/kernel/extra stuffs and reboot.
Im reading that this phone to get modded, require:
<!-- I have to be on stock Oreo?? --!>
unlock bl
flash unlock_critical
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
flash rom
flash twrp installer (so i can boot to recovery without pc)
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
reboot recovery
flash Gapps
flash Magisk
reboot
Thanks to who want to help or fix my errors.. Im only asking if these steps are right!
Francesco0301 said:
<!-- I have to be on stock Oreo?? --!>
Click to expand...
Click to collapse
I unlocked mine in stock oreo, but I don't think you have to be in oreo to unlock bl. Some Custom ROMs, though, were only flashable in stock oreo (because pie vendor is unstable or something), but I think after 10.0.2 most of Custom ROMs was updated to be flashable over stock pie (the thread might be not updated, but you're actually able to, read few last pages or search around the thread of course just to make sure, it's ROM dependent).
Francesco0301 said:
unlock bl
flash unlock_critical
Click to expand...
Click to collapse
As for the unlocking steps --correct me if I'm wrong as it was from memory-- I think there are 3 unlock, OEM unlock, flashing unlock, and flashing_critical unlock.
Francesco0301 said:
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
Click to expand...
Click to collapse
If you fastboot -w, I don't think you need to wipe data again.
Francesco0301 said:
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
Click to expand...
Click to collapse
You could do this in twrp in the "reboot" section. Select the slot, then reboot to recovery. You'll know what I mean when you boot TWRP, it's a new addition in TWRP compared to non-A/B-partition-device-thing you used to mod.
Francesco0301 said:
flash Gapps
flash Magisk
Click to expand...
Click to collapse
Keep in mind if you want to flash custom kernel, it is to be done before Magisk. Imagine having a boot.img from custom rom zip flashed to your system, that boot.img must be modified in this order: TWRP -> Custom Kernel -> Magisk. It will break each other if not in that order.
If you already flashed everything including magisk, using the device, THEN decided that you want a custom kernel, what you'd do is grab boot.img from custom rom zip, fastboot flash boot_a boot.img (if you flash rom on b, vice versa), then basically you repeat from fastboot set_active b then boot twrp yada yada until you flash magisk EXCEPT wipe, rom, and gapps. Do so so it's clean and with minimal issue. The order is important.
And for some Custom ROMs you need to flash custom kernel for it to boot, so keep an eye to the thread whether you need it or not. Or maybe telegram, as sometimes they haven't updated their thread but say something in telegram group. It's a good idea to join the group for news or to search around some information.
But yeah everything else is correct afaik. I hope what I say is clear and understandable enough. Happy modding!
Francesco0301 said:
fastboot set_active b
Click to expand...
Click to collapse
Pretty much everything is good but just make sure of your active parition and set the other so it might be fastboot set_active a (if you're active parition is b and vice versa) , but i was exactly like you but modding the mi a2 is not that hard just needs a bit more understanding
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Gloff said:
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Click to expand...
Click to collapse
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Badger50 said:
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Click to expand...
Click to collapse
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Gloff said:
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Click to expand...
Click to collapse
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Badger50 said:
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Click to expand...
Click to collapse
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Gloff said:
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Click to expand...
Click to collapse
Yes
p70shooter said:
Yes
Click to expand...
Click to collapse
I assume the boot.img from December Update, yes?
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yes. fastboot flash boot boot.img :good:
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
p70shooter said:
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
Click to expand...
Click to collapse
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Gloff said:
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Click to expand...
Click to collapse
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
p70shooter said:
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
Click to expand...
Click to collapse
Hahahahahaha....I think I remember a couple of those! ?
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
So when updating, do you guys just flash the entire updated factory image when a new update is released? No need to uninstall Magisk, so you don't have to flash the previous update's boot.img?
In other words do you flash new full factory image>patch boot.img>flash magisk_patched> done VS.
Flash old stock boot.img>OTA/Factory image>patch boot.img>flash magisk_patched>done?
This has never been clear to me as far as new updates go. I feel like the guide should have an "I'm rooted and just want to update to the latest security patch" section.
Gloff said:
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
Click to expand...
Click to collapse
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Badger50 said:
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Click to expand...
Click to collapse
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Edit: fastboot flash boot boot.img --slot=all did not work either. I used the boot_a/boot_ b method and it worked fine.
Gloff said:
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Click to expand...
Click to collapse
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Badger50 said:
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Click to expand...
Click to collapse
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Gloff said:
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Click to expand...
Click to collapse
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Badger50 said:
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Click to expand...
Click to collapse
Tried that, middle of the attachment results in fastboot: unknonw option --slot=all
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/
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
Help
sayanmitra753 said:
Help
Click to expand...
Click to collapse
Dump boot and vbmeta partition patch in magisk app.
And flash boot partition with vbmeta using fastboot after that you can update magisk using magisk app
HowWof said:
Dump boot and vbmeta partition patch in magisk app.
And flash boot partition with vbmeta using fastboot after that you can update magisk using magisk app
Click to expand...
Click to collapse
Do i need mtk client to bypass ? Or can i simply flash using fastboot and adb ?
sayanmitra753 said:
Do i need mtk client to bypass ? Or can i simply flash using fastboot and adb ?
Click to expand...
Click to collapse
Fastboot.
Mtk client you need to dump partitions.
Remember to turn off vbmeta veryfiction when flashed
HowWof said:
Fastboot.
Mtk client you need to dump partitions.
Remember to turn off vbmeta veryfiction when flashed
Click to expand...
Click to collapse
Thanks.. successfully rooted using mtk client
sayanmitra753 said:
Thanks.. successfully rooted using mtk client
Click to expand...
Click to collapse
did you unlock the bootloader before that or did you just use mtk to flash patched boot.img? it didnt work for me when i was trying to flash patched boot.img from magisk with mtk on a locket bootloader c11 global firmware. gladly i kept an backup of the original boot.img and vbmeta. but i now get an verification error on bootup.
which version of magisk did you use?
08whuoweo3 said:
did you unlock the bootloader before that or did you just use mtk to flash patched boot.img? it didnt work for me when i was trying to flash patched boot.img from magisk with mtk on a locket bootloader c11 global firmware. gladly i kept an backup of the original boot.img and vbmeta. but i now get an verification error on bootup.
which version of magisk did you use?
Click to expand...
Click to collapse
Of course unlocked..flash thailand rom first to use deeptest apk..deeptest is not available on indian rom, don't know about other region..then after flashing thailand rom with sp flash tool , use deeptest to unlcok..after unlocking bootloader you can return to your region rom by flashing with sp flash tool again.. bootloader will stay unlocked..