Related
Hello guys...
I was using Thundersnap GB and "noobly" did a factory restore through system... Well, I lost everything including my rom, and my system only boots into CWM. I have managed to re-add some ROMs into sd, have installed them with CWM with no errors, wiped everything as usual, but the system insists to reboot into cwm, I cant run the rom.
Did anyone have an idea of what Im missing? :crying:
acpesreplays said:
Hello guys...
I was using Thundersnap GB and "noobly" did a factory restore through system... Well, I lost everything including my rom, and my system only boots into CWM. I have managed to re-add some ROMs into sd, have installed them with CWM with no errors, wiped everything as usual, but the system insists to reboot into cwm, I cant run the rom.
Did anyone have an idea of what Im missing? :crying:
Click to expand...
Click to collapse
I think you have corrupted boot loader sequence. Search XD for universal_recoveryloop_breaker.zip. Copy it to your sd card.and install it in recovery. It seems that you cannot use the systems factory reset options once you have installed a custom[wkparks] recovery and bootloader. only use twrp or cwm to reset to factory. Hope this helps.
keith210350 said:
I think you have corrupted boot loader sequence. Search XD for universal_recoveryloop_breaker.zip. Copy it to your sd card.and install it in recovery. It seems that you cannot use the systems factory reset options once you have installed a custom[wkparks] recovery and bootloader. only use twrp or cwm to reset to factory. Hope this helps.
Click to expand...
Click to collapse
Thank you for your help, man, but it didnt work. Actually I lost access to recovery, went stucked in LG logo now. I cant even recover with LG Tool... The program recognizes when I connect in download mode, but when upgrading the process stops at 10% due to bad communication or something else. I saw a video about reinstalling the drivers via device manager to get properly recognized, but I couldnt get it to work. Run Windowns 8/64, with LG p720h.
I think only way now is to unbrick, right? P920 method works with my P720?
Thanks in advance anyway.
It is likely a driver issue. Windows 8 tips at the top here
http://forum.xda-developers.com/showthread.php?p=39269819
I think drivers are the same for P720 but not certain. Roms are not the same so you will need to find firmware to flash.
My Moto G (XT1033) 1st Gen with stock lollipop has stuck in a boot loop.
I am still able to go in to recovery mode. Have tried clearing cache, but that didn't seem to work.
I don't have CWM installed it's pure android as stock have installed updates only through OTAs.
Have googled about it and many are stating that a factory reset will solve the issue. But I don't want to lose data in the phone.
Main reason for the boot loop could be App as I use beta versions of Facebook, Whatsapp and Nova launcher from apkmirror.
What can be done to recover data or just get this boot loop fixed?
P.S: My device is not rooted and does not have any CWM or TWRP recovery.
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
BBThumbHealer said:
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
Click to expand...
Click to collapse
oh okay mate. I have been googling for such issue but the mostly suggested method is reset that I haven't done (not to lose data). Will wait for a day if I get any solution otherwise will reset it.
Let me know what happened to your phone. Hope it gets fixed soon
okay so here's the update. Was successful to take backup as per http://forum.xda-developers.com/showthread.php?t=2426426
And made factory reset after that but now it is still getting stuck on bootloop with M logo and powered by android screen. :crying:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
BBThumbHealer said:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Click to expand...
Click to collapse
Damn mate ! I am going to follow same steps.
1) Unlock bootloader
2) Flash custom recovery if needed
3) Flash Custom rom
btw did you had unlocked the bootloader? @BBThumbHealer
lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Thank you for you reply mate. :good:
I have somehow managed to backup data by script. but the problem is now even after resetting it is still stuck into bootloop.
But I am a bit confused here in steps.
1) Unlock bootloader
2) Flash custom recovery like TWRP and clear dalvik cache
3) and then flash any custom rom
correct me if I am wrong. I am going to follow these steps. @lost101
Phone started! yeeey!
So heres the update bro @BBThumbHealer.
Unlocked bootloader.
Flashed TWRP.
Cleared cache/dalvik cache/data.
Flashed http://forum.xda-developers.com/moto-g/development/nx-nexus-experience-rom-10-0-3-ambient-t3268555/
And device is working smooth as silk now and that too with Marshmallow !:fingers-crossed:
Let me know your status bro. Hope I could help you in some way
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Hello guys, My phone is stuck on bootloop
I have already rooted device and now it is stuck on bootloop even the Recovery isn't opening. I know I would have to reset the phone with mfastboot but I want my internal storage to be backed up before doing all this Is there anyway to do so? Anyone here can help me out?
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
BBThumbHealer said:
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
Click to expand...
Click to collapse
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
sahil_arora05 said:
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
Click to expand...
Click to collapse
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
BBThumbHealer said:
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
Click to expand...
Click to collapse
Ok going to try that. Is there anyone who can provide me a link to download STOCK recovery for moto G xt1033. Can't find that.
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
BBThumbHealer said:
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
Click to expand...
Click to collapse
tThanks again buddy.
BBThumbHealer said:
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
I already gave you the solution in post #6. Stop ignoring what I say and do it.
BBThumbHealer said:
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
Thank you @BBThumbHealer.
Damn man that's the basic steps that you are following and that too pretty neat and right. Even though it is causing issues then there might be some other hardware bug may be ! Hope your phone gets started soon!
Hi Guys,
phone : Moto G (XT1033), Falcon
- stuck in bootloop
- able to go to recovery
- unable to flash custom recovery such as twrp or cwm
- as suggested,
1. Unlocked the bootloader successfully, can see code status = 3 in recovery mode
mfastboot oem unlock <CODE>2. Unable to flash twrp. It writes successfully but shows stock recovery only
mfastboot flash recovery twrp-3.0.2-0-falcon.img3. so tried booting twrp using with success
mfastboot boot twrp-3.0.2-0-falcon.img4. cleaned cache, dalvik etc.
5 using twrp, used ADB which enables MTP which let me transfer Android6.0.1_NX_R10.3.3_MotoG2013.zip to internal memory
6 Using twrp to flash ROM - Android6.0.1_NX_R10.3.3_MotoG2013.zip
It seems it started installing but its been more than one hour and it seems its still doing something.
It has stuck at - "Patching system image unconditionally..."
is this normal? Did I miss anything?
Appreciate help in advance. thank you for your time...
Best Regards,
Jignesh
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.
EDIT : I dont know how to delete this post, but I already solved my problem ! Sorry..
I just didnt go until the end of the instructions and forgot to install my new OS..
Hi everybody !
I decided recently to install TWRP (I have never done that before).
I have a samsung galaxy s7 (smg930 w8).
I followed instructions using Odin.
I had a lot of trouble booting into recovering mode after downloading TWRP but I finally managed to it.
Then I think I installed TWRP and dm-verity (what is it for by the way ?).
But then, while rebooting system, I got a boot loop...
I am back into TWRP recovery mode, but I have honestly no idea what to do.
Thank you very much in advance.
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?