Develop Bugs

[Q] Epic won't pass a phone with pc screen after attempting to root, what do i do?

I've rooted my Evo quite a long time ago so my mom wanted me to root the Epic since it just a phone we have on the Sprint account but never use it for anything, just lays around dead while we pay the bill for it, well she wanted me to root it so that we can use the phone as a hotspot since we leave town often.
I followed the directions from qbkings77 on youtube, however when i was using Odin 1.85 it always failed, so i just wanted to call it a night and try again the next day, well when i tried to reboot the phone it just shows a screen that shows a Phone and a Computer, with a caution sign in the middle of both.
Now because of this it wont boot to any other screen but that and even with it completely off the phone and battery are heating up.
Can anyone please help me?

Get a better cable... like a blackberry cable and try again... 99% of the time odin failing is because of a bad cable! The one that comes with the phone is a POS!
Sent from my SPH-D700 using Tapatalk 2

I have good luck with an HTC one off of Ebay. It's pretty much anything goes besides the Samsung one. I had the plastic tip actually crack in half while Odining.

restart computer try again and switch to another usb slot

akosidarwin said:
restart computer try again and switch to another usb slot
Click to expand...
Click to collapse
This... but with another cable!
Sent from my SPH-D700 using Tapatalk 2

I've rebooted my computer, used different cables, tried other ports etc, however odin is still failing and the phone still will not boot up the os.
Odin Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.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> zImage
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is their something i'm missing or have i just damaged the phone beyond repair

Try redownloading the file it might be a bad download. It happened to me before
Sent from my SPH-D700 using Tapatalk

still receiving same results, but the phone is now going to the Android system recovery on its own when its just connected to the computer
Can I be able to use this recovery in anyway to get the device rooted or must i use odin to place cwm on the device to root it?

Did you install Epic drivers?
Are you running Odin as admin?
Are you trying with a prerooted ROM? I recommend you to go to Dev Section and download a Odinable Prerooted ROM instead a Kernel Root.
Sent from my SPH-D700 using Tapatalk 2

Yes I have installed the Epic drivers, I'm using Odin 1.85, and it's the stock rom I would like to have superuser capabilities on
Sent from my Sony Walkman Z, A Device better than an Ipod in everyway possible :-D

You need a better cable. Try a heavy duty Blackberry cable.
Sent from my SPH-D700 using xda premium

Then use a Stock rom prerooted there a lot in Dev Section.
And yes try to find a BB cable. I rooted Evos, Captivates, Optimus(what a pain) with the same cable.
Sent from my SPH-D700 using Tapatalk 2

issues
trying to odin back to stock
Using victory Tar (downloaded twice)
HAve tried EC03, EL30, and FC09
tried multiple cables
tried running odin (1.61 and 1.82) in admin
When I have re-partition checked it says it cant repartition (f reset not checked)
Wen I don't have re-partition checked I get D:0/004> Complete(Write) operation failed. (f reset not checked)
ANy thoughts?

Make sure to include the victoryxxx.pit file that comes with odin. Check f.reset. also try with no battery.
Sent from my PantechP4100 using xda premium

damonbarnum said:
trying to odin back to stock
Using victory Tar (downloaded twice)
HAve tried EC03, EL30, and FC09
tried multiple cables
tried running odin (1.61 and 1.82) in admin
When I have re-partition checked it says it cant repartition (f reset not checked)
Wen I don't have re-partition checked I get D:0/004> Complete(Write) operation failed. (f reset not checked)
ANy thoughts?
Click to expand...
Click to collapse
What from are you coming from?
If your on mtd rooms like cm9 then you need to have the vicxxx in the pit and put the from in the PDA. I used to have f. Reset checked all the time but I don't any more. After everything is in it spot. I put the phone in download mode plug it in wait for the yellow box and run it. You could you tube qbking77 and watch his videos they are very helpful
Sent from my SPH-D700 using xda premium

[Q] Phone stuck after flashing stock rooted

