Database Users

[HOWTO] [REF] Flash official JPM Froyo 2.2 using KIES

UPDATE: Samsung seems to have pulled the update from their servers. I recommend using Odin to upgrade to JPM/JP6 instead of the method in this tutorial.
LOOK at what kies offers you before flashing if it's not JPM/JP6 then its not the froyo rom described in this thread.
Since some of the threads are buried and out of date I figured I would post this once more. Please read the whole post before flashing it can save you from a lot of hassles later.
Make sure your phone and network uses the same bands as this rom. In other words don't flash this on a US device that needs the 850 band since this rom is for europe.
****If your phone does not have a working 3 button recovery mode or if you don't know what that is then visit this link for more information before flashing your device****
I don't know if this is safe on branded, carrier locked devices.
This should be obvious but backup anything you don't want to lose.
First uninstall all lagfixes
Start up kies and connect your phone. Wait till kies recognizes the sgs.
Go to firmware upgrade.
If it doesn't report a JPM/JP6 upgrade close the upgrade window but do not close kies!
Go to windows start > run > and type "regedit"
Navigate to HKEY_CURRENT_USER/Software/Samsung/Kies/DeviceDB/
You will probably see a bunch of numbered keys (they look like folders) Find the key/folder that has strings that match your current firmware. So if you are on JPK look for that in the keys. If you have more than one galaxy S (it can happen) then match the imei with the phone you want to upgrade.
Change the following values so they look like this:
"SoftwareRevision"="I9000XXJF3/I9000SWC/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEE"
"HIDSWVER"="I9000XXJF3/I9000SWC/I9000XXJF3/I9000XXJF3"
No go back to kies and click on firmware upgrade again. You should now see the JPM upgrade.
Other info:
First boot can take a while so let it sit for a couple minutes while you stare at that glowing S
Doing this will not change your product code.
3 button recovery mode still works.
This won't wipe your phone's apps, settings, messages or SD card. (at least not for me coming from jpk)
It doesn't matter what firmware you are on we are just using the JF3 value to fool kies.
You will lose root if you were rooted. New root by Chainfire can be found here.
If kies crashed while extracting the firmware then try an older version of kies. If kies sees the update but still refuses to flash then try running kies as an administrator.
If your phone really hangs for more than 5 minutes at first boot then something probably went wrong. In that case start up in 3 button recovery mode and do a factory reset. Dont blame the registry hack, its kies that's the problem. As always flash at your own risk
If your android market is missing after flashing read the following thread for a solution: http://forum.xda-developers.com/showthread.php?t=810230
If the phone flashed ok but the rom doesn't run properly, force closes etc, then you can try entering 3 button recovery mode and doing a clear cache and a factory reset. Doing this will wipe your phone.
If you have lost your data connection after flashing you may have to re-enter your APN settings. Your can find this information on your carrier's website.

How to flash official JPM Froyo using kies.
Hi,
First uninstall all lagfixes
Click to expand...
Click to collapse
Is it very important ? If yes, why ?
Thanx

lupin57 said:
Hi,
Is it very important ? If yes, why ?
Thanx
Click to expand...
Click to collapse
Kies might not be able to modify a different filesystem than RFS. So if your lagfix for example uses ext4 then that could be a problem.

All I have done is change the firmware code and I am being offered JPM. So do you really need to change the country code as well?

I cant get this to work, been trying for the last 20 mins. It detects the firmware, starts downloading but crashes on "decyrpting files" every time. Tried on two different pc, one with WinXP 32 and one with Win7 64.
Is this just Kies being crap again? Or am I doing something wrong?

Last question. Does your 3 button recovery still work ?

madpete said:
I cant get this to work, been trying for the last 20 mins. It detects the firmware, starts downloading but crashes on "decyrpting files" every time. Tried on two different pc, one with WinXP 32 and one with Win7 64.
Is this just Kies being crap again? Or am I doing something wrong?
Click to expand...
Click to collapse
Strange, what version of kies are you using? See if there is an update. I'm on win7 64 and have no problems. I have "run as admin" checked in the executable but i doubt that makes a difference.

Tehpriest said:
Last question. Does your 3 button recovery still work ?
Click to expand...
Click to collapse
Recovery mode still works

Tehpriest said:
All I have done is change the firmware code and I am being offered JPM. So do you really need to change the country code as well?
Click to expand...
Click to collapse
Probably not, but it really doesn't matter, Kies overwrites those keys the next time you connect your phone.

