Database Users

Can't get back to Stock ROM (what am I doing wrong?)

History of what I did:
I first installed the first small OTA Update to 4.5.1 then unlocked the Bootloader and flashed TWRP v46 from xdvs23. And made a full TWRP Backup and flashed Magisk afterwards.
Everything worked fine until I debloated the System and wanted to make the OTA Update to 4.5.2 (1,5 GB), which didn't work. After I flashed it, the phone didnt boot anymore. So I restored the TWRP Backup, which doesn't work either.
Current status:
TWRP v58 is flashed and works. I can flash ExcperienceOS from Jamal, which works fine, too. But flashing the OTA file doesn't work and restoring my backup wont work either -_-
I would really appreciate help to get back to an OTA updatable version of OxygenOS!

If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.

djsubterrain said:
If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.
Click to expand...
Click to collapse
I did that several times. It doesn't work sadly... I get into a bootloop

You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway

djsubterrain said:
You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway
Click to expand...
Click to collapse
I might have, I will try that, thanks

Or just wipe everything, flash stock recovery, and flash Full OxygenOS zip.
https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2

I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...

How about trying to wipe everything from wipe menu except internal storage and then flash the oos zip followed by lazy flasher zip from here - bit.ly/lazyflasher
If this doesn't work then try changing to a different version of TWRP!

Casual_Max said:
I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...
Click to expand...
Click to collapse
You didn't do these steps wrong by any chance?
Steps To Disable Forced Encryption i.e, Decrypt Data
1. At first time when you open twrp, it will ask you to allow system modification.
2. Allow it and then flash the no-verity-opt-encrypt.zip file .
3. Then Go to Wipe-->Format Data.
4. Type Yes to confirm wiping of Internal Storage.
5. Now you have decrypted the data sucessfully.
Note: Dont try to restore the nanodroid backup which you have taken before. It may end in bootloop.
Click to expand...
Click to collapse
From here:
https://forum.xda-developers.com/on...der-intall-t3626122/post72777899#post72777899

ok, there I see what caused my first bootloop. Thanks
But why doesn't flashing the Stock ROM .ZIP work on an wiped (fastboot format userdata) phone? What else do I have to do?
EDIT:
*** solved ***
I failed hard. Luckily the OnePlus Support is excellent and was able to fix my issue with a remote session using their official tools. The Phone and I are both happy again.
Thanks for all the help, though. I learned quite a lot while dealing with this issue. It's a very kind and nice community here

Axon 7 randomly stopped booting

Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?

Chrono7x said:
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Click to expand...
Click to collapse
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash

Choose an username... said:
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Click to expand...
Click to collapse
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.

Chrono7x said:
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Click to expand...
Click to collapse
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first

Choose an username... said:
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Click to expand...
Click to collapse
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?

Chrono7x said:
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Click to expand...
Click to collapse
What? No... That's for normal phones. How did you manage to install LOS without knowing that you need the univ. bootloader and modem?
So, you can't access the internal storage via the file manager on TWRP i'm guessing.
Wipe - Format data, after that flash the Universal bootloader, modem, LOS, Magisk, GApps. Magisk takes care of dm-verity and disables encryption. Don't try to uninstall it though or your internal storage will get encrypted as soon as you do. But if you want to change ROMs you can just fpash it before booting and it won't ger encrypted.

Need a little help understanding A/B partitions

I have a few questions I'm new to the a/b partitions thing I've read the page on a/b partitions. But I'm still in the mud.
1 I'm on Verizon bootloader unlocked twrp 3.2.3-23 and magisk installed I have 9.0.11 installed twrp and magisk in slot a/b
now is it necessary to backup stock rom? If I install lets say crDroid in slot A install twrp installer I know twrp goes into both slots reboot back to recovery making sure I'm still in A install gapps and magisk reboot back to recovery making sure again I'm still in A slot then reboot to crDriod that should work yes?
2 Now If I wanted to go back to my stock rom witch is in B slot can I not reboot back to twrp and switch to slot B and go to stock?
Thanks guys this A/B partition is still clear as mudd

Making a back up is always recommend, but it's up to the user to decide if the want to or not. The down side is loosing all your data, so there is that.
The short answer to your 2nd question is no you can not dual boot ROMs on this device. I posed the same question in a different thread and you can read the explanation from Dark Nightmare here.
https://forum.xda-developers.com/showpost.php?p=78375631&postcount=988
Sent from my ONEPLUS A6013 using Tapatalk

