Database Develop

Odin stuck at Set partition

Hello
So I have flashed my rom several times and this time.. I might have seriously bricked my phone.
Odin is stuck at Set partition with the following messages:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Enter CS for MD5..
<ID:0/008> Check MD5.. Do not unplug the cable..
<ID:0/008> Please wait..
<ID:0/008> Checking MD5 finished Sucessfully..
<ID:0/008> Leave CS..
<ID:0/008> Enter CS for MD5..
<ID:0/008> Check MD5.. Do not unplug the cable..
<ID:0/008> Please wait..
<ID:0/008> Checking MD5 finished Sucessfully..
<ID:0/008> Leave CS..
<ID:0/008> Enter CS for MD5..
<ID:0/008> Check MD5.. Do not unplug the cable..
<ID:0/008> Please wait..
<ID:0/008> Checking MD5 finished Sucessfully..
<ID:0/008> Leave CS..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
I have opted to flash to JPC (which I have successfully flashed to several times) and have checked re-partition, auto re-boot and f. reset time.
I do not remember having to wait this long on this step.
Appreciate any help.

i try the followings usually (not in sequence)
disconnect usb
reboot the phone
restart odin

Thanks.... I pulled the batt... restarted odin this time with re-partition unchecked and its working now..

Thanks, this worked for me as well!

I did just as you said, but checked "re-partition". It worked as a charm! Thank you very much!

I get the same problem
I get the same problem, but for me i cant go to download mode. when phone rebbot i have a icon ( this is not conetion between pc and phone), i can't go to download mode either by comand ou by typing volume down+menu+off
Can you help me?

Hi everybody,
I'm new to xda, just joined today because i ran into some trouble. Android 2.3.4 Gingerbread just appeard and i thought to flash my Galaxy S. I've done the following, i transfered all of my files from the phone to the pc, did a format on the internal and external sd card, did a factory reset, unmounted the external sd card, removed the sim then put the phone in downloading mode. Then i got Odin3 v1.85 and the files needed to flash:
The pit file: s1_odin_20100512.pit
The phone file: MODEM_I9000XXJVP_REV_00_CL1019177.tar.md5
The CSC file: GT-I9000-CSC-MULTI-OXAJVP.tar.md5
The PDA file: CODE_I9000XXJVP_CL264642_REV03_user_low_ship.tar.md5
Started Odin, loaded all the files in their right spot, connected the phone to the usb cable, odin recognized it, checked the Re-Partition box, the Auto Reboot box and the F. Reset Time box then clicked on start. Then the following appeared in odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9000XXJVP_CL264642_REV03_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9000XXJVP_REV_00_CL1019177.tar.md5 is valid.
<OSM> GT-I9000-CSC-MULTI-OXAJVP.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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!!
and now it's stuck (or i think it's stuck) on Set partition, it's been on Set partition for about an hour and my question is, do i wait a little more longer or did i just bricked my phone ?
LE: oh and i forgot to mention, i had 2.2 don't know the exact code but it was the russian version that came with the phone and it wasn't rooted

@bigbrother88
Unplug the phone, remove the battery for a few min. and try to flash again.
You must only use the original Samsung USB-cable to flash the device.
If your device is Russian then the CSC code is SER, remember that if you want to flash back your device to the original firmware.

I unplugged the phone, taken out the battery, left it like that for 5 min then i tried again. Now it seems to be stuck at:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I'm using the usb cable that came with the phone, so i guess it's the original Samsung USB cable.
Can i flash the phone without checking the Re-Partition box ? And i am loading all of the files at once, the pit, pda, phone and csc, i don't need to do some files first then others right ?
And sorry if i'm being such a nuisance but this is my first time trying to flash galaxy s
LE: finally i managed to flash my phone, all i had to do is uncheck Re-Partition box and worked like a charm, thank you for your help

Remove all about KIES not thr driver ... and flash it..
Sent from my GT-I9000 using Tapatalk

Use another Odin version
I had the same issue...
Use another Odin version and will work.
I used the one included in the EZbase package.

