Hi guys,
I was going to update by dirty flashing tesla rom on my 3T, after booting to TWRP it wiped itself. I rebooted and a welcome screen appeared. I red some posts of people having this problem. Do You have any fix for this? I was using TWRP 3.0.3.1. I then updated to the latest 3.0.4 but the issue was still there. I red that formatting data in ext4 fixes the issue. So I did it and the issue was fixed.
Is there a way to keep data in f2fs and rebooting to TWRP without losing DATA?
I should have the nougat firmware since i updated to official 4.0.2 OOS and then modded my 3T.
Some time ago, I met a similar problem. I updated twrp but Data partition always lost something after rebooting whether in ext4 or f2fs.
And then I ①flashed stock recovery ②relocked bootloader ③unlocked bootloader again ④flashed twrp.
I believe I tryed several times, and it worked and works well in f2fs now.
95先生 said:
Some time ago, I met a similar problem. I updated twrp but Data partition always lost something after rebooting whether in ext4 or f2fs.
And then I ①flashed stock recovery ②relocked bootloader ③unlocked bootloader again ④flashed twrp.
I believe I tryed several times, and it worked and works well in f2fs now.
Click to expand...
Click to collapse
If i stay in f2fs and boot to recovery it asks me to swipe right to allow modifications. Using ext4 it doesn't ask it to me...It's an annoying bug cause I can't flash anything without losing data every time....
phoenixita said:
If i stay in f2fs and boot to recovery it asks me to swipe right to allow modifications. Using ext4 it doesn't ask it to me...It's an annoying bug cause I can't flash anything without losing data every time....
Click to expand...
Click to collapse
Oh , I remember that TWRP was also reset after I converted Date partition at that time.
May be you can try the ①②③④ if you have enough time.
Related
Hey Boys and girls,
I dont know why lineage os 14. 1 dont run on my s4active. Its a I9295.
First i installed twrp 3.1.1.0 recovery with heimdall 1.4.1 on ubuntu 16.04.
Then i flashed lineage-14.1-20171017-UNOFFICIAL-jactivelte from Sd Card in recovery mode
(with the same setup and method i flashed lineage os 14.1 on I9300 and I9500 without problems)
Next i can see lineage startscreen for hours
I tested it too with twrp 3.1.0.0 and two older builds of lineage 14.1. with and without gapps, everytimes I wiped Dalvik, System, Data, Internal Storage and Cache bevore flashing,
and wipe cache&Dalvik after flashing. Always whithout errors.
Thank you everybody and sorry for my scool english
Unfortunately I can't offer help, because I suffer from the exact same problem. Tried to flash tsvetkov_vlad's CM14.1 once some time back in spring already and the behavior has not changed since.
It remains stuck showing the boot animation and does not even arrive at the screen to input the encryption password.
There are no errors in the TWRP log.
Ok, I found the solution (for me). I stumbled accross some blog post claiming that most of the time when the boot animation shows infinitely long, there is a problem with mounting some partition. For me, that was /cache, which I had previously formatted as f2fs. After changing it back to ext4 again, booting works as expected. This has never been a problem with any of the older versions of CM I used before, though.
Maybe this helps?!
Oh yes this was the solution for me too.:fingers-crossed:
I had to formate /cache in f2fs then back in ext4 for four times.
Then booting was completely normal.
Longpu you have changed my live My gratitude will haunt you forever and ever
Hi, Im having a really weird issue. Every single 9.0 ROM i flash boots fine, and once in the system after a second or two it crashes / the screen goes black. This happens on all Pie ROMs. Any ideas? Im using a 64 bit twrp and following all the install procedures...
William1020000 said:
Hi, Im having a really weird issue. Every single 9.0 ROM i flash boots fine, and once in the system after a second or two it crashes / the screen goes black. This happens on all Pie ROMs. Any ideas? Im using a 64 bit twrp and following all the install procedures...
Click to expand...
Click to collapse
Same issue
[email protected] said:
Same issue
Click to expand...
Click to collapse
This is due to encryption. Disable encryption under twrp recovery. Formate userdata partition and then flash pie roms. It will work
santoshx99 said:
This is due to encryption. Disable encryption under twrp recovery. Formate userdata partition and then flash pie roms. It will work
Click to expand...
Click to collapse
How can I disable encryption in twrp? I can't find any option for that.
If you want to disable Encryption, you should wipe Data completely using Format Data, then Advanced Wipe
Note: I'm not sure if you should wipe System as well, but i did anyway
Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs
I had this issue last week I believe and it happened again last night. The only reason I can even use my device is that I'm using xtended TWRP. I was using Resurrection Remix Nougat with the December security patch and decided to see if MSM Xtended could come close to matching the battery life I get from RR7.1. I got through the setup and quickly decided I preferred Havoc, so I flashed Havoc and set it up. I realized I didn't backup my apps so I tried to restore my RR backup on TWRP. Before it booted it came to the screen telling me encryption was unsuccessful and to factory reset to use my device.
Now, in no ROM have I encrypted my device. I didn't try to encrypt anything, no app data, pictures, no zip archive, no encryption of ANYTHING. I have no clue what did it, but each time I was using RR and did a fresh install of a Pie ROM. The only difference between this time and last time is that last time I attempted to use the official version of TWRP that doesn't have the encryption capabilities as Red Wolf or TWRP Xtended.. when I flashed the official TWRP last time I was locked out as if I did unsuccessfully try to encrypt. Last time, after flashing official TWRP, I was able to recover my files by using fastboot to flash TWRP Xtended.
Like last time, I have full access to my files in recovery, and as long as I use a Pie ROM, I can flash at will with no issues. Restoring a backup or attempting to clean flash anything other than a Pie ROM results in encryption unsuccessful.
Has anyone else encountered this? And outside of fastboot format userdata, is there any way to fix it? Any idea of what could be causing this? I mean, I'm about to fix it the only way I know, but I'm wondering for future reference.....
I tried something just now before wiping everything... I've kept it unencrypted for no real reason, so I decided to try something after backing all my stuff up.. I did a clean flash of the latest OOS, didn't use a patched boot image or the encryption disabler and allowed OOS to encrypt my device.. I booted into OOS and completed the setup; all my files and everything was still there, settings->security said I was encrypted. I rebooted to recovery and I still had TWRP xtended, restored my Resurrection remix backup, and booted right up. I'll just keep it encrypted, since it works and I have no real reason NOT to be encrypted..
One of the problems with switching ROMs on this phone is that some ROMs use Full Disk Encryption (FDE) and some use File Based Encryption (FBE). As these are quite different and incompatible with each other, it's important to switch to ROMs only using the same encryption type.
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
One of the problems with switching ROMs on this phone is that some ROMs use Full Disk Encryption (FDE) and some use File Based Encryption (FBE). As these are quite different and incompatible with each other, it's important to switch to ROMs only using the same encryption type.
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Although I've resolved it satisfactorily enough for me, I'm still curious as to what exactly changed. I say that because up until, I think the 20181211 build of havoc I could switch between my restores with no issues. Sometime after that build is when I encountered that encryption issue. Mind you, up until I encrypted my device yesterday, I religiously kept my device unencrypted, avoiding any sort of encryption. I just found it odd that because I haven't attempted any sort of encryption that it would tell me that encryption was unsuccessful on restores and clean flashes of Resurrection remix nougat, yet no problems at all with either havoc or xtended Pie... like I said, it's just more of a curiosity now that it seems to be resolved.
Hi there,
I tried to install a ROM on my Mi9T pro. I use Orange Fox and it asked me when I entered the recovery for the password, that decrypted my Data partition. All well so far.I installed the ROM Havoc and Magisk. After reboot into System, there was a bootloop. I entered the recovery again and the Data(internal storage is encrypted. Which is not too bad, because I know the password, but I do not get asked for the password/pattern. It says:
E: Error making /sdcard/fox, unable to wipe Data, unable to format to remoce encryption.
So I cannot install a new rom as the partion is encrypted and I cannot remove the partition.
“E:Unable to decrypt FBE device”
Does anyone have a recommendation on what to do?
Kind regards
berndbrecht said:
Hi there,
I tried to install a ROM on my Mi9T pro. I use Orange Fox and it asked me when I entered the recovery for the password, that decrypted my Data partition. All well so far.I installed the ROM Havoc and Magisk. After reboot into System, there was a bootloop. I entered the recovery again and the Data(internal storage is encrypted. Which is not too bad, because I know the password, but I do not get asked for the password/pattern. It says:
E: Error making /sdcard/fox, unable to wipe Data, unable to format to remoce encryption.
So I cannot install a new rom as the partion is encrypted and I cannot remove the partition.
“E:Unable to decrypt FBE device”
Does anyone have a recommendation on what to do?
Kind regards
Click to expand...
Click to collapse
When installing over MIUI you need to format data. You should still be able to format data, which should allow you to boot into the ROM after.
If Orange Fox won't let you format data at this point, then the issue is with Orange Fox. In TWRP when this happens, even though the data partition is encrypted and TWRP doesn't ask for the password, TWRP can still format the data partition.
If you can format data in OF, then good. If not try installing TWRP then formatting data. If that fails your best option is to restore to MIUI with a stock fastboot ROM, then start again.
thank you for your comment. as a follow up. do you recommend a certain twrp release? i just don't want to **** up the phone. when ich connect the phone to my laptop, I can see the internal data, but neither can i copy, nor make the names of the files any sense (encrypted i guess). is there now way to decrypt the files from the situation as is? i do not mind, as i back upped all the important stuff, but if possible i would do without format.
btw. i came from lineage os. what i did: i wiped data, system, cache and data, then installed the rom ( included gapps) and magisk. then restarted.
berndbrecht said:
thank you for your comment. as a follow up. do you recommend a certain twrp release? i just don't want to **** up the phone. when ich connect the phone to my laptop, I can see the internal data, but neither can i copy, nor make the names of the files any sense (encrypted i guess). is there now way to decrypt the files from the situation as is? i do not mind, as i back upped all the important stuff, but if possible i would do without format.
btw. i came from lineage os. what i did: i wiped data, system, cache and data, then installed the rom ( included gapps) and magisk. then restarted.
Click to expand...
Click to collapse
Use the latest TWRP from here https://forum.xda-developers.com/k2...cial-twrp-xiaomi-redmi-t3944363/post79823568. Go with the latest unofficial as it is the same as the official version, but with some minor bug fixes added.
Orange Fox is only really worth using when sticking with MIUI. Most of it's extra functions are MIUI specific.
When you get into this situation, unfortunately, there is nothing that can be done to recover or decrypt the data partition, as far as I know.
Normally going from one AOSP ROM to another you should be OK and won't need to format data. But occasionally this problem will happen, I've had it happen when going from LOS to AOSiP. Formatting data in TWRP, when this happens, will then allow you to boot into your new ROM. I haven't yet found out why this sometimes happens.
You will just need to backup your data whenever you flash a ROM, just in case this happens again.
Robbo.5000 said:
Use the latest TWRP from here https://forum.xda-developers.com/k2...cial-twrp-xiaomi-redmi-t3944363/post79823568. Go with the latest unofficial as it is the same as the official version, but with some minor bug fixes added.
Orange Fox is only really worth using when sticking with MIUI. Most of it's extra functions are MIUI specific.
When you get into this situation, unfortunately, there is nothing that can be done to recover or decrypt the data partition, as far as I know.
Normally going from one AOSP ROM to another you should be OK and won't need to format data. But occasionally this problem will happen, I've had it happen when going from LOS to AOSiP. Formatting data in TWRP, when this happens, will then allow you to boot into your new ROM. I haven't yet found out why this sometimes happens.
You will just need to backup your data whenever you flash a ROM, just in case this happens again.
Click to expand...
Click to collapse
Thanks man, many thanks. did flash the twrp and it worked out. having some minor problems with the rom, but in general it worked out fine
much appreciated.