Related
I have been at this for 16 odd hours and have overcome wifi probs, activation probs, chevvy issues.. done 3 flashes of wp7, radio updated.. all is grand now but the memory card issue!
Please, someone allow me to go to bed by explaining how I can format the card to show more than 200mb?!
I have taken the card out, formatted on my pc, reformatted with other tools, am stuck, and have spent the last hour searching through threads for info I had earlier but can no longer find! it doesnt help that any search containing "SD" is ignored as xda search sees it as too small a word.
Who wants some good Karma?
I really dont get why this topic is been creating/cloned etc on a regular basis??
Please use search function, this topic has been discussed many times.
Use some commen sense, dont look for "SD", use keywords like "WP7" and "200" or "200mb", "partition" etc. Or even reading the readme that came with the WP7 rom would be a good start
Why not help me instead of witholding what you know and making me forrage around one hell of a mess of a forum to find information I have been searching for since this afternoon????????
from the read me, and i quote "WARNING: WP7 will format the SD card during the first boot.
Two SD card partitions are created during cold boot.
First one is a 200Mb FAT partition and another one with unknown format which
is used as RAID with main memory."
That doesnt explain how to change the RAID partition into physical memory I can access from the device...
xandercom said:
I have been at this for 16 odd hours and have overcome wifi probs, activation probs, chevvy issues.. done 3 flashes of wp7, radio updated.. all is grand now but the memory card issue!
Please, someone allow me to go to bed by explaining how I can format the card to show more than 200mb?!
I have taken the card out, formatted on my pc, reformatted with other tools, am stuck, and have spent the last hour searching through threads for info I had earlier but can no longer find! it doesnt help that any search containing "SD" is ignored as xda search sees it as too small a word.
Who wants some good Karma?
Click to expand...
Click to collapse
Here is what you need to do:
Make sure your SD card is in the phone
Do a factory reset by going to settings>About>Reset your phone.
After WP7 reboots, it will recognize your card and all the date.
You will have to re-enter your Activation code.
changochulo said:
Here is what you need to do:
Make sure your SD card is in the phone
Do a factory reset by going to settings>About>Reset your phone.
After WP7 reboots, it will recognize your card and all the date.
You will have to re-enter your Activation code.
Click to expand...
Click to collapse
Thanks for the advice.
Is there any way this can be done outside of the device? I have heard that I can get an SD formatting tool but whatever one I downloaded did nothing to help.
I am reluctant to do the 4th hard reset of the day for this OS as a) there is talk of the auth code working only 3 times, and b) I have everything else working now and dont want to tempt fate!
Is it only a WP7 hard reset that will resolve this for me now?
:-(
Thanks in advance of your help my man!!
also, wont a hard reset undo all of the unlocking and such from chevvy?
xandercom said:
also, wont a hard reset undo all of the unlocking and such from chevvy?
Click to expand...
Click to collapse
Im pretty sure it will undo the unlocking, but it only takes a few minutes to go thru it again once you have everything downloaded.
Hard reset number 5 it is then!!
It didnt save my settings on the mem card, obviously as it wasnt in there in the first place during the previous hard reset.
Im becoming a master at hard resets and personalisation now!
that's not gonna help, , the first time it boots its gonna again make a 200meg partition and the rest create a raid.
download a partition program (there are loads, personally i have a ubuntu laptop and use that, you could also make an ubuntu live cd, boot to that and delete teh partition there.
through Ubuntu...
phone into magldr, usb mass storage, connect to Ubuntu, the 200meg filesystem icon will soon appear on the desktop, right click, format, instead of clicking ok click disk utility, select the 200 partition and click unmount then click delete, then select the unknown partition, and click delete.
if you are going back to android now would be a great time to set up an ext partition if you want one.
If you are sticking with wp7, then you can't format it to show more than 200meg, that's all that wp7 allocates to the fat partition, all the rest goes to system storage. Messing with the disk (even removing it whilst wp7 is running, i believe) will trash the data on the card and wp7 will reformat it.
If you are heading back to wm then create a fat32 partition the full size of the card.
samsamuel said:
that's not gonna help, , the first time it boots its gonna again make a 200meg partition and the rest create a raid.
download a partition program (there are loads, personally i have a ubuntu laptop and use that, you could also make an ubuntu live cd, boot to that and delete teh partition there.
through Ubuntu...
phone into magldr, usb mass storage, connect to Ubuntu, the 200meg filesystem icon will soon appear on the desktop, right click, format, instead of clicking ok click disk utility, select the 200 partition and click unmount then click delete, then select the unknown partition, and click delete.
if you are going back to android now would be a great time to set up an ext partition if you want one.
If you are sticking with wp7, then you can't format it to show more than 200meg, that's all that wp7 allocates to the fat partition, all the rest goes to system storage. Messing with the disk (even removing it whilst wp7 is running, i believe) will trash the data on the card and wp7 will reformat it.
If you are heading back to wm then create a fat32 partition the full size of the card.
Click to expand...
Click to collapse
Sam,
Ive already tried this and it worked for me. Im just going off my experience.
samsamuel said:
that's not gonna help, , the first time it boots its gonna again make a 200meg partition and the rest create a raid.
download a partition program (there are loads, personally i have a ubuntu laptop and use that, you could also make an ubuntu live cd, boot to that and delete teh partition there.
through Ubuntu...
phone into magldr, usb mass storage, connect to Ubuntu, the 200meg filesystem icon will soon appear on the desktop, right click, format, instead of clicking ok click disk utility, select the 200 partition and click unmount then click delete, then select the unknown partition, and click delete.
if you are going back to android now would be a great time to set up an ext partition if you want one.
If you are sticking with wp7, then you can't format it to show more than 200meg, that's all that wp7 allocates to the fat partition, all the rest goes to system storage. Messing with the disk (even removing it whilst wp7 is running, i believe) will trash the data on the card and wp7 will reformat it.
If you are heading back to wm then create a fat32 partition the full size of the card.
Click to expand...
Click to collapse
Actually, it has done the trick, however now I am back to having a locked device again and cant deploy apps from my pc. Back to where I was 6 hours ago.
All I want is space to store more than 4 apps before the dang thing runs out of space.
Time to grab a beer me thinks.
I put WP 7 on my HD2 and it was working fine but I decided to go back to Android. I then took my 16 GB Sandisk card out and put it in the memory card reader but it only shows the partition of 200 MB.
I even download a program to format/partition the microSD card but I still could not get it to get back most of the available space in my 16 GB card. It keeps showing 200 MB on my computer and I tried to get rid of the partitioning but I still cannot do it.
Is there a solution to this?
sounds like your memory card is corrupted :/
Try
http://www.sdcard.org/consumers/formatter/eula/
If that doesn't fix it, it may be borked completely.. though some people have had success with the Nokia phone formatting tools
Easy,
Put your SD Card in your PHone
POwer off you phone
During Boot hold power off/on button on phone to access the MAGDLR Menu
Connect you Phone to PC
Choose MASSSTORAGE in MAGDRL Option number 4
Format your SD CARD over PC
Power off Phone - Job done!
i had the same problem, the way the i fix it was the i format the sd card in my blackberry and it works for me i try it in a samsung and fix the problem. the computer wasnt able to fix problem i used the format method from the computer. didnt work, and i used paragon software didnt work either. the only way was with different phone
I don't know why everybody thinks you have to put the card into something else. Enter MAGLDR, go to USB, connect it to the computer, run SD Formatter,Select correct drive, Options - Format Type= Full Erase On -Format Size Adjustment =ON.
This has been covered many times since the introduction of WP7. Using the search term 200mb in this section. I came up with plenty of answers to your problem.
Wil Badger said:
I don't know why everybody thinks you have to put the card into something else. Enter MAGLDR, go to USB, connect it to the computer, run SD Formatter,Select correct drive, Options - Format Type= Full Erase On -Format Size Adjustment =ON.
This has been covered many times since the introduction of WP7. Using the search term 200mb in this section. I came up with plenty of answers to your problem.
Click to expand...
Click to collapse
Thank you. I followed you instructions and I got my SD card back to 14.8 GB now.
Wil Badger said:
I don't know why everybody thinks you have to put the card into something else. Enter MAGLDR, go to USB, connect it to the computer, run SD Formatter,Select correct drive, Options - Format Type= Full Erase On -Format Size Adjustment =ON.
This has been covered many times since the introduction of WP7. Using the search term 200mb in this section. I came up with plenty of answers to your problem.
Click to expand...
Click to collapse
yesss! this finally did the trick!! i've tried different way recommended by different people but this was the only one that actually worked!!!
When I try to turn my phone on, it will not get passed the ROM loading screen (Energy blue logo). This is because the internal memory is full.
I really need to get into the file system to delete a file (and fix the problem) or copy certain stuff out - it has pictures of my fiance on to say the least, and I really want them.
But, as Windows won't boot I can't do this in the traditional way. Obviously I can still get into bootloader - so is there a way I can access the file system? A bit of software I can run on my laptop that can somehow access the file system through bootloader mode? All I need to do is identify a c.1mb file and delete it...
The background to all this is the phone was displaying messages about 'memory nearly full' - but it had done this before and just stopped, so I left it again. Except, at some point signal reception dropped and stayed at 0. So I rebooted, and got stuck at the loading screen - which is where we've been for the last few days now.
I really hope someone can help. If you can, I'll buy you a few beers.
Thanks,
David
Phone was running WM6.5 with HSPL (3 I'm fairly sure)
How in the hell did you manage to fill your internal memory up, why not just use a SD card for storage?
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
I think I took too many photos! Though I'm not exactly sure tbh... Some bug in the ROM kept changing the save dir from SD card to internal, but I did keep an eye on the space, perhaps just a few too many photos in one night...
Anyway ActiveSync isn't working (for me at least) in bootloader mode - don't I need to have Windows Mobile loaded?
Should activesync work in bootloader mode?
TheATHEiST said:
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
Click to expand...
Click to collapse
doesnt work. you cant access the live file system from anywhere except within running wm.
You can dump off the rom partition into .raw files, but when you rebuilt it (in a ktchen) you would still only end up with the original rom as it was out of the box, no user data.
@OP, you could possibly go into bootloader, confirm 2.08.hspl, flash magldr, and then boot from an sd android, though i suspect you still wouldn't see the winmo files. (I assume there are now android builds that can be booted to and run from sd without the need for haret/winmo? i'm a nand man meself so unsure. )
It's what i'd try if it really was that critical, otherwise I'd weep for a little while, kick myself and write 'backup' post-its all over my office, then hard reset and move on.
Thanks for the advice - I will definitely try your suggestion before 'moving on', losing a whole bunch of contacts will also be a real pain.
Do you know of any threads/links explaining magldr and how it will help?
Is there no other way to access any part of the internal memory and just delete 1 file?
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Thanks
Bear in mind WP7 and winmo are two very different OSes.
WP7 has been out btw.
Once you flash the device, with MAGLDR, android or WP7, the internal storage is wiped so it makes no sense to flash it if you still want what is in it.
davenash said:
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
Click to expand...
Click to collapse
any type of flashing (nandroid, wp7 or wm) will destroy whats on there already, thus defeating the object.
There are more than two options in magldr, one of which is 'boot sd ad' for boot sd card android.
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Click to expand...
Click to collapse
its probably not an issue of the file system type, android (linux) can access fat partitions no problem. Its probably more to do with whether the sd builds can mount the internal rom or not.
Im no linux head at all, still fumbling in the dark though, so i could be wrong.
Hi,
I think I didn't post too often here but now I need your help.
I also did some searching first but in threads like http://forum.xda-developers.com/showthread.php?t=1143949 I did not finy a good solution, yet.
I am owning a HD2 and used CoreDroid 1.6 till yesterday. I connected my phone via USB to my computer to load it and left office. When I came back, I noticed my phone was still on. I touched it but nothing happened. The surface was frozen. Not even the off-button showed any effect. Thus, I removed the battery, waited a bit and inserted it again.
Unfortunately the phone did not boot any more. Just hangs at the first "Coredroid Screen". I tested around and when I removed the SD card and rebooted again, it worked. I checked the card and it had some file system problems. Thus, I saved all data and formatted it. However, my HD2 did not boot also with any of the other SD cards I tested (no difference how it is formatted). The system starts booting from NANE and shows the first CoreDroid screen and then just angs.
Then I noticed, that it said after booting "internal memory is full" (I checked it: 0 kb free). I searched for the reason and I found in the internal memory root a folder /bin. Observing it I saw, that nearly ALL executables have a size of 1.5 MB. I am talking about the executables that usually have some few kB.
In panic mode, I used Task29 to completely clear NAND. Then I installed MAGLDR and the appropriate CWM for CoreDroid. I downloaded the newer version 1.7 and flashed it. Same result. Did not boot with SD card but without it worked. However, I had that strange /bin folder with only 1.5MB files. Then I used MAGLDR to clean the system partition again and installed 1.6 again but same problem. I also used not the CWM provided by CoreDroid but also the "generic" downloadable and changed settings accordingly. Same effect. I even tried a CWM with 400 MB system partition instead the proposed 390 MB but same effect. 0 Bytes free. I also tried the latest Hyperdroid and Cyanogen ROMs with the same effect.
So I wonder if there is some tool for "checking" the internal memory for possible problems? Resetting it with Task29 did not bring any benefit.
Hope someone can give me a hint what I would do in this case.
I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.
If you were able to boot magldr and reflash roms and install cwms, I think your internal memory should be fine.
Try flashing some other rom, preferably with no sense. I'd say hyperdroid, i remember it as quick and light.
It might be problem with your phone SD card reader hardware...
samsamuel said:
I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.
Click to expand...
Click to collapse
Thanks for your answers.
The strange thing is: it does not boot if ANY SD-card is inside. If I remove the SD-card, it at least boots. In other words: it boots as long as there is NO SD-card at all.
I must admin I prefer Coredroid since I think it supports many nice features like all the options when connecting it via USB cable (going online over computer connection, usb tethering, etc). However, on the weekend I try flashing again some other roms to check. Still I would like to check what is going on :/
Yeah, I believe you.
Just hope it's not a hardware problem...
phone model : I9000
Original condition : was working ok but doesn't read internal or external memory
Present condition : phone doesn't boot , always black screen Look here
Original firmware: unknown " for sure it was froyo 2.2 "
i've tried to flash it with lots of firmwares with Odin and no luck
can someone plz help me
thanks alot
Is download mode working ?
Hi,
If you've flashed with ODIN I'm assuming you've tried to get into download mode and that still works - but whatever ROM you flash, you get stuck at the black screen after the Samsung Logo and the Samsung animation.
How do you know it doesn't read from the SD memory?
Can you try mounting the SD memory from inside CWM and try reading? (Bear in mind some CWM version do not support mounting SD memory for USB reading)
i had the same problem as you on 2.2.1, just install new firmware and everything will be ok.
To Enter Recovery Mode:
Switch your phone off. Wait until vibrate
Now Press and HOLD the following Keys in the same order: First Volume UP, Second Home Key, and Lastly The Power Button.
Keep the Buttons Held until you see the phone Light up, then Let go off the power button, but keep the Volume and Home Keys Pressed.
Once you see a menu with the caption Recovery Mode on the Top let go of all the buttons.
after hard reset everything will work fine, after that install new firware with odin or kies (since you are on 2.2)
jayeshup said:
Is download mode working ?
Click to expand...
Click to collapse
yes phone still can enter Download mode and recovery mode
torrentship said:
Hi,
If you've flashed with ODIN I'm assuming you've tried to get into download mode and that still works - but whatever ROM you flash, you get stuck at the black screen after the Samsung Logo and the Samsung animation.
How do you know it doesn't read from the SD memory?
Can you try mounting the SD memory from inside CWM and try reading? (Bear in mind some CWM version do not support mounting SD memory for USB reading)
Click to expand...
Click to collapse
the phone was working when it came to me and it reads internal memory 0.0 and external SD memory didn't read it at all .
i guess you mean by CWM is to use clock work mod , the phone now doesn't boot to cwm recovery mode , it boots to samsung recovery mode only and download mode .
milets said:
i had the same problem as you on 2.2.1, just install new firmware and everything will be ok.
To Enter Recovery Mode:
Switch your phone off. Wait until vibrate
Now Press and HOLD the following Keys in the same order: First Volume UP, Second Home Key, and Lastly The Power Button.
Keep the Buttons Held until you see the phone Light up, then Let go off the power button, but keep the Volume and Home Keys Pressed.
Once you see a menu with the caption Recovery Mode on the Top let go of all the buttons.
after hard reset everything will work fine, after that install new firware with odin or kies (since you are on 2.2)
Click to expand...
Click to collapse
mate i tried to flash the phone with many files like 2.1 , 2.2 , 2.2.1 , 2.3 , 2.3.3 , 2.3.5 , 2.3.6
but always same result , the thing is that the phone was working before i flash it the first time ,
thank you all for help and plz share with me a solution
wbr
Have you tried flash phone with full (3 part) rom + pit file?
Firstly, I think ke_be's suggestion is spot on; give that a try.
But,
the phone was working when it came to me and it reads internal memory 0.0 and external SD memory didn't read it at all .
Click to expand...
Click to collapse
I'm not sure how to read this - do you mean the external SD memory (which to avoid confusion is the SD card that you can put into the phone physically rather than the internal partition called sd_ext) was not readable from the beginning?
Also - does ODIN give any warnings at all or does it always say "Success!" and then reboot?
Becuase it sounds like it thinks it's flashing the image properly but in fact it is not which could very well be symptomatic of memory read/write problems.
(It's difficult to tell without DMESG!)
torrentship said:
Firstly, I think ke_be's suggestion is spot on; give that a try.
But,
I'm not sure how to read this - do you mean the external SD memory (which to avoid confusion is the SD card that you can put into the phone physically rather than the internal partition called sd_ext) was not readable from the beginning?
Also - does ODIN give any warnings at all or does it always say "Success!" and then reboot?
Becuase it sounds like it thinks it's flashing the image properly but in fact it is not which could very well be symptomatic of memory read/write problems.
(It's difficult to tell without DMESG!)
Click to expand...
Click to collapse
i've tried kebe's and flashed many many flashes 3 parts + PIT file same result
what i meant is the external SD memory which i insert in phone under the battery cover , this one the phone does not recognise at all , also the internal partition which is originally comes inside phone from samsung also was not readable , when i go to setting storage it was 0.0 MB , or something like that .
Odin does not give any errors and always it success flashing and reboot
and what is DMESG! ?
thank you for your help
Hi there,
Ok - well I think that as the phone couldn't read the Internal or External SD memory when you got it that despite it appearing to be semi-functional, it was essentially broken!
The internal SD memory was clearly able to be read as the kernel and android is stored on it (the /system directory for example). So the question is - why were the SD_EXT directory and the external SD directory not readable and indeed do these issues have a bearing on the inability to start the phone!
Well.. both sd_Ext and external_sd are using the VFAT filesystem which is different from the rest of the mountpoints which use RFS or EXT or the like. (It's so Windoze can access it) So I wonder if somehow the driver that accessed that has a problem.. though there's not much we can do about that..
Also - when a new ROM is flashed, it doesn't actually do much with sd_ext an external_sd so that's also curious... I'm wondering if there is a "write" error on the phone's memory interface.
So - to check that - find a rom which has CWM and USB Mounting working in it (most GB roms have this) and flash it using ODIN but do not boot into it. Instead, try to get into CWM and then mount the USB storage from the Mounts menu option and try to write a file to it.
Indeed, if you are able to flash a new kernel or bootloader that implies it does NOT have a memory write problem! But it serves a purpose becuase it'll be useful having CWM on there rather than the Samsung recovery menu.
Essay over!
BTW DMESG is a little linux prog which displays the kernel output - it would probably show us some info about what's stopping the boot but I don't know how to view it prior to a ROM successfully booting - if someone does that'd help a lot.
torrentship said:
Hi there,
Ok - well I think that as the phone couldn't read the Internal or External SD memory when you got it that despite it appearing to be semi-functional, it was essentially broken!
The internal SD memory was clearly able to be read as the kernel and android is stored on it (the /system directory for example). So the question is - why were the SD_EXT directory and the external SD directory not readable and indeed do these issues have a bearing on the inability to start the phone!
Well.. both sd_Ext and external_sd are using the VFAT filesystem which is different from the rest of the mountpoints which use RFS or EXT or the like. (It's so Windoze can access it) So I wonder if somehow the driver that accessed that has a problem.. though there's not much we can do about that..
Also - when a new ROM is flashed, it doesn't actually do much with sd_ext an external_sd so that's also curious... I'm wondering if there is a "write" error on the phone's memory interface.
So - to check that - find a rom which has CWM and USB Mounting working in it (most GB roms have this) and flash it using ODIN but do not boot into it. Instead, try to get into CWM and then mount the USB storage from the Mounts menu option and try to write a file to it.
Indeed, if you are able to flash a new kernel or bootloader that implies it does NOT have a memory write problem! But it serves a purpose becuase it'll be useful having CWM on there rather than the Samsung recovery menu.
Essay over!
BTW DMESG is a little linux prog which displays the kernel output - it would probably show us some info about what's stopping the boot but I don't know how to view it prior to a ROM successfully booting - if someone does that'd help a lot.
Click to expand...
Click to collapse
wow , dude seriously thank you for your effort ,
i dont know much in linux and also on samsung hardware and software ways ,
but i love the idea you said about CWM rom ,
so what is that GB roms ? and where to find them ? noob questions i know , but i really i'm new to samsung android stuff .
with best regards,
Ok not to worry.
To test if you have CWM (clockworkmod) :
Turn off your phone
Hold down the UP volume button and the HOME button on your phone
Now, whilst keeping those two buttons held down, turn on the phone.
When you see the Samsung logo on there, you can release all the buttons.
If it says "2e" or "3e" recovery - you DO NOT have CWM so you'll need to get it. Otherwise you do have it - let me know.
If you don't have it:
Use this link to Ramad's Firmware Collection to get yourself a copy of the ODIN package for JVT (imo the best GB rom) and flash it to your phone (using ODIN!).
Then you should have ClockworkMod installed.
Let me know how you get on / any questions.