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!

Tab is Fu***d

So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions

Not come back on at all ?
Contact your service center then
Oh one thing...
When something like this happened, people call it "Bricked" not "Fu***d".

GOF007 said:
Not come back on at all ?
Contact your service center then
Oh one thing...
When something like this happened, people call it "Bricked" not "Fu***d".
Click to expand...
Click to collapse
lol i am fully aware of that just expressing how i feel about the brick and saying that it will not do anything..no download mode nothing.

thenewak said:
So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions
Click to expand...
Click to collapse
Do you get any lights whatsoever when it's plugged in?
Also, have you tried leaving it on charge for a while in the mains? Generally, when ODIN fails, the phone/tab allows you to get back into download mode, so this is new to me.
Was it flashing the radio (modem.bin) at the time, out of interest?

nprussell said:
Do you get any lights whatsoever when it's plugged in?
Also, have you tried leaving it on charge for a while in the mains? Generally, when ODIN fails, the phone/tab allows you to get back into download mode, so this is new to me.
Was it flashing the radio (modem.bin) at the time, out of interest?
Click to expand...
Click to collapse
No modem only the .tar and .pit files. i had flashed my galaxy s plenty of times with no problems. i left it charging tonight while im at work to see if that will do anything but i get no lights or anything. ive seen that some ppl get the pc to device screen but i dont get that either. but just wanted to try some things before shipping it to samsung only bc im in iraq and shipping takes forever.

Do U get anything when plugging the tab via USB to your computer ? And I do not mean Odin, I am just saying if the computer sees the USB connection.
Also, have you tried to press the POWER button and tap the screen at the same time ?
P_

pakalrtb said:
Do U get anything when plugging the tab via USB to your computer ? And I do not mean Odin, I am just saying if the computer sees the USB connection.
Also, have you tried to press the POWER button and tap the screen at the same time ?
P_
Click to expand...
Click to collapse
Nope the computer doesn't recognize it either. i get nothing at all..no i haven't tried that ...what exactly will that do?

If I bricked my Tab, I too would describe it as F***ED! But even with my moderate modding experience, Im not ready to do the phone mod. Just seems to me like too much risk.
Good luck with your Tab!

How is this a development issue? This isn't your personal support forum.

miketaylor00 said:
How is this a development issue? This isn't your personal support forum.
Click to expand...
Click to collapse
well i figured this would be an appropriate place to ask this type of ? as other ppl do. due to the fact that i was installing firmware from this section of the forums i figured i would ask the developers that read and write here.
anyways...i called samsung and told them idk why it wont cut on and they said to call it a power issue. so im going to send it to them to see if they can tell what i did..hopefully not. but we will see.

thenewak said:
well i figured this would be an appropriate place to ask this type of ? as other ppl do. due to the fact that i was installing firmware from this section of the forums i figured i would ask the developers that read and write here.
anyways...i called samsung and told them idk why it wont cut on and they said to call it a power issue. so im going to send it to them to see if they can tell what i did..hopefully not. but we will see.
Click to expand...
Click to collapse
Try leaving it connected to your computer for up to 1 hour with Odin loaded and ready on the screen.
Someone it will take time before it allow your PC to talk to it when it a messed up state due to a bad flash!

rmanaudio said:
Try leaving it connected to your computer for up to 1 hour with Odin loaded and ready on the screen.
Someone it will take time before it allow your PC to talk to it when it a messed up state due to a bad flash!
Click to expand...
Click to collapse
even if it will not power on at all?

thenewak said:
So i was flashing the firmware to use the phone on the tab and while doing it the install failed. the tab cut off and will not come back on at all. no download mode nothing...anything can help. wont connect to odin either. any suggestions
Click to expand...
Click to collapse
What were the names of the tar and pit files you flashed?

rotohammer said:
What were the names of the tar and pit files you flashed?
Click to expand...
Click to collapse
i dont see the thread on here but it was on here about a week ago. the first one that got you 3g + phone. Im not on my laptop bc im at work but do you know what im takling about.
Edit: i think it was the old JME and 512.pit...

OK just as an update and for anyone who had the same prob...as in tab will not do anything...i called samsung used the 1 yr warranty and told them it was a power issue...that i went to work it was on came home it was off and wouldnt power up so they replaced it with another one.

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

[Q] S4 stuck in download mode

OK s4 got the new lollipop update but when it kept in asking I clicked OK but it COMPLETELY TURNED OF THEN rapidly said could not do normal boot on the top but I remove battery still going into download mode my phone was in 4.4.4 root but I in rooted also please help me I really need to take business calls how do I get BACK AND GET 5.0 ?

Guccimaine said:
OK s4 got the new lollipop update but when it kept in asking I clicked OK but it COMPLETELY TURNED OF THEN rapidly said could not do normal boot on the top but I remove battery still going into download mode my phone was in 4.4.4 root but I in rooted also please help me I really need to take business calls how do I get BACK AND GET 5.0
Click to expand...
Click to collapse
Sounds like the rom is corrupt or not present, you would need to kies or odin back to 4.4.4 and reapply.
If you cant do anything BUT download mode, you gotta get odin and go to sammobile download your phones official rom and apply it. After this you can attemp the OTA update again.
PLEASE READ THE GUIDE CAREFULLY as this procedure is risky if done wrong or on a bad usb connection.
Lollipop uses a new system it's not a normal update.

Don't use Kies , use Odin.
Kies can easily break your phone.
Just use Google for ROM searching and install them over Odin.
Sent from my GT-I8190 using XDA Free mobile app

OverBit said:
Don't use Kies , use Odin.
Kies can easily break your phone.
Just use Google for ROM searching and install them over Odin.
Sent from my GT-I8190 using XDA Free mobile app
Click to expand...
Click to collapse
Just now missed it use kies my phone died it was on a black screen got over heated got sceard went to best buy and fixed it for free

Guccimaine said:
Just now missed it use kies my phone died it was on a black screen got over heated got sceard went to best buy and fixed it for free
Click to expand...
Click to collapse
Good to hear it's fixed, Kies is a "supported" program so when it screws up you usually can get it fixed for free. Odin is not (even though it works better)

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