I finally managed to upgrade SGS firmware through Kies because I found a solution on how to connect Kies to Samsung Galaxy S. The solution is quite long though, but the end result is worth it. I now can connect Kies to SGS successfully all the time.
I live in Indonesia, bought the phone from a gadgets store. The phone is unlocked/sim free/unbranded.
The original firmware code (dial *#1234#):
PDA: I9000DXJF4
Phone: Unknown <-- what the ??
CSC: I9000OLBJF4
And this is what I've done:
Downloading and installing Kies from Australia instead of Indonesia. The version number is higher 1.5.1.10083. The important 64-bit drivers already included. Installed smoothly on Windows 7 Ultimate 64-bit, but had driver problem in Windows Vista Home 32-bit. I don't bother to try to reinstall Kies in Vista again though, so I don't know if this version is really not working in Vista 32-bit. UPDATE: This version is working in Vista 32-bit and Win7 64-bit!
Press/dial *#272*HhMm# (Hh and Mm is hour and minute in 24H format, 2 digits) then select the code from the list equal to "Sales Code" at the top, which is XSE (Indonesia), and press Install. Warning, this step will erase the internal SD card. Make backup first if you must.
After the installation from step two is completed, the phone will reboot itself. To make sure that everything is still working (no more downloaded Applications or Contacts though, everything was wiped out), I did reboot the phone once again. The phone works normally. But my phone type was still "Unknown" at this point.
Without changing any setting in the phone and Kies, I connect the USB to the phone, Kies fired up automatically, and voila! My phone was detected, and Kies also gave me a notification that a new firmware is available (I9000DXJG4). So, I downloaded and applied the firmware.
New firmware installed successfully. Works better and faster/smoother than DXJF4. GPS is much better now. Love it. Dial *#1234# gives me this now:
PDA: I9000DXJG4
Phone: I9000DXJG4 <-- yay!
CSC: I9000OLBJG4
In this firmware, Samsung also includes an application/widget called "Task Manager", which is pretty much like those "Task Killer" apps in the market.
And now, The Buts!
YouTube (APK) is not working. In JF4 it worked well.
Android Market now can't download every item I selected, but it can show the list normally. I did login successfully using my Google account.
Samsung Kies detected the phone but now giving me this warning "The SIM card is not inserted, can continue communication". The SIM card is inside the phone!
Samsung Kies really gives me a headache, literally. Old problems fixed, new problems arise. Anyone knows how to solve that three problems? Please?
Or, should I redo the *#272*HhMm# procedure once again after installing the new firmware?
Did some experiment and it was a success.
So, I did a Factory Reset. All caches and some data are gone, but all downloaded applications and contacts are still intact. YouTube (APK) is now working and I can access Android Market again. The big downside: My phone type is back to "Unknown"!
Next, I dialed *#272*HhMm# again, let the phone reboot and setting up itself. And voila! The phone type is back to normal again "I9000DXJG4".
YouTube app and Android Market is still working normally. I haven't try to connect the phone to Kies though.
I read somewhere in xda-developer forum that after upgrading (and downgrading maybe?) the phone firmware you need to do a Factory Reset first, so you need to backup your data before upgrading/downgrading.
I think that's the answer of my question above. And dialing *#272... completes the whole process in my case.
My impression of JG4? It's fast and responsive. It's a great piece of firmware.
KIES recognize Galaxy S without problem!
Well, the fix I've listed above work very, very well!
Kies now will recognize the phone correctly. And I can make backup of my contacts or upgrading the firmware through Kies.
I'm very happy with Samsung Galaxy S and Kies now!
awright. gotta try this trick )
hello fellow indonesian )
Hello there!
I have written the guide above in this website: http://lintascafe.com/2010/09/14/ulasan-samsung-galaxy-s-part-2/
tupique said:
I finally managed to upgrade SGS firmware through Kies because I found a solution on how to connect Kies to Samsung Galaxy S. The solution is quite long though, but the end result is worth it. I now can connect Kies to SGS successfully all the time.
I live in Indonesia, bought the phone from a gadgets store. The phone is unlocked/sim free/unbranded.
The original firmware code (dial *#1234#):
PDA: I9000DXJF4
Phone: Unknown <-- what the ??
CSC: I9000OLBJF4
And this is what I've done:
Downloading and installing Kies from Australia instead of Indonesia. The version number is higher 1.5.1.10083. The important 64-bit drivers already included. Installed smoothly on Windows 7 Ultimate 64-bit, but had driver problem in Windows Vista Home 32-bit. I don't bother to try to reinstall Kies in Vista again though, so I don't know if this version is really not working in Vista 32-bit. UPDATE: This version is working in Vista 32-bit and Win7 64-bit!
Press/dial *#272*HhMm# (Hh and Mm is hour and minute in 24H format, 2 digits) then select the code from the list equal to "Sales Code" at the top, which is XSE (Indonesia), and press Install. Warning, this step will erase the internal SD card. Make backup first if you must.
After the installation from step two is completed, the phone will reboot itself. To make sure that everything is still working (no more downloaded Applications or Contacts though, everything was wiped out), I did reboot the phone once again. The phone works normally. But my phone type was still "Unknown" at this point.
Without changing any setting in the phone and Kies, I connect the USB to the phone, Kies fired up automatically, and voila! My phone was detected, and Kies also gave me a notification that a new firmware is available (I9000DXJG4). So, I downloaded and applied the firmware.
New firmware installed successfully. Works better and faster/smoother than DXJF4. GPS is much better now. Love it. Dial *#1234# gives me this now:
PDA: I9000DXJG4
Phone: I9000DXJG4 <-- yay!
CSC: I9000OLBJG4
In this firmware, Samsung also includes an application/widget called "Task Manager", which is pretty much like those "Task Killer" apps in the market.
And now, The Buts!
YouTube (APK) is not working. In JF4 it worked well.
Android Market now can't download every item I selected, but it can show the list normally. I did login successfully using my Google account.
Samsung Kies detected the phone but now giving me this warning "The SIM card is not inserted, can continue communication". The SIM card is inside the phone!
Samsung Kies really gives me a headache, literally. Old problems fixed, new problems arise. Anyone knows how to solve that three problems? Please?
Or, should I redo the *#272*HhMm# procedure once again after installing the new firmware?
Click to expand...
Click to collapse
were u able to use 3 button combo after that?
My fix
Whenever my SGS is no longer seen by Kies (Win7 x64):
Close Kies and the tray icon
Stop Kies mode on the phone
Disconnect phone
Connect phone
Put phone in Kies mode
Wait for Win7 to settle
Go into Windows Device Manager
Delete the phone from "Mobile Devices" (you may even see it with an "!" icon which is what put me onto this method)
Stop Kies mode on the phone
Disconnect phone
Run Kies
Connect phone
Put phone in Kies mode
Windows then re-detects the phone and after a short while so does Kies.
Hasn't failed yet.
anonymusneo said:
were u able to use 3 button combo after that?
Click to expand...
Click to collapse
Lucky for me, the 3 button combo problem is not an issue for my hardware. Before I finally "found" those steps above, I once used a 3 button combo step to fix KIES problem as said in this forum or other forum, I forgot.
The 3 button combo problem is related to defective hardware rather than firmware I guess.
Taomyn said:
Whenever my SGS is no longer seen by Kies (Win7 x64):
Close Kies and the tray icon
Stop Kies mode on the phone
Disconnect phone
Connect phone
Put phone in Kies mode
Wait for Win7 to settle
Go into Windows Device Manager
Delete the phone from "Mobile Devices" (you may even see it with an "!" icon which is what put me onto this method)
Stop Kies mode on the phone
Disconnect phone
Run Kies
Connect phone
Put phone in Kies mode
Windows then re-detects the phone and after a short while so does Kies.
Hasn't failed yet.
Click to expand...
Click to collapse
From my experience, whenever KIES can't detect my SGS, it also means that the IMEI number in my SGS is gone and listed as Unknown. KIES needs IMEI number to be present.
The source of my IMEI problem is quite surprising: the One Click Lag Fix. Whenever OCLF is activated, IMEI number is listed as Unknown, and KIES can't find the phone, and vice versa.
However, I'm quite sure that my problem with OCLF and the missing IMEI number is not a common problem, because there were no reports about this in XDA forums.
tupique said:
From my experience, whenever KIES can't detect my SGS, it also means that the IMEI number in my SGS is gone and listed as Unknown. KIES needs IMEI number to be present.
The source of my IMEI problem is quite surprising: the One Click Lag Fix. Whenever OCLF is activated, IMEI number is listed as Unknown, and KIES can't find the phone, and vice versa.
However, I'm quite sure that my problem with OCLF and the missing IMEI number is not a common problem, because there were no reports about this in XDA forums.
Click to expand...
Click to collapse
Hi!
I just have the same problem.
Did you find a solution for it?
Thanks,
vrehenriqu said:
Hi!
I just have the same problem.
Did you find a solution for it?
Thanks,
Click to expand...
Click to collapse
LOL, i have the same problem! any fix yet?
Thanks!!!!
A TURKISH MAN CAN SOLVE!
Problem:
When I connect device to computer, update notification appears for 2.2.1. However, when I click on update after skipping or non-skipping backup, device disconnects and notification appears that device not connected. Then, clicking on OK update process ends but my galaxy s is connected to KIES. I tried numerous times.
Full error message: Firmware update stopped because GT-I9000 has been disconnected. Please check the connection and try again.
I tried those:
Updating KIES
Hard reset device
Uninstall & reinstall KIES
Open KIES as admin
Open KIES in compatibility mode
Restart phone
I also tried Win7 32 bit,XP and XP virtual PC
Alcohol cleaning of all ports
Solution:
Go to your control panel, find region and keyboard settings. Then make all your settings as English (U.S.A). At last tab, computer will restart. Open Kies as admin and in compatibility tab select windows xp service pack 3. Update will be found as usual. Go for it. Your connection will be lost but the firmware is downloading this time. Update will be finished without no problem.
Thank me in advance because it will definitely work
It works also for Bada.
Photographs are in Turkish because Turkish people solve this problem with hard work. However, you can figure out from the context.
Link for photographs: http://www.maxicep.com/bada-os/kies...leyemeyenler-icin-resimli-anlatim-469728.html
Turkish people forget Kies not work for USA users with those settings already .
jje
JJEgan said:
Turkish people forget Kies not work for USA users with those settings already .
jje
Click to expand...
Click to collapse
I am not underestimating other solutions. I truly believe other solutions still apply to those including driver install/reinstall, admin mode,compatibility mode, using win7 32 bit or XP, cleaning with alcohol etc.
i've heard problem when update via kies on win7 32 bit. is it true?
iCatchU said:
i've heard problem when update via kies on win7 32 bit. is it true?
Click to expand...
Click to collapse
That is correct
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
http://forum.xda-developers.com/showthread.php?t=1280097
Please read my problem I have encountered and how I have solved, hope this helps.
After step 6 while trying to install Mango I recieve error code 801812c1.
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
theonlyremedy said:
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
Click to expand...
Click to collapse
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
alodar1 said:
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Click to expand...
Click to collapse
Called Dell Mobility. Even though I could restore back to previous version, they offered to replace the device, which I took.
Kind of sad though, I've never had problems with wifi or anything else on this phone. In fact the only problem ever with a VP was me dropping the thing. I'm hoping the refurb I get will also not be a problem.
alodar1 said:
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
Click to expand...
Click to collapse
Thanks alodar1..
I asked Dell to do a service and added that I don't need an replacement. The service guy said the phone is new and they are not trained to service this, so they would only do a replacement. I'm not ready to do a replacement, they ask me to go for international warranty, moreover they replace with factory refurbished phones.
BTW, I would like to know if there is anyway to format the memory card without removing or replacing. Right now I have another problem whenever I press the power button to boot my phone it directly goes to Software Download mode, the camera button was never pressed.
While trying to repair using Windows Phone Tool, I received this error "The tool cannot recover this phone, please contact technical support", so being a little curious I fired up .NET Reflector and loaded the tool to find out what was happening, I found that the this error is thrown if the phone is not Samsung made (see attached file). Is there any similar tool for Dell Phones?
*UPDATE 1* Is there anyway to force flash without using Zune, any third party tool, Zune seems to go to restore mode and can't find my phone. I have a feeling that erasing the contents of SD card will solve the problem.
*UPDATE 2* I did the registry trick and was able to see my DVP in Computer window. But instead of one DVP, I see 2 and both have storage of 3.75 GB each. But my DVP is 16GB, both DVP are empty. Previously I was never able to see my DVP even after registry patch. Now I have feeling that corrupt drivers caused the problem, yesterday I completely removed and reinstalled Zune Software, now the registry patch worked.
Please let me know with problem my DVP could be hardware fault or just the software. If its hardware then I'll go for replacement right away.
Just recieved my replacement VP. Ordered yesterday around noonish. Went downstairs to get the Motorola Xoom box that was delivered...and the VP was there too. Bonus....
Did not come with Mango....but....there's not a scratch on this thing....not a rub, not a bump...nothing. Still has plastic in places I doubt they would put plastic after refurb. I'm wondering if I got one of hte left over new ones....
Doesn't matter....Mango won't install no matter what...so...maybe I'll try ICS.
My Mango is now Ripe..
alodar1 said:
My Mango is now Ripe..
Click to expand...
Click to collapse
Nice to hear that!
alodar1 said:
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
Click to expand...
Click to collapse
How do you flash it back to 7392? I need to flash mine.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
not a flash, but a restore. I've always made copies of my backups ...
You an't reflash as the user above me already said, that said, the backups are stored in
=> %userprofile%\AppData\Local\Microsoft\Windows Phone Update
so for backing up your restore poiints you can copy that folder and then keep it.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
I was just curious. I wanted to fix my phone. The backup restore didn't work. I was just looking for some way to flash it or at least format the SD Card, so that I reinstall OS and can get my phone working. After four days of trying to fix my phone, I finally gave up and sent it for service to Dell. I even copied a little bit of code from phone support tools and tried them, I was just able to get the phone details without any problem, Mango was installed in the phone, but still it didn't boot. It would be good if we find a way to touch the SD card and format it from PC, probably we'll be able to revive many bricked phones. I would be happy to join the project if some one starts it. I can write C# code.
Mine is an error during backup
Error Code 801812DC during backup
I also add new thread.
If anyone knows, please tell me what I need to do.
Is Kies once the firmware it becomes addable on Kies does it fix everything like Kernel and restore it to factory when you bought the device...
Is this the safeist method?
animeware said:
Is Kies once the firmware it becomes addable on Kies does it fix everything like Kernel and restore it to factory when you bought the device...
Is this the safeist method?
Click to expand...
Click to collapse
I use this metod on all my samsung devices. Unfortunetly there is not avalable software for S4 as of now on samsung servers. We need to wait and i think developers will get faster then samsung stock software.
You can use Kies to restore you software. I just check and they added galaxy S4 firmware to server. Here is how : http://forum.xda-developers.com/showthread.php?t=1984717
norbarb said:
You can use Kies to restore you software. I just check and they added galaxy S4 firmware to server. Here is how : http://forum.xda-developers.com/showthread.php?t=1984717
Click to expand...
Click to collapse
Your method works the best!!! On the S4 though, plug in the phone and then start the firmware restore....
Awesome! This was extremely easy to do. Once Kies was connected, the only thing I had to do was tell it to update the firmware. I didn't have to give it my serial or model number or put my phone in "download" mode or anything. It took care of all of that automatically.
Here's a link to the desktop Kies client. You can simply use the USB cable, you don't even have to run Kies on your phone for it to work.
ht tp: //ww w.samsung. com/us/kies/
I accidently deleted touchwiz before I installed another launcher, and it apparently didn't like that very much. Even a hard reset didn't straighten it out, but this did the trick! It does look like I'm going to have to re-root it though.
Also, wiping it appears to have smoothed a lot of the lag out. It's still not 100% perfect, but it does seem quite a bit smoother, and it appears to have completely taken care of the super-lag that was being caused by the keyboard in landscape mode.
I'll try to document everything I install or change, to see if there's something that triggers the lag. Hopefully it will just stay this way.
So glad it helped you out! All thanks to Norbarb for the method and idea.....
Hi,
I have a carrier branded s10+, in Europe, with no simlock. I have tried to flash an open market firmware with Odin but it fails. After clicking start fails immediately without doing anything to the phone.
I have previusly removed the Samsung account to turn of FRP as I always did when flashing.
What could be the problem? The fingerprint having the phone encrypted? I will eventually factory reset and try to flash it with no initial setup being done, but I kinda want to avoid a factory reset if it won't make a difference.
This is not the first time I use Odin, but this problem is new to me.
Add a screenshot of Odin when the error occurs.
mmuntean2 said:
Hi,
I have a carrier branded s10+, in Europe, with no simlock. I have tried to flash an open market firmware with Odin but it fails. After clicking start fails immediately without doing anything to the phone.
I have previusly removed the Samsung account to turn of FRP as I always did when flashing.
What could be the problem? The fingerprint having the phone encrypted? I will eventually factory reset and try to flash it with no initial setup being done, but I kinda want to avoid a factory reset if it won't make a difference.
This is not the first time I use Odin, but this problem is new to me.
Click to expand...
Click to collapse
you will probably need to use a modify version of odin https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657 2nd post
Found the solution. after removing the Samsung account, disabling encryption on the phone and disabling Find my phone from device managers, I enabled OEM Unlocking. Flashing worked with no issues after this.