My Nexus 5x is running cyanogenmod and an older version of TWRP that I used to root the device over a year ago. Usually bootloop is not a problem because I can fix the issue through recovery. My recovery is encrypted and when I go to enter the password to decrypt it, my phone freezes and resumes bootloop. What options do I have?
Flash stock images via fastboot?
Open TWRP and enter it without the password. Head over to Format and swipe the bar, type in YES and format your devcie.
YES YOU WILL LOSE ALL YOUR DATA, but this solves the issue of encrypted recoveries.
Also if possible, get the latest version of TWRP which I believe is 3.0.2.2, from their official website.
Let me know if it works.
I have tried to flash all factory images via fastboot, but when I re-flash and get in to TWRP, my recovery crashes and my phone goes back to bootloop.
Related
I've recently flashed the latest twrp on my oneplus3 a3003 through fastboot. All fine, I flashed the cyanogenmod 14.1 and the gapps 7.1 over the oxygen os. Now I tried to boot into recovery to flash the pixelfy zip file, but I found out that I can't access recovery mode. All I get is boot logo and the capacitive buttons illuminated for a while, then the screen goes off and I have to press the power button for 6/7 seconds. I tried reflashing the recovery.img through the terminal and no result, I tried through TWRP manager, it says successful but the result is still the same. Ah, before installing the twrp I hard bricked the device and I unbricked it, so to me it's like a corrupted partition. Is there a way to restore twrp (or to restore the recovery partition, still being able to flash twrp) without losing data? If no, is there a way to restore it to a funcional state without having to use qualcomm drivers? If no, is there a way to restore it to a funcional state AND keep it that way?
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Vas0sky said:
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Click to expand...
Click to collapse
Is it possible that you gave me this recovery? I'm looking for one too same problem as you
Thanks
http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Here you go.
I was running an unlocked one plus 3 on OxygenOS 4.0.2 (Android Nougat) and have TWRP installed. As 4.0.3 got released yesterday, i tried installing it today but i accidentally hit install on the OTA update setting which caused my phone to reboot. Now my phone won't boot into the os, i get a black screen after 'powered by Android'. I tried getting into Recovery however i get the same response, a black screen. I do not think it is hardbricked as the Fastboot still works and when i go into fashtboot it states that the OEM is 'unlocked'. I have personal data on this device pls can someone help. I do not know what i should do> How do i boot into recovery without crashing?
Is it possible to install twrp again with the PC? I had once also the same problem, install it again and after that it booted again into recovery.
Just install TWRP from fastboot, then you'll have access to internal storage by TWRP
It's happening because it's trying to send you to recovery which is twrp 3. 0.4-1which is bugged so just go to fastboot and flash twrp 2.0.4-1 and then try booting in.. You can even update the phone by flashing the update zip by oneplus from recovery
Device - oneplus 3
Secure Boot - enabled
Device State - Unlocked
recently wanted to update my rom (Resurrection Remix-N). When I boot into TWRP, I get an error 7. I was also having issue with titanium backup (keeps crashing) so I was thinking it was the ROM since I haven't updated in a while. Since I couldn't update with TWRP and error 7, I decided to switch ROM.
I did a nand backup, then proceeded to factory reset in TWRP, reboot recovery (habit of mine).
And now I was stuck with at TWRP decrypt Data because my previous pattern is not working. Gives me a "pattern failed, please try again!")
My question, is there a way to at least get my data off the device (backup to laptop and restore later)?
I can boot into fastboot. but I can't see device storage on laptop.
okie03 said:
Device - oneplus 3
Secure Boot - enabled
Device State - Unlocked
recently wanted to update my rom (Resurrection Remix-N). When I boot into TWRP, I get an error 7. I was also having issue with titanium backup (keeps crashing) so I was thinking it was the ROM since I haven't updated in a while. Since I couldn't update with TWRP and error 7, I decided to switch ROM.
I did a nand backup, then proceeded to factory reset in TWRP, reboot recovery (habit of mine).
And now I was stuck with at TWRP decrypt Data because my previous pattern is not working. Gives me a "pattern failed, please try again!")
My question, is there a way to at least get my data off the device (backup to laptop and restore later)?
I can boot into fastboot. but I can't see device storage on laptop.
Click to expand...
Click to collapse
A method thats worked for me in the past is to use fastboot to re-install TWRP. Use TWRP 3.0.4-1 and reboot your phone to recovery.. You'll be im MTP mode so you can transfer files onto your phone for flashing.. If you get code7 in TWRP, use a different FIRMWARE+Modem version.. If you want the latest RR use 4.0.3.. Your data should be safe..
hagar006 said:
A method thats worked for me in the past is to use fastboot to re-install TWRP. Use TWRP 3.0.4-1 and reboot your phone to recovery.. You'll be im MTP mode so you can transfer files onto your phone for flashing.. If you get code7 in TWRP, use a different FIRMWARE+Modem version.. If you want the latest RR use 4.0.3.. Your data should be safe..
Click to expand...
Click to collapse
I have already tried that unfortunately, it didn't work. Flash twrp-3.0.4-1-oneplus3 but I am still asked to decrypt data. My internal storage show as 0MB I also have MTP enabled but still not showing on laptop. It shows device connect but no storage.
okie03 said:
I have already tried that unfortunately, it didn't work. Flash twrp-3.0.4-1-oneplus3 but I am still asked to decrypt data. My internal storage show as 0MB I also have MTP enabled but still not showing on laptop. It shows device connect but no storage.
Click to expand...
Click to collapse
I had that once when i messed about with f2fs.. Only way i found was to flash stock ROM and recovery, reboot and fastboot TWRP again.. Now my laptop could see my phone and i could start from scratch again.. I'm sure there is a better way but this worked for me.. Sorry i cant be of more help
Flash all 670 img's till one works :laugh:
I think error 7 is related to firmware flash 4.0.3 and then your rom of choice should be fine
hagar006 said:
I had that once when i messed about with f2fs.. Only way i found was to flash stock ROM and recovery, reboot and fastboot TWRP again.. Now my laptop could see my phone and i could start from scratch again.. I'm sure there is a better way but this worked for me.. Sorry i cant be of more help
Click to expand...
Click to collapse
You were lucky. I flashed stock recovery so I can flash stock rom but still no luck. I miss samsung odin.
Thanks anyways for ur contribution.
Down graded to Oneplus 2 until I fix my phone.
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp
Hi,
I downgraded my Nexus 5X from stock 8.1 (OTA) to the latest stock 6.0.1 firmware (via fastboot), and booted up to make sure it's working. All is fine. Device is wiped to a factory state.
I then flashed the latest TWRP recovery, and then rebooted to recovery to try and flash Magisk. At this stage, TWRP asks me for a password to decrypt data, and I didn't set any password at all. If I click on Cancel to continue, I'm able to see the zip file that I placed in /sdcard, presumably coz it's encrypted and TWRP can't read it? What's the password though?
I notice upon Android bootup, under Settings->Security, that my phone is encrypted. I tried factory resetting the phone to disable encryption, but it shows up encrypted even after factory reset.
Also noticed that when I try to reboot, it always reboots back to TWRP rather than Android. Once I flash it back to the stock recovery, then I can boot to Android.
How can I get TWRP to work on an encrypted phone without a password?
I had a similar issue with 8.1. I reset my phone, waited booting and setup is done, then I tried different versions of TWRP and finally no password required!
Which version of TWRP worked for you?
I ended up using 3.0.2-2, which was released around the same time as the 6.0.1 image that my N5X is running on. Formatted data and wiped everything but system in TWRP, rebooted to TWRP, and it worked after that. Weird how fastboot format userdata didn't work.