TWRP 3.1.0 - wipes userdata and more - OnePlus 3T Questions & Answers

I install latest TWRP 3.1.0 version today.
All the user data, some apps (Waze, Gmail, Gmaps...), SMS were wiped.
I have RR-N-v5.8.2-20170218-oneplus3t-Official currently installed.
I reinstall some apps back.
After system reboot all seemed fine.... But after boot to recovery (TWRP 3.1) and than boot into system all was gone again.
It looks like every boot to recovery wipes user data and some apps...

Flash 3.0.4-1 again

Same problem here with 3.1.0.0.

I flashed 3.1.0.0 img with 3.0.4-1 and do not have the issues OP is describing.
Edit: stock Open Beta 3 rooted.

sossio18 said:
Flash 3.0.4-1 again
Click to expand...
Click to collapse
I did... and restore system from backup BUT some userdata is gone forever...

Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.

Anova's Origin said:
Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.
Click to expand...
Click to collapse
Happened to me on OOS. Went back to 3.0.4-1
Sent from my OnePlus 3T using XDA Labs

It was updated to 3.1.0-1 try that

I suppose this of because of the official TWRP 3.1.0-0 is not using the backported F2FS driver. I'm using EXT4 filesystem on data partition so therefore I'm not experiencing any data loss.

Was on RR 09.03 with OB3 firmware, it completely destroyed my phone. Bootloops, impossible to go back to recovery, when in recovery, impossible to see files to flash them, even going back to 3.0.4.1 did not solve everything, reinstalled Freedom OS but had screen total freezes.... Had to go through the total disaster recovery utility, and I am still re-installing everything...
TWRP 3.1.0.0 ate 4 hours of my flash-addicted life... FML !!!
**STAY AWAY FOR NOW**

Blu_spark 3.1.0 version is not affected by this, only the official.

Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!

Kjaups said:
Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!
Click to expand...
Click to collapse
Can confirm. TWRP 3.1.0-1 works fine. (rooted OOS 4.0.2)

I had at least two serious issues with official TWRP 3.1.0-1 and LineageOS:
1.) After a first flash attempt via fastboot I was no longer able to unlock my phone with my PIN under LineageOS.
2.) When booting into TWRP I got a black screen - unable to do any useful.
3.) After I could no longer unlock my phone under LineageOS I reinstalled LineageOS from TWRP 3.1.0-1. All looked fine until I rebooted from TWRP into LineageOS: TWRP obviously wiped my device and I was offered
the setup wizzard of LineageOS. All my setting were gone.
I had issue 3.) already with TWRP 3.0.3-1. I immediately reflashed TWRP 3.0.4-1 - the currently only working TWRP version.
I would like to add that I had removed any encryption on the phone before I started at 1.). My device is still unencrypted. I once removed stock encryption because I heard about problems with TWRP and encryption.

Related

OP3T Stuck in TWRP after flashing LineageOS

Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.

[Solved] Official Oxygen OS 5.0 boot loop problem for rooted users

Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.

OnePlus 3T Boot Loop, TWRP Available, Bricked?

I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
weaponG said:
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
weaponG said:
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
Click to expand...
Click to collapse
Oh wow. I had to apply the Firmware Update, and now I am running Sultan's Lineage. This is truly exciting. The animated splash/intro screen is still occurring on the phone. This should be great. Thanks so much for your kind assistance.

Flash oxygen os 5.0.5 on OP3T with magisk using TWRP ??

Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??
Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.
I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!

Help getting from LineageOS 14.1 to OxagenOS 5.08 (Something wrong with flash mem?)

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

Categories

Resources