Don't you have to rename it and delete md5 in the file name? I had to with a .tar file on my girls sidekick
Sent from my SGH-T989 using Tapatalk
Sent from my SGH-T989 using Tapatalk
[STOCK] [ROM] T989UVKID [26.09.2011][Android 2.3.5] Tmobile
- Thread starter Przekret
- Start date
-
- Tags
- development
C
chib1panda
Guest
C
chib1panda
Guest
but original file inside the rar is .tar.md5 so it'll pickup md5 as its last extension and didn't Odin run with .tar only
Sent from my SGH-T989 using Tapatalk
There seems to be some uncertainty in this thread. If someone could clarify a couple of points it would really help the rest of us:
1) What exactly is this .tar.md5 file flashing? Is it a full back to stock, including ROM, Recovery, and Kernel? Or is it just flashing stock recovery and kernel?
A clear answer for 1 will likely answer this as well, but:
2) For those like me coming from a Vibrant, we are nervous about a "back to stock odin method" that doesn't include a .pit file. Is a pit file not necessary? Again, if the answer to the first question is that it flashes everything (ROM, Recovery, Kernel), then obviously there is no need for any other files. Simple clarification would be nice though. Thanks!
Well I seem to be having a problem getting this to flash properly. I first tried loading the package in .tar form in PDA using Odin 1.81 and as soon as it got to cache Odin failed. So I tried one more time and same result. So, I DL Odin 1.85 and re-DL the firmware package and try again using it as MD5 file. Well now after putting the phone into DL mode I get the phone-triangle-computer screen and a message telling me to recover the phone by syncing with Kies, and while I am reading the message I see Odin light up a com port so I hit start. Now Odin gets to cache and it keeps on flashing so I think OK it's working, but now I get the Windows error telling me Odin has stopped working. So, I try to flash it once again and the same results. I give up trying to get this to work.
So to get out of the jam I flashed clockwork with Odin to restore my OEM backup and thought I would have to pull the battery when it hung on the reboot...but it reboots just fine...all the OEM bloat is back along with Odex files (I was coming from the de-odex version.) I can also confirm that the Flash does not wipe as all apps and settings were the same. I did not play with it too much before I just went ahead and restored my OEM nan backup but everything seemed to be working even with 4 failed flash attempts.
It does flash the modem, recovery, kernel, and system, as well as cache. Mike said he flashed it OK a page or two back so it must work. I don't feel like forcing the issue on my phone right now but using these steps will be the way to do it.
1. Use Odin 1.85, and keep the .ini helper file that comes with it.
2. Leave firmware package as MD5 and put in PDA.
3. No .pit file needed.
---------- Post added at 12:33 PM ---------- Previous post was at 12:02 PM ----------
Also, I have owned two Vibrants and a Nexus S that have been flashed with Odin, by me, more times than I can remember. Along with a friends GS4G and Vibrant. So I probably have 500 flashes with Odin at least. Also back with one of my Vibrants doing DD commands and tarballing my own Odin packages. So I just wanted to say I am not a Odin noob. Odin is really a big reason why I stick with Samsung phones..along with that AMOLED display. I also would not have tried the .tar if I had read this thread since I posted last as it seems someone else posted a problem with it that way. I'll give it a few days and try re-flashing to see if it works.
I also reflashed stock recovery and kernel after my nan restore and then flashed clockwork back. So Odin is working with my phone.
So to get out of the jam I flashed clockwork with Odin to restore my OEM backup and thought I would have to pull the battery when it hung on the reboot...but it reboots just fine...all the OEM bloat is back along with Odex files (I was coming from the de-odex version.) I can also confirm that the Flash does not wipe as all apps and settings were the same. I did not play with it too much before I just went ahead and restored my OEM nan backup but everything seemed to be working even with 4 failed flash attempts.
It does flash the modem, recovery, kernel, and system, as well as cache. Mike said he flashed it OK a page or two back so it must work. I don't feel like forcing the issue on my phone right now but using these steps will be the way to do it.
1. Use Odin 1.85, and keep the .ini helper file that comes with it.
2. Leave firmware package as MD5 and put in PDA.
3. No .pit file needed.
---------- Post added at 12:33 PM ---------- Previous post was at 12:02 PM ----------
Also, I have owned two Vibrants and a Nexus S that have been flashed with Odin, by me, more times than I can remember. Along with a friends GS4G and Vibrant. So I probably have 500 flashes with Odin at least. Also back with one of my Vibrants doing DD commands and tarballing my own Odin packages. So I just wanted to say I am not a Odin noob. Odin is really a big reason why I stick with Samsung phones..along with that AMOLED display. I also would not have tried the .tar if I had read this thread since I posted last as it seems someone else posted a problem with it that way. I'll give it a few days and try re-flashing to see if it works.
I also reflashed stock recovery and kernel after my nan restore and then flashed clockwork back. So Odin is working with my phone.
Ok so after playing with some ROMs/kernels today I wanted to see if flashing this would work for me now...and it did. The only other thing I left out that you may need for this to work are the newer Samsung Galaxy USB drivers. You will also need to do a factory reset after Odin flashes because it only wipes cache after the reboot, and then you will be out of the box new again. It also takes about 7 min to flash.
Last edited:
i tried this last night because i messed up my phone some how...It would only boot into download mode.
So i started up odin and used this .tar
It failed 6x + at the same place everytime cache
So i unplugged phone replugged it back in (put me in odin mode)
Put the Stock Recovery.tar in pda and flashed
And this booted the phone.
So i started up odin and used this .tar
It failed 6x + at the same place everytime cache
So i unplugged phone replugged it back in (put me in odin mode)
Put the Stock Recovery.tar in pda and flashed
And this booted the phone.
I apologize for the double-post; I didn't realize that both threads were in the same sub-forum 
I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps to restore to stock:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!
I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps to restore to stock:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!
Last edited:
I just checked hotfile link was dead.
Could you re-upload stock ROM?
I'm DL'ing it now. Seems to be working fine.
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
15T989UVKID:
Code:# autogenerated by buildinfo.sh ro.build.id=GINGERBREAD ro.build.display.id=GINGERBREAD.UVKID ro.build.version.incremental=UVKID ro.build.version.sdk=10 ro.build.version.codename=REL ro.build.version.release=2.3.5 ro.build.date=Mon Sep 26 03:02:45 KST 2011 ro.build.date.utc=1316973765 ro.build.type=user ro.build.user=se.infra ro.build.host=SEP-42 ro.build.tags=release-keys ro.product.model=SGH-T989 ro.product.brand=samsung ro.product.name=SGH-T989 ro.product.device=SGH-T989 ro.product.board=MSM8660_SURF ro.product.cpu.abi=armeabi-v7a # Samsung Specific Properties ro.build.PDA=T989UVKID ro.build.hidden_ver=T989UVKID ro.build.changelist=594724 ro.product.cpu.abi2=armeabi ro.product.manufacturer=samsung ro.product.locale.language=en ro.product.locale.region=US ro.wifi.channels= ro.board.platform=msm8660 # ro.build.product is obsolete; use ro.product.device ro.build.product=SGH-T989 # Do not try to parse ro.build.description or .fingerprint ro.build.description=SGH-T989-user 2.3.5 GINGERBREAD UVKID release-keys ro.build.fingerprint=samsung/SGH-T989/SGH-T989:2.3.5/GINGERBREAD/UVKID:user/release-keys # Samsung Specific Properties ro.build.PDA=T989UVKID ro.build.hidden_ver=T989UVKID ro.build.changelist=594724 ro.tether.denied=false ro.flash.resolution=1080 # end build properties
Download:
http://hotfile.com/dl/135209606/7ce6b84/SGH-T989_TMB_T989UVKID.rar.html
Pass: sampro.pl3Well I seem to be having a problem getting this to flash properly. I first tried loading the package in .tar form in PDA using Odin 1.81 and as soon as it got to cache Odin failed. So I tried one more time and same result. So, I DL Odin 1.85 and re-DL the firmware package and try again using it as MD5 file. Well now after putting the phone into DL mode I get the phone-triangle-computer screen and a message telling me to recover the phone by syncing with Kies, and while I am reading the message I see Odin light up a com port so I hit start. Now Odin gets to cache and it keeps on flashing so I think OK it's working, but now I get the Windows error telling me Odin has stopped working. So, I try to flash it once again and the same results. I give up trying to get this to work.
So to get out of the jam I flashed clockwork with Odin to restore my OEM backup and thought I would have to pull the battery when it hung on the reboot...but it reboots just fine...all the OEM bloat is back along with Odex files (I was coming from the de-odex version.) I can also confirm that the Flash does not wipe as all apps and settings were the same. I did not play with it too much before I just went ahead and restored my OEM nan backup but everything seemed to be working even with 4 failed flash attempts.
It does flash the modem, recovery, kernel, and system, as well as cache. Mike said he flashed it OK a page or two back so it must work. I don't feel like forcing the issue on my phone right now but using these steps will be the way to do it.
1. Use Odin 1.85, and keep the .ini helper file that comes with it.
2. Leave firmware package as MD5 and put in PDA.
3. No .pit file needed.
---------- Post added at 12:33 PM ---------- Previous post was at 12:02 PM ----------
Also, I have owned two Vibrants and a Nexus S that have been flashed with Odin, by me, more times than I can remember. Along with a friends GS4G and Vibrant. So I probably have 500 flashes with Odin at least. Also back with one of my Vibrants doing DD commands and tarballing my own Odin packages. So I just wanted to say I am not a Odin noob. Odin is really a big reason why I stick with Samsung phones..along with that AMOLED display. I also would not have tried the .tar if I had read this thread since I posted last as it seems someone else posted a problem with it that way. I'll give it a few days and try re-flashing to see if it works.
I also reflashed stock recovery and kernel after my nan restore and then flashed clockwork back. So Odin is working with my phone.2
actually, the md5 file is for odin. i just finished flashing it. these are original factory images that take you back to 100% stock. these should at the very least be stickied, if they dont belong in the dev section. these files will save someones phone when theyre in a jam. op, thanks for posting this.
also, flashing this doesnt wipe data and it is odexed.11
Hmmm, the stock Odin firmwares for the Vibrant, Galaxy S 4G, and the Nexus S were all posted in the development section. If you want this in general section that's ok, but it would be nice to have conformity among the different device sections as it may lead to some confusion.
Thank you OP for posting this. I always like to have the ability to flash stock firmwares/recovery/kernel in one package with Odin.
