Database Users

Axon 7 B09 root problem

Hi I have a problem with supersu. The device seems properly rooted. Checked it with root checker. Current supersu version is 2.79. Every time I try to delete a system app it seems it is removed, but after a restart its still there. Tried it with tibu and mixplorer. On mixplorer I get the message 'not deleted'

Just have a look here:
https://forum.xda-developers.com/axon-7/help/command-to-root-changes-to-persist-t3440276

Cyb3rzombi3 said:
Just have a look here:
https://forum.xda-developers.com/axon-7/help/command-to-root-changes-to-persist-t3440276
Click to expand...
Click to collapse
Thanks. That did the trick.

[SOLVED] Unable to get Magisk Manager to work - Request help

So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
UPDATE:
Got it to work. You need to have the app installed on internal storage. Mine was installed on sdcard. doh!

buggerman said:
So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
Click to expand...
Click to collapse
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I

Haizum74 said:
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I
Click to expand...
Click to collapse
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.

buggerman said:
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.
Click to expand...
Click to collapse
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?

Haizum74 said:
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?
Click to expand...
Click to collapse
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled Magisk Manager because some people said uninstall and reinstall and try again.
I haven't installed/ uninstalled Magisk yet. Only the manager.

buggerman said:
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled it because some people said uninstall and reinstall and try again.
Click to expand...
Click to collapse
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?

Haizum74 said:
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?
Click to expand...
Click to collapse
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.

buggerman said:
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.
Click to expand...
Click to collapse
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.

Haizum74 said:
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.
Click to expand...
Click to collapse
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk

Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs

Ahh I thought so, well that yt video is ideal then.

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
buggerman said:
Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
As above

Haizum74 said:
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
As above
Click to expand...
Click to collapse
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
No, not if you still want to keep OTA updates without having to download them manually. From what I am aware, unlocking the bootloader and rooting as per the videos instructions is the only way to keep auto OTA.

buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Click to expand...
Click to collapse
TWRP by mohancm

TWRP not booting for me.

UPDATE:
Got it to work. Moved the app to internal storage. My device installed it on sdcard by default. That was causing the freeze.

6T Cant get past loading screen

I'm on a rooted OP 6T, I installed TWRP and Magisk when I first got it on release day. I was using systemize to system install my GCam apk, rebooted and now I cant go any further than the dots loading screen. I tried a date wipe, still cant get any further. I want to try uninstalling magisk or the individually modules but I can't figure out how I do that. When I try to access my files through recovery they seem to be encrypted so I don't know how to get the uninstall zip flashed. Can someone please help

update
I got the magisk uninstaller sideloaded but it says magisk is not installed, is there a way I can just go back to stock and clear everything? I havent installed a custom rom just unlocked and rooted

If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.

geminium said:
If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.
Click to expand...
Click to collapse
not sure what downloading mode is, but I did get into ADB sideload mode. I tried sideloading the magisk uninstallers so I could get rid of whatever module caused the issue, but I got the reply that magisk isn't installed. So now Im not sure what to do from here besides trying to go fully back to stock, which Id rather not

Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one

Striatum_bdr said:
Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one
Click to expand...
Click to collapse
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?

stryver said:
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?
Click to expand...
Click to collapse
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data

Striatum_bdr said:
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data
Click to expand...
Click to collapse
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.

stryver said:
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.
Click to expand...
Click to collapse
No it's all virtual, the physical partition system is not modified.
Again, what do you have to lose by flashing boot.img...

Striatum_bdr said:
No it's all virtual, the physocal partition system is not modified
Click to expand...
Click to collapse
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right? So if say, new system app was causing any conflicts, those conflicts will also survive.

stryver said:
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right?
Click to expand...
Click to collapse
Again what do you have to lose by flashing boot img? Your phone doesn't boot... At worse it won't boot and you'll have to come back to factory by fastboot the would system

Striatum_bdr said:
Again, what do you have to lose by flashing boot.img...
Click to expand...
Click to collapse
Sorry I'm not trying to be argumentative, I'm merely speaking what makes sense to me

Endless speculation can be ended by experimentation...

Striatum_bdr said:
Endless speculation can be ended by experimentation...
Click to expand...
Click to collapse
Agreed, now where is OP to confirm our speculation??

And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description

Striatum_bdr said:
And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description
Click to expand...
Click to collapse
I was just going to check this, never used it myself. Probably should have checked before speaking. Lesson learned lol oh well
Again, sorry if I came off argumentative.
Next thing that comes to mind for OP is that there is a difference between 'wiping data' and 'formatting data'. If you just wiped, try to format data. I had a bootloop from uninstalling a magisk module and quickly recovered by formatting.

stryver said:
Agreed, now where is OP to confirm our speculation??
Click to expand...
Click to collapse
I ended up just downloading the OnePlus tool and stock fajita rom and taking it back to stock. Still not sure exactly what caused the problem, I did everything over again with no issues the second time around

