Hello Community,
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update? Wasn't able to find it until now.
Sincerely PIPT
You need to do some reading before trying anything more, because you're likely to brick your phone and then you'll really be in trouble.
Yes, you can download and apply updates without having your data wiped and starting from scratch, but there's a very specific process to do this. Failing to follow the proper steps will result in a bricked device. Save yourself some trouble, and learn more about what you're doing before you make a mistake that you can't fix.
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again ?
chazarss said:
You should flash full rom over your system like dirty flash, just wipe dalvik and cache after flashing completed, then reboot.
This is safe way if you have root and twrp
Keep in your mind you will lose root and twrp after upgraded, flash them again
Click to expand...
Click to collapse
You also have to flash supersu after dirty flashing the rom. Also I personally wipe Dalvik and cache before flashing the rom. I've never had any issues with the procedure I follow.
---------- Post added at 17:19 ---------- Previous post was at 17:17 ----------
olskar said:
I had the same situation as you. I first tried update with OTA, it downloaded and rebooted and failed.
When it booted again, and ran the OTA updater it downloaded the full ROM package, rebooted and installed fine in twrp.
Click to expand...
Click to collapse
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
PIPT said:
I am using a custom recovery (TWRP) and my phone is rooted. Can I update this build update in an official way (like in the picture) or do I need to flash a complete ROM? And if I need to flash a complete ROM, has someone the ROM from the new build update?
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
bonham1988 said:
If you have a custom recovery or you're rooted never install an OTA. you need to have official recovery to install an OTA. Dirty flashing the full rom is the best way to update.
Click to expand...
Click to collapse
You can flash full OTA packages through TWRP. You can't flash the smaller patches, but if it's the full firmware, then TWRP 3.0.4.1 will work just fine. Just be sure to flash SuperSU or Magisk before booting to retain root.
redpoint73 said:
See here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
In addition to the needed files, the thread has detailed instructions on how to update (stock phone vs. rooted with TWRP) in Post #3 of the thread.
Based on this, you must flash the full ROM zip (as opposed to the partial OTA "patch"), if you are rooted. But you should still be able keep your data. But I would still back up what is important to you, before updating. Just common sense to have your important data backed up, especially before large OS updates.
I'm actually about to do this myself today (rooted OOS 4.0.3 to 4.1.1), so I'll let you know how that goes.
Click to expand...
Click to collapse
Can I install stock recovery too to make OTA updates and then after the update install TWRP and flash root again? I only ask because I want to do the smaller updates (bug fixes and improvements) too and won't wait for OS and Firmware updates to update my build, because not every little update is listed to get installed manually.
But all in all thx for so many answers
I updated officially with stock recovery and full it's zip, DM Verity has been triggered. It's annoying, anyone else?
edit: fixed it, still annoying that a stock rom tripped it tho.
Related
Hi everyone,
We appreciate everyone’s feedback from the OxygenOS Open Beta 8. With your help, we have optimized and improved several key areas.
The changes include:
Added Expanded Screenshots
Shelf Design Optimizations
General UI Optimizations
DPI Optimizations
Battery Performance Optimizations
Stability and Performance Optimizations
General bug fixes
Please visit the download page here:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/
If you’ve already flashed a previous Open Beta build, you will receive this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data may transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the Open Beta, you’ll continue getting Open Beta OTAs.
Please follow the link below for the UI/UX experience survey. We’d really appreciate a few minutes of your time, as it will help us make OxygenOS even better. One last thing: this is a limited program, so we may disable this download link once we receive enough feedback.
- Feedback on UI/UX: https://goo.gl/forms/hEqMPq9U9QNrxvhc2
Note: If you flash this Open Beta build, you’ll receive Open Beta OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
Thank you for helping us build a better OxygenOS.
Never settle.
Installation Methods
Before we start:This method is only for the OnePlus 3
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Downloads:
Beta 9 Full Zip Official Download
Compatible Stock Recovery
********************* For Stock Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA/Full Zip from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3 is now running on the latest OxygenOS firmware & OS.
PS: The first boot may take some time so keep calm and wait for it to boot.
* After flash is successful go back to recovery and a wipe of cache is recommended.
* If in any case flash is unsuccessful the system would prompt you to download the full 1.4GB zip. So download that and follow the same process as above.
************************ For Rooted Users with TWRP Recovery ************************
Download Beta 9 Full Zip
1. Download the Beta 9 Full Zip on your phone internal memory.
2. Download the Latest SuperSU SR5
4. Reboot To TWRP (Modified 28) & Take a Nandroid of your existing ROM
5. Go to Wipe > Advance Wipe > Select Dalvik & Cache & Swipe to Wipe
6. Install Menu > Select Beta 9 Rom Zip > Swipe to Flash
7. Wipe Dalvik & Cache
8. Flash SuperSU to maintain root
9. Reboot System and Enjoy the Beta 9 Update
* Do not flash Xposed as not compatible with 7.0 builds yet
If you come from a custom rom, i recommend a clean flash and make sure you use the modified TWRP 3.0.2-1.28 as the official one is incompatible with the CB firmware yet.
PS: The first boot may take some time so keep calm and wait for it to boot and the system would boot twice due to flash of supersu so keep calm
PS: Rooted users may either flash the full Beta 9 Zip or they need to flash the previous full zip beta 8 first to overwrite system partition followed by the relevant Beta 9 OTA zip for a successful flash else just the OTA flash would fail with error 7 in TWRP
I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)
salomaoa said:
I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)
Click to expand...
Click to collapse
You can't install the ota update on TWRP recovery. You need the stock one.
Try reflashing TWRP recovery via fastboot and then flash open beta 9(not the ota)
salomaoa said:
I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)
Click to expand...
Click to collapse
Download the recovery at the bottom of the page.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/
Copy it onto your phone with the this Open Beta 9 package.
Start up TWRP, format /dalvik, /cache, /system, /data.
Flash the Open Beta and clean the caches if asked.
Flash the original recovery from TWRP as recovery image, and restart your phone afterwards.
Your phone may boot into the new recovery, then show "Update failed", then do another restart, but after that mine was working.
Does all partitions support f2fs?
smk513 said:
Does all partitions support f2fs?
Click to expand...
Click to collapse
AFAIK, only data partition is f2fs
Sun90 said:
AFAIK, only data partition is f2fs
Click to expand...
Click to collapse
I wonder if the new version is possible...
Thank you for your response.
flashing with twrp will result in recovery booting loop. after downloading ota simply reboot to recovery, download oneolusrecovery from ob9 page. transfer it to phone. select install image in twrp, select reocover, flash as recovery and reboot to recovery. itll show updating.. takes about 20mins
Will modified twrp also not work?
Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Edit: anyways, im on modified twrp, rooted, beta 8, can i dirty flash beta 9?
jfodra said:
Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Click to expand...
Click to collapse
It works. I flashed the full zip with it.
Edit:
Yes you can dirty flash. Everything is working as expected.
jfodra said:
Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Click to expand...
Click to collapse
It will work with full zips !! It won't work it ota updates
As simple as this
Dirty flashed over OB8, everything working fine!
Edit:
Using Modified TWRP
Dirty flashed over OB8, so far no issue's.
Did flash TWRP img after update in TWRP (just to be sure), first boot took a while tho.
Anyone tried supersu?
I have this from yesterday. I was on 3.2.8 from OnePlus site, dated 12.05.16.
Clean flash with TWRP 3.0.2-1.28, thanks to eng_stk. Flash the rom & SuperSU SR5 (if you want root). Refalsh recovery 3.0.2-1.28. Reboot to recovery. If it not works reflash recovery.
Then reboot to system.
I did not flash any mods. All it's ok.
t181 said:
It works. I flashed the full zip with it.
Edit:
Yes you can dirty flash. Everything is working as expected.
Click to expand...
Click to collapse
Oh okay thanks. So is it the same as before? Flash beta 9, flash twrp again, then flash sr5 then reboot?
Edit: Nvrmind, flashed it already and d*mn. It does feel smoother than beta 8. ???
Can it be flashed over modded Open Beta 8 ?
M3ntoR said:
Can it be flashed over modded Open Beta 8 ?
Click to expand...
Click to collapse
Yep. Just make sure to have the full update and not the OTA one. Also, just in case make sure you have the TWRP img and super-su on your phone's memory to be able to flash them again
Any mirror for this? Full zip is downloading really slow and I've already stucked on twrp after OTA Need to dirty flash the full zip, but it is going to dowload around Christmas with that speed...
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
RotesMeerJogger said:
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
Click to expand...
Click to collapse
I have a detailed thread already running on how to update here
http://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
I shall keep it up to date with further releases
Sent from Funk Tuned 3T
okay, i have searched in the wrong category thanks a lot for the link!
this thread can be closed.
how can i receive the updates when i root my phone?
and is there anyway to change the emoji without root?
a7mad-911 said:
how can i receive the updates when i root my phone?
Click to expand...
Click to collapse
You should still receive OTA notifications with root. And it should detect you have root, and will download the full update zip, and it will install with TWRP.
Otherwise, you can manually download the full zip update from Funk WIzard's thread which he linked in Post #2 above (which also has detailed instructions on how to update when rooted and TWRP installed).
Works like a charm with magisk 13.6
I just did it with my OP3t and was super easy.
1) download update.
2) go to hidden folder .Ota
3) move zip file to another folder
4) put Magisk in the folder, too
5) reboot to recovery, flash ROM, then Magisk
6) wipe dalvik/cache and reboot
Edit: updated following testing of redpoint73's correct advice
LeighR said:
4) put twrp and Magisk in the folder, too
5) reboot to recovery, flash ROM, then twrp, then Magisk
Click to expand...
Click to collapse
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
redpoint73 said:
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
Click to expand...
Click to collapse
This means I will keep all apps/settings/files?
Thank you.
JayDz said:
This means I will keep all apps/settings/files?
Click to expand...
Click to collapse
Yes.
Although I will caveat that with my rule of thumb: "hope for the best, prepare for the worst". In that a "dirty" flash of an update is often possible (saving your a lot of work setting up the device again). But you should still be prepared to wipe and do a "clean" install if you run into any problems. So back up your data, by your method of choice, before you try to update.
In particular, for a major update (such as OOS 4.x to 5.x) a clean install (default wipe in TWRP - data, cache and Dalvik) is typically advised.
Shall?? You used the word 'shall' properly in context? Kudos to the school system (I here assume India's) you attended, and to you for paying attention, using the 'King's English' in it's most proper form.
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
serifle said:
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
Click to expand...
Click to collapse
Try flashing this 6.0.1 stock-based ROM:
Computerfreek274_MM_1.0.6 Marshmallow 6.0.1
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's debloated, tweaked version of 6.0.1 Verizon stock firmware.
Yes, you may lose root temporarily. Just re-flash this version of SuperSu, found in this post. On stock 6.0.1 or stock-based 6.0.1 ROM ONLY that version of SuperSu (BETA-SuperSU-v2.62-3-20151211162651) will work for initial root. After you re-root, THEN you can update to newest version of SuperSu.
Also, not sure why you don't want to update to newer TWRP. You don't have to... but I always do. You just flash newer TWRP within TWRP. You install it like any other file in TWRP. Choose install, then "image", then "recovery".
What version TWRP are you using. Our official TWRP maintainer @bhb27 has released TWO newer versions just in 2017 alone.
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
Note:
This is a pre released of 3.0.3 when all the changes are finalized I make and released a new one or when important bugs fix are released
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Any problem found report and use a old version.
Click to expand...
Click to collapse
Just wipe the cache in TWRP.
Hello,
I was wondering, I'd like to root my OP3T , following the guide w/e here or on OnePlus forum. But will be my flashed update as stable as if I keep it on stock recovery ? ( Since people w/e they have OTA on stock or flashing new update on custom recovery )
Besides, I'm already on Nougat 7.1.1 if I root, I won't lose it right ?
And I looked for the right TWRP and the right SuperSu but on their guide are for MM 3.5.1 and not on N 7.1 so where can I find the right version ? on their Website ?
So thank you very much for your help !
If you root your phone, the System Update app will detect it and download the full ROM for each update rather than the partial update. This occurs regardless of the status of your recovery. Since root modifies partitions that the user generally does not have access to, the updater will always overwrite all non-/data partitions during the update. Plus, when you flash an update, it removes root anyways.
My advice is keep TWRP as a custom recovery. When an update is released, you can still go into the Update menu in Settings and download the full ROM (it will do so automatically if it detects root). Then just flash the full ROM in TWRP, flash whatever you used to root, wipe cache, and you're done. If something goes wrong, you can always use TWRP to restore a prior backup. The same can't be done for the stock recovery.
Ok thank you very much for those informations !
Still, do you know which version I should download ? Since I'm on 7.1.1 , thread only shows for 7.0
I searched and I found : SuperSU 2.79 and for TWRP it's the 3.0.4-1 ? Are they right ?
Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.
I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs
Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?
laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.