Database Develop

[TUTORIAL][ROM] How to fix your phone and apply the update

I have talked to many people that had issues applying the OTA update. Here are the steps to get your phone back to stock and apply the update.
As always, I'm not responsible for anything. yadda yadda.
First, download http://www.multiupload.com/NMPX3KMWRS
This contains Odin, the Samsung Drivers, stock odin rom, updated odin rom, pit file.
If you don't want to lose your settings, etc. you can skip to the second part. If your phone still doesn't work than start from the top.
-PART 1-
Step 1.) Make sure you have the appropriate drivers installed for your phone. If you are on 64bit then choose 64, if you are on 32 choose 32. You may already have the drivers installed and it will tell you after you try to install them.
Step 2.) Power your phone off
Step 3.) Open Odin.exe and plug a usb cable to your computer that will connect to your phone (do not plug it in to the phone yet, just the computer)
Step 4.) Hold down both volume buttons at the same time and while holding them down plug the usb into your phone. You should see a COM message show up in Odin.
Step 5.) To ensure your phone is back to stock, in odin you will want to check the repartition button. ONLY CHECK IT WHEN YOU ARE FLASHING BACK TO STOCK. Leave the other check boxes the way they are.
Step 6.) Click the PIT button and select the 512.pit file
Step 7.) Click the PDA button and select Original.tar and then click Start
It should go through a bunch of steps and then your phone will reboot. Below are the steps to update it to the latest release.
Close Odin and power your phone off.
-PART 2-
Step 1.) Open Odin.exe and plug a usb cable to your computer that will connect to your phone (do not plug it in to the phone yet, just the computer)
Step 2.) Hold down both volume buttons at the same time and while holding them down plug the usb into your phone. You should see a COM message show up in Odin.
Step 3.) Leave all check boxes the way they are. Do NOT check the repartition box.
Step 4.) Click the PIT button and select the 512.pit file
Step 5.) Click the PDA button and select T959UVJI6.tar and then click Start
It will go through a bunch of steps and then your phone will reboot. Congrats, you are on the latest update!

This should be stickied in general so the whole first page isn't taken up with topics about being soft bricked.

When you say updated odin rom, is this the official updated ota that its rolling out now?
Sent from my SGH-T959 using Tapatalk

Beautiful. Thank you for the post. Will do this later tonight and update the sticky in general. Thank you!
I assume with this method you lose your apps and settings? That's not the case with the ota... I could be wrong.

will this work on a hardware lock phone?

s15274n said:
Beautiful. Thank you for the post. Will do this later tonight and update the sticky in general. Thank you!
I assume with this method you lose your apps and settings? That's not the case with the ota... I could be wrong.
Click to expand...
Click to collapse
You are correct - the fix with the repartition will wipe all your data, but it actually should not be necessary to flash back to the stock ROM. We resolved this problem on the main thread for this issue earlier today by just using ODIN 1.3 to flash to the JI6 ROM directly. This approach saves all user data and restores the phone directly to the new version without losing any user settings or data.
Edit:
The older thread is here: http://forum.xda-developers.com/showthread.php?t=802828
The solution we found is pretty much identical to the final 5 steps above in the OP post - many of us have executed just those steps to restore without reverting to stock and without losing user data.
Edit 2 - Thanks youneek for updating the instructions with this option

Can I flash over J14 or do I need to revert to stock?

Thank you for this thread. I was able to revert back to stock and flash JI6. I know that it wasn't necessary to go back down to stock but I just wanted to start everything over. It went very smoothly, I actually did it while I was sitting in my night's class lol.

How long?
How long should it take for the first Odin cycle - returning to stock - to take?
Odin 3.1 has been running for at least 15 minutes. ID: COM shows as 0:[COM6]. PIT and PDA are appropriate. The Odin message area reads:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!

Everything for me took less than 5 minutes.
Sent from my SGH-T959 using XDA App

RebDovid said:
How long should it take for the first Odin cycle - returning to stock - to take?
Odin 3.1 has been running for at least 15 minutes. ID: COM shows as 0:[COM6]. PIT and PDA are appropriate. The Odin message area reads:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
Click to expand...
Click to collapse
Entire Odin took me less than 5 minutes last time I did it.
This happened to me the first time I odin'd my phone .... I restarted the phoen and got the Phone--PC error. Just get back to download mode & restart the flash, should work next time through.
Considering what Odin does, it is a very buggy program and is prone to crashes.

