Related
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.
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
Okay, so I had a thread before about getting EB13 on my phone.
Well, at this point, I don't care about that, I just want my phone to work.
Here's what happened, I tried running the Samsung EB13 flash and it failed (my phone got stuck on a green screen)
Now, it won't boot (stuck on Samsung screen)
So I'm trying to use Odin to flash back to stock, but it gets stuck at <ID:0/005> SetupConnection..
PLEASE tell me this isn't bricked?
If it's not, how can I fix it?
Any help would be greatly appreciated!
EDIT: This time Odin froze on the next step, Initialization..
What are you coming from (DK28, DI18, etc) and which stock are u ODIN'ing back to? (Hopefully DI18). Also, check ur USB cables, I find that is a common problem when things don't go as planned. (At least it has been for me.)
Sent from my SPH-D700 using XDA App
garr741 said:
What are you coming from (DK28, DI18, etc) and which stock are u ODIN'ing back to? (Hopefully DI18). Also, check ur USB cables, I find that is a common problem when things don't go as planned. (At least it has been for me.)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I had stock (rooted) DI18 installed, and now I'm just trying to use Odin to flash the stock kernel (since I assume I can use my CWM backup to fix everything else?)
If not, I'll try using a full tarball for DI18 (if you think that's what I should use instead)
Follow the instructions here-
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=559&AT_ID=351569
mattallica76 said:
Follow the instructions here-
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=559&AT_ID=351569
Click to expand...
Click to collapse
I did follow (basically) the same instructions.
By that I mean I wasn't looking at those, but I did the same steps.
Problem is it crashes pretty early on after starting.
Something wrong with the EB13 utility & Odin's connection to my phone.
Very strange.
Starting to freak out though.
s84471 said:
I did follow (basically) the same instructions.
By that I mean I wasn't looking at those, but I did the same steps.
Problem is it crashes pretty early on after starting.
Something wrong with the EB13 utility & Odin's connection to my phone.
Very strange.
Starting to freak out though.
Click to expand...
Click to collapse
Try re-installing the utility in the link I gave you, and try again.
Try ODINing back to DI18 proper, full tar. I also had issues with the EB13 utility and while I didn't brick my phone, maybe if you're having issues it's best to do DI18 then update.zip?
(As long as you can get into download mode, I think it's safe to say you're not bricked..)
Okay, so I used Odin with the EB13 tarball and it started going, but seems to have hung at factoryrfs.rfs
There was a progress bar on my phone, but now the screen is just solid cyan and Odin's progress bar isn't moving.
Any ideas?
Assuming this step just doesn't take a long time.
Kawinma said:
Try ODINing back to DI18 proper, full tar. I also had issues with the EB13 utility and while I didn't brick my phone, maybe if you're having issues it's best to do DI18 then update.zip?
(As long as you can get into download mode, I think it's safe to say you're not bricked..)
Click to expand...
Click to collapse
He already tried that.
mattallica76 said:
He already tried that.
Click to expand...
Click to collapse
He said he just tried the kernel and asked whether or not he should do the full DI18 tar.
Which USB cable are you using? If it's the stock cable that came with your Epic, ditch that ****. They suck! Go get a different USB-A male to micro USB-B male plug, such as the Gigaware cable that Radio Shack sells. I can personally attest to the fact that the OEM cable that Samsung/Sprint provide is not very reliable: once I switched to the Radio Shack / Gigaware cable, my flashing problems cleared up.
Kawinma said:
He said he just tried the kernel and asked whether or not he should do the full DI18 tar.
Click to expand...
Click to collapse
OP states he attempted to flash back to stock, didn't say anything about kernel.
AmericanJedi001 said:
Which USB cable are you using? If it's the stock cable that came with your Epic, ditch that ****. They suck! Go get a different USB-A male to micro USB-B male plug, such as the Gigaware cable that Radio Shack sells. I can personally attest to the fact that the OEM cable that Samsung/Sprint provide is not very reliable: once I switched to the Radio Shack / Gigaware cable, my flashing problems cleared up.
Click to expand...
Click to collapse
I'm using a cable I had from having bought a Micro USB charger. I think it's a Palm one.
Currently trying to Odin DI18, but my phone is back to not being recognized.
Maybe both these cables are no good...
Okay, I'm trying the DI18 tarball, and my phone just goes to a solid color screen on a random step (seems to always be zImage or factoryrfs.rfs)
Is this really just 2 bad cables?
Could always try another USB port. I've seen posted in threads time and time again that users having a problem would then change ports and things just worked.
nikon120 said:
Could always try another USB port. I've seen posted in threads time and time again that users having a problem would then change ports and things just worked.
Click to expand...
Click to collapse
I've tried that as well.
Even tried 2 different computers.
Always ends up with my phone going into a solid color screen...
Why do I get a feeling this is gonna end up being a full brick.
I do have the equipment protection policy on it, so if I just tell them I lost it, any idea if they'd replace it?
Since I assume bringing in a phone with CWM would cause my warranty to be voided.
s84471 said:
I've tried that as well.
Even tried 2 different computers.
Always ends up with my phone going into a solid color screen...
Why do I get a feeling this is gonna end up being a full brick.
I do have the equipment protection policy on it, so if I just tell them I lost it, any idea if they'd replace it?
Since I assume bringing in a phone with CWM would cause my warranty to be voided.
Click to expand...
Click to collapse
I think since you were trying to update using the Samsung tool, it would be a covered replacement in the Sprint store. Even if you didn't use the Samsung tool, given the roll out you should still be covered--regardless if you had the insurance or not.
may not be helpful but worth a shot.. i have this issue everytime i odin.. (not exactly what you have but phone is stuck on restarting adb agent or something)
basically i have ms security essentials and windows firewal turned out..somehow .. (i have no clue) .. while they are running odin will wait forever.. the moment i disable both ms sec essentials and windows firewall it would work... not sure if this is the same case but u might want to give it a shot.
Alright, crisis averted.
Seems I got lucky one time and Odin went through and restored DI18 successfully.
Then I applied update.zip and am now happily running EB13
Thanks for your help everyone!
Just a tip for the future: I've found that when I ran the newer cwm and ext4, every time I tried to odin a stock tar, it would fail if I didn't check the re-partition box. Posssibly doing the same may have helped you.
Sent from my SPH-D700 using Tapatalk