Related
Before installing a Custom ROM on my rooted Desire I am trying to sort out the SDCard as required but am running into problems.
The guides I've read say to change the size of the Fat32 partition on my card to allow an Ext partition. The trouble is in GParted my card just comes up as 'unallocated'.
If I do format it to Fat32 and add an Ext partition (both Primary) once I put my recovery files (and or update.zip for custom ROM) on the card and enter CWM Recovery it doesnt see the files. It just says 'no files found'.
At one point my phone said it couldn't mount SD Card. This even occured when booting phone as usual as no memory card was showing up.
Has anyone else had this problem?
Well I've spent about three hours on this again today still to no avail.
I tried formatting the card in recovery then brought it up in gparted. The card was still showing up as 'unallocated' and when I created the Fat32/Ext partitions the card once again failed to be read by recovery. Although Windows has no problem seeing it.
Eventually my phone and gparted couldnt see or mount the card at all. After running my phone and formatting the card it eventually saw it.
I thought the problem may be because I connected my card to gparted through the phone so tried a card reader but the card reader didn't appear to work. I don't know if the difference I explained is important.
Is it feasible to install a decent custom rom with A2SD with the partition created through recovery? (which gparted also didnt see) as I am having an absolute headache with gparted. Every work around I try just creates a new problem.
Try this: Use Gparted to partition whole card to 1 FAT32 primary partition and then partition it via 4ext recovery into two partitions as required.
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Steveh8204 said:
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Click to expand...
Click to collapse
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Droidzone said:
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Click to expand...
Click to collapse
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Steveh8204 said:
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Click to expand...
Click to collapse
You were the one who mentioned a full wipe! I thought that was what you meant.
Droidzone said:
You were the one who mentioned a full wipe! I thought that was what you meant.
Click to expand...
Click to collapse
The installation instructions mention a full wipe but reading further it does mention a factory reset so its ok. Will let you know how I get on once the kids are in bed.
Right after some messing about I've had some success. I booted back into Android once I'd used GParted and after a while it saw my SD Card ok.
My Windows PC only saw 12.9GB (of a 16GB card), my phone saw the full 14.9gb in Android and GParted saw both partitions.
As I'd just done a factory reset and my PC saw my Phone I transferred the ROM File to my memory card and installed.
As I had downloaded the Extreme edition I followed the Classic install instructions as instructed and rebooted (after booting to android after install).
The LEd flashed green a couple of times as mentioned but then stopped and is now stuck on the htc screen.
Am I right the file I installed (Supernova_2.4.0.0_signed) is the classic version? Should I have downloaded a sepaerate file for the A2SD installer? The instructions don't seem to suggest this.
And most importantly how do I get my phone to work? lol, please help!
Update: Before I installed the ROM it was showing up correctly in GParted and in Windows it was only showing the Fat32 section which I assumed to be correct. After removing the battery I am back to starting up as normal (with the new Custom ROM) but the SD Card will not show up in GParted and will only allow me to use in Windows if I format first which I havent done. Therefore I can only conclude the file system has got lost somewhere which is why the A2SD installer crashed.
I've very happy with the improved ROM but I still don't have extra stoarge space which was the whole point in upgrading.
Any idea where I can go from here?
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Droidzone said:
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Click to expand...
Click to collapse
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Steveh8204 said:
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Click to expand...
Click to collapse
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Steveh8204 said:
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Click to expand...
Click to collapse
Take my advice and move over to 4ext recovery.. It's the best atm.. you'll love it.
Edit:
I saw your post at droid-force.com and have responded to it there/
My HTC Desire started misbehaving earlier in the year, it would crash and reboot, when it rebooted the SDCard would not be detected, a few days later, it would crash again and the SDCard would re-appear.
When it was visible, the SDCard would work ok a long as you didn't use it much, listening to music for any length of time would cause it to fail again. The SDCard will stop working a day or so after boot, all by itself without any use.
Sometimes it was visible but apparently needed formatting (which isn't true). The card tests fine in computers and I've used two different cards with the same issues.
I figure the issue is with the SDCard controller, although I'd like to get other's views on what the issue might be. I'd like to repair the phone by replacing whatever is necessary, but my knowledge of the hardware build is non-existant right now, could anyone advise where I might start?
dnel said:
The card tests fine in computers and I've used two different cards with the same issues.
Click to expand...
Click to collapse
Do the cards misbehave in recovery also? Have you tried a different rom ?
handy5876 said:
Do the cards misbehave in recovery also? Have you tried a different rom ?
Click to expand...
Click to collapse
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I've wiped and reloaded the rom, recently I successfully updated to the latest Cyanogenmod 7 but the procedure is too risky if I lose the card while flashing so I wouldn't do it again.
A link for HTC Desire disassembly if you are up to it
http://www.formymobile.co.uk/desiredisassembly.php
Never opened my desire. More details in this Nexus one teardown also http://www.ifixit.com/Teardown/Nexus-One-Teardown/1654/2
dnel said:
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I/QUOTE]
check the contacts first before doing a disassembly . it might just need a spray contact cleaner on both card and phone.
Click to expand...
Click to collapse
or you could try this before disassembling your phone http://forum.xda-developers.com/showthread.php?t=691187
it might be an "usb brick".
Thanks for the replies, I decided to try a few things before I took a screw-driver to my phone and so far it's good news but I'm not sure why...
I remembered that a couple of weeks before the SDCard failed, I used alpharev to s-off and flash hboot to CM7r2. So a few days ago I reverted this change.
I re-flashed the stock hboot and then switched from Cyanogen 7.2.0.1 to the last MIUI gingerbread. This process nearly bricked my phone, at one point it wouldn't even boot into recovery and then the 4GB SDcard I was last using in the phone failed completely, but interestingly it failed while it was in my computer and not my phone. After this I switched to a 32GB class 10 SDCard that was in my phone when the SDCard originally started to misbehave so although the 4GB SDCard failed I don't think this is related to the problem because the problem presents with both cards.
After I flashed stock hboot and loaded MIUI, the problem hasn't presented itself, not once.
I then flashed back to CM7r2 and reloaded MIUI and the SDcard worked but I couldn't install any market apps, complaining of a lack of storage. This is with nothing in /data except for the dalvik cache and 250MB of "free space".
I then flashed to the Data++ hboot and reloaded MIUI and the market now works and the SDcard is working.
I don't know how the partition table on the MTD may have caused my SDCard to fail, the best I can guess is there is some bad memory area which when CM7r2 is loaded, corrupts an important system memory area.
I'm leaving it stable right now and will see whether the problem arises again before making further changes. I would be interested to know if there's any fsck-like apps that I could used to check the MTD for errors?
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.
Hello folks,
Recently I have flashed CM 10 via CWM 6.0.3.2 on my Samsung Galaxy W. (I followed this procedure: http://forum.xda-developers.com/showthread.php?t=1990795)
Everything worked out fine (yay) exept for two issues I have:
1. My SGW doesn't recognize my Sd card (internal) at all. (though internal is mounted in cwm menu)
I have several folders regarding my sd and external sd:
- sdcard> tells me it is "unplugged" (in German> translation might differ) when I enter via file manager
- mnt/sdcard> here it tells me my sd card is unplugged as always
- storage/sdcard0> unplugged
- external_sd> it tells me sd card unplugged if I enter
- mnt/external_sd >here I can enter all of my folders
- storage/sdcard1> here I can enter again
2. My SGW can't mount my external sd anymore. I can clearly enter my external sd's files, but apparently I cannot mount my PC. Especially not with Multimount because it requests me to mount my internal sd (issue 1).
So how do I get it to work properly? - is it possible to do it via Terminal Emulator?
Specifications:
- Samsung Galaxy W
- Android Version 4.1.2.
- Kernel Version: 3.0.80-cyanogenmod-gc689589
[email protected] #1
- Cyanogenmod Version: 10-20130605- UNOFFICIAL-ancora
Thanks a lot in advance
Hi, I have similar issues with internal storage after flashing to 4.2.2 and also 4.1.2. Model is galaxy W previously 2.3.6 stock.
At root, i have
/data, which seems to be my internal storage as the FX file explorer show it has a storage of 1.07gb
/external_sd, which contains my files in micro sd card
/sdcard, which ES say SDCard unmounted
/storage, which contains sdcard0 (SDCard unmounted), sdcard1 (micro sd), usbdisk (SDCard unmounted)
In the andriod settings > storage, I can see internal storage with total space 1.07gb, but unable to mount it.
My camera and gallery says "No external storage available".
What should I do? Please help
Have You Try To Change Your Rom?!
ElGzzar said:
Have You Try To Change Your Rom?!
Click to expand...
Click to collapse
Hi, yes actually i did. I've tried 4.2.2, 4.1.2, then 4.0.4. All gave me the same problem.
lennnostra said:
Hi, yes actually i did. I've tried 4.2.2, 4.1.2, then 4.0.4. All gave me the same problem.
Click to expand...
Click to collapse
Try To Format Your SD On Your PC With FAT32 Mod?!
Then Try 10.1 (4.2.2) Rom
Done :good:
ElGzzar said:
Try To Format Your SD On Your PC With FAT32 Mod?!
Then Try 10.1 (4.2.2) Rom
Done :good:
Click to expand...
Click to collapse
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.
honeyx said:
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.
Click to expand...
Click to collapse
If The Internal Is The Problem Then You Must Back To The Main Software 2.x.x
Then Back To The Edited Mods And Rom's
The Internal Storage Will Work
...............................
When That Happen To Me ... That What I Have Done
Sorry For Bad English
Over :good:
ElGzzar said:
If The Internal Is The Problem Then You Must Back To The Main Software 2.x.x
Then Back To The Edited Mods And Rom's
The Internal Storage Will Work
...............................
When That Happen To Me ... That What I Have Done
Sorry For Bad English
Over :good:
Click to expand...
Click to collapse
You probably mean back to stock Samsung ROM. But how will this fix corrupted partitions? And why "must" if there are probably more simple ways to fix it rather than flashing roms forth and back?
First of all he should format both and switch to Mass Storage mode to see if this fixes his issue. Flashing ROMs still can be tryied as a last resort.
honeyx said:
You probably mean back to stock Samsung ROM. But how will this fix corrupted partitions? And why "must" if there are probably more simple ways to fix it rather than flashing roms forth and back?
First of all he should format both and switch to Mass Storage mode to see if this fixes his issue. Flashing ROMs still can be tryied as a last resort.
Click to expand...
Click to collapse
Yeah I Mean (back to stock Samsung ROM) And That This Makes The Phone Due To His Condition Also Came From Its Supplier ..
And That's Fix All Internal Storage Problem's .... By Format The Internal Storage With Force From stock Samsung ROM ...
And I Think He Can't access The Internal Storage To Format It By Him Self ...
I Have Tried That Problem Whin I Have Got My Mobile New .. I Haven't Found Solve For It , So I Have Back To The stock Samsung ROM
..
And Found Every Thing Work Fine Then I Have Back To CM Mod Again... :victory:
If You Have Another Simple Way For That Problem Tell Him ,Please ...
Over :good:
ElGzzar said:
Yeah I Mean (back to stock Samsung ROM) And That This Makes The Phone Due To His Condition Also Came From Its Supplier ..
And That's Fix All Internal Storage Problem's .... By Format The Internal Storage With Force From stock Samsung ROM ...
And I Think He Can't access The Internal Storage To Format It By Him Self ...
I Have Tried That Problem Whin I Have Got My Mobile New .. I Haven't Found Solve For It , So I Have Back To The stock Samsung ROM
..
And Found Every Thing Work Fine Then I Have Back To CM Mod Again... :victory:
If You Have Another Simple Way For That Problem Tell Him ,Please ...
Over :good:
Click to expand...
Click to collapse
I think you are mixing something up. First of all he didn´t say he can´t mount / access it from CWM Recovery but from a running ROM. This is two different things so it still should be possible to access both in CWM Recovery and to do a format.
Secound. Flashing a ROM will not format the internal Storage but only the partition where the ROM will be flashed to. They are not the same, so this is also two different things. So even if you flash a ROM but are having corrupted SDcards (Internal and external) they will stay corrupted till you fix this.
And this is why I suggested to first boot into RECOVERY, format both and finally after rebooting change to Mass Storage as the MTP Mode is not always working very well. If this doesn´t help he still can flash back to stock ROM.
However now I´m just repeating what I already said before. If you can´t get it, then I´m sorry for you.
honeyx said:
I think you are mixing something up. First of all he didn´t say he can´t mount / access it from CWM Recovery but from a running ROM. This is two different things so it still should be possible to access both in CWM Recovery and to do a format.
Secound. Flashing a ROM will not format the internal Storage but only the partition where the ROM will be flashed to. They are not the same, so this is also two different things. So even if you flash a ROM but are having corrupted SDcards (Internal and external) they will stay corrupted till you fix this.
And this is why I suggested to first boot into RECOVERY, format both and finally after rebooting change to Mass Storage as the MTP Mode is not always working very well. If this doesn´t help he still can flash back to stock ROM.
However now I´m just repeating what I already said before. If you can´t get it, then I´m sorry for you.
Click to expand...
Click to collapse
Yeah Yeah I See Now Thank's For Teaching Me .. :victory:
And I'm Sorry That is My Missd
Sorry For Bad English ToO ..
Over XD
Thanks
honeyx said:
This can be done for the SDcard you can unplug and plug directly to an other device like an PC, but not with the internal.
So better try the following. Secure your files if you can. Reboot into recovery and format there both. Rebooot into CM10 or whatever ROM you are using and change your USB operation mode from MTP to Mass Storage.
Click to expand...
Click to collapse
Thanks man,
your knowledge regarding this issue immediately solved my problem. My girlfriend's very happy now
Maybe I ll get lucky tonight Just kidding, I get lucky whenever I want
Greetings,
Max
Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you
brendyh said:
Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you
Click to expand...
Click to collapse
This thread seems relevant but I tried the script to see if I could tell you what mine is called but got "permission denied".
http://forum.xda-developers.com/showthread.php?t=1854087
T989D
latest CM10.1 nightly
latest Uber nightly
brendyh said:
Hello all. I did make a post in the 4.2.2 thread regarding issue with CM 10.1 but still wasn't able to find a solution to this issue. My problem is after flashing from 10.0 > 10.1 (stable) it seems that the device is unable to automatically mount the internal storage and crashes. It does open after initial flashing but after rebooting the phone, internal storage goes away. After flashing again and again, the issue still occurs. I have tried reformatting the internal storage but that also seems to not work. If anyone can please help it'd be much appreciated. Thank you
Click to expand...
Click to collapse
When you say you're reformatting the internal storage, are you talking about just the "/sdcard" bit (from inside Settings while the phone's running) or full wipe (from CWM or whatever recovery you use)?
There was a known bug a few months back which caused an issue mounting the internal storage (i.e. the "/sdcard" bit) which did get fixed, but some people were saying they still had continued problems from a mount command left behind in "/data/local/userinit.sh". I saw some comments saying deleting this fixed the problem. If you're doing a full wipe (from recovery) before flashing CM, it would get rid of that file anyways.
noob41 said:
This thread seems relevant but I tried the script to see if I could tell you what mine is called but got "permission denied".
http://forum.xda-developers.com/showthread.php?t=1854087
T989D
latest CM10.1 nightly
latest Uber nightly
Click to expand...
Click to collapse
I also was unable to get the script.
GaidinBDJ said:
When you say you're reformatting the internal storage, are you talking about just the "/sdcard" bit (from inside Settings while the phone's running) or full wipe (from CWM or whatever recovery you use)?
There was a known bug a few months back which caused an issue mounting the internal storage (i.e. the "/sdcard" bit) which did get fixed, but some people were saying they still had continued problems from a mount command left behind in "/data/local/userinit.sh". I saw some comments saying deleting this fixed the problem. If you're doing a full wipe (from recovery) before flashing CM, it would get rid of that file anyways.
Click to expand...
Click to collapse
I formatted the internal storage via recovery by mounting the usb storage and formatting from there. I did try to delete the command and doing a full wipe but both did not help. Full wipe allowed the internal storage to be mounted on initial flash but after rebooting, the internal storage disappears.
Edited:
After spending the morning figuring out what went wrong I may have got it to work. For starters, I rebooted and waited 2 minutes before using my phone and found that it worked around 50% of the time for the i.s. to mount. When it failed I put in commands seen from another thread and that also worked roughly 60-75% of the time. I also deleted the actual userinit.sh and it helped along with the previous two actions. It's a hit or miss so far but as of right now, I am able to go into the internal storage.
I can't even get to my internal storage via CWM. Won't mount it, won't format... nothing. Help?
edit - figured it out.