- Disconnect phone from computer.
- remove battery, leave it for two minutes.
- Open task manager, kill the Kies process if its running in the back ground
- open odin 1.3, check repartition, select files
- go to download mode, connect phone and start flashing
you should be fine, don't be in a hurry

The first time I experienced exactly the same I got pretty mad...but patience made it for me in the long run
Sent from my GT-I9000 using XDA App

Experienced the same here. You have to kill any "kies" processes on your pc by taskmanager!!!
No need to pull battery! Just press on/off button long enough and then re-enter download mode and reconnect via usb.
Worked here with odin 3 v1.82 pit file and repartition checked.

Uhh, I realize it might be considered an old thread, that should not be resurrected.. but what "fixed" it for me is running Odin as an Admin.

Was flashing from custom ROM to the stock 2.3.5 and got the same Set Partition issue. Solution was like said above: disconnet usb, pull out battery for two minutes and flash again.

Useful thread. Kies was the culprit in my case!

If you don't use kies just uninstall it and use only the usb drivers http://forum.xda-developers.com/showthread.php?t=728929

Thank you
I did this...
disconnect usb
reboot the phone
restart odin
...then tried it again with all 3 boxes checked again and it worked.

ykk_five said:
i try the followings usually (not in sequence)
disconnect usb
reboot the phone
restart odin
Click to expand...
Click to collapse
Works great for me. Thanks alot!

[Q] Galaxy Note bricked? No. Problem solved.

This is the situation:
Windows XP 32bit
Galaxy Note with LA4
Odin V1.85
KIES latest version
Latest Android SDK
I tried today to downgrade to a directly rootable stock ROM. It failed?
My Note stucks on the bootscreen.
I can put the Note in the downloadmode. When I start Odin, I see a yellow box under ID:COM with 0:[COM7], so my computer sees the Note. I want to flash the rootable stock ROM as described in many threads, especially following Dr. Ketans Guide
But it fails, it stucks at Initialzation..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_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> SetupConnection..
<ID:0/006> Initialzation..
I tried the LA4 stock ROM, same problem.
After this I have putted the Note in recovery mode and this is what I see:
"E:failed to mount /sdcard (Unknown error: 0)"
"E:install_application_for_customer:Can't mount /sdcard"
" your storage not prepared yet. please use UI menu for format and reboot actions."
"copy application failed"
In the recovery mode I tried Factory reset and Wipe cache...no effect.
Since 4pm I have tried many things, read threads and posts, but nothing has solved my problem. By the way I have not seen a problem as described above no where. Is there a genius who can solve this/my problem?
Or is my Note bricked?

The only thing i can see is that it can't mount the SD. Other than that, i don't know. And you know i had my own problems yesterday, so i'm not in the position to know what might be wrong. But one thing is sure, it's not bricked since you can enter download mode.
I know it's frustrating, but you'll have to wait for somebody that knows some things about Odin. I used it myself for the first time yesterday since the Note is my first Samsung device.
Sent from my iPad GT-N7000 using xda premium

see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps

I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)

Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
As you can read I did trie data factory reset, after flash with Odin it didn't work. Thanks for your help.

gee2012 said:
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
Click to expand...
Click to collapse
As you can read I can't ENABLE USB DEBUGGING, because I can't start my Note up normally. Thanks for your help.

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thanks, but no effect.

dr.ketan said:
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Click to expand...
Click to collapse
With the pit-file it showed PASS!:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At my screen the following:
Firmware upgrade encountered an isseu.
Please select recovery mode in Kies & try again
If I open Kies to select recevory mode it asks for a recovery code. I tried some codes like 0000,1234 and others, but no good...
Then, I entered the download mode of the Note and tried a flash with KK9 (one file) it shows PASS:
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan

Note not bricked.
Problem solved.

And the problem was?
Sent from my GT-N7000 using xda premium

Read my first post...

got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<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> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks

Caesarea038 said:
With the pit-file it showed PASS!:
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Click to expand...
Click to collapse
Really glad to hear.
It is really painful when some one say bricked lovely device.
its ok now, congratulation.
it is advisable once you format internal SD card. Not in hurry, but at least before next update.
Sent from my GT-N7000 using xda premium

