Hi,
whenever i connect samsung galaxy S2 (GT-I9100) through kies it shows that a new firmware is available i.e PDA:KL1/ PHONE:KL1/ CSC:KL1 (INU)
but always after downloading firmware components i got a error that - FIRMWAREUPDATE HAS STOPPED WORKING.
Problem details are-
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: gt-i9100.exe
Problem Signature 02: 11.9.8.1
Problem Signature 03: 4e695566
Problem Signature 04: PresentationFramework
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4d9590eb
Problem Signature 07: 987
Problem Signature 08: 42
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Please help and I am using genuine windows7 (64bit).
Thanks a lot in advance.
since you are apparently unrooted and everything is stock, you could also contact samsung support about that issue.
an alternative that this site can offer you is to use odin for flashing, which is way more reliable than kies but needs a little bit of reading and getting used to, since not everything is automatic there.
Yeah call Samsung
Sent from my GT-I9100 using xda premium
Solution to Kies error CLR20r3
pulkit.delhi said:
Hi,
whenever i connect samsung galaxy S2 (GT-I9100) through kies it shows that a new firmware is available i.e PDA:KL1/ PHONE:KL1/ CSC:KL1 (INU)
but always after downloading firmware components i got a error that - FIRMWAREUPDATE HAS STOPPED WORKING.
Problem details are-
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: gt-i9100.exe
Problem Signature 02: 11.9.8.1
Problem Signature 03: 4e695566
Problem Signature 04: PresentationFramework
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4d9590eb
Problem Signature 07: 987
Problem Signature 08: 42
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Please help and I am using genuine windows7 (64bit).
Thanks a lot in advance.
Click to expand...
Click to collapse
"Dude, I was facing similar issues and after lot of head breaking I found the solution. Follow these steps and you should be able to get ICS.
1st - Ensure that you are using Genuine Windows on your PC/Laptop
2nd - Do not try upgrading using USB dongle (TATA Photon+), you need to use LAN
3rd - Install/connect phone to PC only after you have installed KIES.
4th - Remember, that after installing KIES, you restart your PC and restart after installing drivers for the device. Basically, do restart after every action before going for upgrade option.
All the best!!"
i appreciate you want to help already, after you are just new to the forum, but all 4 of your points, how to say it gently, do not apply here.
1. it is stated in the original post that the windows version is genuine, although i can not see how that has anything to do with it, since kies or samsung altogether has no access to registration information and has no interest in motivating people to buy windows legally, as the two companies are not affiliated. still, i don't want to condone piracy, i am just saying, it does not have anything to do with the issue.
2. when you say usb dongle, i assume you are talking about a wi-fi connection, as you then talk about lan. that has nothing to do with the update process, because the update will be performed through usb. of course for a successful download of the rom to flash, a stable internet connection is necessary, but these days, even ota rom downloads on 3g are mostly successful, you cannot generally say, that if your computer is connected through wi-fi, your upgrade will fail.
3. the error message posted above is caused by kies. obviously it is already installed and started at that point.
4. see 3. i assume there was already a successful connection in kies, or it wouldn't have gotten to that point.
still, i really appreciate that you are trying to help, but especially upgrading is always a sensitive topic, as it bares the risk of bricking. in that case you should only post helpful information that you are absolutely sure of.
in general, you raise valid points there, though:
@OP: you might want to try re-installing the latest version of kies, make sure your rom download is successful and the file is not compromised. you can always try another pc for the upgrade.
but and i am repeating myself here:
this is xda developers and not the samsung support forum. samsung has trained and paid professionals to deal with issues like this and you paid for that service with the purchase of your phone. xda developers, however, is not there to support simple things related to the stock usage of the phone, still, if you desperately want ICS on your phone without voiding your warranty, you can still flash your phone through odin. you can read up on that here and will certainly receive support if requested.
Related
Hello,
Official android 2.3.6 has been released in India and I tried to update it through Kies. After the initial download, I get the error, "Firmware Update not responding",
The detailed description of the error is
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: gt-i9100.exe
Problem Signature 02: 11.9.8.1
Problem Signature 03: 4e695566
Problem Signature 04: FirmwareUpdateAgent.Common
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4e695566
Problem Signature 07: 208
Problem Signature 08: 0
Problem Signature 09: System.IndexOutOfRangeException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Read our privacy statement online:
url
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I have the latest version of kies and tried in windows7, 64bit computer and as well as a 32Bit windows 7 PC.
Was you fone full charged or at least 60% charged? Do it this way below>
Stop Kies in task manger if running.
Download firmware which you want to upgrade to from links in forum.
Boot fone into Download mode by Volume down button + Home & Power buttons at the same time and connect usb cable and flash via Odin.
Firmware from http://www.sammobile.com/ or http://forum.xda-developers.com/showthread.php?t=1075278
Odin Flash app from here http://www.multiupload.com/1RTGSE061G
All deatils are laid out how to flash fone.
Just to add turn off any antivirus and firewall to be on the safe side when updating via live update or even flashing via Odin.
Hi everyone!
I have a problem when try to download the "“htc_sync_setup_3.3.21.exe” to my PC.
After run the software at the end does not finish the download to abble me to install the driver due to the following error:
c:\users\Jose\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IES\958DOYEN\htc_sync_setup_3.3.21.exe
I switch off the firewall and antivirus protector and still the sdame problem.
Some time appears with diferent ending such as:
c:\users\Jose\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IES\958DOYEN\setup_2.0.53.0_htc.exe
also at the end of the message said: Unspecified error.
I hope and much appreciated if some one know how can I fix this installation!
Thanks, Jose
Greetings,
Both my devices are stuck in bootloop but they are facing different issues; details are as followed:
Devices Information:
- Manufacturer: SAMSUNG
- Devices Model: SM-J200GU
- Devices Nickname: j2lte
- Region: XME
- Firmware: J200GUDXS3AQG2
- Baseband: J200GUOLB3APC1
PC info:
WIndows 7 Ultimate SP1 with latest updates
Java 8 Update 144.
______________________________________________________________________________________
I know there are thousands of similar threads, most solutions I found were "enable USB debugging", "use ADB Fastboot", "reinstall drivers" and so on but trust me, I've tried every single options I could; few of them are:
REINSTALLED both Android and Samsung USB drivers (from version 1.3.8.5 to 1.5.6.3), whether you mean both installed together or separately
REINSTALLED Minimal ADB and FASTBOOT (1.3, 1.4, 1.4.2, 1.43)
TRIED using different versions of ODIN. (v1.85, v3.09, v3.10.6, v3.11, v3.12)
_____________________________________________________________________________________
Issue for Device #1: PC UNABLE TO DETECT DEVICE
Screen Options: Stock Recovery, Bootloader, Bootsplash/Bootlogo
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
I have tried 3 different cables from SAMSUNG OFFICIAL, Lenovo and another off-market (REMAX) respectively on all the 8 USB PORTS that I have, and yes I have reinstalled the USB PORTS and also DISABLED and re-ENABLING it. I am able to boot into stock recovery but it's written "E: UNABLE TO MOUNT /SYSTEM" when I tried to perform HARD RESET. This only happens after I flashed the latest Firmware (J200GUDXS3AQG2).
_____________________________________________________________________________________
Issue for Device #2: PC ABLE TO DETECT DEVICE
Screen Options: Bootlogo/Bootsplash ONLY
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: OFFICIAL
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED
No matter what key combination I pressed, IT ONLY BOOTS INTO BOOTLOADER MODE. Yes, not even a chance to peek at the BOOTSPLASH/BOOTLOGO screen. Stock firmware flashing was SUCCESSFUL but it BOOTS back to the damn same BOOTLOADER page (without all the details), able to flash TWRP (v2.87, v3.0.0, v3.0.2, v3.1.1) SUCCESSFULLY but FRP LOCK is ON.
_____________________________________________________________________________________
I hope the details given are sufficient enough for all you GRANDMASTERS, HACKERS, DEVELOPERS or even PASSER-BYs to provide me with a solution other than what I have done. In summary;
Device #1: PC unable to detect device, HARD RESET successful with ERROR "E: unable to mount /system".
Device #2: Tried flashing TWRP but FRP Lock ON, tried flashing stock firmware SUCCESSFULLY but boot into BOOTLOADER mode again, unable to enter stock recovery page or any other screens EXCEPT FOR THE BOOTLOADER.
_____________________________________________________________________________________
Thank you in advance & have a great day.
No one?
DaRdamnDoG said:
No one?
Click to expand...
Click to collapse
Have you tried using a different windows computer ?
George Malas said:
Have you tried using a different windows computer ?
Click to expand...
Click to collapse
Device #1 has been fixed, apparently another third party USB cable managed to get my PC to detect it in bootloader mode, the rest was easy.
As for Device #2, I was told by mobile shop owner that in recent months many of Samsung devices (especially Galaxy S7 variants and Galaxy Notes) had the same issue as I mentioned and he explains further that it is some sort of the manufacturers' effort or tactic to encourage mobile users to upgrade our devices.
How big of a ****ing asshole is Samsung to do such thing. Really ? They want to kill your ,quote on quote ,old device just so you can buy a new one. Just so I can clear things up in my mind , you mentioned above that you tried flashing TWRP on device #2 but FRP Lock was ON. But FRP Lock has nothing to do with TWRP. FRP Lock is Factory Reset Protection which purpose is to prevent someone from setting up the phone without knowing the credentials of the Google Account previously linked with the device. As long as your bootloader is unlocked , you can hop on TWRP ,flash a custom ROM and your problem should be solved.
I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.
Hello, I need help, I own a Samsung galaxy s8 and I tried to root it, I failed and ****ed up hard :'(
I tried to flash it following multiple tuto and it failed, I had the issue :
sw rev check fail bootloader device 3 binary 2
but now, my phone has a blue screen with :
an error has occurred while updating the device software.
Use the emergency recovery function in the smart switch PC software
The smart switch pc software doesn't recognize my phone.
Please help me i'm out of option :'(
Hi , try to put your phone into Download mode , and use latest Odin version in order to re-flash the latest stock version of OS if you are note sure which one is , just send me 7 and 8 number from imei ...
Thank you for your answer, I managed to fix my phone by flashing the latest firmware. I was downloading it from a website and it turns out it wasn't the last one.
After I looked on different site, I went on sammobile and I downloaded the latest version, It took me one entire day, the download speed was slow AF and my internet connection crashed in the middle of it.
I had to ask a friend to download it at his place and then, bring it to me.
I'm really happy, I managed to fix it.