Downgrading from OOS 4.0 - OnePlus 3 Questions & Answers

Hi.
what is the easier way to downgrade from OOS4.0 without any issues. i did think about the Qualcomm unbrick tool but not 100% im on 100% stock again so no TWRP, running EXT4 not f2fs
Thanks

can anyone help?

If you're on ext4 you can just flash (sideload) older OOS over it, no need to do anything else.
Sent from my OnePlus 3 using Tapatalk

would that work tho as OOS4 encripts each time and i cba to screw around with it

Encryption has nothing to do with downgrading (or upgrading), different partitions. ROM is on /system while encryption is on /data.
Worst case scenario is data loss, but the downgrading itself should work without issues.
Sent from my OnePlus 3 using Tapatalk

dont care about data loss as ill be rooting and twrp for MIUI once im back on MM.
stock recovery adb sideload 3.28 full zip i guess?

Related

Upgraded to 6.0.1, and now my 5X is Encrypted again

Hey
I disabled encryption my Nexus 5X once I was on 6.0 using TWRP.
Now after upgrading to 6.0.1 the device is encrypted again.
How can I avoid that in the future? I want to device to stay decrypted when I upgrade.
Thanks
When upgrading, if you flash the stock boot/kernel and start up Android it will encrypt your data again. To avoid this make sure you flash a custom boot/kernel that does not force exception before booting into Android
So installing twrp and elementalx right after upgrading should be OK?
Upgrade
Flash TWRP
Format
Flash systemless SuperSU
Flash ex kernel
That's the order I did it in and my phone is not encrypted
If you are already decrypted, upgrade by flashing system.img (along with vendor, radio, bootloader). Don't flash data.img, so you don't lose your current data. You also won't need to format the data partition if you are already decrypted.
Just make sure you flash a modified boot.img each time you upgrade before booting back into the system (best to make sure the modified boot.img is for that specific build) - or go systemless and flash SuperSU that modifies the boot.img automatically to remove encryption.
Thanks I'll do that next time!
I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk
hamedunix said:
I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..
tacofromhell said:
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..
Click to expand...
Click to collapse
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk
hamedunix said:
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.
peltus said:
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.
Click to expand...
Click to collapse
Been into rooting and stuff like that; however, I don't mind encryption as long as it won't affect my experience on N5X.
Sent from my Nexus 5X using Tapatalk

Returning to 3.2.8

Good Evening.
im considering returning back to MM as OOS4 isnt really living up to what i want. is it as simple as using qualcom tool to go back to earlier software. im still on ext4 not f2fs so reformating isnt an issue
Thanks
RevTheory said:
Good Evening.
im considering returning back to MM as OOS4 isnt really living up to what i want. is it as simple as using qualcom tool to go back to earlier software. im still on ext4 not f2fs so reformating isnt an issue
Thanks
Click to expand...
Click to collapse
What Qualcomm tool?!
Also, flashing back to Marshmallow should be a simple process. I highly recommend you flash FreedomOS instead of the official OxygenOS. Also, flash the latest ElementalX kernel, while you're at it. Personally, I trust XDA devs more than I trust OnePlus, and I make that suggestion every time I get the chance.
The process should go like this :
-flash latest official TWRP recovery
-reboot recovery
-flash 3.2.8 firmware (+ modem)
-flash FreedomOS & kernel

Unable to Mount Data in TWRP

I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs
Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.
Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.
Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor
help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me
I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.

TWRP

