Ok, I know someone is going to yell at me. I have searched for 24 hours on this site before deciding to post. Please don't verbally assault me too badly. Here is what happened, overnight, the phone must have gotten an OTA update. It is now frozen at the Samsung Galaxy screen.
I cannot get to CWM which I did have on 4.1.1
I can only get to download / ODIN mode (vol down, home, power.) So I downloaded Odin 3.07 (the newest i think)
I downloaded KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 (AFTER A LOT OF SEARCHING!)
I can get Odin to see my phone, com4, I put the above file in PDA and eventually get this....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong? Is it the wrong file I am trying to flash? Is there any way to get CWM back? Because I do have semi recent backups. ANY help would be appreciated. I'm pretty much willing to pay somebody at this point.
Thanks and sorry if I missed the thread on this. I REALLY tried via google and internal XDA searches
- Keith
AT&T Galaxt note 2
Hoping those keywords garner more attention. I am still stuck with a non working phone and my SIM is in an iPhone 4s..... yuck
Also I have a PIT issue?
keithh85 said:
Ok, I know someone is going to yell at me. I have searched for 24 hours on this site before deciding to post. Please don't verbally assault me too badly. Here is what happened, overnight, the phone must have gotten an OTA update. It is now frozen at the Samsung Galaxy screen.
I cannot get to CWM which I did have on 4.1.1
I can only get to download / ODIN mode (vol down, home, power.) So I downloaded Odin 3.07 (the newest i think)
I downloaded KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 (AFTER A LOT OF SEARCHING!)
I can get Odin to see my phone, com4, I put the above file in PDA and eventually get this....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong? Is it the wrong file I am trying to flash? Is there any way to get CWM back? Because I do have semi recent backups. ANY help would be appreciated. I'm pretty much willing to pay somebody at this point.
Thanks and sorry if I missed the thread on this. I REALLY tried via google and internal XDA searches
- Keith
Click to expand...
Click to collapse
At least with the MD5 file I am trying to load, It says I need a PIT file. Which I have downloaded, but it just sits there for what seems like forever then gives me this error....
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
keithh85 said:
At least with the MD5 file I am trying to load, It says I need a PIT file. Which I have downloaded, but it just sits there for what seems like forever then gives me this error....
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
Click to expand...
Click to collapse
Hey, I used to flash my phone like 3-4x a week and the I bricked it, this video helped me get back on my feet, hope it helps. Just go from there as a base and then you flash whatever you need to install on your phone. Good luck!
http://www.youtube.com/watch?v=WwNOAgopXvc
Pit file? I have found 2 PIT files. neither work
Looks like my phone needs to be re-partitioned also? I am completely lost. Reading some of the threads that might mean my internal memory went dead. Anyone?
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
keithh85 said:
Looks like my phone needs to be re-partitioned also? I am completely lost. Reading some of the threads that might mean my internal memory went dead. Anyone?
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Try different USB port.
2) did you put your md5 file in a folder? If so check folder name.
3) Run odin as admin
reply
A_youu said:
1) Try different USB port.
2) did you put your md5 file in a folder? If so check folder name.
3) Run odin as admin
Click to expand...
Click to collapse
Yes to all 3.... I read something about SDS (Sudden death syndyronme) on galaxy phones. I think that's what happened. I really don't know but I cannot flash anything without needing pit file.
keithh85 said:
Yes to all 3.... I read something about SDS (Sudden death syndyronme) on galaxy phones. I think that's what happened. I really don't know but I cannot flash anything without needing pit file.
Click to expand...
Click to collapse
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Thanks for the reply, I will try a 4.3 rom
A_youu said:
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Click to expand...
Click to collapse
ODIN MODE (red)
Product name:
Current Binary: Samsung Official
System Status: Custom
Android guy
Downloading...
Do not turn off target!!
your other question...
A_youu said:
Can you post what it says on Download mode screen? Also, is it OTA update from At&t? If so may be it updated your bootloader version to 4.3. So, try to flash 4.3 rom (may be you can try stock).
Click to expand...
Click to collapse
Yes, AT&T kept telling me I needed to update. I would try to kill the screen but it would keep popping up over and over. So I finally let it download with the intention never installing it. I guess it did it without my knowledge.
PIT file....
I finally got ODIN to make some progress... But I do not know what to do from here. Picture attached.
keithh85 said:
I finally got ODIN to make some progress... But I do not know what to do from here. Picture attached.
Click to expand...
Click to collapse
Ok, Can you try to flash new stock rom? You can follow here - http://forum.xda-developers.com/showthread.php?t=2589891
Also, make sure that you don't flash "AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)" bootloader as this bootloader is only for 4.3 leaded version.
Failed
A_youu said:
Ok, Can you try to flash new stock rom? You can follow here - http://forum.xda-developers.com/showthread.php?t=2589891
Also, make sure that you don't flash "AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)" bootloader as this bootloader is only for 4.3 leaded version.
Click to expand...
Click to collapse
Same result... Here is the screenshot.
keithh85 said:
Same result... Here is the screenshot.
Click to expand...
Click to collapse
When Odin fails, are you getting any message on the phone itself? If you look in the top left corner it should display some information. Mine will usually give me a message when Odin fails.
phone screen
cameron213 said:
When Odin fails, are you getting any message on the phone itself? If you look in the top left corner it should display some information. Mine will usually give me a message when Odin fails.
Click to expand...
Click to collapse
No the phone never changes.
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
flymacs said:
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
Click to expand...
Click to collapse
I will give it a shot. I have nothing to lose at this point. I've been on an iPhone for 3 days now
flymacs said:
I'm "guessing" you may be having a problem with the ota bootloader. I've seen luck with this thread in restoring a soft bricked phone due to trying to flash from the ota 4.3 to the leaked 4.3:
http://forum.xda-developers.com/showthread.php?t=2581321
Might be worth a try. Hope it helps
Click to expand...
Click to collapse
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
keithh85 said:
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
Click to expand...
Click to collapse
Do you have pit file? If so try to give all files together in Odin -
pit file in "PIT" & select re-partition checkbox
ROM in "PDA"
and try to flash.
keithh85 said:
I will try again but I see I already have that file on my PC. If I try to flash it, it fails and it says no PIT partition found. I am starting to think I have a hardware issue.
Click to expand...
Click to collapse
Had posted a possible solution for you over on general then saw this thread...
http://forum.xda-developers.com/showpost.php?p=49378159&postcount=62
Includes link to the pit file
Related
So i was trying to run Odin, so that I could update my firmware to 2.2 use the ECO3 method. And it got unplugged while doing it, oops
First it had the bricked little icon with phone and computer and lilttle orange triangle. And then it is just a black screen
When i try to power it up, you can tell that it is one, but it is a dim backlit black. i can sometimes connect it to odin.
any other solutions/roms/updates, or anything i can do to fix it, I WANT MY PHONE BACK
PLEASE HELP!!!!
string14 said:
So i was trying to run Odin, so that I could update my firmware to 2.2 use the ECO3 method. And it got unplugged while doing it, oops
First it had the bricked little icon with phone and computer and lilttle orange triangle. And then it is just a black screen
When i try to power it up, you can tell that it is one, but it is a dim backlit black. i can sometimes connect it to odin.
any other solutions/roms/updates, or anything i can do to fix it, I WANT MY PHONE BACK
PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have cwm? If do, flash any of the ec07 roms and imnuts hacked kernel. If that doesn't work (it should, unless you tried to repartition) then hit irc, and I'll see if I can help. All of the roms and the kernel are in Ciscogee's database sticky.
PERCEPTION IS REALITY
Thanks for the fast reply, and no, I do not have clock work, how do i get it through download mode only, because odin doesnt seem to flash things on my device well,
any other solutions?
http://androidforums.com/continuum-...rap-i-screwed-my-phone-up-recovery-guide.html
thanks again, i was able to run the odin thin again, but it stops and says
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I400-EC07-FROYO-REL-PRODUCTION.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
help again
Can you read through the forum before creating a thread please?
Sent from my SCH-I400 using XDA App
string14 said:
thanks again, i was able to run the odin thin again, but it stops and says
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I400-EC07-FROYO-REL-PRODUCTION.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
help again
Click to expand...
Click to collapse
Make sure repartition is checked, and you are using the pit file.
PERCEPTION IS REALITY
I did, I have done al that you have told me
string14 said:
I did, I have done al that you have told me
Click to expand...
Click to collapse
Keep trying. That isvthe pain of Odin. It's simple uservinterface, but it doesn't alswaysvwork, the first time. I've had to flash something 4 times before before itvwould pass, and i know I was doing it right. The alternative is HEIMDALL. More complicated, but I've never had a fail when I did it right. I'll be in irc in a few ifvyouveant me to walk you through heimdall.
PERCEPTION IS REALITY
Thank you so much, yeah, could you walk me through it? Please?
I need my phone to work, and the COMport is always messed up, or the write operation fails
Since I don't see you in irc, go here:
http://forum.xda-developers.com/showthread.php?p=18698679
There is a link on there for a tut I made for using heimdall for this situation. And that thread contains everything you need (except 7zip). I'll be in irc in a bit, and be there for most of the day, likely.
PERCEPTION IS REALITY
OK, i found a tutorial on heimdall, but while flashing i get
ERROR: Failed to access device. libusb error: -12
WHAT NOW????
string14 said:
OK, i found a tutorial on heimdall, but while flashing i get
ERROR: Failed to access device. libusb error: -12
WHAT NOW????
Click to expand...
Click to collapse
That is a driver issue. either reinstall the heimdall drivers, or unplug and replug and try again. I'm in IRC now.
Hi everybody,
I didn't download or flash anything recently, and was on 4.1.1 stock firmware. My phone was working perfectly last night. I woke up this morning, and it was stuck on the Samsung boot logo and very hot from the charger.
I was panicking, and quickly loaded up ODIN and tried to download the same firmware I had before. I can't get a yellow bar in ODIN no what I try. I never had this issue before. I have been reading and trying different things for the past 4 hours. I am using the original USB cable, tried all the different USB ports, a different PC, re-installing the drivers, re-installing Kies, re-installing ODIN, and nothing seems to give me the yellow bar in ODIN.
I cannot boot into recovery mode, only download mode. Please help, I'm very worried my phone could be bricked somehow
Seems there is no PIT partition??
If it matters, here is what I get when I try to load firmware without the Yellow bar in ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I have just downloaded the toolkit and trying it. It keeps saying "waiting for usb debugging mode to be enabled"
cheetahpro said:
Hi everybody,
I didn't download or flash anything recently, and was on 4.1.1 stock firmware. My phone was working perfectly last night. I woke up this morning, and it was stuck on the Samsung boot logo and very hot from the charger.
I was panicking, and quickly loaded up ODIN and tried to download the same firmware I had before. I can't get a yellow bar in ODIN no what I try. I never had this issue before. I have been reading and trying different things for the past 4 hours. I am using the original USB cable, tried all the different USB ports, a different PC, re-installing the drivers, re-installing Kies, re-installing ODIN, and nothing seems to give me the yellow bar in ODIN.
I cannot boot into recovery mode, only download mode. Please help, I'm very worried my phone could be bricked somehow
Seems there is no PIT partition??
If it matters, here is what I get when I try to load firmware without the Yellow bar in ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I have just downloaded the toolkit and trying it. It keeps saying "waiting for usb debugging mode to be enabled"
Click to expand...
Click to collapse
I have the exact same problem right now with my phone.
have you found any solution?
Anti_virus_abdo said:
I have the exact same problem right now with my phone.
have you found any solution?
Click to expand...
Click to collapse
Download and flash pit file, then flash stock, or if you have custom recovery then download recovery flashable stock rom and flash using sideload.
Mufrad said:
Download and flash pit file, then flash stock, or if you have custom recovery then download recovery flashable stock rom and flash using sideload.
Click to expand...
Click to collapse
i'm struggling same problem during laast 5 days and tried almost everything for solve this problem.
i tried to flash stock recovery but phone didnt react and odin failed with "there is no pit partition". i dont want to use pit for reparttion and erase all my personel stuff on my phone but give up lastly and used pit file with stock recovery.but beside odin worked at start but stopped the screen that "setting parttion"
please helppp???.i dont want to send my phone to guarantee service because of they eraase all my personel stuff c
@dr.ketan
cagriekim said:
i'm struggling same problem during laast 5 days and tried almost everything for solve this problem.
i tried to flash stock recovery but phone didnt react and odin failed with "there is no pit partition". i dont want to use pit for reparttion and erase all my personel stuff on my phone but give up lastly and used pit file with stock recovery.but beside odin worked at start but stopped the screen that "setting parttion"
please helppp???.i dont want to send my phone to guarantee service because of they eraase all my personel stuff crying:
Click to expand...
Click to collapse
unfortunately you have to, it's not an option.
Anti_virus_abdo said:
unfortunately you have to, it's not an option.
Click to expand...
Click to collapse
could u solve the problem????
cagriekim said:
could u solve the problem????
Click to expand...
Click to collapse
No, it's not a software problem, it's SDS :/
so i am going to replace the motherboard, and i am out of warranty because i bought it from more than a year, so i am going to pay 220$ for the replacement.
I'll NEVER EVER buy a crappy Samsung device again.
Hi. I tried following a simple guide to rooting my S3, but it failed horribly. I followed the steps (download Odin+this file, load the file into Odin, hit Start and bam your phone's rooted) but it failed. Here's the log from Odin.
Code:
<ID:0/003> Added!!
<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/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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Now my phone won't run properly, it says to run Kies in recovery mode or something but I don't understand. In retrospect I should've downloaded Kies onto my computer first, as well as SU onto my phone, and I probably should've found out my model number, but here I am.
I'm not trying to install a custom OS, I just want root access so I can use root-only apps. Can anyone tell me how to save my phone?
if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward
You may just have bricked your phone, because that package was for the international variant.
relieved
jdelano said:
if you have a custom recovery installed go here
http://forum.xda-developers.com/showthread.php?t=2248798
if you need to use odin to restore your phone to proper working order go here
http://forum.xda-developers.com/showthread.php?t=2247844
good luck, make sure to read everything about what you attempt to put on your phone going forward
Click to expand...
Click to collapse
Wow, thanks a lot man! I will be sure to!
seb0910 said:
Wow, thanks a lot man! I will be sure to!
Click to expand...
Click to collapse
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171
jdelano said:
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
If it's a true brick then that won't work, because in a real brick the phone doesn't even turn on. When that thread refers to a brick, it's really referring to a soft brick which is easy to recover from.
yes, I am assuming soft because the OP said "Now my phone won't run properly", not it won't turn on. I know its bad to assume but I took the leap any way
The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1
griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.
Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.
griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.
Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.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> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?
Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
alex2003881 said:
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
Click to expand...
Click to collapse
Same happened to my phone too and no luck. still stuck! Someone help please!
If you can boot into Odin mode, flash a stock rom from sammobile.com.
audit13 said:
If you can boot into Odin mode, flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
I tryed this no result
What happened when you used Odin? Post the Odin log?
audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
Nand write fail. Or Sometimes, complete write operation failed!
audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
When i try to put rescue firware with odin says setup connection after that fail.
Tomorrow i'm going to samsung official service.
I'll comeback with edit!
karanvirkohli said:
Nand write fail. Or Sometimes, complete write operation failed!
Click to expand...
Click to collapse
What does the log actually say? It probably failed when trying to flash a certain file.
Did you try different USB cables and USB ports?
Flash repair firmware
4 file
Sent from my GT-N7100 using Tapatalk
Hey, sorry for hijacking your thread.
I have the same problem. I tried many different scenarios and I couldn't fix it. I gave up and went to Samsung and after 48hs I called finding out that they refused to fix it. Talked to the IT guy and he said he has no idea how to fix it and told me the only fix is to change the whole motherboard and he said its not suggested to do so as its expensive. I have no idea what I should do. I flashed custom recovery, stock recovery. Tried to separate the whole firmware and flash it piece by piece using the skipsoft tool. I tried flashing PIT files with custom recovery, stock recovery, stock rom I have tried multiple PIT files from multiple websites.
This happens when I try flashing stock rom downloaded by samfirm or sammobile.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_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..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
If I to flash a PIT file using any of the scenarios mentioned above I get this ( the 4 files repair rom in this example )
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.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> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.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_XEF_N7100OXADLJ2_422394_REV00_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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
It will keep doing this forever until I unplug the cable. I'm running stock Kitkat 4.4.2 but all methods I find are for older versions with different bootloaders yet I still tried them as there are no recent fix from what I can find.
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
audit13 said:
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes I did all that. Same error. If I extract the tar file and do another odin flashable tar using skipsoft tool it doesnt work, removing one file at a time didnt work either. I tried the latest on sammobile, the latest on sammobile for my country, and the latest from Samfirm for my country. I also tried using SmartSwitch and Kies recovery using the serial number and model number and they don't recognise the phone during downloading like about 60% of downloading it will show an error that it doesnt recognise it.
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
audit13 said:
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
Click to expand...
Click to collapse
Same exact error of post #10
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md 5 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> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
audit13 said:
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
Click to expand...
Click to collapse
Odin screen that is in download mode ? Yes it says GT-N7100.
You're using the latest ROM for the phone? Which country?
audit13 said:
You're using the latest ROM for the phone? Which country?
Click to expand...
Click to collapse
Yes. Egypt. I have used both latest on sammobile and download by using samfirm. I have tried both of them. I have tried indian and few other countries all lead to the same error.
Are you using the original Samsung cable?
audit13 said:
Are you using the original Samsung cable?
Click to expand...
Click to collapse
It is not the one that came with the phone but it is one that I bought from Samsung. I also tried few other cables that came with LG and Asus phones.