Related
I have the Developers Edition of S5 and I successfully flashed recovery TWRP and root last night. I tried backing up apps to ext sd card in Titanium Backup but it keeps saying insufficent storage available error. However i can install play store apps without problems. I have over 5GB of data free. And my sd cards wont show via usb over computer on Mac. The option is grey out and android transfer doesnt work displaying an error message to restart device but it doesnt work either. USB debugging is enabled. I installed and uninstalled kies3 for Mac which also wont work. Any suggestions on these problems that can fix them? I'm pretty frusterated at the moment. I didnt have this problem with my HTC Rezound before.
Droid9684 said:
I have the Developers Edition of S5 and I successfully flashed recovery TWRP and root last night. I tried backing up apps to ext sd card in Titanium Backup but it keeps saying insufficent storage available error. However i can install play store apps without problems. I have over 5GB of data free. And my sd cards wont show via usb over computer on Mac. The option is grey out and android transfer doesnt work displaying an error message to restart device but it doesnt work either. USB debugging is enabled. I installed and uninstalled kies3 for Mac which also wont work. Any suggestions on these problems that can fix them? I'm pretty frusterated at the moment. I didnt have this problem with my HTC Rezound before.
Click to expand...
Click to collapse
1) you need to have sdcard access via root to write to it. Blame kitkat. Use this: https://play.google.com/store/apps/details?id=nextapp.sdfix
2) I can all but guarantee your backup exceeds your available 5gbs free, that's why it's failing. Backup one or two apps and I bet they go through.
Sent from my HTC6525LVW
Fixed!
1ManWolfePack said:
1) you need to have sdcard access via root to write to it. Blame kitkat. Use this: https://play.google.com/store/apps/details?id=nextapp.sdfix
2) I can all but guarantee your backup exceeds your available 5gbs free, that's why it's failing. Backup one or two apps and I bet they go through.
Sent from my HTC6525LVW
Click to expand...
Click to collapse
Last night I was able to fix it using a different method. Following this fourm. http://forum.xda-developers.com/showthread.php?t=2572354 Thanks for your help by the way. :good:
1ManWolfePack said:
1) you need to have sdcard access via root to write to it. Blame kitkat. Use this: https://play.google.com/store/apps/details?id=nextapp.sdfix
2) I can all but guarantee your backup exceeds your available 5gbs free, that's why it's failing. Backup one or two apps and I bet they go through.
Sent from my HTC6525LVW
Click to expand...
Click to collapse
Thanks, this will save me from having to make the config changes myself to fix the stupid broken app permission setting when I root my new dev edition =)
Im looking for any suggestions. I just got my moto x 1575 and soon after upgrading to MM, I installed a new micro SD and found that I could use it as a part of the internal storage. I opted for this feature and proceeded on to unlocking my BL afterwards (http://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808).
All seemed to be going well when I ran 'fastboot reboot' until it wouldnt let me get past the google account login window. This page just loaded endlessly. I rebooted and tried again multiple times with no success.
Next I go into TWRP and wipe data. After that, the phone started to freeze at the blue Motorola logo (before the animation).
Is there anyone who can help? I am wondering if I can simply flash and image and if so which image do I need to flash?
I have fastboot access but ADB will not connect.
I can boot into TWRP but SD memory seems to be messed.
If would really appreciate if someone could assist me with this and willing to donate to anyone who can get me going.
Which phone do you have/where you located (USA?)? Can't point you to a image to flash without knowing. Once you do find the correct image, format microsd card outside phone and put the image on the microsd.
bw03 said:
Which phone do you have/where you located (USA?)? Can't point you to a image to flash without knowing. Once you do find the correct image, format microsd card outside phone and put the image on the microsd.
Click to expand...
Click to collapse
Thank you for your reply. I am using the US model, XT1575.
I am unable to access the SD card. I may be able to push files to it but my computer will not recognize the phone in ADB devices right now. Im still trying to work on that.
check device manager on your pc while booted to twrp. look to see if the device has the drivers installed.
rsa 329 said:
check device manager on your pc while booted to twrp. look to see if the device has the drivers installed.
Click to expand...
Click to collapse
Ive installed ever driver I can find. It shows up as being installed correctly in in device manger.
ay0ung said:
Ive installed ever driver I can find. It shows up as being installed correctly in in device manger.
Click to expand...
Click to collapse
it shows up installed while in adb sideload?
Since you say you already have TWRP on the phone, pull sd card from the phone and format it in windows. No need to use ADB.
Put this image in: http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155.
Put sd card back in phone, boot into TWRP and flash your phone.
BTW, I'm using the linked ROM and its good.
bw03 said:
Since you say you already have TWRP on the phone, pull sd card from the phone and format it in windows. No need to use ADB.
Put this image in: http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155.
Put sd card back in phone, boot into TWRP and flash your phone.
BTW, I'm using the linked ROM and its good.
Click to expand...
Click to collapse
Thanks I was actually returning to say I got it resolved. In a similar was as you suggest.
The Micro SD is trash now I think (a shame to b/c I got the 64Gb card yesterday) windows will not format it, in any type format.
However, the adb issue I was having was related to the laptop I was using (running Win10) it seems. I got a laptop from someone else (running Win7) and connected while in TWRP and copied the exact ROM you suggested, bw03.
Wiped, flashed, wiped, and held onto my butt cheeks and it finally booted. I'm ecstatic as this was a Christmas gift.
Anyways... I found a place on Christmas Day with micro SDs (tried to charge me $20 for 8Gb.. lol) poped it in and chose the portable format option in MM and again, I am unable to access memory card and internal storage. I'm still trying to figure this out and will post anything worthwhile.
When you say you can't access card, you mean through windows? If so, you need to pull the menu down on the phone and select mtp when connected via the USB.
bw03 said:
When you say you can't access card, you mean through windows? If so, you need to pull the menu down on the phone and select mtp when connected via the USB.
Click to expand...
Click to collapse
Yea, i know that. It does nothing when I select mtp. It reverts back to charging right after.
Yeah, I was reluctant to make sd card into internal. You get a warning that sd card will only work on MXP prior to execution. Not doing it until we get to bottom of this.
Sent from my XT1575 using XDA Free mobile app
chindynasty said:
Yeah, I was reluctant to make sd card into internal. You get a warning that sd card will only work on MXP prior to execution. Not doing it until we get to bottom of this.
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
That's a smart move. I have been trying to understand how I fudged it.. I'm certainly not new at this and currently work as a server tech so I know most things like this are user error, but I did everything normally.
I've been trying things all kinds of ways. Installed Ubuntu just to see if I could have any luck there, but nothing.
At my work computer (Windows), I went back to the driver idea. I pluged it in but thought to revoke its previous auths... something I never tried before. Windows checked for the drivers and everything worked well after that.
I'm not sure if that would have resolved it the whole time, but it works well now.
Now i'm worried to even flash another ROM from storage. Ill likely transfer it to internal storage with ES explorer.
I want to use the feature that allows the SD card to be used as Internal storage rather than Portable storage. When I go to Settings-Storage there are no 3 bar, "settings" to allow me to chose to change my current SD card to act as Internal storage. It only Identifies it as Portable storage. It does the same thing when I put in a new SD card. I have a second Galaxy S5 that does exactly the same time so it would appear that the Verizon S5 doesn't support that feature of Marshmallow. Any suggestions?
zico21 said:
I want to use the feature that allows the SD card to be used as Internal storage rather than Portable storage. When I go to Settings-Storage there are no 3 bar, "settings" to allow me to chose to change my current SD card to act as Internal storage. It only Identifies it as Portable storage. It does the same thing when I put in a new SD card. I have a second Galaxy S5 that does exactly the same time so it would appear that the Verizon S5 doesn't support that feature of Marshmallow. Any suggestions?
Click to expand...
Click to collapse
Samsung removed Adopted Storage because they were too lazy to make it work.
The trick to make it work on the S7 does work on the S5.
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
Instead of the : separator I had to use , as the separator to match what I saw in the responses to adb commands.
use the same character you see between the disk numbers after you execute the "sm list-disks" command.
Adoptable Storage Hack Not Working
My son and I each have a 16GB Samsung Galaxy S5, and have followed the procedure listed in Paul O'Brien's article for the S7. Neither of us saw any errors, but it is apparent that the S5 is not using the newly-prepared SD card. My son was getting low memory warnings, which prompted him to try this out. The problem is that he is still getting the warnings after setting up a fast 32GB SD card. Has anyone had the same experience? Has anyone solved the problem?
Big red is crap
Sent from my SM-G900V using Tapatalk
sean19661 said:
Big red is crap
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Don't blame Big Red for this, this is the doing of Samsung
make sure you have the latest version of adb installed before executing commands. data ratio is done with this , instead of this :
[email protected] said:
make sure you have the latest version of adb installed before executing commands. data ratio is done with this , instead of this :
Click to expand...
Click to collapse
To be clear before I try this (sorry if this is a stupid question), would you replace both : with , ?
Like this: 'sm partition disk,179,160 private'
OR just the : in the ratio itself
Like: 'sm partition disk:179,160 private'
Thanks!
kuyankee said:
To be clear before I try this (sorry if this is a stupid question), would you replace both : with , ?
Like this: 'sm partition disk,179,160 private'
OR just the : in the ratio itself
Like: 'sm partition disk:179,160 private'
Thanks!
Click to expand...
Click to collapse
Yes just for the ratio itself.
GS5 Adoptable Storage
tngeezer said:
My son and I each have a 16GB Samsung Galaxy S5, and have followed the procedure listed in Paul O'Brien's article for the S7. Neither of us saw any errors, but it is apparent that the S5 is not using the newly-prepared SD card. My son was getting low memory warnings, which prompted him to try this out. The problem is that he is still getting the warnings after setting up a fast 32GB SD card. Has anyone had the same experience? Has anyone solved the problem?
Click to expand...
Click to collapse
I am having the same problem with my GS5. Followed all the steps, no error messages but the 64gb was not set up. Any ideas?
Thanks
galaxy2016 said:
I am having the same problem with my GS5. Followed all the steps, no error messages but the 64gb was not set up. Any ideas?
Thanks
Click to expand...
Click to collapse
I was having the same issue. Then, in the comments of the linked article I found the following step, which worked for me:
After following the steps to set it to private: Settings > Storage > SD card > More. Migrate your data
That seemed to do the trick for me. It now shows tons of storage even when plugged into my PC. So far so good. I'll report back if I run into any issues with it.
Worked for me
galaxy2016 said:
I am having the same problem with my GS5. Followed all the steps, no error messages but the 64gb was not set up. Any ideas?
Thanks
Click to expand...
Click to collapse
Followed all the steps for my GS5. I thought it was a dud at first, until I realized that I forgot to replace the : with a komma. Worked like a charm! Verizon be damned! Good luck.
My app downloads are still being saved to the phone internal storage, not the adopted storage on the SD card. Shouldn't have to migrate data do SD if S5 supports adoptable storage. Anyone know a workaround or a solution. Thanks.
After following all of the steps with ADB, it seems like I'm successful, but when I reboot, my new, formatted, working SD card (Lexar MicroSDHC 633x 32GB) comes up as corrupt. Any ideas?
(I tried using Root essentials too -tried both methods 4 or 5 times... but no dice)
For those of you that got adoptable storage working - what ROM are you on. I'm trying to figure out if Touchwiz is what's blocking it for me - do you have to be on a CM13 build?
@Nova5 ? @[email protected] ? @kuyankee ? @Mortis13 ?
Thanks!
To make it work on the s5 you need adb, connect the phone by USB and issue the commands through adb on the desktop. Samsung hid the option from the gui.
Nova5 said:
To make it work on the s5 you need adb, connect the phone by USB and issue the commands through adb on the desktop. Samsung hid the option from the gui.
Click to expand...
Click to collapse
@Nova5 - thanks. But as I mentioned in the previous post, I've tried it on adb on the desktop. Looks/acts like it works, but when I reboot, the SD card shows up as corrupted. Everything I've read seems like it SHOULD be able to work, but I'm running into a dead end with every tip I get.
Have you done it and gotten it to work? What ROM are you on? What SD card are you using?
(Those are the only variables I can think of that would be causing me a problem.)
Im running my stock rom, non-rooted VZW S5 with it, used the ADB commands, many reboots. No problems. You do have to ignore the bizarre memory count in the Storage settings. When Samsung removed the UI for Adoptable, they also prevented it from properly calculating it. It works, but it just counts wrong. I used a 128Gig Silicon Power Ultra1 class card. Did a 25/75 split so that I have a decent sized user accessible space.
"sm partition disk:179,160 mixed 25"
Was the command I used (change numbers to match your discovered disk numbers) the 25 is what percentage you want to give to adopted internal memory.
Running fine and has been since I posted on June 3rd. Start with a totally blank card, no partitions at all. get into developer settings, enable USB debugging, use ADB, connect, issue command. Wait while it processes. Sometimes its seconds, sometimes minutes. If you're using a custom rom, that could be the problem. Samsung half crippled it, but it still works
Is link2sd still not working with marshmallow? Not being affable to really move apps to the adoptable storage was really killing me, had to downgrade to 5.0
zico21 said:
I want to use the feature that allows the SD card to be used as Internal storage rather than Portable storage. When I go to Settings-Storage there are no 3 bar, "settings" to allow me to chose to change my current SD card to act as Internal storage. It only Identifies it as Portable storage. It does the same thing when I put in a new SD card. I have a second Galaxy S5 that does exactly the same time so it would appear that the Verizon S5 doesn't support that feature of Marshmallow. Any suggestions?
Click to expand...
Click to collapse
If the phone is rooted, I believe there is an app that you can install that will set it up for you. Otherwise you have to enter some commands using ADB shell.
I used this guide to get mine going. Don't forget to migrate data when you are done!
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
Hey guys I've been trying for a while to get adoptable storage working on my AT&T s7 edge 935a with 6.0.1 with a 256gb sd that came with a Samsung promotion using the adb instructions and it isn't working is the US AT&T version not compatible or am I missing a step i also tried using a app called essential tools and it wants me to flash a file called asplugin.zip but the flash is never successful my phone also has root access. Is there any other know work around to enable adoptable storage I have been working on this for days now and 32gb of phone storage for apps just isn't enough for me. after i type sm partition disk:179,0 private it just does nothing ive also tried doing it mixed thinking that mayb the size was just to large but still nothing
[email protected]:/ # sm list-disks
disk:179,0
[email protected]:/ # sm partition disk:179,0 private
Mine, worked following the walk thru here. is your phone rooted?
Any solutions found regarding this? I'm having the same exact issue. I think Samsung removed adoptable storage completely from the newer firmware. We may need to downgrade.
try XinternalSD module...it changed my sd card to internal storage for everything.
supac said:
Mine, worked following the walk thru here. is your phone rooted?
Click to expand...
Click to collapse
I am having the same issue. Is rooting required? I thought the whole magic of Modaco's adb "hack" was that you could do it without rooting the phone.
guillorylild said:
Hey guys I've been trying for a while to get adoptable storage working on my AT&T s7 edge 935a with 6.0.1 with a 256gb sd that came with a Samsung promotion using the adb instructions and it isn't working is the US AT&T version not compatible or am I missing a step i also tried using a app called essential tools and it wants me to flash a file called asplugin.zip but the flash is never successful my phone also has root access. Is there any other know work around to enable adoptable storage I have been working on this for days now and 32gb of phone storage for apps just isn't enough for me. after i type sm partition disk:179,0 private it just does nothing ive also tried doing it mixed thinking that mayb the size was just to large but still nothing
[email protected]:/ # sm list-disks
disk:179,0
[email protected]:/ # sm partition disk:179,0 private
Click to expand...
Click to collapse
Same problem here. I had a 128GB (SanDisk) SD that had 2 corrupted files that would not allow deleletion and I mistakenly thought those were causing the problem. I plugged in a 64GB (SanDisk) and today bought a new 128GB (Samsung). I haven't been able to change any of them to 'private'. The "list-disks" command returns 179,0, but the "sm partition disk:179,0 private" just returns immediately to the command prompt in the adb shell.
Everyday I like this phone less and less.
Adoptable storage was disabled in the recent ATT firmwares. If you enabled it on an older firmware when it was still possible, it seems like it carries over to newer firmwares (but i cant comfirm this, maybe someone else could). If you MUST have adoptable storage, maybe ODIN one of the older ATT firmswares and enable it. ATT disabled it when we were still on V2 bootloader, so its not possible to revert if youre on the newer v4 bootloader firmwares.
Another option is installing the U firmware and enable it there. But you'll lose wifi calling and other carrier specific features
You can easily do this using root essentials app from app store..
Root is required for this.
It works 100% just one issue that is ir doesn't report the correct available space.
Still looking for that solution.
Hi
Everytime I root this verizon S7 G930U after a couple mins the 16gb card says it is corrupt it tries to format it but doesnt work when I pull it out put it in computer it is fine
Thank you for your time I think it happened after I ran v15 fix debloat
Edit unroot back to stock problem fixed
Do you have a different card to try?
JimmyJammm said:
Do you have a different card to try?
Click to expand...
Click to collapse
Yes plus it did it to first card I had which was from previous phone. I got a new samsung card was working fine till I re rooted dunno if it happened before or after I ran the debloater. If I re loaded it will be good again
It tries to format but still comes up corrupt pc says its fine
stevosdiesel said:
Hi
Everytime I root this verizon S7 G930U after a couple mins the 16gb card says it is corrupt it tries to format it but doesnt work when I pull it out put it in computer it is fine
Thank you for your time I think it happened after I ran v15 fix debloat
Edit unroot back to stock problem fixed
Click to expand...
Click to collapse
I am observing a similar problem. This week I decided to move up from my marshmallow-powered Verizon Galaxy Nexus (i515) to a brand new Verzion Galaxy S7 (G930V) that came with PH1 firmware. Shortly after rooting the stock ROM I noticed that the phone labeled my external sdcard (PNY Elite 200GB UHS-I) as "corrupted" in the settings. I wrote this off to my experimentation with adoptable storage. Reformatting portable storage in settings did not fix the issue; returning to stock did. I then started playing with the couple versions of stang5litre's ROM in the development thread. The same thing kept on happening: at some point the portable storage in settings became labeled "corrupted." Again, I didn't think much of it because I was jumping back and forth between stang5litre's versions and stock to compare features and figured I was doing the corrupting.
As it turns out, the sdcard really isn't corrupted.
Scanning the sdcard on my Windows PC with CHKSK reveals no errors.
Scanning the unmounted sdcard in Android via adb (fsck.exfat /dev/block/mmcblk0) produced no errors.
I can mount /dev/block/mmcblk0p1 to /mnt/media_rw and access the sdcard data.
If the sdcard "corruption" is happening with rooting, I wonder if the solution is in a SuperSU setting.
msbrown74 said:
I am observing a similar problem. This week I decided to move up from my marshmallow-powered Verizon Galaxy Nexus (i515) to a brand new Verzion Galaxy S7 (G930V) that came with PH1 firmware. Shortly after rooting the stock ROM I noticed that the phone labeled my external sdcard (PNY Elite 200GB UHS-I) as "corrupted" in the settings. I wrote this off to my experimentation with adoptable storage. Reformatting portable storage in settings did not fix the issue; returning to stock did. I then started playing with the couple versions of stang5litre's ROM in the development thread. The same thing kept on happening: at some point the portable storage in settings became labeled "corrupted." Again, I didn't think much of it because I was jumping back and forth between stang5litre's versions and stock to compare features and figured I was doing the corrupting.
As it turns out, the sdcard really isn't corrupted.
Scanning the sdcard on my Windows PC with CHKSK reveals no errors.
Scanning the unmounted sdcard in Android via adb (fsck.exfat /dev/block/mmcblk0) produced no errors.
I can mount /dev/block/mmcblk0p1 to /mnt/media_rw and access the sdcard data.
If the sdcard "corruption" is happening with rooting, I wonder if the solution is in a SuperSU setting.
Click to expand...
Click to collapse
Same exact thing here installed stang all was good I believe until I installed xposed I pulled the card for now last time I had not installed xposed & it happened real quick after root. First time I rooted installed xposed & it happened right away. Second time right after root no xposed. Third time had it rooted 3 days all good installed xposed couple reboots later did it again wtf lol. Im a boat heavy diesel mechanic working 16-18 hrs a day so with the time consumption of all this I get a little cross eyed at times lol thanks
msbrown74 said:
If the sdcard "corruption" is happening with rooting, I wonder if the solution is in a SuperSU setting.
Click to expand...
Click to collapse
I played around with various SuperSU options to no avail.
What is the mount point of the external sdcard supposed to be?
msbrown74 said:
I played around with various SuperSU options to no avail.
What is the mount point of the external sdcard supposed to be?
Click to expand...
Click to collapse
I think /whatever u named or labeled card not %100 though
I took things all the way back to stock and have been going in slow steps, letting things sit for a bit between steps to see the moment when the portable sdcard gets "corrupted". I also made sure to diligently follow instructions.
Stock Verizon S7 (G930V, PE1) - SD card good
Rooted following psouza4's pinned guide - SD card good
FlashFire'd S7_or_S7Edge_Fixes_V15.zip - SD card good
FlashFire'd xposed-v85.1-sdk23-arm64-custom - SD Card good
ADB installed Xposedinstaller_3.0_alpha4.apk - SD Card good
SDcard is apparently /dev/block/vold/public:179,1 which mounts to /mnt/media_rw/5075-2B3F as exfat. /mnt/media_rw/5075-2B3F is mounted to /storage /5075-2B3F as sdcardfs.
I'm guessing the "5075-2B3F" is my card label.
Going to let things sit for a few days before I try out stang5litre's V2 ROM again.
msbrown74 said:
I took things all the way back to stock and have been going in slow steps, letting things sit for a bit between steps to see the moment when the portable sdcard gets "corrupted". I also made sure to diligently follow instructions.
Stock Verizon S7 (G930V, PE1) - SD card good
Rooted following psouza4's pinned guide - SD card good
FlashFire'd S7_or_S7Edge_Fixes_V15.zip - SD card good
FlashFire'd xposed-v85.1-sdk23-arm64-custom - SD Card good
ADB installed Xposedinstaller_3.0_alpha4.apk - SD Card good
SDcard is apparently /dev/block/vold/public:179,1 which mounts to /mnt/media_rw/5075-2B3F as exfat. /mnt/media_rw/5075-2B3F is mounted to /storage /5075-2B3F as sdcardfs.
I'm guessing the "5075-2B3F" is my card label.
Going to let things sit for a few days before I try out stang5litre's V2 ROM again.
Click to expand...
Click to collapse
I installed G930U firmware half the battle is over right there most the bloatware is gone. Rooted & cleaned up a little more no xposed yet gotta get some rest. I'll tell u though when I factory re setted off stang v2 I got stuck on activation screen still said stang but corrupted tried everything to no avail no odin cause usb debug is now deactivated. Then I tried power vol up & down keys & home up comes maint boot where one option is to turn on usb debug. Restart to download odin recognises its all good from there
stevosdiesel said:
I installed G930U firmware half the battle is over right there most the bloatware is gone. Rooted & cleaned up a little more no xposed yet gotta get some rest. I'll tell u though when I factory re setted off stang v2 I got stuck on activation screen still said stang but corrupted tried everything to no avail no odin cause usb debug is now deactivated. Then I tried power vol up & down keys & home up comes maint boot where one option is to turn on usb debug. Restart to download odin recognises its all good from there
Click to expand...
Click to collapse
I'm sitting on four days rooted no problems. Used G 930U used fix & not fix & debloat as I used originaly, debloated myself using SD maid pro which is pretty handy no xposed yet gotta get a little more rest before that case it goes bad lo do want xposed mainly for extra stuff for greenify. I Just want to say thanks to everyone here for all the information gathered here. You usually won't here much from me here as I usually try to work through my problems just reading, don't like to bother people. Thanks so much again
I have the same issue, tried 6 different cards which all work on other cells and my pc. I am back to factory now and cards still do not work on my s7
daweeze02 said:
I have the same issue, tried 6 different cards which all work on other cells and my pc. I am back to factory now and cards still do not work on my s7
Click to expand...
Click to collapse
As of now I have everything working including xposed w/ greenify. its been almost a week all is stable. Dont know the exact cause maybe overzealous de bloat. Don't use package disable as this is for non root anyway, I think I used it on first 2 foul ups uninstalled it after root maybe it was too late. Also I just used the fix & not the debloat/fix although I have no Idea if that had any effect the first two times. I've been using SD maid pro to debloat & maintain once u get it figured out its real nice just be careful as default settings are safe but there are settings that will allow you to take yourself down I know from experience lol. Once this symptom happens I dont think there is an easy fix gotta re load . I also think leaning to the conservative side of debloating might help. Right now mine is as close to perfect as I could hope for after four failed attempts. Thanks to u all