I was running fine on CM7 like I have been for months now and I go to use my phone and its frozen. I can turn the display on and off but everything else is frozen. I try to reboot and it won't boot up past the kernel screen. So I decided to try to flash back to stock and now my external and internal SD cards won't mount. I can boot up my phone on stock JF6 but cannot access either SD card. And it would only boot up when I had my external card in the phone. I have never had this problem and I did nothing to change anything that I've been running for months.
Is my phone screwed and semi-bricked?? I will be pissed if it is when I didn't even do anything to it. Its well past the time to get a warranty replacement since I've had this phone since last August. I've flashed 100s of times and never had any problems and now I don't do anything and its screwed up. Please someone give me some good news.
All these views and no one can help? Im thinking I'm screwed. I'm within 6 months of an upgrade so I think I could get them to allow me to upgrade if they don't replace my phone.
Have you reformatted the external SD (in a computer, outside of the phone)? Does ADB see your device when connected?
I can get to download mode and recovery,but cant flash cwm recovery since it cant find either sd cards. My pc sees my phone, I can flash with odin but it doesnt do any good. I cant see the sd cards on the pc though, can just see it in odin. Havent tried adb yet.
What program did you use to flash back to stock?
If it was Odin, I believe that there is an option (in the full version of Odin) to repartition. It might be worthwhile to see if you can find a package that will make use of that reparitioning option, and give that a whirl to see if it fixes your file system.
You could also do it with the latest Heimdall (1.3.1, I believe), but I'd recommend asking Benjamin Dobell (the person who made it - here on XDA) about using it for repartitioning.
I used odin one click which repartitions. I've used it tons of times and I dont think its the problem since it was screwing up when I still had cm7
You said Odin can see your SD cards. If you take your external SD, put it in an adapter, and stick it in your computer (assuming you have the tools for this, of course), does the computer recognize it? If so, is the size of the card read correctly, and what format does it recognize the card as?
The card reads fine. My main concern is my internal as well. Neither one of them are recognized by the phone. Says something like incorrect mounting points. In settings, the option to format/mount are grayed out and in total space it says unavailable for both. The external reads fine on my wife's phone, so its definitely something hardware on the phone. I just don't understand how it could all of a sudden break with me not changing anything.
jjtitus098 said:
The card reads fine. My main concern is my internal as well. Neither one of them are recognized by the phone. Says something like incorrect mounting points. In settings, the option to format/mount are grayed out and in total space it says unavailable for both. The external reads fine on my wife's phone, so its definitely something hardware on the phone. I just don't understand how it could all of a sudden break with me not changing anything.
Click to expand...
Click to collapse
If you can use ADB on the phone, you could try using the ADB shell and seeing if you can pull/check the /etc/void.fstab. It might give you a clue as to why Android is running but not seeing your internal or external SD.
For reference, mine says:
## void configuration file for the emulator/SDK
volume_sdcard (
## This is the direct uevent device path to the SD slot on the device
emu_media_path /devices/platform/goldfish_mmc.0/mmc_hst/mmc0
media_type mmc
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun0
)
Well, can't get adb to work. Surprisingly, I don't really know how. I've never needed it in the year and a half that I've had the phone. Luckily, I called Samsung and they said my phone is still under warranty since I've had to get a replacement once before. So ill be taking my phone to the at&t repair store and see what phone I can get out of them.
Related
It happened yesterday when I upgraded to xrom. I have formatted and repartitioned my sd card. Nothing is working. When I connect my sd card to my computer I noticed a lot of weird files were being stored on it. They reappear every time I delete them.
My phone is creating files like this "qxdm_20090910_184004_3.dm" (32 megs!)
hmm....very interesting... reboot into recovery and repair the ext files? it might work. most likely not, but its worth a shot.
I though about trying that but I don't have cyanogens recovery .
Mine just did the "sd card has been removed" thing half an hour ago.
I just copied a new theme .zip to my sdcard and then rebooted into recovery.
I could not apply the update since it could not mount the mmcblk0p1 partition. When boot all the way up to android i get the icon saying that the sdcard has been removed.
i just did an adb push of a file to my /sdcard from the recovery console and it returned no errors...but i cannot see any files on the card.
wtf.
Any ideas?
Yeah my problems still not fixed. I have searched the XDA, forums, Google, none have offered any solution. I have found a lot of people with this same problem.
are you using swapper? if you dont turn it off, this could happen.
i would recommend getting cyans recovery image, it has a lot of tools to debug.
get a live cd of linux/gparted and see if you can see all your partitions. if not, your sd card is most likely dead. try reformatting. if that doesnt help, you may need to get a new card.
if it does show up on your pc, but doesnt work on your phone, then post here again
Have the same problem. Got it right after updating cyanogenmod 4.1.2 I've also been looking for answers and I think I'm just gonna get a new one
I have never used swap. I tried installing cyans recovery image through terminal but it can't find my sd card. I can still update my rom through jfs utility. My sd card works perfectly fine on my computer.
Something like this happened to me a while ago. It first said Sdcard was damaged and i couldnt access it via any file manager. I rebooted and turned out all my apps went up in the air and dissapeared and my fat32 partition was gone to. i reccomend backing up your sdcard and reformatting your card then go froom there
I have already tried all that. Nothing so far has worked :-(. Man this is horrible. I can't even take pictures!
Hi all
I rooted my phone today. I then installed clockworkmod and saved a stock backup. Following that, I successfully enabled 3 button recovery.
My problem appeared either after rooting or after clockworkmod. The problem was there prior to enabling 3 button recovery. I suspect it was clockworkmod that caused the problem.
Anyway, when I connect the phone to the computer the 16gb internal sd card & 2gb phone storage appear as removable drives in 'my computer'. However, double clicking on the drives gives the message 'no disk in the drive, please insert one'. Windows can't read the usable file space, browse or even format the drives.
However, I can browse the internal sd card fine using any android file manager.
Also, I can use adb to push/pull files.
What is going on?
I need to know quite quickly what to do. I initiated a phone repair with my carrier due to the mtp crash bug, so they are expecting it to be returned pronto. If the phone is stuffed, I'll send it back. If this can be fixed, I'll keep it since I managed to get the three button recovery working.
Also, I think there's a boot rom or something to do with clockworkmod still installed? How do I get rid of that if I'm sending the phone back. I know how to unroot.
Edit: I just found an external sd card to test. I formatted it in windows by using a sd card reader, then when I plugged it into the phone and tried it as a mass storage device windows didnt like it. Putting it back into the card reader one last time and windows recognised it. Makes no sense....
Edit2: In kies mode, kies can access it. And also it adds a 'galaxy s' to my computer where the internal sd card actually works... now I'm even more confused!
Have you tryed formatting your internal Sd or useing recovery 2e and factory resetting your phone?
I've tried formatting it and reset via settings->privacy->factory reset data.
Is 3 button recovery any different to the above type of reset? What will it roll the system back to?
(The recovery image I made in rom manager will have the same problem. I dont currently have an update.zip on my sd card due to formatting it, but I can get one on there using adb if I need to.)
quitestuck said:
I've tried formatting it and reset via settings->privacy->factory reset data.
Is 3 button recovery any different to the above type of reset? What will it roll the system back to?
(The recovery image I made in rom manager will have the same problem. I dont currently have an update.zip on my sd card due to formatting it, but I can get one on there using adb if I need to.)
Click to expand...
Click to collapse
Is your usb debugging on by chance? If so, turn it off ans reconnect the phone to the pc.
Mine does this when usb debugging is on and im on a stock eclair rom... Hope it helps...
Sent from my GT-I9000M using XDA App
That thought occurred to me too. Definately off. Ive checked it many many times now
When I first used adb, I simply pulled the plug out. I couldn't see any 'quit debug' command. There are start/kill server commands, they dont seem appropriate. Doesnt look like I should have had to do anything other than just pull the cable out.
Update:
I think that the update.zip's applied to my phone have changed some software to an earlier version that what my unit was shipped with.
When I first got the phone, I just plugged it into the pc and selected 'mass storage' on the phone. The drives then appeared (and worked) in windows.
Now, I have to click mass storage. That on its own isnt enough. But if I pull-down the tray menu at the top of the screen, there is another option to click (something along the lines of 'select this to transfer files between your phone and pc'). If I click that, it works.
There are some slight differences still:
1) I could swear that my phone originally allowed access to the 2gb phone internal memory (I never tried reading/writing to it, but I'm convinced windows displayed a 2gb drive).
2) I used to get the "xx/13.4gb free" under the drive letter in 'my computer', which I now only get in the status bar at the bottom of windows file explorer.
QUESTION
Does everybody else have to click "mass storage mode" AND pull down the task bar and click "transfer files" to get the internal sd to work as mass storage in windows?
Or do they just have to click "mass storage mode" and that's all?
Thanks
I always had to pull down the menu and manually mount the sd card when using mass storage.
Sent from my GT-I9000M using XDA App
Definately wasnt the case on my phone (bought mid october, so its quite new) because I got my music on there via mass storage twice before 'hacking' it. I couldn't have done that without knowing about the extra buttons to press. It's good to know that it's just a side effect of the update.zips I've applied, and that I get to keep the phone
Cheers
So my phone got stuck at boot screen. Bell says I get full replacement, but I'm gonna lose all the data. I have the internal full of children opening gifts on Christmas.
Reading a million forums. Tried to learn enough to flash the firmware with odin. Tried flashing the stock JH2 back to phone. Phone boots to recovery and says problem mounting SD.
Can ADB be used to connect to phone in "Download mode" to Pull the media???
PLEASE PLEASE help?????
after odin is done the phone reboots to:
E:Can't mount /dev/block/mmcblk0p1
(no such file or derectory)
E:copy_dbdata_media: Can't mount SDCARD:\copy default media content failed
I'm still desperately trying to get my files. I've read about 1254 more threads. Found this one about flashing back to eclair...
http://forum.xda-developers.com/showthread.php?t=797302
So far I tried JH2, JL2, JM8 and still no luck. Anybody out there got any ideas?? links to help or compassionate remarks?
Phone no boot need remove files inside...is this really an impossibility??
Argh.... it never happens when the internal has useless data aye.
You tried flashing a firmware using all three files (PDA, modem, CSC) with repartition?
P.s. apologies if you have tried all this, just trying to establish a baseline
Sent from my GT-I9000 using XDA App
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Hoodmin said:
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
Repartition only erases the 2GB portion, ive done several repartitions and it never touched my personal files on the internal SD
Hoodmin said:
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
That won't work...the 'internal SD' is not a SD card in the traditional sense (standard, mini, micro) - it's a physical chip (IC) that's soldered on to the mainboard.
I haven't heard of anyone being able to pull data off a phone that's got the mmcblk0p1 failure. The best I've heard is of people repartitioning/formating the sd memory in order to get it working again - but of course, that would mean losing all data...sorry...
As what EarlZ said, repartition won't touch the part of the SD dedicated to user data. I've flashed via Odin countless of times and never once did my internal SD get wiped with a repartition so why not flash to something like JPU with repartition using 512 pit file?.
Edit: and reading the error seems to tell me it's a problem in the 2GB portion of the internal SD where the system and such get stored. So yes, do try a repartition. I guarantee you that your user data will be safe. The only time it would get wiped is if you actually choose to format that partition like how one does in Windows or through the settings. Odin flash won't do this most definitely.
If that fails...
Also take a look at this...
This guy seemed to have been lucky and got is supposed dead I9000m SGS working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
Well hot damn them are some good replies. I was brave enough to try re-partition and a few mod roms like in the thread mention as well as a few thread techniques I read. I must have read about 4622 threads by now. Still no luck for me I really really appreciate the help.
Thinkin I might just go wrap up the kids christmas presents tonight while they sleep and just make em open them all again hahaha.
In the mean time I'll just keep readin and keep tryin. Learned a lot at least.
So....
Original problem = boot cycle
-I flash back to JH2 and at least to phone gets to recovery mode and i see the mmcblk0p1 error. progress
-try flashing to the newer JL2 and it goes back to boot cycle
-try flashing back to JH2 to get recover mode again and still boot cycle
-read a million forums about trying mod roms and other techniques and still boot cycle
-get encouraged that re-partition will only affect OS side of SD card and try a million things again. Still boot cycle
-decide to go back to the JK4 that i started on and seems to be the root of all evil and then BAM recovery mode returns and this time it even recognized the device
-any attempt to connect with device either with kies or windows explorer causes PC crash
-phone even recognized by ADB I "think" this program could be used to try and "pull" media from the device but that's just a guess and I don't know how to use it
-the error now is not mmcblk0p1 instead: E:Can't/b mount /devlock/stl10 which could mean something or could be just the same and it leads me to this thread: http://forum.xda-developers.com/showthread.php?t=788850
-try flash techniques in the thread and back to boot cycle
-try going back to the JK4 so I have recovery mode again and still boot cycle. progress gone
I'm gonna flash this damn thing again and again until the damn copper lights on fire
Wow i Admire you man.Listen i dont know much about ADB but i think i saw a post of someone that literally pushed files in his internal card with it,and i clearly remember him saying he could browse through his phone although its card was burned.If so then a single copy would be possible.Since i cant help more,you better start reading on how to use it and find basic commands for it.
I wish you the best man!!!!
Have you tried this kernel: http://forum.xda-developers.com/showthread.php?t=901772
I seem to be able to get that running on my dead GT-i9000M. It has a file browser so maybe you can see if your pictures are even there/accessible. Also has a USB Mass Storage option but it didn't seem to work for me.
However, phone is still dead and needs to go in for repairs/replacement.
OK so now I'm f&*#ed
Tried JP1 method from this stupid page
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
and now I don't have download mode anymore.
somebody plz just shoot me
EDIT: Ok excuse this panic post. I still had connection to ADB and a simple "adb reboot download" command got me back.
Wow thank JDROM. This recovery mode really looks promising. I got the file manager working but I can't seem to find any directories with DCIM/ label or any media. Sure looks like this could help me somehow. Might only have half the SD mounted or something. I'll have to play around and read some more, but I gotta say this is the best progress I made in a while.
THanks SO much
Edit: Found in File manager to run partition manager and formating options show up. In here there is mounting options to /mnt/sdcard or /mnt/external_sd except when I try it returns the E:Can't mount /dev/block/mmcblk0p1 to /mnt/sdcard with parameters vfat(null) So hmmmm....
Edit: Also learned a bit more about ADB commands to possibly ""Adb pull /sdcard/DCIM"" if I ever get it mounted.
Well that's it for me. The quest is over. I admit defeat. Memories Lost. Game Over
That sucks man...i had a bunch of stuff on my phone that i lost when the internal died....mine took out the external sdcard i had in it too - so all my backups were destroyed as well!
Moral of story: Save important crap on something like dropbox!
Some dev should make a program that automatically syncs certain directories (like pictures, or backup folders) to dropbox. I'd donate for that.....
Im having issues with the internal SD card after the update. So is Dennishwc
http://forum.xda-developers.com/showpost.php?p=10484065&postcount=1057
Via Windows 7 64 "Error 0x80070057:The parameter is incorrect 'for file copy and 'The file is too large for the destination file system' when I try to make a folders.
When I try to format in Windows, it shows capacity only as 2.19GB rather than 13gb or whatever it should be. Same occurs on a Win XP laptop I tried, but explanation of the errors are more general but seem to be the same.
Seems it might be this issue that 2.2 caused for the SGS Vibrant ?
http://forum.xda-developers.com/showthread.php?t=860328
http://forum.xda-developers.com/showthread.php?t=846384
Could just be the SD card failing unrelated to the update, but I have no idea. Seems I can copy to an external SD, and then copy via the phone to the internal SD. Odd.
I have tried format via Windows, which resulted in 2.19gb size, but phone reboot reset it to 13gb. Format via phone did not resolve either.
Any fix that will work? or is it borked.
I'll repost my question here.
Did you try the "format internal-sd" from CWM recovery ?
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
rye&ginger said:
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
Click to expand...
Click to collapse
Download Rom Manager from the market and run it. Click on install clockworkmod recovery. Then you can reboot into recovery. Please see the clockworkmod thread for more info
Sent from my SGH-I897 using XDA App
Don't forget to root first. I had a pain rooting this JL1. I spent 20 minutes playing with JL1 and I couldn't stand the lagginess. I'm sure lagfix would've helped, but I just went to a custom ROM instead.
Tried superoneclick only once and I'm rooted even went as far as unlocking it. Also, my phone isn't affected by the sd card bug. I can transfer files bigger than 2.19 Gb and it's showing the full size in Windows. Froyo runs flawless so far even though it's still not clear whether it's official or not.
Hmm, that's an odd one indeed.
Curious - I took a look at the 2 threads that Rye pointed out and one seems to be about external sd issues and the other about the mounting issues with 2.2 vibrant kernels. Doesn't seem like the problem you are having is either one of those... Could be but didn't seem that way upon review.
Did you happen to try and restore any backup after upgrading to 2.2 or anything? Can't imagine what would cause it but seems like it's getting mounted strangely or something... Surprised that a format internal sd wouldn't fix it in recovery...
Second question - what Samsung drivers / driver pack are you using on your Windows 7 x64 install? Wondering if the driver is failing to recognize the file system type and is causing Windows to treat it as a file system that shouldn't accept a file larger than 2+GB...
I havent noticed any problems with the size of the file. What happened with mine is that i transfered a couple of movies (about 3 or so) and then transfered about 4 gigs of music. halfway through the music it started giving me the error. after that, even transferring individual mp3 or pictures would result in an error. The internal sd card showed up on my computer as having 8gig free. after that i ran the check disk (by right clicking, going to properties then tools). my computer found errors and corrected them. after that, the internal sd card showed up as only having like less than a hundred mb left
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19gb.
Im about to do the CWM recovery format and will post the results.
If you are using the Rogers 2.2 update with no kernel modifications then the CWM will not work for you.
The Froyo kernel from Samsung comes with Recovery 3e which RomManager can not replace for 2e as 3e requires digitally signed packages.
consider (i have not tried):
- root device
- adb shell
- su
- backup any files you need on /sdcard to /sdcard/external_sd
- use the format commands to re-format /sdcard
-- probably mkfs.vfat or the like.
rye&ginger said:
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19GB.
Im about to do the CWM recovery format and will post the results.
Click to expand...
Click to collapse
Yea, really not sure if the drivers are a problem or not. When I checked mine, running the Rogers 2.2, it shows the same as what yours does in the format utility - 2.19GB. That is odd because it seems to set the filesystem type as FAT32 which can easily handle the 13.0GB size of the volume. The properties in Windows show 13.0GB w/ about 11.0GB on my disk that is available...
Regardless, I would be hesitant to format or repair that disk within Windows. Who knows if there is something within Android that is put there as a translation layer that maybe Windows isn't seeing / reading correctly through the driver, etc. I'm sure someone does know but I'm not that guy so if anyone call fill in the details...
And, after just testing on my own system... bang, same issue trying to copy a 900MB file to it... Hmm, this just got interesting.
Going to check a couple of other things, will post result.
I had this exact same issue. The only fix for it that I could find was to do a complete restore of the stock rom. Oh well, nice to have a fresh phone.
Hmm, this is not a fun problem.
Just tested formatting the volume - from within the running phone only, mind you - and the result is strange. After copying everything from my SD card to my computer, with no issues, I unmounted the USB, formatted the card through the settings / sd card storage menu / format internal sd card. Took about 30 seconds after which point I reconnected the device, windows picked it up and I mounted it, recopied about 2GB worth of data to the card with no issues at all. Added an additional 500MB file to it with no issues. Disconnected the device from within windows using the safe removal tray tool, turned off usb connection on the device and then unplugged it. Remount the usb device and windows sees it no issues but I can't copy a single item or create a folder on it. Exact same errors as what Rye described and I encountered the first time.
So, seems like after a fresh format the sd card can be mounted in windows, ONCE, and then all hell breaks loose.
Why??? Will keep testing but looking like I need to move back to my previous di11igaf's ROM. Can't work like this...
Interested in what you find, Rye.
Oh btw, i am able to transfer files with no problems if i connect to the pc in media player mode. I have problems when i am in mass storage and kies connect modes
Riker2k, good stuff. I have no news, Im stuck where I am unless I swap the kernel it seems as I cant use CMW Recovery to format.
This is over my head, so I will for now probably just do a format, load up the card via Windows, and then use the external card to slowly add items when I want to and transfer over to the internal through the handheld. Ghetto. Either our Sd cards will get worse and die, or more people will have issues and it will get patched I guess?
Dennishwc, I will try media player mode but I think it did nothing when I connected that way the other day. I didnt mess with it much though. I need mass storage to use iSyncr app though, but there is a wi-fi add-on that may help me avoid that.
Well I just tried the format and dump a lot of stuff via Windows idea, and it only did about 2.2gb before the error stopped the fun. It did this twice, so this is is EXACTLY at the 2.19gb capacity that Windows is seeing in the format utility. So, I do have some news.
Again, this is over my head as to what to do next.
Has anyone tried moving files over via adb and see if you hit a 2.19GB limit?
I am having the same issue when copy files while connected in USB Mass Storage Mode (consistent).
On the plus side, I also tried connecting in USB Kies Mode, and I have yet to see this error. Copying is slower; but, it seems to work.
This could be a workaround for folks getting the error in Mass Storage Mode.
I am running Rogers 2.2 (all stock) and rooted with SuperOneClick.
i'm having the exact same problem. if i pick "mass storage" i can't copy anything over hte internal sd card, but if i use "media play" option, i can do it without any problem. i guess that's a temporary solution
i'm having the same problem, though the size and free space of the internal storage shows up correctly in my system.
i can also copy files no problem to the external SD when in mass storage mode.
The AMOLED screen on my Nexus One broke, so, I sent it for repair to a dealer cause there is no official HTC support for Nexus One in India. Before I sent the phone I took a backup of my SD card and also removed it from the phone.
After I got the phone back with the new screen installed, I put in my SD card and it says Blank SD card or unsupported file system. So, I tried different SD card and the same thing popped up with every card I put in. It would ask me to format the card and even if I formatted, it would not mount the SD card. The SD cards work in all other phones and SD card readers.
So, I sent the phone back to the repair guy and he said that its most probably a software bug because if it was a hardware bug then the error message would not pop up at all. He said that it would be best to reflash the ROM but then he tried and the ROM could not be reflashed.
Now the Phone is with me and everything works except for the SD card. Plugging the phone in the computer also doesn't help as the card is not being mounted by the phone at all.
The phone I am using is a Nexus One with stock ROM Android 2.3.4 (never rooted or hacked).
Please help me find a solution to this. I'm even ready to install a custom ROM but can't do so without an SD card.
Please help!!!
Ok well android can't find the SD card but lets see if your bootloader can if not then send it in for repairs again because it's not software. Check my sig there is a link that says passimg try those instructions and tell me what you get.
Hey,
Thank you for the response but most of the instructions require the SD Card. However, in my case as you know the SD Card itself is not functioning. So even if I download the Passimg file, I can't place it on the SD card.
Is there a way to use ADB to wipe the phone completely and then reinstall the original factory stock ROMS?
I did go back to the vendor and asked him to repair the device but after a heated argument he just said that the device's SD card is working but it is not recognizing the cards in it which he said is because of a software bug and for that you need to re-flash the device completely but he didn't have the means to do it, so now I'm left with an unusable phone.
So, in shot can I do the whole reflash thing without the SD card working?
Thank you for responding, you're the only one so far whose come to the rescue. Waiting to hear from you.
Thanks
Hey,
So I just understood the full extent of your recommendation. You wanted me to check if the bootloader detects the Passimg file or not given that booting into Android is not doing that.
As per the instructions on the passimg page I need to download the FRG83 ROM and apply the update. But I'm just wondering if I do this and if the bootloader actually detects the update on the SD card, won't I also need to downgrade the HBOOT version or is it jut safe to apply the downgraded FRG83 over the GRJ22 build that I currently have on the phone?
The details of my phone are as follows:
Nexusone pvt Ship S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Oct 12 2010, 14:33:16
Please guide as per your convenience,
Thank you.
I'm not 100% sure but I'd assume that if you do as what you're planning to do.. the HBOOT should also be flashed automatically with the rom. double check incase!
Hi Again,
So, I took the risk and downloaded the FRG83 ROm loaded it into my SD card using a different phone and then put that card into the SD card slot of the Nexus One.
I went into the boot loaded and it automatically detected the PASSIMG.zip file and asked me whether I want to install the Update - I chose YES.
The update installed successfully and I booted into Android. After finishing the Wizard, I checked the Android Version and it says FRG83 but when I look at the notification bar it still shows me the same error "Blank SD card or has Unsupported File System".
So, we can conclude that the SD card and the SD slot work fine.. Any thoughts on what could be done next?
Well that's weird ok well lets see what the computer says. Put the card back in that other phone and connect it to the computer then on the computer go to computer then right click the card (probably E: maybe F: ) then go to properties and check file system make sure it's FAT32.
Not sure if it's wort posting on this thread still, but lots of people come searching for a solution to this problem so I figured I'd post at least another thing to try.
I've had this happen several time on various Android phones. I've been able to bring the card back every time. I throw the card into my micro usb reader, pop it in my computer, and run disk utility (I don't know what equivalent would be for Windows). You should see your SD card come up and see your main data partition there below it. Click on the partition and click repair in the bottom right.
It will run through some stuff and you'll be able to see if it's found anything in need of repair and if it repaired it.
The few times this has happened to me Disk Utility said it was an empty block at beginning of some data or something...
YMMV
Not sure if it's worth posting on this thread still, but lots of people come searching for a solution to this problem so I figured I'd post at least another thing to try.
I've had this happen several time on various Android phones. I've been able to bring the card back every time. I throw the card into my micro usb reader, pop it in my computer, and run disk utility (I don't know what equivalent would be for Windows). You should see your SD card come up and see your main data partition there below it. Click on the partition and click repair in the bottom right.
It will run through some stuff and you'll be able to see if it's found anything in need of repair and if it repaired it.
The few times this has happened to me Disk Utility said it was an empty block at beginning of some data or something...
YMMV
When I had this exact problem, I had to replace the SIM/Micro SD flex board to fix it. They were $15 shipped on eBay at the time.