Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.
Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!
Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................
The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.
Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.
Doesn't work to flash with odin either?
xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.
sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M
Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...
Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??
Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.
Related
Okay, I know there is many post about this, but none seem to answer my question or help me. I have a Vibrant and I've been searching this site along with google to help fix my phone.
I brought it off a friend so warranty won't happen since T-Mobile is being asses. My phone is suck on the black screen after it passes the big S logo. It stays black, and I get 4 lights bright on the buttons. I've reflashed my phone with Odin and it has not worked. I think it correctly as well. Com3 was on, ran the stock Vibrant with Pitt and Tar with PDA one. That had only got my phone off the complete brick that my phone had gone through, when It wouldn't even turn on.
I got the brick off and now I'm stuck with this program. I did have a one click root fix and I was trying to mess around with clock work. To help answer some questions. No, I can not boot into recovery mode. Yes I have cleaned and wipe out cache. Yes I can go into Download mode, but its pointless since odin doesn't do much for me. No I can not go into the phone since the black screen is there and no I can not flash a update file for some reason.
Saying that, I would be grateful for some help and before hand I thank anyone who comes across this even if they don't help, just for taking time to read this and maybe referring someone else to help me or even pointing me in the right direction. Thanks and once again PLZZZZZZZ HELPPPPPPPPPPPPPPPP.
No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?
zephiK said:
No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?
Click to expand...
Click to collapse
Okay. One thing I notice when I try to put my phone into the Android system recovery it says this "
-- Movi_check start .. !!
checksum confirmation need _checksum [1301305579]
MBR _Chksum in header :4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MBR Checksum Error
Movinand Checksun Confirmaton Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti - CSC ...
Installing Muti - CSC "
Another thing, I hit reinstall packages and It says "
-- install from sdcard...
finding update package ...
opening update package ...
E: cant open /sdcard/update.zip
(no such file or directory)
installation aborted.
the drivers I use are the samsung Vibrant drivers for windows 7 64. I know it works because the phone before didn't come up when I didn't use the driver. It always failed and when I install it, than it read my phone. When I connect the phone to the computer, the phone does read it and on odin, it says com 3 in yellow. I than Install pitt and install tar.
The tread you sent me too, I actually went through there before. Both of those drivers didn't work but I found one for windows 7 and it started working for my computer. I could tell it works because the computer actually reads the phone and so does odin. Like I use odin right because it goes through the phone and than says pass at the end. so like WTF lol. I'm pretty sure I'm doing it right tho
Another thing. I used odin a few seconds ago, got the phone to run and it went through the green bar and a blue screen now saying reset came up. My phone than went into androids recovery mode but it started to wipe out data. When doing so, the data said wipe fail. It booted up and now back to the start. Black screen, 4 panels on the bottom lit up and nothing to do.
I'm starting to think it has to do with clockwork I did a partition in it and every since than my phone has been doing this blackscreen with 4 lights.
ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work
same thing here, know idea, odin says everything passed but still the black screen and four buttons. i also noticed that the sound and tmo splash screen are not in sync. no idea ???? help would be great!!!!!!!!!!! same errors though. also from the partion feature in clockworkmod.
i assume your on windows i don't keep up if there is a working version for mac. Anyway, make sure your update.zip is just named update DO NOT add .zip yourself or the phone for what ever reason sees .zip.zip. I would also go ahead re download your odiin files just to make sure non of them are corrupted for what ever reason.
files all check out good, i can't gain access to the phones sd, i have flashed this thing with every checked build i could find, all with the same result. the master boot record is not adding up.? still have know idea.
have you tried using this.. http://forum.xda-developers.com/showthread.php?t=740558
this work for me and was able to flash to stock..
somebody please help I'm experiencing the same problem as the OP? can somebody point me in the right direction I've been looking for hours
Instead of making us read the entire thread perhaps you could summarize your specific problem.
My initial impression goes like this.
1. Get into download
2. ODIN back to STOCK 2.1
Run odin in admin mode
Use rage against the cage
After getting back to stock Recovery 2e go ahead reroot and flash away
Sent from my SGH-T959 using XDA App
Don't know if this is still an issue, but here's how I fixed it.
http://forum.androidspin.com/showth...yo-That-does-not-Brick!-Downgrading-Is-Fine-)
Downloaded this file knowing it wouldn't work, Had ODIN flash it and got into this weird recovery screen. Just pulled the battery and then flashed back to stock using ODIN.
Helped me out.
Use 512 .pit and True Stock 2.1 from this post
http://forum.xda-developers.com/showthread.php?t=747335
And quit messing with your phone! lol
This is how i fixed mine too, my phone would go through a seemingly normal start up, but the UI would never load and it would stay on a blank screen.
Flash Eugenes373s froyo that doesnt brick. once it brings you to the recovery screen, pull the battery and once again use odin to flash back to stock. the phone should boot up now.
mnm0071980 said:
ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work
Click to expand...
Click to collapse
Hey i just encountered the same exact problem four days ago except i flash with odin it says pass but im still stuck on a black screen after the s logo my problemwas encountered by tryig flash a kernal. Please tell me that u found a solution
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
I had that happened before with odin 1.2. Updated to 1.7 and everything worked afterward.
Sent from my SGH-T959 using XDA App
yeah used both versions
sometimes using a different computer solves the problem for me.
Had this happen too. In my case switching to a USB port in the back of my PC rather than one of the ports on the front of my PC case fixed the issue. Try Odin'ing with your other USB ports?
Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help
having same problem
I'm having the same problem. What is a corrupted JFD file and how do I fix it?
Ran into the same issue. I checked "Phone Bootloader Update" in odin 1.82 and it finally worked. Not sure why, but I'll take it.
Bandage said:
Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help
Click to expand...
Click to collapse
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...
^ check my signature for going back to stock thread. If you have an operational phone, you should be good with my guide.
ccole22653 said:
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...
Click to expand...
Click to collapse
Its the .tar file used for pda sometimes it gets damaged when you download it just need to redownload it
Sent from my SGH-T959 using XDA App
Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
I finally found what the problem was, my stock tar file was not completely downloaded and was 180MB vs 291MB what it should have been. Redownloaded, tried again and it worked perfect. To those that still have the problem, try re downloading the files instead of trying the same one over and over, worked for me ;-)
hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.
blemish31 said:
hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.
Click to expand...
Click to collapse
I have been having the same problem here. I am only able to enter download mode, my phone won´t boot, not even cwm.
I have been trying to install a new rom via Odin but it gets stuck at factoryfs.rfs , I have tried everything even all said in this thread it still wont work. Also tried checked and downloaded several times the files as you mentioned.
Please, if anyone knows what else to try.
PS: I also tried installing other roms rather than darkys resurrection and they would all get stuck in some point during the installation via Odin, really wierd, please help!!!
Dude, you'd be better off starting a new thread in the Q&A section.
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.
dpaul007 said:
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.
Click to expand...
Click to collapse
Actually if you read up on DarkyRom, the Darky team makes Odin .tar's of their base roms. So yes you can Odin a custom rom. It's actually easy to make a Odin tar ball of any Samsung TWiz based rom on your phone.
Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
What files are you flashing?? Are you flashing with or without a .pit?
Here is a guide from XDA for Flashing. Its easy to follow and ive never had an issue with it. Good Luck.
http://forum.xda-developers.com/showthread.php?t=1307637
I just plugged my usb into the back and i got past it. sat for the last 2 hours troubleshooting.....
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
I can't ODIN back to a stock ROM.
I forgot to take disable Voodoo( I KNOW LMDSKDJ) and I ODIN like regularly,but it got stuck after 30 minutes of me waiting. I did the pull battery trick, and it didn't boot up, so I did the take out the battery and hold Volume and put back the battery trick.
I managed to get back to Download mode, but after trying to ODIN several times, it always hang at either "Get Pit for Mapping" or modem.bin, or not load at all.
I even tried to partition, but to no avail.
I've looked up several cures for this, but I can't simply find one. I hope I didn't eff up my phone.
Maybe your odin.exe is broken. Try redownloading it, otherwise it might be your pit file or stock rom that is corrupt.
One thing to try if Odin isn't working for you. Repartitioning seems to be the way to fix it, but Odin seems to get confused if there's a micro SD card when you repartition. Try turning you phone off, taking out the SD card and the SIM card while you're at it. Put the battery back in, get into download mode, and reflash stock. This helped me when I was having trouble getting back to stock from the horrible 2.2 off of mini kies. Not sure if this is the same issue you're having but I thought I'd throw it out there.
I don't know where you got the PIT and PDA files from but try this place:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
I would download all from there, it worked for me a week ago when I almost bricked my phone
Also, make sure only two check boxes are checked, noting else!
Good luck and update with progress!
If u flashed dow kernel without disabling voodoo then ur phone is bricked and u can't odin back. Trust me I've tried and to no avail, I really need a fix for my phone.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Usually persistance is key.
Take everything out (sim, battery, sd) and boot up ODIN with all the files ready to go. Hold the up and down button on your phone and then connect it to your computer. Put the battery in and let go of the volume buttons and that should put you into download mode. Odin away. If it doesn't work, keep trying. I bricked my phone pretty badly to the point where when it was plugged in, it wouldn't even charge, but doing this, I was able to get into download mode and get it working. It took a while to work, but it did work.
^^^
I had the same happen to me with an update on the dead horse kernel. Odin wouldn't recognize the phone the first few times and when it did it would hang. I would suggest that every time it does not flash successfully, unplug, close and re-open odin, and start download mode over. Start fresh every try.
I have never bothered disabling lagfix when odining back and have never had an issue..I don't believe lagfix or voodoo in general is causing problems for odin .
And I have used odin many many times
After re-downloading ODIN and the pit/tar files, I managed to successfully ODIN back to the stock ROM.
I would imagine it was a corrupted ODIN, but I've been using the same one for mulitple ODINs.. lol
Thanks everyone! :] This is why I love this board!
I'm glad you made it. There is a Thanks button for the guys that provided helpful information as a sign of your appreciation.
Cheers!
Sent from my SGH-T959
I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!
If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.
why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .
Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin
charge your phone ?
bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!
download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .
come back report resoults if not we help more .
also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?
The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.
To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.
from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...
Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it
Good advice, I will work on this and get back to you later tonight.
Thanks again!
sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy
if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that
Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.
Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?
you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.
Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374