dakine said:
Strange, what version of kies are you using? See if there is an update. I'm on win7 64 and have no problems. I have "run as admin" checked in the executable but i doubt that makes a difference.
Click to expand...
Click to collapse
1.5.3.10093_82 on Win7 64 and 1.5.3.10093_81 on WinXP 32, I thought about run as admin too, so I tried that but still same.

madpete said:
1.5.3.10093_82 on Win7 64 and 1.5.3.10093_81 on WinXP 32, I thought about run as admin too, so I tried that but still same.
Click to expand...
Click to collapse
I'm on an older version: 1.5.1.10074_2 so I doubt that's the issue.
So the same thing is happening on different pc's? All I can think of is that you could try doing a factory reset but that will wipe all your data. You removed any lagfixes right?

hi, first of all a big thanks for the easy walkthrough (think allot of people were wanting this) just a few questions, have you applied the lagfix after the firmware update or does it not really need it??
if you did apply the lagfix, any chance you could let us know how you done that? (or just link me to the relevant guide)
ill be trying to apply the new firmware tonight, hopefully kies recognises my phone!
also is this ok to do for branded 8gb vodafone devices??

What happens if I can't remember what lagfix I used... Yes I know it was a stupid mistake :/

dakine said:
I'm on an older version: 1.5.1.10074_2 so I doubt that's the issue.
So the same thing is happening on different pc's?
Click to expand...
Click to collapse
Yeah exactly the same thing, it starts downloadingand gets about 3 quarters of the way along the progress bar, then it changes from downloading files to decrypting files. Straight away the updater crashes and windows says the program is not responding, only option is to close. Dont understand it.
Is this just me guys?
I do have another machine up stairs that has an older version of kies on it, guess I could try that.
Just getting a bit worried that it's kies, and I wont be able to update to anything...god kies is pants.

You should probably add informations about band and frequency so that someone would check it before replacing it with a firmware based on different settings and be left with no data and such

madpete said:
Yeah exactly the same thing, it starts downloadingand gets about 3 quarters of the way along the progress bar, then it changes from downloading files to decrypting files. Straight away the updater crashes and windows says the program is not responding, only option is to close. Dont understand it.
Is this just me guys?
I do have another machine up stairs that has an older version of kies on it, guess I could try that.
Just getting a bit worried that it's kies, and I wont be able to update to anything...god kies is pants.
Click to expand...
Click to collapse
Did you remove any lagfixes? It sounds like kies cant extract the files on the phone. You could also try a factory reset if you don't mind losing your data.

I currently have a i9000m on 2.1 (with unlock, root, and lagfix).
I currently have lagfix disabled with the "disable lagfix" method.
If I were to upgrade to Froyo 2.2, will it update both the Firmware and the Kernel?
(I want to get rid of lagfix permanently).

dakine said:
Did you remove any lagfixes? It sounds like kies cant extract the files on the phone. You could also try a factory reset if you don't mind losing your data.
Click to expand...
Click to collapse
Yeah removed lagfix and unrooted just incase, just trying an older version of kies now. If not I might wait for the uk version, if that doesnt work I'll try the factory reset. Thanks for your help dakine.

david2189 said:
hi, first of all a big thanks for the easy walkthrough (think allot of people were wanting this) just a few questions, have you applied the lagfix after the firmware update or does it not really need it??
if you did apply the lagfix, any chance you could let us know how you done that? (or just link me to the relevant guide)
ill be trying to apply the new firmware tonight, hopefully kies recognises my phone!
also is this ok to do for branded 8gb vodafone devices??
Click to expand...
Click to collapse
I have not applied another lagfix yet, first I need root access.
Sorry I'm not sure about branded devices especially if they are carrier locked.

It was kies, just tried on a third Win7 pc but this one has kies version 1.5.1.10074_45 installed and its gone through the upgrade without crashing....so far.
Edit: Yep thats worked, I'd best not upgrade this version of kies!

Link for the Android 2.3.3 GRI54 for the Nexus S 9023

I flashed my Nexus S with CM7 RC 4. Accidentally my original nandroid backup got deleted. I want to flash my device with the factory android 2.3.3 image. Please let me know the link to download the Android 2.3.3 for SNS 9023 GRI54.

You find it on:
http://forum.xda-developers.com/showthread.php?t=973534

I have already downloaded the rom files and the odin but the odin don't recognise my NS.
Can you tell me how to do a fastboot flash ?

If you want odin to recognize your nexus you have to install the samsung usb drivers .. You can find them here: http://forum.xda-developers.com/showthread.php?t=728929

I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.

