Database Develop

[Q] Couldnt Update to Lollipop, LF USA XT1063 Mirror

First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.

Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!

Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?

bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!

If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355

Stuck in bootloop

First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.

totallybeachin said:
First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.
Click to expand...
Click to collapse
your phone cant run without a boot.img, thats the kernel and it controls the whole phone. it would never ever boot up without. anyways, what you need to do is wipe data in twrp, then reflash your rom and supersu.

I don't want to sound ignorant, but I'm going to anyway...
Could you please tell me which file is my rom?
I followed the guide(s) for rooting, and downloaded the files as were instructed, and as far as I know, I didn't download a ROM.
Only a custom recovery (TWRP), a modified boot image, then flashed SuperSU through TWRP.
Is the ROM on my phone somewhere? I can boot into recovery and look through file manager.
I also have TitaniumBackup. Would it be in a backup from that app somewhere?

Oh I didn't see the above question. So no, while the rom is on your phone, it's not in any flashable form, so you should download the latest factory image for shamu and flash that, a modified boot image for that version, and then root it. Do a factory reset, clear cache and dalvik, and you shoulbe up and running.

factory reset/wipe data might fix it, if not, then you need to flash a factory image(since you dont have a flashable cystom rom).

In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?

totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
system.img is your rom. recovery.img is your stock recovery
---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------
totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
factory reset and you wont lose root. factory.img and you will lose root. a custom rom requires twrp recovery, a custom kernel(for root), and the latest supersu.

Are you sure that it's not the xposed module is causing the bootloop??
use TWRP filemanager to delete /data/data/de.robv.android.xposed.installer/conf/modules.list
and try to boot again

Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....

totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
Click to expand...
Click to collapse
Sure, otherwise it wouldn't boot

totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....
Click to expand...
Click to collapse
a rom always has a kernel included, as thats what ties the software rom to your hardware phone. it ties your cpu to it, your buttons, etc.. all to your rom. its also like the btain center to your phone.

Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)

totallybeachin said:
Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)
Click to expand...
Click to collapse
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules

Droidphilev said:
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules
Click to expand...
Click to collapse
Yeah...I found it there instead of app drawer.
And the 'trick'.....I didn't have this after data
de.robv.android.xposed.installer/conf/modules.list

[STOCK] Flashable Oreo ROM H872 20A (20g Update!)

H87220a Flashable ROM for the T-Mobile LG G6
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP v3.2.1-0, 11g ROM
Based On: LG Stock ROM
Click to expand...
Click to collapse
This ROM based on H87220xxxx.kdz then extracted and repacked with autoprime's zip based on this thread.
Also, thanks for runningnak3d for TWRP install method. This ROM is ARB01 which is safe if you want revert to 11g.
Installation :
Modullar Installation
You should install at least bootloader, modem, and system in order to boot properly.
Install xxxOreo.zip using TWRP don't reboot
Press back button and Install Magisk (It's mandatory if you want root and twrp retained)
DONE and Reboot
[*]In most case, you'll lost your /data due to data encryption. so backup first
[*]This build's ONLY for T-Mobile US LG G6
[*]If you decided to downgrade, make it sure that firmware is ARB01 (11g or later)
Download :
As requested by many people I've uploaded new update within 4 modules (Bootloader, Laf, Modem, and System).
You can download here: H87220g (latest)
LGH87220F
LGH87220D
LGH87220A
Recommended TWRP/Orangefox Recovery
my G6 seems broken, it has no display but it still ringing when I call it. probably LCD issue. Basically, I can't test any future update with this phone. I've planned to buy v30 soon and try to repair my g6 by myself. Any info or some suggestions will be appreciated
Have a nice day,

OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW

MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
Click to expand...
Click to collapse
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:

immns said:
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:
Click to expand...
Click to collapse
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).

NighthawkXL said:
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).
Click to expand...
Click to collapse
yep, flashing back original laf will save you in the future mistakes.

By "Stock" do you mean LG's bloatware stuffed "stock" or do you mean "Vanilla Android" stock?
MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW
Click to expand...
Click to collapse

BTW -- I did this method, got laf back to what it should be, rooted the H872 Oreo, installed GApps, and have a pretty good setup with Volte/WiFI calling, Goodle Dialer and Messages (with web message support), stock camera, etc -- kinda best of all worlds.
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
For those that are not aware, with TWRP still in recovery, you can boot to this following the factory reset options for the phone, but after answer to confirm "Yes" twice, you will boot into recover TWRP, so you can always get back there without a laptop and / or fastboot. If I recall, the key sequence is hold down button, hold power until logo appears, then turn power on and off until factory reset appears...
But TWRP needs to be fixed to access that data partition -- no idea what that is all about.