I just got my 5t. It's unlocked, stock Oreo latest update. I am encrypted. The only thing I'm not sure of is which TWRP to install. Is one fof them for nougat?
Does it matter that I'm encrypted. I've been a fan of Dirty Unicorns for years and thinking about trying that first. Any help is really appreciated. Thanks
I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
However, since stock is encrypted, perhaps take codeworkx or blu_spark nandroid first.
And going from encrypted to unencrypted needs data reformat + factory reset.
Moreover, going back from unencrypted to encrypted can be tedious. In short, one not only needs to data reformat + factory reset, one needs to pass through stock recovery if I understand well. I find instructions somewhere in the official TWRP thread or elsewhere.
In short: going unencrypted is almost a one way street. But there always is a way back.
Dior DNA said:
I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
Click to expand...
Click to collapse
You're right. DU stopped posting on xda awhile back but think I saw a dumpling build online, however I'm not sure if it's nougat or Oreo...
I don't necessarily need encryption but is that the only issue? So if I want unencrypted, the official version will be fine? Does anyone know if I can decrypt with TWRP? (I'll probably have to format data but that's fine) Thanks
KLit75 said:
You're right. DU stopped posting on xda awhile back but think I saw a dumpling build online, however I'm not sure if it's nougat or Oreo...
I don't necessarily need encryption but is that the only issue? So if I want unencrypted, the official version will be fine? Does anyone know if I can decrypt with TWRP? (I'll probably have to format data but that's fine) Thanks
Click to expand...
Click to collapse
DU no doubt is 8.1 and YES you need to format data.
The other way back to encrypted seems the harder part.
Dior DNA said:
I don't think there is a dedicated 5T Dirty Unicorns thread on XDA. But I read it is an unencrypted ROM. Correct me someone if I am wrong. There is a Dirty Unicorns Google+ thread. People who have encrypted ROMs seem to use codeworkx or blu_spark TWRP. But for unencrypted ROM I hear official TWRP is fine.
However, since stock is encrypted, perhaps take codeworkx or blu_spark nandroid first.
And going from encrypted to unencrypted needs data reformat + factory reset.
Moreover, going back from unencrypted to encrypted can be tedious. In short, one not only needs to data reformat + factory reset, one needs to pass through stock recovery if I understand well. I find instructions somewhere in the official TWRP thread or elsewhere.
In short: going unencrypted is almost a one way street. But there always is a way back.
Click to expand...
Click to collapse
I now have codeworkx twrp, rooted with magisk. I gotta say I'm pretty impressed with stock but I KNOW I'm gonna want to flash a custom ROM soon and that's not a fast process when you're encrypted.
You said make a nandroid...have you ever restored just data from stock to a custom ROM? I may have but it's been awhile. I'm thinking I might have issues.
If I want to flash ROMs I'm going to need to format (better sooner than later) so from what I remember, I should:
1. Boot TWRP
2. Format data
3. Full wipe?
4. Adb push ROM, gapps, magisk
5. Flash all of them
I'm just hoping you or someone else can verify. I've got a lot of stuff to transfer over from my old phone but it makes no sense to do that now if I'm going to have to format. Thanks
UPDATE_
I got it. Running Dirty Unicorns now. It was a bit of an adventure. MTP would not work. Had to adb push the zip files. And then it booted back into TWRP asking to allow modifications. I don't remember any of my devices doing that but I swiped yes and the rom booted.
One thing...there was an immediate notification telling me to update TWRP. I'm using the latest codeworks one so not sure if I should update or even if an update will work since I'm not on an official build. Have you encountered anything like this?
KLit75 said:
I now have codeworkx twrp, rooted with magisk. I gotta say I'm pretty impressed with stock but I KNOW I'm gonna want to flash a custom ROM soon and that's not a fast process when you're encrypted.
You said make a nandroid...have you ever restored just data from stock to a custom ROM? I may have but it's been awhile. I'm thinking I might have issues.
If I want to flash ROMs I'm going to need to format (better sooner than later) so from what I remember, I should:
1. Boot TWRP
2. Format data
3. Full wipe?
4. Adb push ROM, gapps, magisk
5. Flash all of them
I'm just hoping you or someone else can verify. I've got a lot of stuff to transfer over from my old phone but it makes no sense to do that now if I'm going to have to format. Thanks
UPDATE_
I got it. Running Dirty Unicorns now. It was a bit of an adventure. MTP would not work. Had to adb push the zip files. And then it booted back into TWRP asking to allow modifications. I don't remember any of my devices doing that but I swiped yes and the rom booted.
One thing...there was an immediate notification telling me to update TWRP. I'm using the latest codeworks one so not sure if I should update or even if an update will work since I'm not on an official build. Have you encountered anything like this?
Click to expand...
Click to collapse
@KLit75
Stock is indeed good ROM. Many people use Beta which is equally good.
Some Custom ROMs do some do not support encryption. You may have to
read a bit in the ROM threads. Some TWRP are better for encryption as
well. Official TWRP perhaps catched up. You may may have to read a bit
in the TWRP threads.
When I went OOS 5.0.4 -> Custom (GZOSP) I had to format data and
become unencrypted.
I then reinstalled phone from scratch but had Titanium backup (for
accounts etc...) and also /data/media/0 backup (for some media).
So no: I never fully restored data from stock to a custom ROM. I did
restore some app data from Titanium backup though.
I have not restored encrypted TWRP stock backup either. I probably
never will, but I had asked around and read about it for all
certainty.
I believe one needs a special step which is to clean via stock
recovery and flash stock. Then one can perhaps restore whatever
encrypted TWRP backup. I hear different versions of ROMS may have
different encryption mechanisms. I am not authoritative on Android
encryption, read other threads.
You will need to search and ask if you want to go back to encrypted.
Perhaps it is easier than I tell here.
Note that I had backups (Titanium media TWRP) copied over to computer
for all certainty. I sometimes also work with OTG stick for copying in
both directions.
I think almost no experience is same for 2 people. That's why we all
tell slightly different stories. Trying to understand and master the
procedures is the challenge, and have many backups, and a way back.
No TWRP ever asked me to upgrade. I allow TWRP to make modifications.
My computer is Linux and I do not use MTP.
You can stay on codeworkx TWRP. Myself I did so but, eventually, since
I am unencrypted, I now am on official twrp-3.2.1-2-dumpling.
Recall also it is advised to always turn off lock screen Security
before taking a TWRP backup.
Good luck and enjoy your 5T.

