Database Info

Stuck while installing Pacrom, no backup, safestrap gs4

I started to install pacrom on my verizon galaxy s4 and am havings troubles. I'll start from the beginning.
I rooted the phone via Towelroot app and checked it with rootchecker.
Then i downloaded the following.
downloadandroidrom.com/file/GalaxyS4/SCH-i545/roms/PACMan/pac_jfltevzw-nightly-20130913.zip
downloadandroidrom.com/file/gapps/PA/pa_gapps-full-4.2-20130610-signed.zip
androidfilehost.com/?fid=95784891001603023 this is safestrap for "FOR USERS OF MJ7/MK2" IDK the difference between that and ME7/MI1 but i used MJ7/MK2
From here I opened up the safestrap app and installed the recovery and loaded it up. I left it on the stock rom slot while i continued to wipe everything and install the rom and GAPPS. This was a mistake, however, because i it bootlooped. I tried wiping and installing many different ways and still ended up with a bootloop. I realized in needed to use a rom slot and set that up. I wiped all the necessary things and installed the rom and GAPPS. Still it bootlooped. I have even tried to install without GAPPS with no avail. I forgot to make a backup of the stock and the stock slot just bootloops the pacrom boot screen. I cant find a way to add filed from my computer because whenever i connect it during the boot screen it shows up as a disc drive on my computer. Normally i would choose USB settings and make it where i can transefer data files, but i cant do this. I really need some help with this as I have done all I know to do. The downloads may be the problem, but from what i understand they are the correct ones. Thanks

Download this rom, move it to your phone and flash with recovery.
If you can't get the file on the phone I will help you out.

Rooting mistake! Can't reinstall stock firmware, no root, no recovery.

I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2

DJBTB said:
I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
Click to expand...
Click to collapse
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I've tried doing a factory reset if I get lucky and it takes me into the main screen but immediately it gives me the "seandroid" error message the same as if I press volume up, menu, and power. I am able to boot onto download mode ive tried this to flash firmware but Odin gives me a Fail (Auth) message each time. I'm not even sure if TWRP has a version for my phone yet I'm not sure much about TWRP. If there's a way I can break this chain I'll try anything.

TWRP working so far
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!

DJBTB said:
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
Click to expand...
Click to collapse
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.

DJBTB said:
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
Click to expand...
Click to collapse
By the way, when flashing stock firmware via Odin, root is not required. The only time root is required to flash stock ROM is when flashing a stock firmware that has been converted into a custom recovery stock flashable.zip. It is not uncommon for someone in this community to convert stock firmware into a recovery flashable .zip. This is used so that the device doesn't lose root or custom recovery. When flashing stock the normal way via PC, it removes root and reverts the device back to stock recovery. Then the device has to be rooted and flash recovery again. The stock flashable .zip avoids all of that because it gets flashed in custom recovery, this way, recovery is not lost and root is not lost.
This only applies "IF" someone converts the firmware to flashable .zip. Not all devices have a stock flashable .zip available though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

PROBLEMS in installing TWRP and root (20a)

spent the last 3 weeks ( NO LIE ) trying every method under the sun to get my device rooted
easy recowvery
Hard Recowvery
manual ADB and flashing img
tot updates
kdz downgrades
basically everything
im not sure what else to do if its even possible at this point
Device details
tmobile locked LG G5 (h830)
OEM unlocked
its on 20a firmware ( coming from 20i )
ive rooted and installed twrp on may phones so i have a vast knowledge of these things
a few observations are
phone seems like its rewriting stock recovery on each reboot
fastboot won't accept any commands, i get "writing 'recovery'...FAILED (remote: unknown command)"
both hard recowvery and easy recowvery work up to the part of twrp install then it reboots to nothing
FINAL NOTE
im wondering if t-mobile is blocking the fastboot commands since im on temp unlock via device unlock app
if thats not a thing idk whats wrong im hoping one of you great minds can help this poor soul

Anyone?

Did you check oem unlock in developer options

rflores said:
Did you check oem unlock in developer options
Click to expand...
Click to collapse
thanks for replying ,
yes i did
its greyed out now but its been off
the fastboot commands says its unlocked as well

Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!

speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
thanks for this reply
i will try this as soon as i get home
thanks in advance

speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
providing an update
Ive just tried everything listed in you post specifically and failed , so i tried like 2 more time ,
it reboots into stock recovery so still no TWRP ,
boot loader is unlocked , cause i just checked again , and its still not accepting any commands

Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.

speters04 said:
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
Click to expand...
Click to collapse
thanks for reply;
none of those work for me either, I've been trying all this time
it says its successful in deploying commands, but when it restarts I see the LG logo two times, then it boots back up
( i assume its rewriting recovery there )

Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.

I had the same issue after returning from 20k to 20a. I didn't have this problem doing the same from 20f. T-Mobile might've introduced some security kink at 20i that sticks across updates. I was only able to flash twrp after flashing 20a with UPPERCUT to enter LGUP, booting into 20a, allowing debug in developer options, then running easyrecowvery with verification disabled (press 5 for advanced options, then 7 I think, then 0 to return to main menu, then 1 or 2). With verification enabled, easyrecowvery will just take you to the non-existent Android recovery screen and leave you there. I think that's where you're stuck??

speters04 said:
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
Click to expand...
Click to collapse
well lets use Autorecowvery for example
ive exhausted all options there and Ive gotten the success messages , does its fancy restarts and success messages all around , but when it restarts to install the "no-verity-opt-encrypt" it reboots and comes right back to android . ( note it reboots 2 times at this point , so i know its rewriting stock recovery )
see below
https://ibb.co/eq5ctR

It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!

speters04 said:
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
Click to expand...
Click to collapse
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read

When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips

dtgo said:
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
Click to expand...
Click to collapse
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...

poog said:
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
Click to expand...
Click to collapse
well ive been working to get to this screen it NEVER happens , i already know im set when im there
the phone isnt encrypted so i know i wont have to format data , since , format data removes encryption

speters04 said:
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
Click to expand...
Click to collapse
ive tried both your suggestions plus more
copied to the phone and renamed
downloaded on the phone then renamed
dowloaded on pc and renamed then copied to phone
used adb to push and rename to phone

still having challenges with this
do you think its a dead case guys

OP isn't the only one with this hair-pulling problem...I too downgraded a new H830 from 20M (? I can't remember which one exactly since I've LG-Uppercutted 20A and troubleshooted this constant problem so many times now)---I get the exact same error as OP, also with the highly suspicious 'greyed-out OEM Unlock' (in the Developer Options of the Settings).

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.

This problem has been solved?

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.

hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery

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?