foamerman said:
I have a few questions I'm new to the a/b partitions thing I've read the page on a/b partitions. But I'm still in the mud.
1 I'm on Verizon bootloader unlocked twrp 3.2.3-23 and magisk installed I have 9.0.11 installed twrp and magisk in slot a/b
now is it necessary to backup stock rom? If I install lets say crDroid in slot A install twrp installer I know twrp goes into both slots reboot back to recovery making sure I'm still in A install gapps and magisk reboot back to recovery making sure again I'm still in A slot then reboot to crDriod that should work yes?
Click to expand...
Click to collapse
I'm new to A/B as well but have been flashing quite a bit. Maybe someone can correct me if I'm wrong. From what I've observed, ROMs are designed to flash to the slot you're not using and, on reboot, switch slots. TWRP zip installer is designed to install to both slots. Magisk and Gapps, however, install to the current slot. This means you should flash the ROM (which flashes to the non-active system and boot partitions and possibly others), flash the TWRP installer (which installs to both boot partitions, including the one that was just flashed). Then reboot back into recovery (which will be the other slot that the ROM was installed to), and then install all the other zips needed (i.e., Gapps, Magisk, etc...).
Switching A/B partitions in the TWRP reboot menu also triggers the partition switch after reboot, if needed. It doesn't seem to immediately switch before a reboot however, even though it gives that impression.
foamerman said:
2 Now If I wanted to go back to my stock rom witch is in B slot can I not reboot back to twrp and switch to slot B and go to stock?
Click to expand...
Click to collapse
The data partition, which contains user apps and system and user app data, is not slotted. Moving back and forth between slots that share a common ROM type and are close in version might not pose a problem. But A/B slotting wasn't designed for switching Roms back and forth. It was designed to try to ensure that there is always a valid bootable ROM without regard to use data (i.e., potentially, after a factory-reset). Don't expect to boot up an AOSP modded ROM using the data and apps from an OygenOS ROM. Do a backup of all partitions to be safe (with the exception of system and vendor since system_image and vendor_image give a bit-for-bit copy, instead of file-for-file copy). Copy the TWRP directory to a computer afterward, if possible. Make sure to wipe data if flashing a ROM of a different type, not just a different version (after flashing everything but before initial system boot).

phillymade said:
Making a back up is always recommend, but it's up to the user to decide if the want to or not. The down side is loosing all your data, so there is that.
The short answer to your 2nd question is no you can not dual boot ROMs on this device. I posed the same question in a different thread and you can read the explanation from Dark Nightmare here.
https://forum.xda-developers.com/showpost.php?p=78375631&postcount=988
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Nsane457 said:
I'm new to A/B as well but have been flashing quite a bit. Maybe someone can correct me if I'm wrong. From what I've observed, ROMs are designed to flash to the slot you're not using and, on reboot, switch slots. TWRP zip installer is designed to install to both slots. Magisk and Gapps, however, install to the current slot. This means you should flash the ROM (which flashes to the non-active system and boot partitions and possibly others), flash the TWRP installer (which installs to both boot partitions, including the one that was just flashed). Then reboot back into recovery (which will be the other slot that the ROM was installed to), and then install all the other zips needed (i.e., Gapps, Magisk, etc...).
Switching A/B partitions in the TWRP reboot menu also triggers the partition switch after reboot, if needed. It doesn't seem to immediately switch before a reboot however, even though it gives that impression.
The data partition, which contains user apps and system and user app data, is not slotted. Moving back and forth between slots that share a common ROM type and are close in version might not pose a problem. But A/B slotting wasn't designed for switching Roms back and forth. It was designed to try to ensure that there is always a valid bootable ROM without regard to use data (i.e., potentially, after a factory-reset). Don't expect to boot up an AOSP modded ROM using the data and apps from an OygenOS ROM. Do a backup of all partitions to be safe (with the exception of system and vendor since system_image and vendor_image give a bit-for-bit copy, instead of file-for-file copy). Copy the TWRP directory to a computer afterward, if possible. Make sure to wipe data if flashing a ROM of a different type, not just a different version (after flashing everything but before initial system boot).
Click to expand...
Click to collapse
OK I understand what you both are saying my understanding is that data is still there in both slots yes? so If I want to go back to my 9.0.11 stock rom I should be able to just reboot to twrp and select slot B and go back to to stock yes? guys I'm sorry this is my first A/B partition phone I'm just trying to figure it out

foamerman said:
OK I understand what you both are saying my understanding is that data is still there in both slots yes?
Click to expand...
Click to collapse
As long as it isn't wiped, yes.
foamerman said:
so If I want to go back to my 9.0.11 stock rom I should be able to just reboot to twrp and select slot B and go back to to stock yes? guys I'm sorry this is my first A/B partition phone I'm just trying to figure it out
Click to expand...
Click to collapse
No. Except for the possible exception that both slots contain different versions of the same ROM, the data will work with one ROM but not the other.
When flashing a ROM in TWRP, just mke sure to make a nandroid backup first and follow the installation directions. If you have to switch back, you will need to flash the nandroid backup.
It is a pain and there are pitfalls. This phone is relatively new and this is the cost of flashing a custom ROM/bootloader.

