how can i downgrade from oos 9.04 to 9.03?
Flash full OOS zip.
Kollachi said:
Flash full OOS zip.
Click to expand...
Click to collapse
Where can that be found. Cant find it on oneplus website
WillowTree said:
Where can that be found. Cant find it on oneplus website
Click to expand...
Click to collapse
Try a search in this thread, maybe somebody posted it :
https://forum.xda-developers.com/on...-6-mirrors-official-oxygen-os-t3792244/page55
Totone56 said:
Try a search in this thread, maybe somebody posted it :
https://forum.xda-developers.com/on...-6-mirrors-official-oxygen-os-t3792244/page55
Click to expand...
Click to collapse
Found it, thank you.
Will something break if i downgrade?
WillowTree said:
Found it, thank you.
Will something break if i downgrade?
Click to expand...
Click to collapse
If you use the stock "Local Upgrade" option, it won't let you.
If you use TWRP or blu_spark TWRP, just remember to wipe Data.
There is a chance the security patch level is lower on the old bulid. If it's the case, you'll have to Format Data (Not wipe, really format) to remove all encryption, or it won't boot :/
This will erase all of your storage, including folders, downloads, everything.
Totone56 said:
If you use the stock "Local Upgrade" option, it won't let you.
If you use TWRP or blu_spark TWRP, just remember to wipe Data.
There is a chance the security patch level is lower on the old bulid. If it's the case, you'll have to Format Data (Not wipe, really format) to remove all encryption, or it won't boot :/
This will erase all of your storage, including folders, downloads, everything.
Click to expand...
Click to collapse
Sorry for being ignorant but how do i "format data"?
So I have to boot into TWRP > flash 9.0.3 OOS > wipe data > reboot to system and that it?
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
[/COLOR]
WillowTree said:
Sorry for being ignorant but how do i "format data"?
So I have to boot into TWRP > flash 9.0.3 OOS > wipe data > reboot to system and that it?
Click to expand...
Click to collapse
One advice : Be near a computer with the 9.0.3 and TWRP zips near you.
You should flash 9.0.3, then TWRP (or it will erase it).
This will install it on one slot.
Reboot recovery, and do this a second time, 9.0.3 and TWRP, to fill the other system slot
Reboot recovery a second time to go back to the first slot, and to format data, go into the wipe menu, and you'll see (if i remember correctly) two buttons, Format Data, and Advanced Wipe. It's above the "Factory Reset" slider.
You'll have to touch Format Data, and confirm by typing "yes", there will be a warning.
- > If when you reboot the recovery, it doesn't ask for your password, it means it's busted by the security patch, and you have to format haha !
This is why it's good to have a PC nearby, to copy the zips again if you have to format during the process.
Totone56 said:
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
[/COLOR]
One advice : Be near a computer with the 9.0.3 and TWRP zips near you.
You should flash 9.0.3, then TWRP (or it will erase it).
This will install it on one slot.
Reboot recovery, and do this a second time, 9.0.3 and TWRP, to fill the other system slot
Reboot recovery a second time to go back to the first slot, and to format data, go into the wipe menu, and you'll see (if i remember correctly) two buttons, Format Data, and Advanced Wipe. It's above the "Factory Reset" slider.
You'll have to touch Format Data, and confirm by typing "yes", there will be a warning.
- > If when you reboot the recovery, it doesn't ask for your password, it means it's busted by the security patch, and you have to format haha !
This is why it's good to have a PC nearby, to copy the zips again if you have to format during the process.
Click to expand...
Click to collapse
I greatly appreciate your help.
Just to clarify the last part, what if i don't have a password in the first place. Will it still "not ask for it" if. The security patch is messed up?
Edit : what if i want to re-flash the current stock OOS (9.0.4) do i only flash it in twrp and reboot. Nothing else?
WillowTree said:
I greatly appreciate your help.
Just to clarify the last part, what if i don't have a password in the first place. Will it still "not ask for it" if. Tje security patch is messed up?
Click to expand...
Click to collapse
Mmmmh. When you normally boot into TWRP, does it ask anything to decrypt the data ?
Mine asks for my password, if I don't enter it, all folders are unreadable and empty.
I never used it without a password.
Maybe it will enter TRWP without asking for anything, but all the folders and files will be encrypted and unusable. This is the case where you have to format everything.
If you want to go from 9.0.3 to 9.0.4 later on, you just have to flash it yes.
It's advised to still flash it on both slots like described above, just to be sure though, but you will not have to wipe anything
Totone56 said:
Mmmmh. When you normally boot into TWRP, does it ask anything to decrypt the data ?
Mine asks for my password, if I don't enter it, all folders are unreadable and empty.
I never used it without a password.
Maybe it will enter TRWP without asking for anything, but all the folders and files will be encrypted and unusable. This is the case where you have to format everything.
If you want to go from 9.0.3 to 9.0.4 later on, you just have to flash it yes.
It's advised to still flash it on both slots like described above, just to be sure though, but you will not have to wipe anything
Click to expand...
Click to collapse
Yes, you are correct. It does ask for a password if you have that enabled. But i always disabled it, just in case.
I think i got it now. When i see that the files are unattainable, i will format. And reboot after that.
What i meant was that. I want to re-flash the same stock version that i now havd (9.0.4) just to see if that solves my (connect-disconnect wifi/data issue). If not then i will proceed to downgrade to 9.0.3
WillowTree said:
Yes, you are correct. It does ask for a password if you have that enabled. But i always disabled it, just in case.
I think i got it now. When i see that the files are unattainable, i will format. And reboot after that.
What i meant was that. I want to re-flash the same stock version that i now havd (9.0.4) just to see if that solves my (connect-disconnect wifi/data issue). If not then i will proceed to downgrade to 9.0.3
Click to expand...
Click to collapse
You should do a simple factory reset at the same time if you re-flash your current version. I had bad WiFi issues too on this one after a dirty flash from 9.0.3. With a clean 9.0.4 flash, it was fine.
To be sure, you could re-flash 9.0.4 on both slots (It has been said to resolve issues sometimes), and do a simple factory reset (Without formatting, a classic "Clean Flash"). The ROM itself is fine, so it would eliminate issues you could have with your particular setup
Totone56 said:
You should do a simple factory reset at the same time if you re-flash your current version. I had bad WiFi issues too on this one after a dirty flash from 9.0.3. With a clean 9.0.4 flash, it was fine.
To be sure, you could re-flash 9.0.4 on both slots (It has been said to resolve issues sometimes), and do a simple factory reset (Without formatting, a classic "Clean Flash"). The ROM itself is fine, so it would eliminate issues you could have with your particular setup
Click to expand...
Click to collapse
That's exactly what i thought. A factory reset might solve the problem so i went and googled it and people were having issues when doing a simple factory reset in twrp > https://forum.xda-developers.com/oneplus-6/how-to/factory-reset-os-patched-boot-img-t3795998/amp/
But yet again i were to re-flash stock on both slots it would bring back "stock boot.img" i suppose, if I'm not wrong.
---------- Post added at 12:40 PM ---------- Previous post was at 12:04 PM ----------
It all went fine. Wifi issue seems to be fixed, need further look in to.
My guess was right, after flashing stock OOS second time on the other slot it must've stocked the boot.img so the factory reset went fine and booted into system as it should.
Thanks again for your help @Totone56
WillowTree said:
That's exactly what i thought. A factory reset might solve the problem so i went and googled it and people were having issues when doing a simple factory reset in twrp > https://forum.xda-developers.com/oneplus-6/how-to/factory-reset-os-patched-boot-img-t3795998/amp/
But yet again i were to re-flash stock on both slots it would bring back "stock boot.img" i suppose, if I'm not wrong.
---------- Post added at 12:40 PM ---------- Previous post was at 12:04 PM ----------
It all went fine. Wifi issue seems to be fixed, need further look in to.
My guess was right, after flashing stock OOS second time on the other slot it must've stocked the boot.img so the factory reset went fine and booted into system as it should.
Thanks again for your help @Totone56
Click to expand...
Click to collapse
Nice, enjoy !
And yes, flashing the ROM also switches slots. So if you were booting slot _a before, now you're on slot _b. So the kernel is the stock one, that went with the zip you just flashed
Related
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
easiest way is to factory reset from recovery, if you can afford it.
First off it is stuck on boot animation, wipe data (factory reset) from recovery and you're good to go hopefully
Transmitted via BACON
ipsmaxes said:
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
Click to expand...
Click to collapse
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Hi it my case too. And I did disable some anoying Google apps.
mathsjob said:
Hi it my case too. And I did disable some anoying Google apps.
Click to expand...
Click to collapse
In my experience, it's Google App the only one causing problem, I removed Google Play Books, Play Videos, Play Music, Google+, etc. and not a problem
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
mathsjob said:
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
Click to expand...
Click to collapse
I fixed the problem dirty flashing again the ROM but if you already wiped data and flashed again the ROM, you may have another different problem causing the bootloop.
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
mathsjob said:
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
Click to expand...
Click to collapse
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
brath23 said:
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
Click to expand...
Click to collapse
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
mathsjob said:
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
Click to expand...
Click to collapse
If you don't have TWRP recovery, you could try to fastboot this ROM: http://builds.cyngn.com/factory/bacon/cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip
There are plenty of guides to do this, even some scripts to make the process kind of automatic.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
More guides on XDA:
http://forum.xda-developers.com/showpost.php?p=63294096&postcount=4
And some script to make the process easier.
https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/
Make sure you choose your Oneplus ONE version correctly (16GB/64GB)
Thanks a lots for your quick answers, I will try using your ADB process.
Hey so yeah I already factory reset from recovery,
I didn't wipe my data yet because I still want to recover some files from the phone.
and yeah I did have almost every google app disabled (not removed).
after a factory reset these are normally activated again though? so idk what's up with that.
also does somebody know a way to retreive all files from the phone, through adb maybe? since I can't acces the file system on my pc rn
I'm gonna try to fastboot that rom you linked later (after I attempt to recover my files)
brath23 said:
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Click to expand...
Click to collapse
I did it yesterday
A disaster....
tommy92tc said:
I did it yesterday
A disaster....
Click to expand...
Click to collapse
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
brath23 said:
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
Click to expand...
Click to collapse
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
tommy92tc said:
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
Click to expand...
Click to collapse
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
brath23 said:
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
Click to expand...
Click to collapse
Genius!!!!
Unfortunately it's too late, I already reinstalled all the apps and everything, now I have a clean system so I'll stay with that.
However it's a good way to restore, I'll remind it if anyone else will need it
Hello Guys,
We have Only 1 Twrp Recovery. And u guys Might be Pissed that it has Encryption. But the Encryption Problem Is Not in the Twrp, it is due to ROM.
Guide to Remove Encryption
1. Boot to Twrp Recovery
2. Do a Factory Reset, Internal Storage Wipe
3. Reboot to Recovery Again
4. Hurray We have Removed the Encryption
F.A.Q'S
1. This Method Removes All Ur Files Which are there in Your Internal Storage.
2. I wont be responsible For the Bricks u Do For Your Device
Do Give a Thanks If U Like My Work
Reserved
ChalapathiRevanth said:
Reserved
Click to expand...
Click to collapse
pls can you tell me what this settings look like after decryption
Nothing Related to Settings
SkaboXD said:
pls can you tell me what this settings look like after decryption
Click to expand...
Click to collapse
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security
ChalapathiRevanth said:
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security
Click to expand...
Click to collapse
no,no,no i know that, i just want to know did encryption setting changed to decrypted.
What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk
Did not Get you!
SkaboXD said:
no,no,no i know that, i just want to know did encryption setting changed to decrypted.
Click to expand...
Click to collapse
PM Me
Nothing Related To Performance!
Nikola Jovanovic said:
What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk
Click to expand...
Click to collapse
This Is nothing related to performance, it just removes encryption in Twrp Recovery. So we can see the Internal Storage in Twrp Recovery.
If u Want to Get Performance, Remove the ****ty Apps, which are present with System App Remover!
I can confirm that this method works, i didn't know that it was that simple.
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
yeah, that is only recovery that works, you can brick device if you wipe /system. You should wipe /system only when you are doing full wipe (flashing new ROM). You can wipe /data but it will remove existing non-system apps. I never did twrp backup so you can try.
Does the twrp encryption removal survive ota updates and oreo beta update?
Device Specific Comments
MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
However Only Device Specific Comments, SkaboXD
I hope This Guy Solved Your Problem
redweaver said:
Does the twrp encryption removal survive ota updates and oreo beta update?
Click to expand...
Click to collapse
I don't think so because every .nb0 file that i flashed have encryption enabled. But after flashing new rom, you can immediately factory reset when you boot to rom to prevent losing data.
---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------
@MoHuToP
ok, i tried full twrp backup, but it stops on system image backup, it stoped around 60%. Backup have 11.5 GB (really huge isn't it).
DELETED
Ok, this method worked on Nougat with SuperSU because SuperSU patched fstab and file contexts successfully. It doesn't work on Oreo because Oreo now have plat_file_contexts and non_plat_file contexts. SuperSU needs to be updated to patch these files succesufully or we need to manually patch it so we can remove encryption.
Just to update this guide: This works only on Nougat. You need to have installed twrp and unlocked bootloader. Magisk doesn't work with this method because it doesn't patch fstab and file contents file so you need to uninstall it by going to Magisk app and clicking uninstall. After that go to TWRP, flash unSu > stock boot.img. You can flash Magisk after that with removed encryption.
Steps:
1. Flash SuperSU 2.79 stable with TWRP
2. Reboot your phone to system.
3. Reboot to TWRP again.
4. Choose Wipe > Swipe to Factory reset
5. Choose Wipe > Advanced > Internal Storage
Now you wiped Data, Cache, Dalvik cache and Internal Storage.
Your phone will have removed encryption now.
If you want Magisk, just flash unSu script > stock boot.img > Magisk
If you update your phone, it will encrypt your phone again so you need to repeat steps again.
I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?
xabaras666 said:
I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?
Click to expand...
Click to collapse
This is only for the NOKIA 3 - if you have tried this on a different device there could be the possibility of Bricking it, let's hope not.
I suggest going to your own device forum for assistance.
I have reformatted and factory resetted many times but the issue keeps coming back after I boot into system. To clarify, my steps were to reformat inside the wipe section, boot into recovery and check to see there's no encryption, and then boot back to system to install magisk with the manager app. I have tried adding a factory reset to that process, but that won't work either. My TWRP is 3.2.1-0 and I will try to update it and see if it works. Also, sorry if I reply slow.
Just tried to restore a backup for the first time using official TWRP. At the end of restore it had red text saying something like couldn't mount system but said restore complete. Tried booting and it gives the unlock warning then goes to black screen and led light out up constantly and doesn't boot. I try to boot back into recovery and just stays on TWRP splash screen. What did I do wrong and how do I fix this?
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.
Do u have the stock oxygenos full zip on ur phone?
Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Bradl79 said:
Do u have the stock oxygenos full zip on ur phone?
Click to expand...
Click to collapse
No. Can I download it from the oneplus site and transfer it via twrp file manager?
U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though
vinnievegas said:
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.
Click to expand...
Click to collapse
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
What full rom zip?
vinnievegas said:
What full rom zip?
Click to expand...
Click to collapse
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
mikex8593 said:
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Click to expand...
Click to collapse
How do I get the rom to my phone?
vinnievegas said:
How do I get the rom to my phone?
Click to expand...
Click to collapse
I believe OTG works in official TWRP if you have OTG cable and usb. MTP works in unofficial TWRP but I'm not sure which one I that was. May have been this one but don't flash the fix. I think the fix disables MTP
https://forum.xda-developers.com/oneplus-6/how-to/recovery-twrp-3-2-1-1-hydrogen-oxygen-t3795770
Let me know how/if it works out for you.
Bradl79 said:
U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though
Click to expand...
Click to collapse
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?
vinnievegas said:
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?
Click to expand...
Click to collapse
That should work. Just wipe data and cache in TWRP, then restore data from your old backup. I'd recommend keeping a zip file in internal storage of the ROM in case of emergency. That way you can recover without having to wipe internal storage again.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
Old thread but thanks! I had same problem and your method worked for Xiaomi Mi A1
Similar, but reinstalling from scratch. I don want to preserve any data on divice.
By mounting Data partition from TWRP this is what you can see among other things
Internal Storage
NitrogenOS-Updates
Nitrogen-OS-P-kenzo-20190519.zip
I don't remember what next. Any link any link is sufficient and very welcome.
Also a suggestion on where to go to ask, if this is not the right place!
Mi device "xiaomi 3", is perfect for me!
I flashed this firmware yesterday, could any of you who have flashed this and have TWRP check if it skips PIN input in TWRP and automatically decrypts?
Just wondering if it's just my phone or a big security issue.
I use TWRP by pretorian80 which is the only, besides zxz0O0's, that can decrypt FBE.
I also flashed blackball's TWRP, which doesn't decrypt, and I can still view internal SD
I did not decrypt (Format Data) and fileencryption flag is still there in fstab.
ante0 said:
I flashed this firmware yesterday, could any of you who have flashed this and have TWRP check if it skips PIN input in TWRP and automatically decrypts?
Just wondering if it's just my phone or a big security issue.
I use TWRP by pretorian80 which is the only, besides zxz0O0's, that can decrypt FBE.
I also flashed blackball's TWRP, which doesn't decrypt, and I can still view internal SD
I did not decrypt (Format Data) and fileencryption flag is still there in fstab.
Click to expand...
Click to collapse
help I'm in the recovery stock, but it does not let me wipe, it just does not progress please help me, I need to make the wipe data factory reset so I can start my phone, my version is L09 c432 oreo
Excuse me for doing it this way, it's a way to get your attention, I really need help from you.....:llorando:
mataflakitas said:
help I'm in the recovery stock, but it does not let me wipe, it just does not progress please help me, I need to make the wipe data factory reset so I can start my phone, my version is L09 c432 oreo
Excuse me for doing it this way, it's a way to get your attention, I really need help from you.....:llorando:
Click to expand...
Click to collapse
See if you can get it to Low-Level wipe, but it needs to bootloop a few times for that to start.
ante0 said:
See if you can get it to Low-Level wipe, but it needs to bootloop a few times for that to start.
Click to expand...
Click to collapse
I had to make a return to nougat, with the developer's guide firedence in the German forum, thank you anyway
ante0 ...
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Reflash 10.0.1 with the system Updater in settings using local upgrade option. Use Oxygen Updater to re-download if you removed the file. Then through fastboot, boot up twrp (fastboot boot twrp.img) and flash magisk. Unofficial TWRP for Android Q is available in the development forum.
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
E30Nova said:
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
Click to expand...
Click to collapse
No problem. This was due to boot.img mismatch with system. I'd recommend staying away from downloading and flashing patched images.
There's a thread here that explains how to update without losing root, always follow those steps.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
To summarise:
- Download the zip through Oxygen Updater.
- Settings > System > System Update > Cog icon > Local upgrade.
- Select zip. Don't reboot after flashing.
- Open magisk & click install.
- Select after OTA option and then reboot.
If you want to keep TWRP, I would suggest re-downloading the installer and flashing it from magisk instead of using the retention script. After reinstalling magisk (after OTA) and rebooting, you should flash the twrp installer through magisk and then reinstall magisk with the direct install option.
Yeah, I knew it was going to screw stuff up, but I did it anyway.
It's not the first time I knew I shouldn't do something but did it anyway, lol.
At least it was a simple fix, and I didn't lose any data. Maybe my stupidity will hopefully be a lesson to others. If it seems like a bad idea or common sense says not to do it, don't do it, lol.
Thanks again.
E30Nova said:
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Click to expand...
Click to collapse
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------
disbeyad999989 said:
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
Click to expand...
Click to collapse
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
disbeyad999989 said:
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
Click to expand...
Click to collapse
You can always simply boot twrp.img without flashing. (Just make sure you use the right image matching the currently installed android version) I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
EDIT: This user has solved his problem though. Only commenting for posterity.
kgs1992 said:
You can always simply boot twrp.img without flashing. I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
Click to expand...
Click to collapse
That's very true i didn't think about that also, go that route better