Develop Bugs

[Help] Problem Rooting using the No-PC Method

Hey Guys,
Before I ramble on about my problems, I would like to thank all the amazing devs that work night an day to make our phones awesome. I have been reading these forums for a couple of weeks and have seen how helpful everyone in these forums are to us noobs.
I'm not new to Rooting (Rooted my G1 a while back and Jailbroke a 1st Gen iPhone way way back lol), but this is my first time Rooting my 3G Slide, which I have had since they were first launched.
I am attempting the No-PC Method described here: http://forum.xda-developers.com/showthread.php?t=896148
I have been trying since last night with no success. I have followed the process step by step, to the T, and continue to encounter the same error every time I try.
I succesfully flash the ESPRIMG.zip and then go to Recovery to apply the "update.zip" file so I can go into Clockwork Recovery, however instead of going into Clockwork Recovery it just gives me the following error:
E:failed to verify whole-file signature
I have searched the forums and none of the responses and solutions have been helpful as almost all of them are users who have already flashed a ROM on their phones as opposed to the Stock one, and a lot of them seem to be prior to this new AndRoot method.
Also, I am using this method as I do not have a USB cable for my phone or a PC for that matter, and havent really researched any Mac mathods of Flashing a Custom ROM to the phone.
Any help would be mucho appreciated!

i think you have to have the update.zip file in the root of your sd card

I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/

