I used the guide in the following link. I checked to make sure i was doing everything as it says. This is not my first phone that I have rooted and installed custom roms......just saying....
Here is the guide i used
http://forum.xda-developers.com/showthread.php?t=1309293
for almost an hour now odin has said...
"<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> zImage
"
Phone is stuck in the Download with 'Downloading.....do not turn off target!!"
Just got my S2 today.....wanted to wait a week before i bricked it. PLEASE HELP??
Don't worry, it's not ruined. The package you're working with does not contain bootloaders.
Unplug the phone, pull the battery, and close Odin.
Then start it over again. There's a chance the file you're using is corrupt and needs to be redownloaded.
Not really sure why you're using Odin to flash a kernel. That will trip the flash counter. Creepyncrawly posted an awesome write up how to flash without tripping the counter.
And he today posted a collection of newer ways to root that also don't involve tripping the flash counter.
Sent from my páhhōniē
Related
Hi, so i downloaded the version for my phone
GT-I9100_XEO_I9100XXKH3_I9100XXKH3_I9100OXAKH3.
I wiped factory/data reset, system something and dalvik cache.
I used odin to flash ticking only the PDA,
but it stuck for like 1 hour on this stage:<ID:0/012> factoryfs.img
Both the loading bar on the phone and on odin are on the same level.
Here is the full Message:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img
<ID:0/012> factoryfs.img
Any help please??
99nirc99 said:
Hi, so i downloaded the version for my phone
GT-I9100_XEO_I9100XXKH3_I9100XXKH3_I9100OXAKH3.
I wiped factory/data reset, system something and dalvik cache.
I used odin to flash ticking only the PDA,
but it stuck for like 1 hour on this stage:<ID:0/012> factoryfs.img
Both the loading bar on the phone and on odin are on the same level.
Here is the full Message:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img
<ID:0/012> factoryfs.img
Any help please??
Click to expand...
Click to collapse
Did you by chance check repartition? If so I think you may be in trouble.
Nope, i checked like 4 times before i clicked start, and i can see it now,
I didnt ticked Repartition...
99nirc99 said:
Nope, i checked like 4 times before i clicked start, and i can see it now,
I didnt ticked Repartition...
Click to expand...
Click to collapse
Okay well there may be hope. Pull the battery and then use the button combo to see if you can get to download mode if you can then I suggest you restart your PC and make sure your using a UBS connection that is on the back of your PC, do not use any USB hubs or front usb connections. Also make sure kies in not running in the back round as it can interfere with the USB connections.
I made a backup with Cwk so i hope nothing will go wrong...
I pulled the battery, and i got to download mode, but odin doesnt seem
to recognize the phone...
Edit: i just noticed on processes, that kies Was running...
but Odin doesnt recognize the phone now...
Edit2: Odin managed to recognize the phone, so i started the process again...
but i got an error:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img
<ID:0/017> factoryfs.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i try again?
99nirc99 said:
I made a backup with Cwk so i hope nothing will go wrong...
I pulled the battery, and i got to download mode, but odin doesnt seem
to recognize the phone...
Edit: i just noticed on processes, that kies Was running...
but Odin doesnt recognize the phone now...
Edit2: Odin managed to recognize the phone, so i started the process again...
but i got an error:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img
<ID:0/017> factoryfs.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i try again?
Click to expand...
Click to collapse
Well as long as you can get to download mode there is hope. Maybe try a different firmware package.
Are you using the Samsung USB cable or the HTC one?
Successful!!
I just tried it again and it worked!
Thanks alot everyone, especially the one who told me to check
if kies was running
Hi, I been stuck on cache.img for hours (i left it overnight) kies isnt running in the background and i tried many times, im trying to flash XWKI4.
I came across this post and im using a HTC cable to connect, is this a problem??
Edit: Kies really messed up my phone it kept failing on firmware upgrade, asked me to do firmware emergency but that wasnt working either, eventually the firmware upgrade worked BUT the phone doesn't recognise my SIM card so i want to reflash in ODIN
saffad said:
Hi, I been stuck on cache.img for hours (i left it overnight) kies isnt running in the background and i tried many times, im trying to flash XWKI4.
30 mins max
I came across this post and im using a HTC cable to connect, is this a problem??
Probably is not the correct cable as per instructions
jje
Click to expand...
Click to collapse
hah yea had the same problem, its always dam kies gw gw
Tell me about it, kies is useless.
I tried another firmware but thats stuck on boot.bin right now, i have to travel 2hrs to get my samsung cable!! no idea what to do now..phone doesn't start (says do an emergency recovery). Thinking of going to service centre, i know I haven't void my warranty.
. Thinking of going to service centre, i know I haven't void my warranty.
ROOT = warranty void .Custom rom = void warranty
So if you have neither you are ok if not you need to flash stock rom to unroot and set rom counter to zero with USB jig .
jje
JJEgan said:
. Thinking of going to service centre, i know I haven't void my warranty.
ROOT = warranty void .Custom rom = void warranty
So if you have neither you are ok if not you need to flash stock rom to unroot and set rom counter to zero with USB jig .
jje
Click to expand...
Click to collapse
i never rooted and i never flashed a custom rom, i never even flashed a rom, just used kies to upgrade..so i think im ok
saffad said:
i never rooted and i never flashed a custom rom, i never even flashed a rom, just used kies to upgrade..so i think im ok
Click to expand...
Click to collapse
Yes you are ok .
Kies update broke phone well known service call .
jje
I have got stuck on DATAFS. Should I pull out the battery and give another try or ?
THX
THX A LOT Revived my SII!
****ty kies that sucks my sii wile upgrading fw...
THX ODIN and XDA
how much time it will take via oden i have single file putted in PDA box file is about 1.5 gb
asadnow2k said:
how much time it will take via oden i have single file putted in PDA box file is about 1.5 gb
Click to expand...
Click to collapse
5 - 10 mins to flash an entire firmware. Unless u flashed the wrong file...
"To err is human, to forgive is divine"
Sent from my SGS II
1.5 Gb pda file?
What the hell are you flashing there?
Sent from the little guy
Alright, so sorry if this has already been mentioned before, but I am just tired of googling around threads for an answers so I'm resorting to the Q&A. So I've just picked up a Bell Samsung Galaxy S II and have tried to use a tutorial off of http://androidforums.com/galaxy-s2-...lock-root-bell-galaxy-s2-step-step-guide.html. Generally I have worked with rooting many htc devices but the SSGS2 was my first samsung device which is new grounds to me so I'm not really sure what to do about this problem. Everything goes fine until I reach the part where I have to root the phone with CF-Root-SGS2_XX_OXA_KG2-v4.1-CWM4. Whenever I try to root it, Odin gives <ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
and stays at zImage. Yes I am in download mode and yes I have enabled debugging under development.
Did you disabled Kies? If not stop it with taskmanager
Sent from my GT-I9100 using XDA App
No root on XDA ???
jje
I've had the same trouble with cf root kk2. Stuck on Zimage. I've rooted before with this, but this file is giving me trouble. Can't figure it out yet. Tried downloading the file again from chainfires thread. I'll figure it out sometime after christmas I guess.
Sent from my GT-I9100 using XDA App
Hi Guys,
M Flashing my new Samsung Galaxy S2 & unfortunate i by mistakenly used CF root for galaxy note on my S2. As i searched lot on forums i found to flash it back with the correct CF root i did it but still no luck. Now my phone shows a small mobile icon with the computer & middle of that shows orange warning triangle. And I'm trying to get in CWM recovery mode as well but m not able to only download mode is working. M worried did i bricked the phone or what. As I'm Trying to root with other custom & official roms to get it back but it shows these message.
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> boot.bin
<ID:0/022> NAND Write Start!!
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/023> Added!!
<ID:0/023> Removed!!
<ID:0/023> Added!!
<ID:0/023> Removed!!
& get failed. Please guys help me otherwise i will be in a big trouble as these phone is not mine my girlfriends & i don't want her to get angry on me. Guys please help me if i can get it back.
Can you put the phone in download mode?
Sent from my GT-I9100 using xda premium
if u r able to get into the download mode then u have not bricked your phone yet....all u need to do is flash the stock firmware via odin...but please follow the instructions carefully....u can find the firmwares in dev section....
Edit :
Here is the thread :
http://forum.xda-developers.com/showthread.php?t=1075278
Sent from my GT-I9100 using xda premium
i think u are in big trouble. better marry your girlfriend so she can't break up with u. she will be very upset and kick your ass. better find a phone service right away before she comes home.
if it is her phone and not yours why bothering to flash?
if u cannot go in download mod try to get an usb Jig
Nevermind. OP can get into DL mode, fix should be fairly simple.
I had a S2 i777, then I got a S3 so I gave the S2 to my mother. I just installed fresh ShoStock because I thought that would work well. It worked ok, but after about a month I came home and she said it wasnt working.
It appeared to be bootlooping at the ShoStock logo. I downloaded a new rom for it on my phone the put the SD card in her phone, booted into clockwork and tried flashing it. Trying to wipe or flash at all results in hanging for a few minutes then rebooting and getting stuck at the Samsung S2 logo now. Since then I've tried various odin methods for flashing to unbrick around xda. Every time I try to flash with odin, it either says error or it just hangs until I manually stop it after 30+ minutes. I've even got as desperate as to have Kies revert it to stock, it also hangs at 2%.
At this moment, you can see the screen its stuck it in the attached screenshot, its probably worth noting its been at this screen ever since the first Odin flash failed.
I do have a microUSB jig so I can kick it into download mode if I have to. Anyone got any ideas :f
Try the following procedure exactly as written. In case the problem is nand read/write corruption, this should clear it and get the phone working again.
1) Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
When I try and flash Siyah in Odin for step 1, it just hangs.
<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!!
Click to expand...
Click to collapse
The box at the top says kernel and the progress bar goes all the way across, it will never get past this.
Since it won't flash the kernel, the next thing to suspect and try to find out if the cable is faulty. Or anything in the path from the computer to the phone. So...
Try a different cable, or as many different cables as you can put your hands on.
Try different ports on the computer, and use the ones attached directly to the motherboard if it is a desktop.
Try a different computer.
In some cases where there is a connection problem, just flashing repeatedly may eventually result in a pass, as some have reported.
Tried it on two different laptops, with three different microUSB cables on each, no dice.
I tried flashing the kernel from step one you gave, I also tried the I777UCKH7-CL503881 FULL Odin3 One-click from the Download Repository and it hangs at:
<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> boot.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
Click to expand...
Click to collapse
I don't have any additional suggestions for trying to fix it yourself. The problem could be one of several things. It doesn't seem like a simple soft brick. Maybe it could be damaged memory or some other hardware failure. Or maybe not.
If you are close to an AT&T service center, maybe you could take it by and ask them to flash it back to stock for you. If that fails, then at least you are pretty sure the problem is in the phone, not the connection. I realize it is not under warranty any longer, but they should at least try that for you.
You could send it to Samsung repair center to be worked on. They would probably fix it, but it won't be free, and it will also take two to three weeks. If it were me, I would call them first and discuss the issue with them.
Give these guys a call or message them and tell them your problem and they can most likely fix it. I have had work done by them in the past there quick and there professional...
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t/
Sent from my SGH-I777 using xda app-developers app
As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.