Hi everyone,
In my overzealous attempts to reformat an old 4gb external SD card through CW Recovery, I managed to reformat my internal SD card (I was using the Clockwork Recovery version 2.5). I thought that "format sd card" would reformat my external memory card and not leave me without a usable phone, but I guess I misunderstood.
I spent at least five hours going through all of the ODIN tutorials and trying them out, and found that using Eugene's 2.2 with 2E recovery ROM actually allows me to boot up (hooray! ), while the stock rom from this thread simply forces a bootloop on my poor phone, with occasional freezes. Even using AIO's "Flash to Stock" from Eugene's 2.2 doesn't work.
Further searching has lead to the thread about partitioning using parted, which has been hard for me to use effectively (I made a new partition, but I couldn't get it to mount properly).
I was really excited to come across this tutorial, but it didn't solve my problem. After getting through all of the steps, at step 5, ODIN3 versions 1.0, 1.7, and 1.81 (I tried all 3 on 3 different walk-throughs of the tutorial) never were actually capable of repartitioning the sdcard properly. Every time after the first time of using "parted" to reduce the card to a single partition, I found that that lone partition was always the only one there (15.5 gb /SYSTEM Fat32). No changes had been made to the sd card's partitions.
I don't know if it helps any, but the ROM I was running before I reformatted the card was Bi-Winning 3.0, and Voodoo had not been disabled at the time of the reformat, which may be why I can't flash new ROMs through the recovery as well.
As near as I can tell, ODIN can't actually return my vibrant's partitions to factory settings, so is there a way for me to do that manually? I think that would solve my problem.
Thanks,
-NewbieCube
My guide (you linked to) clearly states its not for this intent... if you read it, you would also see I linked to Eugenes froyo that does not brick. If you did it, THEN you did my guide ODIN to JFD, you are on a fully functional stock 2.1 JFD build.
If your intent was to just format the external sd, go to menu settings, sd card/phone storage, unmount the external and format it.
Right, I know that. In fact I read all through your thread and tried to flash to Eugene's first, and then to JFD, but JFD does not boot properly. It just gives me a black, unresponsive screen. I'll definitely go back through once more and try that again, though, as you clearly know what you're talking about.
I basically formatted the wrong storage (internal sd vs external sd), and would like to get that internal back to stock, so you are right that Eugenes -> JFD should work. I'll report back with results.
^ yeah, exactly... that should work with no issues. let me know if it does not.
Oddly enough, that didn't work for me either. Since my phone still can boot into Eugene's (albeit with 0.00B available to apps), I know this should work, just from reading through your guide. So once more, here's what I did:
1. Download mode -> ODIN 1.70: Flash Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit (from Eugene) Re-Partition NOT checked (Eugene's thread says not to)
2. Boot up into Unbrickable Froyo, with no application space remaining Mount sdcard and move Update.zip (s15274n's) into the root folder without issue.
3. Download mode -> ODIN 1.70: Flash s1_odin_20100512.pit, and T959UVJFD.tar (s15274n's) with Re-Partition checked
4. Boots once automatically into recovery, saying something about a failed MBR checksum and failure to clear userdata
5. Bootloops that never get past the VIBRANT logo screen
6. Boot into recovery and try deleting user data and cache data manually and to reinstall packages, but bootloops continue.
I really don't know what I'm doing wrong here...
UPDATE:
I even used Heimdall on another computer and got the same result, so it isn't ODIN. Why is reformatting the internal SD card to stock so difficult to do?
delete my post
I FIGURED IT OUT!!! ...by random chance
For my problem, it was indeed the voodoo lagfix that was messing things up, and this post:
http://forum.xda-developers.com/showthread.php?t=888084
helped me out tremendously.
Related
My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
thanks!
~peter in oakland
wrong section
huzzam said:
NOTE: I figured this out, don't bother replying! thanks for looking
My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
EDIT: "adb push" has saved the day!
thanks!
~peter in oakland
Click to expand...
Click to collapse
I also use a mac. You need to be careful how you delete and format your sd cards. I just deleted some stuff off my sd card by dragging it into the trash and it didnt free up any space on the sd card. I have also seen problems with formatting them with the mac also. Also ODIN is a great way to put things back to stock. you will need to use bootcamp to install windows on the partition. If I weere you I would still ODIN back to stock and reflash to make sure you dont have errors in the future
Format sd card through clockworkmod recovery. Itll wipe everything, but it should bring it back to being usable. Also heimdall works with mac right? I havent used heimdall but read its an open source rom flasher replacement for odin.
Sent from my SGH-T959 using XDA App
I was going to suggest Heimdall as well. You should be able to flash back to a stock firmware, then sort things out from there. If you want to do that and then report back here, we could help from there.
Information about Heimdall is available in this thread along with a link to download the program.
Good luck.
Here's my issue: I wanted to start with a fresh "slate" for flashing a custom ROM (I originally had TRIGGER+OVERSTOCK). I backed up my apps/settings and the current ROM, disabled the Voodoo lagfix and unrooted the phone. Then, I ODIN'd back to JFD. At this point I downloaded TitaniumBackup and ROM Manager. When I tried to mount the Internal SD card, nothing happened...just the external card mounted. I went back and checked my ODIN settings an noticed that I had left the "Re-Partition" box checked. Freaking out at this point, I then went ahead and rooted the phone, and checked the file system through the Super Manager app. All my data was still there!!! So I went ahead and used ADB to "pull" the TB and ROM Manager data onto my computer just in case. My question is: how do I get the internal SD card to mount correctly?? Any help would be HUGE!!! Thanks in advance for everything!
Oryon007
I can't really tell by your post, are you trying to mount your external sd onto your phone or onto your computer?
I have Odin'ed to JFD with repartition checked many times, and have never had your problem. If I were you, I would just go through and Odin again using a different JFD image (maybe you just had a bad flash, what version of Odin were you using?) As long as whatever you are flashing with Odin contains all the essential bits, repartitioning should not do anything too deadly to your phone. (I learned this the hard way, do not try to Odin and repartition with JI6, for example, because JI6 has no dbdata image included).
If you just want to troubleshoot your current install, check the "/etc/vold.fstab" and "/etc/vold.conf". I can't actually tell you what those two files should look like as I am currently running a 2.2.1 rom (I think the files should differ between versions of the OS, but I'm not sure).
I am a pretty big Linux and Android noob, but I'm pretty sure that those two files are responsible for mounting both sdcards onto your phone, at least partially. (I would have no idea where to look to fix it if it isn't mounting onto your computer.)
Sorry if any of my advice is off, like I mentioned a little earlier, I am a pretty big noob, albeit very interested in Android.
Sorry for the confusion....I'm attempting to mount my internal SD to my computer. As far as ODIN is concerned, I'm using 1.7 with the flash files from this post:
http://forum.xda-developers.com/showthread.php?t=734475&highlight=stock+odin
I've used this ODIN flash before without any issues, so I'm still a bit stumped on why I can't mount my SD card. I can see the entire file system from within my phone as well as through ADB, but (for whatever reason) cannot mount it to my PC. I am leaning towards the issue of the SD card being partitioned wrong. Any thoughts? Any ideas on how to repartition the internal SD back to "stock"? Thanks again for any help provided!
-Oryon007
That's actually the same JFD image I use. I would just use Odin to flash JFD again with the repartition checkbox checked. I'm pretty sure that that will solve your problem.
Make sure you use the pit file too, without that you will have serious issues if you are repartitioning.
I'll try this again, just in case I missed something the first time...wish me luck!! I'll let you know how this turned out, too!
-Oryon007
Alright, good luck. Did you use the pit file when you originally flashed JFD and repartitioned? Not using that file may have been why you had this problem.
Ok...so, no change with the internal SD. When I attempt to mount the SD cards to my PC, the only one that shows up is the external one. After unmounting them, I can still see both cards with filesystems. Could the internal SD have been partitioned incorrectly? If so, how do I get it repartitioned right?
EDIT: I did use both original files from here...
Okay, I'm sorry but I have no clue how to help you. Are you sure its not just your computer? You may have to try and get help from somebody more knowledgeable than me. Have you tried flashing any other rom through Odin over JFD?
Not yet...I wanted to make sure that it wasn't something that I was doing incorrectly through ODIN. Again, my ultimate goal in all this was to have a "clean slate" to install a custom ROM on; the catch I'm running into is that I can't mount the internal SD card to place the files on to flash through CWM, even though I can see all the files through the phone and through ADB. *sigh* Thanks for your help though! It's always nice to have help when you run into these issues...
EDIT: After trying to ODIN JI2 files, I get the following error upon boot of the phone in Recovery:
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Click to expand...
Click to collapse
Look at what I said at the end of the second paragraph, on the second post in the parentheses.
EDIT: Just flash a rom using Odin that does have a dbdata file. You probably checked repartition while flashing JI2.
Last night I was having a similar problem. While I wasnt flashing back to stock or anything, I could only get G: (external sd) to mount to my pc but not the F: (internal storage). Eventually I disabled USB Debugging, plugged in the USB cable from the pc, and it gives you 3 options for USB Mode: Kies, Media Player, Mass Storage. Once I selected mass storage, both internal and external sd cards mounted to the PC with no problem. Just remember to re-enable USB Debugging after.
Finally got it!!
Finally found the issue!! Only took me a week....lol
Going to manage my disk drives found that my PC wanted to assign a drive letter that was already assigned to a mapped network drive. *duh* Obviously not going to work. Reassigned the drive letter and voila!! I can mount my internal SD card!! w00t!!
That's really terrible and hilarious at the same time. Why wouldn't windows just pick another letter to map it to?
I've had a Gtab for a few days and tried TNT 4.4 and now Vegan 5.1, and in both ROMs, my tab keeps freezing. It often freezes on Gallery, but it has frozen elsewhere. I've tried wiping it with clockwork, but the problem wont go away. Any ideas? Any other way of reformatting the drive or anything else?
Since you're familiar with clockworkmod, you could try to re-partition the internal sd to 2048 and 0. WARNING: this will format your device and delete everything on the user partition (what's called "sdcard" in these ROM's), back up all data externally (micro sd or usb flash or pc) or it will be gone!!!
This is a common fix for force close across platforms.
Be Sure To BACKUP Important Data to something other than the Internal Device's 16 GB flash memory.
I would also re-flash whatever ROM you want after the re-partition.
There is also a "format all" procedure from Calkulin in one of his threads in development forum.
Edit: There's a couple of format procedures in the development forum, one uses nvflash (sticky) and Calkulin's looks to be .zip. I haven't used either of these, but I would be familiar with nvflash/apx and have that set-up before attempting either.
Hi guys i have problem with a phone thats friends gives me to repair and this is the problem.
Phone was dead so i put in download mode and flashed with "T959UVJFD" , and the phone stucks on GALAXY S logo and then the 4 lights of the down of the phone on and the screen was black so i tried differents combinations of roms, pits files , etc.
The phone finaly booted propely when i flashed a kernel "Bali_1.8.8UV-zImage" with heimdall .
After the phone booted i was happy but i checked and internal 16gb was not recognized and also when i inserted sd card also no detected.
Finaly i was searching solution also when tried to flash with RIFF BOX BY jtag and still same , phone only boots when i flash with kernel "Bali_1.8.8UV-zImage" but still no internal or external storage .
Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Anybody can help me?
I need to work one of them storages
Did you ever find a solution to this? I have an old Vibrant laying around that has this same problem....both the external and internal memories are unavailable no matter what I do.
rikimaer said:
... Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Click to expand...
Click to collapse
a) When you see this message in recovery, what happens if you simply select "Reboot phone" and hit the Power button? Does it then boot up?
b) mmcblk0 = Internal sdcard. I hate to say it, but it sounds very likely your friend's phone could have been hit by the Encyption Unsuccessful bug (refer to Merio90's thread).
As a test, you could follow Merio90's OP steps and use the updated CWM recovery (via update.zip) to re-partition your external sdcard. Note: all data will get wiped (so backup first). When you "reinstall packages" in recovery, you may get that "can't mount ... emmcblk0" error again. Just "reinstall packages" again. Then see if you get int / ext sdcard detection at that point.
If still not detected, proceed to flash a CM7 v7.2.0-vibrantmtd rom. Flash it twice (1st flash updates recovery; 2nd flash converts to mtd partitioning and flashes rom). Merio90's thead is geared towards ending up at an ICS rom, but keep in mind essentially all of the Vibrant EU occurences have been on ICS rom's. This is why I suggest using that stable CM7 build as a test. For kicks, see if you get sdcard detection (probably not). If not, do the vold.fstab emmc/sdcard swap, which works the same and uses the same syntax on GB & ICS (ie. refer to Merio90's OP for vold.fstab syntax). Flash CM7, edit your vold.fstab, & reboot (for swap to take place).
If you're good to go ... you can always proceed onto a JB rom from there. Read through the last discussions re. JB rom flashing issues and kernel compabitibility - ie. to save you the trial & error.
If you still don't get sdcard detection at this point, maybe this is something different altogether. But, my hunch is that you'll get detection on CM7 (after the vold.fstab swap).
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.