I recently used sideload (TWRP) to install a custom ROM (RR (LOS)) on my OnePlus 3
I did not set up a PIN / fingerprint
Rebooted into recovery since install in order to perform TWRP backup
Rebooted into recovery today to flash something different and TWRP is asking me for a password (have no idea what changed)
Since I do not know password, I tried to mount system and it apparently will not mount
Rebooted Android and now asking for password
The bootloader appears to be unlocked (checked in fastboot to be sure)
Wiped Data in Fastboot and have a phone again. So, let's change the question...why or how did this happen?
Was it because I sideloaded the ROM (never did it before and wanted to try it lol)? Or...?
Related
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
Out of sudden any version of TWRP I have can't decrypt /data for some unknown, magical reason.
I tried to make clean start from booting stock and completing initial setup and then installing any custom I had on disk.
Here's what I did:
1. Stock (setup)
2. Bootloader unlock
3. Flash TWRP
4. Flash LOS
5. Boot
6. Reboot to recovery
7. TWRP can't access /data
I tried with official 3.2.2 and 3.2.1 (honestly official builds never worked for me), modded FBE (tried anyway), as well as from https://github.com/TeamWin/Team-Win-Recovery-Project/issues/854#issuecomment-372503905 That last one used to work till this day, now it wont decrypt no matter what I do. Anyone had such issue with this thing, or it's end of my bullhead being a rebel?
Bump
Hello everyone,
I did something stoopid: I changed my twrp after wiping system.
Before I removed every protection from my phone (pin, fingerprints, trusted faces)
Now my data are encrypted.
I sent my old rom (crdroid 31-07) via adb push to sidelod-folder and installed it.
Result: TWRP Bootloop
I restored everything as it was before.
Same TWRP, same vbmeta, but my os just won´t start - it keeps crashing and boot into twrp.
Then I flashed latest fastboot rom with "save userdata", flashed my old twrp and vbmeta again, sideload crdroid, installed -> it reboots to twrp.
Is ther any way NOT to format data and get it decrypted?
Thx for helping!
Edit:
Solved it by installing twrp latest by @redispade + his latest rr release (from telegram channel) - It booted up, I can read my data again & now I save EVERYTHING!!!
I upgraded a couple months ago from 8.1 to 10. I ended up doing a full wipe ( or so I thought) through TWRP and flashing the 10 image. However, it seems that I somehow screwed up the encryption on my phone. I can boot the phone and put in my PIN to access and use the phone normally, but inputting the same 6 digit and my old pre-10 4 digit PIN into TWRP does not decrypt the phone and allow me to flash things. If I continue in read only mode in TWRP, I can flash but everything in my data partition has jumbled file names.
So my question is: Am I going to need to back everything up and wipe in order to fix this? Can I simply use Magisk to disable Force Encryption then decryp that way while keeping my data intact?
I would prefer using the simplest least painful way possible, but if I have to wipe to fix it then so be it.
Twrp decoding doesn't work for Q .. best to remove lock before entering TWRP
Also try "default_password".
Well I got impatient and ended up screwing up everthing.
Now I'm having trouble getting TWRP installed back on the phone. I have wiped everything, flashed the latest January factory image, booted to TWRP image, but when I attempt to flash the TWRP zip I get "failed to mount /system" and "failed to mount /vendor". If I boot back into the installed TWRP, I am not able to flash any other zips such as Magisk.
Sunsparc said:
Well I got impatient and ended up screwing up everthing.
Now I'm having trouble getting TWRP installed back on the phone. I have wiped everything, flashed the latest January factory image, booted to TWRP image, but when I attempt to flash the TWRP zip I get "failed to mount /system" and "failed to mount /vendor". If I boot back into the installed TWRP, I am not able to flash any other zips such as Magisk.
Click to expand...
Click to collapse
Disable your screen lock. Download twrp again to your pc. Put a copy of the twrp.img file on your phone as well. Fastboot into twrp, select instal, select image, go to your twrp.img,.select to install it to Recovery Ramdisk. You'll have to flash custom kernel and magisk again if applicable :good:
Hello There,
I have Redmi Note 5 Pro with unlocked bootloader. But unable to root it no matter what.
Let Me Explain The Situation.
1. After flashing TWRP, it asks for "decryption password" which is nowhere to be found on internet. But in order to decrypt it i had to format the phone. GOOD Now Storage is Detected in TWRP.
2. But if i boot phone in System and again boot it in Recovery then TWRP is replaced with Stock Recovery.
1 & 2 are in INFINITE LOOP now.
3. So OTG...... OTG is not even recognizing by TWRP, but OS is detecting it.
4. TWRP "Enable MTP" also not working.
So Let Me Know If I am Forgetting Something.
Please Help Me To Root IT.
PS : I have past experience of Rooting/ Flashing rom / Unlocking Bootloader etc.
I guess the main problem you're having is that your phone keeps replacing TWRP with the stock recovery once you boot into system. I've had same problem on different devices. To prevent this from happening you should not boot into system immediately after flashing twrp, rather you should boot directly into twrp recovery (try "fastboot boot recovery.img" command after flashing twrp - I'm assuming that your twrp img is saved as "recovery.img") and flash Magisk before booting into system. By flashing Magisk before booting into system your phone would no longer replace twrp, and then your phone would be rooted as well. At least that worked for me.
And also use orangefox rather than twrp on this phone