shaharda said:
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
...........................
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Click to expand...
Click to collapse
Can you tell me exactly the problem and what you did step by step?

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Today I figured something out:
If you encounter problems with rooting/flashing try another or original USB cable, maybe a different USB port....
My problem as described in my first post was a combination of a fail USB cable and a software problem.

thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).

now the battary won't charge. need to send it to the Lab.
thanks anyway. (i'll as them what they did)

shaharda said:
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
Click to expand...
Click to collapse
Can you enter DOWNLOAD MODE?

[PROBLEM SOLVED]Odin keep failed

I was trying to root my galaxy note, I download the rooted stock rom (N7000DXLC2) from here http://forum.xda-developers.com/showthread.php?t=1535025
but the odin failed and showing this
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000DXLC2.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000OLBLC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then my phone can't boot anymore, it jus stuck at the samsung n7000 screen,
i tried to download stock rom and flash again, but it failed like above,
and when i go try to flash the kernel, it success to go to the recovery mode,
but it showing error like
E:Error in /cache/recovery/sec_csc.zip (status 7)
And i maybe forgot to enable usb debugging before i root, is this the cause? how i enable it now?
what can i do now? I tried to change port, change pc, uninstall kies, reinstall driver, close antivirus, and all doesn't work, please help...

To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and setting it in the options anyway.

bioweb said:
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and set it in the options anyway.
Click to expand...
Click to collapse
I tried that, and I uninstalled the kies,
but the odin still showing the same error.

PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......

17n337 said:
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
Click to expand...
Click to collapse
CAUTION : Just dont go on blindly flashing the PIT file. Its a repartitioning file. To be used only when your partition is corrupted.

Galaxy Note stuck
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???

vinay28761 said:
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
...
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but
...
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
...
Can anyone explain my current situation...???
Click to expand...
Click to collapse
First: this thread is marked as solved since april. Chances are very low for a reaction (but at least I did)
Second: Make a new one in Q&A
Third: What do you mean with "Took the TB"? Especially when you flash a new Stock Rom after
Fourth: Did you put the tar-file under "Phone"? Should be "PDA".
Fifth: Read a lot in the stickies here - good start for handling Odin is Dr. Ketan's thread
Sixth: your current situation might result from not reading enough. I hope you didn't brick your device and can restore a running Rom with the instructions from the stickies. Good Luck

how exactly did you reach this situation?

Did you resolve this ?
vinay28761 said:
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
Click to expand...
Click to collapse
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?

dannyogolo said:
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
Click to expand...
Click to collapse
Yes, i resolved it. I just followed dr. ketan's guide to flash through ODIN properly and exactly as described. I would request you to do the same.
Hope it solves your error too. If not, please post your screenshots.

could you jst give me details about dis nand write fail problem?i m having same problem in my gt n7000

Does anyone know where i can download PIT file for samsung gts6802 and a bootloader?
It woulb be very helpful. Thank You

[Q] Problems with Odin, need help.

Hi everyone, sorry if this is the wrong place for this post, mods pls move it to the right forum.
I have a non-rooted, non-operator free Samsung Galaxy Note with Gingerbread and I want to root it, set it operator free and flash ICS.
I tried to flash a ROM via Odin (N7000XXLPY_N7000OXALPY_DBT), followed the steps (open Odin, select the md5 file @ PDA, startup the phone on download mode, connect the phone to pc, now Odin recognizes it and shows the yellow case, then I press start) but at a certain point it just stops working and I dunno what to do, its frustrating...
Here's the Odin's Console log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.img
It just stops at this point and don't do nothing... What can I do?

kelomancer said:
Hi everyone, sorry if this is the wrong place for this post, mods pls move it to the right forum.
I have a non-rooted, non-operator free Samsung Galaxy Note with Gingerbread and I want to root it, set it operator free and flash ICS.
I tried to flash a ROM via Odin (N7000XXLPY_N7000OXALPY_DBT), followed the steps (open Odin, select the md5 file @ PDA, startup the phone on download mode, connect the phone to pc, now Odin recognizes it and shows the yellow case, then I press start) but at a certain point it just stops working and I dunno what to do, its frustrating...
Here's the Odin's Console log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.img
It just stops at this point and don't do nothing... What can I do?
Click to expand...
Click to collapse
Usually ODIN takes a lil long to flash a rom.So give it a good 10mins time and see it comoletes the installation....
Or you may use the new ODIN by grgsiocl.It shows the remaining time left to finish flashing.Its there in themes and apps section.
Sent from my GT-N7000 using xda app-developers app

sometimes 30 or more minutes.
Usually it stops there either thought corrupt download of rom, redownload it try again.
Or because you have bricked it "op op" emmc "style" way.
If you did not root phone, or put different kernels on, then dont do anything and contact entropy, he is looking for a case where without this the phone was superbricked.
Sent from my GT-N7000 using Tapatalk 2

You may not have all the drivers from Samsung? Download Kies, run it. Then turn off Kies, antivirus and firewall. Commissioning Odin as administrator.

Wait for atleast 20 mins approx to get the stage completed or throw out to samsung service center to get it done.
Swyped From My Juicy Flavoured AOKP JB.

[Q][I9000]Bootloop, Home button is broken, How to flash new ROM?

Hello,
I have I rare problem. I tried to flash a new ROM and it failed, so now the phone is stuck on the boot image. Ok, usualy I would have solved this with CMW 3 button recovery combination, but my phones Home button is broken so I cannot acces it, but I made the USB Jig and can acces download mode.
My question is how do I unbrick my phone?
What I tried: Using SDK tools to reboot the phone in recovery with ADB, no succes. Sdk doesnt see my device.
Something called Fastboot, but from what I read Samsung doesn't have such a feature for the phone to enable.
Thank you.

I had the same problem a couple of time ago, but all 3 buttons were defect (see my signature ).
What I always did:
when you can get in download mode then restock via odin and phone will boot again.
Here is slappys rescue kit what i always use when i have to restock.
Unzip it and flash the Rom via Odin. There is also a txt file with a guide included.
http://forum.xda-developers.com/showpost.php?p=29114573&postcount=2
With this flashed rom you will have in the power down menue the funktion: back to recovery or back to download. So first time go back to download mode or use usb jig again and then flash the included root kernel.
Then flash the rom of your choice.
If you would go to jelly bean i would recommend to use Mackays 1.3.0. first. Because you have to flash JB twice or even 3 times and after the first flash of this Mackay it goes automatically back in recovery mode.
Link to older Mackay Roms:
http://www.xdafileserver.nl/index.php?dir=Samsung/Galaxy+S/MackayROM/JB41/old
After flashing this you could go to google play and download an app for softkeys for example softkeys for root users.
After that and if you want or like you could flash also a JB rom with included virtual softkeys, like for example SLIM. You have to enable the navigation bar in settings but after that you can use your phone quite normal.
Hope this helps and wish you a good success!

How long should it last to restock with odin?I'm waiting for about 30m and nothing. Still says Do not turn of target! No Loading bar n phone or Odin showing any progress. What is wrong?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EZbase-PHONE-XXJVO.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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!!

Solved it. I was using the USB port in front of the Desktop unit and i guess it doesn't have enough voltage. Worked when i switched to the back USB port. Thanks a lot man!! You saved my phone !
rahbert said:
How long should it last to restock with odin?I'm waiting for about 30m and nothing. Still says Do not turn of target! No Loading bar n phone or Odin showing any progress. What is wrong?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EZbase-PHONE-XXJVO.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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!!
Click to expand...
Click to collapse

rahbert said:
Solved it. I was using the USB port in front of the Desktop unit and i guess it doesn't have enough voltage. Worked when i switched to the back USB port. Thanks a lot man!! You saved my phone !
Click to expand...
Click to collapse
Great and Strike . Glad i could help and you can use your phone again!
Have fun with it and enjoy...perhaps JB?!