Database Develop

No further update of CM13 via TWRP possible

Hey folks,
after hours of reading around I have almost no idea left how to update my CM13 (13.0-20151213_nightly-titan) currently installed to a newer version. I tried with TWRP 2.8.6.0 and even 2.8.7.0, but it's all the same: I choose the zip file to install, the filesystem is detected correctly - but the installation just won't continue (usually the detection is followed by "patching the system unconditionally"). TWRP doesn't freeze, but just nothing happens . When I brake up after some time (usually an installation is done very quickly) with pressing the power button, my phone boots in the old version normally.
I tried another TWRP, wiped cache and dalvik, fixed permissions, set root in phone options, tried several CM13 builds... But I'm afraid of wiping data and system as it's a lot of work to get everything right again afterwards :crying:. Do you have any idea why TWRP doesn't want to install the new build?
Thanks a lot!

First always take a nandroid backup before you make any changes.
Even thought TWRP 2.8.7.0 is released, For Moto G 2014(titan)
only 2.8.6.0 is official https://dl.twrp.me/titan/
Try doing a clean installation(Wipe the data & System). That should do the trick.
just for the record the recovery is stopping you from installing a new build

Seems to be an issue with TWRP. You could give a try using CWM PhilZ Touch recovery. I have flashed using this recovery numerous times without any problem.

Thank you two for your replies !
Maddy, I know that 2.8.7.0 is unofficial for titan, but nevertheless it's working (for others). I want to avoid a complete reset, but in the end this could be a solution. But as I reflashed twrp (and tried another version also) I'm really wondering why twrp could be the problem ...
pank, I will take a look on CWM PhilZ, but until now I was really happy with twrp (and of course with its backup function). I hope it's possible to flash CWM using twrp and vice versa .

Unfortunately CWM PhilZ Touch Recovery shows the same behaviour than twrp - installation of new zip file just doesn't work (without any error) . If someone has an idea (except of a full wipe) please give me input !

Update the bootloader to the latest version. Had a similar problem a few months back that resulted in lots of hair tearing This solved it.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007

Great hint - just checked your link already this morning and everything seemed to make sense... But I figured out that bootloader 4883 (newest version) was installed at my phone . Downgrade to 4882 should not be possible, and I'm also afraid of that .
I think I have something to do around Christmas - full wipe and a clean install! Damn...

Try installing this app called "CyanDelta" from playstore. What it does is it downloads the necessary files to upgrade from cm latest build (not the hole file) it's could be around 30 mb only. Totally legit!!... And it would dirty flash after download....
Do let us know how it turns out ?

I already tried CyanDelta, great tool! But as it's just creating a script for TWRP it has the same behavior . Oh, and I discovered that the nightly I'm using is no more available on cyanogenmod's official website ^^.
By now I think I've spend more time on searching for a solution than a full wipe including everything would need :laugh: ...

For me TWRP gives this behaviour only when Downloaded zip has some problem in it.
when it's not downloaded correctly it stuck at patching System
Have you tried latest zip?
also check SHA1 after download, doing that will confirm zip is downloaded correctly

Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...

No_Future said:
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
Click to expand...
Click to collapse
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.

mwalma said:
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
Click to expand...
Click to collapse
Yes, you can try Cyanogen Recovery
download it and from fastboot
you can either just boot once and try it or flash the recovery replacing TWRP
Code:
fastboot boot recovery.img
Code:
fastboot flash recovery recovery.img

Great, I didn't know that it's possible just to boot once with a special recovery image. I'll try cyanogenmod recovery today !

Great news: With use of Cyanogenmod Recovery I was able to flash the newest build :victory:! I'm looking forward to try one day with TWRP, but for now I'm totally up to date . Thank you all again and have some nice days !
Edit: A full wipe and clean install solved this problem completely . Now the flashing with TWRP works again.

Phone not booting after FlashFire flash.

Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.

Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.

irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.

irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/

Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:

ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.

[Q][HELP] OP3T Soft bricked after installing TWRP Recovery

Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance

First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.

Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?

redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance

Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0

redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro

Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide

mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine

mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.

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

Xiaomi Note 9 is still bootlooping even after installing stock firmware

Hello! Just created an account in this forum to seek help because this is driving me nuts.
I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.
So, I tried the following:
- I followed the guide in this forum for hard-bricked Note 9 phones (https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.
- I flashed stock firmware, but still no system.
- I flashed the MIUI version that the phone came with through fastboot, but still no system
- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)
- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.
- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.
I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.
Thank you.

Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data (you did first make a backup of your personal data right?)
Then phone should boot again.
I hope this helps. Good luck!

lebigmac said:
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data
I hope this helps. Good luck!
Click to expand...
Click to collapse
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system

bump

bump - really desperate about this matter

I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!

lebigmac said:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
Click to expand...
Click to collapse
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you!