Rooting problem open beta 17 - OnePlus 3 Questions & Answers

After Root open beta 17 stook on boot logo
Any solution

Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..

I have the same problem. Neither SuperSu nor Magisk works.

persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help

Use SuperSu 2.82

2.82 works fine for me! Many thanks!

My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)

TO root latest beta an stable version you can follow this guide:

Related

[Question][root] Root 9.2.3.0 (9.5.3.0?) - TWRP

Hi all!
I'm with the 9.2.2.0 Global.
I have the original recovery, just supersu flash with a temporary TWRP (boot instead of flash).
Update a few months ago, when the update came out, to version 9.2.3.0, and I was not able to reboot from TWRP to root the system again, so I went back to version 9.2.2.0.
Is there a method to root easily if I update now?
Do you think I'll have problems with version 9.5.3.0 again ?!
Thank you very much!
You can root this version by supersu.zip 2.82 (don't use supersu.zip SR2.82)! Flash it over recovery.
bahuy2003 said:
You can root this version by supersu.zip 2.82 (don't use supersu.zip SR2.82)! Flash it over recovery.
Click to expand...
Click to collapse
The problem is not in sueprsu flash.
I have the problem to booting the TWRP after updating.
Does BOOT, but can not mount any partition, and any change becomes a soft brick.
Don't use SuperSU, use latest beta Magisk instead.
And whats the problem if you flash TWRP 3.2.1-0 ?

How to Update Rooted Oneplus 5T to 5.1.2?

I do have an idea on how to do it i just want some clarification.
I will lose the TWRP and Root on the process right? If so can someone tell me a step by step guide on updating? And dirty flashing at the same time? The do's and dont's. Thanks!
You are currently in which build? Beta to stable is not recommended.
Btw, I am using bluspark recovery and it survived dirty flashes for me. Else no worries after system boots, boot to bootloader later and flash twrp image again.
Im on stable build should i trust the OTA that has been downloaded on the phone update itself or just use the zip file and flash it via twrp instead? Thanks
Download zip file
Flash it in TWRP and DON'T REBOOT YET
flash Magisk in TWRP
Reboot
Done
At least that's what I did and the root is still here
Kartoflaszman said:
Download zip file
Flash it in TWRP and DON'T REBOOT YET
flash Magisk in TWRP
Reboot
Done
At least that's what I did and the root is still here
Click to expand...
Click to collapse
After flash magisk I flash twrp

[Help] Flashed TWRP but nothing is getting flashed

1)Installed TWRP 3.3 from our beloved @mauronofriofrio
2)Opened twrp,flashed superSu 2.73
Tried flashing a different version of superSu too.
3)Flashing is always successful but there's no change in the system,no root,nothing.
4)After a reboot I can't access the twrp again.It goes back to stock recovery.I have to reflash everytime I need to access twrp.
Rom Version : Latest Official A23
RyanCr7 said:
1)Installed TWRP 3.3 from our beloved @mauronofriofrio
2)Opened twrp,flashed superSu 2.73
Tried flashing a different version of superSu too.
3)Flashing is always successful but there's no change in the system,no root,nothing.
4)After a reboot I can't access the twrp again.It goes back to stock recovery.I have to reflash everytime I need to access twrp.
Rom Version : Latest Official A23
Click to expand...
Click to collapse
Use magisk instead of supersu
mauronofrio said:
Use magisk instead of supersu
Click to expand...
Click to collapse
I'm using A23 build of stock rom.I have no idea how to get boot image out from an unrooted phone.Will there be any problem if I use A19 build boot image and patch it with magisk?

Boot loop any GSI & any Mint Kernel combo Galaxy A50 (SM-A505W)

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.

Question after device restart magisk root lost

hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
wakram001 said:
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
Click to expand...
Click to collapse
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Aserar said:
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Click to expand...
Click to collapse
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Flash Magisk zip
wakram001 said:
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Click to expand...
Click to collapse
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Aserar said:
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Click to expand...
Click to collapse
ok now I will consider custom recovery.( twrp ).

Categories

Resources