Hi, I upgraded my Samsung Note II to the version 5.1.1 with the cyanogenmod rom, but now I would like to downgrade it to the kit kat version 4.1.2 or 4.4.2.
The problem is when I flash it with Odin, the message I get is FAIL. I think it is because of KNOX and because I am not root.
Is it even possible to go back to the previous version? Could somebody help me? I don't know what I'm doing wrong.
This is the Odin log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100OXXFNE1_N7100XXUFND3_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> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks.
Related
Hi
plz help me
i have samsung galaxy note2 GT N-7100
i instill 4.3 china rom from sammobile.com
But i faced a problem i instilling rom with ODIN3 v3.09 and stooped download rom for mobile and not update .
Writing attached to explain what happened on the program ODIN3 v3.09
And where you stopped update
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
can you help me and give me the right solution
Ary22m said:
Hi
plz help me
i have samsung galaxy note2 GT N-7100
i instill 4.3 china rom from sammobile.com
But i faced a problem i instilling rom with ODIN3 v3.09 and stooped download rom for mobile and not update .
Writing attached to explain what happened on the program ODIN3 v3.09
And where you stopped update
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
can you help me and give me the right solution
Click to expand...
Click to collapse
What rom are you currently using?
deivid50 said:
What rom are you currently using?
Click to expand...
Click to collapse
Android 4.1.2 Jelly Bean
Try a different USB port and/or different PC.
thank you dears , I changed pc and I used Odin (3.04 and 3.09) OS (Windows 8 & 7) .
The odin message is
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_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> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<ID:0/010> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thank you dears
Thank you dears , I changed pc and I used Odin (3.04 and 3.09) OS (Windows 8 & 7) .
The odin message is
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_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> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<ID:0/010> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Hello I can not flash the phone via ODIN. i8160
Tried many official firmware, single-file and multifile.
Tried to drop 2.3.6.
Phone does not boot on the logo (in recovery also comes)
Phone did not fall, just in the morning was not involved.
also tried this method http://forum.xda-developers.com/galaxy-ace/ace-2-help/galaxy-ace-2-recovery-mode-doesnt-t2788130
Please help.
Sorry for the English.
<ID:0/010> Added!!
<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> cache.img.md5
<ID:0/010> NAND Write Start!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_GT-I8160_I8160XXLK6_CL1211243_REV00_user_SEC_KEY_LK6_4G.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_GT-I8160-MULTI-CSC-OXELF1_SEC_KEY_4G.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> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
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 dn4 rom on my note n7100 and i want update my bootloader to latest while i trying to update i gott this error
<ID:0/005> 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/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> sboot.bin
<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)
<ID:0/005> Removed!!
<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..
and on the dwnloading mode
SW Rev Check Fail Device 2 Binary 1
anyone knows whats going wrong????
Using Unofficial LineageOS 14.1 (v2awifi). During using my Tab Pro 12.2 SM-T900 I got a failure and switched off my tablet. Since that time I can't start my tablet. Can only turn on my tablet in downloadmode. Can't enter recovery. Tried to flash TWRP, but that is not possible. Because the failure was suddenly, I could not and can't switch and change usb-debugging and media-transfer possiblities.
I tried to install Stock Rom with Odin, got the next faillures:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
And sometimes:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
So I can't flash the stock rom for repairing my ROM. Please help me, so that I can use my tablet again. How to fix PIT-partion ?
I have the same problem. Any resolution?
Same but on an SM-T320. Flashed an appropriate PIT, stock firmware...nothing working. I'm thinking it's a physical issue at this point.