Cannot flash BL or Modem - Galaxy S 5 Q&A, Help & Troubleshooting

Hi guys! I do have a Galaxy S5 SM-G900F,running latest Blisspop rom. I wanted to update the MODEM (Currently I have BOD3 on both modem and BL),but as the process finishes and phone restarts, BL and Modem are still the same. I already tried changing USB port and on another PC. Thanks!

Desactives kies if you ve installed it
& dont use Windows 8 because
you must adjust its parameters
By options in win8 reboot

yanis488 said:
Desactives kies if you ve installed it
& dont use Windows 8 because
you must adjust its parameters
By options in win8 reboot
Click to expand...
Click to collapse
Hi.
I do not have Kies Installed. I am using Win10 Pro.

Wolf80 said:
Hi.
I do not have Kies Installed. I am using Win10 Pro.
Click to expand...
Click to collapse
You can retry flash twice
like indicated on threads
Or changes with other usb cables
& other Os like xp win or w7
It is not ever easy so good luck
Man !

UPDATE: I tried flashing on Windows 7 with Odin 3.09 and 3.10.6,BL and Modem still wont flash. I am starting to think for problems related to NAND.

Related

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?

Kies problem

I've installed Kies but it won't run on my xp pro 64 bit. It did work before I updated to Gingerbread but since then ,nothing. Kies won't run,either with the phone connected or not. Think it's more a problem of the pc but can't find a solution online. I have tried uninstalling,rebooting and re installing both Kies and the USB drivers to no avail. Attached file of error when trying to run Kies. Kies did connect ok when I could get it running but now I can't even get it to run.
have you tried running as administrator ?? also what about running in compatibility mode ?
I have the same problem after rooting with the Fug-Mod method. Maybe it is the same reason for your problem.
Custom-ROMs are not supported by Kies.
Try to run Kies in compability mode. Then reinstall the drivers. After that it work without issues. Or just reinstall Kies.
Just tryed to start it via XP SP3 mode and, like every time i execute Kies, it works.
Device: Galaxy S @ Simply Honey 2.3.3 (JVB)
PC OS: Win7 x64 SP1
stepping said:
I have the same problem after rooting with the Fug-Mod method. Maybe it is the same reason for your problem.
Click to expand...
Click to collapse
Other people had this problem too. Reflash with stock firmware and use cf-root instead. Worked for me, even after flashing supercurio's kernel afterwards.
Sent from my GT-I9000 using XDA App
Kies does not like Win 7 x64 .
Latest version Kies only one i ever got to work .
jje
Liam Good said:
I've installed Kies but it won't run on my xp pro 64 bit. It did work before I updated to Gingerbread but since then ,nothing. Kies won't run,either with the phone connected or not. Think it's more a problem of the pc but can't find a solution online. I have tried uninstalling,rebooting and re installing both Kies and the USB drivers to no avail. Attached file of error when trying to run Kies. Kies did connect ok when I could get it running but now I can't even get it to run.
Click to expand...
Click to collapse
Thanks to Jjegan your solution is here> http://forum.xda-developers.com/showthread.php?p=13166133#post13166133
Update
I uninstalled all usb drivers,uninstalled Kies. Then I reinstalled Kies without connecting any cable or phone but I am still getting the exact same error message. Kies can't know I have my phone rooted or even which Rom I am using as I have not connected the phone but it still won't run. Any other suggestions welcome.

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..

[help] odin for windows 8 64 bit

