Related
Greetings. I received the OTA update (which I did not install!) on my OnePlus 5T today. I'm on OxygenOS 5.0.4 with magisk installed, phone is rooted, bootloader unlocked, stock recovery (no TWRP).
What's the right path to upgrade to 5.1.0?
I'm experienced with the command line and have no problems with it.
Based on my ideas, I think the path should be:
- Download full Oxygen OS 5.1.0 Full Zip
- Start TWRP using adb
Code:
fastboot boot
(which TWRP version?)
- Wipe dalvik and cache
- Flash the downloaded file
- Wipe dalvik and cache
- Flash magisk
That's it. Am I missing something? Do I need to reinstall magisk as specified as last step? Which TWRP version should I use (from the official website?)?
Thanks for your help :good:
Please go through the dedicated update thread that ive made for the update
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
The thread has all the instructions and files needed to update. As far as twrp is concerned i recommend latest codeworkx or or bluspark recovery. The links are available on the thread.
Feel free to post on the thread if you have any further doubts.
Thanks @Funk Wizard , I read that thread (I linked it in my post) but it mentions "For Stock Non Rooted Users with Stock Recovery" and "For Rooted Users with TWRP Recovery" while in my case I'm rooted with STOCK recovery, which doesn't fit any of those 2 sentences. Which one should I follow?
As you are rooted you can flash the full zip from stock recovery that would remove root or you need follow and flash via twrp. If rooted stock recovery is no good TBH and i recommend staying on TWRP.
You can flash twrp from fastboot and then follow the instructions on the flashing post.
In case you dont need root anymore you can just flash the full zip from stock recovery. It will remove root and you will stay on stock recovery. In both the cases, use the full zip to flash via twrp or stock recovery.
No good? Please be more specific, why it's no good? From my understanding keeping stock recovery with magisk installed and bootloader unlocked allows me to pass all SafetyNet checks, which is very helpful if you don't want to deal with apps complaining that you are rooted. I can easily boot to TWRP as long as I can plug my phone into my computer by just using the fastboot command. The only downside I could see is if I brick my phone and have usb debugging disabled, I can't fastboot from adb.
Flashing TWRP would make me fail SafetyNet checks, which I'm not interested into.
After I flash the full zip, do I also need to flash the OTA update?
Thanks by the way, basically the only real "special" thing I need to do is install Magisk again after flashing.
Flashing twrp doesn't break safety net. So it's upto you if you want to stay on stock recovery with no additional benefits or on twrp.
Also, if have full time zip then you don't need to flash ota zip again.
That's good! I'll definitely flash twrp in that case.
@sshivampp Sorry to resurrect this thread, but looks like it's important. On TWRP website itself it's stated that installing TWRP would break dm-verity. What's the consequence of this? https://twrp.me/oneplus/oneplus5t.html
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app
I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?
nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good:
Hello all If any one can help me ,
I was rooted running rooted stock oxygen os before on my Oneplus 5T
after flashing Oxygen OS 5.1.4 Full Zip my phone is not rooting it gets in initial oneplus logo and freeze there without loading OS
Phone is working fine after Flashing Oxygen OS 5.1.4 Full Zip without any issue its not booting after flashing either SuperSu or Magisk
Steps which I follow are
1 Flash custom recovery I have tried both Codeworkx TWRP | Blu_Spark
2 after flashing recovery boot in to recovery flash Supersu or magisk
3 reboot
when I reboot if i Flash supersu it stuck on oneplus logo, If i flash magisk it reboot itself to fastboot so Os is not loading at all.
I have to flash full Zip again every time to get it working but then I dont have root access.
I have tried at least 10 times with different even old versions of magisk and supersu with out any success.
Is there any particular recovery or different version of magisk or superuse I need to flash?
your help will be really appreciated.
Try a different approach. Instead of installing recovery, just get phone rooted first. There is a way where you can boot into twrp (without installing it), and then flash magisk/supersu zip. If your phone is rooted, then you can install twrp later (or keep oem recovery)
This is how you boot into twrp (or any recovery): fastboot boot recovery recovery.img
Let me know how it goes.
As you said boot to recovery without installing it.
One problem currently I am installing recovery and flashing root. After that phone is not booting up in to OS it stuck on oneplus logo. Then I have to force off phone boot in to recovery and flash full os zip to get it working. I can boot in to TWRP because my os didn't load. Now if I use your method and flash root file and if phone won't boot to os that means I won't be able to boot in to TWRP again to flash full os zip to get phone working atleast without root. Any idea?
Huh, frankly I have no idea why you are facing this menace. I can just give two suggestions.
1. Try with older, more stable versions of TWRP and Magisk
2. Get yourself a custom ROM, most ROM's will work flawlessly after flashing root files
Hope for the best!
I usually switch from OpenBeta to LOS and back again. Here's how I switch back to OpenBeta (steps should work for official OOS):
1) Back everything on internal storage up. This one's important
2) Boot into official OOS recovery
3) Wipe EVERYTHING (this is why you need to follow Step 1)
4) Sideload the version of OOS you want. The instructions will be right there on the recovery screen
5) Boot into Fastboot and flash TWRP
6) Flash Magisk and (optional) Xposed
My goal is to get a GSI with Android 11 or higher installed with the corresponding Mint Kernel. The reason being is I can't Magisk root a GSI (tried various methods like: Magisk patch TWRP recovery, install Magisk zip in recovery) and I believe the ramdisk=no is the problem on the SM-A505W variant of the Galaxy A50. I have rooted Pixel phones easily in the past.
I read a suggestion somewhere that installing Mint Kernel could help make rooting easier since Magisk is pre-installed (true?), but I can't get any GSI + Mint Kernel to boot.
GSIs attempted = lineage 18.1, 19.1, Palladium (android 11), SparkOS, Pixel Experience (android 11, 12)
I've then gone to fetch the corresponding Mint Kernel from https://github.com/FreshROMs/android_kernel_samsung_exynos9610_mint/releases
Is my variant just not able to work with Mint Kernel? I'm sure someone, somewhere knows a GSI and Mint Kernel combo that works and allows for Magisk rooting. If so, pls identify versions and any methods you used.
frustrated
p.s. Magisk 25.2 is my preference as I like this version best so far
p.s.s. I do use the key combo to boot from recovery vs system when trying to boot with Magisk when using only a GSI. Only been able to root stock firmware by Magisk patching AP file and flashing with ODIN, then using key combo VOL_UP + POWER (hold a few seconds) when powering phone to boot.
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
V0latyle said:
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
Click to expand...
Click to collapse
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
With stock firmware, I get root holding VOL_UP + POWER (for a few seconds prior to booting). I dont use TWRP in this case, rather ODIN to flash Magisk patched AP file.
GreekFire123 said:
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
Click to expand...
Click to collapse
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
V0latyle said:
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
Click to expand...
Click to collapse
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
GreekFire123 said:
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
Click to expand...
Click to collapse
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
V0latyle said:
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
Click to expand...
Click to collapse
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
GreekFire123 said:
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
Click to expand...
Click to collapse
you can't flash magisk as zip to the recovery on old samsung devices "read magisk FAQs for samsung devices". Check out the fresh discord server so that you can get more assistance directly from the dev.
Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !
I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)
best way is the magisk install
ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13
TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.