Well I just had my phone replaced today due to a bad proximity sensor. I got home and decided to update it to EB18 with root from this thread. Well Odin crashed on me. I tried again and selected Odin3 1.61, selected the pit and tar, selected repartition (per instructions) and clicked start. I let it sit for 30 minutes and still no response. This is the response from Odin and the phone is in download mode with no blue progress bar. Odin is recognizing the phone when I connect it to the computer.
<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> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
Click to expand...
Click to collapse
The 1 + power button puts me in download mode. Whenever I just press the power button I see an icon that is a cell phone + caution + computer. I've tried two different cables (one even worked 100% on my old phone), different USB ports and different computers. I tried the stock tar/pit and even the Samsung update app for 2.2. I still cannot Odin this phone successfully. Anyone have any other ideas?
Try Odin again, as long as you can get into Download Mode, you are NOT bricked.
Be sure to follow EXACT instructions.
If it was bricked it wouldn't turn.on at all. Its like that cause it doesn't have anything to.boot up. Try downloading the tar file again.
Sent From My Evo Killer!
Well you guys must have brought me some luck. I tried Odin1.7 and it seems to be successfully flashing DI18 rom. *crosses fingers*
Edit: After hours of trying it finally flashed successfully to DI18 but will not flash to any other version (EB13 Extended will just sit at "Set PIT file..").
Are you using a pit file? Of it flashed to di18 and wont to eb13 then try redownloading the tar file. Might be a bad download
Sent From My Evo Killer!
musclehead84 said:
Are you using a pit file? Of it flashed to di18 and wont to eb13 then try redownloading the tar file. Might be a bad download
Sent From My Evo Killer!
Click to expand...
Click to collapse
Yep I'm using the .pit that was included with the EB13 Extended archive. I followed the instructions and checked Re-Partition and then it sits at:
<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> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
Click to expand...
Click to collapse
If I use other stock roms (EB13, DI18, DK28) I will used s1_odin_20100512.pit or victory_8G_100528.pit and follow instructions and NOT click Re-Partition and I get
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.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> param.lfs
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Another odd thing is if the phone is turned off and I connect it to the USB cable, it will boot into the Android system recovery (2e) automatically.
I'm at a loss on why this will not flash. I had zero problems with my last phone (other than the stupid proximity sensor) and this replacement phone just wants to fight me.
Don't use the pit file when trying for the regular eb13 file. Sometimes the pit file causes mine to fail so I quit using them. Try that once.
Sent From My Evo Killer!
Still no go. Keeps failing at params.lfs. I've tried 2 computers, 3 different usb cables, multiple usb ports. I don't know what to do.
Re-Partition checked = Sits at Set Pit File and then nothing.
Re-partition unchecked and with or without pit file = automatic failure.
I spent the last few hours and $35 replacing this phone for nothing.
I appreciate the advice though.
Well I finally got EB13 installed. I pulled out an old netbook and installed the Samsung drivers.
1. Started up Odin3 1.61
2. Removed battery from phone
3. Connected USB cable to phone
4. Connected USB cable to netbook
5. Power + 1
6. Added s1_odin_20100512.pit
7. Added SPH-D700-EB13-8GB-REL.tar.md5
Funky but I finally have a working Epic 4G. I ain't even going to try to root this bastard.
I believe EB13 extended is already rooted.
Mugen678 said:
I believe EB13 extended is already rooted.
Click to expand...
Click to collapse
I opted to go for the stock EB13 instead of the extended.
Related
I've tried every method I can but none seem to work for my Epic I'm thinking about throwing it down the balcony a calling sprint and tell them I need a replacement so if there any way to help please please let me know??? Miss my phone!!!!!
Looks like your in download mode unplug the usb cable and boot into download mode then odin something.
I EnFamouz I said:
Looks like your in download mode unplug the usb cable and boot into download mode then odin something.
Click to expand...
Click to collapse
I tried it Odin isn't recognize the device.
He's not in download mode anymore, this is just the phone telling you it doesn't have a connection to a machine to get boot informaion from and that there is no firmware to boot it self from.
Do a battery pull and read one of the other 99 threads with the same title as yours.
Sent from my SPH-D700 using XDA App
yaboyloudog said:
I tried it Odin isn't recognize the device.
Click to expand...
Click to collapse
Oh and you can't get into download mode.
Kcarpenter said:
He's not in download mode anymore, this is just the phone telling you it doesn't have a connection to a machine to get boot informaion from and that there is no firmware to boot it self from.
Do a battery pull and read one of the other 99 threads with the same title as yours.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did they all say pull the battery and hold both volume keys till you get into Download Mode (which isn't happening) then flash a new ROM. And those post are for other galaxy devices haven't seen one for the Epic.
what did you do before this happened?
yaboyloudog said:
I did they all say pull the battery and hold both volume keys till you get into Download Mode (which isn't happening) then flash a new ROM. And those post are for other galaxy devices haven't seen one for the Epic.
Click to expand...
Click to collapse
You don't hold down the volume keys on the epic. You open the keyboard and hold the 1 key and the power at the same time. That will put you into download mode. Than odin should recognize your device.
Sent from my SPH-D700 using XDA App
hugo87 said:
You don't hold down the volume keys on the epic. You open the keyboard and hold the 1 key and the power at the same time. That will put you into download mode. Than odin should recognize your device.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Your Greatness at it peak all these ppl developer and then there you a genius.....Thank you....but what do I do now.
ok got it but what do I do now
<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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
yaboyloudog said:
ok got it but what do I do now
Click to expand...
Click to collapse
This is what I keep getting...
<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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
yaboyloudog said:
This is what I keep getting...
<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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Reboot computer and phone. Try a different USB port, try a different USB cable. Phone MUST be in download mode for this to work. Keep trying, if it fails, exit Odin, open it again and keep trying. Be sure to unplug and replug the USB cable between Odin attempts.
Some people have had success by removing the SD card prior to using Odin.
Keep trying, it can take multiple attempts before it works.
Its working Thanks your the best...
yaboyloudog said:
Its working Thanks your the best...
Click to expand...
Click to collapse
Glad to hear that.
the exact same thing is happening to me... but i'm stuck on the odin.
this is what i'm getting..
Code:
<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> boot.bin
<ID:0/004> factoryfs.rfs
Just keep trying. If you still cant get it redownload the tar file again. It takes me 5 trys sometimes.
Sent from my Evo killer!
Make sure you're using latest version of odin 1.61 I think. Also make sure you put tar file in pda... not phone.
Sent from my SPH-D700 using Tapatalk
issues with Odin
I ran into a lot of issues getting Odin to flash the stock ROM on my Epic, including Odin errors, and Odin hanging on " SetupConnection..", but here's what I did to finally get this to work:
-pulled battery and SD card from Epic
-launched Odin just after a reboot of PC
-plugged into PC via USB and held power and the 1 key to get Epic into download mode (SD card and battery still pulled)
-used PIT: victory_8G_100528.pit
-used tar (in PDA section): SPH-D700-DG27-8Gb-REL.tar
-only had the option "auto-reboot" selected
With this scenario, I was finally able to get my Epic back to stock. Thanks to everyone who posted before me on this subject.
On a side note, I'm not 100% whether or not my phone was bricked, but it wouldn't get past the initial Samsung boot screen after I had tried to install some non standard software.
Just downloaded DI01package3.tar.tar from adrynalyne's post in xda.
were using EB01 SC 2.4 with voodoo so disabled voodoo lagfix and system lagfix in red cwm.
Tried to flash DI01package3.tar.tar with odin. (I added this file by clicking PDA)
and got this error
<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> Sbl.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
It didnt turn on so pulled battery and tried to turn on
but showed me little picture like this.
(cell phone - triangle(?) - computer)
It seems like I can't even see that picture on the phone now..
help me.. damn.. im scared..
Was your phone charged? Do Odin again. I would go for dj05
Leave the battery out, open odin, hold the volume down button and plug usb cable while holdind the vol down and try flashing again.
good day.
tats_06 said:
Was your phone charged? Do Odin again. I would go for dj05
Click to expand...
Click to collapse
Yes, it was charged. I chose DI01 package because I thought it will fix my battery issue and other problems that I didn't notice.
chopper the dog said:
Leave the battery out, open odin, hold the volume down button and plug usb cable while holdind the vol down and try flashing again.
good day.
Click to expand...
Click to collapse
Thank you. I just pulled battery and tried same file with odin and it worked.
I just read your reply after I finish flashing DI01 package with odin.
If I saw it earlier, I could've saved my time, but still thank you.
I was just out of mind so forgot that I posted this in xda.
So I followed this thread exactly, for my rogers I337M
[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY]
http://forum.xda-developers.com/showthread.php?t=2293800&highlight=cf+auto+root
and after I started ODIN after selecting the .tar.md5
I got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
And in it says fail on ODIN. And now when I boot up I can't get to my stock OS
only to a screen where it says, "Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I Can't use my S4 any more . I was wondering if it was because I had a locked bootloader, but the I337M varient should be unlocked right?
I also had the new MG1 firmware before I tried all this, but I saw alot of other MG1 users used this method.
PLEASE HELP, I would be forever grateful.
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
scott14719 said:
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
Click to expand...
Click to collapse
Completely sure.
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
mymusicathome said:
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
Click to expand...
Click to collapse
ok so I got the latest firmware for my device.
Build Date: 01.07.2013 -> Region: RWC (Canada (Rogers)) PDA: I337MVLUAMG1 Changelist: 897376 Android: 4.2.2
I got it from this thread
http://forum.xda-developers.com/showthread.php?t=2269304&highlight=flash+stock+firmware
I got back into the download mode (VOLDOWN/HOME/PWR) with the android icon where it says. "Downloading... Do not turn off target!!" plugged in my device got into odin put the stock firmware in PDA and ran then got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
and my device still doesn't work.
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
jd1639 said:
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
Click to expand...
Click to collapse
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
I really have no idea what to do.. I have 1 year warranty left with this phone, and me trying to CF-Auto root was the only thing I've done that could have voided my warranty, but it failed and now that I'm stuck would I still be okay if I took it in for warranty?
PromyD said:
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
Click to expand...
Click to collapse
Try it on a different computer.
jd1639 said:
Try it on a different computer.
Click to expand...
Click to collapse
agreed. or at least a different usb port. are you using the cable that came with your device? i'm assuming you had usb debugging switched on.
So i've tried it on another computer, but since my device is in download mode it doesn't install any samsung drivers to properly identify and read the S4, so it doesn't work. Can anyone please give me some direct links to download the proper usb drivers on windows for my S4.
http://lmgtfy.com/?q=samsung+galaxy+s4+drivers
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Lo
PromyD said:
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Click to expand...
Click to collapse
You're welcome. Glad to have helped. It's good you got your phone working again.
Ps, nvm
SGH I337M Bricked as well
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Copy a rooted i337M rom to your SD card. Boot into recovery , wipe and flash.
Sent from my SGH-I337M using XDA Premium 4 mobile app
I cannot boot into recovery.
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
OverclockDaS4 said:
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Click to expand...
Click to collapse
Take a deep breath, and try another cable. I find a large portion of flash errors are caused by junky usb cables. If that fails, try another usb port and another pc entirely, if possible. Let us know some more info, someone has already asked, more details the better. Good luck.
Sent from my SGH-I337M
pyrexid said:
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
Click to expand...
Click to collapse
Knox does trip if you root.... not sure there is any method that doesn't...... guess if its important... do some research.. I couldn't find one when I did mine... used CF-auto..... on i337m
A long time ago I sent my phone in for repairs (screen). I factory reset it and lost root. I don't even remember how I rooted it, it was an automated tool. After it came back from repairs, it still had 4.2.2 and MDL (it was a repair shop not Samsung).
Whenever I reset/turn phone off and back on, I get an error about com.android something, but only then, it works normally after. Due to this error, my phone tries to upgrade but fails (thankfully). I want to root my phone but I'm afraid it will fail because of that error. What exactly should I do next? I asked in another thread and I was told Motochopper was the best tool to root on 4.2.2. I just want to get rid of this error then root, that's it, what should I do next?
Moto chopper should work. I'm guessing towelroot would too. https://towelroot.com
Sent from my Nexus 5 using XDA Free mobile app
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
SRCP said:
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
Click to expand...
Click to collapse
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. Last question. Do you think I should flash first or try to root right away?
SRCP said:
Thank you. Last question. Do you think I should flash first or try to root right away?
Click to expand...
Click to collapse
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks.
jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
SRCP said:
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
Click to expand...
Click to collapse
This looks bad. The blue bar on phone moved a bit then stopped and it's stuck there. I tried Odin again and now I get this:
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
I restarted the phone and now I'm on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I did have it connected to a rear usb port, let me change it.
RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
It worked. Tried a different cable and port. I have all my apps, is that normal? I thought this did a factory reset.
Thanks guys. It worked, I'm rooted .
Hi there,
Originally submitted to the note 4 section and realised it may not be quite as active and probably posted in the wrong place, I do apologise for that.
First off, I messed up. I've root my android phones over the years now and it came to the point I wanted to unroot my note 4 and get it back to stock.
This time I forgot to enable usb debugging before flashing to stock
So I can get into download mode, but not recovery mode. If I try to enter recovery mode I get the "firware upgrade issue, connect to kies" message. Trying to flash with odin fails, with multiple firmwares (5.0.1 and 5.1.1) and with my pit file, and trying different usb ports.
I've been googling for 4 hours now, I know how annoying it is for same old threads to be brought up, but nothing has helped me get to the bottom of it.
If someone could go through what I need to do step by step it would be much appreciated. Pretty sure there's a way of sorting it since I can at least access download mode, but I also know it may well be completely messed up.
Many thanks chaps.
Alright guys, looks like I've fixed it. So this is for anyone that stumbles across this thread with the same issue.
So after trying to install stock firmware from Samsung (I also used the pit file for my phone, don't think this is necessary though), and odin failing to flash it (I'll paste the odin log at the bottom of this post), I used "All samsung recovery" that I downloaded from here. http://www.4shared.com/file/bIYubEevba/All_samsung_recovery.html
Using odin v3.09, make sure your phone is in download mode and connect to the PC. Odin should recognise it's detected with a blue box.
Click AP (or PDA in earlier versions I believe) and select the All_Samsung_Recovery.tar zip file downloaded from the link above.
Might take a second to load into odin, it's not crashed be patient. And then click start.
Took my phone about 10 seconds and it was all done, just booted straight into the OS I originally tried to flash, so obviously it didn't fail like odin said.
Ok, so hopefully this will help someone. Let me know if I missed any information that I should add.
Here is the odin log when trying to flash the stock firmware originally:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COI3_N910FEVR1COJ1_N910FXXU1COI3_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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!