Hi,
I tried to fix an old Note 10.1 GT-N8005 which is in a boot loop, it displays the Samsung Note Logo and resets forever. I can run Odin with Volume -.
I tried Odin on W10 with a stock file and Odin says it's a success (see below), but the Boot loop is still there. Odin on the tablet gives a strange information, that says INVALID RPMB DATA.
I googled around, I found that there might be a problem with the eMMC, might... I don't think so, because my wife told me, that the tablet worked ok until Samsung started an OTA Update, since the there is a boot loop. I don't think, that a Update can damage the hardware.
Any idea how to fix ist, if this error occurs and the eMMC might be ok?
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1673 M
<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> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Related
Hi, I followed everything in the how to get root video on the Galaxy S4, but when I tried to flash it to the 423399 kernal (so I can eventually obtain root), it failed. No I am stuck. I can only get to the odin download screen and if I just try to boot it normally it goes to the firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. When I reboot into Odin download, its connected and I load the 423399 into PDA then Start. Here's what I get.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MD2_423399_Kernel.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> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know why but it keeps Removing. I am no longer getting a blue load bar under the Downloading... Do not turn off target!!
I can not get into recovery mode either.
Any help would be much apprectiated!
I tried the "Unbrick method" by flashing the stock restore. Didn't work.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
PaulJ69 said:
I tried the "Unbrick method" by flashing the stock restore. Didn't work.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
is usb debugging turned on on the phone?
theidoctor said:
is usb debugging turned on on the phone?
Click to expand...
Click to collapse
He said he can't get his phone to load so therefore he can't enable USB debugging. I sent you some info to try and assist you. Message me back if you need anything.
So after trying a ton of different things and kept getting the same
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
I figured it was something on my end removing the connection. I took out the USB cable and plugged it directly into the back of the motherboard and Bingo! it worked!
Thanks again DarkMenace for sticking it out with me!
PaulJ69 said:
So after trying a ton of different things and kept getting the same
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
I figured it was something on my end removing the connection. I took out the USB cable and plugged it directly into the back of the motherboard and Bingo! it worked!
Thanks again DarkMenace for sticking it out with me!
Click to expand...
Click to collapse
Anytime.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
hello,
I just try my Tab2 also to flash. I get always the flash process via odin following message:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.5.1.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anybody help me?
Greetings Coldjack
coldjack said:
hello,
I just try my Tab2 also to flash. I get always the flash process via odin following message:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.5.1.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anybody help me?
Greetings Coldjack
Click to expand...
Click to collapse
It might be the same mistake I made when flashing my phone.. I didn't run Odin as administrator in win7. After I did run it as administrator the error was gone.
But.... I also had a similar error with bad files so it could be that too.
Sent from my GT-P7510 using XDA Free mobile app
Hi, l made it as Administrator.
And there comes the error.
Greetings coldjack
Tried rooting my phone, stuck on startup screen and download mode.
Didn't work so I am now trying to install stock firmware.
When in Odin3, there are different things that happen. It says "Added!!" Sometimes I get stuck at setupconnection, but other times it initializes and i get a nand write start fail.
I am using Odin3 v3.10.6
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCV_G925FH3G1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also get this failure sometimes
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCV_G925FTEF1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
SM-G925F
I have already tried different USB ports, different cables
I can't restart because on the boot screen i get a "recovery is not seandroid enforcing" message.
I'm having the same issue with a non-edge S6, did you find a way to solve it? How did you solve it?
how long does it take normally to flash a rom? I'm trying to flash a stock rom from a hard brick and my odin just sits at setup connection and doesn't move and doesn't get an error either.
If it is hard bricked then nothing short of a jtag will save it.
Hi
i updated my S III with stock firmware with 4.3 (I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5) via Odin. It was successful and worked fine for a few days, but after 3 or 4 days my phone get stucked on Samsung logo screen, i tried wiping data and cache from recovery, but problem is same. So i am trying to re flash my phone with same stock rom. But i am not able to do it.
I am using Odin 3.07,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_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> 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)
<ID:0/004> Removed!!
I also used to Root it with cf auto root,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried using different USB ports and USB cables?
audit13 said:
Tried using different USB ports and USB cables?
Click to expand...
Click to collapse
Yes Tried, Recently my S III was updated via same port and USB Cable,
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
audit13 said:
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
Click to expand...
Click to collapse
Yes I tried, Here is result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_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> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Stuck on Get PIT for mapping,
Since it is stuck on the pit file, this leads me to believe that the cable is not compatible or the internal memory is damaged.
I have flashed many different Samsung phones over several years and I find that USB cables can cause the flash to fail when Odin is trying to read the partition information (PIT), flash a bootloader, or flash the system image.
I had a Movistar (Spain) firmware installed on my Samsung S5, and I wanted to replace it with some default Samsung firmware. It was working for a while but now it's stuck in Samsung logo bootloop. I tried like 5 different firmwares, one of them launched the phone but had some password on it, one of them just wouldn't go past the launch logo, one of them caused my motherboard to overheat like crazy, and last one gave me an error while trying to do the upgrade "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I was doing the upgrades with Odin. Please help me select the right firmware, I'm afraid to carry on on my own, I feel like I'll just do more damage.
Edit: I got this error in Odin when I tried flashing G900FXXU1CQDC
<ID:0/007> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4137 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> persist.img.ext4
<ID:0/007> userdata.img.ext4
<ID:0/007> modem.bin
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)