Develop Bugs

Rooting problem open beta 17

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:

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

Installing Magisk results in bootloop

I'm not new to these things, but this time it seems I'm totally stuck.
What have I done till now?
- unlocked bootloader
- checked Anti-Version -> 4
- followed step 5 in this thread
What have I gained?
- I'm able to boot into TWRP and also to install several ZIPs. But every ZIP I install goes into bootloop. I have to flash the uninstaller-versions and then my phone works totally normal.
- I tried to install Magisk v16.0, v16.3 and v16.7, no success with each of them.
- I patched boot-image through Magisk itself -> also no success, still bootloop
What haven't I done yet?
- used lazyflasher to permanently flash TWRP as recovery
What are my phones creds?
- I'm on MIUI 9.6.3.0
If I'm right I can't flash any MIUI-version below 9.5.19.0 because of Anti 4. How will I be able to install Magisk and have a working phone? I found a thread where several links were included, one of them showing to some kind of ROM-kitchen, where I'd have the choice to create a custom ROM-zip with Magisk included (among other things like wallpapers, ringtones, which ROM-Version) but I can't find the link anymore. Would that be a possibility? Installing a MIUI beta 10?

just try using lazy flasher...

Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?

Tischbein said:
Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?
Click to expand...
Click to collapse
Yes exactly..

Thanks, worked this way.

How to update OTA updated on rooted Phone

My phone is rooted with magisk and i have twrp recovery..
I am getting latest miui OTA update i want to update my phone but I don't wanna lose my all data is there any way to update miui without losing data on rooted phone ....
What i have?
1. Rooted
2.TWRP RECOVERY
What i don't want to lose?
1. My current Data
2. Magisk root...
Thanks...

Create backup, flash FULL OTA (not incremental) and flash magisk, wipe caches (recommended) and reboot.
If you'd like OTA support you can switch to supporting recovery like redwolf. Read the forums.

If i do what you have mentioned above , so there is no issue of a data loss ?? Or i have to use another recovery?

Hi,
firstly I am sorry for reviving an old thread, but I could not find any answer to this question. Also I am a new member and this is my first post (sorry, if I make any mistakes).
So how do I update my MIUI in the correct way and easily without any dataloss? A step-by-step guide would be very nice.
I have MIUI Global 10.3.2.0 Stable and want to update to MIUI Global 11.0.3.0 Stable.
"Normally" (before my device was rooted) I would directly update via system-update, but I am kind of scared since my phone is rooted now. It is the first time I have rooted my device, so I am new to this topic. I have used Redwolf to root my RN5P, but without flashing it as my recovery (just "fastboot boot redwolf.img", the normal TWRP did not work, since it always asked for password), also I have Magisk 20.1 (Stable) and cam2api installed.
Hope someone can help me. Thanks ahead.

yasin0005 said:
If i do what you have mentioned above , so there is no issue of a data loss ?? Or i have to use another recovery?
Click to expand...
Click to collapse
No data loss happen for me.. Like as you mine was rooted and twrp.. Just flash full recovery rom zip flash with latest version twrp( Not ota)
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
mitu725 said:
No data loss happen for me.. Like as you mine was rooted and twrp.. Just flash full recovery rom zip flash with latest version twrp( Not ota)
Click to expand...
Click to collapse
Yes you lost magisk root... Just flash after, like as you did before

I am waiting since two weeks. Please someone answer/help me. Thanks.

- Get the recovery ROM from https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
- fastboot into custom recovery, if not already permanently installed
- flash the ROM
- re-install Magisk through recovery
- re-install camera2api
Other possibility, since you have only rooted your device, but haven't installed any custom recovery
- use the builtin update from MIUI
- fastboot any custom recovery
- re-install Magisk
- re-install camera2api
Neither way any data will be lost, nor will any app be de-installed

Tischbein said:
- Get the recovery ROM from https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
- fastboot into custom recovery, if not already permanently installed
- flash the ROM
- re-install Magisk through recovery
- re-install camera2api
Other possibility, since you have only rooted your device, but haven't installed any custom recovery
- use the builtin update from MIUI
- fastboot any custom recovery
- re-install Magisk
- re-install camera2api
Neither way any data will be lost, nor will any app be de-installed
Click to expand...
Click to collapse
Thank you for your reply. But in both ways I have to install custom recovery. That is not what I want (else I would have done it earlier in the frist place when I have rooted my phone). I want to keep the original MIUI recovery and "everything original/stock as possible" (that's the reason I stick to MIUI and do not use any custom rom).

Mura1 said:
Thank you for your reply. But in both ways I have to install custom recovery. That is not what I want (else I would have done it earlier in the frist place when I have rooted my phone). I want to keep the original MIUI recovery and "everything original/stock as possible" (that's the reason I stick to MIUI and do not use any custom rom).
Click to expand...
Click to collapse
Read it properly.. In the second method its written that we should fastboot any recovery not flash(install) it.. I hope your problem is solved now:good:
My question is i have orange fox recovery installed. How do I install ota ? Is just flashing the full rom zip enough? I want to preserve data.

@Mura1 you should only fastboot into any custom recovery. This you must have done in the past to root your device. It's the same way.
@Anymeofyou yes this should work. It's the same way I upgrade the device. Afterwards I flash the custom recovery and magisk as well, but that may be only a precausion. In the past I had to fastboot TWRP and flash TWRP once again within TWRP to have it installed. OrangeFox should keep the custom cevoery after an update, but since its only a few seconds to flash OF once again, it doesn't hurt me.
Till now no loss of data recognized.

Ah, thank you @Anymeofyou, know I got it and big thanks to @Tischbein in the first place . Sorry, for having to reading it multiple times (my bad).
I have updated now successfully. Have a nice day.

Tischbein said:
@Mura1 you should only fastboot into any custom recovery. This you must have done in the past to root your device. It's the same way.
@Anymeofyou yes this should work. It's the same way I upgrade the device. Afterwards I flash the custom recovery and magisk as well, but that may be only a precausion. In the past I had to fastboot TWRP and flash TWRP once again within TWRP to have it installed. OrangeFox should keep the custom cevoery after an update, but since its only a few seconds to flash OF once again, it doesn't hurt me.
Till now no loss of data recognized.
Click to expand...
Click to collapse
Thanks @Tischbein

UL-ASUS_I001_1-ASUS-18.0210.2201.211-1.1.1-user.zip

After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?

fux1976 said:
After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?
Click to expand...
Click to collapse
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.

ausaras said:
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.
Click to expand...
Click to collapse
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1

gilsol said:
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1
Click to expand...
Click to collapse
Thank you very much for sharing. This puts my mind at ease.
I will update when I find the time.
Thanks, again!

jb

*issue resolved*