how to rescue my data?

I'm using Official Pixel Experience 11.0 and I noticed there got a beta version for Pixel Experience 12, Considered it's "beta" instead of "alpha" or "prebuild", I think it wouldn't be that risky, So I just flashed it via the Pixel Experience Recovery's sideload. When I try to check how wonderful my new system was, Dang, it directly entered the Recovery and all my data have not been backup! I have tried to sideload to the old PE11 but not work. Then I installed twrp and orange fox tried to backup my data but seems data and sdcard partitions could not be unencrypt. Any have ideas about how to rescue my data? Or is there any way I could backup all the encrypted partition to a img so I could deal with this encrypt later instead of doing nothing? These data is important to me.
No. If tou carefully read instructions, you can not go from A11 to a12 without formatting data, then install now already we have beta.
tze_vitamin said:
No. If tou carefully read instructions, you can not go from A11 to a12 without formatting data, then install now already we have beta.
Click to expand...
Click to collapse
So it's all kinds of rom does not support ota update from a11 to a12 or just I used a wrong method? I wondered if I could take my data out from this phone without rescue the system? I could reinstall the system but I really export my data.
You will not find OTA custom ROM , a11 to A12, you can maybe find A12 to A12. But if you wait for stock ROM tou will get it OTA . custom ROM is different.. especially if someone is not encrypted and formatting is important to be able to flash and boot system
tze_vitamin said:
You will not find OTA custom ROM , a11 to A12, you can maybe find A12 to A12. But if you wait for stock ROM tou will get it OTA . custom ROM is different.. especially if someone is not encrypted and formatting is important to be able to flash and boot system
Click to expand...
Click to collapse
Thank you very much for you info, but I wondered if it is possible to export my data out of the phone?
I found on youtube, Put your phone into Fastboot and in ADB type Backup all
after installing system , again in ADB type restore.
try research about this commands on google to have it for next time if something similir happend

Categories

Resources