Hey everyone,
I have an OnePlus 3 with LOS 16.0 installed on it.
My hardware buttons stopped working yesterday, so I did an FW update to FW 40 OB.
I tried to reboot after the update, but now I get a message, that my password is correct, but the encrypted data is damaged.
It says that my only option is to hard reset the phone.
I can't even revert to a backup since TWRP also can't encrypt my data.
Is there any way to recover the data / make to phone working again? I already resetted to FW 5.0.8, but I still get the same error.
EDIT (SOLVED):
Regarding to this post https://forum.xda-developers.com/showpost.php?p=79209161&postcount=1477 I can do nothing
Related
Hello,
I have recently flashed the Marshmallow update to my phone coming from WW-2.20.40.194. It was encrypted and used a PIN on both the boot and the lock screen. With Lollipop, I can decrypt my phone in TWRP by entering my lock screen PIN. However, neither TWRP 3.0.2.0 nor a TWRP repack (found at: https://drive.google.com/drive/folders/0Byp0425xydUaYzk1anRCak0zZXc) on Marshmallow are able to decrypt the phone, saying the password is invalid. I have tried the lock screen PIN, "default_password", as well as using an app called "SnooperStopper" to change my encryption password to something other than my lock screen PIN, with no luck. Is anyone else experiencing this or have a fix?
If i recall you must unencrypt before any flash. Your encryption key is now lost along with all your data. Sorry.
Sent from my ASUS_Z00AD using XDA Premium HD app
Maybe you'll need to downgrade to L, decrypt the phone, upgrade to M again and encrypt it a second time.
After uploading the M update, Asus also uploaded a rom to downgrade from M to L, so anyone can perform a downgrade just the same way they did the upgrade.
Thanks for the replies! I haven't lost any data, since I backed everything up manually beforehand. However, even if I didn't backup the data, I can still unlock the phone itself (get past the lock screen and to all my files), just not through TWRP's lock screen. I've tried encrypting before and after upgrading to Marshmallow, with the same results.
UPDATE:
Just tried again with TWRP (tethered and untethered) on a clean install, same results. Steps:
Used fastboot to completely erase phone (data, cache, dalvik, system, etc).
Flashed stock recovery for Lollipop (WW-2.20.40.194).
ADB sideloaded WW-2.20.40.194 in stock recovery.
Wiped data and cache again in stock recovery.
ADB sideloaded Marshmallow (WW-4.21.40.134).
Rebooted to system, logged into Google account, set up system, etc.
While setting up system, chose to lock device with PIN.
After setup, encrypted the phone.
Rebooted to bootloader.
Fastboot boot TWRP.
Tried to enter PIN, says invalid. Tried to enter "default_password", says invalid.
Fastboot flash TWRP, same results.
Hi yes, ive had the exact same problem running a nightly build of CM13 / Android 6.0.1. It just tells me the password is wrong. TWRP 3.0.2.0
Personally I think something changed in recent Android builds and TWRP just hasnt figured out that its broken yet. TWRP 3.0.2.0 is almost 6 months old now ...
I need to find a way to update my roms also so this is a problem.
I am glad to hear it is not just me having this issue. I believe this as well, though TWRP 3.0.2.0 worked just fine on an older version of XOSP (CM13-based, I think from a build around December 2015). Something must have changed since then.
I have discovered the problem. You can read all about it here.
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
tl;dr
Snapdragon 800+ CPU phones (any maybe others) have HW_Crypro (hardware crypto chip) and Android 6 + enables this. Which requires recompiled TWRP with support for HW_Crypto
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
Hello,
I am having issue with my mi mix 2 (chiron), since using custom ROMs (9.0 based). The roms and everything connected with it works fine, but problem comes, when i want to install new OTA update (that is quiet offen, since developer release new version several times per weak). Everytime i boot in recovery (TWRP, last official available version for chiron), data partition is encrypted and i am unable to decrypt it in twrp (twrp says, i have inputed wrong password [i have tried to change to text password, didnt help]). I have also tried different versions of TWRP - same result. The only way how to not lose data is to install update from external storage, which is anoying. Lastly i have tried to search for help here and other forums, but did not find any solution. Does anyone else face this problem and is there any way, how to decrypt data partition in twrp?
Thanks in advance
Marek
Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance
Hey there,
in all my years using/modding android phones I was never this lost on finding the issue.
My Oneplus 5t was unlocked, had latest blue_spark TWRP 3.40 recovery and stock oos 10.0.0 with the blue spark kernel and magisk installed. I just upgraded to the 8t and wanted to revert my phone back to stock. So I made a nandroid backup in TWRP and used the unbrick tool to get the phone in the fastest way possible fully wiped back to stock.
(https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 OOS 5.1.7).
Well after my phone was fully stock I was already kinda suspicious about it not finding any OTA updates and manually installed the latest oos 10.0.1 update. First it seemed like everything was working just fine but then I realised that the camera is not starting anymore and gives me the error "Error starting camera" ("Fehler beim Öffnen der Kamera). Since then I have tried everything possible for 2 days but I still am unable to fix the issue.
Everything I tried.
1. deleting camera app data/cache and phone cache in stock recovery
2.factory resetting the phone
3.Using the latest 9.0.11 unbrick tool from this thread https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
-with this my wifi was not working but the camera was working again
- and this also showed me (while using mobile data) that there is a ota update available (oos 10.0.1)
- after updating my wifi was working and the camera was not working
4.Using at least 7 or 8 different unbrick versions (still from this thread here https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890)
- here I noticed that as soon as I had a android version below 9 it would not show me available ota updates and would not even let me manually update but camera and wifi was working
5. unlocking the bootloader, flashing twrp 3.40 and restoring my nandroid backup
- camera is not working
So as you guys can see I am really close on losing my mind with this phone and I would appreciate any help you can give me :fingers-crossed:
// looks like I need to send in my phone to Oneplus
//Oneplus "certified" service in poland was unable (my guess is they did not even bother) to find the issue and quoted a 300€ repair bill for changing the mainboard ^^
Anybody else with this problem? My 6 Pro gets soft bricked with the
SD1A.210817.036.
It loses the signal (Tmobile) then restarts to recovery saying
“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."
Device Completely stock
This is what I have done
1
Try Again (Same behavior)
2
Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.
3
Sideload Rescue OTA (SD1A.210817.036.) same ****
4 now with heavy weapons
Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.
5
Got a device replacement (Hella lucky they had my device in stock)
6
Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.
7
Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)
Always the same problem.
There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin
Any suggestions?
Only thing I see consistent is the data being restored. That data could be corrupted. Not sure if that's possible. Try setting up as new device or from a different backup.
I think"new device" is the way to go. Over the years I've found some apps don't work with a new update.
Points 5 and 6 suggest that it's something to do with your data and app restore causing the issue.
How modified was your previous device?
Just got my Pixel 6 Pro yesterday. I have had to restore 3 times. The first two were from a back up and the third time, from scratch and the same thing is happening. It took a while for the third time to happen (over night and a few hours into the day) and I thought I was safe and put a screen protector on and then bam! Just before it happens I get a lot of the Google apps like phone app and some heat app crashing, then it reboots and says Android is corrupt.
Corrupted data error message after December update
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
forum.xda-developers.com