Well I wanted to flash Valhalla v1.2 [KI1] so I proceeded to odin KG4 and all it does is sit there
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
That is as far as it gets and its been plugged in for over 5 minutes just sitting there. I got impatient and removed the battery and unpluged the USB which probably wasn't the best idea ever. Sometimes going into download mode I get usb device not recognized and I no longer get the download screen to come up anymore its a bunch of dots now and other times odin sees the phone but no matter what it still gets stuck sitting at Initialzation. Any ideas on how I can get something to flash on it?
Edit: And now Odin cannot see it at all.
Edit2: Tried a different USB port it sees it and I attempted to flash again but its stuck on partitioning.
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Disconnect USB cable
Battery pull. Battery back in
Vol + and -
Connect USB cable
Try Odin again
FBis251 said:
Disconnect USB cable
Battery pull. Battery back in
Vol + and -
Connect USB cable
Try Odin again
Click to expand...
Click to collapse
Soon as I did that download mode came up properly and now its flashing thanks so much.
Related
Hi guys,
I tried to root my phone and installed the "One-Click lag fixed"
Then, my phone get into trouble
So, I can power on my phone and it stuck at the "Galaxy S" pages. Not loading into the system. Then, after it keep loading on that page for a while, the screen turn black and if I touch the 4 button that are placed under the screen, they glow. If I press the power off, it will restart itself and stuck at the "Galaxy S" page again.
Here I have downloaded the (1) ODIN v1.3 (2) s1_odin_20100512.pit and (3) T959UVJI6.tar
I open the ODIN exe, press volume up and down button then plug my phone to my computer, then my phone showed an Andriod digging the ground.
Then I added s1_odin_20100512.pit next the PIT option and T949UVI6.tar under PDA option. And click Start
Here's what the ODIN showed:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> modem.bin
<ID:0/003> zImage
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Also, ODIN showed PASS; therefore, I unplug my phone from the computer
however, when I am done with ODIN and my phone reboot itself. The same thing happened. It stuck at the "Galaxy S" page
What did I do wrong!?
Thanks everyone.
sounds like a busybox issue. try this flashable version in recovery mode then reboot. :
So here is the rundown. I flashed GC 1.9RC2.3 and was getting some force closes. Tried Data/Factory Reset and that still didn't fix the issues. So now I'm trying to reflash GC 1.9 FE to restart over and ODIN has been stuck on cp_modem.bin for the past 20 minutes.
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> dbdata.rfs
<ID:0/004> lte_modem.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> cp_modem.bin
Is this normal? I don't remember it taking this long to flash the previous time.
WilliamKingX17 said:
So here is the rundown. I flashed GC 1.9RC2.3 and was getting some force closes. Tried Data/Factory Reset and that still didn't fix the issues. So now I'm trying to reflash GC 1.9 FE to restart over and ODIN has been stuck on cp_modem.bin for the past 20 minutes.
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> dbdata.rfs
<ID:0/004> lte_modem.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> cp_modem.bin
Is this normal? I don't remember it taking this long to flash the previous time.
Click to expand...
Click to collapse
Are you using the PDA button? Did you reinsert the battery after Odin recognized your phone?
sounds like slow USB connection...try another usb port.. preferably a rear port...the modem does take a bit to flash and progress shows on device for modem
Yes I am using PDA and I have been using ODIN since my Vibrant and never had to take the battery out to flash. As far as moving the USB to a different port, if I cancel out the install right now will I be perma-bricked?
Update: So I switched USB ports and it flashed pretty quickly. I guess the port on the front wasn't cutting it.
let it go if the staus bar is moving on your device...otherwise you dont really have a choice but to turn Odin off and start over...but I guess 'YES" you can brick your device
chiahead52 said:
let it go if the staus bar is moving on your device...otherwise you dont really have a choice but to turn Odin off and start over...but I guess 'YES" you can brick your device
Click to expand...
Click to collapse
Yeah I was nervous as hell to stop the download. I just closed ODIN out first and then took out the battery. Crossed my fingers and hoped for the best. I'm glad it went through the second time because I would've been pissed if I had to send my phone off.
The only time I've seen bricks is when something happens in odin to interrupt the flashing of boot.bin
hazard209 said:
The only time I've seen bricks is when something happens in odin to interrupt the flashing of boot.bin
Click to expand...
Click to collapse
Thanks for the knowledge. Hey Hazard I noticed your name in the credits of GC 1.9RC2.3 when I flash it. Could you check out my other question regarding the G-Talk app and any suggestions you have about it would be great.
So here's what happened. I tried to install CWM 6.0.1.2 using EZ Recovery and it rebooted into ODIN with the words, could not do normal boot, in red. When I reboot it, it would just go back to the ODIN screen, so I tried to use the root 66 method. At first, it would get to system.img.ext4, but the green bar would barely move and be stuck there for 30 minutes. I would try again by taking out the USB cord, rebooting phone (maybe bad idea?). I did it again and it would be stuck there. I tried different USB ports on my laptop. Some will get to system.img and be stuck or get to recovery.img and say fail. Is my phone hard bricked or is there something else I can do? Thanks!
I also tried it on a different computer and it gets stuck on boot.img instead. Any help would be greatly appreciated!
It seems like using the older version of Odin gave me more consistent results. I now always get to system.img before it fails. The green bar gets 1/3 of the way then says failed.
<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
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway to get it to be successful?
have a problem with my S3, few days ago he`s stuck in boot lop, i cant to pass to recovery mode only to download mode. I have tried to reinstal new original firmware from sammobile in odin but he give me error, PIT PARTITION MISSING, also i have tried to flash few PIT files but in some he give`s me error or he`s stuck with message Get PIT for mapping (i have leave 5hours but nothing change, stuck on that message). I used odin version 1.85, 3.04, 3.07 but with no success.
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping.. --->> And stuck hours and hours
and sometimes
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Nothing cant be installed if my pit partition is missing.
I have tried to flash clock work mode in adb but my phone cant be recognized in cmd console.
My question is, there is any chance to get my phone back with z3x box? I have samsung&lg edition so if is any chance i want to try.
Thank you for read me
Hi there,
You'd be best served asking for help from the experts who own your device here:
[HELP THREAD] Galaxy S3 Ask any question.
Good luck
Hello. Sorry for my enlgish.
Theres a soft-bricked SM-P900, I can normally open download mode. (asking for Kies)
Here's the Odin log:
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It's always stucks on "system.img" in ANY .tar I try to flash.
Yesterday, it could power on. But now it's not powering on at all. I hope this is because of battery charge.
===UPD: Yes, it was because of battery charge. Now it's powered on.
What should I do, guys? Help, please!
V01DY said:
Hello. Sorry for my enlgish.
Theres a soft-bricked SM-P900, I can normally open download mode. (asking for Kies)
Here's the Odin log:
It's always stucks on "system.img" in ANY .tar I try to flash.
Yesterday, it could power on. But now it's not powering on at all. I hope this is because of battery charge.
===UPD: Yes, it was because of battery charge. Now it's powered on.
What should I do, guys? Help, please!
Click to expand...
Click to collapse
If it were me I would verify the files, perhaps redownload it. I'd also try a different USB port, cable or reinstall USB drivers on the computer. Sometimes one has to clean out old device drivers manually. I've done this with USBDEVIEW.
Sent from my SM-P900 using Tapatalk