[guide] how to dirty flash open beta on 5/5t ( compitibility & magisk solution)

Hello there,
Although we have done these things tens of times recently we are having some issues with the updates if we are rooted and have magisk modules installed.
I just want to write a small guide to overcome these things which might be helpful.
1) Download the full update zip form Settings/system/system updates/ it is downloaded inside Internal/.ota folder which is hidden by default. or download from anywhere and keep in your storage.
2)Install and Open Mixplorer file manager (MANDATORY) from HERE (Trust me its the best file manager Thanks to @HootanParsa ) if you are already on Pie Be on latest blu_spark TWRP V9.100 HERE Thanks to @eng.stk and skip #3
3) Go to .ota folder open the update zip and delete Compitibility.zip (extracting and repacking is not necessary)
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
5) Reboot to recovery and flash Full update.zip
6) Flash latest Magisk Zip HERE Thanks to @topjohnwu (it keeps your TWRP alive)
7) Reboot System
8) Open Magisk Manager and Enable all modules and reboot your phone
Cheers!!
Note: if you still get reboot issues just keep a latest magisk modules remover in your storage HERE reboot to TWRP and flash it and reboot to system.
Don't forget to smash Thanks Button ??

I believe you need to delete the compatibility zip also to flash in TWRP ?

benny3 said:
I believe you need to delete the compatibility zip also to flash in TWRP ?
Click to expand...
Click to collapse
Yeah it's a must read no 3

intoxicated.mad said:
Yeah it's a must read no 3
Click to expand...
Click to collapse
My bad i missed #3. I'm installing beta 22 as we speak.

benny3 said:
My bad i missed #3. I'm installing beta 22 as we speak.
Click to expand...
Click to collapse
I made it bold for you lol

Might want to fix the link to MiXplorer. It takes you to the the thread, but opens it in reply mode.

Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs

tcat007 said:
Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
On H2OS I did delete that manually and installed bromite webview but it didn't work on OOS, BTW if you keep Chrome you won't have issues I guess.

intoxicated.mad said:
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
Click to expand...
Click to collapse
And if you forgot to disable the magisk modules(like i did :angel: ), just flash "Magisk Uninstaller" - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, then the Magisk installer and then.... nooo more rebooting problem.
Thanks for the guide :good:

getting error 7 on twrp you got the link the the stock boot image of pie by any chance??

Dragonlord07 said:
getting error 7 on twrp you got the link the the stock boot image of pie by any chance??
Click to expand...
Click to collapse
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip

intoxicated.mad said:
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip
Click to expand...
Click to collapse
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
Dragonlord07 said:
did it on a desktop so using 7 zip
Click to expand...
Click to collapse
nvm it worked

Dragonlord07 said:
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
nvm it worked
Click to expand...
Click to collapse
I had problem with 7 zip that's why I didn't mention,
Glad it worked for you :good:

@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse

the Doctor said:
@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Click to expand...
Click to collapse
Nevermind, I'm sorry for including it

Guide updated with blu_spark TWRP V9.91 link no need to delete compitibility.zip now!! Cheers

Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.

mestradab said:
Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.
Click to expand...
Click to collapse
I think you are on Oreo or decrypted and blu_spark TWRP v9.91 isn't compatible with that as far as I know, so ignore that part and try using previous version.

Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards

mestradab said:
Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards
Click to expand...
Click to collapse
Did you delete using Mixplorer??
Make sure you follow every word properly

LineageOS 17.1 system issue?

So, I've gone back to LineageOS for Android 10 on my v20(vs995) and I rooted via magisk.. Why can't I edit any system files or anything related to the system? I can't edit permissions for system files, can't install BusyBox to system, can't edit buildprop, etc.
I've tried resetting the system even and still nothing.. Help please
Thanks.

texas7412 said:
So, I've gone back to LineageOS for Android 10 on my v20(vs995) and I rooted via magisk.. Why can't I edit any system files or anything related to the system? I can't edit permissions for system files, can't install BusyBox to system, can't edit buildprop, etc.
I've tried resetting the system even and still nothing.. Help please
Thanks.
Click to expand...
Click to collapse
You can no longer make changes to system it is all done systemlessly in magisk, refer to the magisk thread for more info
Sent from my LG-H910 using XDA Labs

cnjax said:
You can no longer make changes to system it is all done systemlessly in magisk, refer to the magisk thread for more info
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Why on earth would they do this?..magisk is just getting to be more of a pain... SuperSU was such a simple root method but it doesn't work anymore
Thanks though.

texas7412 said:
Why on earth would they do this?..magisk is just getting to be more of a pain... SuperSU was such a simple root method but it doesn't work anymore
Thanks though.
Click to expand...
Click to collapse
Changes Google made to the Android OS forced magisk to adapt
Sent from my LG-H910 using XDA Labs