Thank you
Easy, breezy, beautiful !!!
The update doesn't wipe the data if you had a stock ROM before that. All my apps and settings are intact after the installation just perfect...
Just have a question: is it ok to root the phone with one-click-root?
Thanks again...

kangxi said:
Everything for me took less than 5 minutes.
Click to expand...
Click to collapse
So, if I need to try again, what do I do (besides not turning off my Vibrant)?

I've done the update but now when I try to root the phone again, I get a 'E:cannot open /sdcard update.zip (No such file or directory)' now when I choose re-install packages. I've tried the one click root apk method and the update.zip placed in the directory manually. Nada. Whats the deal?
My directories are labeled D and F when mounted on my pc if it means it's looking for it in E now...

RebDovid said:
So, if I need to try again, what do I do (besides not turning off my Vibrant)?
Click to expand...
Click to collapse
Just put your phone back into download mode and try again.
Sent from my SGH-T959 using XDA App

one-click-root
Nokternal said:
I've done the update but now when I try to root the phone again, I get a 'E:cannot open /sdcard update.zip (No such file or directory)' now when I choose re-install packages. I've tried the one click root apk method and the update.zip placed in the directory manually. Nada. Whats the deal?
My directories are labeled D and F when mounted on my pc if it means it's looking for it in E now...
Click to expand...
Click to collapse
I just rooted with one-click-root.. no problems here.. disregard the question from my previous post.
I just enabled usb debugging, connected the phone, started one-click-root and the phone rebooted... then "reinstall packages" and the phone came back rooted...
Can't access LBSTestMode menu from *#*#1472365#*#* anymore...any idea?

i just tried this and odin is stuck and has not done anything the message area say this please help
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs

Hi all,
I've read almost every post about the update, but still have some questions so here goes.
I'm on complete stock, untouched. didn't even install clockwirkmod recovery. The ONLY thing I did was root.
I'm out of the US so obviously no OTA for me.
I was wandering if I need to unroot inorder to use the Odin method and wether it is possible to reroot after. Does the update break root, does it have any this to do with it?
Also, is flashing clockwork rec risking anything? Afterall I understand I have to nandroid backup so I need it right?
Thx
BTW, this is my first post (noob) so will be happy to get a bit more than the common nutshell answer since I'm new
Sent from my SGH-T959 using XDA App

i followed these steps but i can't make my phone go into download menu. damn it! the ota taking too long to arrive.

OMG!
This fix the phone!
My phone was bricked by OTA and this method DOES recover my phone back to normal. I could even recover my important DATA!
PS. T-mobile can't recover my data.
Thank you superman in XDA.

Sprint SGT - E:Can't mount /dev/block/mmcblk0p1