No. Except for the possible exception that both slots contain different versions of the same ROM, the data will work with one ROM but not the other.
When flashing a ROM in TWRP, just mke sure to make a nandroid backup first and follow the installation directions. If you have to switch back, you will need to flash the nandroid backup.
It is a pain and there are pitfalls. This phone is relatively new and this is the cost of flashing a custom ROM/bootloader.[/QUOTE]
OK one more I think lol If I have 9.0.11 on my internal storage can I not go into slot A and wipe it and install it back on there and be OK?

foamerman said:
OK one more I think lol If I have 9.0.11 on my internal storage can I not go into slot A and wipe it and install it back on there and be OK?
Click to expand...
Click to collapse
Internal storage is an encrypted folder in the data partition that is wiped separately from data. As long as you don't wipe internal storage for any reason it should be ok, in theory. But it's not in practice.
Most of the problem with this phone is maintaining encryption back and forth between ROMs. Honestly, if you can't afford to lose data, don't try to flash ROM's yet. I have had very little luck flashing back and forth and, after reflashing data, being able to avoid a bootloop. TWRP has only supported encryption on this phone for a month or so and IMHO it's not ready for prime time. I have relied on Titanium Backup and moved it's backup folder back and forth between my phone and computer.

Nsane457 said:
Internal storage is an encrypted folder in the data partition that is wiped separately from data. As long as you don't wipe internal storage for any reason it should be ok, in theory. But it's not in practice.
Most of the problem with this phone is maintaining encryption back and forth between ROMs. Honestly, if you can't afford to lose data, don't try to flash ROM's yet. I have had very little luck flashing back and forth and, after reflashing data, being able to avoid a bootloop. TWRP has only supported encryption on this phone for a month or so and IMHO it's not ready for prime time. I have relied on Titanium Backup and moved it's backup folder back and forth between my phone and computer.
Click to expand...
Click to collapse
Well the mud is starting to clear up a little. Yea I've been a little leery about trying to install roms yet. I have read all the post in the Recovery thread mauronofrio is getting a 6t soon so maybe he can figure it out. But again Thank you.

TWRP can't stay, even flashed by installer

Hi guys,
I'm not newbie with flashing but this one I don't understand.
Probably I've done some mistakes with flashing/install/uninstall of roms/magisk/twrp.
Now I'm stuck with TWRP and can't boot into system because of something.
Every time I run TWRP and try to install all my files are encrypted, no matter I install TWRP by .img or .zip. Only working TWRP with decryption is temporary one, by "fastboot boot twrp-3.3.1-6-fajita.img" command. But when I flash it by regular .img file by this tut (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), after reboot it's back like 3.3.1-6-fajita version, BUT without decryption skills.
I thing I done some mistakes with uninstalling magisk ect. but I think it doesn't matter.
I tried to uninstall magisk by Magisk-uninstaller-20190204.zip on both slots, I tried install all again in regular way (install temp TWRP through fastboot command, install TWRP through this temp TWRP, install full newest OTA .zip, install TWRP again (I know I shouldn't but I tried both combinations - .zip and .img) and install Magisk and at least system reboot. But when I rebooted between OTA and Magisk (like guide tells) TWRP can't decrypt files. No matter what I've done nothing helped.
What can I do that I have not done yet? Of course, all is about I don't want format my data and re-install all from the scratch...
So... tell me, is possible to make TWRP great again?

Is everything only showing as encrypted when you try to restore a backup? I've been booting the img via fastboot then flashing the zip as it seems you have and it's been working fine as far as it staying installed and not showing all my files as scrambled, I also made the mistake of using Magisk uninstaller at one point, that didn't end well. Seems these A/B phones are temperamental as hell. I read somewhere else that doing backups to USB storage my be more reliable for a backup restoration, not sure if that would effect the encryption issues or not but I may have some time to test that tonight.

I've done that too - not helped. I restored my full nandroid backup by fastboot temp recovery (as I wrote, only this one can decrypt my files) but I've got "You device is corrupt"... and of course TWRP can't decrypt my files.

How to install TWRP and custom rom?

Please give me instruction!
What I have done to there:
1. Unlocked bootloader
2. Boot TWRP .img file
3. Install recovery ram disk from the same .img file
4. Reboot to TWRP
5. Install TWRP installer .zip file
6. Reboot to TWRP
7. Wipe system, data, dalvik partitions
8. Flash Havoc and TWRP installer
9. Reboot to TWRP
10. PARTITIONS ENCRYPTED/UNABLE TO FLASH GAPPS
I'm using TWRP UNOFFICIAL BY MAURONOFRIO.
What to do now?
I'm tired! Give me instruction!

You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.

Maybe this thread will help.

dj_ooms said:
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Click to expand...
Click to collapse
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION

ALYSKY said:
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
Click to expand...
Click to collapse
Its the third post (link) in the thread I linked to....