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!!!
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
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.
Hello, I have Galaxy SII, SGH-I777 w/AT&T. When i turn on the phone i get black screen that says "Samsung Galaxy SII". I can't get passed this screen. The only other thing i could do is hold up/down volume & power button that takes me to a screen where i'm giving 2 options, continue or cancel. Click cancel, i'm back at black screen. Click continue it takes me to "ODIN MODE" and says downloading. No clue what it's downloading but it's stuck at this screen now. I'm not very techy w/phones, not sure if there's a simple solution. Phone is factory OS, i never installed anything outside of what AT&T pushed through software upgrades. Please help!
When you press continue and get the screen that says downloading, your phone is in download mode, which means it is ready to receive new firmware via Odin. Since all you can get is either download mode or the black screen when you use the button combination that should take you to recovery, that means that the firmware has become corrupt in some way. The only way to fix this is to re-flash the stock firmware using Odin. Please read through some of the guides that are linked in my signature. That should give you enough basic information to flash back to stock. If you have any questions along the way, feel free to ask them here.
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
ytka98 said:
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
Click to expand...
Click to collapse
Since you are running stock ROM & kernel, if you've ever performed a factory reset or wipe on your phone then you may have an emmc superbrick on your hands.
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
ytka98 said:
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
Click to expand...
Click to collapse
What AJ Newkirk says is a possibility, but not definite. If the phone does have damage to the emmc memory, then yes, you would probably have to get a new phone. I only ever saw two reports of emmc memory damage reported here, and only one of them was even close to conclusive, so the likelihood that your phone has some other issue is quite good.
Do you know what version was currently on the phone? The latest version pushed out by AT&T is 4.0.4 (UCLL6). Also, did you ever perform a wipe data/factory reset at any time? And finally, please describe the circumstances surrounding the phone's failure to boot. We'll try to help.
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
ytka98 said:
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
Click to expand...
Click to collapse
If you were flashing the UCKH7 downloaded from that guide, try flashing the latest 4.0.4 firmware instead. You can get it from the download repository.
Also, after you open Odin on your desktop, enter download mode the usual way: with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL and info below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Removed!!
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
ytka98 said:
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL ...
Click to expand...
Click to collapse
Yes, but it appears that you may have Nand read/write corruption. (Not actual physical damage to the memory, but just corruption that needs to be reflashed.)
Here are the steps:
1) Flash kernel as PDA in Odin.
2) Flash the full stock package again as PDA in Odin.
If that is not successful then:
3) Download the Bootloader. Flash it as PDA in ODIN. Without ticking Re-Partitioning.
4) Flash kernel as PDA in Odin.
5) Flash the full stock package again as PDA in Odin.
I believe you can flash either a custom kernel or the stock kernel to clear the nand r/w corruption, but the problem is there are not many kernels packaged as tar available. I don't know whether flashing a Gingerbread kernel and then coming back with the ICS stock will clear the problem, but since the only kernel tar I know of is Gingerbread, why don't you try that first. If that doesn't work, I can package up an ICS kernel for you to use, but you'll need to be patient since I am pretty busy right now.
Download the Siyah 2.6.14 Gingerbread Kernel. From the line that says download, choose the TAR version. Flash that is step 1 and then the UCLL6 tar md5 package you used before in step 2.
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
ytka98 said:
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
Click to expand...
Click to collapse
Pressing all three buttons does not take you to download mode, it takes you into recovery mode. To enter download mode: (as I posted in a previous post in this thread) with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
I ran SiyahKernel v2.6.14 TAR and got this response:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I then ran I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5.7z and got this response:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
i777 UCKH7 sbl.tar and this happens:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have the device already plugged in and in download mode when you start Odin? Try unplugging and plugging the device back in with Odin open.
Sent from my SGH-I777 using xda premium
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Same boat
I am in the same boat. I will admit that i rooted my phone, and yes, selected a factory restore and now i am in this noob-predicament. Now I cant get the phone to communicate with ODIN. I have tried the jig with no avail. My phone displays:
"ODIN MODE
Product Name: SGH-I777
Custom Binary Download: YES (5 counts)
Current Binary: Custom"
When I use the Jig, the only display that changes is ODIN MODE changes to FACTORY MODE
Hoping for a cure...
Thanks for the help!!!
I had the same problem "can't open com port" until I used the original Samsung cable. I tried unsuccessfully for hours until I read that somewhere. With the right cable, it worked immediately.
Sent from my SGH-I777 using Tapatalk 2
ytka98 said:
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Click to expand...
Click to collapse
To answer your earlier question, "Am I doing this right?" Look at the following complete instructions for Odin and follow as described. Attempt to flash the Siyah kernel tar (Step 1 in the previous post.)
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
Step 5) in this sequence will complete only if you have the correct drivers installed. Let us know how it goes, or which step is unable to complete.
If you get through all 10 steps and you still get the com port error, then try a different cable, or a different usb port, or even a different computer. If you have a desktop computer, you must use the usb port on the back, one that is connected directly to the motherboard.
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now i see the following message for the last 10 minutes:
<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> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sign "Kernel" above green turned red and now says "Fail"
ytka98 said:
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now all the buttons on the screen are grayed out and i see the following message for the last 10 minutes:
<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> zImage
<ID:0/004> NAND Write Start!!
The phone still says "downloading...do not turn off target!!" . what's my next step?
Click to expand...
Click to collapse
If your problem is nand r/w corruption, you need to get a kernel to flash successfully as the first step, before you flash the complete package. The flash should complete in under 10 minutes, so it sounds like it's not going to complete. I could put the 4.0.4 stock kernel into a tar for you to try to flash to see what happens. Before I do that though, I need to find some additional information about the boot loader flash. I probably won't be able to get back to you before tomorrow.
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...