OK--1st post EVER in a forum, so I feel like I'm gonna get layed into,
but here goes:
Just got Epic Touch two days ago and felt I needed root so I downloaded
and used the EL29 Odin one-click method of flashing the stock rooted ROM.
This was yesterday. No problems. Took 15 minutes. I installed some apps,
then I installed ROM Manager And tried to use it to install CW, but I'm not sure if that was successful, as I tried to do a couple of NAND backups from within the GUI
of ROM Manager and failed both times, going to the stock android recovery screen.
I think I pulled the battery both times.
Then I installed Widget Locker, was playing around with that for a bit, took
a photo and tried to attach it to a text response, then the phone locked while
I was sending that. Pulled battery, wont get past Samsung startup screen.
Looked around a bit, decided to try and reflash using the one-click method.
I get:
<ID:0/006> 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/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> recovery.bin
every time. BTW, I cannot access anything with VolUP+power buttons.
I've tried different combos of that, always Samsung boot screen hang.
I can get into Odin, and Odin sees my device. but never has the device indicated
that anything is happening. No progress bar.
Also, I have tried the two USB cables that i have in all the ports of my computer,
but I do not have another handy.
So I poked around and found this:
http://forum.xda-developers.com/showthread.php?t=1492771
which suggested I individually flash ROM, kernel, and modem.
none of that has worked, either.
Flashing the modem does get a green progress bar(in Odin, not on the device),
but then it hangs at--
<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> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
flashing kernel yields:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_KERNEL_PDA.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> zImage
<ID:0/006> NAND Write Start!!
...and a hang.
So....... haven't foud anything else adressing this. Lotta stuff out there about
careless ICS/CWM brickers, but I didn't do anything fancy, did I?
Just stock rooted, 5 hours of use and blammo.
Thanks for the assistance.

Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?
Edit: If you need them, the samsung drivers are here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Please remove kies prior to installing them. In any case, you should probably uninstall what you have now and install the driver suite if it's still not working, then reboot the pc and try again. Sometimes the drivers aren't working correctly and require a reinstall.

I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure.
Sent from my SPH-D710 using XDA

I think what Rocket meant to say is not use Rom Manager any more.
Sent from my SPH-D710 using XDA

RE:
>> Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?<<<<
I have BOTH installed...but Kies I only installed midway (i.e. this morning)
through troubleshooting. nonetheless i will uninstall/reboot/reinstall/reboot
with these guys. Which is better?
And YES, EVERY time i've tried something with either EL29 oneclick or 1.85 regular Odin, I have always started Odin first, and then plugged the phone in.
If I plug the phone in before putting it in download mode, it just displays an empty battery charging icon, and cannot be turned off except by removing battery.
RE:
>>>>I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure. <<<<<<<<<<
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Thanks for the replies.

iguai said:
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Click to expand...
Click to collapse
It sounds like you're ok but Kies needs to go, it conflicts with the regular drivers and causes issues using odin. Goood luck and let us know how it goes.

make sure the samsung drivers are on you PC/Laptop. make sure your computer sees your phone. I have read that sometimes trying different USB ports and cables can be helpful as well when using Odin. hope this helps.

OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.

iguai said:
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
Click to expand...
Click to collapse
You're likely bricked. Sorry. Rom Manager has been bad for almost all Samsung phones.
Sent from my SPH-D710 using XDA

