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.
Related
Earlier I was on Megapixel Rom running february vendor img. I flashed my PN ROM backup thru flashify then it boots up with my security lock pattern. It shows that my pattern is not correct. I am rebooting to y TWRP but still it doesn't show me any files and I cant flash a zip rom. Someone help me (((
Try using different decryption method...
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Gameplay_Ethan said:
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Click to expand...
Click to collapse
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
lesterinidad said:
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
Click to expand...
Click to collapse
factory reset?
v12xke said:
factory reset?
Click to expand...
Click to collapse
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
lesterinidad said:
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
Click to expand...
Click to collapse
See the sticky thread in General: https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
You might be better off flashing the full factory image to start over and then reflash whatever you want in terms of recovery and custom rom. I did that when I was in the same situation as you. But I have never successfully restored a nandroid backup on the 6P and I never had that problem with any other phone I have ever owned. Different versions of TWRP only give me different issues when I try to restore a backup. I've had bootloops. I've had TWRP ask for a password even though I removed security before making the back up as people advise. I've had backups that seemed to restore until I started getting error messages that there was something wrong with my device and I should contact the phone manufacturer. I've given up on Nandroid backups on this phone.
I flashed the no-verity-opt-encrypt-5.1.zip to disable the internal encryption, but now the phone can't boot into the OS anymore. It can still boot into TWRP, is there any way to recover it? Thanks.
awdrifter said:
I flashed the no-verity-opt-encrypt-5.1.zip to disable the internal encryption, but now the phone can't boot into the OS anymore. It can still boot into TWRP, is there any way to recover it? Thanks.
Click to expand...
Click to collapse
lol that zip doesn't 'disable encryption', it prevents the system from encrypting the storage the first time that it boots with a non-encrypted storage. Installing SuperSU or Magisk is usually enough because they have that script integrated too.
The way to fix it is to go to Wipe --> Advanced wipe --> Format data --> type 'yes'. You're gonna lose your internal storage and data.
After doing that, don't reboot. Go to Install and flash Magisk or SuperSU or that no-verity zip (only flash one of those).
Well, I tried to update TWRP last night and I think I have completely bricked it. To flash it back requires opening up the phone, which I'm not going to do. Maybe I'll make a smash the phone video later. I'm glad I only attempted this after I got a new phone, never ZTE, never again.
awdrifter said:
Well, I tried to update TWRP last night and I think I have completely bricked it. To flash it back requires opening up the phone, which I'm not going to do. Maybe I'll make a smash the phone video later. I'm glad I only attempted this after I got a new phone, never ZTE, never again.
Click to expand...
Click to collapse
Lol the one who messed up was you, not ZTE
If you knew that flashing that zip on an already-encrypted storage wouldn't do anything, it'd still work...
Also, I'm curious: What did you do to brick your phone while attempting to update TWRP? It was as simple as putting the .img on your phone and goin to Install image...
Well, if I knew why it bricked I wouldn't flash it would I? The ZTE phone had some kind of encryption in the internal storage, I was trying to disable it. It probably tripped some security measure. The phone's software was garbage the day I got it (almost 1 year ago). After I rooted it I thought I could flash some third party rom to fix it, but since it was encrypted I can't. I didn't want to mess with my only phone, so I begrudgingly used it for almost a year, but now that I have a replacement phone, I thought I would attempt to disable the encryption and flash different rom just to experiment before giving the phone away. So in a sense I already written off this POS. Never ZTE, never again.
awdrifter said:
Well, if I knew why it bricked I wouldn't flash it would I? The ZTE phone had some kind of encryption in the internal storage, I was trying to disable it. It probably tripped some security measure. The phone's software was garbage the day I got it (almost 1 year ago). After I rooted it I thought I could flash some third party rom to fix it, but since it was encrypted I can't. I didn't want to mess with my only phone, so I begrudgingly used it for almost a year, but now that I have a replacement phone, I thought I would attempt to disable the encryption and flash different rom just to experiment before giving the phone away. So in a sense I already written off this POS. Never ZTE, never again.
Click to expand...
Click to collapse
Okay. For anyone who comes next: it is NOT NECESSARY to root the phone to install a custom ROM! Simply with unlocking the bl and installing TWRP, then wiping system and formatting data, then using the universal bootloader and modem, you can install a custom ROM.
I was asking what you did to brick it while updating TWRP. Never heard about something like that
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.
Well, decryption actually. I would love to disable encryption entirely like on the OP6, but apparently that's not possible due to the fingerprint or something. It's so frustrating. I load OOS then Havoc (or ASOIP, maybe others) and everything seems fine until i try to flash something in TWRP only to find it won't accept my pattern, pin, fingerprint etc. Anyone seen this?
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
king_david43 said:
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
Click to expand...
Click to collapse
ZeroKool76 said:
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
Click to expand...
Click to collapse
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
jaysonic88 said:
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
Click to expand...
Click to collapse
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
reppi said:
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
Click to expand...
Click to collapse
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
jaysonic88 said:
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
Click to expand...
Click to collapse
Ok, i think i found the issue. According to the guy who wrote the unofffical TWRP 3.3.02 it's a bug in the code. He sent the info including the lines of code that were causing the problem to teamwin.
https://forum.xda-developers.com/showpost.php?p=79515334&postcount=2559
Howdy!
I had my 6T PERFECT, just like I wanted it.....exactly like I wanted it.
I downloaded the latest OOS update, clicked ok when it told me my phone would be unrooted after the update, something that DID NOT happen with my last update. I figured no problem, I will just root the phone after the update.
Well, TWRP recovery is gone. I boot into the Oxygen recovery screen. I have a Titanium backup folder that has a boat load of files I do not know how to use. TWRP still has a folder on my phone with 2 back ups in it.
I did a quick search and checked with google and can't find an answer simple enough for me to use.
How can I do a back up of my phone that will restore it just like it is, without me having to set up all the apps again, and set up my launchpad again like I want it.?
Question 2, how do I use the back up files I already have and will that do what I am wanting to do?
I may be hoping for something that does not exist, but I would like to root my phone, restore a backup, and upon reboot see the exact same phone I am looking at now. I can transfer the back up files to my computer no problem, but I don't know if that will accomplish my goal.
Thanks in advance!
JC the Newbie
https://forum.xda-developers.com/oneplus-6t/how-to/guide-local-upgrade-oos-losing-magisk-t3956818
Thanks Striatum, that will help in the future, however, it does not address the questions in my post.
PattayaGlock said:
Thanks Striatum, that will help in the future, however, it does not address the questions in my post.
Click to expand...
Click to collapse
Flash again twrp through fastboot (many guides here and there) flash Magisk and restore your backup, either the twrp ones either titanium backup
Thank you. I will see if I can muddle through either of those.
It looks as though I may have asked the wrong question. Perhaps I should have asked "if my bootloader is already unlocked can I reflash twrp and magisk after an OOS OTA update without wiping my data". I am back up and running with a rooted phone and did not lose any of my data or settings. Thanks for the help.
PattayaGlock said:
It looks as though I may have asked the wrong question. Perhaps I should have asked "if my bootloader is already unlocked can I reflash twrp and magisk after an OOS OTA update without wiping my data". I am back up and running with a rooted phone and did not lose any of my data or settings. Thanks for the help.
Click to expand...
Click to collapse
....I perfectly understood what you wanted to know.
This is basic knowledge, the answer is yes
How can you mess with your /data partition when twrp and Magisk are dealing with /boot partition
Thank you for the clarification.
Basic knowledge for you guys perhaps, but not for a newbie at the stage I am at. Well, where I was before you straightened me out! LOL.
After flashing a custom ROM in TWRP, when I reboot into recovery and click install, all of the directories have turned into folders with names that look like random letters and numbers, and I can no longer read/write from that internal SD card. Anyone know what is going on or have a solution? I don't want to lose my backups or data, that would suck. But if I have to to get my internal storage back, then fine. Thanks in advance if you can help!!!
boobteg2 said:
After flashing a custom ROM in TWRP, when I reboot into recovery and click install, all of the directories have turned into folders with names that look like random letters and numbers, and I can no longer read/write from that internal SD card. Anyone know what is going on or have a solution? I don't want to lose my backups or data, that would suck. But if I have to to get my internal storage back, then fine. Thanks in advance if you can help!!!
Click to expand...
Click to collapse
No need to post your issue in multiple threads...
This has nothing to do with backup it's an encryption hiccup.
PattayaGlock said:
It looks as though I may have asked the wrong question. Perhaps I should have asked "if my bootloader is already unlocked can I reflash twrp and magisk after an OOS OTA update without wiping my data". I am back up and running with a rooted phone and did not lose any of my data or settings. Thanks for the help.
Click to expand...
Click to collapse
I'm in same position. I lost root/twrp after local update. I can just flash twrp again and magisk without loosing data?
callumbr1 said:
I'm in same position. I lost root/twrp after local update. I can just flash twrp again and magisk without loosing data?
Click to expand...
Click to collapse
That is correct. You can flash both without losing any data. That is exactly what I did......and exactly what I was unsure of.
JC