After flashing a rom mod storage (SD and Internal) access denied. - General Questions and Answers

Hello, i'm having a problem here. I have a Galaxy S5 and i am using XtroLite Lollipop Rom for quite some time now. Yesterday i decided to flash the aroma mod of it's rom so i could add the option fo multiple windows. I had done it before with the same aroma mod and it worked flawessly so i flashed and it did work, but then i noticed some errors and when i looked the explorer both of my storages (internal and external) are there but show no files inside and apparently give no access permissions, the only thing i have permission to access is the root folder. When i go to philz touch recovery i can check the files on both storages and they are there its most likely they are just not accessible. Tried to plug to a pc while on recovery but no deal. I searched google a lot but didn't find anything related, i also can use most of the apps that were installed on the phone but can't install any newer, cause of internal storage being inaccessible, and im without a terminal installed atm.
I kindly ask for some help, thanks in advance.

bump
bump

bump
bump

Related

[Q] ClockworkMod Recovery 6 - no sdcard, no internal dirs! Help?

Bear with me, a noob in the woods....
Installed older version of CWM (5.2.8 maybe?) and it worked fine except no access to external sdcard. It did, however, let me browse around the tablet's internal folders and so I could install from there. But... because I wanted to do restores onto an external 8meg sdcard I have (and one I have proven the Asus can write to happily with OS loaded)... I decided to update CWM to ver 6.0.1.2. I did the update via the old version in a recovery session. But now, I get no options at all for directories I can access. Or am I being dense here? the sdcard will not mount and is not accessible. (Even tried reformatting it.)
I would like to install either a version of TWRP or a version of CWM that will let me access both internal directories and external sdcard.
The good news? I can still boot to my EOS (ver 79) customized ver of Jelly Bean. So I have the working OS... just no way to change my Recovery system into something useable. To replace it, it has to work to let me replace it! (Catch 22 big-time.)
Thanks for any help.

[Q] Phone broken or still hope?

Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200

[Fixed]Need some help

Alright, I've tried everything I could, looked online(/in the forums) for solutions or help, but I just can't figure this out... After struggling a great deal installing the 5.2 update on my K1, I decided to simply flash the 5.2 recovery os image and start from there.
That went fine, so I went to install Magisk to root my tablet, but that didn't go as well. I ran into the same issue I was running into trying to update to 5.2 which is that my storage doesn't properly mount in TWRP (it works normally when using a file manager on the tablet itself and gets detected as it should by the storage manager in settings). I formatted the SD-card I'm using as partially Internal/adaptable storage and partially external, which is probably what causes the problem as TWRP shows the external SD card perfectly, but of the internal storage it only shows the contents of a folder named "InternalStorage' (presumable /sdcard/internal storage, however I can't actually see this to confirm) which is present on the root of the internal SD card. Any files that are in for example my Downloads folder on the internal storage aren't shown in TWRP. I thought installing a factory image would fix this issue, but it hasn't.
In either case, to get around this issue I sideloaded the Magisk zip file to root and it wen't as expected, didn't get any errors. But after booting my tablet, the Magisk Manager app wouldn't finish loading, it's stuck on the flash screen with the Magisk logo. Used the uninstaller and reinstalled through TWRP by placing the zip files on the external SD card and the app still won't load properly. I figure it has something to do with the way I have my SD card setup/partitioned, but I'm at my wits end as to how to fix this atm...
Any help will be appreciated! Preferably something that doesn't include re-partitioning the SD card :angel:
PS: The tablet was rooted with SuperSU before the factory reset, but I'm wanting to make the switch to Magisk because I want to install the Sony Framework to use Remote Play. If there is any other way to install the Sony Framework, using Xposed for example, I can maybe try rooting with SuperSU again.
EDIT: I fixed the issue, turned out the app was installed on the external sd card, moved it to internal storage and it worked!

Help me cant access to storage

last night i just rooted my device because i want to change the emoji.ttf file. The .ttf file that i just downloaded are so big, so the storage of the root explorer cant store that. so i DELETED some files in the root directory that leads me to the bigger problem. I cant access the internal storage!! I've read the solution about it but most of it need the twrp recovery. i didnt install that on my phone. Now its too late to install because the chrome cant access my storage. pls help meeee.
i am using samsung galaxy alpha
p/s pardon my grammar
bro, just backup all ur phone contents, then after you format your phone , go to settings and just do factory reset, if the problem is solve then ok, either you should flash your phone with custom rom of same version which android version you are using, you will get your internal storage back. reply pls

[SOLVED] TWRP can't mount internal storage - the problem is coming back...

I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution​
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.​
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.​
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.

Categories

Resources