So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.

GoofyPanda said:
So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.
Click to expand...
Click to collapse
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.

MetroWestMA said:
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
Click to expand...
Click to collapse
I believe that's possible, all you need's the right dm-verity disabler that works with this phone. In theory, just format (not wipe) your data partition, flash rom, flash dm-verity disabler, and then reboot. Data partition is encrypted by bootloader, I've checked twrp's fstab and all point to the right direction. But still, we've to try this before knowing what's actually possible or not. For now, I utilize LG Mobile Switch to backup my data and it's totally fine.
UPDATE: It doesn't work, dm-verity patches actually only patch boot.img while this phone has aboot, tz, and a lot elf programer

immns said:
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.
Click to expand...
Click to collapse
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later

GoofyPanda said:
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later
Click to expand...
Click to collapse
I doubt it is...because mine didn't and there was no /system/recovery_rom_boot.p to delete.
you can try installing a program like Titanium Backup that has the option to reboot into recovery.
Did you get it to the menu asking to factory reset -- if you got that and answered yes both times and did not get into recovery, then it is gone...

Kdz h827bk is same as h872?

AdrianNeo said:
Kdz h827bk is same as h872?
Click to expand...
Click to collapse
do you mean h872bk? The answer is yes, this is from H872BK kdz

immns said:
do you mean h872bk? The answer is yes, this is from H872BK kdz
Click to expand...
Click to collapse
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.

AdrianNeo said:
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.
Click to expand...
Click to collapse
if your phone is from T-Mobile, it's b872bk. please check ota update. if you got oreo update then you're in the right path. but if not, then it's more likely that your phone is the 872tn one.

I'm assuming the 2 letters at the end signify the color of the devices (BK = Black and TN = Titanium/Silver). Even though the devices are the same, perhaps there are minute differences in each build? I flashed the 20a zip that was provided by OP, but it changed my splash screen to say G6 ThinQ? The G6 I have is T-Mobile branded Titanium color, but I definitely had the devices before the ThinQ moniker became a thing. I'm going to download the KDZ branded for my 872TN and see what happens when I flash with LGUP.

The G6 ThinQ splash screen came with the oreo update. I think too that bk=black and tn=titanium no diff at the builds.

Your zip save my phone
Keep it up bro ..
Thanks

So I should be able to flash this through twrp like any other zip?
Y'all were talking about deleting deleting things so I wanted to make sure before I did anything.
I'm in agreement with fixing the laf after getting root, and this way looks like it would simplify matters if you got stuck with an issue and didn't want to or didn't have access to a pc.
Thanks

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

Flash back to Android 11

Hey all, dug around, but can't find the info I need. While I was carrier/bootloader locked, I took OTA updates to Android 12. I have the camera issue lots of people are reporting where the rear camera generally refuses to start, but randomly works, almost like some other app has it locked.
I'd really like to try flashing it back to Android 11 and installing a custom ROM since TWRP isn't available for android 12 yet. Is this possible? Where would I find files that I could use via fastboot?

@galamdring
Sounds like you are still BL locked? If so, you cannot flash anything via fastboot. This means no downgrading or custom ROMs. Have you tried flashing a "rescue" OTA via recovery? This involves setting up adb on your PC and flashing the full OTA image the phone via adb in recovery. The instructions are found at the top of the page where you download the OTA image files.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

Sorry that wasn't more clear, I am BL unlocked now. I was able to install Magisk, use it to modify the boot.img, and install a kernel. I tried modding TWRP into the boot img, but it just sits at the TWRP loading screen, as I've seen for others on A12.
The biggest thing I want to try is a custom ROM, but I would really prefer to backup my current system to flash back if things don't go well, and it doesn't seem like there is a way to do that without TWRP.

galamdring said:
Sorry that wasn't more clear, I am BL unlocked now. I was able to install Magisk, use it to modify the boot.img, and install a kernel. I tried modding TWRP into the boot img, but it just sits at the TWRP loading screen, as I've seen for others on A12.
The biggest thing I want to try is a custom ROM, but I would really prefer to backup my current system to flash back if things don't go well, and it doesn't seem like there is a way to do that without TWRP.
Click to expand...
Click to collapse
Making a nandroid backup is not nearly as important these days as Google has really improved their backup to cover more. I use appdash for my non-store apps and Nova launcher to save all my shortcuts and widgets. It's fairly painless to completely wipe the phone and get back to where you were in 20-30 minutes.