yixmal said:
I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/
Click to expand...
Click to collapse
yeah, that's not good if that's all you have there. i was working with someone over at the tmobile forums who was getting the same error (http://forums.t-mobile.com/t5/myTouch-3G-Slide/Easy-root-unroot-Froyo-for-all/td-p/649239/page/6) and it turned out they had the downloaded files in a different folder, and moving them to the root made it work... you may want to try using the files you need from this link instead: http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html

I'm a newbie to the whole programming side of computers, familar with using one though. I am going through the steps of the no pc rooting, and I read through step 6 and I thought it was confusing it says...
Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device multi-select copy then rm r/w in program in upper left on data local folder. I am confused with the rm r/w section there, I haven't gone through the steps, just want to have a general idea before I get in there and screw something up.

Yeah, that ones a lil tricky apparently. Root explorer can be found in the market for ~$4, but if you click the link for the tmobile forum, we found that another app (free) works just as good.

I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Anyways, mine's working now.
As for the step 6 on the instructions. It basically means that after you paste the files you need to go back to the android system (the folder where you can see everything thats on the android) and at the very top of the window you will see a button that says "R/W" next to something like "Mount as R/O". You just need to hit that button so you can write to the folders, then go back to /data/local and long press "Image_flasher" click on permissions and make sure everything is checked, then repeat on "mtd0.img" file.
I know its a long explanation for such a small step but I try to be as detailed as i can. Hope it helped.

Get
update.zip
Put iton ur SD card
and a ROM.zip that you like n the SD card as well..
see if that works

yixmal said:
I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Click to expand...
Click to collapse
^ This
I just went through the same thing - I had restored my phone back to stock and then went to re-root it. I have 2 copies of ESPRIMG, file sizes as follows:
The one that was giving me problems: 145,045,641 bytes
The one that ended up working: 143,701,302 bytes
Once I used the slightly smaller ESPRIMG the process worked perfectly. When using the other one I was getting the same error as the OP.

[Q] Glide suddenly stopped recognizing any SD cards

Hi all!
I am having this issue with my AT&T i927 and I hope you guys can bring some light to the matter.
I was using OsiMood 2.2.14 (which is great!), for about a week, when out of nowhere I got a message saying that the SD was removed or something similar. I was just charging the phone, I wasn't using the phone at all when I got the message.
So far I tried:
1. Tested 3 different SD cards, whith no lucky.
2. Tried to restore only sd-ext under CWM (advanced option), but it did not work.
3. Restored the original AT&T settings that were backed up with CWM and the problem persisted.
Is there any way to mound the ext-sd with CWM or any other way to make sure that it's not a hardware issue?
I read about a so called "usb brick" on other Android phones, but couldn't find anything specific to our model. This may be the case?
Thank you!

Change the volds. fstab file from mmc1 to mmc2. That will redirect the kernels path to the external SD. Problem solved
Sent from my SAMSUNG-SGH-I997 using xda premium

Thank you for the reply, but how exactly am I suposed to do that?

Seemingly, you must edit this file located at /system/etc/vold.fstab on your phone, with a text editor or if you prefer a shell.

Right, I have got to the following line:
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1/mmc1
Should I change it to the following?
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/sdhci-tegra.2/mmc_host/mmc2/mmc2
Another issue is that the file is read-only, how do I edit it? Also there is another identical file under /etc ... should I change the /system/etc one only?
Thanks!

/etc is a link to /system/etc, so this is exactly the same file.
You can edit it with a file manager like "ES File Explorer" which provides root access and write rights on mount.

Thank you. I've managed to change that line as in my previous post, but the issue persists.
By now, I've also flashed the original firmware with ODIN and also tried to flash the kernel only, but still no go.
Any other thoughts?

No ideas? Please guys, I haven't got my sd slot access back yet
Could someone please paste here the original vold.fstab so I can check if something is messed up there?
Thanks

After you flashed the firmware through odin, did you do the "Firmware Upgrade and Initialization" through kies, its under "tools"
(This will wipe your device)
After I did odin stock, I had problems untill I did this.
Sent from my SAMSUNG-SGH-I927 using XDA

Ok I will try that now as a last resort and I will post how it goes.
Well, maybe the real last resort would be the emergency recovery option, but it requires a code.
Fingers crossed...

Um, its been a while! How's it goin'?
Sent from my SAMSUNG-SGH-I927 using XDA

Thanks for the idea, but it didn't work. Still no SD card access.
Any other ideas? What about this emergency option on Kies, is it worth a try?
Any chances to be a hardware issue? like a sudden SD slot defect on the phone? There was no damage or falls or anything like that, for sure.

Well, now it's unrooted with stock recovery... take it to AT&T. They will test it and likely replace it right then. If they don't replace it they will mail you a replacement and you mail the defective one back.
We had to do this when my Dad's Atrix bricked from an ota from Motorola. (it was unmodified too, pure stock.)

Humm... I am afrraid it won't be possible as I livein Rio, and there's no ATT over here. I had to take the risks, as I need a physical keyboard (had a n900 before).
'There's samsung however, but my flash counter is not nil, and I am not sure that they would sort it here, as it's not sold here. To make things worse, I would need the purchase invoice from.US, not sure they sent me that.
Any thoughts are very welcome.

Humm... I am afrraid it won't be possible as I livein Rio, and there's no ATT over here. I had to take the risks, as I need a physical keyboard (had a n900 before).
'There's samsung however, but my flash counter is not nil, and I am not sure that they would sort it here, as it's not sold here. To make things worse, I would need the purchase invoice from.US, not sure they sent me that.
Any thoughts are very welcome.

Oh, that's a bummer. I really don't know, I'm sorry.
Sent from my SAMSUNG-SGH-I927 using XDA

Is there anyway for us to boot into fastboot mode? As I've found on google a way to restore sd brick, it's a fastboot command that you use on windows cmd, having the phone on the usb.
Any clues?

Had this happen to me the other day on my stock rom. Was fooling around in a game and got kicked back out to the home screen where it told me both the internal storage and the sd had been ejected. Took about an hour of turning the phone on and off, but I did manage to get it to work by booting with no sd card inserted, then inserting it after media scanner ran the first time.
Good luck hope this helps

Thank's for the advice men, I will try it and post the results here.

I tried what you said but id didn't work, so I put it back on stock using Odin and updated using Kies. So it was almost back to the original state (only the version was 2.3.5 rather than 2.3.6).
As I had tried everything, I was convinced it was a hardware issue, however, out of nowhere, it recognized the sd that was inside it.
I have no clue how I did it, so I could help other people. I only know that I have installed a animal sounds kids game, that had a counter and some ads and it apparently cleared the recent apps tab (if you hold the home key) and it was back to life then.
Anyone knows, what sort of command would clear the recent tab and in some way force the device to mount or unmount the ext sd?

[Q] Apps not installed after reboot

I need a bit of help guys, the thing is that I'm running Pac-Rom on my LG Nitro HD because I found it to be the most stable rom
after a long trial and error period as well bricking my phone many times. I have only 1 problem on this custom rom, my apps tend to disappear for
absolutely no reason whenever the phone turns off or reboots. I've been messing around for the past 3 days trying to figure out if it's some issue
with the encrypted .android.secure folder so I installed all apps onto the onboard internal storage and deleted the folder then tried replacing all the
apps back on the SDcard hoping that would work, and it didn't. Not all of my apps disappear though, some stay on the SDCard and work perfectly
fine but games over 20-30MB will disappear and I have no clue why. My next effort would be to format the entire SDCard again because I don't
understand why these apps keep disappearing Any ways I appreciate any help, I've been googling and lurking this forum for days now haven't found
anything but a terminal command that doesn't work for me :crying:

Wow this forum is really dead huh?

so,you try to install app to sdcard, and they will disappear?
if this is the case,then make sure you sdcard is not fake. i have seen cards formatted as 16gb, but actually is only 2gb

xordos said:
so,you try to install app to sdcard, and they will disappear?
if this is the case,then make sure you sdcard is not fake. i have seen cards formatted as 16gb, but actually is only 2gb
Click to expand...
Click to collapse
Nah it's not fake, I have tons of pictures, movies, and music on it as well I'm running Pac-ROM and it shows me the amount of my storage on the sdcard as well, it's just when I install the applications onto the sdcard and the phone restarts the apps I installed onto the sdcard just stay on my screen (if placed on) and when I go to tap on them it says "app not installed" :\

i've never heard of this but it sounds like some sort of bug caused the by reflashing of the partitions during reboot.
does the app get deleted from the sdcard or is the app still on the sdcard just not registered with phone?
if the app hasn't been physically deleted it's a rom issue, try the rom in my sig its based off stock but debloated with custom kernel, its very stable.
or if you have your heart set on the rom your already using, try redownloading and reflashing, don't just reflash your download file was probly corrupt. and i don't think these forums are that dead, this is just a bit of an odd issue that the average person doesn't want to guess at, i like guessing tho
if the app is physically deleted from the sdcard, i would try doing some malware/virus scans, because that would be really fishy.

KronicSkillz said:
i've never heard of this but it sounds like some sort of bug caused the by reflashing of the partitions during reboot.
does the app get deleted from the sdcard or is the app still on the sdcard just not registered with phone?
if the app hasn't been physically deleted it's a rom issue, try the rom in my sig its based off stock but debloated with custom kernel, its very stable.
or if you have your heart set on the rom your already using, try redownloading and reflashing, don't just reflash your download file was probly corrupt. and i don't think these forums are that dead, this is just a bit of an odd issue that the average person doesn't want to guess at, i like guessing tho
if the app is physically deleted from the sdcard, i would try doing some malware/virus scans, because that would be really fishy.
Click to expand...
Click to collapse
Well I ended up getting frustrated and downloaded Titanium Backup Pro then moved all my apps onto the SD-Card which works wonders but I decided to change my rom because Pac was using 500mb+ of my ram for system rom memory rather than the normal 200mb since Pac is a hybrid of AOKP, Paranoid Android, and CM10.1 so now I'm happy I got past the SD Card apps not being installed but now I'm having this issue. Yet I cannot even post in the development section due to my posts...

Nevermind I still have the same problem even switching through roms, I'm now running HONO Full Throttle and I'm losing all my apps whenever I restart my phone and have them all on my SD card.

[Q] Help me with media issue?

So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.

No answers anyone?

Just do some searching mate. And use ROOT EXPLORER and give it access.

nsh121193 said:
So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.
Click to expand...
Click to collapse
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.

spexwood said:
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.
Click to expand...
Click to collapse
Okay, thank you, I will try that soon and see if it works.

[Q] Can only create folder through "My Files"?

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