I made the mistake of rooting my phone a quick way using the kingroot app along with superuser. I wasnt aware that restarting the phone would frp lock it. I restarted the phone yesterday and next thing you know im stuck on a screen with a big yellow triangle and black exclamation point in the middle that has text above it that reads: "Custom Binary Locked. FRP Locked"
I quickly found out it was due to using the kingroot app. So every time i tried to power on the phone, the same message came up and i wasnt able to do anything. I came upon the method of using Odin 3.10.7 to flash the stock firmware back onto the phone and hard resetting it; which i have tried and failed.
First i downloaded Odin and the firmware I needed from sammobile.com and extracted them both and proceeded but i keep getting this:
<ID:0/006>Added!!
<OSM>Enter CS for MD5..
<OSM>Binary Check MD5..Do not unplug the cable
<OSM>Please wait..
<OSM>Checking MD5 finished successfully...
<OSM>Leave CS
<ID:0/006>Odin engine v(ID:3.1100)..
<ID:0/006>File Analysis
<ID:0/006>Setup Connection..
<ID:0/006>Initialization
<ID:0/006>Get PIT for mapping..
<ID:0/006>Firmware update start..
<ID:0/006>SingleDownload.
<ID:0/006>aboot.mbn
<ID:0/006>NANDWrite Start!!
<ID:0/006>sbl1.mbn
<ID:0/006>rpm.mbn
<ID:0/006>tz.mbn
<ID:0/006>hyp.mbNON-HLOS.bin
<ID:0/006>sec.dat
<ID:0/006>boot.img
<ID:0/006>recovery.img
<ID:0/006>system.img.ext4
<ID:0/006>FAIL! (Ext4)
<ID:0/006>
<ID:0/006>Complete(Write) operation failed.
<OSM>All threads completed. (succeed 0 / failed 1)
The screen in my phone had read:
ODIN MODE
PRODUCT NAME: SM-G530T
CURRENT BINARY: CUSTOM (Which Now reads Smasung Official after many attempts)
SYSTEM STATUS: CUSTOM OS (Which now read official)
FRP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWERV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
AFTER THE FAILED DOWNLOADS IT READS UNDER:
VOLUME SIZE IS TOO BIG 4362240 < 4546560
ODIN: Invalid id ext4 image
Below it reads Downloading....Don Not Turn Off Target
I have tried Odin several times and gotten the same messages. I was thinking maybe the file was too big? because it says volume size too big. There is no other place other than sammobile though to download my firmware. Although now, it shows that the system is somehow partially flashed on my phone because it reads samsung official on the top of the screnn when put in download mode; but now also when i try to power the phone on instead of the custom binary message it reads: An error has occured while updating the device software. Use the emergency recovery function in the smart switch PC software.
I have downloaded Kies 3 and smart switch all of which read that my device is unsupported and when i try the device initialization function it ssays my s / n is incorrect. The S/ N is the serial number right?
Pleasehelp. Is my phone recoverable?
I repeatedly get the volume size is too big message.
Related
Hey Guys I have a problem with my samsung galaxy s4 I9505. Everytime i lock my phone or it goes on standby and when i open it agian . I get the out of service problem . The only thing that i can fix that problem is that i have reboot the phone . I have installed like 10 different roms i get the same problem everytime
Odin mode
Product name GT-I9505
Current Binary : Custom
System Status : Custom
Knox KERNEl LOCK : 0x0
KNOX Warranty VOID :0x1
CSB-CONFIG-LSB :0x30
WRITE PROTECTION : ENABLE
nevruz said:
Hey Guys I have a problem with my samsung galaxy s4 I9505. Everytime i lock my phone or it goes on standby and when i open it agian . I get the out of service problem . The only thing that i can fix that problem is that i have reboot the phone . I have installed like 10 different roms i get the same problem everytime
Odin mode
Product name GT-I9505
Current Binary : Custom
System Status : Custom
Knox KERNEl LOCK : 0x0
KNOX Warranty VOID :0x1
CSB-CONFIG-LSB :0x30
WRITE PROTECTION : ENABLE
Click to expand...
Click to collapse
You need to flash a new modem in order to fix any drop issue. and please use the search button next time. Download/Unzip this file http://www.mediafire.com/download/zriv6i5c01lqns6/GSM_Modem_XXUEMKF_and_LTE_Modem_XXUMKF.rarand flash the file with odin by selecting phone.
Thanks mate i hope it works. For now there is no problems
nevruz said:
Thanks mate i hope it works. For now there is no problems
Click to expand...
Click to collapse
I'm having the same problem, but whenever I try to flash a modem, in Odin it says "FAIL!" in a big red box and the message says:
<ID:0/007> NAND Write Start!!
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it'self, it also says "SECURE CHECK FAIL: mdm"
Am I using the wrong modem? I've tried several It's a T-Mobile (M919) phone.
I have flashed modems no issue, maybe try another one and see how you go
Sent from my Gt-i9505
Working on this at 3am was a bad idea. Being tired and becoming impatient was not a good combination. I was running version 4.4.2 for Samsung Note 3. Upon trying to downgrade the firmware to 4.3 using the official .md5 from sammobile, it went through almost the entire process, failed, and I received an error code in Odin v3.09 under Message:
NAND WRITE START!!
FAIL! (Auth)
Phone was stuck in download mode with almost the full loading bar. After about 20 minutes of waiting and becoming impatient, I pulled the battery. Upon bootup, I have become stuck in Odin Mode. When booting up, I get this, minus quotations:
"ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
System Status: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WIRE PROTECTION: ENABLE
UDC START
Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I have tried recovering in Kies, but it does not recognize it. I can not boot into recovery mode, but I can still boot into download mode (thankfully). I have retried using the official firmware again as well as a Poland 4.4 release (as recommended on an article in this forum) After a google search, I came across an article on droidviews on "How to Unbrick AT&T Galaxy Note 3 SM-N900A"
I attempted to follow their tutorial. In odin, it seems to go well all the way to the very end. I tried initially without the bootloader, then a second time with. I keep getting the same error message (there are previous lines stating what it has done, I can post if needed):
NAND WRITE START!!
FAIL! (Auth)
The phone hangs up again and I have to do a battery pull.
Additional notes, possibly not helpful: I did do a factory reset before attempting this. Attempted to use Odin 3.07. After searching these forums, I have tried CF-Autoroot, using CWM recovery.tar, All through out this, I have tried using different cables other than factory, tried it on 3 total different computers (home desktop, laptop, and now work computer), different usb ports, entirely uninstalling and reinstalling drivers, and verified that Kies was not running in the background (terminated through task manager). Found an article in this forum to do just a re-partition in Odin using a PIT file. I used the one I got from droidview mentioned above. It says successful in Odin, then the phone starts to power-cycle at the Samsung splash screen. I can still boot into download mode, but I can not boot into the recovery mode (power cycles again). After the power cycling, I attempted to reflash the AP, and after it goes through almost the entire process, it gets the error "FAIL! (Auth)" and phone hangs up again. After reboot, I get the error on the phone again, "Firmware upgrade encountered an issue..."
Let me know if there is any other information you need me to provide. I am willing to try whatever I need to do to get it fixed if anyone has any ideas. Very desperate. Any help is greatly appreciated!
- Casey
re: Odin flash Firmware
bishouji said:
Working on this at 3am was a bad idea. Being tired and becoming impatient was not a good combination. I was running version 4.4.2 for Samsung Note 3. Upon trying to downgrade the firmware to 4.3 using the official .md5 from sammobile, it went through almost the entire process, failed, and I received an error code in Odin v3.09 under Message:
NAND WRITE START!!
FAIL! (Auth)
Phone was stuck in download mode with almost the full loading bar. After about 20 minutes of waiting and becoming impatient, I pulled the battery. Upon bootup, I have become stuck in Odin Mode. When booting up, I get this, minus quotations:
"ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
System Status: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WIRE PROTECTION: ENABLE
UDC START
Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I have tried recovering in Kies, but it does not recognize it. I can not boot into recovery mode, but I can still boot into download mode (thankfully). I have retried using the official firmware again as well as a Poland 4.4 release (as recommended on an article in this forum) After a google search, I came across an article on droidviews on "How to Unbrick AT&T Galaxy Note 3 SM-N900A"
I attempted to follow their tutorial. In odin, it seems to go well all the way to the very end. I tried initially without the bootloader, then a second time with. I keep getting the same error message (there are previous lines stating what it has done, I can post if needed):
NAND WRITE START!!
FAIL! (Auth)
The phone hangs up again and I have to do a battery pull.
Additional notes, possibly not helpful: I did do a factory reset before attempting this. Attempted to use Odin 3.07. After searching these forums, I have tried CF-Autoroot, using CWM recovery.tar, All through out this, I have tried using different cables other than factory, tried it on 3 total different computers (home desktop, laptop, and now work computer), different usb ports, entirely uninstalling and reinstalling drivers, and verified that Kies was not running in the background (terminated through task manager). Found an article in this forum to do just a re-partition in Odin using a PIT file. I used the one I got from droidview mentioned above. It says successful in Odin, then the phone starts to power-cycle at the Samsung splash screen. I can still boot into download mode, but I can not boot into the recovery mode (power cycles again). After the power cycling, I attempted to reflash the AP, and after it goes through almost the entire process, it gets the error "FAIL! (Auth)" and phone hangs up again. After reboot, I get the error on the phone again, "Firmware upgrade encountered an issue..."
Let me know if there is any other information you need me to provide. I am willing to try whatever I need to do to get it fixed if anyone has any ideas. Very desperate. Any help is greatly appreciated!
- Casey
Click to expand...
Click to collapse
Get the official NB4 Samsung 4.4.2 note 3 firmware for your phone's
model number from http://SamMobile.com and Odin flash it.
You cannot downgrade to 4.3 firmware.
Good luck!
Misterjunky said:
Get the official NB4 Samsung 4.4.2 note 3 firmware for your phone's
model number from sammobile and Odin flash it.
You cannot downgrade to 4.3 firmware.
Good luck!
Click to expand...
Click to collapse
Unfortunately, they have only released the 4.3 firmware through that website even though the 4.4.2 firmware was released sometime in March.
bishouji said:
Unfortunately, they have only released the 4.3 firmware through that website even though the 4.4.2 firmware was released sometime in March.
Click to expand...
Click to collapse
Have a look around HERE I bet you missed this and you can have it fixed in less than 10 minutes :good: - If not, feel free to tag me and I'll respond
radicalisto said:
Have a look around HERE I bet you missed this and you can have it fixed in less than 10 minutes :good: - If not, feel free to tag me and I'll respond
Click to expand...
Click to collapse
I noticed the dedicated forums, and unfortunately I couldn't find anything helpful minus the Root de la Vega thread (which is what I was originally going off of to root). My best guess was that I was going to have to wait until Samsung had the official release of 4.4.2 website. Who knows when that would be, so I just got back from my local AT&T Device Support Center and had it replaced. Thankfully the KNOX indicator wasn't tripped. Thank you guys for the help!
I have tried searching and do not see anyone with a similar issue. I was previously rooted with TowelRoot, but somehow my phone not only allowed the G900AUCU2ANG3 update today to download, but also allowed it to install. I know I should have removed TR before continuing, but stupid stuff like that happens when you see the update waiting when you first wake up and don't have contacts in or glasses on...
I can fully restore my phone to normal use, other than wifi. For whatever reason, the failed update shows to have changed the baseband, but I have no ability to connect to a wifi network, and despite about 15 factory resets since this morning, my device status still shows "Custom." Here is exactly what I see when I go into Download Mode (or as close as I can replicate it):
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
At this point, I can't find anyone with an NG3 stock firmware to use with Odin, and Odin keeps failing because the old firmwares won't pass the authorization stage. I attached the Odin screenshot to this post in case someone has other ideas. I can actually use my phone (not bricked), but wifi will not connect even though it can see various open and secure networks. I get an error stating "Failed to Obtain IP" when trying to connect to networks with "Very Strong" signal strength (I can see the AP from my desk).
Thus, I really need to be able to do 1 of 2 things:
1) Restore it to stock myself so I can have wifi, or
2) Be able to get it to show "System Status: Official" so that the local AT&T Device Service Center I drive by twice a week taking my kid to hockey practice will plug it in and update it and restore it. They managed to save my wife's Note 3 from a fairly bad soft brick / boot loop issue, but I also know that the "Custom" thing will pretty much guarantee they don't work on it.
Thanks in advance.
..
fffft said:
Writing a full stock firmware image, followed by a factory data reset will remove the custom status. So that would satisfy No. 2.
As to your first wish, I find it hard to believe that you couldn't find an ATT firmware image anywhere. There are dozens of firmware sites and I can only assume that you just did a short or cursory search. If you spend a few minutes with Google you can surely locate any ATT firmware version that has been release longer than one day.
Either way, use Odin to write a firmware image as the fastest way to resolve the situation. If you have difficulties, try this guide
If the problem persists, then you need to provide us with more details. Notably, the verbatim Odin error log, along with the exact file name you are trying to write and a detailed, step by step description of how you are using Odin.
.
.
Click to expand...
Click to collapse
I definitely have searched high and low for a stock version (both before the original post and just now) that will work with the failed update G900AUCU2ANG3. No one has a stock firmware I can find, and I cannot find any method by which to downgrade to an older version that I can find, such as G900AUCU1ANCE.
Here is what my phone says in Settings --> About device:
Baseband Version:
G900AUCU2ANG3
Build Version:
KOT49H.G900AUCU2AND3
File name I'm trying (but know won't work...not the newest baseband): G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar
Odin Error Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
..
fffft said:
The additional information definitely helps. But it's still a drop in the bucket. You didn't give us a detailed, step by step description of how you are using Odin e.g. what version of Odin you are using , which line you entered the firmware file line on (e.g. AP, PDA, etc) and so forth. And most importantly, did you try the procedure that I linked to in my last post?
We can't see your phone and these details are important as any one of them could cause failure. So we need to check off each item that you are doing.
Nominally the Odin error you posted says that your bootloader refused the firmware version you tried to write. More likely it is a timing error from a marginal USB cable or port. Odin is well known as tempermental with respect to USB timing. Try a different USB cable (yes, really. and yes, it is important. don't skip this step) and different USB port.
Most critically, ensure that you are entering download mode by removing the phone battery, then replacing it and using the volume down + home +power key sequence. And also important, if the first Odin write fails, do not close the Odin window. Instead remove the phone battery again, go into download mode again and then hit write again in the open Odin window. Inevitably, the second attempt will then succeed.
Try the very good procedure that is listed here <---- click on the link
Odin can be frustrating, but with a modicum of patience and attention to detail you will succeed. Good luck
.
Click to expand...
Click to collapse
I ended up going to the local AT&T Device Support Center (luckily it's about 2 miles from the ice rink at which my son practices) and they flashed it back to stock with no problems. She said I was one of 4 people that day who had issues with that particular update, and since my Knox Warranty showed 0x0, she thankfully ignored the "Custom" on device status. All is well and I have a clean backup in Kies if needed in the future and TowelRoot back on the device to kill some bloat. Thanks!
Can I get a flashable G900AUCU2ANG3? I am selling the phone and they want it stock and updated. I can't flash it back to stock. I didn't update it but it gives me the same Odin error as though I was trying to downgrade. Used to be able to downgrade it and do whatever I wanted when I was tinkering with getting SuperSU to stick after update. I've made no major changes. Did something come down from Samsung that locks Odin? I froze Knox and thought that might have something to do with it so I thawed it and factory reset after unrooting. No good.
Long story short I'd like an Odin flashable latest firmware to see if it will take. Sorry I don't have more info right now but the buyer has the phone right now.
I have a new Note 4 for T-Mobile in the US (SM-N910T3). I rooted the phone, installed TWRP, installed some apps...things I normally go through when rooting a phone. Everything seemed to be fine. Now, however, the phone will not boot up. It stalls at the screen with the message at the top that says:
Custom binary blocked by FRP
SECURE FAIL: KERNEL
If I try to boot into recovery, similar message:
Custom binary blocked by FRP
SECURE FAIL: RECOVERY
I can boot into download mode and this is displayed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I've tried using ODIN to try flashing the stock ROM, CF Auto-Root, etc. however, it always fails. For example.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmofrp-smn910t3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I'm at wits end now. I want to get back to the stock ROM and try rooting again (this time noting the warning about having Activation Lock unchecked). Am I doing something wrong, do I need to flash something else to the phone with ODIN...what can I do to get back to a working phone?
Thanks in advance for your help in this...super appreciated!
That's google's factory reset protection. You had google account set and a screenlock applied before the procedure?
Sent from my SM-N910C using Tapatalk
aleksandar.1 said:
That's google's factory reset protection. You had google account set and a screenlock applied before the procedure?
Sent from my SM-N910C using Tapatalk
Click to expand...
Click to collapse
I had just added a google account to download some apps from the Play store. The screen lock, yes, just the basic swipe screen that I think is set as a default.
Now I just get a display of the text I included at beginning of this thread and a yellow triangle. Can't get past that. And when using ODIN to try as I've read/seen elsewhere, the process always fails. Can't seem to find how to get past that. Really need some insight.
Thanks!
HehZeus said:
I had just added a google account to download some apps from the Play store. The screen lock, yes, just the basic swipe screen that I think is set as a default.
Now I just get a display of the text I included at beginning of this thread and a yellow triangle. Can't get past that. And when using ODIN to try as I've read/seen elsewhere, the process always fails. Can't seem to find how to get past that. Really need some insight.
Thanks!
Click to expand...
Click to collapse
I called Samsung Tech Support, they sent me to Best Buy where Samsung has a "store within a store" to get a software reflash. Three minutes later, all good, back to stock phone...ready to give rooting another try...this time with FRP turned off in Security!
Bought a S5 (SM-G900AZ) "unlocked" cricket phone intending to use it on AT&T, it was running 5.0 and I got root then started disabling some of the bloat via 'no bloat' app, all was well, then I restarted, after the splash it displayed the setting up android window, then went to setting up apps, then it got stuck in a loop where it rebooted repeatedly at this step, never actually starting. I let it retry for a while, dropped the battery and tried again to no avail. Next I put it into the menu so i could do a wipe and clear the cache which I did then restarted, same result. figured I had boned it up and would need to reflash the factory distro to reinstate some of the bloat I disabled. I downloaded the correct firmware of 5.0 from Samsung opened Odin and selected the AP check box, located the Samsung file, it checked the MD5 then I hit start, FAILED.
From ODIN
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> 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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Phone
ODIN MODE
Product Name: SM-G900AZ
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
AP Swrev: S1, T2, R1, A3, P1
Secure Download : Enable UDC Start
SW Rev Check Fail : [aboot]Fused3 >Binary 2
What does the Fused and Binary numbers mean?
Do I need to attack this from another angle?
Any ideas on how to get the factory software back on this thing?
Thank you for reading and any help you can provide.
bump
This is also my problem in my SM-G900I, i cant update to official marshmallow firmware because it always does the same as yours. Even in lollipop firmware still the same result, always failed. I already tried everything, factory reset, all odin version etc but still same result.
In odin 3.10.7 im stuck in this for almost 1 hour (see attached). I tried 5 times and still the same.
hope someone can help us.....:crying::crying::crying::crying:
The assasin said:
hope someone can help us.....:crying
Click to expand...
Click to collapse
He has a name, and called official Samsung service center.
SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Update kies, and usb divers [Tools : Reistall Device Driver]
With your phone booted in to Download Recovery [push Power + Home + Vol Down] then [Vol Up to confirm] then connect to the USB.
Now the USB cable should keep it powered up, you can remove the battery and read the Mod # and SN #
In Kies go to [Tools : Firmware Upgrade and Initialization]
Put in your Mod # [ok]
Put in your SN # [ok]
Click ok on all the confimation boxes.
It will download the correct software from Samsung then push it to the phone and restart, pay attention as it asks you to remove and replace the cable after restart, incidently if you removed the battery eariler to read the Mod # / SN # then when it resets it wont restart, if you happen to walk away.
Put in the battery and power it up, mine rebooted a couple times then booted normally starting back at the Welcome screen, I was able to re root and make some of the changes I was trying to make and now have a working phone.
I hope this helps others.
BrweckedS5 said:
SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Click to expand...
Click to collapse
The first software that every fresh S5 owner gets related with, this is KIES..
Every one assumes that you failed in all known ways and then you started this topic.