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.
Related
Hi,
I tried to follow some instructions on how to flash a custom rom on my galaxy tab 10.1 and unfortunately had to abort in step 2: step 1 was to put the device into download mode, step 2 was to use Odin to flash recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5. I used heimdall 1.3.1 to do it as I don't have any Windows nearby. Heimdall detects my device but loading the file mentioned above as a "Heimdall Firmware Package" fails with the following error:
"firmware.xml is missing from the package"
How do I proceed from here? I would like to have a different ROM because I bought my device in the US but live in Europe (Germany). Some apps like amazonmp3 dont work like this - not sure why but I believe it has to do with my credit card being German etc.
Any suggestions?
cheers
mathiase
Hi again, I just found a thread about running Odin in VirtualBox and I immediately tried it: I could pass the device through to a 32bit Windows XP and installed Odin drivers. Odin detected the device BUT THE WHOLE VM CRASHED when I started the process! Now my Galaxy Tab does not boot at all and tells me to attach it to Kies... PANIC!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
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.
i have Samsung galaxy s1 device i gave to a friend to install new software on it because it had problems in call connectivity when he did that the problem was solved but i had new problems. i can't access googleplay and when i try to install .apk package most of the times the installing halts or throws error for no reason and when i connect to kies it says :
your device's current firmware version is not supported to update firmware via kies
current firmware version : PDA:JPG / PHONE:JPE / CSC:JPF (ATT)
can anyone help me or tell me what to do plz
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.
Hello guys, sorry for my bad English but I hope you will understand my post
I have an old Kiano 5.1 Elegance phone (MT6580). It was broken for a while - freezed on logo after power on. I found matching firmware and compatible flasher: SP Flash Tool. I ticked format all + download. Everything went smooth.
Sadly, the phone is dead now. Even no logo on the screen. I connected it again and clik on Memory Test. All tests passed. Next I clicked Firmware Upgrade - failed with error "Unable to get PMT info". I tried with and without battery.
Also, Download Only and Format + Download is working. Just no turning on after flashing is completed.
Drivers updated with Autoinstaller for Windows 10 64bit.
Can I fix it on my own or just throw it away from the window?
Thanks fo any help.