Related
Hi Everyone,
Anyone got a resolution for sdcard issue with 4.4.4 --- I tried all fixes available -- rooted, updated permissions, etc. installed https://play.google.com/store/apps/details?id=nextapp.sdfix and still having same issue --- I can't even move my pictures from internal to external sdcard.
Link2SD, FolderMount, and Root Explorer is 100% broken and not working.
If it can't be remedy anyone got a good guide to safely downgrade my phone without erasing my files?
any help is greatly appreciated
Thanks,
Shizuwi said:
Hi Everyone,
Anyone got a resolution for sdcard issue with 4.4.4 --- I tried all fixes available -- rooted, updated permissions, etc. installed https://play.google.com/store/apps/details?id=nextapp.sdfix and still having same issue --- I can't even move my pictures from internal to external sdcard.
Link2SD, FolderMount, and Root Explorer is 100% broken and not working.
If it can't be remedy anyone got a good guide to safely downgrade my phone without erasing my files?
any help is greatly appreciated
Thanks,
Click to expand...
Click to collapse
Sounds like you may not be properly rooted. I am on 4.4.4 rooted and i installed the same sdfix app you mentioned and my 3rd party apps have write permissions to sd card.
Sent from my D5503
camaro322hp said:
Sounds like you may not be properly rooted. I am on 4.4.4 rooted and i installed the same sdfix app you mentioned and my 3rd party apps have write permissions to sd card.
Sent from my D5503
Click to expand...
Click to collapse
Thanks for the response --- I followed the thread -- http://forum.xda-developers.com/showthread.php?t=2784900 for rooting my phone --- do you have any advise to re-root? or diff. way to root our phone... I checked root checker and it appears normal but you might be correct.
Try this method
http://forum.xda-developers.com/showthread.php?t=2807092
Best solution for rooting but firstly install new rom 4.4.4 unbranded generic and try this method this is one click method from @munjeni my favorite method. After that you will have root and buaybox and recovery. And after this flash again sdfix and try to move sth to exsd
Shizuwi said:
Thanks for the response --- I followed the thread -- http://forum.xda-developers.com/showthread.php?t=2784900 for rooting my phone --- do you have any advise to re-root? or diff. way to root our phone... I checked root checker and it appears normal but you might be correct.
Click to expand...
Click to collapse
You can try what mosespl mentioned, or you can try easy root tool again (that's what I used and it worked the first time). I saw a lot of people in the easy root tool thread were "half" rooted, or things appear to be rooted but SuperSU failed up update binaries because r/w on system was missing (or something like that, I'm a bit new to all this as well).
camaro322hp said:
You can try what mosespl mentioned, or you can try easy root tool again (that's what I used and it worked the first time). I saw a lot of people in the easy root tool thread were "half" rooted, or things appear to be rooted but SuperSU failed up update binaries because r/w on system was missing (or something like that, I'm a bit new to all this as well).
Click to expand...
Click to collapse
Thanks guys -- i just had the time today and unfortunately without success --- I'm stuck with same problem, guess I don't have a choice but to reflash
Shizuwi said:
Thanks guys -- i just had the time today and unfortunately without success --- I'm stuck with same problem, guess I don't have a choice but to reflash
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54272368&postcount=2094
try flash this patch in recovery to disable RIC if your rom support init.d ... if not, you can also use script manager to give it(99diasbleric) ROOT permission and set it to run at boot.
TheEndHK said:
http://forum.xda-developers.com/showpost.php?p=54272368&postcount=2094
try flash this patch in recovery to disable RIC if your rom support init.d ... if not, you can also use script manager to give it(99diasbleric) ROOT permission and set it to run at boot.
Click to expand...
Click to collapse
Thanks for the help everyone --- i just found out my sdcard is faulty ---- kinda too late I already reflash and use EasyRootTool_v11 and bought new sdcard lol, 100% working now
Thanks again guys.
Shizuwi said:
Thanks for the help everyone --- i just found out my sdcard is faulty ---- kinda too late I already reflash and use EasyRootTool_v11 and bought new sdcard lol, 100% working now
Thanks again guys.
Click to expand...
Click to collapse
Test your old sdcard with a card reader on PC to check if the card is real defective.
Yesterday I put a microsd in z1c and it just can't mount but the card just working fine in windows. At last, I used a USB OTG Cable to connect the card reader with the microsd card and z1c asked me to format it this time and the sd card working fine after that.
TheEndHK said:
Test your old sdcard with a card reader on PC to check if the card is real defective.
Yesterday I put a microsd in z1c and it just can't mount but the card just working fine in windows. At last, I used a USB OTG Cable to connect the card reader with the microsd card and z1c asked me to format it this time and the sd card working fine after that.
Click to expand...
Click to collapse
I actually tested it in Windows and Linux OS -- its 100% broken unfortunately, anyways thanks -- hope I can avail the warranty for this sdcard.
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
Just purchased my galaxy tab s. When I found out how it behaves with external memory rooted it at once, did the thing for read/write permissions, disabled this weird safety feature and... It does not alow editing files to any program which causes a big problem when I try to use "iGO" navigator for example which keeps its files on SD, or use some office program to edit any content on SD... It does alow creating and deleting files though.
Any ideas? Many thanks in advance!
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Or try using a custom kernel
DUHAsianSKILLZ said:
Or tey using a custom kernel
Click to expand...
Click to collapse
what do you mean?
hmaxos said:
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Click to expand...
Click to collapse
Maybe there is some fix possible about it?
gyrtaz said:
what do you mean?
Click to expand...
Click to collapse
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
DUHAsianSKILLZ said:
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
Click to expand...
Click to collapse
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
gyrtaz said:
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
Click to expand...
Click to collapse
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
DUHAsianSKILLZ said:
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
Click to expand...
Click to collapse
The file seems to be edited properly but none of programs are able to edit files. Biggest problem at the moment that iGO won't save its configuration and shut down when a route is entered. I assume it is because of unability to edit files in sd also
Hey guys
Im running low on space in my phone so i decided to move my titanium backup folder to the external sd card. However, its says the folder is not writable. Any way I can solve this ? Im running 5.0 and have xposed installed
Solved: I flashed the ex sd card fix zip and it worked like a charm
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
EddyOS said:
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
Click to expand...
Click to collapse
Yes I am aware but I was wondering are there any root solutions currently available to fix this ?
Just root then apply the sd card fix. Job done.
Sent from my SM-T805 using XDA Free mobile app
It says that the system partition on stockhtc kernel is protected and hence the method will not work
You likely need S-OFF in that case?
Wait... Did you actually root the phone yet?
Darth said:
Wait... Did you actually root the phone yet?
Click to expand...
Click to collapse
Yup phones rooted. Its been checked with root checker and I am running titanium backup, xposed alpha, and automagic premium with it
Then I'm not sure, sorry.
Darth said:
Then I'm not sure, sorry.
Click to expand...
Click to collapse
Is there a way to manually remove the protection for the system partition and make it writable ? I have twrp recovery
xdaaccount123 said:
Is there a way to manually remove the protection for the system partition and make it writable ? I have twrp recovery
Click to expand...
Click to collapse
You're already rooted... That's not the issue.
But I'm not sure what is unfortunately.
Darth said:
You're already rooted... That's not the issue.
But I'm not sure what is unfortunately.
Click to expand...
Click to collapse
should I maybe run through the root process again ? Like reflash supersu ?
Sounds like you have root.
I think you're barking up the wrong tree here. Lol
Here's some things to try,
http://forum.xda-developers.com/htc-one-m8/help/lollipop-titanium-backup-extsd-error-t3009584
http://forum.xda-developers.com/htc-one-m8/help/lollipop-grant-access-to-sdcard-t3015672 (same as above I think)
http://forum.xda-developers.com/htc-one-m8/help/lollipop-blocking-writes-to-external-t2969254
See if anything there helps.
Darth said:
Here's some things to try,
http://forum.xda-developers.com/htc-one-m8/help/lollipop-titanium-backup-extsd-error-t3009584
http://forum.xda-developers.com/htc-one-m8/help/lollipop-grant-access-to-sdcard-t3015672 (same as above I think)
http://forum.xda-developers.com/htc-one-m8/help/lollipop-blocking-writes-to-external-t2969254
See if anything there helps.
Click to expand...
Click to collapse
Unfortunately ive already tried all of those :S
Ive found a really interesting thing though I dont know if its pertinent. When I edit the xml file, it doesnt save after reboot
EddyOS said:
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
Click to expand...
Click to collapse
Sorry for the noob question, but could you explain that? With the stock File manager I can copy/move files to the external memory card. So is that file manager not part of Android or do you mean that apps are not allowed to write to the sd card? But the the stock camera can - all my photos are on sd card ...
xdaaccount123 said:
Ive found a really interesting thing though I dont know if its pertinent. When I edit the xml file, it doesnt save after reboot
Click to expand...
Click to collapse
try a custom kernel; stock kernel usually has /system write protection enabled so it won't allow changes to stick to the system partition
EDIT: or change the file while booted into custom recovery (ie pull the file, edit it, push it back, make sure permissions are correct)
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
unifex_ said:
Sorry for the noob question, but could you explain that? With the stock File manager I can copy/move files to the external memory card. So is that file manager not part of Android or do you mean that apps are not allowed to write to the sd card? But the the stock camera can - all my photos are on sd card ...
Click to expand...
Click to collapse
IF (yes big if) i remember correctly, only system apps have [full] access to the sdcard, all user apps only have access to their respective directories.
feel free to correct me, havent been keeping up to date :angel:
nkk71 said:
try a custom kernel; stock kernel usually has /system write protection enabled so it won't allow changes to stick to the system partition
EDIT: or change the file while booted into custom recovery (ie pull the file, edit it, push it back, make sure permissions are correct)
Click to expand...
Click to collapse
I think I am going to do that. Can you recommend a custom kernel for flashing ? And I have no idea how to change the file while booted into custom recovery, could you please walk me through it if its not too much trouble ?
xdaaccount123 said:
I think I am going to do that. Can you recommend a custom kernel for flashing ? And I have no idea how to change the file while booted into custom recovery, could you please walk me through it if its not too much trouble ?
Click to expand...
Click to collapse
i'm still on KK, but have always used ElementalX (both on M7 and M8), but if you rather do it through TWRP, can you upload the xml for me, i'll change it and post instructions back on how to push it back in TWRP
I have found solution to play games which contains obb data in android oreo based Roms. I have been facing issue from last one week that obb data automatically converted into file and we lost all obb data of all games.
So here is the guide how can you solve this issue by following below steps.
1) Install Xposed framework for Oreo Roms from below link depending on your Android OS Version.
https://www.xda-developers.com/xposed-framework-for-android-oreo-beta/
2) Then go to the playstore and install "Obb on sd" for xposed.
3) Activate the xposed module and Reboot your phone.
4) Download any of your favorite games which contains Obb Data.
5) Then copy Android folder from your internal storage to External sdCard as it is.
6) Open "ObbOnSd" app and go to settings of this app.
7) Select all option and that's it.
The above guide is Personally tested by me. Kindly follow above guide at your own risk.
I am not responsible for any bricked device or damage.
I don't have an SD card
Has anybody figure out the cause of this yet? I'd really love to be using Oreo roms but can't due to this single issue
darkglobe87 said:
I don't have an SD card
Click to expand...
Click to collapse
Get one bro
Having one sd card is always helpful...
darkglobe87 said:
Has anybody figure out the cause of this yet? I'd really love to be using Oreo roms but can't due to this single issue
Click to expand...
Click to collapse
Every custom rom has this issue and dont know what can be the cause of this issue..
will have to wait and use xposed framework untill someone solves this issue....
I've noticed something in case it helps anyone.
The issue described in this thread seems only to happen to me after connecting to WiFi and downloading apps from the play store. I went several days and several restarts without it, then today I connected to WiFi and downloaded some apps, now it is present.
Can anyone give any more ideas about why (or even IF) this could happen?
Also we can install Magic Folder Binder (Magisk Module) to avoid cant pass safetynet
RokCruz said:
Also we can install Magic Folder Binder (Magisk Module) to avoid cant pass safetynet
Click to expand...
Click to collapse
What? I don't follow. That's a totally different issue.
darkglobe87 said:
What? I don't follow. That's a totally different issue.
Click to expand...
Click to collapse
i mean if you install xposed you cant pass safety net right?
with magisk module Magic Folder Binder you can bind you obb folder to your sdcard
Right. Yes, if we have a microsd card...
I still need a permanent easy fix