Related
So, yes before anyone tells me to read, Ive read the instructions on how to use Odin again and again. I downloaded Odin and the 64 bit usb drivers, i have a laptop running on windows 7. I put my phone in downloading mode and connected it to my laptop, but nothing seems to happen in Odin, no COM number, just nothing, I uninstalled the drivers and Odin and installed them once again, and i tried a different port...still nothing. I'm running on the leaked android 2.2.1, the phone is not rooted, just flashed with the update.
Any suggestions??....
Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Another idea... Try right clicking on Odin and running as administrator (not sure if this will effect anything, just throwing ideas out there).
Koadic said:
Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Click to expand...
Click to collapse
Yeah I bought another cable i know the one that comes with the phone is useless.
Will give a shot to the administrator idea and see what happens o.0,
thanks
The other thing is that you must put your phone in download mode, open ODIN and THEN plug in your phone. Aside from that, the USB thing is your best bet.
Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>
My last bit of advice would be to check in IRC at #samsung-epic the people there are very versed in using ODIN and are very helpful
monnie27 said:
Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>
Click to expand...
Click to collapse
I've had this issue before myself. I have two Windows 7 machines, both 64 bit. One would recognize my phone in download mode, and the other would not. I installed the correct drivers on both machines.
Make sure you are connected to one of the USB ports on the rear of the machine. Some people have had issues using the front USB ports.
ok thanks, I managed to get it to work somehow, i repeated the process od uninstalling and installing the drivers, Odin and somehow it worked this time. However i had Kies installed on the laptop, so i decided to uninstall it just for the heck of it ....and well after that, Odin recognized the phone o.0.
But thanks to all of you for the support ^_^
i would love to know the source of the x64 driver...as i found it to be a load of horsecrap
the driver found on the samsung website installs on both x86 and x64 machines in my experience
i was running windows server 2008 x64 at the time and only got the phone working with the driver directly from the samsung website
peoples long winded history of drivers and windows makes for a bad situation...at least be willing to try THE MANUFACTURERS option first
i bought my phone used...but it did come in the original box...
i just wasn't sure enough, then, to say that it is BS for a company like samsung not to distribute some kind of media/drivers with, or preloaded on, the device.
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
well..i got the drivers from this page:
http://forum.xda-developers.com/showthread.php?t=798067
and used BitZipper to extract them, it worked this time.
good news
enjoy dk28
it saved me from believing android was a suckers solution to windows mobile
my phone instantly locks gps now and the easy access to enabling 3g via the power button menu was nice
i am a believer...adb is my new god...reborn in code...blahblah...
actually i'm just glad something like a cellphone can simply work simply as it should
finally after billions of ages of fail
Well im actually having some problems with the gps navigation and lock. The location is not accurate, it was extremely accurate when i was running on 2.1 and i had no probs with neither of them. I saw a thread related to this issue before and ill see what can be done..
Sent from my SPH-D700 using XDA App
the only method that worked for me:
odin back to dI18 (.md5 extention removed/renamed to .tar extension)
get gps lock
odin dk28 modem (modem only) with victory_8G_100528.pit
gps lock again
odin dk28 (.md5 extention removed/renamed to .tar extension)
i actually didn't even try to get a gps lock after flashing the dk28 modem...
the key here seems to be performing the modem flash separately/first as there are multiple bootloaders working
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?
Ok guys I seem to have a problem
I tried to flash the new firmware through Odin, and it went through ok. Restarted back into Android, then went to flash a custom recovery.
When I tried flashing the recovery, it said there was a PIT error, so I got the i9505 PIT and tried to flash it with the firmware in Odin.
It won't flash at all, everytime I get to NAND Write Start, it says right after Complete(Write) Operation Failed.
Am I pretty much screwed here?
Also it says Write Protection Enabled in the Odin Mode.
Any help would be great!
I can still get in Download Mode, but when I try to turn on, it mentions Firmware Problem and connect to Kies
try to restore it using kies, if that works.
I think I've brought my phone back from the clutches of death.
I've managed to re-partition using a .pit file, and flash back to AME3. Recovery flashed fine too. It seems I can't flash the MEA, it just corrupts my PIT every time I try and flash it... So I think i'll stick with AME3
interesting, something like this should never happen
I have the feeling it was something else, not the ROM itself...
okty2k said:
interesting, something like this should never happen
I have the feeling it was something else, not the ROM itself...
Click to expand...
Click to collapse
I was thinking that myself.
I've never had problems flashing with Odin3 before, but saying that, i'm currently using my girlfriends Windows 8 x64 machine until I get a new laptop. To recover it, I used my dads Windows Vista laptop, and all flashed fine. Very strange.
Also does CSC matter? I'm in the UK, but Kies says my CSC is TGY, which is Hong Kong?
Brownie2k said:
I was thinking that myself.
I've never had problems flashing with Odin3 before, but saying that, i'm currently using my girlfriends Windows 8 x64 machine until I get a new laptop. To recover it, I used my dads Windows Vista laptop, and all flashed fine. Very strange.
Also does CSC matter? I'm in the UK, but Kies says my CSC is TGY, which is Hong Kong?
Click to expand...
Click to collapse
No for the CSC (as far as I know, at least).
It might have been the USB port you used. Also, if any Kies instance was still running, that can also lead to problems.
From what you wrote I think it was a problem with ODIN detecting the phone the right way...
okty2k said:
No for the CSC (as far as I know, at least).
It might have been the USB port you used. Also, if any Kies instance was still running, that can also lead to problems.
From what you wrote I think it was a problem with ODIN detecting the phone the right way...
Click to expand...
Click to collapse
I'm giving it another go on the Vista Machine.
Thing was, the MEA actually installed ok on this computer, but there was no WiFi, so I was going to install Philz CWM and clear data/cache etc. When I went to install the recovery, I got the error No PIT Information Found or something along them lines. From there, my problems really started. I can't understand why.
If it all works out well on the Vista machine, then I think it's safe to say that I won't be using Windows 8 to update my phone anymore.
I'll report back with any info.
Ok final update on this whole situation.
Using the Windows Vista laptop, I reflashed the pre-rooted MEA firmware. It all installed ok, no NAND Write Error, no fails.
Booted into Android, all seems fine. Wifi was working as expected.
Rebooted back into Download Mode, flashed Philz CWM Touch, failed first time, ran Odin3 as administrator and tried again.
Recovery flashed fine, no problems, no errors.
Rebooted into recovery, cleared cache, data.
Rebooted again into Android, finally setting up now.
All seems fine now, running MEA firmware, custom recovery
Hi
Read around XDA and other websites trying to solve my issues... no use.
hopefully im posting this in the right place, sorry if im wrong
SAMSUNG SM-G950FD
trying to root & unlock & TWRP my phone. REad all the steps, have all the different components.
Cant proceed because i cant get my phone to be detected by Odin.
Initially android transfer files wasnt recognizing phone so i figured hardware issue. changed the cable, port, removed smart switch app and removed all packages associated w/ ATF , and reinstalled android transfer file... phone was finally being recognized when plugged into mac.
now i tried running Odin through wine bottler - dont recognize device connected
tried Jodin - needed latest heimdall to run properly
I AM able to install heimdall latest version (incompatible for some reason, and im running OS Sierra 10.12.6) (all i have already is heimdall.frontend 1.4.0)
any tip to actually get Odin or Jodin to recognize and connect to my phone ?
thx
a
baddoor said:
Hi
Read around XDA and other websites trying to solve my issues... no use.
hopefully im posting this in the right place, sorry if im wrong
SAMSUNG SM-G950FD
trying to root & unlock & TWRP my phone. REad all the steps, have all the different components.
Cant proceed because i cant get my phone to be detected by Odin.
Initially android transfer files wasnt recognizing phone so i figured hardware issue. changed the cable, port, removed smart switch app and removed all packages associated w/ ATF , and reinstalled android transfer file... phone was finally being recognized when plugged into mac.
now i tried running Odin through wine bottler - dont recognize device connected
tried Jodin - needed latest heimdall to run properly
I AM able to install heimdall latest version (incompatible for some reason, and im running OS Sierra 10.12.6) (all i have already is heimdall.frontend 1.4.0)
any tip to actually get Odin or Jodin to recognize and connect to my phone ?
thx
a
Click to expand...
Click to collapse
I found heimdall.frontend.1.4.1 version somewhere randomly and tried it. fixed my issue. and Jodin recognized my phone.
enjoying my root
Hello,
I have an SM-G928I telstra branded, i've tried flashing a autorooting kernel and it bootlooped my phone, after this i've flashed twrp and wiped the system... so right now i am on MAC OS X, i use JOdin3 and i've tried flashing a lot of firmwares, but JOdin3 gets stuck on Running, and in the Messages Box nothing seems to go on, i think i might just use the phone as a door stopper right now, but you guys are my last hope, if you know how can i get out of this situation please help me.
P.S. Don't tell me to use Odin on Windows because i do not have access to a windows computer
I think only way is odin on windows
Yeah, only way is odin on windows because JOdin3 is way outdated.
rel0xzje said:
Hello,
I have an SM-G928I telstra branded, i've tried flashing a autorooting kernel and it bootlooped my phone, after this i've flashed twrp and wiped the system... so right now i am on MAC OS X, i use JOdin3 and i've tried flashing a lot of firmwares, but JOdin3 gets stuck on Running, and in the Messages Box nothing seems to go on, i think i might just use the phone as a door stopper right now, but you guys are my last hope, if you know how can i get out of this situation please help me.
P.S. Don't tell me to use Odin on Windows because i do not have access to a windows computer
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=20803
Have you tried this version ?
Get a virtual machine and install windows. Do it there. You can emulate windows on mac