Currently using a DNA with S-Off, TWRP, SU.
Up until a few days ago, I was going back and forth between @santod040's 5.0.1 GPE port (http://forum.xda-developers.com/dro...m-google-play-edition-lollipop-v1-00-t2964089) and 5.0.2 LiquidSmooth (http://forum.xda-developers.com/showthread.php?t=2522989). No SD card issues whatsoever on either ROM.
Recently, when going back and forth once again, I stupidly decided that it would be a good idea to wipe the SD card in between the standard Factory Reset -> reflash cycle to get a completely clean slate to work with. I did this via TWRP -> Wipe -> Advanced Wipe -> Internal Storage.
Simply put, it did not do what I had expected it would. The SD contents was not wiped out (according to TWRP's file browser), and I was subsequently able to push and flash the 5.0.1 GPE port successfully. However, I first noticed a problem when trying to install Swiftkey - the language file wouldn't save to internal storage. Pulled down Root Explorer from the Play Store quickly and tried to access the SD card and was only able to see "empty" directories (see attached screen shot).
Rebooting back into recovery, I was still able to see the full contents of the SD card, and the "empty" directories were displaying their contents per usual. Rebooted back into the ROM, same "empty" folders once again.
Reboot back into recovery, flash @santod040's 4.4.2 stock/rooted offering (http://forum.xda-developers.com/showthread.php?t=2560010), and can view the SD card contents in Root Explorer without issue. Since then, I have shuffled around between the previously mentioned GPE port, LiquidSmooth, 5.0.2 NuSenseSIX (http://forum.xda-developers.com/showthread.php?t=2698088), and the stock KitKat build.
All 3 of these Lollipop selections cannot see the SD card contents, but the stock KitKat ROM can.
What the hell did I screw up, is there a fix for it, and if so, what might it be? Any and all thoughts/advice would be greatly appreciated - this is driving me crazy!
Related
The problem: SD card is not recognized when flashing new roms that have been released the month of Feb 2013. Running the Venom Rom, or even the older NillsP roms, the SD card works fine
Here is my setup
- Rooted, HTC unlocked, S-ON, Gingerbread+patch Firmware
Here is what I have tried
- Running the new "wipe tool 5times wipe" , flashing the EclipticRez rom
- I log into the phone, go to settings, storage, click MOUNT SD card, and it says "preparing sd card" but never finishes
- Restarted the phone, back to settings, storage, mount sd card was still there.... clicked it .. no dice
- I then shut the power off, removed the SD card put in a spare 8 GB, settings, storage, mount, and even tried format.. that all failed
- I then... restored the old Venom Rom, and POOF SD card shows up and works....
- I even tried the new viral rom, and the sd card will not work there too...
- I have tried, wiping the rom again, reinstalling the EclipticRez with a different kernal, no dice...
You should get off gingerbread firmware. That sounds like its the problem.
Sent from my Nexus 7 using Tapatalk 2
where does one get the most current firmware
I thought that the firmware was the problem, but just wanted to ask everyone what they thought.... I have been digging around and can not seem to find where the firmware is posted. I am not sure which version to use for the new roms. Is it the ICS firmware? If so, do you have the link?
The latest (Global leak) version can be found here. http://www.androidfilehost.com/?fid=9390034591667978440. Since your s-on, you might have to relock then flash RUU. Unlock again. Install custom recovery. Then flash a rom. It is a lengthy process.
But since you are s-on. I would recommend flashing this one. http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Just a tip, delete the recovery.img from the RUU zip file and then run it. That way it won't overwrite your custom recovery
Sent from my ADR6425LVW using xda app-developers app
slash79 said:
The problem: SD card is not recognized when flashing new roms that have been released the month of Feb 2013. Running the Venom Rom, or even the older NillsP roms, the SD card works fine
Here is my setup
- Rooted, HTC unlocked, S-ON, Gingerbread+patch Firmware
Here is what I have tried
- Running the new "wipe tool 5times wipe" , flashing the EclipticRez rom
- I log into the phone, go to settings, storage, click MOUNT SD card, and it says "preparing sd card" but never finishes
- Restarted the phone, back to settings, storage, mount sd card was still there.... clicked it .. no dice
- I then shut the power off, removed the SD card put in a spare 8 GB, settings, storage, mount, and even tried format.. that all failed
- I then... restored the old Venom Rom, and POOF SD card shows up and works....
- I even tried the new viral rom, and the sd card will not work there too...
- I have tried, wiping the rom again, reinstalling the EclipticRez with a different kernal, no dice...
Click to expand...
Click to collapse
did you ever try RUU'ing back to stock and starting over again? Did that fix the problem?
My phone just stopped mounting my sdcard on any rom.
I've wiped, tried scott's 5x wipe tool, and both roms I tried will not work. it says "insert SD card" but it's already in. I can get it to say "Damaged sdcard" too, and tried formatting, but that didn't work.
So I'm now downloading the latest RUU [ http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ] it says 10 minutes left on the download..This will be my first time ever going back to stock on my rez. But I surely hope this will fix it. But does anyone have any other suggestion before I go back to stock?
edit: ok. I had the RUU downloaded, and was about to flash it, when I realized my sdcard in an external reader seemed to be acting funny. When I was searching for a file with "find" [lists all the files in subdirs] it would always error out and I would have to pull it out and put it back in the reader again.
So I tried formatting My sdcard again [I just did it a few days ago because I kept losing files to LOST.DIR, thought a reformat was in order]. So I did that again, used gparted in Ubuntu to format my sdcard fat32 again. I put it in the phone and booted it up, and I got no errors! yay. I'm glad I didn't restore it to stock. all is well.
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy
Hi All
I have searched the forums for an answer to this, to no avail. Its not an easy problem to search, but apologies if this has been previously discussed..
After some years of owning and flashing various android phones I have suddenly come completely unstuck. I am not sure what has happened, but I suspect that my internal storage has died. No matter what Rom I load (including returning to stock flashed via Odin) I cannot see the phone's internal storage (i.e. the memory that used to appear as "internal USB" or similar). Instead, the "SD card" is being emulated under the folder "0" in the phone's main storage... I am unsure what is happening here.
This happened after flashing the latest version of Omega Rom (v44). Everything went completely fine as usual, I have no idea why this happened. When I rebooted the Rom had installed but internal storage was missing as described above. For some reason the AOKP elements of the Rom are not present, but the system does seem to work.
I have inserted an external SD card to see if the phone would just use that. No effect. It still appears to be "emulating" the external SD card.
I am not sure where to go from here. I can accept that my internal storage is dead. However, as described above inserting an external SD card still doesn't seem to allow the phone to work normally. It is still trying to emulate the SD card in the phone memory, even on a stock rom. On custom roms this seems to stop the AOKP element from working and I end up with some kind of half way house of custom rom and stock Samsung stuff... its bizarre!
Any help or even just thoughts as to what is going on here greatly appreciated.
I remember that in CM roms there is an issue with the 0 folder thing, but not familiar with it. Maybe someone with more experience could recommend you some action steps.
In case you could always try a full wipe (mega wipe) as it includes your sd card (internal) and leaves nothing on the phone. This will enable you to start from scratch (have a flashable rom on your external SD though).
Just switched from an iPhone 4 and I'm raring to get Hyperdrive set up. The phone is rooted, safestrap is set up and a partition is waiting, but everything I've read so far mentions putting the Hyperdrive .zip onto an external SD card. I wasn't planning to get the new S4 till next weekend, so I haven't got a micro SD card around and I won't have one till Tuesday. Can I flash the new ROM from the internal card? Also, will this method of installing a custom ROM over stock work for the S4 as well? http://forum.xda-developers.com/showthread.php?t=2521899
My guess is no, yes and that I just need to be patient for a few days. Thanks in advance!
you will be fine to move to internal or external either or. or at least it did for me
relt said:
Just switched from an iPhone 4 and I'm raring to get Hyperdrive set up. The phone is rooted, safestrap is set up and a partition is waiting, but everything I've read so far mentions putting the Hyperdrive .zip onto an external SD card. I wasn't planning to get the new S4 till next weekend, so I haven't got a micro SD card around and I won't have one till Tuesday. Can I flash the new ROM from the internal card? Also, will this method of installing a custom ROM over stock work for the S4 as well? http://forum.xda-developers.com/showthread.php?t=2521899
My guess is no, yes and that I just need to be patient for a few days. Thanks in advance!
Click to expand...
Click to collapse
Yeah, you can install any ROM from the internal storage. Its just that, since most apps and content (photos and music) is stored on the internal SD, and TW hogs a lot of storage, its usually easier to use an SD card. However, know this, if theres not enough from to unzip the ROM, it wont install.
For example. I have a HyperDrive MK2 Verizon S4. I have a 2GB SD card that I use for music and photo storage. The HyperDrive ROM is 1.7GB compressed, and must be installed that way. However, extracting it shows its about 2.3GB or so. Because thats larger than the 2GB that SD card holds, you get an error about the zip install failing.
You can install any Touchwiz based ROM, like Hyperdrive, Eclipse TW, or BoneStock, to the stock partition easy. However, t is recommended to back up the stock rooted partition first. Just back up the .system partition, dont worry about /data or /cache or anything. If you need the space, pull the backup to your computer. That way you can easily go back to stock if you need to by factory resetting, wiping system, then restoring to system.
As the title says implies, I am having trouble writing data to my external SD card - both through the phone and while connected to a PC.
Background: Got the S4 about a week ago. It was on NK1. I rooted, de-bloated, and made back-up in SafeStrap. Discovered I had to run the KK SD Card fix, but was able to write to the SD card afterwards. Yesterday, while trying to copy a file to the SD card while connected to a PC resulted in a failure (Device stopped responding or was disconnected error). After that, the whole phone went wonky - Titanium, Root Explorer, File Manager, etc... wouldn't open and/or run properly after wards. Several reboots and the problem persisted.
Figured I would just restore my back-up. Well I screwed something up and got stuck in a boot-loop - I odined back to NC5 (figured I didn't need to be on NK1), and re-rooted. Setting my phone back up I realize I can't write to the SD card again. I run the SD Fix but to no avail. Opened Root Explorer and looked at platform.xml, which has all the correct permissions (as in this post).
What's going on and how do I fix this? The SD card is a pretty important feature for me. I can write to and copy to the internal storage either through the phone and while connected to a PC, but not the SD card. FWIW, the SD card works flawlessly in my old phone, so I know it;s not the card.
Going nuts here.
Thanks,
Edit - So playing around with another (lower capacity) SD card I find that everything works perfectly. When I get time this weekend I will have to reformat and/or get a new card. Strangely, the problem card still works good in my old phone. Very weird.
Turns out the sd card was/is bad. Found a great deal on a 64gb card and it's working great.
So now for more noob questions: What is the correct procedure for restoring and or flashing roms with safestrap? On my other phones I'm used to entering recovery (TWRP) and wiping data/cache/dalvik, formatting, doing a factory reset, etc, then flashing and or restoring.
When I attempted to restore my backup on my S4 (as described above), I wiped data, dalvik, & cache. After that I either did a factory reset or format (can't remember which), the phone automatically rebooted, and that is when I got stuck in the bootloop and couldn't enter safestrap recovery. I am interested in flashing Eclipse but would like to know the exact procedures to avoid losing the ability to enter safestrap.
Thanks for the advice.