Database Info

Won't flash CWM

I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?

ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.

enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?

ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.

enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange

ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts

enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything

Twrp won´t read partitions on oppo r7 plusf.

Hello everyone, i have a problem installing twrp officiall from twrp.me and could not find any thread on my problem. None of the img. files will work when i boot from fatstboot, they boot up allright but i can´t do anything, twrp can´t read partitions. View attachment 3638514
From what i can understand my phone is a r7plusf and not r7plusm. And i got the unoficiall twrp from link in post 2 to work so that i was able to backup but it can´t mount cache so i can´t wipe or flash anyway.
So i decided to try to flash cm13 latest nightly with cm recovery 13, but it failed. I made backups of stock recovery via flashfy. Then i made nandroid bakup via twrp unofficial. I then rebooted and Flashed cm recovery With flashify and that worked. I then booted to cm recovery and wiped data/factory reset and it failed and got stuck. I waited for ca 10 min then was able to reboot system and phone was reset and wiped. I rebooted to cm recovery and tried to flash, failing again and bootloop.
Luckily fastboot still worked. I then booted unofficial twrp via fastboot and flashed latest cm nightly, and it failed, it could not find cache, bootloop still. As nothing else worked i thought it was best to restore nandroid, and gues what? Twrp unofficiall got stuck. By now i got a bit nervous. I was able to reboot twrp again via fastboot and this time restore worked, though it took quite some time before restoring actually began. All worked out well and i was able to restore stock recovery agin with flashify. I wonder if i have some odd batch phone???
Thankful for any input...

tommie.r said:
Hello everyone, i have a problem installing twrp officiall from twrp.me and could not find any thread on my problem. None of the img. files will work when i boot from fatstboot, they boot up allright but i can´t do anything, twrp can´t read partitions. View attachment 3638514
From what i can understand my phone is a r7plusf and not r7plusm. And i got the unoficiall twrp from link in post 2 to work so that i was able to backup but it can´t mount cache so i can´t wipe or flash anyway.
So i decided to try to flash cm13 latest nightly with cm recovery 13, but it failed. I made backups of stock recovery via flashfy. Then i made nandroid bakup via twrp unofficial. I then rebooted and Flashed cm recovery With flashify and that worked. I then booted to cm recovery and wiped data/factory reset and it failed and got stuck. I waited for ca 10 min then was able to reboot system and phone was reset and wiped. I rebooted to cm recovery and tried to flash, failing again and bootloop.
Luckily fastboot still worked. I then booted unofficial twrp via fastboot and flashed latest cm nightly, and it failed, it could not find cache, bootloop still. As nothing else worked i thought it was best to restore nandroid, and gues what? Twrp unofficiall got stuck. By now i got a bit nervous. I was able to reboot twrp again via fastboot and this time restore worked, though it took quite some time before restoring actually began. All worked out well and i was able to restore stock recovery agin with flashify. I wonder if i have some odd batch phone???
Thankful for any input...
Click to expand...
Click to collapse
Got this info from app, it says oppo r7 plusm and oppo r7 plusf. confusing...

no sure if you already figured it out but I think u have an R7PlusF with the bootloader of an R7PlusM. go into the development thread of R7Plus and flash the recovery I posted there. Flash my English translation one via Fastboot. I'm 100% sure TWRP will work flawless for you with that version.
oh and edit that screenshot to hide your IMEI! you don't want to give out that information to the Internet ever!

celoxocis said:
no sure if you already figured it out but I think u have an R7PlusF with the bootloader of an R7PlusM. go into the development thread of R7Plus and flash the recovery I posted there. Flash my English translation one via Fastboot. I'm 100% sure TWRP will work flawless for you with that version.
oh and edit that screenshot to hide your IMEI! you don't want to give out that information to the Internet ever!
Click to expand...
Click to collapse
Yes i have thanks to you, and all my problems with twrp has been resolved, and yes it was very clumsy of me to miss emei...
Thanks for the reminder.

[HELP] Stuck on Recovery Bootloop after OTA Update (CM14.1) , can't access Fastboot

Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.

I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.

[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date

Same thing happened to me! Where did you get a copy of the stock recovery? Link?

resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.

Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.

corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse

resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!

First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.

Kind of bricked my OPO in a weird way after 3 years.

I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage

naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Change the battery. U are not only one... There are lots of people had this issue after 2.5+ year including me. I changed battery two days ago (not original) now its work normal.
https://forum.xda-developers.com/showthread.php?t=3565871
https://forum.xda-developers.com/showthread.php?t=3610933
Sent from my A0001 using Tapatalk

naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Did you tried flashing stock Cos13.1.x through fastboot?

Mr.Ak said:
Did you tried flashing stock Cos13.1.x through fastboot?
Click to expand...
Click to collapse
Yup I've tried that

naeem76 said:
Yup I've tried that
Click to expand...
Click to collapse
So,what happens after that? Does it boots?

Mr.Ak said:
So,what happens after that? Does it boots?
Click to expand...
Click to collapse
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
Here this one, it was weird, it never booted afterwards

Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted

naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
Device works fine when it is in TWRP? Like,no reboots or power off(s) whatsoever? Battery works fine in TWRP? Like,charging and stuff? If it does,then this is unlikely a battery issue,however,I would suggest you to remove battery(go through tutorials on youtube) and attach it again.
This has happened to me before,like if I'm not able to flash anything from TWRP then I just change/update recovery to unofficial/newer versions of it(did you tried this?) or,I just flash Cos13 through fastboot then it boots up fine and I flash TWRP again and boom,everything is back to normal.In cases where I'm even fail to flash Cos13(shows system error/system partition corrupt) or I'm not even able to boot to fastboot i.e.,hardbrick,I just use Cm11S restore tool(modified version of color os toolkit,you can find on general thread) and it flashes perfectly fine and boom,device is back!
I hope it helps!
Ps- This is the tool I'm talking about,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I always use this because after flashing from color os tool,I used to get bootloop,though fastboot mode was accessible then so I could just flash Cos13 through fastboot and I no longer get any system errors and it boots up fine.

naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.

It happened to me once. I had to erase every partition via fastboot, not only system data and cache, but also modem, efs, recovery ecc. Then I flashed stock COS13.1 partitions images and it worked. Just remember: do NOT turn off or reboot your phone between the erase and the flash, it could hard brick the device!
edit: You should also backup your existing efs partition via recovery.

Fixed my device. For future reference, it was a battery issue, Just couldn't retain enough charge, enough to boot into recovery but not enough to boot any ROM, Changed battery and everything is back to normal

Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now

naeem76 said:
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
Click to expand...
Click to collapse
@psxda97

Mr.Ak said:
@psxda97
Click to expand...
Click to collapse

psxda97 said:
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
Click to expand...
Click to collapse
psxda97 said:
Click to expand...
Click to collapse
My trust on you

naeem76 said:
My trust on you
Click to expand...
Click to collapse
LOL!
I'm glad it worked

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?