guys,
i started using windows 8 consumer preview, but i have a problem now that odin 1.85 doesn't seems to detect mine phone. what could be the reason for that?? it doesnt shows any compatability issues. i had installed kies too. is there any work around for this problem??
Download android SDK, it has all google drivers..
I have that too. Win 8 is working fine with all versions of android sdk from 1.6 to 4.1 including api with juno.
Od there any thing else that i missed apart frm sdk.? Does updating kies will do any help?
try running it in compatibility mode
Use original Samsung USB cable to run Odin on Windows 8 and it will work!
jaison thomas said:
guys,
i started using windows 8 consumer preview, but i have a problem now that odin 1.85 doesn't seems to detect mine phone. what could be the reason for that?? it doesnt shows any compatability issues. i had installed kies too. is there any work around for this problem??
Click to expand...
Click to collapse
Use original Samsung USB cable to run Odin on Windows 8 and it will work!
jaison thomas said:
guys,
i started using windows 8 consumer preview, but i have a problem now that odin 1.85 doesn't seems to detect mine phone. what could be the reason for that?? it doesnt shows any compatability issues. i had installed kies too. is there any work around for this problem??
Click to expand...
Click to collapse
i have the same probleme with samsung galaxy i9000
you have to flash ur phone with another pc that have windows seven or xp

Samsung S4 Gt i9505 odin fail message

My samsung s4 GT i9505 was working on 4.3 os last from few days some error on display (Google stop service Like this ) i try to new Rom 4..4.2 by Odin
3.9,during installation Rom one Fail message on odin and after phone show on display phone Recovery mode with kies ,but my phone not connected with kies software.but phone going in downloading mode ,
please help me how can solve problem and how can Repair and which tool and Rom and other files use ?
atifmz said:
My samsung s4 GT i9505 was working on 4.3 os last from few days some error on display (Google stop service Like this ) i try to new Rom 4..4.2 by Odin
3.9,during installation Rom one Fail message on odin and after phone show on display phone Recovery mode with kies ,but my phone not connected with kies software.but phone going in downloading mode ,
please help me how can solve problem and how can Repair and which tool and Rom and other files use ?
Click to expand...
Click to collapse
Hi ,
Make sure Kies if totally off when flashing , download rom again , try once more
MAX 404 said:
Hi ,
Make sure Kies if totally off when flashing , download rom again , try once more
Click to expand...
Click to collapse
Kies i already uninstall from computer
atifmz said:
Kies i already uninstall from computer
Click to expand...
Click to collapse
First of all there is no need to use large bold format.
You did not mention that fact , try downloading rom again
MAX 404 said:
First of all there is no need to use large bold format.
You did not mention that fact , try downloading rom again
Click to expand...
Click to collapse
i try with 4 to 5 Rom all same this issue.i try with these Rom
I9505XXUGNE5_I9505OXAGNE5_I9505XXUGNE5_HOME.tar
I9505XXUEMKE_I9505OXAEMKE_I9505XXUEMKE_HOME.tar
I9505XXUEMK9_I9505EVREMK1_I9505XXUEMK9_HOME.tar.md5
I9505XXUGNE8_I9505VFGGNE2_I9505XXUGNE8_HOME.tar
always fail message
atifmz said:
i try with 4 to 5 Rom all same this issue.i try with these Rom
I9505XXUGNE5_I9505OXAGNE5_I9505XXUGNE5_HOME.tar
I9505XXUEMKE_I9505OXAEMKE_I9505XXUEMKE_HOME.tar
I9505XXUEMK9_I9505EVREMK1_I9505XXUEMK9_HOME.tar.md5
I9505XXUGNE8_I9505VFGGNE2_I9505XXUGNE8_HOME.tar
always fail message
Click to expand...
Click to collapse
Hi ,
Maybe something went wrong during flashing , check this thread , excellent guide to fix possible soft brick
http://forum.xda-developers.com/showthread.php?t=2265477
Almost all Odin errors can be resolved by the following:
- Different cable
- Different usb port
- Different pc.
- Try reinstalling the drivers (you can do this by reinstalling kies). Then make sure kies is not running in the background (alt+ctrl+del)
Lennyz1988 said:
Almost all Odin errors can be resolved by the following:
- Different cable
- Different usb port
- Different pc.
- Try reinstalling the drivers (you can do this by reinstalling kies). Then make sure kies is not running in the background (alt+ctrl+del)
Click to expand...
Click to collapse
Thanks,after Kies update driver Rom download perfect but now problem in Wifi not working ,How can fix ?

Categories

Resources