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?
i'm on axura 2.1 and went to flash a new rom through clockwork and it says E:Can't open /sdcard/*********.zip (bad)
so i redownloaded the rom, put it on my sdcard, tried again, same thing. i then downloaded a different rom, put it on the sdcard, tried to flash, same thing. any ideas? is it odin time?
Did you save it on the internal card or the removable card? It needs to be on the internal to flash through CW.
it's in the right place. in fact, the axura21ve.zip is still on there and will flash fine, but no new zips will flash, so i'm thinking the fs got corrupted...?
I've had this happen on Axura 2.1 also with the mounting_fix_vibrant SD fix.
I can't copy anything from my PC to my internal SD card since flashing Axura 2.1
i thought that sombionix' sd mount fix was included in this rom. apparently not. which is weird because this issue never affected me in linux with previous roms that didn't have the fix. oh well. flashed the fix and am booting a new rom.
I am also unable to flash a different rom over Axura. Can you help me? I want to go back to Bionix but can't!!!!!
I was on axura 2.1 and changed to 2 new roms.
I an on another rom now, just fine.
I have been getting the android logo with exclamation mark a lot more recently though.
I smell ODIN with repartition checked.
Sent from my SGH-T959 using XDA App
Ive also run into this troublesome problem, even Odin back to JFD stock will not help me get the new roms on, wiped internal sd, external sd, cleared cache and everything. Was able to flash back to JFD and then Fusion 1.2 . Havent tried the repartition setting in Odin but I may have to go that route.. any input from you guys would be great, has anyone fixed this problem yet?
[FIXED]
What I did was odin back to JFD and select the "Re-partition" option, didnt delete any of my data and seems to have corrected the problem installing other roms, try that out.
Alright...
So I tried to install voodoo on my phone which was running stock 2.1 Eclair, and somehow it amazingly ****ed everything up. I know it was likely more or less my error than not.
So I was researching how to correct my ****-up which seemed to be that my phone was soft bricked and stuck on the vibrant insignia on boot up. So I read further and decided best thing to do would be use odin to flash Eugenes 2.2 froyo
GREAT! Everything was working the 2.2 rom is on my phone, all lights are Green! BUT I tried to download something from Marketplace and now my phone is telling me there is no space left of Application Storage. So i thought that it might be weird and decided to go ahead and check it out in my SD Card and Phone Storage settings and sure enough, I have one Gig on my External SD available. 11 Gigs on my Internal SD available but NOTHING available in the way of Application storage space...which is a huge bummer...
Sadface - facepalm FAIL -
So then I read that sometimes when installing a lagfix they take up a significant amount of phone space to create databases. So I'm wondering if somewhere on my phone Voodoo is chillin' eating up all my application space...
Or what I should do now to correct the situation.
Any help would be greatly appreciated.
Cheers!
you flashed eugenes froyo right? havw you tried odin back to stock?
Sent from my SGH-T959 using XDA App
Yes, actually what I did, was flashed over to stock, original pit and tar files, and then when the phone booted it gave me an error, but that was expected saying it couldnt mount my SD card. I entered odin again and re-flashed back to eugene's 2.2 froyo and the appropriate pit file and BOOM. With Repartition checked it flashed back to eugene 2.2 with the filesystem cleared from my horrid attempt at voodoo and everything is perfect now. : -) All my application storage space is back!
that's nice.
Sent from my SGH-T959 using XDA App
So finally got my vibrant back up and going after i tried repartitioning the sd card through clockwork. Now that i installed the stock 2.2 it will not allow me to download any apps through the market because it says that i am low on space..??
I checked and i have plenty of space so whats the problem.
Any help out there would help.. THNKS
same problem.. lmk how u solve it pls!!
Do not use clockwork for repartition, use ODIN instead with JFD firmware(2.1) and .pit file. Then reinstall clockwork and install a 2.2 ROM of your choice.
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.