Having trouble using ODIN!!
as now I did the steps and all I have is the phone will boot up through the tmobile screen & S after that screen goes black with the 4 hour button home row lit up.???
As for the recovery I get the following when booting it:
move_check Start..!!
checksum confirmation need_checksum(1300........)
mbr_checksum in header : 4:1
mbr checksum: 533a4003d.........
mbr checksum error
movingand checksum cofirmattion fail
movi_checking done!
update media, please
update media, finished
#manual mode #
appling muti csc
installin multi csc
Much help would be appreciated!!! Have to work all day today which will be slow, so I can work on fixing this. My main question is what type of file is pit & tar? Pit properties is coming up as a window shell comand, Tar opens with unknow app? Not sure if this is my problem or not, I get ODIN to run and complete the steps and end up with the above.
Using Odin V1.3
512.pit
t959UVJI6
did you disable lagfix before you did this? If you didn't have lagfix then I would try to go to stock 2.1: http://forum.xda-developers.com/showthread.php?t=734475
If you had lagfix, its a little more complicated and you may need to use Android SDK. Search for lagfix and flash and the information should pop up.
dont use the .pit file for JI6.. only way I can do JI6 for some reason.
see if that works for you
can you direct me to the files that I need....pda and pit PLEASE...
FriendlyCanadian said:
did you disable lagfix before you did this? If you didn't have lagfix then I would try to go to stock 2.1: http://forum.xda-developers.com/showthread.php?t=734475
If you had lagfix, its a little more complicated and you may need to use Android SDK. Search for lagfix and flash and the information should pop up.
Click to expand...
Click to collapse
was completely stock and I just rooted/unlocked. Swithed Sd cards and stuck in boot loop, after booting up again, trying to recover through ODIN, so probably no lagfix
osugsxr said:
can you direct me to the files that I need....pda and pit PLEASE...
Click to expand...
Click to collapse
just use the JI6 PDA file that you used..... dont add the 512.pit file to it in ODIN
okay found a solution for now, my issue was related to ROM manager with the SD card, kept getting wrong MD5 Sum!! Really pissed me off about this since I was running through ODIN correctly,
Temporary Solution...
Updated the rom with Eugene froyo!! This brought me out of boot looping and now I have a rom on my phone can use it but no downloading or anything. Try to downgrade to stock rom but not luck.
I had the same problem and had to start over again with JFD and the 512 .pit file. Afterward i went to JI6 through KIES and then used Eugene's Froyo ROM with root and took it from there. I had a weird problem where my drive letters went from e and f, to g and h (that's what they are now). I also had a problem with the CW file on my SD card. I eventually had to move it to the phone in order to flash CW recovery. Flashed and am running Nero V3. Best ROM i've ever used!! Highly recommend.....
gtiryan said:
I had the same problem and had to start over again with JFD and the 512 .pit file. Afterward i went to JI6 through KIES and then used Eugene's Froyo ROM with root and took it from there. I had a weird problem where my drive letters went from e and f, to g and h (that's what they are now). I also had a problem with the CW file on my SD card. I eventually had to move it to the phone in order to flash CW recovery. Flashed and am running Nero V3. Best ROM i've ever used!! Highly recommend.....
Click to expand...
Click to collapse
Thats what I think i need to do is reflash Clockwork recovery, not sure how to do so though
Related
I was installing supercurio's voodoo sound kernal using the SGS kernal flasher and my phone is stuck on the Samsung reboot screen. Its saying not enough partion space. I can get into clockwork recovery buy have no idea what to do? The phone is saying convert data partion, not enough space on partion.... I tried to flash this.......Voodoo-stable-5.4.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip
anybody, please help me
my phone keeps rebooting over and over the samsung Galaxy s GT-I9000 screen
somebody please help me
the drugstore said:
somebody please help me
Click to expand...
Click to collapse
You flashed wrong kernel.
EDIT: I made it short above just to let you know im trying to help. You flashed a kernel for GT-i9000, the international model, not SGH-T959, our Vibrants. Go to http://forum.xda-developers.com/showthread.php?t=728929 and download USB driver for your PC. Then go to http://forum.xda-developers.com/showthread.php?t=821625 and download Odin v1.7. And go to http://forum.xda-developers.com/showthread.php?t=870480 and download one of Odin flashable .tar Voodoo kernels, KA6, KA7 or KB1 preferably. Try match it with your ROM just to be safe.
Install the USB driver. Then extract Odin3 v.1.7.rar and run the executable. Leave Odin open. Turn off your phone by pulling out battery, plug USB cord to your phone and to your PC, press and hold volume up and down buttons, and insert battery. You should be in Download mode, and Odin will recognize your phone and display a COM#. Now click on PDA button and select the .tar file you downloaded earlier. And press Start button and wait untill everything is finished and your phone reboots.
The initial boot may take a bit as Voodoo will convert your filesystem into ext4. You will hear voice telling you what's going on. And you should be good to go.
Just in case above instruction doesn't work (I personally never flashed an i9000 kernel), try reverting everything back to stock. Doing so will require a couple of additional files.
Go to http://forum.xda-developers.com/showthread.php?t=734475 and download JFD Odin Image and 512 PIT file. Extract PIT file first. Then launch Odin, put your phone into Download mode, and in Odin press PIT button and select the 512 PIT file you just downloaded. And press PDA button and select JFD .tar file. This time make sure Re-Partition option is selected. And press Start. This take a bit longer than just flashing a kernel, but no longer than 5 minutes. Once you're back to stock (original released in July 2010), flash any other ROM of your choice.
the drugstore said:
I was installing supercurio's voodoo sound kernal using the SGS kernal flasher and my phone is stuck on the Samsung reboot screen. Its saying not enough partion space. I can get into clockwork recovery buy have no idea what to do? The phone is saying convert data partion, not enough space on partion.... I tried to flash this.......Voodoo-stable-5.4.2-Froyo-2.2.1-GT-I9000-unsigned-update.zip
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=848737
I did the exact same thing just a few days ago. I asked on this forum and got some great help. I downloaded the new Odin Software v1.3 and also downloaded the stock Vibrant software. Put them all on your computer,extracted, and hold down just the 2 volume keys then plug in your usb cable. This will put you into download mode. Look in the Odin program and it should recognize your phone, if it doesnt then youll have to download the drivers again. Its in the Vibrant Bible. After all of that upload the Rom to the pda section in Odin and make sure you dont click anything else then push start. This will take a few minutes to load then your phone will reboot and your back to stock. This worked for me hope it works for you.
Thanks everybody, I used Baywolf's, hope his name is spelled correctly, Vibrant toolbox and got into Odin and reflashed my phone back to 2.1 stock, them Samsung Kies to 2.2 stock. Thanks for the replies
im having the same problem except that when i reflash my phone to stock and try to turn on my phone again it wont...i have to reflash it everythime i want to turn it on and it deletes everything everything
Hello good people,
Goal: Upgrading T959UVJFD (2.1) to T959UVKB5 (2.2) w/ Voodoo Lagfix & Root
Tools available: Odin3, 512.pit, both stock roms, KB5+Voodoo kernel
Problem: I can accomplish everything but properly flashing the KB5+voodoo kernel.
Issues:
"Not enough space on partition"
Tried to partition through Clockwork Recovery Mod, and now have MBR checksum errors
Please help:
How do I correct the MBR checksum errors on the internal SD (I've tried Partition Manager on PC as well as chkdsk /r)
How do I properly install Voodoo lagfix when I don't have enough partition space, and attempting to fix that drives the phone wacky?
Additional Notes:
There is no vital information or files on the phone.
Thank you for your time. =0)
Shennanigans! LOL i love that werd! Man i got stories bout that haha!
Usually if I'm unsure i just start from scratch. Skip any step if you feel your phone is past that point. This is just what I would do:
ODIN to stock: http://forum.xda-developers.com/showthread.php?t=734475
Root - http://forum.xda-developers.com/showthread.php?t=723479
Gain CWM recovery - http://forum.xda-developers.com/showthread.php?t=870480
Flash ROM of choice(i assume ur going for this?:http://forum.xda-developers.com/showthread.php?t=1036193 if so keep in mind you'll wanna use the CWM flash as stated in OP. Good luck!
Looks like you have the same issue as mine. can you post your partition layot using parted?
Here is how you fix your problem (and any problem) on the Vibrant. Make a nandroid back up and backup through titanium. Then copy the whole int sd card with all that data on to the computer.
then: Depending on your problem you can follow this guideline OR--- you can just do the JFD only depends on what your phone is doing to you..........
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin (use 1.7 or higher), plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone Then> download Rom Manager and then> you can flash your new Rom.
doing this method will get everything back to normal and the phone will work flashing a new rom without problems just like it did right out of the box
good luck
Thanks Everyone
Hey guys,
Just as an update, I used Odin and got everything stock 2.2, then I followed the instructions in a stickied thread to get the "green" version of ClockwordMod on it and have it rooted.
I then installed the Dead Horse Kernel which has been a blessing. I don't know if that MBR error is still going on, but it hasn't caused me any issue.
I suggest everybody who is looking to have rooted stock 2.2 w/ some nice extras go w/ Dead Horse... doing straight up Voodoo Lagfix will just cause you grief if you're not an advanced person.
Thanks for the replies. I'll be bothering you all again in the near future. =oD
Awesome! Glad you got it werkin!
Earlier today I flashed cyanogenmod 7.1 onto my phone. It was ok, but I didn't like some of the styling, so I decided to change back. rom manager wouldn't let me download clockwork mod recovery, so i tried odin, and now it won't get past the android system recovery. can anyone help? Here is the error message:
E: Can't mount /dev/block.stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA
copy default media content failed.
someone4guitar said:
Earlier today I flashed cyanogenmod 7.1 onto my phone. It was ok, but I didn't like some of the styling, so I decided to change back. rom manager wouldn't let me download clockwork mod recovery, so i tried odin, and now it won't get past the android system recovery. can anyone help? Here is the error message:
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
I have gotten that dbdata error message before, it was written in red.
I don't remember how I fixed it since it was long ago, way before CM, but the thread is around the forums somewhere.
Anyway, don't worry, you will be ok.
did you use the correct pit and tar? repartition? maybe the issue is you are going from cm file system to jfd.
look into eugenes froyo that doesn't brick.
Odin, go get the AIO Tools or something and do the flash to stock option from Download mode and check the repartition as well.
SamsungVibrant said:
I have gotten that dbdata error message before, it was written in red.
I don't remember how I fixed it since it was long ago, way before CM, but the thread is around the forums somewhere.
Anyway, don't worry, you will be ok.
did you use the correct pit and tar? repartition? maybe the issue is you are going from cm file system to jfd.
look into eugenes froyo that doesn't brick.
Click to expand...
Click to collapse
I used s1_odin_20100512.pit and T959UVJI6.tar as my tar file. I have tried checking re-partition but it doesn't change anything. Could you explain what the thing about the cm file system to jfd is?
someone4guitar said:
I used s1_odin_20100512.pit and T959UVJI6.tar as my tar file. I have tried checking re-partition but it doesn't change anything. Could you explain what the thing about the cm file system to jfd is?
Click to expand...
Click to collapse
JFD is the Original 2.1 rom that the phone came with (the J refers to year j=2010) the F refers to the month (June) this was the release of this software build
JI6 (ji6) is the later updated version of the 2.1 rom JI6== 2010/ Sept
When you Odin back to stock it is preferable to use JFD instead of JI6. Make sure to ck repartition, Download Rom Manager >then root >then flash new rom
JFD (for me) never gives any problems, I have had a couple of fails with the JI6 so since you are flashing back to 2.1 just to clear out the old software It is just better to use JFD the original stock rom.
Really doesn't explain everything I think you want, but this is what is important.
This has happened to me several times. Odin using Eugene's "Froyo that doesn't brick" (just search for it) check repartition when odining. This will repartition everything back to normal. You can do whatever after that. Flash Cwm and a new rom.
Sent from my SGH-T959
someone4guitar said:
I used s1_odin_20100512.pit and T959UVJI6.tar as my tar file. I have tried checking re-partition but it doesn't change anything. Could you explain what the thing about the cm file system to jfd is?
Click to expand...
Click to collapse
they use different file systems and when you try to odin back you run into problems, I think your answer is eugenes froyo that doesn't brick, flash that, then you should be back to good.
okay, I have been on here several days trying to find a solution to this..., I know I am the one that borked it, now I am asking for help in understanding what I need to do to fix it... here is a list of things that I know happened...
A. I rooted the phone, added CWM, created a backup.
B. installed ROMManager
I had seen things on the MUINE ROM, saw it in the list for the vibrant so what the heck right?
C. installed the MUINE from the ROMManager app, rebooted, found that it could not "See" T-Mobile...
D. checked here on issues with the current version of MUINE ROM issues... didn't see anything, so I made sure that it was in USB debug mode, and tried to restore the backup I had made earlier... now comes the problem... , I think that when I tried unsuccessfully to do that with CWM, I tried ODIN, and the re-partition box was ticked... and wiped the internal SD and the update.zip etc, and put it into usb debugging off...
since then, I have tried the revert to stock and root thread, the update that does not brick etc... the AIO Vibrant toolbox tells me that USB Debugging is off, and here is the info on the recovery screen...
Android system recovery <2e>
-- Movi_check Start..!!
checksum confirmation need_checksum[1636849899]
MBR_Chksum in header : id
MBR checksum : 4206DE4BFAA052703D8107823C7EDDAF
MBR Checksum Error
Movinand ChecksumConfirmation Fail
--movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
any help is appreciated...
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Alex9090 said:
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Click to expand...
Click to collapse
I am just trying to boot... it goes through the vibrant splash, the galaxy s splash, the tmobile sound and pink splash, and then black... if you touch the capacitive keys, they light up and stay that way... other than that unresponsive... ODIN shows no errors when trying to flash it too... but when it tries to boot after, it comes up to that recovery... I have also from the <2e> recovery screen tried "reinstall packages" but to no avail...
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Alex9090 said:
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
okay, so, load Eugenes rom, and turn off auto reboot, then when Odin is done, reset to the JFD .pit and pda, and turn auto reboot back on for that one?
okay, got it... the load JFD after the no brick without rebooting is what did it, THANKS!!! it probably should be noted when doing this to turn off the partitioning in odin, and the auto reboot and once odin has completed, then remove battery and USB, then bring it into download mode without letting it power up into no brick first... that was the step I was missing, thank you so much for the quick response!!!
Seannon
So my vibrant won't boot up. I've tried odining it back to stock, and no matter what I do, it will almost get to the galaxy S screen (freezes as it is forming the S). Download mode and recovery mode both work.
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Sk3tchy said:
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Click to expand...
Click to collapse
The reinstall packages fails. It says: "can't open /sdcard/update.zip" (no such file or directory).
Woodrube said:
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Click to expand...
Click to collapse
I don't have the option of wiping the Dalvik in recovery. I think its because it went back to the default "Android system recovery <2e>"
I tried wiping everything, but when it boots, it goes to the vibrant screen, then to the tmobile screen (the boot sound works), but then, the screen turns black and it goes back to the vibrant screen again (and it just keeps looping).
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
cashmundy said:
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
Click to expand...
Click to collapse
So I flashed ka7, and it gets past the S logo now, but then it turns black and now it says "Kernel Panic" upload mode:
RST_STAT=0x4
PMIC_IRQ1=0x0
PMIC_IRQ2=0x0
PMIC_IRQ3=0x0
PMIC_IRQ4=0x0
PMIC_STATUS1=0x40
PMIC_STATUS2=0x2C
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Woodrube said:
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Click to expand...
Click to collapse
I tried using the toolbox and reflashing the stock rom, but it just gets to the t-mobile "stick together" screen, then screen turn black, then it goes to the battery charging screen.
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
cashmundy said:
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
Click to expand...
Click to collapse
But I can get into download mode. And which sbl should I flash?
Probably the closest-to-stock Froyo SBL you can find.
I'm using a GB SBL from this thread, and he has Froyo also:
http://forum.xda-developers.com/showthread.php?t=1117990
I got stuck in this loop a few months back flashing back to stock from CM7 when Odin froze.
I could get to Download Mode and Stock recovery but had the same error when attempting to "Reinstall Packages" from recovery. The internal SD partition had corrupted.
I flashed Eugene_2E_JK2_Froyo with Odin, which fixed the Internal SD.
If you follow the write up on unbricking when you have the little triangle and phone error on your screen it will get you out of this one.
Your bootloaders are not the issue here. 2e Recovery isn't seeing the Internal SD Card and that it what is causing the hangup on boot.
Yeah, probably just flashing a decent kernel would fix you up, but unless you can find an Odin kernel file, you need to do the whole rom.
BTW, with Linux, you can use
tar -tf <rom file> if you want to see what's in a rom.
You can download the Odin flashable Overstock Kernel which contains the red recovery and flash it. That would give you the ability to format the internal SD and then Mount it to your PC through recovery and copy a Rom over to flash.
Otherwise the Unbrickable Froyo I mentioned before will also work.
The only thing you can do when stuck in a boot-loop, if the previous suggestions don't work, is to just reflash it. You can flash back to stock easily using Heimdall One-Click. http://forum.xda-developers.com/showthread.php?t=1278683
We're missing some info here. What ROM were you using before you flashed back to stock? Did you use a pit file in addition to the pda file in ODIN?
If you were using an ICS (android 4.0.x), flashing back to stock and didn't use a stock pit in addition to stock pda, it would definetly be giving you problems. ICS uses a different partition scheme then does stock (which is on android 2.1). The pit file tells odin how to partition your phone.If you're flashing from Froyo, then this should not be relevant as it uses same partition scheme as stock.