Hi there Galaxy Tab community!
I'm having trouble fixing a Sprint Galaxy Tab (SPH-P100, CDMA).
I have tried a lot of different solutions and none of them are working for me.
Maybe someone can point out what the issue with my SGT is.
Current status: will get stuck at the "glowing" Samsung Logo (have let it sit for 15-20 minutes after reflashes but still stays there)
I don't really know how to explain this issue so I'm hoping one of you kind members can explain this to me. In Android system recovery <3e> mode before I did any flashing I get this error notice:
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
Is E: the SD card?
I do not have an SD card put in. And when I do, the above error message still appears. There is no SD card mounting error notice. And attempting to do an SD card update.zip does attempt successfully.
Now after trying to ODIN flash back to stock firmware (EA24, DJ30, stock with no modem) they all flash successfully, but all of them still get stuck at glowing samsung logo. And I still get the above mounting error message in recovery.
I did not tick "re-partition" yet, would this make a difference? (I tried searching for what it does but couldn't find any explanation)
Would flashing with Heimdall be any different than ODIN?
And the other solution I read was to reformat the internal SD to rfs format using roto JME (but I think that's only for GSM support?)
ANy help/suggestions would be appreciated!
UPDATE!!!: FIXED!!
Followed this step by step carefully and exactly from step 1 - 7: posted by emieczko (THANK YOU!!!!)
http://forum.xda-developers.com/showpost.php?p=13113921&postcount=21
so now I have to figure out if I still get the above error about E:.. but im scared if its really fixed for good. I will keep this updated! I love this forum!
UPDATE 2: shoot.. spoke too soon haha, tried to do a reflash of EA24 through heimdall and now in original situation. Only attempted another flash because each time i shutdown and restarted it would get stuck, until i would go into recovery and do a factory wipe/ clear cache, which would allow it to then boot to android.
UPDATE3: humm interesting, the OP http://forum.xda-developers.com/showpost.php?p=11650984&postcount=1 actually worked and booted right after a successful flash of the no_modem stock firmware using ODIN and the pit file supplied. and the crazy part is, it still had my gmail account info saved even after i had 'factory reset' a few times when it wouldnt boot up correctly.
UPDATE 4: Okay managed to update from stock no modem (tab_sprint_noModem_20101226) using odin 1.3, then ODIN the EA24 (Sprint Galaxy Tab EA24 Flasher) successfully with first boot attempt! Then since this was more of an official flash, EB25 was downloaded and installed with first boot success! Then the next update before Gingerbread, and then gingerbread OTA was installed successfully with first boot success!!! So now under gingerbread rom everything seems to be working smoothly. no problems with the market, wifi issues seem to be fixed.. only last real thing to make it an officially fixed tab is rebooting and seeing if it boots okay and booting into recovery and seeing if the E: errors still occur.. both which I don't want to face atm haha.\
UPDATE 5: So I was able to successfully reboot 3 times in a row. The method I used was the tablet plugged in with charger the entire time. I noticed upon removal of charger, apps would force close within minutes if i attempt to open even more apps system reboot and hang would occur. The only solution to get it up and working again is to plug the charger back in, then factory reset/ wipe cache and reboot. (FYI: first boot after a factory reset, the tab should vibrate on the 3rd-8th "glow" cycle of the samsung logo. if you see the logo loop.. then yea its boot loop haha). Attemping to boot the tab up without charger plugged in, causes a boot logo hang.. I'm starting to suspect defective tablet :-\
UPDATE 6: Looks like this tablet functions 100% normal when plugged in via USB to PC or Charger. Booting into recovery does not show any failed mounts (reboot into recovery 3 tmies) UNTIL i unplug it and try to reboot into recovery again. ACCIDENTALLY flashed the DK28 (epic 4g) modem! ahhhh after reading all the warnings .. fortunately I was able to ODIN the pit and EA24 rom successfully and the GPS still works. AT the moment I am letting the tablet incrementally update itself to gingerbread (while it is plugged in via usb to pc). And done.. now to do more unorthodox tests to see why its failing with no usb plugged
UPDATE 7: I think this is a hardware issue.. seems to only work normal when plugged in. doh.

So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?

pvtjoker42 said:
So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?
Click to expand...
Click to collapse
Correct! This is the ODIN log after a successful flash of the SPH-P100.EA24.SECURE.REV07-FULL_CL871413
<ID:0/003> Added!!
<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> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> recovery.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Does anybody the average time ti takes to stay on that glowing Samsung Logo after a factory reset/ flash?
edit: nevermind, its less than 10 glowing logo cycles.

Here is the best way to sovle the problem.
if your TAB stuck in the logo ,and recovery got the tips, the IC sandisk "sdin5d2-2g" on the mainboard is broblem .I let some body who is good at repairing mobile phone to use tools to take the IC out ,and throw it into bin. I go back home unpack the zImage kernel ,modify the file in it ,such as fota.rc,recovery.fstab , (in Ubuntu , grep mmblk * */* */*/* ) ,let the mmcblk0p1 for sdcard ,mmcblk0p3 for cache mmcblk0p4 for data , and repack the kernel . Then I repartition my kingston 8g C6 TF card to four primary partition,5.4 for the 1st ,180m for the 2nd ,190m for the 3th ,2G for the 4th. At last I use heimdall to reflash zhe new zImage into kernel and recovery .When the tab reboot ,let it into recovery and wipe the data and cache and reboot . After 10mins ,you will get the first setting for the tab.
here is my new zImage: /115。com/file/dnm9n22m#
the links: /www。diypda。com/forum.php?mod=viewthread&tid=336743
I am a new man in XDA, I can't post the outside link ,so please use " . " to replace " 。 " and add "http:/ " the links ,sorry !
My email is [email protected], you are welcome !

[Q] S3 wont boot - any last hope?

Hey y'all,
So I woke up this morning to find my quite new (~11 months) i9305 to be bootlooping.
Getting into download mode works, recovery however does not, since it loops the very first Samsung screen.
Flashing a new rom using Odin (3.04 / 07 / 09) gives me this:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
Click to expand...
Click to collapse
Even re-partitioning fails:
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
Click to expand...
Click to collapse
To sum it up, it won't flash anything to my mobile, my mobile doesnt output anything in download mode and nothing else works.
Is there anything I forgot trying or is this phone a case for the trash can now?
I'm guessing the nand or worse might be dead.

nachu3 said:
Hey y'all,
So I woke up this morning to find my quite new (~11 months) i9305 to be bootlooping.
Getting into download mode works, recovery however does not, since it loops the very first Samsung screen.
Flashing a new rom using Odin (3.04 / 07 / 09) gives me this:
Even re-partitioning fails:
To sum it up, it won't flash anything to my mobile, my mobile doesnt output anything in download mode and nothing else works.
Is there anything I forgot trying or is this phone a case for the trash can now?
I'm guessing the nand or worse might be dead.
Click to expand...
Click to collapse
update odin to v3.09 latest..
before flashing with odin, you need to make sure that the box re-partition is unchecked or else this will mess up your device. only factory reset time and auto reboot should be checked. also usb debugging should be enabled in developer options in your phone.
trying with other usb ports of your pc might also work.

What are you trying to flash ? Are you knoxed? Aren't you perhaps trying to flash the old bootloader ?

MaHo_66 said:
before flashing with odin, you need to make sure that the box re-partition is unchecked or else this will mess up your device. only factory reset time and auto reboot should be checked. also usb debugging should be enabled in developer options in your phone.
Click to expand...
Click to collapse
Doesn't work and I can't enable usb debugging or even do a factory reset due to my inability to boot.
daedric said:
What are you trying to flash ? Are you knoxed? Aren't you perhaps trying to flash the old bootloader ?
Click to expand...
Click to collapse
I tried flashing multiple things so far, a 4.4 rom, and a 4.1 samsung stock rom with csc & modem.
It doesn't show any knox flag in download mode to me (just Custom Binary Download Count, Current Binary and System Status), so I guess I'm not knoxed?

Doubt, you tried to repartition, did you have PIT file ?

daedric said:
Doubt, you tried to repartition, did you have PIT file ?
Click to expand...
Click to collapse
Of course I had the PIT file, how should I've got that log otherwise if I didn't?

nachu3 said:
Of course I had the PIT file, how should I've got that log otherwise if I didn't?
Click to expand...
Click to collapse
pit are just for re-partitioning the device(they have partition layout in it), you can use odin without pit, i use on my i9300, that looks like a dead nand to me,but for last hope, try without re partitoning(not using pit or not ticking re partition)

nachu3 said:
Doesn't work and I can't enable usb debugging or even do a factory reset due to my inability to boot.
I tried flashing multiple things so far, a 4.4 rom, and a 4.1 samsung stock rom with csc & modem.
It doesn't show any knox flag in download mode to me (just Custom Binary Download Count, Current Binary and System Status), so I guess I'm not knoxed?
Click to expand...
Click to collapse
Your problem might be elsewhere... You're probably Knoxed. Have you EVER flashed a stock 4.3 ? If so, you flashed the new bootloader (knox included) and you cannot flash roms which include the OLD bootloader.
Go to sammobile, download a 4.3 and retry. Not a 4.1, not a 4.4. A 4.3.

For this type of prob.. first use newest phils recovery.. on that format Every nand partitions.. I mean every.. then just flash latest odin firmware.. dont use pit option.. you may get hard brick... try this

[GT-I9295] Lollipop 5.0.1 unroot and/or downgrade to KitKat [GUIDE]

First of all we should thank Samsung for their gesture of generosity, by allowing us to safely downgrade Lollipop to KitKat. Maybe this is because Lillopop is probably the last version of Android our devices will get.
But anyway, let’s stick to the topic.
The following is a step-by-step guide to unroot Galaxy S4 Active International (I9295) with Lollipop and reclaim warranty and/or downgrade from Lollipop 5.0.1 (DOB4) to KitKat 4.4.2 (CNE5) without tripping Knox. At least these are the steps I performed and the firmwares I’ve used. Other might also work, but I haven’t tested.
The main goal in this guide is resetting the flash counters and reclaim warranty.
As we know, for the moment rooting Lollipop with this method involves flashing a custom recovery, which activates the flash counter and the System and Binary status is Custom. However in Download mode there is NO KNOX WARRANTY VOID STATUS! Again: Thank you Samsung!)
So, let’s get to work. The usual warning applied here: Do this at your own risk. I’m not responsible for any damage and/or loss of data or any other issues if something goes wrong during process. Fully charge the battery, backup your data and so on, you know the drill In short – I tell you EXACTLY what I did and, it worked for ME without issues! It might look a bit complicated, but it is really not. It is a workaround until we get an easier root, without the need of flashing custom recovery or Triangle Away get's support for this recovery and/or ROM.
1.*Download all necessary tools: Odin, the official KitKat firmware you are downgrading to, the official Lollipop firmware currently on your phone and ensure all Samsung drivers are up to date.
2.*Put your phone into Download mode. (Turn it on while holding the Volume Down key + Home keys). In fact holding the home button turns out to be optional
3.*Run Odin. Ensure “Auto Reboot” and “F. Reset Time” are the only boxes checked.
4.*Connect phone to the USB.
5.*Click AP and browse for the official Lollipop firmware. (This step is necessary if you have rooted you phone and have flashed a custom recovery. If you are just downgrading, I think you can safely skip it.)
6.*Click Start.
7.*Wait.
8.*When flashing finishes unplug your phone from USB and reset it to factory settings.
9.*Put your phone into Download mode again.
10.*Run Odin again. Same steps as above but now select the official KitKat firmware.
11.*Click Start.
12.*Wait againJ
13.*When flashing finishes, device might stuck in a Bootloop. Put it into recovery mode by turning it on while holding Volume Up key and reset it to factory default settings. If it is still stuck, put it into Download mode and then turn off the phone completely. For some reason just restarting the phone doesn't work sometimes.
14.*Start phone. If Wi-Fi doesn’t work perform a factory reset again. (Worst case scenario: you will need to flash the KitKat firmware again. Not a big deal But this is very unlikely anyway.)
15.*You should now have successfully restored KitKat firmware on your phone. Device status and Binary counter still will show Custom.
Now it is time to reset the flash counters.
16.*Root your phone with Towelroot. Towelroot won't trip Knox.
17.*Install Triangle Away.
18.*Start Triangle Away and choose Reset flash counter.
19.*When device reboot, reset the counters and then after several reboots by itself, a menu will ask you if you want to reboot phone normally or into download mode. Choose Download mode.
20.*When device reboots, Binary and System status and should now show Official and the Knox Warranty Void should be 0x0. (If you haven't previously tripped Knox, of course. It is not resetable.)
21.*Now you can choose if you want to finally downgrade and flash the official KitKat firmware or if you want to stick to Lollipop. In both cases you will have fully unrooted phone with an Official Device and Binary status..
Enjoy

i just wanted to know, if i could use this on the I9505?
how do you do it when your s4 has a 5.0.1 and triangle away doesn't work to Reset Flash / Binary Counter. the counter does not go down. i tried flashing with odin but always fails. but i can root the phone again and i works on a 5.0.1 rom. i just wanted to unroot it.
vskivanov said:
First of all we should thank Samsung for their gesture of generosity, by allowing us to safely downgrade Lollipop to KitKat. Maybe this is because Lillopop is probably the last version of Android our devices will get.
But anyway, let’s stick to the topic.
The following is a step-by-step guide to unroot Galaxy S4 Active International (I9295) with Lollipop and reclaim warranty and/or downgrade from Lollipop 5.0.1 (DOB4) to KitKat 4.4.2 (CNE5) without tripping Knox. At least these are the steps I performed and the firmwares I’ve used. Other might also work, but I haven’t tested.
The main goal in this guide is resetting the flash counters and reclaim warranty.
As we know, for the moment rooting Lollipop with this method involves flashing a custom recovery, which activates the flash counter and the System and Binary status is Custom. However in Download mode there is NO KNOX WARRANTY VOID STATUS! Again: Thank you Samsung!)
So, let’s get to work. The usual warning applied here: Do this at your own risk. I’m not responsible for any damage and/or loss of data or any other issues if something goes wrong during process. Fully charge the battery, backup your data and so on, you know the drill In short – I tell you EXACTLY what I did and, it worked for ME without issues! It might look a bit complicated, but it is really not. It is a workaround until we get an easier root, without the need of flashing custom recovery or Triangle Away get's support for this recovery and/or ROM.
1.*Download all necessary tools: Odin, the official KitKat firmware you are downgrading to, the official Lollipop firmware currently on your phone and ensure all Samsung drivers are up to date.
2.*Put your phone into Download mode. (Turn it on while holding the Volume Down key + Home keys). In fact holding the home button turns out to be optional
3.*Run Odin. Ensure “Auto Reboot” and “F. Reset Time” are the only boxes checked.
4.*Connect phone to the USB.
5.*Click AP and browse for the official Lollipop firmware. (This step is necessary if you have rooted you phone and have flashed a custom recovery. If you are just downgrading, I think you can safely skip it.)
6.*Click Start.
7.*Wait.
8.*When flashing finishes unplug your phone from USB and reset it to factory settings.
9.*Put your phone into Download mode again.
10.*Run Odin again. Same steps as above but now select the official KitKat firmware.
11.*Click Start.
12.*Wait againJ
13.*When flashing finishes, device might stuck in a Bootloop. Put it into recovery mode by turning it on while holding Volume Up key and reset it to factory default settings. If it is still stuck, put it into Download mode and then turn off the phone completely. For some reason just restarting the phone doesn't work sometimes.
14.*Start phone. If Wi-Fi doesn’t work perform a factory reset again. (Worst case scenario: you will need to flash the KitKat firmware again. Not a big deal But this is very unlikely anyway.)
15.*You should now have successfully restored KitKat firmware on your phone. Device status and Binary counter still will show Custom.
Now it is time to reset the flash counters.
16.*Root your phone with Towelroot. Towelroot won't trip Knox.
17.*Install Triangle Away.
18.*Start Triangle Away and choose Reset flash counter.
19.*When device reboot, reset the counters and then after several reboots by itself, a menu will ask you if you want to reboot phone normally or into download mode. Choose Download mode.
20.*When device reboots, Binary and System status and should now show Official and the Knox Warranty Void should be 0x0. (If you haven't previously tripped Knox, of course. It is not resetable.)
21.*Now you can choose if you want to finally downgrade and flash the official KitKat firmware or if you want to stick to Lollipop. In both cases you will have fully unrooted phone with an Official Device and Binary status..
Enjoy
Click to expand...
Click to collapse

Triangle Away does not support this ROM and Recovery.
You must downgrade to KitKat first and then reset the counters. The post above is a step-by-step guide how to do that. Haven't tryied it on I9505, so cannot say. I think it might work, but that's just a wild guess, so think twice before doing it!!!

Recovery error message!
Hey there,
After the downgrade procedure, the odin ended with the following log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9295XXUCNI1_I9295OXXCNI1_I9295XXUCNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0
So far so good.
The system rebooted but 15 minutes later still nothing... just the samsung logo blinking.
I did a reboot again but this time in recovery mode to perform a fully wipe and when i get inside my stock recovery i have only 4 options
Reboot system now
Apply update from adb
Wipe data/factory reset
Wipe cache partition
i dint find a option like "Install from external card" or something like that
below these options i found some errors
E:missing bitmap icon_att_fota_installing (code -1)
E:missing bitmap icon_att_fota_updating (code -1)
E:missing bitmap icon_att_fota_complete (code -1)
E:missing bitmap icon_att_fota_error (code -1)
E:missing bitmap icon_tmo_fota_complete (code -1)
E:missing bitmap icon_tmo_fota_error (code -1)
I did a fully wipe anyway. The system rebooted as expected and now is fully functional, however i would like to fix the stock recovery because I don't know the real implications of using this recovery.
What do you think the problem is and how can I fix it?
Thanks in advance for your help.

I'm not sure I understand your question.
If you successfully downgraded to KitKat and flashed stock rom, your should already have the stock recovery installed.

BIG UP!!
Thank you! I had some problem with the Odin v3.10.6 leaving me with a half brick, so tried with V3.10.5 and headbanging I got it to go!
Bootlooped for me, and after factory reset did the job!:good:
TOTAL BABE!

[Q] Dead...D.E.D...Dead...G900A is confused & andy is ded!

After spending hours of research on the web, with conflicting information on whether you can, or cannot downgrade from 5.0 to 4.4, I threw my hands in the air and said the hell with itt and tried it. Now I have an S5 stuck in bootload. Here are the deets:
-At&t S5 OTA 5.0 (yes, I know now that downgrading is impossible, thank you locked bootloader!)
-Used Odin 3.09 to flash 'G900A_ND3_Stock_Kernel. tar .md5 ' in the AP slot. (all seemed ok at this point.
-Odin read RES OK!
- Phone went to Samsung Screen (stayed there just long enough to get me a bit nervous)
-Then phone went to "Android system recovery <3e>" with the following:
Android system recovery <3e>
KOT49H.G900AUC1ANCE
Volume up/down to move highlight:
power button to select.
>reboot system now
>apply update from ADB
>apply update from exteral storage
>wipe data/factory reset
>wipe cache partition
>apple update from cache
#MANUAL MODE#
---Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
*My question is, what the hell do I do now? I am not exactly a noob to rooting, as I have rooted the last 3 at&t Samsungs I've owned, but this damn s5 is killing me. But any ideas would seriously be greatly appreciated! Thank you in advance!

trinity4200 said:
After spending hours of research on the web, with conflicting information on whether you can, or cannot downgrade from 5.0 to 4.4, I threw my hands in the air and said the hell with itt and tried it. Now I have an S5 stuck in bootload. Here are the deets:
-At&t S5 OTA 5.0 (yes, I know now that downgrading is impossible, thank you locked bootloader!)
-Used Odin 3.09 to flash 'G900A_ND3_Stock_Kernel. tar .md5 ' in the AP slot. (all seemed ok at this point.
-Odin read RES OK!
- Phone went to Samsung Screen (stayed there just long enough to get me a bit nervous)
-Then phone went to "Android system recovery <3e>" with the following:
Android system recovery <3e>
KOT49H.G900AUC1ANCE
Volume up/down to move highlight:
power button to select.
>reboot system now
>apply update from ADB
>apply update from exteral storage
>wipe data/factory reset
>wipe cache partition
>apple update from cache
#MANUAL MODE#
---Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
*My question is, what the hell do I do now? I am not exactly a noob to rooting, as I have rooted the last 3 at&t Samsungs I've owned, but this damn s5 is killing me. But any ideas would seriously be greatly appreciated! Thank you in advance!
Click to expand...
Click to collapse
Did you read my reply in the other thread that you posted your question in.
http://forum.xda-developers.com/showthread.php?t=3126711

dirtydodge said:
Did you read my reply in the other thread that you posted your question in.
http://forum.xda-developers.com/showthread.php?t=3126711
Click to expand...
Click to collapse
I just did, and unfortunately the links in Post #5 are no longer available, so i have been looking through XDA for any links to the stock OC4 kernel. I have a pit file for lollipop but that is it. Happen to know where I can come up with the other relevant files?

still ded
dirtydodge said:
Did you read my reply in the other thread that you posted your question in.
http://forum.xda-developers.com/showthread.php?t=3126711
Click to expand...
Click to collapse
So after some searching, I found " G900A_OA1_Stock_Kernel. tar .md5 " and flashed in Odin 3.09 using AP slot. PASS. however back to the same Android system recovery <3e> screen stated above. Do I need to flash the pit file too?

trinity4200 said:
So after some searching, I found " G900A_OA1_Stock_Kernel. tar .md5 " and flashed in Odin 3.09 using AP slot. PASS. however back to the same Android system recovery <3e> screen stated above. Do I need to flash the pit file too?
Click to expand...
Click to collapse
I'm not sure about the oc4 kernel or the pit file. Have you tried kies. If your already on 5.0 then kies can't do anymore damage ya know