Database Develop

TWRP asking for password for Decrypt Data on (8.1) international global rom

Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English

If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.

strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.

ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder

methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.

ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance

ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!

Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.

methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.

ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?

ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?

ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please

Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?

Trouble rooting my g6

I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.

jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?

kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.

jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting

kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.

jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp

kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!

jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,

Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps

jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.

Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.

Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later

THE root method. (any android version. yes 10 stable)

Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.

<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.

Can't we just flash Magisk on TWRP?

yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.

e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.

There is a new version of twrp, build .27 that is meant to fix backup / restore issues

Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.

e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'

Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.

Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.

UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.

greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.

e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.

greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?

Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching

e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."

e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.

e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.

greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.

How to reset firmware

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

Bootloop with no recovery or fastboot options

Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks

Did you flash anything?

Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.

VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?

jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com

jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.

Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/