Database Info

Hide root?

Sorry if this is in the wrong place, I suppose this is discussion.
Does anyone know a way to hide root from apps like Snapchat? None of the old methods seem to work, presumably because root works differently for this phone/Marshmallow, unless I'm making that up.

make sure you login to Snapchat before you root.

hugeguy said:
make sure you login to Snapchat before you root.
Click to expand...
Click to collapse
I tried unrooting, but it still didn't let me log in. :L No better option than that?

Darkscan said:
I tried unrooting, but it still didn't let me log in. :L No better option than that?
Click to expand...
Click to collapse
nope.. I had to reinstall the Rom and Login and then root the phone. After that you can take a backup of Snapchat with data using titanium pro

I think you can use suhide but i don't think it support nougat yet
Sent from my Pixel using Tapatalk

Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36

TonikJDK said:
Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36
Click to expand...
Click to collapse
Any chance there's a condensed version somewhere that doesn't make me go through 36 pages to find out what everyone's referencing?

See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong

cgrimm9 said:
See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong
Click to expand...
Click to collapse
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.

Darkscan said:
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.
Click to expand...
Click to collapse
Yeah same boat here.. would love to venture out and learn how both partitions work.. would love to do what that user described as I know it is doable with having two partitions... but on another note, I saw a thread to users who were softbricking their device by misusing the reboot to different partition options.. so i have decided to stay away from this until a more compatible TWRP can evolve and it's not tax season

Experimental magisk works fine to hide root. There is a thread.
Sent from my Pixel using Tapatalk

I ended up redoing my phone for the latest update. Decided to stay stock I did install TWRP then decided to run magisk it's not full root but does what I need.here is how I installed it.
1) Dirty or clean flash
2) Flash TWRP
3) Boot to System
4) Reboot to TWRP
5) Flash ElementalX kernel
6) Flash Magisk 11.6
7) Flash TWRP
8) Boot to System
9) reboot system again
10) open up magisk manager you should have magisk root
11) go to settings Enable Magisk Hide enable BusyBox enable systemless hosts
12) reboot phone open magisk manager you should now have magisk root and safety net green Android pay will work and so will apps like Snapchat pokemon go that direction modified systems.

Does magisk root allow root file management and/or Ad Away?

Confused about root

This thread is not about "How do I install twrp" etc. But maybe this can help some of us.
I got a question. If I install twrp and root, am I still able to install system updates? For example, oxygen 5.1.6 comes out. How do I install it?
Have a nice day!

Sconny said:
This thread is not about "How do I install twrp" etc. But maybe this can help some of us.
I got a question. If I install twrp and root, am I still able to install system updates? For example, oxygen 5.1.6 comes out. How do I install it?
Have a nice day!
Click to expand...
Click to collapse
Probably not if it's rooted,in terms of it updating its self. Most likely someone will upload a zip file to flash over the old version though
Sent from my [device_name] using XDA-Developers Legacy app

Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.

mikex8593 said:
Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.
Click to expand...
Click to collapse
What if I have Xposed installed? Will the update go fine with that as long as I disable Substratum overlays and am flashing the full zip and then root afterwards? Or do I have to disable Xposed in Magisk or what? (I use systemless xposed)

mikex8593 said:
Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.
Click to expand...
Click to collapse
Why do I have to delete lockscreen?

Sconny said:
Why do I have to delete lockscreen?
Click to expand...
Click to collapse
What he means is delete the lock screen security so a pin/pattern/face unlock/figerprints... anything other then swipe to unlock your phone because if you have them set and you install a new ROM or flash the Stock ROM then it can't decrypt your phone data or recognize your security on the new ROM.
This also goes for doing a nandroid backup of any current ROM you have installed. Delete all security before booting into TWRP and backing up your ROM.

Eric214 said:
What he means is delete the lock screen security so a pin/pattern/face unlock/figerprints... anything other then swipe to unlock your phone because if you have them set and you install a new ROM or flash the Stock ROM then it can't decrypt your phone data or recognize your security on the new ROM.
This also goes for doing a nandroid backup of any current ROM you have installed. Delete all security before booting into TWRP and backing up your ROM.
Click to expand...
Click to collapse
Oh that's something new to me. But thanks, really

No Worries! Glad to be of help.

NateDev said:
What if I have Xposed installed? Will the update go fine with that as long as I disable Substratum overlays and am flashing the full zip and then root afterwards? Or do I have to disable Xposed in Magisk or what? (I use systemless xposed)
Click to expand...
Click to collapse
Regardless, it will still wipe system. Think of it as a complete factory reset. It will reinstall the full system and data of a brand new room.

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

MicroG experience with U11 Life Android One version (Pie 9.0)??

Does anyone have experience with an unlocked HTC U11 Life and MicroG?
I went on a journey trying to get rid of whole Google stuff on this phone, replacing needed services with MicroG (want to use Maps and PlayStore for bought apps). I just wonder which steps have to be taken on the road since we don't have a custom recovery for HTC U11 Life...

I would recommend using this magisk module https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Should work fine if you are able to deactivate all google stuff and the system still works without it.

saturday_night said:
I would recommend using this magisk module https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Should work fine if you are able to deactivate all google stuff and the system still works without it.
Click to expand...
Click to collapse
I already gave it a try but sadly it needs TWRP to be flashed. Got errors on Magisk...

SHA_NDY said:
I already gave it a try but sadly it needs TWRP to be flashed. Got errors on Magisk...
Click to expand...
Click to collapse
In the early days of this module there was a way without twrp, you could take the official firmware file and extract the system.img, get it from your device or just download one from my collection to your pc. There was a patcher to use on a windows pc for this module especially for devices without twrp, i dont know if they stopped this patcher but it was official from the developer of the module. It patches the system to run this magisk module and you just need to flash the patched system to your device, activate the module in magisk and reboot the device.

saturday_night said:
In the early days of this module there was a way without twrp, you could take the official firmware file and extract the system.img, get it from your device or just download one from my collection to your pc. There was a patcher to use on a windows pc for this module especially for devices without twrp, i dont know if they stopped this patcher but it was official from the developer of the module. It patches the system to run this magisk module and you just need to flash the patched system to your device, activate the module in magisk and reboot the device.
Click to expand...
Click to collapse
Sounds nice, I'll give it a try I think. If I extract system.img from my phone and flash it back later will everything be as before? I mean apps and data and so on? Or will I have to restore a backup afterwards?

SHA_NDY said:
Sounds nice, I'll give it a try I think. If I extract system.img from my phone and flash it back later will everything be as before? I mean apps and data and so on? Or will I have to restore a backup afterwards?
Click to expand...
Click to collapse
I cant say something defenitiv. I experienced that i have to reset the device to boot after flashing a system.img but i also know that someone didnt need to reset his device. I think you have to try it, userdatas/apps are on a different partition anyhow so you dont delete them with flashing a system.img the only question is if the new flashed system will boot without a full wipe of the userdatas. But to have a backup is never wrong.

Sadly MicroG isn't available without TWRP, so bye bye! https://forum.xda-developers.com/showpost.php?p=78626349&postcount=5256

Warning - Notchbarkiller Magisk Module!

Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.

That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.

Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom

For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!

Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).

wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk

lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!

Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1

I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.

Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw

D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...

wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...

Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853

SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed