Related
I am sure this is a noob question here so I apologize in advance. I am a bit confused about how to go about disabling / removing encryption on my Nexus 6. When I look into it, it seems to be required to flash a new boot.img. However, you already need to use a modified boot.img to root.
So, once you are rooted, you can change your boot.img without losing root?
Does the modified boot.img from Chainfires post already disable / remove encryption?
Is there a modified boot image that disables encryption and allows root?
When I am in Titanium Backup, I see encryption: DISABLED. Is that telling me that my phone encryption is disabled or that just Titanium Backup Encryption is disabled?
Also, now there is MRA58K/N/R. Chainfires post has the modified boot image from K. Has the boot.img changed at all from K to N to R? If so, how can one still use the modified boot.img from K after flashing to R?
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
simms22 said:
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
Click to expand...
Click to collapse
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Rektifying said:
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Click to expand...
Click to collapse
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
simms22 said:
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
Click to expand...
Click to collapse
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Anyone else care to answer this for me? I am newer to Android period so I apologize again for sounding noob. I just don't fully quite understand how this root method works. So if a modified boot.img is required for root, how can I turn around and flash a different boot.img and still have root?
I am literally sitting here waiting to flash my Nexus 6 to MRA58R until I figure this out. I am well aware how to flash stock images, custom recovery, sideload superSU. I just want to clean flash my Nexus 6, have root, and have encryption disabled.
Rektifying said:
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Click to expand...
Click to collapse
i use despair kernel. technically, any custom kernel is a modified kernel. and it alows for decryption, even though i did not decrypt. i flashed marshmallow, flashed despair, then flashed supersu. now im on marshmallow with root.
what im saying is that i have never used chainfires kernel, so dont know anything about it.
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Rektifying said:
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Click to expand...
Click to collapse
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
simms22 said:
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
Click to expand...
Click to collapse
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Rektifying said:
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Click to expand...
Click to collapse
yes(but im not sure with marshmallow). with all other android builds, yes.
simms22 said:
yes(but im not sure with marshmallow). with all other android builds, yes.
Click to expand...
Click to collapse
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Rektifying said:
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Click to expand...
Click to collapse
yes.
but the thing i dont know about is that the stock marshmallow kernel might prevent root, even though the files are still there. but you can flash any marshmallow custom kernel(for n6).
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
awesome
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
I was trying to figure out the same thing. What modified boot.img did u use for root access and which modified boot.img did u use to remove encryption. Thanks.
Basically any kernel that does not check encryption and force it to be applied... In other words almost any 3rd party kernel... But double check the kernels feature list and make sure it says no forced encryption.
The device will probably give you a "system is corrupt" error with a stock kernel and root installed. I would flash a custom kernel for sure because it usually doesn't force encryption and does support root! I am using elementalx right now and it's a very good kernel for this. Many other custom kernels work just as well! I HAVE used chainfire's kernel, and it does not force encryption, it also supports root, I can confirm this. If you use chainfire's kernel, make sure you format your data to unencrypt. You can use the "format data" option in TWRP or use the fastboot command "fastboot format userdata". Hope I helped!
EDIT: You have to format your data to decrypt regardless of WHICH kernel you choose, sorry if that sounded confusing.
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?
JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.
WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse
KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.
KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse
[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.
Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?
Any solution for this, or any suggestions to try??
Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.
You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!
First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.
We must unlock the bootloader with fastboot mode or we can do it through developer options??
black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.
-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!
I 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/