hi i'm new on the forum ... i hope i can post this here .. i need help with a note 2 i just got it and and when i start it it doesn't make any sound just comes a white screen wit point and lines .. first i fote its something wrong wit the screen or the graphic ...if i hold volume down +power+home i can access odin mode and the computer recognise that something its connected to it .. i got the usb drivers , odin3.07 and recovery file (CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5) i folow the steps to install ...<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.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> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
on the thread it was saying that the md5 file doesn't need a PIT file ... odin was asking for one so i got one for gt-n7100 ..
Related
Hello all,
I'm trying to return my Bell s3 (i747M) and I'm trying to flash the bell the bell stock rom. I'm using odin but nothing is actually flashing. This is all I see
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513_REV04_user_low_ship.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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried 2 different files on two different computers, any ideas?
Hi
Try to reinstall your drivers.
http://forum.xda-developers.com/showthread.php?t=1903516
Well I'm a bit of an idiot, new pc build and forgot about drivers. Also followed those connection issues and it worked just fine!
I think im soft bricked and ******up pit. I can only flash recovery and it succes only randomly... Battery isnt loading and screen flashes like its going on/off really fast.
When im trying to flash stock rom from sammobile.com it fails with error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_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> 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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Wow im so blind
Accidentally downloaded n5100 when i have n5110... but it wont even then work. atm trying to install cm trough recovery but it stucks at installing update and suddenly boots to note 8 logo and sits there :crying: wiping data says error "Error mounting /data!" is that problem? Ofcourse its error so its problem but how huge problem is that?
Hi,
a friend of mine got is Galaxy note 2 stuck on a bootloop and we doesn't know what happened. The phone doesn't boot to recovery, only to download mode.
I'm trying to solve his problem but i'me having a lot of difficulties.
I installed all the things needed to do a factory reset:
Install drivers;
Intall ADB & Fastboot
download firmwere from samsung
download MJ5 bootloader
pit file to repartition
downloaded odin 3.07;3.09;3.10
but every time i use any of the odin versions to change the bootloader ou flah the PDA i get the same error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.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> 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> param.bin
<ID:0/004> tz.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can any one tell me what could my problem be?
I have a samsung galaxy note 2 since last 2 years. Have been using Cyanogenmod with philz touch recovery from last year without any issue.
Yesterday i put my phone on charging at night as usual and when i woke up in the morning the phone was off. I tried to switch it on but it gets stuck on Samsung Galaxy note 2 logo. Tried to enter recovery but it takes me into stock recovery and into download mode. Cannot access Philz recovery. Tried flashing recovery again from odin but get this error
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007>
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
tried again on a different usb port then got this
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
How do i fix this issue?? Any help would be really appreciated......
coolmob1 said:
I have a samsung galaxy note 2 since last 2 years. Have been using Cyanogenmod with philz touch recovery from last year without any issue.
Yesterday i put my phone on charging at night as usual and when i woke up in the morning the phone was off. I tried to switch it on but it gets stuck on Samsung Galaxy note 2 logo. Tried to enter recovery but it takes me into stock recovery and into download mode. Cannot access Philz recovery. Tried flashing recovery again from odin but get this error
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007>
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
tried again on a different usb port then got this
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
How do i fix this issue?? Any help would be really appreciated......
Click to expand...
Click to collapse
first flash the stock recovery of your current android version, then it should reboot. after that flash custom one.
nitol said:
first flash the stock recovery of your current android version, then it should reboot. after that flash custom one.
Click to expand...
Click to collapse
Tried this, dsnt fix anything. Same error as before.
Today morning i tried booting the phone again and it wont boot only.... no light, no display, just plain dead. i tried changing the battery with one of my friends still nothing. Took it to a repair shop and he tried changing the main board but the screen still wont show anything. He says its looks like both the board and the screen circuitry are gone.
I cant understand how can both the screen and the main board blow off together!
Hello, i have one piece n7100 16gb that was stuck on repair mode...i tried to repair it with odin on windows 10 detected the device but fail: Used Odin3_v3.10.7 and N7100XXUFNL1_N7100OJVFOD1_LYS
Tried on windows xp still fail same..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Tried flashing with 16gb pit file...fail now when turn on phone shows grey screen but goes into download mode....help
andrew21 said:
Hello, i have one piece n7100 16gb that was stuck on repair mode...i tried to repair it with odin on windows 10 detected the device but fail: Used Odin3_v3.10.7 and N7100XXUFNL1_N7100OJVFOD1_LYS
Tried on windows xp still fail same..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Tried flashing with 16gb pit file...fail now when turn on phone shows grey screen but goes into download mode....help
Click to expand...
Click to collapse
search for note 2 partition problem, there are multiple guidea on xda. keep trying with different versions of odin and roms from sammobile
yaro666 said:
search for note 2 partition problem, there are multiple guidea on xda. keep trying with different versions of odin and roms from sammobile
Click to expand...
Click to collapse
Hello, when i go into download mode i get following info:
Product Name: GT-N7100
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
KNOX WARRANTY VOID: 0
RP SWREV:
ALso, i tried flashing 4 files with odin, i get following log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_OJV_N7100OJVDMB1_679347_REV04_user_low_ship.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..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i forgot to mention i flashed only the folllowing pit file: PIT_N7100_16GB_20121102 with Odin3_v3.10.7 after which i get grey screen when i switch on the mobile, but i can still go into download mode....pleeeeaaasssee help
Also need to inform im using windows 10 but with correct drivers and connects with odin.
Cant anyone please help me...tried different roms and firmware still same problem...
I believe the eMMC chip has failed. The same happened to my phone and the service guy said i needed a new motherboard.
Some say it may also be a corrupted bootloader, which i have had no luck in fixing.
Wish i could help
It's ok thanks for informing me at least
Love to hear if you get it up and running again
I would love that too but don't have any solutions at the moment