I Flashed my Vibrant through Rom Manager to Froyo 2.2 from eugene373 and sombionix.
After flashing to both ROMS for Froyo I wanted to revert back to 2.1.
I tried to put sombionix 1.3 eclair ROM back on to my phone using clockwork mod.
The flash was not successful it stopped in the middle but the phone came on with a Force close error of an android process.
I tried to reboot through adb reboot recovery with usb debugging enabled.
The phone shut down like it would reboot into recovery mode and now it gets stuck on boot at the samsung vibrant screen.
I tried to use ODIN to flash back to the stock Rom but the phone is recognized in ODIN but will not flash.
ODIN sees the phone but will not get past flash analysis. (Sat for 8 Hours)
I believe this is the definition of bricked. Please Help!!!!!
Were you in download mode when you attempted to flash with Odin?
ODIN as administrator
Don't know if this will fix it, but it worked for me.
If you are running Windows Vista or 7 make sure to run as administrator when opening ODIN. Just right click on the icon and select 'run as administrator' I would reboot first just to clear everything.
This helped me when I was stuck at 'file analysis'
Good luck.
I Did not say download mode but it was recognized in ODIN
If your phone wasn't in download mode, (shows an android digging with the text "downloading, do not turn off target" than odin will not work. Download mode allows your phone to communicate with your pc while not booted into your os.
Sent from my SGH-T959 using XDA App
So Are You Ssaying I am SOL?
He is saying boot into download mode then use odin.
Cant get into Download Mode Thats why im saying that i am OUt OF Luck
Your phone is hardware locked? AFAIK unless you are hardware locked you can always get into download mode. The non HW Locked models are basically unbrickable.
I'm having the same problem... I'm actually in Download Mode right now... and ODIN sees my phone, BUT its been sitting on Download Mode with noting happening for the past 15 minutes and ODIN says this
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
Any Ideas??? I don't know what to do now.
BabyBoi.JN said:
I'm having the same problem... I'm actually in Download Mode right now... and ODIN sees my phone, BUT its been sitting on Download Mode with noting happening for the past 15 minutes and ODIN says this
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
Any Ideas??? I don't know what to do now.
Click to expand...
Click to collapse
Remove the USB from the phone, remove battery.
Re-open Odin.. this time, PUT the pit/tar etc and preload it in ODIN before you plug in the USB.
Once you finish preloading it.. hook your phone up onto the USB and get it into download mode. And once its detected by Odin, hit Start.
zephiK said:
Remove the USB from the phone, remove battery.
Re-open Odin.. this time, PUT the pit/tar etc and preload it in ODIN before you plug in the USB.
Once you finish preloading it.. hook your phone up onto the USB and get it into download mode. And once its detected by Odin, hit Start.
Click to expand...
Click to collapse
Awesome thanks. That worked
Well Im Glad Someone GOT SOME HELP!!!
Related
Yesterday, I installed FFC, and wanted a fresh install so I formatted sd and tried to flash JI6 with it, but flashing failed and whenever I boot, I get the phone icon with dotted line to a computer icon which has an orange exclamation icon in the middle.
The button-based boot into download mode failed. So I made a jig using a microusb plus 120k, 180k, and 1k resistor. But the method still only boots into the same orange exclamation icon from phone to computer icon. It sounds like it's completely bricked. Is there a snowball chance that samsung would still fix this?
Help would be appreciated.
Thanks, Paul
Okay, there are two methods to fix this: first method is more reliable.
First download Samsung Kies, this gives you correct drivers and makes sure you never have a flash that gets interrupted because of bad drivers. Here is the link to samsung kies:http://downloadcenter.samsung.com/content/SW/201101/20110124222256530/Kies_Mini_For_Vibrant_11011_4.exe
1. Now, take out your battery
2. Put the USB cable that is connected to the computer in.
3. Hold down the two volume buttons while keeping the USB cable in
4. Put the battery in while USB cable is in and volume buttons are still held
5. You should find yourself in download mode.
6. Now, put the pit file I have at the end into PIT and the Tar file I have at the end into PDA, happy flashing.
Second method (unreliable but easier)
1. Install Samsung Kies.
2.Having Odin open, plug in your phone into the cpu using USB cable.
3. Hope that Odin recognizes the device, if it does be happy and flash.
4. Now, put the pit file I have at the end into PIT and the Tar file I have at the end into PDA, happy flashing.
FLASH JFD INSTEAD OF JI6 TO GO TO STOCK, JI6 HAS ALWAYS GIVEN ME PROBLEMS, JUST USE JFD. HERE IS THE LINK: http://sourceforge.net/projects/stockodinjfd/files/T959UVJFD.tar/download HERE IS THE PIT FILE: http://sourceforge.net/projects/stockodinjfd/files/s1_odin_20100512.pit/download
Thanks Ali, second method is the only one that worked, however, after flashing (according to odin, it was successful)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> modem.bin
<ID:0/005> factoryfs.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
it reboots and shows the Vibrant text logo and is stuck there for 10 minutes.
Is this normal?
flashed JI6 and now it's working, i think there might be something faulty with the JFD you posted, that or the fact that sourceforge kills my download every 20 second, i had to use a download manager.
anyway, thanks
Tmobile t959 samsung galaxy s vibrant
Hey guys, I had version 2.2 on my phone. I had this phone for about 1.5 years so I figured, why not update a custom flash?
Anyways, so I googled a friendly newbie guide, as I have no experience with phones. I used odin with a custom flash and it failed giving this message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I cant use my phone at all. I can get back into downloading mode, with the yellow android shoveling, but no matter what i load for a rom file, it always gives me an error. I tried searching endlessly, and I cant figure anything out.
Please, someone, I would really appreciate it if i could get some help. Is there anything I can try? This didnt work from the start...I first thought it was my usb drivers i even updated them but I dont know why I keep getting this fail error message:
Can a mod please delete this? I was doing the stupidest mistake...I was selecting file under PHONE instead of PDA....and I just saw in a youtube video someone selected PDA....as soon as I did that it worked!!!
really bricked phone is solved only by service tools
is not bricked because a really bricked phone will not boot in download mode it's like dead better is to say "is not booting" and the way to solve a "bricked" phone is to flash a stock rom that surely works you have to try many times because you don not know what rom was previously on the phone
1.get a stock rom on sammobile
2.also get corresponding Odin an pit file from there
3.flash by Odin in download mode
if not working try another rom also check if you have Android SDK an Kies make sure you have these tools- you need adb interface working and samsung drivers installed
when in download mode open Device Manager start/run/devmgmt.msc and check if you have adb interface active if not install Odin and SDK then restart PC and try again in download mode...
(don't do anything until you see something like this is Dev Manager -you see this only when phone is connected to PC yes in download mode)
tips
-pit file tells Odin how to flash files on phone in what order and how to so unpack rom and check if you see at least 3 md5 files : CSC/Modem/PDA not all roms are complete don't use a pit file until you have these 3 files in archive
-if Odin says "done" but phone is not booting try to enter recovery and (should work if you downloaded a complete rom ) ...and wipe data/cache/Dalvik-cache then reboot
-if you see ADB Interface connected in Dev Manager it means your phone is in download mode and is not bricked so can be solved ! do not believe me just try !
-if you do not see this install (again) everything/ use another computer and try again! if you don't get a sign this is bricked and send it in service don't lose time
I have a Samsung S3 on O2 (UK). Yesterday I got a system update notification and I downloaded and installed the update (it was quite big, about 300MB). There were no issues during the install and it restarted fine when it finished, however about an hour later the phone just restarted itself on its own (it was in my pocket) and then just kept looping the restart process over and over. I couldnt get the phone to get passed the logo screen. I tried removing the battery, sim card, etc but nothing helped. I read in a post here to try to use the "Recovery Mode" to restart the device. I did that and it worked, I was able to get the phone started again, but about half an hour later it did exactly the same thing but this time I couldn't get into recovery mode anymore! I read a few more posts on this forum and it looked like the update had soft bricked my phone. I could get the phone into download mode so I thought I would try using Odin to re-install the stock firmware. I followed the instructions on the post to the letter, downloaded the correct firmware from Samsung, installed the USB drivers for the phone but when I tried to use Odin it just said the the update failed. Now when I turn on the phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I have read a few posts on suggested work arounds but no matter what I try Odin always just gets stuck on "Nand Start Write!!!". I have tried re-installing the USB driver, using a different cable and even a diff computer but always the same.
Can anyone help? This is really annoying. I have never tried to do a root or mess around with the phone so it seems really odd that something like this would happen following a standard update
P.S These are the instructions I followed when I tried to re-install the official firmware - http://forum.xda-developers.com/showthread.php?t=1671969
Boot to recovery factory restore then flash stock firmware via Odin .
jje
JJEgan said:
Boot to recovery factory restore then flash stock firmware via Odin .
jje
Click to expand...
Click to collapse
Its not letting me boot to recovery mode anymore. I can boot to download mode but when I try to boot to recovery mode it just keeps looping the startup screen which at the moment is the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Then flash a stock ROM image through Odin
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
ascottuk said:
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Hmmm. When I connect the phone it makes the sound in Windows that the phone has been connected but then in Odin the com port is blue not yellow. Does that mean that it has not detected the phone properly?
Glebun said:
Then flash a stock ROM image through Odin
Click to expand...
Click to collapse
This is the message I get in Odin when I try to flash the stock firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
You need a service centre with that comment Nand Start Write! .
jje
Yeah, you probably have corrupted NAND :/, take it for warranty repair, they will replace the mainboard. :thumbup:
Sent from my GT-I9300 using xda app-developers app
Info:
Samsung Galaxy S 3 GT-I9300 (Europe, Denmark)
everything is stock
I used mskip's unified toolkit for my phone's model and tried to root. I tried searching for this problem but haven't come across one yet.
1. I installed necessary drivers for toolkit to work.
2. Chose Root/Unroot Options > ALLINONE (insecure boot, recovery, root, busybox, restore files)
3. Odin opens and I follow instructions to load the corresponding tar file.
4. I press Start. Odin's message field says:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
5. Odin is stuck here and the phone's screen says "Downloading..." I have left it for 1.5 hours and it hasn't rebooted. I think the file also has not been pushed onto the device.
6. I exit out of Odin, then hold the phone's power button to turn off.
7. I reboot and the phone loads fine. Here, the toolkit tries to push superuser but it gets "device not found" error messages. The toolkit then goes back to the main menu.
8. I retry steps 2-4 but only for an insecure boot image. Again, I get the same results. I also used Root Checker to see if it was rooted. It is not.
Is there something I'm missing? Kies is not running on my PC. Should I use another program to root/install a recovery?
Thanks for reading.
Make sure Kies isnt running in the background.
Try turning off any anti-virus / firewall you have.
mikep99 said:
Make sure Kies isnt running in the background.
Try turning off any anti-virus / firewall you have.
Click to expand...
Click to collapse
I turned off my anti-virus and firewall, and it didn't help. Afterwards, I also tried another USB port, to rule out any COM issues. Again, nothing. I doubt it has anything to do with the USB cable itself since I'm able to transfer files between the PC and the phone's internal storage.
Kies? I'd uninstall it if you have it and dont need it.
USB debugging on?
EDIT - Run ODIN as admin?
mikep99 said:
Kies? I'd uninstall it if you have it and dont need it.
USB debugging on?
EDIT - Run ODIN as admin?
Click to expand...
Click to collapse
I do not have Kies installed. USB debugging is on. This is verified by the toolkit, as it does not let me proceed without USB debugging on.
I am pretty sure ODIN is being run as admin. However, the toolkit opens ODIN for me from a batch file. I am trying one more time, this time using another USB cable.
More info:
Samsung Galaxy S3 toolkit v7.0
which contains Odin v3.07
EDIT:
I changed the USB cable from an older one to the one that came with the phone. This apparently made all the difference. Thank you, mikep99 for all your help.
No problem - glad you got it sorted
Hm. Mine gets stuck at Getting PIT for mapping (Brand new phone, old one broke).
Just trying out a different COM port as well :/ Hope it works some time soon. I HATE the cr*p the German Telekom puts on their devices -_-
Lg
I have a similar problem to yours, slight worse.
My phone was going really slow at one point and decided to un root it, with no success. I only factory reset it and still had the root.
I tried to flash it with the stock thingy and got this message in Odin:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
I left it like this for an hour maybe, and I got inpatient and pulled the plug (I may think I should shoot myself for the stupidity)
And I got the error: "Firmware upgrade encountered an issue. Please selected recovery mode in Kies & try again."
At that point I tried to root it with the original root I used at first (CF-Root-SGs3-v6.3) and that worked slightly, but now I have the problem where the galaxy s3 logo "freezes" with an red exclamation mark in the top left corner, I am stuck as ****, ****ed up bigtime, halp.
Hi guys, i 've got a problem, maybe serious. My S2 freezed. I have a custom jelly bean rom. I took off the battery, tried to turn on, but it stucked on bootloop. Now it only goes on download mode. I used Odin, trying to upload a stock Rom. But each time it failed, stucked as showed:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It happens with each version of Odin.
It stucks even when i try to upload the .PIT file or a Kernel one, changing all the USB port I have.
I even tried with ADB, but Adb does'nt recognize galaxy s2. I know ADB requires usb debugging enabled to detect your device, but in jellybean, Developer options are DISABLED by default, therefore, usb debugging is disabled too.
Is there anyone who can help me?
Thanks a lot
You cant enter recovery mode? If you have download mode try to reinstall drivers for Phone and try another cable or another pc.
Odin recognized your phone?
mosespl said:
You cant enter recovery mode? If you have download mode try to reinstall drivers for Phone and try another cable or another pc.
Odin recognized your phone?
Click to expand...
Click to collapse
Yes, Odin recognizes my phone, but stucks as i said before. I' ve tried all port usb I have got, and cables too. But, nothing. Maybe another pc...