Ok so today I used ODIN to go back to stock JFD. I used odin 1.7.
I had no problems, worked fine.
I DID not click on "re-partition" I had left it UNchecked.
However, once I clicked start on odin, odin automatically all by itself put a check mark next to repartition and started doing it's thing.
Well I have no clue why it did that, but my phone is fine.
What is the point of repartitioning, when do you use it, when do you not. Also why did ODIN magically check mark it for me upon pressing start?
edit
actually odin puts a check mark next to repartition on its own when I load the pit file.
little tiny bumb
Repartition is supposedly going to wipe all data on your phone, but it's also a death button that makes you ODIN freeze and making your phone not boot up
draikz said:
Repartition is supposedly going to wipe all data on your phone, but it's also a death button that makes you ODIN freeze and making your phone not boot up
Click to expand...
Click to collapse
A death button? i've read some threads where people suggest using it.
anyways, I find it strange when I clicked start, ODIN automatically put a check mark next to it. My phone seems fine though, actually all my pictures and stuff like that are still on my internal sd card.
Oh all I know is that my odin freezes when I check it haha.
Sent from the dirty little green robot.
It repartitions your filesystem. Lets say you installed CM6.1 which uses ext4, then it will repartition it back to RFS (default).
rk0 said:
It repartitions your filesystem. Lets say you installed CM6.1 which uses ext4, then it will repartition it back to RFS (default).
Click to expand...
Click to collapse
So I'm confused, when do you know you should use it---according to your statement, you only need to use it when you want to switch back to stock RFS from a different file format? What about going from Axura 2.0.5, or stock JK6 to JFD, do you need to repartition? Does it hurt to repartition? What happens if you don't repartition, and go from CM6.1 back to JFD using odin without repartition?
Windows 7 says my samsung internal memory uses fat32, huh? Is that same as RFS.
SamsungVibrant said:
So I'm confused, when do you know you should use it---according to your statement, you only need to use it when you want to switch back to stock RFS from a different file format? What about going from Axura 2.0.5, or stock JK6 to JFD, do you need to repartition? Does it hurt to repartition? What happens if you don't repartition, and go from CM6.1 back to JFD using odin without repartition?
Windows 7 says my samsung internal memory uses fat32, huh? Is that same as RFS.
Click to expand...
Click to collapse
The internal memory is split into many different partitions. To name a few, /data (/datadata maybe?), /cache, /dalvik-cache, /system, /dbdata, maybe a few more.
Anyways that is how some of these lag fixes work, they convert each one into a faster file system. OCLF uses binds (you can look it up) and makes your /data use ext2, while voodoo converts all your filesystems to ext4.
Anyways, that partition for your use is set to fat32.
And I believe the repartition tick will just re-apply those. I've done it several times and it has not wiped my /sdcard. However, there's no guarantee it won't. Anyways it's good to do it when you're starting fresh (or when using a .pit file perhaps).
That's kind of what I've picked up
rbirg said:
The internal memory is split into many different partitions. To name a few, /data (/datadata maybe?), /cache, /dalvik-cache, /system, /dbdata, maybe a few more.
Anyways that is how some of these lag fixes work, they convert each one into a faster file system. OCLF uses binds (you can look it up) and makes your /data use ext2, while voodoo converts all your filesystems to ext4.
Anyways, that partition for your use is set to fat32.
And I believe the repartition tick will just re-apply those. I've done it several times and it has not wiped my /sdcard. However, there's no guarantee it won't. Anyways it's good to do it when you're starting fresh (or when using a .pit file perhaps).
That's kind of what I've picked up
Click to expand...
Click to collapse
so basically, it never hurts to repartition?
SamsungVibrant said:
so basically, it never hurts to repartition?
Click to expand...
Click to collapse
Not always true. After I had a bad flash, I had the Phone ! Computer icon (basically means you're soft-bricked).
When I loaded JFD/Pit file into odin, it automatically ticked repartition and failed. I forgot what I did but I had to do funky stuff to get it to work.
rbirg said:
Not always true. After I had a bad flash, I had the Phone ! Computer icon (basically means you're soft-bricked).
When I loaded JFD/Pit file into odin, it automatically ticked repartition and failed. I forgot what I did but I had to do funky stuff to get it to work.
Click to expand...
Click to collapse
ya in odin3 v1.70, anytime i load the pit and tar, it automatically check marks repartition.
I'm still kind of confused but ok, think I'm getting it.
I'm still confused when to use repartition and when not to.
I've used it in the past by accident, because loading pit automatically puts a tick mark there, but nothing bad ever happend.
Hope someone would know a solid answer to this.
Also, if it repartitions the phone, does it mean it totally deletes and clears the info in EFS?
Who developed Odin?
reasons for checking re-partition in odin?
reasons for not checking repartition in odin?
im a lil lost on this topic...sorry
Should try Heimdall guys, it works basically the same way except A LOT less buggy and is much more reliable. Only difference is that with Heimdall you extract the .tar and place the individual files separately. Not checking repartition will just reformat all the current partitions and set you back to stock (with RFS), checking repartition will wipe the entire device (including /sdcard partition) and set up all your partitions again (if you had a lag fix screw them up or something, causing your device to not boot).
I was always worried having to use Odin because the software is so damn buggy (connection issues, etc.), but Heimdall uses an extra driver to connect to download mode via usb. If you checked repartition and Odin didn't wipe your SD card it was due to a bug or the .pit file not being registered properly.
Ok let me see if I am getting this straight.
Repartition will basically change your file systems from w/e lagfix you had, (ex. voodoo) back to RFS, but also wipe your SD card? Is this what im getting? If we odin back to stock w/o repartition, does that mean we still have EXT4 file systems?
Still takes you back to RFS, just doesn't repartition everything and wipe the SD card.
Sdobron said:
Should try Heimdall guys, it works basically the same way except A LOT less buggy and is much more reliable. Only difference is that with Heimdall you extract the .tar and place the individual files separately. Not checking repartition will just reformat all the current partitions and set you back to stock (with RFS), checking repartition will wipe the entire device (including /sdcard partition) and set up all your partitions again (if you had a lag fix screw them up or something, causing your device to not boot).
I was always worried having to use Odin because the software is so damn buggy (connection issues, etc.), but Heimdall uses an extra driver to connect to download mode via usb. If you checked repartition and Odin didn't wipe your SD card it was due to a bug or the .pit file not being registered properly.
Click to expand...
Click to collapse
Everytime I odin I go all the way back to JFD and repartition and I have never had my internal or external cards wiped
When going back to stock JFD -
DO nothing.
Load the pit/tar, press start. (it does what it needs to, you need to do nothing, and yes, once the tar is loaded, all 3 check boxes will automatically check themselves).
You are not going to lose the data folders on your internal.
Check my signature for a guide on going back to JFD if needed.
I leave that checked all the time. I never had any issues with failed Odin flashes.
Sent from my GT-I9000 using XDA Premium App
I was flashing my phone using Odin and noticed after I clicked start that the re-partition option was checked. I then quickly unchecked the button thinking that leaving it checked would harm my phone. The Odin screen then froze with my phone still attached to my laptop in Download mode. After waiting for a while for it to continue the flashing process I finally close Odin and removed my battery to restart my phone. Unfortunately now I can't restart my phone. When I press the power button nothing happens. Any idea why this happened?
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 wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
pamulli said:
I wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
Click to expand...
Click to collapse
Can you Go into recovery & then into mount options & format data... worse case is to odin to stock then flash this over...
use the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
pamulli said:
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
Click to expand...
Click to collapse
Do you have repartition in Odin checked?
I found several other posts regarding this exact same issue and everyone concluded there is no fix and it has to be replaced. Luckily I'm still under warranty and T-Mobile is sending me out a new one. Oh well...
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.
i made a mistake and re-partinioned my internal sd card with the wrong sizes, is there a way to fix that through adb?
i wonder if there's a odin-flashable rom that installs cwm...
I've never had experience with that, but wouldn't using Odin to flash back to stock, and hitting the re-partition button solve the problem?
i thought it would, but apparently it doesnt.
anyone know what the partition sizes should be? i got the phone working again.