Recently, I flashed the CM11 ROM. After that, I couldn't access the Internal storage (sdcard0) from Inbuilt file manager or from ES File Explorer.
I was running CM10.1 Alpha 9 before this. I flahsed DDLF2, then CF-ROOT and then went to recovery, used wipe data/factory reset and wipe dalvik cache. Then, I flashed CM11.
Did I make a mistake while flashing?
I can still install apps and access both sdcard0 and sdcard1 from the recovery.
How can I access sdcard0 from the ROM? If I can't access it, the Camera, the Gallery and Bluetooth receiving don't work.....
Will re-flashing solve the problem?
Any help would be appreciated.
Ok. So since I'm not a Samsung expert forgive if I make a few mistakes lol. But assuming this is the CM11 you got right?
http://forum.xda-developers.com/showthread.php?t=2534312
drtweak said:
Ok. So since I'm not a Samsung expert forgive if I make a few mistakes lol. But assuming this is the CM11 you got right?
http://forum.xda-developers.com/showthread.php?t=2534312
Click to expand...
Click to collapse
This is weird......
An update was released just a day ago. I will download it, flash it and then see if the problem still persists.
Anyway, I am on this ROM, even though I am not on the latest build.
It seems there was a problem with the SD Card. Recently, it became unmountable. When I removed it, the storage was suddenly fine. No problems at all. Hence, I have found out that the problem was a faulty SD card.
Related
So After I Installed CM10 My Transformer Got Crazy
Somehow The mnt/sdcard Now Called mnt/sdcard1
I Cant Play Games Or Download Apps
Oh And A New Folder Created "storage" And Removable Now Contain MicroSD , SD .USBDisk1 , USBDisk2
I Got Only MicroSD And Yes I Tried To Install Backup It Wont Work
Help
eazyscript said:
So After I Installed CM10 My Transformer Got Crazy
Somehow The mnt/sdcard Now Called mnt/sdcard1
I Cant Play Games Or Download Apps
Oh And A New Folder Created "storage" And Removable Now Contain MicroSD , SD .USBDisk1 , USBDisk2
I Got Only MicroSD And Yes I Tried To Install Backup It Wont Work
Help
Click to expand...
Click to collapse
Are you asking how to get CM10 working correctly? Or just how to get your TF101 working fine again? If the former, I can't really help you there, and that's just going to be difficult because CM10 is still in development, so there could be a host of problems. If you just want to get it working again, I would suggest finding a different (preferably STABLE) ROM and flashing it onto your device. That should work.
Also, if you're flashing a completely different ROM onto your device (not an upgrade or root, or whatever else,) I would go by the general rule of ALWAYS wipe your system, dalvik cache, normal cache, and if you're flashing files from an SD card, be sure to wipe your internal memory too. This will ensure that none of your previous files conflict with the new ones.
This happened to me when i ran one of the JB roms and then tried to nandroid back to revolver. By default the mounting for /data/media/ which is the internal memory is supposed to be at /sdcard/, but for some reason it got switched to /storage/sdcard0/. Nandroiding back to Revolver didn't help as the change was to something before the rom, so even twrp was acting funny because the mountings were present there also.
After some confusion i flashed superwipe lite and all was well. I ran lite since its supposed to leave /data/media/ alone, while reparitioning the rest of the system, so i thought that at some point its got to change the mountings back to the way it was supposed to be in HC and ICS.
Now if i could only remember where those mountings were originally saved i can just go in there and edit the file directly if this happens again.
Sent from my Transformer TF101 using Tapatalk 2
But If I Super Wip My File Will Be Gone No?
And Im Trying To Get My TF101 Back To Work In ICS Rom Too
By The Sorry For My English
eazyscript said:
But If I Super Wip My File Will Be Gone No?
And Im Trying To Get My TF101 Back To Work In ICS Rom Too
By The Sorry For My English
Click to expand...
Click to collapse
What recovery manager are you using? And are you loading your flash packages on a MicroSD or the internal memory?
If you are on jb and want to restore an ics rom you cant...from jb to ics yoj couldnt... but from ics to jb yes
Enviado desde mi Transformer TF101 usando Tapatalk 2
I'm Using Clockwork
I Restored To My Old Mega-tron ICS Rom And Nothing Changed
I'm Loading Form Internal Memory
Help I Need To Finish School Project But I Cant Access To The Files
eazyscript said:
I'm Using Clockwork
I Restored To My Old Mega-tron ICS Rom And Nothing Changed
I'm Loading Form Internal Memory
Help I Need To Finish School Project But I Cant Access To The Files
Click to expand...
Click to collapse
Here's what I would suggest (assuming you have a microSD card):
Load your ROM of choice onto a microSD card and Team Win Recovery Project (TWRP) to your internal memory. Reboot into recovery and flash the TWRP .zip to install it, and then reboot back into recovery. After that, go to "Wipe" and run Wipe Cache, Wipe Dalvik Cache, Factory Reset, and System, and DO NOT REBOOT Then go back and choose "Install" from the menu and make sure you're viewing "using external SD," and there should be your ROM .zip. Flash it and reboot.
Let me know what happens or if you have any questions.
In TWRP My Touch Want Work
eazyscript said:
In TWRP My Touch Want Work
Click to expand...
Click to collapse
This is a TF101 we're talking about, right? You didn't just flash that onto a different model of Transformer?
Yes a TF101
eazyscript said:
Yes a TF101
Click to expand...
Click to collapse
Alright, well, I'm not sure why your touch would't be working if you're using a TF101, but here's my last idea: Go here and do this. Make sure to read it carefully, as that basically just wipes your drive COMPLETELY and reinstalls the STOCK firmware. If you can't figure out how to do that, then I have no idea how else I can help you. I'm sorry.
enterflux said:
Alright, well, I'm not sure why your touch would't be working if you're using a TF101, but here's my last idea: Go here and do this. Make sure to read it carefully, as that basically just wipes your drive COMPLETELY and reinstall the STOCK firmware. If you can't figure out how to do that, then I have no idea how else I can help you. I'm sorry.
Click to expand...
Click to collapse
I Got Him Working The Problem Was With My Fingers I Just Ate Potato
I Wipped And Installed ICS Rom(Megatron) From External But I Got No File Manger And My Cable Kind Of Broken How Can I See If Some Think Changed
eazyscript said:
I Got Him Working The Problem Was With My Fingers I Just Ate Potato
I Wipped And Installed ICS Rom(Megatron) From External But I Got No File Manger And My Cable Kind Of Broken How Can I See If Some Think Changed
Click to expand...
Click to collapse
Can you not just download a file manager app from the Play Store? There's several out there...
I have seemingly successfully installed CM10. However, all of the internal SD folders from my prior stock 4.0.4 install are still there. I want a nice, clean and fresh install and want all junk from the previous stock version gone, but I don't know what's new and what's old. If there is a way to formate/wipe everything, then it seems that that would also delete the new system files as well as as the CM10 Rom zip, thereby making it impossible to reinstall.
Insights and suggestions on this matter greatly appreciated. Thank you.
Make sure you format /system as well as cache and factory reset. Do it twice if it will make you feel better.
You most likely just did a factory reset which leaves a bunch of trash behind.
Format all of that
Flash cm10
Flash gapps
Prcls77 said:
I have seemingly successfully installed CM10. However, all of the internal SD folders from my prior stock 4.0.4 install are still there. I want a nice, clean and fresh install and want all junk from the previous stock version gone, but I don't know what's new and what's old. If there is a way to formate/wipe everything, then it seems that that would also delete the new system files as well as as the CM10 Rom zip, thereby making it impossible to reinstall.
Insights and suggestions on this matter greatly appreciated. Thank you.
Click to expand...
Click to collapse
:crying:
I seem to have answered the last part of my of my inquiry. In CWM 5.5.0.4, I formatted data, system, cache, emmc, sd card. I can now only access recovery mode or download mode. In recovery mode, I obviously can't flash CM10 from the internal SD because I formatted/deleted it! When I get home, I'll try flashing CWM 6.0.1.0 in Odin and then flashing CM10 through the external SD card. If that doesn't work, then I'll have to flash the stock ROM.
Prcls77 said:
:crying:
I seem to have answered the last part of my of my inquiry. In CWM 5.5.0.4, I formatted data, system, cache, emmc, sd card. I can now only access recovery mode or download mode. In recovery mode, I obviously can't flash CM10 from the internal SD because I formatted/deleted it! When I get home, I'll try flashing CWM 6.0.1.0 in Odin and then flashing CM10 through the external SD card. If that doesn't work, then I'll have to flash the stock ROM.
Click to expand...
Click to collapse
Tried it the way outlined above and I now have a nice, clean install CM10!
Next time don't format emmc and sdcard.
For me i delete the files manually using Astro file manager or using a computer and use free app called (sd maid) in google play to remove more and do more cleaning of internal sd card it searches for app remains and empty directories etc all that after flashing the rom immediately before restoring my apps
Not bad but if anybody could find a better solution post it
Sent from my GT-P5100 using xda app-developers app
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
jkremis said:
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
Click to expand...
Click to collapse
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
johnyvlad said:
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
Click to expand...
Click to collapse
Just to be clear, you're saying to try and flash CM10.0 and then do not update when prompted from the notification? The other part was clear enough lol.
Edit: Tried the above and did not fix the problem, but I didn't use fastboot specifically because I have a Samsung phone.
The error I'm getting is "unable to mount /system" when I try and restore a backup.
Bump. Still haven't figured this out.
Problem solved.
Re-flashed CM10.1; doing full data, cache, and dalvik wipes before and after the flash; and the problem was corrected.
Hi, I've been trying to hunt down an answer to my problem with no avail, hopefully someone here can help. I've a rooted Huawei y300 0100 back on factory stock again.
My problem is this after I rooted (went fine first time doing this) installed TWRP created backups, Flashed Fusion x rom no problems at all, found a few bugs thought I would try another ROM, restored my stock from twrp saved backups all good I thought...
Upon re entering recovery everything is fine, factory wipe etc then when it comes to installing any ROM I get the message E: cannot open zip. This happens on any ROM I try, so I know its not the file, file can also be opened on PC and phone explorer.I've formatted the external SD card and re-downloaded ROMs still nowt.
I would just use the stock again and run a new launcher and delete the bloat myself but I can't get Orbit working at all now I'm rooted and back on factory stock when it was working fine on fusionx and orbit/Pandora are pretty much what I did all this for
Any ideas would be appriecated as I'm pretty noobish at this.
Would installing cwm over the top of twrp work?
Do I need to do a special kind of wipe in case of file corruption?
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
Hey Pete, did you flash rom from Int. Sd card or ext. sd card?? Getting the same problem flashing DN3 for note 2 on TWRP 2.7.2.0.
Yay!
petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
ABSOLUTELY confirmed. I was trying it for days. After finding this post, direct downloading to sdcard worked for me.
petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
yeeah... thank you bro
I also had problems with "unable to open zip file" and "bad" errors, seemed to be fixed by formatting a spare 4gb MicroSD to FAT and making sure it was the first thing copied to the SD card. I was using PHILZ recovery, but I'd assume that TWRP will work just as well. I have a suspicion it may have something to do with file fragmentation or maybe allocation block size. Before this I checked MD5SUMs on a few MicroSD cards and they were all perfect, so it wasn't a download or copy corruption, the bootloader just has an issue with the file or filesystem for some reason.
Can confirm. Was having trouble installing Boeffla 3.0 kernal on gnabo 4.4.2 (v8). ( samsung galaxy note 10.1 n801x / n8013 )
Deleted the zips I downloaded, then re-downloaded straight to zip. installed like a boss!
Thanks!
This is a most underrated thread.
Just had the same issue with my old Galaxy S3. Needed to copy the zip directly to internal storage via mtp in twrp.
In newer twrp version it shows zip file corrupt instead of unable to open zip.
So I was trying out a new ROM and I accidentally wiped my internal storage via latest TWRP. No big deal, phone is new and I really only had ROM and kernel files on it.
There's no more files on my SD card, nothing to install. I ADB pushed a ROM and kernel and started over. Installed and rebooted and to my surprise I saw Optimizing App 1 of 193... I got all rebooted and my apps were still there. I searched XDA, but I think it's down ( I searced a ROM thread looking for another answer, but it gave back 0 results. I looked back a couple pages in the thread and found the answer with the keyword(s) I used.. ).
So why didn't wiping internal storage take out my apps? I mean hey, my NANDroid backups got deleted so I'm not complaining lol but yeah, I still have all my apps. Can anyone help me understand what happened?
Edit: Forgot to mention, I wiped EVERYTHING in TWRP. Nuked the phone. Advanced wipe > system, data, cache, dalvik and internal storage
RoyJ said:
So I was trying out a new ROM and I accidentally wiped my internal storage via latest TWRP. No big deal, phone is new and I really only had ROM and kernel files on it.
There's no more files on my SD card, nothing to install. I ADB pushed a ROM and kernel and started over. Installed and rebooted and to my surprise I saw Optimizing App 1 of 193... I got all rebooted and my apps were still there. I searched XDA, but I think it's down ( I searced a ROM thread looking for another answer, but it gave back 0 results. I looked back a couple pages in the thread and found the answer with the keyword(s) I used.. ).
So why didn't wiping internal storage take out my apps? I mean hey, my NANDroid backups got deleted so I'm not complaining lol but yeah, I still have all my apps. Can anyone help me understand what happened?
Click to expand...
Click to collapse
I dont know the specific options in TWRP, but generally "Internal storage" refers to /sdcard and nothing else.
If you're unsure of how the N5 "memory" is set out, have a look here:
Please forward this on to any interested parties who may have been missed
*see edit, sorry
RoyJ said:
*see edit, sorry
Click to expand...
Click to collapse
No idea then. Ask the TWRP devs. Obviously something failed.