I do not have a fastboot image for you ..btw the google drivers are not the same as the samsung drivers ..for odin you will need the samsung ones ...
To go into downloadmode :
turn on you phone, plug your phone into a sb port ( as if you wanted to put something on the phone) then while your phone is still connected to your pc , switch you phone off and keep holding vol up + vol down ..you will see that if you keep holding them phone will go into download mode after you phone is switched off

jaivinder said:
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
Click to expand...
Click to collapse
You installed the samsung drivers, make sure that your phone is power on,disable the usb debugging, ceheck that microsoft.net framework is installed on your pc. When you connect your phone (on your device manager) you must have "android phone" and below that "nexus s" with out any question symbols.If so then select to update your driver and give the path you installed the samsung drivers (eg c:\program files\samsung ....).
Power off you phone, open Odin and follow the pdf file from samfirmware to load the files (bootloader,pda,modem,csc). Hold your phone from the middle of volume buttons(between vol up and vol down) and immediately connect your phone to your pc with the usb cable .you are going to see the yellow triangle with the android.
Try it

Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.

hamajiro said:
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
Click to expand...
Click to collapse
What kind of error?on Odin or on your phone?

afilopou said:
What kind of error?on Odin or on your phone?
Click to expand...
Click to collapse
On Odin. The error message is in Korean so I don't know what it says, but it says something about the PDA tar. Please see the attached image.
Thanks

If I do it without PDA, I don't get an error...

hamajiro said:
If I do it without PDA, I don't get an error...
Click to expand...
Click to collapse
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522

afilopou said:
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
Click to expand...
Click to collapse
Thank you so much for your help.
I don't have a windows PC, but I'll install Windows 7 to my MBP using bootcamp and see how that goes.
I'll check the md5 check sum as well.
Sent from my Nexus S using XDA Premium App

Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App

hamajiro said:
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Looks like that the virtual machine (vm fusion) on macosx generates problems.As far as i remember only parallels worked ok.I have imac as well but i have bootcamp win7 in order to avoid all these problems. Hope to help
Sent from my Desire HD using Tapatalk

Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...

hamajiro said:
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
Click to expand...
Click to collapse
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk

thanks, really needed this link

afilopou said:
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No, I don't remember the initial values...
I'll check them at a Vodafone store when I get a chance.
Sent from my Nexus S using XDA Premium App

OK, so I had a chance to go into a local Vodafone Australia store.
The Baseband version under 'About phone' from the settings was I9023XXXKB1.
Under fastbootmode, the bootloader and baseband versions were I9020XXXKA3 and I9020XXXKB1.
However, CARRIER INFO is 'XSE' for Vodafone Australia, where as the CARRIER INFO from the Samfirmware.com ROM is 'EUR'.
Almost back to factory stock condition! Is it possible to change the carrier info? Does anyone know where I can get the stock Australian ROM for Nexus S?

Aftermath Of Flashing German ROM XLPY

When the official German ICS ROM LPY was released I decided to flash it using Odin rather than wait for the official UK ROM for my UK Note. I thought because it was an official ROM there would be little risk and I would be able to replace it with the UK ROM when that was released.
However, now that the official UK ROM is available I find that I cannot flash it with Odin because Odin no longer detects the Note in download mode. I also found that I could not use Kies because although it could detect the Note, it did not recognise it for updates.
I have never rooted my Note or flashed anything other than the official ICS ROM LPY using Odin.
So I had a working Note but no way of returning to a UK ROM or updating the installed German ROM. So I decided to change the CRC code to the German one ODT to match the German ROM and that seems to have fixed the Kies problem. Changing the CRC code does a factory reset but at least I now might be able to use Kies or OTA for future German ICS updates.
If you search using Google you will find loads of people who can no longer use Odin because it no longer detects their phone. Many reasons have been suggested such as bad USB cable, wrong or corrupt drivers, interference from Kies running in the background etc and I have tried those solutions without success. But I believe that in some cases it is the result of flashing the wrong firmware as I did
Some people have then tried to use recovery mode to solve the problem and ended up not being able to use their phone at all. There are others who are stuck on a buggy custom ROM and cannot use Odin to escape.
I am hoping that there will eventually be an official German ICS update that I can flash using Kies or OTA that will replace my current German ROM and allow me to use Odin again to flash the correct UK ROM.
I'm lucky that at least I can still use my Note normally even though it has German firmware. But if I eventually manage to get the UK firmware installed and running again then I will wait for the correct official updates for my Note in future.

You sure have a weird problem. Did you try on a different computer?
Maybe mobile odin could be helping you out, it's in play store.
i know that you really need the correct drivers to let Odin detect your device, installing kies takes care of that, but i know there are separate drivers around here somewhere to so you won't need kies on your PC (it highly interferes with Odin).
I would give you the link but am on my Note now.
Sent from my GT-N7000 using xda premium

