Related
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?
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.
Alright so here's the backstory. I bought a Vibrant off of ebay that was stuck in a bootloop. I thought to myself, hey I could just shove this thing into download mode and be on my merry way!
Well, I attempted to flash JFD with a jig that I had. Went fine, Odin gave it a PASS.
Still boot looped.
So I then try Eugene's no brick, and after finally getting the right version, it booted up. Then tried to flash to JFD again.
No dice.
Following the directions here I was able to finally get 2.1 to boot, now here is the problem that I'm currently stuck on.
I can't get the internal sd (onboard flash) to mount in the system. If I am at the shell I can browse to /mnt/sdcard and see everything on the phone and on the sd (external_sd).
But when I go into the settings, all I see is space unavailable and the format is grayed out.
The culprit I believe lies in the partition on the internal memory that creates this MBR checksum error every recovery.
Thoughts? Opinions? I know this can be fixed, I've come this far!
Below I've attached some of the voodoo logs, it seems that when trying to make the ext4 partitions, it can't find it. (I was trying this so I could in the end disable it)
Does anyone know what might be going on? Any tips at all?
The only thing that I can figure now is that there might be damage or the internal storage. When looking in /dev/block, there is no reference to mmc anything, like the internal storage isn't even there. Is the flash chip soldered on the motherboard? I'm guessif that it is, which means it would be a difficult fix.
Only other "solution" that I could thing of is if I mod the fstab to mount a microsd as the internal storage. Would this mod be affected by a flashing rom or odining back to stock?
Also is this the right board for this? If not can anyone direct me to the best spot to ask this question?
Thanks a bunch!
Please find my guide on the developers thread and follow it,
You will be bak at no sweat.
Any problems post there.
Hello everyone! I think i might need to repartition my phone, it works fine the only problem is i only have the 2gb of internal storage, and my sd card. The 12 gb internal "usb storage" is no longer there. Does anyone know how i can restore it? I have basic odin knowledge and have found the original PIT file for my phone, but since i have never gone this far into my phone im kinda nervous. What other files do i need? Or is there another way? Thank you in advance for your help!
Have you tried flashing another rom via recovery first? To check its not a rom/kernel fault.
Your question seemingly feels like a mounting issue other than a partition issue, search about "sdcard not mounted" and you possibly will find a solution, also like the above poster said flashing a different ROM might also possibly solve any mounting issue.
Sent from my GT-I9100 using Tapatalk
You could try to mount storage through cwm.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
16GB S3 i9300, Temasek CM11 Rom
I can't get the /data partition to recognize as anything other than 4GB. I've used Mega Wipe, flashed a stock 4.3 rom w Odin, wiped data, formatted data, flashed a pit file in Odin. I don't see any backups, Disk Usage only sees the partition as 4GB. I've done this all many times just to make sure.
My mmcblk0 partition says unmounted and is 7.5GB. Could this be my issue?
Try this
shiggins9 said:
16GB S3 i9300
I can't get the /data partition to recognize as anything other than 4GB. I've used Mega Wipe, flashed a stock 4.3 rom w Odin, wiped data, formatted data, flashed a pit file in Odin. I don't see any backups, Disk Usage only sees the partition as 4GB. I've done this all many times just to make sure.
My mmcblk0 partition says unmounted and is 7.5GB. Could this be my issue?
Click to expand...
Click to collapse
Try this
Erase-All-Content-on-Samsung-Galaxy-S3
Im not sure about this
Flashing a pit file is a last resort on a total brick, it could have been just legacy data held when you updated from 4.1.
Try the rescue firmware, in general thread, if formatting the internal sd card didn't help.
Sent from my GT-I9300 using Tapatalk
I tried the 4.3 Korean Rescue Firmware. Still no go. Only 4GB data partition. My phone is made in China, I'm wondering if that is why. It doesn't appear to be fake as it's taken every rom I've ever flashed to it no problem. I wish there was a little partitioning program so I could see if there's extra umounted space there. I just feel like I'm about out of options, I'm not sure what else to try. Maybe the 4.1.2 rescue rom?
Just tried 4.2.1, no go with that one either
shiggins9 said:
I tried the 4.3 Korean Rescue Firmware. Still no go. Only 4GB data partition. My phone is made in China, I'm wondering if that is why. It doesn't appear to be fake as it's taken every rom I've ever flashed to it no problem. I wish there was a little partitioning program so I could see if there's extra umounted space there. I just feel like I'm about out of options, I'm not sure what else to try. Maybe the 4.1.2 rescue rom?
Just tried 4.2.1, no go with that one either
Click to expand...
Click to collapse
I'm dealing with the exact same issue on a SGH-T999. It's a 32GB phone but is only registering 11.95GB. When I look at mmcblk0 it says it's unmounted (see attached screenshot). I've done many of the steps you have and still no dice. Not sure where to go from here. I hope you and I get answers to our problems.
halebopper said:
I'm dealing with the exact same issue on a SGH-T999. It's a 32GB phone but is only registering 11.95GB. When I look at mmcblk0 it says it's unmounted (see attached screenshot). I've done many of the steps you have and still no dice. Not sure where to go from here. I hope you and I get answer to our problem.
Click to expand...
Click to collapse
I flashed my phone what seemed like 100 times trying everything everyone told me to do and I gave up. My phone is only 4GB but everything works, oh well! I wasted about 100 hours messing with it and nothing can make this 16GB, or ~11GB anyway. I'm hoping to pick up a bigger SD card when I get back in the states as my 16GB is about full, too.
[FIXED]
shiggins9 said:
I flashed my phone what seemed like 100 times trying everything everyone told me to do and I gave up. My phone is only 4GB but everything works, oh well! I wasted about 100 hours messing with it and nothing can make this 16GB, or ~11GB anyway. I'm hoping to pick up a bigger SD card when I get back in the states as my 16GB is about full, too.
Click to expand...
Click to collapse
shiggins,
I finally figured this out and fixed my phone. I know you tried several things. So, let me run past you the solution that worked for me.
I located the appropriate .PIT file for my phone (S3 T999 UVDMD5). Then I flashed the stock rom with root (i.e. root66 ROM) with the PIT file. After I flashed it with the correct PIT file, I got my storage back. Have you tried this?
If you have and it didn't work, it's probably because you didn't have a good or the correct PIT file for your phone. Let me know if you want further direction and I'll do my best to assist.
halebopper said:
shiggins,
I finally figured this out and fixed my phone. I know you tried several things. So, let me run past you the solution that worked for me.
I located the appropriate .PIT file for my phone (S3 T999 UVDMD5). Then I flashed the stock rom with root (i.e. root66 ROM) with the PIT file. After I flashed it with the correct PIT file, I got my storage back. Have you tried this?
If you have and it didn't work, it's probably because you didn't have a good or the correct PIT file for your phone. Let me know if you want further direction and I'll do my best to assist.
Click to expand...
Click to collapse
I know this worked for you but I would use extreme caution here! Flashing pit files is only to be used as a last resort! ( To recover from a hard brick)...
Recommending to flash pit files when (1) Your phone is fully working apart from minor issues is very bad. or (2) When your phone is not hard bricked...It's not just you I see many posts where people just recommend flashing pit files and they don't realize the consequences Flash At Your Own Risk!!
tallman43 said:
I know this worked for you but I would use extreme caution here! Flashing pit files is only to be used as a last resort! ( To recover from a hard brick)...
Recommending to flash pit files when (1) Your phone is fully working apart from minor issues is very bad. or (2) When your phone is not hard bricked...It's not just you I see many posts where people just recommend flashing pit files and they don't realize the consequences Flash At Your Own Risk!!
Click to expand...
Click to collapse
I did flash a pit file a few times that said it was from a 16GB i9300 but that didn't seem to change my NAND partition size. I've pretty much given up, if I have a lot of extra time on my hands in the future, I may try this whole thing again but in the end I was unsuccessful and I'm usually very persistent in troubleshooting phone issues. Thanks for the advice, everyone, though.