TWRP Can't Decrypt - OnePlus 3 Questions & Answers

I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
I have two questions. What is causing this problem? And second, any way I can use fastboot to downgrade firmware 3.2.6, so that I can at least access my internal storage and back it up. I got loads of data in there.

Djalaal said:
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
Hi I made that too with this rom! (https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-5-8-0-oms-t3527344) I think it is that 3.0.3 TWRP that did it! I hawe to wipe everything but i got it working! with these instruction https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ Method 2 worked for me but it wipes all! there seemed to be instructions for not loosing all but i cant test it
Click to expand...
Click to collapse

I have found a solution. Even without decrypting /data, you can still get into recovery (except you can't read your data partition). This is key. What I did is simply use recovery sideload to flash the old 3.2.6 firmware (apparently flashing works even without decryption), use fastboot to flash twrp 3.0.1, and backup all my data to the computer via mtp. Then I completely wiped everything, flashed the new firmware and recovery, and decryption worked.

Related

[Q] Bootloop on recovery

Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.
My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

Cannot install 4.0.2 update

I was using 4.0.0 stock with twrp and root. Tried to install the 4.0.2 update but every boot just took me back to recovery. Tried wiping clean, no change. Tried installing stock recovery v2.0, recovery would hang. Tried using new twrp 3.0.3 and I could get back in, but any ROM, stock or not I installed, would not stick.. Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM. So in the end I flashed OOS 3.2.8 with twrp and then flashed stock recovery. At this point I'm pretty much at factory stock at v3.2.8 with stock recovery v1.0. Now I'm trying to update to 4.0.2 via OTA and for the 3rd time already I have received a installation failed message and rebooted to system. The first time I thought it was because I disconnected VPN after starting the download, so I downloaded a second and a third time. I don't want to resort to sideloading again because I fear I might get the same no OS installed problem I got when I tried to install 4.0.2 in the first place. Does anyone have any insight on what is wrong?
Steps:
1. Install latest Official or Modified TWRP ( 3.0.3/ 3.0.3 version 14 by eng.stk)
2. Enter into recovery. Connect phone to PC and copy downloaded ROM file.
3. Wipe everything in the recovery- Data, System, cache and Dalvic. It will erase everything.
4. Flash ROM zip after completing, don't reboot phone. Reboot to recovery again, and then reboot phone.
If u reboot phone directly after flashing ROM, u will loose TWRP.
Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM.
Click to expand...
Click to collapse
This is pretty normal for nougat OOS. I've faced it for all 3 ROMs i flashed. Don't worry, your ROM was flashed successfully. You can mount and check the /system partition, you can see your ROM files there.
So here's what worked for me. (considering you are on ext4 /data)
1. Flash latest official twrp recovert ext4 version or use the file system swapper zip if it doesn't decrypt your data in recovery. TWRP has some issues as of now and mounts f2fs as default, so you just need to flash the file system swapper zip in order to swap it to ext4 by default.
2. Wipe /system /cache and dalvik cache.
3. Flash full 4.0.2 ROM zip, should be 1.4 GB in size.
4. Flash TWRP image again just in case.
5. Reboot to recovery, not to system.
6. Flash stable 2.79 Super Su and you are good to go.
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
IonAphis said:
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
Click to expand...
Click to collapse
Have you tried this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
P.S. I think you did, but I'm just asking.
Thanks for the tip, but I fixed it. Ended up flashing v3.2.8 via twrp and installed OTA to 4.0.1 via sideload. Recovery would not boot unless first fully booted into the system. After that sideloaded 4.0.2 via OTA and now back to complete stock.
Thanks guys!

Tried flashing Lineage OS but ended up stuck in a boot loop.

I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.

Issue with custom recovery(TWRP) after rooting second time

I have rooted my redmi 1s an year ago, and flashed cyanogenmod(13,14) later, lineage14 on it. It uses custom recovery TWRP(3.1.1). Also, I have flashed latest lineage 15 on it ( Increased system partition to 2gb ).
Few days ago, I moved to Stock miui by flashing latest MIUI 8.2 on it. Then, I tried fastboot mode and flashed MIUI9 chinese. Again, flashed MIUI 8.0.1 on it and rooted. Root got succeeded and checked OK. Then, I tried to Flash twrp using twrp manager, twrp official app. Both succeeded, but, cannot boot to recovery. It got stuck in team win logo.
What may be wrong with me?
Please help to flash custom ROM on it again.
Philz recovery and clockworkmod installed through fastboot and works. But, I have less experience on these. I need to install TWRP. Please provide steps and links for installation. Currently on miui 8.0.1.0
I have solved the above mentioned issue. Finally, I have installed twrp recovery. Actually it was the issue with firmware I think. Installed, MIUI 8.2 and flashed twrp 3.1.1 on it and works well.
Now, the issue is to reset partition of internal storage. I have tried this using clockworkmod to remove any issues with file system. Now, internal storage is only 4GB, also I cannot wipe or access internal storage in twrp. How to reset back to 8GB.
rahulg09 said:
I have solved the above mentioned issue. Finally, I have installed twrp recovery. Actually it was the issue with firmware I think. Installed, MIUI 8.2 and flashed twrp 3.1.1 on it and works well.
Now, the issue is to reset partition of internal storage. I have tried this using clockworkmod to remove any issues with file system. Now, internal storage is only 4GB, also I cannot wipe or access internal storage in twrp. How to reset back to 8GB.
Click to expand...
Click to collapse
Flash the fastboot MIUI latest to fix all the issues :good:
simuhnck said:
Flash the fastboot MIUI latest to fix all the issues :good:
Click to expand...
Click to collapse
It again shows only 4GB space. Is there any steps using twrp
rahulg09 said:
It again shows only 4GB space. Is there any steps using twrp
Click to expand...
Click to collapse
Use this as reference - https://forum.xda-developers.com/redmi-1s/general/tut-repartition-redmi-1s-to-increase-t3506904
Add screenshot of storage.

Categories

Resources