I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
JimZiii said:
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
Click to expand...
Click to collapse
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
Try removing pin/password in settings and see if it still asks for key.
ante0 said:
Try removing pin/password in settings and see if it still asks for key.
Click to expand...
Click to collapse
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
You can Format Data (removes encryption) and edit /vendor/etc/fstab.xxxx and remove the fileencryption line on /data.
I don't have an Honor 8 so I can't check it, but this is how it was done on Mate 9/10 before we got TWRP with decryption on Oreo.
Of course, flashing a new firmware will replace fstab so you'd have to edit it again/restore previously edited one.
Edit: Also, for fun, default password for decryption is "default_password", so you could try that. It most likely will do nothing. This is done automatically when you have no password/pin set.
cypher187 said:
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min ?
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
---
JimZiii said:
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
Click to expand...
Click to collapse
Unfortunately there is no way. Only with HiSuite or sth else. If your device is rooted you can use TitaniumBackup. It can provide a more complete backup of apps, app-data and settings.
Sent from my FRD-L09 using XDA Labs
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Mumtaz77 said:
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Click to expand...
Click to collapse
Install a full package via dload method. Take an 'unbrick' guide from the guides section if you need. You can use a 'FullOTA' package for your region which you can download with FirmwareFinder by TeamMT.
Sent from my FRD-L09 using XDA Labs
Related
Hi there. Recently (just yesterday) I tried flashing TWRP 3.1.0-0-herolte via Odin V3.12.3.0. However I ran into a little issue. Bootloop. TWRP seemed to work fine, but the phone wouldn't boot into android (stock touchwiz), exhibiting the 'samsung galaxy S7' logo periodically, but not going past that. Firstly I'll give some details on the phone and how I 'tried' to to flash TWRP. The phone I have is an Exynos variant SM-G930F running Android 7.0 and the recent update from late March. It is an Australian model (otherwise known as the 'international' version I think). Anyway as for what I was using as a guide, it was this. Before attempting this I enabled 'OEM unlocking' within the developer options but not 'USB debugging' (not sure if this contributed to the issue, but thought I'd mention it anyway). Later on I downloaded the Samsung Mobile Drivers and the tar file for TWRP. Installed the drivers, opened up Odin, entered download mode on the S7. I placed the tar file in AP and connected via micro usb. Almost everything, including auto-reboot, was turned off except F. Reset Time. Though chances are I probably left it on because I'm a doofus. After all that I pressed 'start' without doing any button combinations. Then after the screen went blank I pressed volume up + home hey + power button, roughly all at the same time. And then I entered TWRP. I then swiped to 'allow system modifications'. However as I didn't want to root the phone at the time, I decided to power it off through the menu. The next time I pushed the power button however, it was stuck in a bootloop. I then went back into TWRP and noticed that when I went into the install menu and was looking at the internal storage it appeared as 0mb (I thought that twrp had deleted all my files at the time), and I couldn't access the files I normally do like the downloads folder or app folders. However it seemed like most of the system folders were there like 'root' and 'data' etc. I then formatted the data and then did a factory reset as I thought it might fix the problem but it didn't. I swiped to install the twrp app but unchecked the two boxes. I then did some research and found out that if I ever were to run into an issue like this that I should flash the stock firmware, which is what I did. And viola! It worked again! I was slightly stressed at the time, lol. Luckily the apps and data I had previously were stored in the cloud.
After all this I have a question, what do you guys think I did wrong? Have you ran into this issue before? And what do you think may have caused the bootloop. I eventually want to start rooting my S7 and perhaps flash a rom, but I don't want to run into the issue again. Cheers!
P.S. I'm probably the biggest tech noob I know so go into a little bit of detail if you know what I did wrong so I don't make the same mistake again
Sounds like you hit the problem listed in step 9 & 10.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot
Click to expand...
Click to collapse
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Beanvee7 said:
Sounds like you hit the problem listed in step 9 & 10.
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Click to expand...
Click to collapse
Hm, that might actually be it. As a question how would be able to do that? Do I need to download that separately or something ( the dm-verity and encryption disabler zip I mean)?
EDIT
Actually never mind, it seems to say it right within the guide lol. So the problem should go away if I do that first yeah?
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Beanvee7 said:
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Click to expand...
Click to collapse
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
amalantony said:
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
Click to expand...
Click to collapse
Already did that before bro. Works as swell as a bell.
TheNickleS said:
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
Click to expand...
Click to collapse
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Beanvee7 said:
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Click to expand...
Click to collapse
From what I understand that's because the ldm-verity triggers. And so formating the data removes any encryption allowing for things to be flashed. But because I didn't do all of that first my S7 wouldn't boot up past flashing twrp.
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
So you went 4 years without doing a backup? I think your out of luck.
First, I am pretty sure all your data is gone absent some expensive recovery.
Second, when you took the ota, you went back to stock, which is why twrp and magisk disappeared. This is actually how the system is supposed to work.
I don't know what you did in the stock recovery to cause a wipe. You should have rebooted to bootloader and reinstalled twrp from fastboot.
iElvis said:
First, I am pretty sure all your data is gone absent some expensive recovery.
Click to expand...
Click to collapse
is it possible to recover encrypted storage on an android? i have simply turned the phone off immediately on seeing the new install screen boot up.
iElvis said:
Second, when you took the ota, you went back to stock, which is why twrp and magisk disappeared. This is actually how the system is supposed to work.
Click to expand...
Click to collapse
Fair enough. I knew that.
iElvis said:
I don't know what you did in the stock recovery to cause a wipe. You should have rebooted to bootloader and reinstalled twrp from fastboot.
Click to expand...
Click to collapse
This is exactly where it's just crazy wrong. It just booted up to a recovery, with a screen saying "Decrypt" and a keyboard! NO mention of the next step being "Wiping".. ! This is just plain crazy, if that's how its designed!
94burns said:
So you went 4 years without doing a backup? I think your out of luck.
Click to expand...
Click to collapse
pretty much. was just migrating data from one phone to the next using titanium backup/restore.
How could 4 years of photos and vids be gone? The phone is only weeks old. Surely you have backed these up to a cloud or even a pc at some stage? If you habe data backup turned on, you should have all your apps ready to reinstall.
You should have booted into bootloader, flashed twrp and magisk after the update. The OTA will always resort any custom recovery to stock.
hallo dare said:
How could 4 years of photos and vids be gone? The phone is only weeks old.
Click to expand...
Click to collapse
I just kept migrating it from the previous phones to the next phones. Google photos does have backup of photos and videos. But there was so much more: SMS, call logs, whatsapp photos (the ones which were unlinked due to being moved to SD card earlier), screenshots, voice recordings, telegram images/videos, google authenticator tokens, and many apps whose data doesn't get backed up as part of android/google backup.
angadsingh said:
is it possible to recover encrypted storage on an android? i have simply turned the phone off immediately on seeing the new install screen boot up.
This is exactly where it's just crazy wrong. It just booted up to a recovery, with a screen saying "Decrypt" and a keyboard! NO mention of the next step being "Wiping".. ! This is just plain crazy, if that's how its designed!
Click to expand...
Click to collapse
I don't have answers for either question. You might have more luck posting in the OP community, or in the official firmware thread.
angadsingh said:
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
Click to expand...
Click to collapse
You have a rooted device with a custom recovery so how did you install those in the first place and not loose data then? That wipes your phone doing that. It wiped again because it was being unlocked and relocked that always wipes it. Don't claim this is no fault of your own your running a modified device so yes it is your fault don't come on here and play victim it's really annoying
---------- Post added at 11:50 AM ---------- Previous post was at 11:47 AM ----------
94burns said:
So you went 4 years without doing a backup? I think your out of luck.
Click to expand...
Click to collapse
Wants to go 4 years without a backup then mod his phone and claim it's not his fault he lost data ??? what a joke
That happened to me too, but I solved it because after I flashed stock and then upgraded to 5.1.6 I installed TWRP in fastboot before booting to recovery.
angadsingh said:
I just kept migrating it from the previous phones to the next phones. Google photos does have backup of photos and videos. But there was so much more: SMS, call logs, whatsapp photos (the ones which were unlinked due to being moved to SD card earlier), screenshots, voice recordings, telegram images/videos, google authenticator tokens, and many apps whose data doesn't get backed up as part of android/google backup.
Click to expand...
Click to collapse
Surely you have those titanium backup files though still right? Just restore from that, sure you may lose a week or two but it's better than 4 years.
Sent from my ONEPLUS A6003 using Tapatalk
TechOut said:
You have a rooted device with a custom recovery so how did you install those in the first place and not loose data then? That wipes your phone doing that. It wiped again because it was being unlocked and relocked that always wipes it. Don't claim this is no fault of your own your running a modified device so yes it is your fault don't come on here and play victim it's really annoying
Click to expand...
Click to collapse
Android is supposed to wipe data only on unlocking the device. Once it's unlocked there's no reason Android should automatically wipe data.
It did not get relocked. It is still unlocked. How did you come to that conclusion?
Also, I root my device ONLY to install TitaniumBackup and Helium. I do not meddle with anything else being root (no ROMs, tweaks, etc.). Is it my fault that Android STILL doesn't have a way to backup everything without having to root your phone and install special backup apps?
How can the OS just wipe the data partition without user consent? With NO message displayed whatsoever. Just ask a password go on "Wiping.. please wait". What the hell.
geoff5093 said:
Surely you have those titanium backup files though still right? Just restore from that, sure you may lose a week or two but it's better than 4 years.
Click to expand...
Click to collapse
Yes I could recover some data from the SD card of my previous phone. Not the TB backups though.
I really need a way to (a) image the phone so that I can possibly recover/pay for recovery in the future (b) recover the data from the phone
I did a little reading. Apparently forced encryption is something that Android Oreo comes along with. All the data files are now by default encrypted (at a file level not a partition level). It is apparently encrypted with some randomly generated encryption key decided by Android, and not the PIN you have set to lock the phone. The PIN is just associated with that key. I'm pretty sure that key got deleted as well when the device was wiped (I'm assuming it must have been implemented like that as a security measure). So I have a wiped data partition with encrypted files!
NateDev said:
That happened to me too, but I solved it because after I flashed stock and then upgraded to 5.1.6 I installed TWRP in fastboot before booting to recovery.
Click to expand...
Click to collapse
You knew the data partition would get wiped otherwise? I've been rooting for years and never seen such behavior
angadsingh said:
Yes I could recover some data from the SD card of my previous phone. Not the TB backups though.
I really need a way to (a) image the phone so that I can possibly recover/pay for recovery in the future (b) recover the data from the phone
I did a little reading. Apparently forced encryption is something that Android Oreo comes along with. All the data files are now by default encrypted (at a file level not a partition level). It is apparently encrypted with some randomly generated encryption key decided by Android, and not the PIN you have set to lock the phone. The PIN is just associated with that key. I'm pretty sure that key got deleted as well when the device was wiped (I'm assuming it must have been implemented like that as a security measure). So I have a wiped data partition with encrypted files!
You knew the data partition would get wiped otherwise? I've been rooting for years and never seen such behavior
Click to expand...
Click to collapse
Take this as a lesson, always have a backup. Especially if you mod your phones
Sent from my ONEPLUS A6003 using Tapatalk
angadsingh said:
Android is supposed to wipe data only on unlocking the device. Once it's unlocked there's no reason Android should automatically wipe data.
It did not get relocked. It is still unlocked. How did you come to that conclusion?
Also, I root my device ONLY to install TitaniumBackup and Helium. I do not meddle with anything else being root (no ROMs, tweaks, etc.). Is it my fault that Android STILL doesn't have a way to backup everything without having to root your phone and install special backup apps?
How can the OS just wipe the data partition without user consent? With NO message displayed whatsoever. Just ask a password go on "Wiping.. please wait". What the hell.
Click to expand...
Click to collapse
It did have consent when you took the OTA with your modded device and it said decrypt and asked for your password it was about to wipe. Again you modded your phone and didn't keep a back up this is no one's fault but yours
Yeah I always back up my messages, photos, etc.. To a PC before any type of flash or update, I use smsbackup and have it uploaded to Google drive also titanuim backup and move the files to PC and just back ur DCIM folder. Sorry for ur luck but we all learn lessons the hard way, and no u Cannot recover, but if u have ur old phone may still have the texts on them and use oneplus switch to move them over
I guarantee this post is from a troll, nobody is dumb enough to do any or all of the idiotic things the OP claims.
Got the (important parts) of my data back. It only wiped the "data" partition - which contained internal app data and sms/calls, etc. It did not wipe the "sdcard" partition (also called "internal storage"). Found this out when I was installing TWRP again (before going through the OS welcome process) to create a dd image of my device for possibility of a future recovery. Android file transfer (thanks to TWRP's MTP support) popped up and showed all my files on the sdcard partition. Immediately backed it up.
To all those senior members who're making fun of this, thanks for all the help, really. You guys were really helpful.
angadsingh said:
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
Click to expand...
Click to collapse
I think this is impossible.. First the phone didn't return to me the root message before updating like oneplus 5 and second point, if you enter the pin to decrypt your data in recovery it never do an automatic wipe i'm a bit confused on what you've really done, but for sure you did something wrong because updating system had never wiped anything
Hitman478™ said:
I think this is impossible.. First the phone didn't return to me the root message before updating like oneplus 5 and second point, if you enter the pin to decrypt your data in recovery it never do an automatic wipe i'm a bit confused on what you've really done, but for sure you did something wrong because updating system had never wiped anything
Click to expand...
Click to collapse
Well this is completely possible, I just had the same thing happened to me. It was exactly as OP described it (except it was OOS 5.1.7, and it did not even ask me to input a pin when I rebooted to recovery). Fortunately I had a backup, so it didn't impact me much but still, it is a very weird thing.
angadsingh said:
Got the (important parts) of my data back. It only wiped the "data" partition - which contained internal app data and sms/calls, etc. It did not wipe the "sdcard" partition (also called "internal storage"). Found this out when I was installing TWRP again (before going through the OS welcome process) to create a dd image of my device for possibility of a future recovery. Android file transfer (thanks to TWRP's MTP support) popped up and showed all my files on the sdcard partition. Immediately backed it up.
To all those senior members who're making fun of this, thanks for all the help, really. You guys were really helpful.
Click to expand...
Click to collapse
Thanks for being sarcastic about being helpful. Sorry we can't hold your hand and fix all your problems because your not responsible for your own actions of modding your phone and can't take the consequences when they arise. Maybe you should learn how some more things work and what can happen when you do this before you do it and don't backup your device ever
Hi. I tried to restore a Nandroid backup taken using OOS Pie stable and bluspark twrp. I had disabled any kind of lockscreen security before backing up and restoring. I did not install a single user mod (which is required for the pixel 2 at least). After restoring, all my internal storage is completely messed up with filenames that are random strings that look encrypted. Rebooting the phone always lands me in recovery and flashing the OTA zip does nothing. Plz halp
darkfire404 said:
Hi. I tried to restore a Nandroid backup taken using OOS Pie stable and bluspark twrp. I had disabled any kind of lockscreen security before backing up and restoring. I did not install a single user mod (which is required for the pixel 2 at least). After restoring, all my internal storage is completely messed up with filenames that are random strings that look encrypted. Rebooting the phone always lands me in recovery and flashing the OTA zip does nothing. Plz halp
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
hope this helps, cheers.
vtec303 said:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
hope this helps, cheers.
Click to expand...
Click to collapse
Thanks! That sort of mitigated the issue. The device was stuck on the boot animation and I had to flash the latest stable OTP image again but after that, it started to boot and all my data was preserved. The only caveat was that the standard bootloader is unlocked message was replaced with an ominous "Your device is corrupted" message
/rant
On a side note, for all their claims of being super dev friendly, oneplus is making it annoyingly hard to mess around with their devices by not releasing full device images. It's not easy to restore to stock after ****ing around with stuff. When I used to mess around with my pixel, the stock images made it so easy to restore to stock with no problems for all the stuff I did with it, I had never run into issues where it forced me into crash dump mode or left me booting only to fastboot.
/end rant
/rant 2
XDA auto censors swearing wut?
/end rant
Hey guys.
Got a Oneplus 6 running lastest OTA with latest TWRP installed.
Before flash this latest OTA, I was running latest open Beta, flashed by TWRP, with no problems.
Just booted on TWRP today to flash latest Beta again, but when I drawed the patterns, TWRP restarts. Tryed some more times, same thing, put the right patterns, TWRP imagem boots into it again.
Rebooted into system, but the system said wrong pattern now. Can't boot in system anymore too.
Booted in TWRP again, went to File Manager, and deleted these files inside /data/system (Guess I ****ed up even more here)
locksettings.db-wal
locksettings.db-shm
locksettings.db
Now I can boot in system, but it stay stuck on Initializing system on screen, and I can access only configuration using the status bar. Tryed to set the same pattern on security, still don`t work on TWRP decrypting, and system keeps saying Initializing.
Got pretty stuck here, don't know nothing else to try, anyone have any clue on what I can do?
When asked for the pattern in TWRP instead of trying to enter it choose the "do not decrypt /data" option. Then you can format (not wipe) /data. Obviously you'll lose everything, including on internal storage.
And also, it may happen again if you don't flash the no_verity zip. That stops the ROM re-encrypting /data. See this thread for more info.
Looks like some Security Patch downgrade stuff. You flashed an older build, encryption gets messed up because the Security Patch date is older than the one previously installed, you'll have to format your Data partition to decrypt the storage.
As said above, running decrypted will prevent those situtations
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
And: instead of a pattern, it's recommended to use a PIN (at least 8 digits) or password (at least 6 letters/digits/specialchars)
remewer said:
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
Click to expand...
Click to collapse
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Totone56 said:
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Click to expand...
Click to collapse
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Agreed, that is what i personally do. I like being able to flash anything and potentially having to format the whole storage without any worry. Using Google Photos, Keep, Doc, ect, using Spotify and syncing every contact really makes life easier.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Which is fine if you are only getting this issue directly after ROM flashing or at some other predictable time. But when I was getting it, my lockscreen code/pattern was initially working fine after flashing the ROM, then it would stop working at some seemingly random moment. So the only way I could reliably have any data stored was to run with /data unencrypted. Which I agree is not ideal.
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
the.cybertronic said:
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
Click to expand...
Click to collapse
The bad news is once twrp loses access to data. The only fix is to format data and everything will be fixed.
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
The reason that format is the only answer is because when twrp does not ask for password. It believes you are unencrypted. What has happened is the file that store your password and encryption key is corrupted so any answer you give is wrong.
There's nothing you can do but format data. I've encountered this issue already.
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Joker123## said:
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
Click to expand...
Click to collapse
vegetaleb said:
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Click to expand...
Click to collapse
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
Zhuang zhuang said:
There's nothing you can do but format data. I've encountered this issue already.
Click to expand...
Click to collapse
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
the.cybertronic said:
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
For future reference, brick means a brick. Like, can't boot to fastboot/twrp/or use msmtool
the.cybertronic said:
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Zhuang zhuang said:
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Click to expand...
Click to collapse
damn, good to know if I ever install OOS again - I now switched to Havoc... even though I had to skip rooting it all together after I couldn't get Magisk running with the latest safety net changes (thanks Google -.-)