Related
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Heisenberg said:
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Click to expand...
Click to collapse
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
ent3rpryze said:
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
Click to expand...
Click to collapse
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
ent3rpryze said:
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
Click to expand...
Click to collapse
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Heisenberg said:
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Click to expand...
Click to collapse
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
ent3rpryze said:
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
Click to expand...
Click to collapse
I've never seen this happen before. I'm pretty sure you can use Tasker to automate backups. I usually advise people to keep at least one backup or ROM zip on their phone, just in case.
IT HAPPENED AGAIN!
Per the ever hepful Heisenberg's recommendation, I wiped my phone and reflashed purenexus. This was yesterday. Everything went smoothly. Recreated my security PIN. Was able to unlock my phone with it without incident...until just now. Incorrect PIN error 3 times.
What is going on?!?!
It should be noted that both times this has happened has come after I turned my phone off. This time I happened to be charging my phone while it was off. I can't recall if it was the same case the first time it happened. Is this a purenexus issue?
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Heisenberg said:
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Click to expand...
Click to collapse
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
elevatorguy said:
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
Click to expand...
Click to collapse
thanks for that, but i believe i did that because i backuped a clean factory 6.0.1, sans any security setup. not sure if that was necessary but that's what i did.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
The problem isn't with the ROM, I (along with what I'm guessing is pretty much every other user) use fingerprint and/or PIN/pattern security on Pure Nexus with no issues. A nandroid backup is one of those backups you create with TWRP, so yes it's what you described. But this problem shouldn't be occurring on a clean flash of Pure Nexus, can you please explain in detailed steps how you installed the ROM?
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
On Marshmallow, the scramble pin option is bugged if you use a long pin. Some rom devs choose to leave this out entirely. I haven't played with it to determine the cut off point but 4 digits is fine. I think I tried 8 digits once and it locked me out.
Sent from my Nexus 5X using Tapatalk
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
Awesome.. Thanks a bunch for posting this... I am using Oneplus 3T , Resurrection Remix 5.7.4 ( Marshmallow) . Had turned on Scrambled PIN.. Ran into same issue as yours.. Last option left for me was to do factory reset from TWRP but I was scared to lose Google Authenticator Setup on my phone and many other things... Your solution saved me!! :good::good:
I also had a similar problem:
- freshly installed Carbon ROM with TWRP
- added lockscreen password in phone
- locked screen
- tried accessing using password
The password just fails. Using a shorter password works normally. The failing password is 13 characters long.
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Did you remove all security from your devices before making a backup?
I've seen several posts that tell people to do so before backing up. So I think that's where the issue is.
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
It's affecting the OS?
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
He's talking about the OS, not TWRP.
Heisenberg said:
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
He's talking about the OS, not TWRP.
Click to expand...
Click to collapse
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.
DJBhardwaj said:
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.
Click to expand...
Click to collapse
Not that I'm aware of, I could be wrong though.
Heisenberg said:
Not that I'm aware of, I could be wrong though.
Click to expand...
Click to collapse
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:
DJBhardwaj said:
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:
Click to expand...
Click to collapse
Interesting. I'll have to give it a try myself at some point when I get the time.
Heisenberg said:
Interesting. I'll have to give it a try myself at some point when I get the time.
Click to expand...
Click to collapse
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Which TWRP recovery version did you use?
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
If the backup you restored had a security pin still active then it won't restore properly or you won't be able to deactivate the pin code when asked for a screen pincode. At least that's how it has been in the past. They may of fixed it by now but that's only in the latest version.
This happened to me the other day when updating to the new PureNexus. There's a file in MM you can delete through TWRP so the OS will boot without a passcode, and then you can set a new one. I'm not sure whether I'm allowed to post it here as it seems dodgy but I found it in another XDA forum.
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.
DJBhardwaj said:
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:
Click to expand...
Click to collapse
I can confirm that the issue has been resolved. Performed a backup and restore of my PN setup today.
Everything on my phone was successfully backed up and restored, including pin and fingerprint.
bouchigo said:
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.
Click to expand...
Click to collapse
This is how I fixed mine a couple days ago. Easy and quick. I also recommend this method. Although all I deleted was the locksettings.db because I couldn't find the others lol either way it worked
Sent from my Nexus 6P using XDA-Developers mobile app
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3AOKwsYI1C5WWVTeDZSSFhXZ0U/view?pref=2&pli=1
Try flashing this zip it will remove your current lock security. It is working on my phone though. (Don't have nexus 6p yet ) just be sire to make a backup before as i have never tested this for nexus 6P.
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
318sugarhill said:
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
Click to expand...
Click to collapse
what did you use to update to N?
I was on the beta. I never flashed anything else. Like a dummy I had my adb commands backwards (was using adb instead of fastboot). Otherwise I would have reflashed MM.
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
same here.... guess this is the first brickable nexus device... the only thing that gets me to boot is if I flash N then flash the MM F vendor image, but it does not detect the sim card and camera don't work.
Mgrev said:
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
Click to expand...
Click to collapse
Look in the other post about botched nougat install , some of us got phone working
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
minidude2012 said:
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
Click to expand...
Click to collapse
I have a twrp backup, but it doesn't help at all.
Mgrev said:
I have a twrp backup, but it doesn't help at all.
Click to expand...
Click to collapse
From that thread, my solution.
FragmentsOfLife said:
Okay, this is the method I used to fix my phone. The issue was the phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the lock.
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Click to expand...
Click to collapse
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
Hoping to find the answer for you!
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
anidaniel said:
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
Click to expand...
Click to collapse
I have already done that, and it does not work.
I have already contacted my retailer about getting a replacement.
Hello guys,
I ran the latest oxygen OS and TWRP recovery. Today I saw that the new official Oreo OTA is out so I downloaded the full zip and tried to dirty flash it in TWRP. It did not work out and i got an error, and people suggested to use twrp blu_spark for flashing the oreo build.
So I flashed twrp blu_spark in fastboot, booted into recovery and installed the oreo zip. Before I did that, TWRP always asked to type in my password to decrypt the files.
After flashing oreo my phone wouldn't boot into Android, it just stayed at a black screen while the LED was shining. I realized I had to **** up somewhere so I booted back into recovery, but TWRP doesn't ask for my password to decrypt my data and now everything in my internal storage has weird file names (which I suppose come from the decryption) and I don't know how I can decrypt my data again. I also flashed the normal TWRP but it didn't ask to decrypt my data either.
Can somebody please help me? I can't do anything at all at the moment and I don't want to wipe my system as I unfortunately don't have a backup (I have one, but that's a TWRP backup and in internal storage which is encrypted...).
Thank you so much in advance, you are my last hope
I think my problem is that I don't have a PIN setup in android, because it's actually bricked (had to flash the wrong oreo probably or so). Do you think TWRP will ask for a password again if I somehow manage to install the old oxygen os and setup a lock screen PIN again?
Same Issue here... Searching for a solution
I ended up wiping everything except internal storage. I then pushed the old oxygen os to the internal directory and flashed it (in hope it wouldn't change anything in my internal storage/sd card). Looks like I was wrong. After flashing it also apparently wiped my complete internal /sdcard.
All data gone. Nothing I can do now anyway. If somebody would have known a better way to decrypt my data again with a broken android, feel free to comment - feeling really bad now, so many photos etc. on it. At least learned my lession to always take a back up, but normally I'm super careful and not flashing anything that would wipe/brick something on my device. This freaking oreo update is making me crazy.
Sieth said:
Same Issue here... Searching for a solution
Click to expand...
Click to collapse
If you have broken your android/system like I (it didn't want to boot into the system anymore after flashing) I think there's almost no chance. Atleast my device is clean now and I can't do anything at all and my data is forever gone now. But I learned my lesson and you probably too - always take a backup.
I mean okay, after I thought about it it's not too bad as I didn't have a lot of important photos on it and I fortunately backed up my whatsapp to google drive before playing around so yeah, atleast a clean device now and will look for a nice oreo ROM.
If you think you can find a solution good luck, but I think the only way to get TWRP to decrypt the internal storage partition again is to set up the display lock in your ROM again - and if you have a bricked ROM and flashing a new one it will wipe /sdcard completely like in my case...
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
jahidinbedod said:
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
Click to expand...
Click to collapse
sorry, too late, wiped it already. why should this twrp work? I tried normal one and blu_spark, none of them asked me to decrypt my data.
jahidinbedod said:
test it this twrp
https://androidfilehost.com/?fid=745849072291696652
Click to expand...
Click to collapse
Done and nothing happened, still not asking me to enter a pattern\pin. Is there a way to force it? maybe a line or a terminal code? I remember my pattern ofc
Vanniman said:
Done and nothing happened, still not asking me to enter a pattern\pin. Is there a way to force it? maybe a line or a terminal code? I remember my pattern ofc
Click to expand...
Click to collapse
I don't think there's much chance. I was able to see all those weird filenames in internal storage when connected to my PC, but I could not copy or change files to internal storage. If this would have worked, there might be a chance to decrypt the data manually on your PC if you find how to do it/if it's even possible.
I seriously think there's no good solution for our problem. :/
Michael1200 said:
I don't think there's much chance. I was able to see all those weird filenames in internal storage when connected to my PC, but I could not copy or change files to internal storage. If this would have worked, there might be a chance to decrypt the data manually on your PC if you find how to do it/if it's even possible.
I seriously think there's no good solution for our problem. :/
Click to expand...
Click to collapse
All deleted now... I know that feel
So I wiped the whole device. Adb sideloaded the new rom. Working flawless.
Now installed Magisk 14.0 and device stuck at boot with blue light.
So the rooting is to blame... (In my case...)
So I adbd again the rom.zip and got it working again. But no root for now
Update: flashed Magisk beta v14.6 (1468) and now ist's working.
Vanniman said:
All deleted now... I know that feel
Click to expand...
Click to collapse
RIP our data.. :/ atleast starting with a super clean device now. lesson learned ^^
Hi all.
i was in the same boat as all of you. screwed up somewhere and then lost everything and did a side load. but now the problem is whenever i boot with twrp it still keeps showing my internal storage as 0. so am not able to root it. how do i go about solving this?
---------- Post added at 07:54 PM ---------- Previous post was at 07:54 PM ----------
Sieth said:
So I wiped the whole device. Adb sideloaded the new rom. Working flawless.
Now installed Magisk 14.0 and device stuck at boot with blue light.
So the rooting is to blame... (In my case...)
So I adbd again the rom.zip and got it working again. But no root for now
Update: flashed Magisk beta v14.6 (1468) and now ist's working.
Click to expand...
Click to collapse
How did you flash magisk beta? in my case twrp says that my internal storage is 0
What I did was format not wipe.
ADB sideload rom.zip
Install latest beta from magisk.
So now I have a clean device with working root
Sieth said:
What I did was format not wipe.
ADB sideload rom.zip
Install latest beta from magisk.
So now I have a clean device with working root
Click to expand...
Click to collapse
Nice, data lost as in my case but clean device is great too atleast. ^^
f***, same happenned to me. I did a back-up with twrp before but i left it in my internal memory.
I do have a month old back up on my laptop. How can i push this over to the phone? Can i restore a backup from bootloader ??
I gotta try everything to save my data, too many important things for work on there. I was too ****ing eager to get oreo
I've done the exact same thing. Problem now is that TWRP isn't seeing anything on the phone, there is nothing there. So I can't root with Magisk or install custom recovery.
Edit...had to use blu_spark twrp instead
Bigred065 said:
f***, same happenned to me. I did a back-up with twrp before but i left it in my internal memory.
I do have a month old back up on my laptop. How can i push this over to the phone? Can i restore a backup from bootloader ??
I gotta try everything to save my data, too many important things for work on there. I was too ****ing eager to get oreo
Click to expand...
Click to collapse
Not much chance to get back the data if you can't boot into android at all. You can wipe everything completely and then copy your old backup to your internal storage which will work again once wiped/decrypted. I haven't found a solution to save the data without wiping, I tried different twrp versions like the normal one or blu_spark but none asked to decrypt data and in my internal storage my files were left all encrypted with those weird long file names.
Are you trying to say that all my data is lost even tho I know decryption key? All I did was update to Android O and I had backup and TWRP is showing that my internal storage is full but the files are all encrypted it wont ask me for decryption key. What can I do
SPyxOff said:
Are you trying to say that all my data is lost even tho I know decryption key? All I did was update to Android O and I had backup and TWRP is showing that my internal storage is full but the files are all encrypted it wont ask me for decryption key. What can I do
Click to expand...
Click to collapse
Exactly. That's the weird problem. If I'm right we had to **** up something badly so that TWRP doesn't even know that our internal storage is encrypted and displaying the (encrypted) files just how they are. The problem in my case was that I couldn't even copy the encrypted files from internal storage to my PC or moving files from my PC to my device. The whole partition was just locked, I couldn't do anything on it, neither adb push or whatever else. Tried different TWRP versions but none asked me to decrypt.
I think the mistake is that if you install a new OS version which is somehow not backward/dirty flash compatible (like in my case the new oreo update) your pin/pattern will get deleted and because of that TWRP does not ask you to decrypt as the ROM is telling that you don't have a password set up! But the problem is when you install a new ROM, it wipes /sdcard so the data is lost if you don't find a way to somehow decrypt your internal storage. :/
Really bad to know you can't do anything at all even tho you know your decryption key - I hope someone finds a solution. I for myself wiped because I don't have so much time to look for a solution.
Hi so I just rooted my op6t yesterday after having it for a couple weeks and I did everything fine and installed a couple root apps. I later discovered custom kernels and wanted to flash one. I went into twrp and all the folders were weird names and the same thing shows on my computer when I plug the phone in. After looking it up my phone is encrypted. I never clicked anything that said to encrypted my phone and it wasn't encrypted before. In Android it says it's encrypted and now I have to reset it to unencrypt it? I'm ok with that but that's a little annoying. Some people said something about a bug in twrp that has to do with encryption but I'm confused why my phone just did that. I restored apps and settings with Google backup which I ran right before I rooted the phone and restored right after I rooted it. Does anyone know what caused it to encrypt itself and how I can prevent it from doing it again? Thanks.
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
OnkeIM said:
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
Click to expand...
Click to collapse
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Skyline3499 said:
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Click to expand...
Click to collapse
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
tech_head said:
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
Click to expand...
Click to collapse
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Skyline3499 said:
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Click to expand...
Click to collapse
That version of TWRP does not support decryption.
GO back and flash the stock boot image.
Temp boot TWRP.
install Magisk and move on.
yerger said:
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Click to expand...
Click to collapse
Ok, thanks, that twrp version worked with the encryption and everything if fine now.