Related
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!
Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.
Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!
Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................
The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.
Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.
Doesn't work to flash with odin either?
xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.
sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M
Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...
Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??
Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.
READ BEFORE YOU FLASH: THIS FIRMWARE HAS A PROTECTED BOOTLOADER THAT WILL PREVENT YOU FROM FLASHING SAMSUNG OFFICIAL FIRMWARE.
MORE INFO HERE
I don't know if this process actually flash boot and spl because JM6 doesn't seem to have them, but you're on your own and I don't recommend you to do it.
Ok I'm going to make a detailed guide of how this worked for me because succeed depends a lot on which firmware you have in your tab. It's a good idea to start with JM6 since you can flash it completely if you have an older firmware or JMA (I guess you won't be able to flash it in the future if a new firmware is released). You won't lose your internal SD Card data but your phone will be factory reset.
1) Download JM6 from HERE
You'll get Odin 1.7 + PIT + PHONE + PDA + CSC.
2) Download JMA from here: HERE
3) Download JMC from here: HERE
4) Start Odin 1.7 and select:
*PIT P1_SMD_MAP.pit
*REPARTITION YES
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: CODE_P1000XXJM6.tar.md5
*PHONE: MODEM_P1000XXJM6.tar.md5
*CSC: CSC_P1000OXAJM6.tar.md5
5) Put your TAB in download mode: Turn it off, press POWER + VOL DOWN
6) Press start in ODIN and wait until process is completed. Your tab will REBOOT in download mode.
7) Now press POWER + VOL UP and when you see SAMSUNG logo RELEASE POWER BUT KEEP PRESSING VOL UP in order to enter recovery and let the TAB flash dbdata, it'll reboot and boot into android. (unplug your USB cable because Odin won't recognize it on some systems)
8) Open Odin 1.7 again or press RESET and select:
*PIT: NONE
*REPARTITION NO
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: JMA.tar (from JMA file obviously)
*PHONE: NONE
*CSC: NONE
9) Repeat 5), 6) and 7)
10) Open Odin 1.7 again or press RESET and select:
*PIT: NONE
*REPARTITION NO
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: P1000XXJMC_P1000OXAJMC_P1000XXJMA_HOME.tar (from JMC file obviously)
*PHONE: NONE
*CSC: NONE
11) Repeat 5), 6) and 7)
I have an AT&T TAB and this process worked for me.
If you need 850 + 1900 you only have to flash MODEM (PHONE button in ODIN) from HERE (modem_bell_i9000.zip) with No PIT, no repartition, no PDA and no CSC.
I hope this helps anybody and sorry about my english
EDIT: If for some strage reason you get the !!! --- !!! screen in your tab, don't panic. You can start the whole process again, Odin will detect your phone, it's a download mode anyway.
EDIT2: I always choose to wipe all my data. I use Titanium backup and I can get most of my data back from there. It's better to have a functional tab than a brick full of useless data. Wiping will always be safer.
EDIT3: Made some modifications to step 7. What you need to do is to enter recovery and that's it. It wasn't clear. Now I think you'll get it right. I didn't test it without step 7 but some people seems to be doing well without doing step 7. Maybe device is entering recovery automatically and flashing dbdata on its own (this is to be expected but sometimes it just doesn't happen).
What about rooting the device before you flash...?
Working great!!! However, I just didn't do step 7 in any of the 3 updates. What exactly do you mean in step 7? Which of the 4 options should I choose in Step 7?
Thanks
pt4audi said:
What about rooting the device before you flash...?
Click to expand...
Click to collapse
I could root my device with z4root or superoneclick.
lucboucim said:
Working great!!! However, I just didn't do step 7 in any of the 3 updates. What exactly do you mean in step 7? Which of the 4 options should I choose in Step 7?
Thanks
Click to expand...
Click to collapse
When flashing ends your device should install dbdata in recovery mode. Maybe with this procedure dbdata is flashed automatically when flashing JM6 at the beginning it's not necessary to do it manually.
If dbdata is not flashed you will not be able to boot android. Your device should display something like this when that happens (in recovery mode):
E:copy_dbdata_media:cant mount DBDATA: copy default media conent failed.
Click to expand...
Click to collapse
But I guess you're ok
Just ignore step 7 if your device entered recovery mode automatically after flashing ended.
OP , did U enable the voice capabilities ? And what was your initial firmware ?
Do U feel confident to say that you can str8 go from whatever FW you have to JM6 as a full flash , and not anymore move your way up from JJ4 (russian FW ) ?
P
pakalrtb said:
OP , did U enable the voice capabilities ? And what was your initial firmware ?
Do U feel confident to say that you can str8 go from whatever FW you have to JM6 as a full flash , and not anymore move your way up from JJ4 (russian FW ) ?
P
Click to expand...
Click to collapse
If by voice capabilities you mean putting a sim card, yes, I tried and it works fine. I didn't test it that much, just a few calls and a lot of gprs. My initial firmware was jk5.
If I had a firmware older than JJ4 I'd just try to flash JM6 directly. I'm guessing here but I think that flashing JM6 the way I flashed it (following another guide in another forum) is like a full flash, it shouldn't matter what you had before.
Maybe someone with more knowledge could throw a light in here. What I can tell you is that I'd do it. I'm one of those guys that learn the hard way, and I've never bricked a device for good.
You're like me then. I do not even have my Tab yet but my fingers are already so much itching. In the meanwhile I am reading and learning. I am totally new to Samsung but I've had my hands busy for the past year with my Nexus One, so quite confortable playing with rom/kernel/radio world .
P_
Flashing for morons
Monrad, thanks, this is a super post.
Just for me and all the other morons in the world. Can you also please give a basic run through of what you've done. I have the following questions.
1) You have 3 waves of activities in your post: JM6, JMA, JMC. Generally, what is each wave doing?
2) Please would you also explain what the fields in Odin1.7 are for?
*PIT -does this set the partitions on Samsung tab?
*REPARTITION -if PIT file this is automatically selected
*AUTO REBOOT YES -why do I select yes
*F. RESET TIME YES -what's this one for?
*PDA: CODE_P1000XXJM6.tar.md5 -PDA is core PDA firmware?
*PHONE: MODEM_P1000XXJM6.tar.md5 -what does this do? load modem drivers?
*CSC: CSC_P1000OXAJM6.tar.md5 -I'm not sure what CSC stands for and does?
3) With regards to getting my dirty hands on the right firmware, when I go to http://www.samfirmware.com/WEBPROTECT-p1000.htm, I look at the latest firmware for Europe. At the bottom of the list are 3 downloads:
a) JM6, b) JMA, c) JMC. What are the differences between these firmwares. I understand that J = 2010, but don't know how to decrypt last two digits.
4) Which PIT should be used in Step 1 of your sequence? What are the PIT files at the bottom of the page (in Flash Tools Section) of http://www.samfirmware.com/WEBPROTECT-p1000.htm
5) I bricked my tab. I got it alive again, only by loading the JMA via Odin 1.7. Basically I put my Tab in Download Mode. Started Odin1.7. Used the Eur Pit file (referred to in my Step 4), and then loaded JMA.tar (extracted from JMA file mentioned in my Step 3). With all the check marks checked in Odin. That was it, and my Galaxy Tab rebooted and seems to work totally fine. Why would I do the other steps mentioned in your sequence? What benefit is there?
5a) Note when I do *#1234# I get:
PDA: blank
PHONE: P1000XXJMA
CSC: blank
the PDA and CSC show blank....is that why I should first load JM6 and follow your sequence? What functionality do I currently not have because of these blanks?
6) A question on rooting my Tab... what are the benefits to doing this?
Thanks for dealing with my long winded post! I really appreciate what you've done so far.
You are a good man, Monrad!
I followed steps and got my AT&T tab updated.
A word about wiping data: I had my Tab fully set up with original AT&T firmware and then I started installation I got into lots of trouble. Instead of recovery mode it went into blank screen with vertical white line (I suspect it did dbdata update behind it though), then it rebooted and my apps started crashing.
The only way to fix it was to get to setting and do factory reset. After that everything went by the book.
So you may want to clarify that data must be wiped from Android, unless you have some other way.
Thanks again
How and where do I find the Dbdata file ?
When I go for step 7 i get the "can´t mount" and "media content failed" messages.
Edit:
alexnoalex said:
So you may want to clarify that data must be wiped from Android, unless you have some other way.
Thanks again
Click to expand...
Click to collapse
I believe this can also be done from recovery.
i used roto-jmc and dont boot into recovery of flash dbdata.rfs seperately and everything is working fine.
kromosto said:
i used roto-jmc and dont boot into recovery of flash dbdata.rfs seperately and everything is working fine.
Click to expand...
Click to collapse
Where did you get the Roto-jmc?
from the link
http://forum.xda-developers.com/showpost.php?p=9989856&postcount=50
Great man. Thanks.
Edit: didn´t help. I still get the same errors.
I now seems to work. But my *#1234# says jm6 even on the jmc firmware?
Anybody knows what is the differences between JMA and JMC ?
You don't need to flash JMA. You can go straight from JM6 to JMC
You can skip oen unnecessary step
Can i do this on my euro Tab from Denmark?
Im on JM6
Sent from my GT-P1000 using XDA App
Just did the update from JMA on a euro tab, I took the firmware from samfirmware not the one on the first post. I don't know the difference but the size is not the same..
Everything works fine, even without doing a factory reset, all my applications are working fine.But I don't see any differences between JMA and JMC
Guys
Currently i have
PDA: P1000JPJJ1
PHONE: P1000JXJJ1
CSC: P1000OJPJJ3
Its currently arabic firmware. Can i use this guide & update to this Euro fimrware? I dont need arabic. I am not rooted as well. Will this guide work for me?
i have a problem, all ok till JM6
and tab after start fine
but for JMA or JMC no dbdata in recovery
help me (for now i'm back to JM6)
Hey friends,
I really looked everything up, but I could not find anything what helped me with my problem.
I have a Galaxy S4 (GT-i9505) and I wanted to update my modem from MKE to ML6. Because I had some issues with updating it (there still was the MKE at my "Status" after updating to ML6), I tried to double-overwrite it (someone wrote at a forum, that that will solbe the overwriting method). So, I started Odin 3.09 and deleted the "Auto Reboot" option. After the first flashing, I took out the battery and replaced it again. Then I did a secound modem flashing. The result was: There was still the MKE modem AND I cannot call anyone. Everytime I try to call someone and I click the call button, my Galaxy seems to crash. The screen is getting black and I have to shut it down by holding the power button for several secounds. Of course, I already tried out other modems (like to MKE modem again and MJ8), but the problem still exists.
Could anybody please help me!
Thanks,
Robert
Have you tried changing rom + modem? you cannot just randomly try modems with a certain rom as some will work others not.
A|ex said:
Have you tried changing rom + modem? you cannot just randomly try modems with a certain rom as some will work others not.
Click to expand...
Click to collapse
Yes, I tried both the Google Roms 4.4 and 4.3, as well as several other custom roms.
robatkills said:
Hey friends,
I really looked everything up, but I could not find anything what helped me with my problem.
I have a Galaxy S4 (GT-i9505) and I wanted to update my modem from MKE to ML6. Because I had some issues with updating it (there still was the MKE at my "Status" after updating to ML6), I tried to double-overwrite it (someone wrote at a forum, that that will solbe the overwriting method). So, I started Odin 3.09 and deleted the "Auto Reboot" option. After the first flashing, I took out the battery and replaced it again. Then I did a secound modem flashing. The result was: There was still the MKE modem AND I cannot call anyone. Everytime I try to call someone and I click the call button, my Galaxy seems to crash. The screen is getting black and I have to shut it down by holding the power button for several secounds. Of course, I already tried out other modems (like to MKE modem again and MJ8), but the problem still exists.
Could anybody please help me!
Thanks,
Robert
Click to expand...
Click to collapse
it seems that your doing in a wrong way mate Try this , Turn OFF your Phone Manually (Wait about 5 sec) Now press and hold Power+VolumeDown in order to reach Download mode. Open odin select PHONE/CP (Find the modem you download) Connect the cables (check to see if it shows added on top/or should be a blue?Notsure or wait atleast 10 sec) then click start ,once done , remove the cable. and after done rebooting go to you phone setting>More>Device info and check if your baseband version change. have a nice day.
Repulsa said:
it seems that your doing in a wrong way mate Try this , Turn OFF your Phone Manually (Wait about 5 sec) Now press and hold Power+VolumeDown in order to reach Download mode. Open odin select PHONE/CP (Find the modem you download) Connect the cables (check to see if it shows added on top/or should be a blue?Notsure or wait atleast 10 sec) then click start ,once done , remove the cable. and after done rebooting go to you phone setting>More>Device info and check if your baseband version change. have a nice day.
Click to expand...
Click to collapse
Thanks, but that is what I have done at least ten times. I tried Odin3.04 and Odin3.09. I tried MKE, ML6, MJ8. I tried Google Roms 4.4 and 4.3, as well as other custom roms. That's weird!
I have never had any luck with 3.09 i always stick to 3.07, where are you getting your modems rom?
robatkills said:
Thanks, but that is what I have done at least ten times. I tried Odin3.04 and Odin3.09. I tried MKE, ML6, MJ8. I tried Google Roms 4.4 and 4.3, as well as other custom roms. That's weird!
Click to expand...
Click to collapse
Mind giving this a shot?pull your battery out wait a few sec atleast and put it back and then hold and press power+volume down /follow the tutorial on top. Check to see if the modem gonna change .
Sent from Hell ?
A|ex said:
I have never had any luck with 3.09 i always stick to 3.07, where are you getting your modems rom?
Click to expand...
Click to collapse
I got the modems from here: http://forum.xda-developers.com/showthread.php?t=2192025
Repulsa said:
Mind giving this a shot?pull your battery out wait a few sec atleast and put it back and then hold and press power+volume down /follow the tutorial on top. Check to see if the modem gonna change .
Sent from Hell ?
Click to expand...
Click to collapse
Which tutorial do you mean?
btw: sending a sms works, as well as receiving....but no incoming or outgoing calls
Had the same thing yesterday, tried all sorts of modems, with no avail.
Ended up flashing a stock rooted Rom (MGA), flashing a custom recovery and restored a Nandroid. Forgot that flashing a complete stock Rom usually also wipes the internal SD so that was a bit of a hassle.
Now, running a new Rom again, with Wifi, sound and being able to make/receive calls again. Easiest fix also: flash a (compatible) stock Rom :good:
Pfeffernuss said:
Had the same thing yesterday, tried all sorts of modems, with no avail.
Ended up flashing a stock rooted Rom (MGA), flashing a custom recovery and restored a Nandroid. Forgot that flashing a complete stock Rom usually also wipes the internal SD so that was a bit of a hassle.
Now, running a new Rom again, with Wifi, sound and being able to make/receive calls again. Easiest fix also: flash a (compatible) stock Rom :good:
Click to expand...
Click to collapse
Thank you mate. I also found (5 sec before I read your post) this post here: http://forum.xda-developers.com/showpost.php?p=46969768&postcount=2
So, everything works now. The short version for other guys with the problems is:
- flash stock rom via Odin (PDA)
- you can find the stock rom for your country at sammobile.com
- also use the "pit-file" of the linked post (but I don't know, what the pit-file is changing?!)
optional:
- re-root your device again, because now it is not rooted
- new custom rom
Thanks for every help!!!
Robert
Try flashing ML6 Firmware and ML6 Modem (and Wi-Fi fix if needed), had the same issue but after doing so it's fixed.
Occured 1 time again, did a cache wipe didn't occur in 2days now.
Guller said:
Try flashing ML6 Firmware and ML6 Modem (and Wi-Fi fix if needed), had the same issue but after doing so it's fixed.
Occured 1 time again, did a cache wipe didn't occur in 2days now.
Click to expand...
Click to collapse
Except flashing the Wifi Fix was the thing I did to ruin it all. Don't flash a "new" Wifi fix using an old bootloader. You will lose sound/being able to make calls. It's the thing that messed it all up over here.
Pfeffernuss said:
Except flashing the Wifi Fix was the thing I did to ruin it all. Don't flash a "new" Wifi fix using an old bootloader. You will lose sound/being able to make calls. It's the thing that messed it all up over here.
Click to expand...
Click to collapse
I was already on the new bootloader.I've flashed Original FW, Modem + Wi-Fi fix and it fixed my phone. (Possibly also PIT but can't remember)
It can be that our problems were different but produced the same problem.. I'm not a dev nor do I understand everything about Android.
I can be wrong, but that's how I fixed my phone. Just trying to help
Just got my phone back from the repair shop and I seem to have messed up its ability to be a phone! Managed to restore a nandroid (seems it was still rooted) but the wifi / calls weren't working ...
The CSC code revealed with so I tried CSC changer from the shop and inadvertently made things worse ... I've ended up with a German CSC and can't get it back to BTU! (CSC changer goes through the motions but can't change it back )
So I thought I'd try to get back to the main problem, this longer 'CSC' number that gets displayed with *#1234# - it shows both my AP and CP as:
I9505XXUBMEA
But the 'CSC' here is:
I9505OXABMEA
I'm hoping if I can change that I'll be closer to get this phone working? Can anyone help? (NB it's on Android 4.2.2. right now)
Thanks! :laugh:
Damn, well, still pulling out my hair here. So far I've tried installing the same pre-rooted ROM that got me set up last time I rooted:
I9505XXUBMEA-PRE-ROOTED-ODEX-FULL.tar.md5
No wifi...
Then as I seemed to remember similar problems last time, the following files:
I9505XXUBMEA-MODEM.tar.md5 (via 'PHONE')
I9505XXUBMEA-WiFi-FIX.tar.md5 (via 'PHONE')
All go fine over ODIN, but I still have no WI-FI and the dialler goes blank if I try and make or receive calls! ><
Any help would be much appreciated..
Have you tried flashing the original stock firmware?
Sent from my GT-I9505 using Tapatalk
Not sure which one to use! Does it matter? Want to stay on 4.2.2 and keep life simple (seems 4.3+ complicates things) .. but I can't seem to find a 4.2.2 UK ROM (That's BTU, right?)
Can anyone point me in the direction of a stock ROM that I can flash to reset things?
Glad you got help in the other thread.
Sent from my GT-I9505 using Tapatalk
For sure all was ok before you restored ur backup. Dont restore more backups atm:
1. Make a backup of ur Internal Memory
2. Make a factory reset (Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.)
3. Conect it to Kies 3
4. Kies 3 will give u the info you need for know ur correct CSC. This will be btw parenthesis close CSC.
5. Knowing ur CSC, take a look for this firmware in Sammobile.com
6. Download and flash it with ODIN (Dont flash a "Black EDITION" if ur phone isnt it)
7. Dial *#1234# again and take a look if u have the same what Sammobile was telling you. If not, flash again the firmware. (Example in pic attached)
8. Attach more problems here if u still having them :highfive:
Thanks so much Joku. I've got to step 4 but it doesn't give me a lot of info. Offers firmware upgrade then says :
Current firmware: PDA:MEA / PHONE:MEA / CSC: MEA (DBT)
No idea what this means or how to find relevant firmware in step 5 so any advice would be much appreciated!
Cheers
Joku1981 said:
For sure all was ok before you restored ur backup. Dont restore more backups atm:
1. Make a backup of ur Internal Memory
2. Make a factory reset (Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device > Delete All/Erase Everything.)
3. Conect it to Kies 3
4. Kies 3 will give u the info you need for know ur correct CSC. This will be btw parenthesis close CSC.
5. Knowing ur CSC, take a look for this firmware in Sammobile.com
6. Download and flash it with ODIN (Dont flash a "Black EDITION" if ur phone isnt it)
7. Dial *#1234# again and take a look if u have the same what Sammobile was telling you. If not, flash again the firmware. (Example in pic attached)
8. Attach more problems here if u still having them :highfive:
Click to expand...
Click to collapse
Also do I know for sure this is the right (original) firmware? >< so much to learn!
jomtones said:
Also do I know for sure this is the right (original) firmware? >< so much to learn!
Click to expand...
Click to collapse
Yeah. You was right. It was very difficult to find coz is an old firmware. I give u the link of what i found: HERE
*EDIT: Continuing step 6:
- Download and unzip this firmware
- It will give ya 2 files. You can delete the .dll
- Put ur phone in DOWNLOAD MODE and conect it to ur pc
- Open ODIN and flash the firmware (like the example in pic attached)
- Wait the process till end and enjoy ur phone again like new
Many thanks for the link Joku! Downloading now, I'll let you know how it goes..
Damn, not having any luck with this file - I've tried downloading it twice now on different PC's but it fails to write - drops out after aboot.mbn then 'complete(write) operation failed'...
Joku1981 said:
Yeah. You was right. It was very difficult to find coz is an old firmware. I give u the link of what i found: HERE
*EDIT: Continuing step 6:
- Download and unzip this firmware
- It will give ya 2 files. You can delete the .dll
- Put ur phone in DOWNLOAD MODE and conect it to ur pc
- Open ODIN and flash the firmware (like the example in pic attached)
- Wait the process till end and enjoy ur phone again like new
Click to expand...
Click to collapse
So update... found I couldn't flash ANYTHING after the failed stock ROM flash, so I got a .PIT file and flashed that, now the phone boots again at least! Now downloading the Spanish stock ROM suggested by Malyrbu - http://forum.xda-developers.com/showpost.php?p=52635376&postcount=12236
One question - do these stock ROM files contain a kernel too? Might getting the right stock kernel help fix things?
Thanks!
jomtones said:
So update... found I couldn't flash ANYTHING after the failed stock ROM flash, so I got a .PIT file and flashed that, now the phone boots again at least! Now downloading the Spanish stock ROM suggested by Malyrbu - http://forum.xda-developers.com/showpost.php?p=52635376&postcount=12236
One question - do these stock ROM files contain a kernel too? Might getting the right stock kernel help fix things?
Thanks!
Click to expand...
Click to collapse
1. You dont need flash any Spanish stock ROM. Flash only the one I was telling you. I downloaded the DBT firmware and works perfect for me. OTHER LINK -> HERE
2. The firmware i told ya (DBT) contain STOCK Kernel too.
Weird, tried it a few times on different PC's now. Will try redownloading from your new link, thanks!
Joku1981 said:
1. You dont need flash any Spanish stock ROM. Flash only the one I was telling you. I downloaded the DBT firmware and works perfect for me. OTHER LINK -> HERE
2. The firmware i told ya (DBT) contain STOCK Kernel too.
Click to expand...
Click to collapse
*sigh* well I still couldn't get that stock ROM to flash... re-downloaded from your new link and ran it again, fails in the same spot! Not sure what's going on... might try that Spanish 4.2.2.? If it would fix my wifi problem I could then go ahead and add a custom ROM, right? :crying:
Well, Spanish ROM borks too! >< ... looks the same as the other one you sent. If it's any help, I can see in tiny red text on the S4 screen -
SW REV. CHECK FAIL : fused : 3, Binary : 1
Ah f*ck, I think I may have borked phone stock flashing by trying to install a higher firmware ROM when I first got the phone back... not sure but when I google the SW REV CHECK FAIL that seems to be the problem people have.
Dunno what's going on... when I get the phone to boot after flashing PIT again it says Android Version 4.2.2 in the 'About Device'... but I still can't get WIFI to work ><
If it was in warranty I'd take it back about now, sadly it's an ebay'd phone!
OK I think I may have sussed out why it's not working. Really sorry for the confusion but I think I screwed things up right at the start, and then didn't remember ... one of those dumb things you do playing with your phone late at night. The first ROM I tried to flash, right after getting it back from repair, was a 4.4.2! .... I had no idea what a big deal that was ><
SO ... thankyou for bearing with me this long! Feel like such an idiot right now. I guess then that some fundamental thing has gotten changed by the ROM I tried then (it was this one ). DOH!
As I understand it, there's no going back now and I'll have to stick with 4.4.2 - please correct me if I'm wrong!