Related
So, I got a 4GB sdcard the other day. It came out of a blackberry a friend of mine was using. I formatted the card to FAT32 with the utility in windows 7, and everything seemed to be fine. I downloaded ext2fsd to be able to copy my ext partition to my new card. I followed the directions from the website about mounting the ext partition.
After I performed the steps above, my sdcard became unusable. I tried to take it out, and put it back in my card reader, and I get an error saying windows needs to format the drive, if I try to format it, it doesn't work. I've tried in gparted as well, and also get an error. I even tried from Amon's revorery, and sdparted in the console. I don't get errors with the latter two, but my card reader still says it's RAW.
I know that was lengthy, but I'm trying to figure out anymore steps to take, or if I should just throw the card away.
Thanks
ok..
wow.
You have to have 3 partitons. If you only format it with 1 partiton, you cant save data on a partition that doesnt exsist.
You have to go to recovery console and make a fat32, ext3 and linux swap partion.
I dont have the patience to go trhough it all with you because its in 100 different threads so .. use search?
Not trying to be rude, but this is stuff you can fin don your own here very easily if you werent expecting someone to do it for you
EDIT-- sorry, dont think i read fully what you did. I had this same thing happen today on a friends brand new 8gb.
HEres what I did since you have Amen ras recovery..
Format to just FAT32.
Turn on usb
give it a second to pop up and it will and check the size.
Then turn off the usb, go into parted on console, rm 1, then remake all 3 partitons according to the size of the card.
I suggest not using the full partiton in the recovery because it usualy screws up the swap.
From there you will be fine.
If it doesnt work that way, then im sorry, the card may be pooped or to low a class maybe?
crypysmoker said:
ok..
wow.
You have to have 3 partitons. If you only format it with 1 partiton, you cant save data on a partition that doesnt exsist.
You have to go to recovery console and make a fat32, ext3 and linux swap partion.
I dont have the patience to go trhough it all with you because its in 100 different threads so .. use search?
Not trying to be rude, but this is stuff you can fin don your own here very easily if you werent expecting someone to do it for you
EDIT-- sorry, dont think i read fully what you did. I had this same thing happen today on a friends brand new 8gb.
HEres what I did since you have Amen ras recovery..
Format to just FAT32.
Turn on usb
give it a second to pop up and it will and check the size.
Then turn off the usb, go into parted on console, rm 1, then remake all 3 partitons according to the size of the card.
I suggest not using the full partiton in the recovery because it usualy screws up the swap.
From there you will be fine.
If it doesnt work that way, then im sorry, the card may be pooped or to low a class maybe?
Click to expand...
Click to collapse
Yeah, I know you're not trying to be rude, but I know I need 3 partitions. I'm pretty aware of the way a sd card needs to be partitioned. I've tried everything mentioned. I think it's about time to call it quits. It's a class 2 card, so I don't think that's the issue, and I can't format in Ubuntu, or Windows. Oh well I suppose. Thanks.
You can try this app. Its called Sd formatter...it reformats the SD. IT worked for me.
http://panasonic.jp/support/global/cs/sd/download/sd_formatter.html
cholito said:
You can try this app. Its called Sd formatter...it reformats the SD. IT worked for me.
http://panasonic.jp/support/global/cs/sd/download/sd_formatter.html
Click to expand...
Click to collapse
I forgot to include this in the original list of things I tried, but I did give it a go. It is telling me the card is write-protected even though the switch on the adapter is set to the unlocked position. I've also tried it with a different adapter. I appreciate everybody's input.
well try using parted commands to write from block 0 to the last block and partition the whole thing as fat32
is that not working?
did you tried partitioning with RA 1.2.3 recovery?
@B-man007
I haven't tried writing the whole thing to FAT32 with parted. I'll give that a try tonight (don't have the card with me).
@cholito
I'm using RA 1.2.2, I think the script is the same, so I don't know that it would make a difference if I was using that or 1.2.3
I just got a new 8 gb microSD card, from ebay and no matter HOW HARD I TRY, using every friggen method in the book, it won't partition properly, and when i finally do get it to partition, it keeps being read by my phone as a blank SD card, but the phone won't format it.
I have tried to using, Paragon Partition Manager, as well as SDpart on Amon_RA's recovery. Both tell me that it has been partitioned correctly, however sometimes on SDpart, it just partitions forever.
The SD card I use is this one: http://cgi.ebay.ca/NEW-8G-8GB-TF-Mi...gital_Camera_Memory_Cards?hash=item3ca7f3ab6b
which to my knowledge should work....unless i'm REALLY clueless and i just missed something really obvious, any help at all would be nice...if you need ne more infor to help, please ask.
bgmrk said:
I just got a new 8 gb microSD card, from ebay and no matter HOW HARD I TRY, using every friggen method in the book, it won't partition properly, and when i finally do get it to partition, it keeps being read by my phone as a blank SD card, but the phone won't format it.
I have tried to using, Paragon Partition Manager, as well as SDpart on Amon_RA's recovery. Both tell me that it has been partitioned correctly, however sometimes on SDpart, it just partitions forever.
The SD card I use is this one: http://cgi.ebay.ca/NEW-8G-8GB-TF-Mi...gital_Camera_Memory_Cards?hash=item3ca7f3ab6b
which to my knowledge should work....unless i'm REALLY clueless and i just missed something really obvious, any help at all would be nice...if you need ne more infor to help, please ask.
Click to expand...
Click to collapse
you might wanna try ubuntu
I was hoping not to have to do that, but looks like i'll give it a try.
EDIT:
After installing ubuntu and partioning the card...what i think was successful (no errors) and the phone reads it fine, however it can't read the amount of storage on the SD secondary drive. And when I copy over a rom to reflash, at the recovery screen it gives me an error saying it's (bad). And then when i look at the ROM file, the size is down to 0kb, from the original 38 mb. I also can't download any updates using CM updater, it starts...and then freezes and gives me an error...this happens on NO MATTER what ROM, and i've tried both Amon_RA's and cyn's recovery. Both give the same error. Any help is welcome.
hmm i had a similar problem before. if you went into parted from the console and print, what does your "Partition Table" say?
Hi all,
A couple of days ago i decided to give my phone a completely fresh start, looking back i wish i never did. Here's my problem:
As soon as i create any ext partition on my SD card the phone will not boot past the splash screen. When i remove the partition all is well but i really love APPS2SD so this is not an option for me.
Here's some more info on my setup;
ADP1 (PVT 32B ENG S-OFF)
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Running the latest cyanogen's recovery
Here's what i already tried (i know its a long read but please hang in there);
I formatted the SD card using a HTC Magic (as stated on cyanogens wiki that formatting on android 1.6 is preferred). Put signed-dream_devphone_userdebug-ota-14721.zip and update-cm-4.2.13-signed.zip on the SD and followed instruction to flash both in correct sequence. This works flawlessly, booting up with no issues at all. I then turned the phone off and put the microSD in my PC.
I then proceeded to shrink the FAT32 partition (Ubuntu GParted) to make room for the ext partition but not created this partition just yet for testing purposes. Put the SD card back in the phone and i boots up like a dream (no pun intended) running smooth as ever so the shrunk partition is still working great! Once again turned the phone off and put the SD back in my PC to create the ext partition and that's where the problems begin; as soon as ANY ext partition is present (i tried ext2, ext3 and ext4) the phone will not get past the splash screen!!
As soon as i remove this ext partition all works great once again! So then i figured i'd probably have to flash everything from scratch with the ext partition present but this gives me the same results every single time with ext2/3/4 partition present. I even gave Amon-RA's recovery a try with this same process, and even tried to create the partitions using that. No luck, same results every single time.
Now in the past i always used APPS2SD with a ext2 partition without any problems but now i am unable to just get it back to work!
I have a feeling that something goes all messed up somewhere in creating the ext partition but i just cant put my finger on it where, i've ben on this for 3 days now so any input would be very much appreciated!
maarten82 said:
Hi all,
A couple of days ago i decided to give my phone a completely fresh start, looking back i wish i never did. Here's my problem:
As soon as i create any ext partition on my SD card the phone will not boot past the splash screen. When i remove the partition all is well but i really love APPS2SD so this is not an option for me.
Here's some more info on my setup;
ADP1 (PVT 32B ENG S-OFF)
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Running the latest cyanogen's recovery
Here's what i already tried (i know its a long read but please hang in there);
I formatted the SD card using a HTC Magic (as stated on cyanogens wiki that formatting on android 1.6 is preferred). Put signed-dream_devphone_userdebug-ota-14721.zip and update-cm-4.2.13-signed.zip on the SD and followed instruction to flash both in correct sequence. This works flawlessly, booting up with no issues at all. I then turned the phone off and put the microSD in my PC.
I then proceeded to shrink the FAT32 partition (Ubuntu GParted) to make room for the ext partition but not created this partition just yet for testing purposes. Put the SD card back in the phone and i boots up like a dream (no pun intended) running smooth as ever so the shrunk partition is still working great! Once again turned the phone off and put the SD back in my PC to create the ext partition and that's where the problems begin; as soon as ANY ext partition is present (i tried ext2, ext3 and ext4) the phone will not get past the splash screen!!
As soon as i remove this ext partition all works great once again! So then i figured i'd probably have to flash everything from scratch with the ext partition present but this gives me the same results every single time with ext2/3/4 partition present. I even gave Amon-RA's recovery a try with this same process, and even tried to create the partitions using that. No luck, same results every single time.
Now in the past i always used APPS2SD with a ext2 partition without any problems but now i am unable to just get it back to work!
I have a feeling that something goes all messed up somewhere in creating the ext partition but i just cant put my finger on it where, i've ben on this for 3 days now so any input would be very much appreciated!
Click to expand...
Click to collapse
Your sd could be going bad.
Which version of Amon_Ra are you using?Try repartitioning your sdcard and try another rom like Super-D thats much faster and see where that gets you.
Ace42 said:
Your sd could be going bad.
Which version of Amon_Ra are you using?Try repartitioning your sdcard and try another rom like Super-D thats much faster and see where that gets you.
Click to expand...
Click to collapse
Thank you for the very fast reply!
I'ver tried repartitioning multiple times with different partition sizes and i used the latest of Amon_RA's work (dream v1.5.2).
I will give Super-D a try just for kicks..
And before i forget, i also tried flashing with the defanged DRC83 base and older versions of cyanogens just to make sure without any luck. I also always double-check the MD5sums on all the files that get on my phone!
Ace42 said:
Your sd could be going bad.
Click to expand...
Click to collapse
Well my friend, your first hunch appears to be correct! I've done some small experiments with the card - copying large files back/forth and checking integrity - and it appears that the card is indeed messed up! That's just one of those things i never seem to come up with myself!
I just came back from the store to buy a new cheap card, and even tho its only a class 2 everything formatted and installed without any problems including the APPS2SD! So i guess ill have to order myself a new card, bummer those things only last a year and a half as it appears, i guess ill just have to keep the receipt and get myself a new one under warranty every now and then......
Thanks a million for pointing me in the right direction!
maarten82 said:
Well my friend, your first hunch appears to be correct! I've done some small experiments with the card - copying large files back/forth and checking integrity - and it appears that the card is indeed messed up! That's just one of those things i never seem to come up with myself!
I just came back from the store to buy a new cheap card, and even tho its only a class 2 everything formatted and installed without any problems including the APPS2SD! So i guess ill have to order myself a new card, bummer those things only last a year and a half as it appears, i guess ill just have to keep the receipt and get myself a new one under warranty every now and then......
Thanks a million for pointing me in the right direction!
Click to expand...
Click to collapse
I had that happen to my 8Gb, had it for about a year i think.
did you use 1.6 or did you format from Amon? Also, is i possible not to load "signed-dream_devphone_userdebug-ota-14721.zip". And just go download everything again from the market? Someone said I don't need that file? Where they trying to brick me?
surfereddie said:
did you use 1.6 or did you format from Amon? Also, is i possible not to load "signed-dream_devphone_userdebug-ota-14721.zip". And just go download everything again from the market? Someone said I don't need that file? Where they trying to brick me?
Click to expand...
Click to collapse
I just formatted the card in a cardreader using Gparted, a FAT32 partition for the whole size of the card minus space for the EXT and swap partition (in my case 512+32Mb resp.). Don't know if it is mandatory but i also flagged the FAT32 boot and lba and it works brilliant for me!
I indeed used the devphone OTA update, but only do this is you have a ADP1... I guess you could probably mess up a normal G1 with that rom. Just follow instructions! Pick the correct 1.6 base rom for your phone (either defanged or the devphone version), flash it and without a reboot flash the latest cyanogens rom over the base, its all explained quite idiot-proof on cyanogens wiki.
I recently tried to flash Fresh Toast 2.1 and after 15+minutes my phone was stuck in a bootloop. I rebooted to recovery and deleted all the data and cache. Now no matter what ROM i try to flash it just keeps booting over and over. Anyone have any ideas? I was using apps2sd and completely formatted the sdcard, would this have affected anything? Also tried nandroid back up, but says "No files found" when I try to do so. Also when i try to format the sd:ext i get an error mounting sd:ext
In recovery try and format your sdcard with only a fat32 partition. Then try and enable ?MS-USB? and copy a ROM to your sdcard.Wipe data and dalvik and then flash ROM.
If that doesn't work try replacing your sdcard with another one.
Or you can push your ROM.zip to the sdcad through adb without mounting the sdcard
A2SD will only work if your sdcard is partition with EXT and swap. So if you don't have it partitioned then apps will install on your phone.
I gave it a shot but no luck, i am using the clockworkmod recovery 1.8.1.4.
I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...
27midwest1 said:
I had the same issue happen the other day after a wipe and reinstalled rom... I have the same clock work mod you have also... what I noticed was that my phone only did that when I had the sd card in but once I removed it (after several hours of flipping out over it!) it booted fully.. but every time in reinserted the card, it rebooted.. so what I did was used paragon partition manager to create 3 partitions on the sdcard (i have an 8gb card) and made 2 Linux ext2 partition of 258mb or something close to it and the remaining was formatted at Fat32.. after I did this, I re-flashed my rom and everything has been working fine ever since... it may have been some corrupted files in the 2 Linux partition or something because I was running all my apps from the sd card and I had noticed the other day that every time I connected my hero to my laptop via usb, and launched pdanet, my phone rebooted...EVERYTIME.. and this is what led me down this road... If I made any mistakes here, I'm sure someone will correct me, as this is my first post...
Click to expand...
Click to collapse
Would you mind posting the steps to do that? Im pretty computer savvy but I need some steps to go from. Would I be better off picking up a new SD?
pulled the SD and it booted, thank god lol. Thanks for your help guys!
no problem... glad I could help.. as for the new sd card, you could very well just get another, but I managed to keep the one that I had but just reformatting it and re-flashing my rom (Damage Control v2.08.1) and it's been working fine since then..
Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?
I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc
nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved
thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S
nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?
jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..