Hi, uninstall Kies and reboot your PC. Then download the latest version of kies and install it again. Connect your Note via USB cable and wait for the drivers to get installed. Then put your phone in download mode, close kies and connect the Note to the PC. Wait for Windows to automatically download and install the drivers. Once the drivers are installed, open ODIN. It should detect your phone in Download Mode.

Nirak said:
You sure have a weird problem. Did you try on a different computer?
Maybe mobile odin could be helping you out, it's in play store.
i know that you really need the correct drivers to let Odin detect your device, installing kies takes care of that, but i know there are separate drivers around here somewhere to so you won't need kies on your PC (it highly interferes with Odin).
I would give you the link but am on my Note now.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
If you read some of the many posts by people who cannot use Odin to flash any more then you will see people have tried different computers, separate drivers, Kies drivers, starting Odin in administrator mode, several cables including official Samsung USB cable, trying Kies Mini, using Task Manager to stop any Kies software running whilst using Odin etc. but to no avail. Which is why I believe the problem for some people is within the Note and not the PC.
Unfortunately, in order to use Mobile Odin you need to be rooted and you need to use Odin get root. Although I read a post here recently where someone had developed a way to root without using Odin. It would be interesting to hear from anyone who has used that non-Odin root method to use Odin Mobile to flash a new ROM.

lifehijack said:
Hi, uninstall Kies and reboot your PC. Then download the latest version of kies and install it again. Connect your Note via USB cable and wait for the drivers to get installed. Then put your phone in download mode, close kies and connect the Note to the PC. Wait for Windows to automatically download and install the drivers. Once the drivers are installed, open ODIN. It should detect your phone in Download Mode.
Click to expand...
Click to collapse
I tried your method but to no avail because I think my problem and many others is within the phone rather than the PC.

Gaugerer said:
If you read some of the many posts by people who cannot use Odin to flash any more then you will see people have tried different computers, separate drivers, Kies drivers, starting Odin in administrator mode, several cables including official Samsung USB cable, trying Kies Mini, using Task Manager to stop any Kies software running whilst using Odin etc. but to no avail. Which is why I believe the problem for some people is within the Note and not the PC.
Unfortunately, in order to use Mobile Odin you need to be rooted and you need to use Odin get root. Although I read a post here recently where someone had developed a way to root without using Odin. It would be interesting to hear from anyone who has used that non-Odin root method to use Odin Mobile to flash a new ROM.
Click to expand...
Click to collapse
I've rooted my stock ICS following this thread:
http://forum.xda-developers.com/showthread.php?t=1647148
no odin involved.
But i never used MobileOdin.

Nirak said:
I've rooted my stock ICS following this thread:
http://forum.xda-developers.com/showthread.php?t=1647148
no odin involved.
But i never used MobileOdin.
Click to expand...
Click to collapse
Yes, that is the method I was talking about. You could try MobileOdin available in Google Play to see if you can run it and perhaps flash a rom. That would be interesting for it would eliminate all the PC problems.

Gaugerer said:
Yes, that is the method I was talking about. You could try MobileOdin available in Google Play to see if you can run it and perhaps flash a rom. That would be interesting for it would eliminate all the PC problems.
Click to expand...
Click to collapse
Why don't you give it a go yourself:
http://forum.xda-developers.com/showthread.php?t=1347899
I've just set up my device as i wish and have no intention of flashing it again..sorry

I am on LPY and was able to flash SpeedMod via PC Odin with no problems.
Try different USB port and use the original Samsung USB cable. I never used Kies before, so I am not sure about this part. I used to setup the driver installer only.
Hope it helps..

[Q] Samsung Kies issues

Obviously, kies is a **** piece of software. My phone connected once, where I did a full backup, and proceeded to restore stock mf3 firmware through Odin, which worked fine. Now...I cannot connect to Kies to update to Android 4.3. It comes up in explorer and everything works fine, but i get "Connecting" in Kies and then an unsupported device message. Any known fixes?

Is 4.3 worth losing SafeStrap?
Sent from my SGH-I337 using Tapatalk

HeDsh0t said:
Obviously, kies is a **** piece of software. My phone connected once, where I did a full backup, and proceeded to restore stock mf3 firmware through Odin, which worked fine. Now...I cannot connect to Kies to update to Android 4.3. It comes up in explorer and everything works fine, but i get "Connecting" in Kies and then an unsupported device message. Any known fixes?
Click to expand...
Click to collapse
Kies works just fine if you use it for what it is intended for. If it connected to your phone before, but will not now it is because something on your phone or your PC changed not Kies. Also, Kies does not have the 4.3 firmware yet, so it wouldn't update your phone anyway. You either have to get the OTA or side load the update. It sounds to me like you have a driver issue, but it's definitely something on your side if it connected before.

