Run the Odin3 v3.09.5
Connect with the Gear Fit (Target should be download mode)
Connect PC with the Gear Fit.
Check the COM Port from the ID:COM field of Odin3.
Install PC driver if you need.
Samsung_USB_Driver_for_Mobile_Phones_v1_4_9_0.exe
USB_CDC_Driver
Choose the binary of Gear Fit (Pit file included in CSC file : NB9)
BL: BL_R350XXU0AXXX_user.tar.md5
AP: AP_R350XXU0AXXX_user.tar.md5
CSC: CSC_OXA_R350XXU0AXXX.tar.md5
Screen from ODIN:
Error case:
Case 1 : The device is not rebooted automatically after downloading binary.
-> Press power button of Gear Fit over 7 seconds. (HW reset)
And then, check the S/W version of Gear Fit.
Case 2 : Odin3 download program can not find new Gear Fit device (COM port) after finishing download sequence.
-> Please restart Odin3 program.
Here is a good tutorial on youtube on how to do this.
http://www.youtube.com/watch?v=JTqvZgLwPJo
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
its possible to use this method for update gear fit for non samsung device?
the guide step this:
Find a S5 or Note 3 in a carrier store, best buy, or a friend.
Connect your Gear Fit to that device either by using the APK below or downloading it from the Samsung Store on that device
Go through the setup and update the Gear Fit.
Yes that step is mandatory becuase you can't update the Gear Fit using a non-samsung device.
Hi,
What sould i do, if odin stops at
/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> R350XXU0BNG2_R350OXA0BND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> font.bin
<ID:0/003> NAND Write Start!!
Can i unplug the gear fit, if the gear fit is doing nothing?
--------------
edit:
i did it with odin 3.09.3 from sam mobil, the last firmware BNG2, too.
only one tar.md5 file in AP-Mode selected
hi,
the firmware NG2 with the odin version from sammobile did not work for a ne5 build.
the gear fit is not brick, it works.
How do I get my Fit to stay in download mode? It's currently stuck in a bootloop, and drops right back out of download mode to start looping again.
Kelly
Samsung Galaxy Note 4 (Verizon)
Samsung Galaxy Note Pro 12.2
Gear fit Reboot loop FIX!!!
My gear fit started this loop and I couldn't figure out how to get it out of it. I use my gear fit ALL THE TIME, so I relentlessly pursued a proper fix. I followed this URL and Downloaded what I needed to and it all worked like a charm!! Make sure to get a good unzip program to properly unzip all files you need to download. With that being said, here is the fix!!
addictootech.com/manually-upgrade-samsung-gear-fit-via-pc-odin ( put a www -dot- in front of this site and copy and paste the url...since I'm a new user I can't post a link.
Hi I'm also suffering from the rebooting loop on my GearFit.
I also followed the instructions on .addictootech.com/manually-upgrade-samsung-gear-fit-via-pc-odin/
yet I failed again and again,
It's neither possible to connect my Galaxy S5 rightnow, nor to my PC
I downloaded Odin twice and make sure everything is done properly.
That's why I did everything more than twice. I'm geting the same message "all threads completed. (succeed 0/ failed 0)"
I tried all possible combinations like restarting my PC or reconnecting GearFit and even restarting ODIN.
Is there way that you can help me on that issue
Related
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nuld said:
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
vegeta1 said:
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
Click to expand...
Click to collapse
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Nuld said:
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Click to expand...
Click to collapse
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
clockcycle said:
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
Click to expand...
Click to collapse
Odin says "<ID:0/011> Added!!" (or some other port of course) whenever I connect the phone, doesn't that mean that it detected the phone?
I actually did the troubleshoot connection in Kies yesterday and it reinstalled the driver. I have since removed Kies (not the driver) from my computer, as I thought that this might be the reason why Odin fails.
Ok I am getting really desperate, I have spent a large part of the weekend trying to get this to work and still no luck. Any further suggestions would be highly appreciated
I have re-installed the USB driver a few times now and Kies is not installed to make sure that there are no conflicts between ODIN/Kies. I have also found a ROM for Vodafone NZ (I9300XXALE8_I9300VNZALE4_VNZ) which is where I got the phone.
ODIN detects when I plug the phone into my computer, but fails with the following:
<ID:0/011> Get PIT for mapping..
<ID:0/011>
<ID:0/011> There is no PIT partition.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What is the cause for this error and do I need a PIT file and do a re-partition to fix it?
Is it normal that when in download mode, the product name shown on the phone screen is empty?
Thanks!
Your partition table is corrupted. No point trying to fix.
Quickly send to samsung to reflash your phone.
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Nuld said:
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Click to expand...
Click to collapse
You are in a position now where further repairs by yourself are even more likely to end up with no warranty .
Phone broke during official update return under warranty .
Flashing other firmwares risks invalidating warranty .
jje
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
archeuscaine said:
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
Click to expand...
Click to collapse
Off the phone. Then press power button + volume up + home button
Sent from my GT-I9300 using xda app-developers app
Dear all there is a good news for all of you about SIII product name blank now it can be consider under warranty as Samsung policy.
I have a bricked Samsung Galaxy S2 and have been doing some research on how to fix this. There is a lot of info online, but I don't understand most of it as it is too technical and I need help having it translated into layman's terms!
Context:
- Galaxy S2 (GT-I9100)
- Unlocked
- Purchased from Kogan 2 years ago (no longer under warranty)
- Appears to be Polish stock based on the packaging and manual
- I am in Australia
Problem:
- Phone is stuck in boot loop, unable to get past the intro flash screen that says Samsung Galaxy S2 GT-I19100.
- It keeps resetting itself and going back to flash screen infinitely. I need to remove the battery in order for it to stop doing that.
- I'm unable to get into the mode that would allow me to do a factory reset, however I am able to get into download mode.
What I think I need to do, but need help verifying:
- Download Odin onto my PC. (I think Odin is software that allows me to access the core of the phone via my PC, is this correct?)
- Download the correct version of the operating system. From what I can gather, there are different versions depending upon which network you are with. Because my phone is unlocked, I need to get an unlocked version but I'm not sure whether I should get one designed for Australia or for Poland (or whether it matters)?
- Connect PC and phone via USB cable
- Turn on Odin
- Somehow use Odin to reinstall O/S on my phone
Questions:
- Are the steps above correct or am I missing something?
- Does it matter which version of Odin I install or can I just do a google search for Odin downloads?
- Where do I find the file I need to reinstall the O/S?
- Where can I find instructions on how to use Odin once I have the correct file to install?
Please help. Hopefully if I can document the instructions in a really simple way in this thread, it might help other technology illiterate people like me in the future.
BUMP (please )
milesindahouse said:
BUMP (please )
Click to expand...
Click to collapse
hi ... I found a guide that covers all your doubts .. You can access it here ... :good: :fingers-crossed: ... From next time, always search the forum before creating a new thread (or) asking a question ... almost all your doubts can be cleared with a simple search .. :cyclops:
Thanks for your response and the link to the tutorial. I have followed all of the steps and am getting a red FAIL.
Things I have tried are:
- uninstall and reinstall KIES (and Samsung drivers)
- different USB ports on same PC
- different USB ports on another PC
- different firmware files (I9100XWLSH_I9100XSALSA_I9100XXLS9_HOME.tar.md5; I9100XWLSJ_I9100XWXLS8_I9100XXLS7_HOME.tar.md5; I9100XWLSW_I9100XXMS2_I9100XEULS5_HOME.tar.md5)
- disabling anti virus software
- different USB cables (am currently using the default that came with the Samsung Galaxy S2)
- checking that KIES is not running (and confirming in task manager that there are no active processes)
- double checking that the correct options boxes are checked in Odin
- checked that the firmware files successfully downloaded (via WinRar)
My error log is as follows:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSJ_I9100XXLS8_I9100OXXLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to get stuck at the NAND write step every time I try. What does this mean? Am I using the correct firmware file?
I would really appreciate help. I feel like I am so close. Maybe I need a different type of firmware since it is a Polish phone being used in Australia? In the meantime, I am going to try installing a couple of different versions of Odin and seeing if that makes a difference but I would really appreciate any other ideas. Thanks in advance!!
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
I'm not a robot
dckmnn said:
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
Click to expand...
Click to collapse
Hey brother I also had similar problem today midnight here in india . and i also tried several methods to restore my phone.
i tried kies also but but it required full rom package to download ,as my internet speed is slow I tried other method and it worked. I am very happy now :victory:
just connect your GT-I9300 in download mode. use odin 3.07. download CF-Auto-Root-m0-m0xx-gti9300.tar.md5 file that we normally use for rooting. Select pda in odin select CF-Auto-Root-m0-m0xx-gti9300.tar.md5 and click start.
Its just recovery related problem. my entire data is there as it is in my phone.
Hit thanks If I helped you
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
dckmnn said:
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
Click to expand...
Click to collapse
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
homer timpson said:
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
That though is written in the sticky's.
homer timpson said:
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
Sorry for the late response! The phone wasn't able to enter recovery, only download mode.
Another not robot here
[UPDATE]
I sold the phone "as is", I got it cheap and sell it almost at the same price so any mod can mark this thread as "Solved".
Easy come, easy go they say.
Regards.
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
xdausernl said:
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
Click to expand...
Click to collapse
We have a whole section for this device as well as some modded stock ROMs, Kernels, Recoveries, etc.
https://r.tapatalk.com/shareLink?ur...&share_sfid=2401&share_fid=3793&share_type=sf
Sent from my LG-Q710AL using Tapatalk
Why reflashing stock ROM with Odin for SM-T210 Tab 3 WiFi repeatadly fail?
xdausernl said:
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
Click to expand...
Click to collapse
With the newest version of Odin flashing several ROM's, observe 'Get PIT for mapping' and 'PBL.bin' fail, there's no progres ... so it get stuck, more or less.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1397 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
With versions 1.87, 1.85 and 3.09 of Odin, observe 'Get PIT for mapping' and 'NAND write' fail, below the log I get:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210XXBNI1_T210PHNBNI1_T210XXBNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The stock ROM I seem to need for this device 'SM-T210, Tab3, 7.0, 8GB WiFi, has these specs: KOT49H, T210XXBOB1, PHN, build date Feb 3 2015, Android version 4.4.2
Kernel version: 3.4.5-4081557
I'm not sure about KitKat or Jelly Bean as both seem to have Android version 4.4.2.
So what's going wrong here?
No mather what stock ROM I try to get installed via Odin, any attempt does fail.
When I try to update via 'recovery' on the Samsung Tab3 from a stock ROM on an flash drive, installation will still fail.
Perhaps due to I once forget to uncheck 're-partitioning' in options before any change has been tried, and I've no idea of the concequenses.
Before, when connecting the Tab3 device to an computer, through the USB cable, I was able to browse the Tab3 content.
But after that incident, I seem to have no longer access to the Tab3 device from a (Windows) computer.
So far, I haven't been able to find how to recover from this, or a manual how to get an functioning Tab3 back.
Please help!