Allow your phone to charge for SEVERAL hours.
Follow this guide to the letter: http://forum.xda-developers.com/showthread.php?t=1274337
Flash this rom which has root: http://forum.xda-developers.com/showthread.php?t=1703406
If you follow this correctly and your phone does not boot. You are bricked.
Sounds like somehow you reversed the modem or rom and flashed them between the phone and pda (which I hope you didn't because you are bricked if you did... but its good in away because you can take it back and say look what I woke to...).
Let us know if it works...
Edit- and if it does boot, don't ever try to install cwm with rom manager on this phone.

No dice. I am, however, going to give it one more try on a friends computer this evening. That's my last throw though, I think, unless I get some fresh inspiration.
I'll report back tomorrow.

OK---I gave it everything, and no dice.
This phone was bricked.
I believe using ROMManager to try and install CWM f'd some things,
and perhaps when I was trying to do individual flashes
in Odin I flashed a modem in PDA.
Thanks for all responses.

Tried everything and nothing
So I wasn't trying anything crazy with my phone, left it charging, and went to check the time and it was off, tried turning it on and nothing.
I was running CM10 Beta 2... so I went into recovery mode, tried to run do wipe factory reset, wipe dalvik, wipe cache, flash the CM10 again, and it was getting stuck.
Mounted usb on pc and tried to save some files to flash the full tar through odin, in the middle of that copy it failed, so I tried to odin the tar anyway and it was getting stucked.
Tried flashing modem separately - stuck on Wait 2 mintues...
Tried flashing kernel separately - stuck on NAND Write Start!!
Tried flashing rom - stuck
Tried flashing pit file - stuck
Tried one click - stuck
The thing is that I can't just say to samsung service that I didn't do anything to the phone, because when you try to boot in recovery it shows CWM 6..., but only one line, it doesn't really load cwm.
So even if I use a usb jig to reset odin counter, they'll notice I had done some stuff to the phone, even when I wasn't really doing anything when it crashed.
Any new way to fix the phone? I don't have insurance or anything, so I might be pretty much screwed
Anything else I could do? Thank you very much!

[GSM] Unable to flash anything or let any changes to the memory stick.

Ok, so apparently I wrote a huge post and it disappeared because I got logged off.
I posted another long version here.
In short my phone froze while updating and connected to my pc. Pulled everything and now it keeps rebooting. Probably storage related (see link above). No change I made stays after a reboot, app uninstall, file deletion (through root explorer or windows). And here is the thing, I can flash whatever, but it won't do anything.
I tried manual flashing the stock image, it does its thing and then reboots in the same situation.
I tried flashing the individual images using this guide, didn't work.
I tried flashing the stock image using the Galaxy Nexus Toolbox, once again, nothing.
I tried ODIN using:
This guide
And this guide
I even tried creating my own odin file using this guide and one using this guide.
Odin will do stuff for about 25 to 30 minutes. It will then reboot the phone with no changes made. At this point odin will have a square saying RESET!. So after rebooting I check if it will still freeze and reboot by going to settings -> apps. It will freeze and reboot. Pull battery, go into download mode, odin will do some stuff and claim it passed by saying PASS!.
These are the messages posted by odin:
HTML:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODIN_JRO03C.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
I don't know what to do anymore. Besides get some sleep. Tomorrow I will see if I can get odin to dump some logfiles or something.

Uh, what you said is kinda impossible...
Linux permissions revolve around a 0-1000 scale. Root being 0, and no access being 1000.
Odin uses root privilages, and so does CWM/TWRP.
Anyways, I'd just replace the phone.
You most likely corrupted your internal storage, which is near impossible to fix.
Or you screwed up multiple partitions in just the right way where it'll work, but it wont either.
Sent from my Galaxy Nexus using xda app-developers app

rsjc741 said:
Uh, what you said is kinda impossible...
Linux permissions revolve around a 0-1000 scale. Root being 0, and no access being 1000.
Odin uses root privilages, and so does CWM/TWRP.
Anyways, I'd just replace the phone.
You most likely corrupted your internal storage, which is near impossible to fix.
Or you screwed up multiple partitions in just the right way where it'll work, but it wont either.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What is impossible? That nothing seems to work? Because it sure as hell isn't working.
I did find a way to get zip files on my phone using the toolbox, but flashing cm9.1 didn't work.
I do indeed think my memory is corrupted.

No it is not corrupted. I don't think. I think the permission has been messed up... when you're flashing a Rom, does it give you an error, or does it flash successfully? If successfully, the permission is messed up and you need to figure out how to change the permission using adb, which can be used when in recovery mode. Sadly, I don't know much about permission changing, do this is as far as I could help
Good luck, and I hope you fix your phone
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
No it is not corrupted. I don't think. I think the permission has been messed up... when you're flashing a Rom, does it give you an error, or does it flash successfully? If successfully, the permission is messed up and you need to figure out how to change the permission using adb, which can be used when in recovery mode. Sadly, I don't know much about permission changing, do this is as far as I could help
Good luck, and I hope you fix your phone
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
I just tried flashing through cwm again using the temporarily boot from the toolkit. It says:
HTML:
Installing /sdcard/[...].zip
finding update package
opening update package
installing update
fixing fs_size in crypto footer
install from sdcard complete.
And it installed in maybe five seconds.
The crypto thingy has me worried, it's not normal, is it?

Also, I just tried creating a backup with cwm and it said there was an error making a back up image of /system.

One last bump.

Well, I hate to say it, but I think it's a hardware issue. I've seen a few others with the same issue: flashing images seems to work successfully, but they actually didn't flash.
So, just to confirm, you tried flashing the images individually in fastboot and it says "OK" after each one, but nothing ends up being flashed. Is that correct?

efrant said:
Well, I hate to say it, but I think it's a hardware issue. I've seen a few others with the same issue: flashing images seems to work successfully, but they actually didn't flash.
So, just to confirm, you tried flashing the images individually in fastboot and it says "OK" after each one, but nothing ends up being flashed. Is that correct?
Click to expand...
Click to collapse
I was afraid this would be the case. Still weird though how it happened while it was sitting on my desk while connected throught usb.
Anyway, I will be returning it tomorrow.

I bricked my Sprint Samsung Note II SPH-L900 and this is how I fixed it.

I figured I would post this as a basic how to for people who brick their phones because they are in a similar situation.
Sprint Samsung Galaxy Note II SPH L900
Used this root method because it was for Samsung Note II owners who already had Android 4.3.*,
http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-sprint-sph.html
Installed TWRP but it didn't stick to Download mode. I could boot into TWRP when my phone was up even after rebooting but could not boot the device directly into TWRP to access my custom recovery image.
Installed Perseus and Macks Rom AllStar V5.0 after saving them to my SD Card and did this after booting into TWRP from within my stock ROM.
Like an idiot I didn't read all the comments on ChainFire 3D when I was searching root 3d because I'm on a big kick right now of making it all 3d like.
Instead of flashing ChainFire 3d from recovery I used my in rom option since I had all my root programs running nicely and thought why not its just a button click instead of rebooting into TWRP. There was my mistake.
Alright so now I am bricked out of my phone in a boot loop. Nothing is happening but ChainFire said when you install not to freak out if your phone hangs for awhile, pull the battery after two minutes. Well I did and still bricked in a boot loop.
Scour the forums and Internet because I know I still have access to my phone through Odin. I don't have debug mode turned on so I can't even create an ADB shell to my device. That was my first through, run ADB shell, launch TWRP and restore my custom recovery. Would have worked except I had no way of getting to TWRP. Tried installing the Samsung ToolKit. Couldn't recognize my device.
Opened Odin back up and thought why not try to flash TWRP and have it reboot, maybe TWRP will launch. Well I don't know if that would have worked or not because every time I tried to reflash TWRP Odin encountered an error.
Alright, abandoned that idea and did some more research. I knew I could still flash to my phone but I didn't have anything to reset the caches to install another ROM and I didn't want to install something else where things could go potentially worse. I needed my damn phone back. Boom! Found some very helpful articles on restoring to stock and found the stock recovery one click solutions.
I am making this so lengthy in case you are going through something similar where you are stuck in a boot loop, locked out of TWRP but can still flash to your phone with Odin.
These two threads were massive help and they take you to the file locations:
http://forum.xda-developers.com/showthread.php?t=2116490
http://www.sxtpdevelopers.com/showthread.php?t=154
I restarted my phone in download mode which was a little tricky because when I put the battery in it would start booting. Had to make sure volume down, home and power were pressed while sliding the battery in. It's tricky but you can do it with one hand and use the other to insert the battery. Don't give up just because if you put the battery in your phone automatically boots!
I used this specific file. http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
I didn't know if my phone was MA5 or MA7. I was worried that something would be off if I downloaded the wrong one but I chose MA5 oneclick exe and it did the trick. I used the Rooted version that didn't delete my data so when the phone came back on all my changes were still there. Everything from the kernel was gone but my settings and etc were unaffected.
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
So anyways, there are some resources and an additional thread. I'm pretty tech savvy but when the damn thing bricked I wasn't for sure what to do. Hopefully this is semi helpful for someone.
*Cliff Notes:
If you brick yourself out of your Sprint Samsung Galaxy Note 2 (II) and you can't access recovery, go download one of these oneclick solutions from sextape or garwynn (big ups to you guys) and reflash it from download mode using their programs. If you rooted your phone using Odin you will feel right at home with their software and it is no big deal. Phone will be back up in no time.
Edit: So after I got back to my stock ROM and tried to reflash my previous roms they wouldn't stick. E Signature verification kept failing but I still had root. Used CWM Recovery straight out of the app store and rebooted in recovery. Wiped everything. Used the esignature toggle and disabled it. Bam was able to reinstall roms and I am back to tinkering

The title was misleading. I thought you meant a hard brick. What you encountered was a soft brick aka bootloop. Thanks for writing it up for the noobs though.
Sent from my SPH-L900 using Tapatalk 4

Yes title is misleading but great post for us thats need it
Thank u much for ur time to make this
SGN2

I bricked my sph l900 also..I had 4.3 rooted then went to jellybomb had a back up of my 4.3 rooted. Flashed back to it and it's now stuck in note 2 animation. Can't get into recovery or adb. Plz can anyone help ?
Sent from my SM-N900P using xda app-developers app

Is there a fix ?
Sent from my SM-N900P using xda app-developers app

odin oneclick failure
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<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..
<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>
<OSM> All threads completed. (succeed 0 / failed 1)

kevo7000 said:
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<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..
<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>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use the original Samsung USB cable.:good:

new battery issue
gizmoscoop said:
You need to use the original Samsung USB cable.:good:
Click to expand...
Click to collapse
I used every cable I owned oven the original cable for my Note 2. I ended up taking it to sprint and replaced it. With this new note I've had two batteries completely fry. 100 % but will not power on without charger.smh

What is it that you did when the onclick kept failing?!!?
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
I keep running the NA5 Stock NoData exe and it keeps failing

[Q] Odin update from 4.3 to 4.4.2 always fail. why?

1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.

Are you using a full factory firmware?

buhohitr said:
Are you using a full factory firmware?
Click to expand...
Click to collapse
I don't know actually. I just downloaded the file from Sammobile.
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
I don't know actually. I just downloaded the file from Sammobile.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
You have stock rom installed right now right? What is the build of your 4.3 rom? I would try Odin 3.09 and another firmware (maybe the same 4.3 stock rom that you currently installed) to see what's going on...

buhohitr said:
You have stock rom installed right now right? What is the build of your 4.3 rom? I would try Odin 3.09 and another firmware (maybe the same 4.3 stock rom that you currently installed) to see what's going on...
Click to expand...
Click to collapse
Yes I have stock rom installed. Unrooted. Build is JSS15J.P600XXUBMJ6. This rom is the one already installed in my note when I bought it. EDIT: I found this in Sammobile. It might help: http://www.sammobile.com/firmwares/1/?model=SM-P600&pcode=XTC#firmware
I tried to flash the the kitkat rom from Cellular South and Spain. Both didn't work.
Thanks for your time helping me

sure you run ODIN as administrator ?

lightman33 said:
sure you run ODIN as administrator ?
Click to expand...
Click to collapse
Yes I'm sure. Right click then run as administrator then allow

UPDATE: I tried flashing again using Odin. This time I removed everything connected via USB including the mouse. Still, no luck

ivanskie01 said:
1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.
Click to expand...
Click to collapse
I think you first need to get a 4.4 supported kernel when updating to KitKat from JB...atleast that's what you gotta do when flashing from recovery...

ivanskie01 said:
UPDATE: I tried flashing again using Odin. This time I removed everything connected via USB including the mouse. Still, no luck
Click to expand...
Click to collapse
Can you provide a link where you found the CelluarSouth 4.4 firmware??

The Dork Knight Rises said:
I think you first need to get a 4.4 supported kernel when updating to KitKat from JB...atleast that's what you gotta do when flashing from recovery...
Click to expand...
Click to collapse
I'm flashing from Odin, not from recovery
Sent from my SM-P600 using XDA Free mobile app

buhohitr said:
Can you provide a link where you found the CelluarSouth 4.4 firmware??
Click to expand...
Click to collapse
Here it is: http://www.sammobile.com/firmwares/3/?download=28717
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
Here it is: http://www.sammobile.com/firmwares/3/?download=28717
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
It seem to be the full firmware for your p600. I would do a factory reset and try different usb port on your pc (do not use hub). If that still doesn't work give another 4.4 firmware a try to see if firmware related issue. Good luck!

buhohitr said:
It seem to be the full firmware for your p600. I would do a factory reset and try different usb port on your pc (do not use hub). If that still doesn't work give another 4.4 firmware a try to see if firmware related issue. Good luck!
Click to expand...
Click to collapse
I'll try again tomorrow thanks!
Sent from my SM-P600 using XDA Free mobile app

UPDATE
I did the factory reset but still, I can't flash the kitkat firmware.
I also noticed that after one try of flashing and I click the reset button in Odin, the process gets stucked at "SetupConnections". Is this a bug in Odin 3.09 or should I download another Odin?

UPDATE
I tried rooting my note by following this: http://forum.xda-developers.com/showthread.php?t=2490805
I got the same "PIT Mapping issue" and failed.
I also tried flashing a custom recovery via Odin, and failed.
I tried using different downloads of Odin, same issues.
Now I don't know if something's wrong with my Note or my laptop or the USB ports of my laptop.
Help

ivanskie01 said:
I'm flashing from Odin, not from recovery
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
But the method still remains the same, doesn't it? Try flashing a supported kernel first...
Take a nandroid though...

ivanskie01 said:
1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.
Click to expand...
Click to collapse
@ The Dork Knight Rises: Nah...to flash a supported kernel first..makes absolutely no sense in odin mode no kernel is running. The update needs to flash a new bootloader in order to be able to boot 4.4 and that can cause trouble.
When having Samsung kies installed, de-install it and reboot windows
Install these USB drivers(They are issued for the verizon P605, but that says that these are the right generation they are not device specific): http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW
And reboot windows. Make sure no antivirus is running whilst flashing.
Boot your tab into stock recovery (power+volume up) and make a data/factory reset there.
Let the tab boot up the old Android 4.3 until it prompts you for input.
Switch it completely off.
Hard boot into Odin mode pressing power+volume down, choose download mode. No other way! No soft boot into it!
Open odin 3.09 as admin
Connect tab and wait until you get a blue sign in Odin and drivers have been installed completely.
Add the firmware file to AP / PDA wait until odin is ready (no spinning circle).
Make sure re-partition is not ticked
Click the start button, sit back and wait a few minutes
After the FW has been flashed the tab reboots into stock recovery first (probably to update the BL) and then into Android 4.4, let it connected until Android is up and running.
If it is not working try another PC .Alternatively try the one from Spain it is also an XX firmware as your 4.3 and has open CSC (OXA) as well.
Make sure you are following these steps closely and chronologically!

Vaira said:
@ The Dork Knight Rises: Nah...to flash a supported kernel first..makes absolutely no sense in odin mode no kernel is running. The update needs to flash a new bootloader in order to be able to boot 4.4 and that can cause trouble.
When having Samsung kies installed, de-install it and reboot windows
Install these USB drivers(They are issued for the verizon P605, but that says that these are the right generation they are not device specific): http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW
And reboot windows. Make sure no antivirus is running whilst flashing.
Boot your tab into stock recovery (power+volume up) and make a data/factory reset there.
Let the tab boot up the old Android 4.3 until it prompts you for input.
Switch it completely off.
Hard boot into Odin mode pressing power+volume down, choose download mode. No other way! No soft boot into it!
Open odin 3.09 as admin
Connect tab and wait until you get a blue sign in Odin and drivers have been installed completely.
Add the firmware file to AP / PDA wait until odin is ready (no spinning circle).
Make sure re-partition is not ticked
Click the start button, sit back and wait a few minutes
After the FW has been flashed the tab reboots into stock recovery first (probably to update the BL) and then into Android 4.4, let it connected until Android is up and running.
If it is not working try another PC .Alternatively try the one from Spain it is also an XX firmware as your 4.3 and has open CSC (OXA) as well.
Make sure you are following these steps closely and chronologically!
Click to expand...
Click to collapse
Thanks for the instructions ) I'll try to do this before classes start )
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
Thanks for the instructions ) I'll try to do this before classes start )
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Be aware that this process wipes all your installed apps and personal data. Also make sure that you are using the original USB cable that came with your device and make sure the device is fully charged.
Start with those steps when your tab has been switched off. With hard boot I mean to boot using key combination, no boot using reboot menu. Be sure you are in download mode where the green android / Knox flag is shown before you connect the tab with your PC.
It worked for me exactly this way. Although I have the P605 (no verizon edition). The provided Samsung drivers should be the right for you as well, good luck.