HORiZUN said:
Is 4.3 worth losing SafeStrap?
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
To be honest, Im not sure what that is. I rooted my phone on mf3 firmware, and couldnt unlock my bootloader, unless I would install Echoe 4.3 rom, but cant install a custom recovery.

Find the sticky in the general section about SafeStrap for MF3 firmware before you update the device to 4.3. You may change your mind.
Sent from my SGH-I337 using Tapatalk

HORiZUN said:
Is 4.3 worth losing SafeStrap?
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
scott14719 said:
Kies works just fine if you use it for what it is intended for. If it connected to your phone before, but will not now it is because something on your phone or your PC changed not Kies. Also, Kies does not have the 4.3 firmware yet, so it wouldn't update your phone anyway. You either have to get the OTA or side load the update. It sounds to me like you have a driver issue, but it's definitely something on your side if it connected before.
Click to expand...
Click to collapse
I have no idea what I could be doing wrong, it seems 90% of people have issues with this poorly coded software.

HeDsh0t said:
I have no idea what I could be doing wrong, it seems 90% of people have issues with this poorly coded software.
Click to expand...
Click to collapse
90% of the people are not using it correctly. Like I said, it works just fine for what it is intended for. It was not intended to use on a phone that has been modified or changed in any way other than factory specs for any reason. It is not supposed to re-flash firmware on a phone that was messed up modifying in any way...that includes rooting. So if you are trying to use Kies for any reason, and do not have a 100% stock phone, it is already user error. Also, the correct drivers need to be installed for it to work.

scott14719 said:
90% of the people are not using it correctly. Like I said, it works just fine for what it is intended for. It was not intended to use on a phone that has been modified or changed in any way other than factory specs for any reason. It is not supposed to re-flash firmware on a phone that was messed up modifying in any way...that includes rooting. So if you are trying to use Kies for any reason, and do not have a 100% stock phone, it is already user error. Also, the correct drivers need to be installed for it to work.
Click to expand...
Click to collapse
I AM 100% stock, thats the thing. It actually worked when i was rooted, and now that I am on stock, it doesn't work

HeDsh0t said:
I AM 100% stock, thats the thing. It actually worked when i was rooted, and now that I am on stock, it doesn't work
Click to expand...
Click to collapse
Also, MF3 was never on Kies either so I'm not sure if it would make a difference or not. Plus, you can always try Kies3 and see if it will connect.

scott14719 said:
Also, MF3 was never on Kies either so I'm not sure if it would make a difference or not. Plus, you can always try Kies3 and see if it will connect.
Click to expand...
Click to collapse
Looked into safestrap...might do that and flash a custom Echoe rom at 4.3

But really, what is wrong with Kies. Coming from a rooted S4 to a stock S5, Kies is shameful. The user need file access!

Note 3 Factory Data Reset Daily -

Ok - haven't seen this problem anywhere - all I see are posts and articles regarding how to get it off the Samsung screen during boot... Which is a Factory Data Reset... I have to FDR my phone daily.. not running anything custom (accept this was originally a Rent-A-Center phone - and I know they have a special system built in to kill the phone if its not paid for etc... Was paid off well over a year ago)
How do I fix this?? Do I have to root and install a custom ROM?? Do I have to do something else? Having to FDR every day, and sometimes twice is becoming rather annoying.

Flash your models stock rom through Odin .

JJEgan said:
Flash your models stock rom through Odin .
Click to expand...
Click to collapse
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.

AncientNerd said:
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.
Click to expand...
Click to collapse
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Awesome - Thanks!

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!

AncientNerd said:
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!
Click to expand...
Click to collapse
What's your phone's model? It doesn't have to be carrier-specific to be able to flash it.
Also, try TWRP instead of CWM recovery, devs seem to prefer TWRP overall.

SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.

AncientNerd said:
SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.
Click to expand...
Click to collapse
I've got a N900T and I've found software in both Sammobile and Updato, I don't know why you're not finding anything (N900T is supposed to be T-Mobile's variant)
Anyway, I would try out the following tutorial: Link
I found it very useful when I wanted to completely flash my phone clean and root.
I am not sure about what roadblocks you could have of this phone being a RAC phone, but if you still want to give it a try I'd suggest you try out the tutorial I showed you