Can someone tell me how I can safely update from open beta 9 to open beta 20 while maintaining root. I just want to make sure if there are any extra steps since open beta 9 was before the treble update. I am rooted with magisk.
also can anyone share updated twrp links or links for anything else I need if possible. Thanks
I heard that, I followed the guide in the development section and got and error when trying to flash it. I'm on TWRP 3.2.3-1 as well.
Yes, everything is fine, I have root. It took me a while, because of TWRP. The only problem is, that while you can get magisk, twrp will get overwritten by stock and I could not prevent it.
Process:
1. Install stock recovery (from here: https://www.androidfilehost.com/?fid=674106145207488252) in fastboot (fastboot flash recovery filename.img)
2. Install the new open beta
3. Download magisk on your phone
4. Install TWRP by codeworkx (from here: https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673) in fastboot and boot to twrp immediately.
5. Install magisk from within TWRP's first boot
6. After reboot twrp will most likely get overwritten by stock recovery, but we don't care as we have magisk already.
7. Profit.
@jazzgott so is there no way for me to reinstall twrp after updating? How will I update to new versions after?
@jccspeed
1. flash twrp via fastboot (pc, usb cable and phone and everything in need for this needed)
2. after flashing the recovery, turn off your phone, this is important.. do NOT boot your phone into the OS after flashing.. turn it off (chose power off with your volume keys within the fastboot mode and press the standby button once shortly)
3. hold volume down und power button at the same time until you see the "boot loader unlocked" warning stuff.. keep it pressed there for 2 or 3 more seconds. then let loose of these buttons.
4. you should now be in TWRP. congratulations.
if you now flash magisk, you will keep twrp as long as you keep magisk installed. you can freely boot into the OS and still have TWRP installed. How ever, if you don't install magisk and boot into your OS, your OS will overwrite TWRP with stock recovery.
forgot to mention: please use codeworkx pie twrp. its the one I have installed and have gotten into no problems so far.
@jazzgott @moeq123
Does this method erase the user data? I am encrypted and rooted(magisk). I want to preserve all my data.
@ajithpoison
at first I want to mention something important: always do a full backup.
if you unroot your phone (say, if you uninstall magisk using the uninstall.zip from within the magisk app itself and reboot) you should be able to update to open beta 20 via system update settings (where you need to choose a .zip file for the update.. so you need to download the open beta 20 rom from onceplus website).
(please verify that you are on stock recovery after the uninstalling magisk and reboot process. do this by booting into recovery with the power and volume down method. if you don't know how, google how to boot into recovery for your device)
This updating process should not erase your user data at all.
But be aware, that, if you want to go back to stable releases, you have to wipe everything.. so your user data will be erased if you choose to go back to stable releases.
if you want root and twrp back again, follow my instructions mentioned above.
@moeq123
Let me explain my situation in brief.
I am on the open beta channel. I am rooted(magisk) and I have the official TWRP and I am encrypted.
This is how I update everytime:
1. Download the zip
2. Reboot to recovery
3. Wipe cache and dalvik
4. Install update.zip
5. Install Magisk
6. Wipe cache and dalvik again
7. Reboot
This time, the above method will not work due to the compatibility thingy. I want to preserve app data. There are specific apps which I use and I don't want to lose those app's data. Previously I used titanium backup to take backup of app data. I am not sure whether backing up the app data and then restoring it will work since I am upgrading from oreo to pie. Is there any definite way to backup and restore app data after upgrading to pie?
I am summing up the method which I have to follow now. Correct me if I am wrong.
There are two methods which I know as of now.
Method 1:
The official method given by FunkWizard which involves deleting the compatibility.zip for which some users have reported ERROR 7.
Method 2:
1. Download Magisk & OB20 and have it in internal storage and switch off the phone.
2. Install stock recovery via fastboot.
3. Install the new open beta via stock recovery and switch off.
4. Install TWRP by codeworkx and boot to recovery
5. Install magisk from within TWRP's first boot
6. Clear cache and dalvik
7. Reboot to system and Profit.
(Will TWRP remain as a recovery after following all this or will it get overwritten by the stock recovery?)
@moeq123
Nevermind. I have got it to work without losing any data. I followed all the steps which were in the post by @funkwizard who put up the OP5T OB20 Official update post. It worked well except for one thing. The magisk manager did not show up even after installing magisk through the recovery. (I use BluSpark recovery). So I did a manual installation of the magisk manager apk and everything worked fine. I did not lose any data and so far no bugs.
Related
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9
So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again
Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.
Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups
install beta 7 firmware
Don't bother! It's not worth it! It's just a stupid message!
I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip
Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
This did not completely work for me going from .35 to .64. All the steps completed successfully but when I rebooted the phone, Magisk was not installed so I didn't have root. I was able to then boot to TWRP and successfully install Magisk, but I don't know why it didn't work the first time. Anyone else try this? Did it work as intended for you?
One other thing I noticed - TWRP no longer has an option to wipe the cache under wipe > advanced, only for Dalvik/ART cache. Why?
Wish I would have tried this before i updated and lost root, i flashed a root boot.img with fastboot now im bricked and don't know what to do.
EDIT: got twrp did a factory reset and im in now.
dungnghien said:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
Click to expand...
Click to collapse
In my experience after install back twrp reboot back to recovery (twrp) before flashing magisk .
Does this work when updating to A10?