Database Develop

[ROM][NANDROID-BACKUP] minusculeShield 1.0

minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)

This is great. Will give this a shot today or tomorrow. Thanks!

themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.

I still get notification prompts for ota.

themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such

jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.

same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can

milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way

[Q&A] [ROM][SlimKat][4.4.4] [unofficial]

Q&A for [ROM][SlimKat][4.4.4] [unofficial]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Anghirrim said:
Finally tried the cast fixed version and still have boot loop. So back to version 8.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem with 8.4. With 8. everything works fine

IparryU said:
Cast version works perfectly fine.
Any chance you could include OmniSwitch in the next build @infrag? And possibally an option to use that as default recents? If not, no problemo!
Click to expand...
Click to collapse
Reposting here.

Proximity
Anyone else having problems with their proximity sensor?

updated modern, still getting invalid mmi
I was getting loads of chinese text through with the ussd/mmi system like trubul here, infact I made a thread about it. And also the loss of ussd code functionality with "invalid mmi code" error that he described.
Azlanhu says:
"had the same problem. Apparently, u need to flash the new modem/baseband I9305XXUFNI3 . "
Trubul seems satisfied with the solution, however when I flash the modem linked, whilst it sorts out the Chinese text, I still get invalid mmi codes all the time.
Am I missing something? Is a baseband something separate I need to flash, and if so where can I find it. Or something else?
Cheers.

I9305 (d2lte) SlimKat
I would like to know is it possible to install in Germany the SlimKat D2LTE version, or it may thereby lead to problems?

SlimKat vs SlimSaber
I know that Slim Saber Saber with the mod has been created, but I do not see quite the difference, so I would like to know your opinion of what you think are friendly for BATTERY?

Google Play No connection issue
My i9300 is stuck in a no connection issue in all the gapps, tried everything, clearing cache, data and even hard resetting
I have a rooted Slimkat 4.4.4 build8.0, stock Slimkat's kernel
Sorry for my bad english

SlimKat 4.4.4 8.6 Camera issue
Really nice rom - well done! The only issue I found so far on i9305 is that the camera does not work - it crashes when trying to access it. Even installed Camera MX but that freezes the phone completely on a black screen and a restart is required. I've noticed others were having the same issue. Are there any fixes for this?

Anghirrim said:
Hi, camera used to be fixed by just going back into CWM and wipping cache + dalvik cache. It used to work for me.
For the DPI, did you activate the root in the security option. I think you need it.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same issue with my camera. It was working before V8.6 but now I can't seem to fix it anymore.
No wiping of cache, even clean install (with format of /system) didn't do any good.
I also tried to extract various camera2.apk packages from older versions but I always run into the same problem
when starting up the stock camera app (other camera apps result in a freeze of the entire phone).

Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?

TheDesperadoz said:
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
Click to expand...
Click to collapse
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.

woww thanks you

Is there a way to return to the AOSP recent apps window? The only thing I don't like on this rom is the recent apps window and how it looks and also the fact that there's a gesture instead of a clear recent apps button
Sent from my GT-I9305 using Tapatalk

nielowen said:
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
Click to expand...
Click to collapse
Thanks for the support. I already tried this twice though (and yes I followed the instructions to the letter) but I get the same annoying "unfortunately camera has stopped"
popping up when I then start the CMfix app.
I'm just not sure if this is a ROM issue or if this might be due to a conflict between my apps. Maybe I will try a clean wipe, of cache and system, then reboot into ROM
and see if the camera will work or not. This should tell me if it's ROM related or not.
I hate to restore everything afterwards though and to return to the issue for further investigation
I'd be glad to hear if someone else found an alternative solution!

Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.

Finally got the camera working again
nielowen said:
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Click to expand...
Click to collapse
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working

Also one could try installing a different GAPPS build - there is a stable one from mid September and various betas up to a day ago,
maybe that might be another cure (or cause) to fix the camera bug.

Slim install failed
hi people who can not install Slim, brings in TWRP 2.7 Failed with what have for a recovery flashed her. sorry for my english
https://drive.google.com/file/d/0B4k...ew?usp=sharing

TheDesperadoz said:
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Click to expand...
Click to collapse
Hey! Tried this and the other mentioned stuff several times but still no success... has anyone heard from other ways to get the cam to work? or maybe an alteration of the quoted post?

Fix dec 2016/jan 2017: Snapchat on rooted android device running xposed.

POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.

Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.

Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.

It didn't worked. S7 edge exynos (6.0.1)

Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.

hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?

Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.

AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.

Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?

Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.

Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.

Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.

immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!

Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.

just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)

ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?

Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily

Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.

There is something wrong with your data partition ....

Hello World,
before I explain my problem, I am most humbly asking for one small favour:
Please(!!) nobody give me any advice along the line of: Just do a factory reset and start from scratch
I've got almost a thousand apps installed on my system and I'm in no mood to even try to reconfigure it all over again.
Some time ago I installed the latest beta of Cyanogenmod on my Samsung Galaxy Note Tablet SM-P900.
After some time I encountered so many quirks with it, that I decided to flash back to the latest stable build 12.1-20151029 (Android v5.1.1).
Since I was always able to upgrade w/o wiping data, I did the same here, but right after the downgrade the system started misbehaving.
Matter of fact, I could only boot through to the desktop, once I had removed some google.* related dirs from the data/data location. Right afterwards I reinstalled the affected apps from backup and that fixed that.
Unfortunately during the proces of peeking and poking in data/data I messed up some ownership/permission settings.
I also managed to fix those via an old backup (via: chmod/chown --reference), *but* now I am getting a popup message telling me:
"There is something wrong with your data partition..." everytime I reboot the system.
Afterwards I can work just fine with the tablet, but every 3rd or 4th day it suddenly reboots - then being stable again for another couple of days.
If I could only find out what fault this messages refers to, I could fix it manually - but I couldn't find anything useful by reviewing the logcat info.

Magisk Manager Has Stopped. (Crashing on open)

Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.

Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?

Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.

MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?

I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,

dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.

Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again

Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated

Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.

Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.

Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader

zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!

eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5

zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.

For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.

JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.

Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.

Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?

Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED