I tried flashing my s4 back to stock using odin but i instead got a "Firmware upgrade has encountered a problem. connect to kies" error message. I keep trying to flash my s4 using odin but i keep getting this error. Help please!
lrdmg said:
I tried flashing my s4 back to stock using odin but i instead got a "Firmware upgrade has encountered a problem. connect to kies" error message. I keep trying to flash my s4 using odin but i keep getting this error. Help please!
Click to expand...
Click to collapse
Probly the Knox counter. From what I've heard if you flash anything including a stock file with no mods it trips it. No positive if this applies to you but read this link: http://omegadroid.co/wanted-knox-void-warranty-0x1/
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Did you do a full wipe before you connect to Odin and once connected to Odin tick nand erase all.
Sent from my SGH-M919 using XDA Premium 4 mobile app
lrdmg said:
I tried flashing my s4 back to stock using odin but i instead got a "Firmware upgrade has encountered a problem. connect to kies" error message. I keep trying to flash my s4 using odin but i keep getting this error. Help please!
Click to expand...
Click to collapse
I'd suggest you reinstall the samsung USB drivers.. I have the best luck reinstalling from KIES. Looking at your pic I don't see the device detected-- should be listed in one of the two rows below your "FAIL" -- its not seeing your device yet. Should say "COM1:" or something there if memory serves..
I fought doing this for a couple days from within a Windows VM on mac (running VMware fusion) and it was a total bust, had to run odin from a PC in the end (bootcamp on the mac but thats another story) and it never actually saw my device-- looked just like what you have until I got the drivers running.
Related
Hello,
Let me start off by saying if this is the wrong place to post this please inform me of the right forum.
I just recently got a Samsung Galaxy SIII (on August 29) and everything was working really well, until today. Yes it is rooted. I plugged the phone into my computer and Kies said there was a firmware update for my phone. I began doing the upgrade and my beloved windows computer got the blue screen of death during the actual update process.
After restarting my computer, I began to do the update recovery to continue with my upgrade. Same blue screen. I spoke to a rogers tech rep and he requested I re-install my Kies software, which I did. Upon having no success from that I began to do more research, however most of them are saying to reflash the stock firmware (which I have) using ODIN. I have no success here as well. Every time i do get into download/recovery mode, ODIN recognizes my phone, but fails when i click start.
In my recovery mode the information i see is as follows:
ODIN MODE
PRODUCT NAME: SGH-1747M
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOM SECUREBOOT: ENABLE
Is there anything at all I can do to fix this? Or am I one of those most unfortunate people who just got screwed lol.
ANY assistance is VERY MUCH appreciated!
Thanks in advance
If you have clockwork recovery, try formatting the system first then flash the ROM. Just dont reboot without flashing the ROM first.
Have you tried the emergency firmware load through KIES?
Sent from my SGH-I747M using xda app-developers app
cue_32 said:
If you have clockwork recovery, try formatting the system first then flash the ROM. Just dont reboot without flashing the ROM first.
Have you tried the emergency firmware load through KIES?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thank you for the quick reply! sorry for my late one, just got home from a family emergency...
no I don't have CWM.. I'm very familiar with it though I didn't put it on my SIII (i was planning to do so tonight)
I've tried the emergency firmware, however it asked for a code which I don't have :S
I'm new to Samsung's version of Android, previously I owned an Xperia X10
Try running Odin on a different computer
If you're using a desktop use the usb ports on the back Odin don't like the usb hub on front, or try different computers, I have one computer that Odin will never work on but I go right to my other one and works fine, try restarting pc or uninstall Odin and download a different version, also try downloading a few different roms try these below, I've been in that position then finally after trying and trying a Rom will finally take
http://forum.xda-developers.com/showthread.php?t=1739426
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
rob1216 said:
If you're using a desktop use the usb ports on the back Odin don't like the usb hub on front, or try different computers, I have one computer that Odin will never work on but I go right to my other one and works fine, try restarting pc or uninstall Odin and download a different version, also try downloading a few different roms try these below, I've been in that position then finally after trying and trying a Rom will finally take
http://forum.xda-developers.com/showthread.php?t=1739426
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
that worked!!!!!!!!! thank you, i just changed the USB port lol.. its always something so simple you wouldn't think to do it initially!
thanks so much!
I have a T-Mobile Galaxy S3 and I'm trying to go back to stock or any rom at this point. I've tried Odin 3.04/3.06/3.07 and it keeps failing and on the phone it says "Unsupported dev_type". I've tried 3 different file types, two fail almost immediately and one goes all the way to the end and then says FAIL. My Custom Binary Download now is up to count 6. At this point I'm not too sure what to do. Any help would be appreciated guys, thanks!
Maisum said:
I have a T-Mobile Galaxy S3 and I'm trying to go back to stock or any rom at this point. I've tried Odin 3.04/3.06/3.07 and it keeps failing and on the phone it says "Unsupported dev_type". I've tried 3 different file types, two fail almost immediately and one goes all the way to the end and then says FAIL. My Custom Binary Download now is up to count 6. At this point I'm not too sure what to do. Any help would be appreciated guys, thanks!
Click to expand...
Click to collapse
Did you reflash stock recovery first, then Odin the ROM?
I always do that to avoid issues. Also, which stock ROM are you trying to flash?
Your counter shouldn't trip if you're flashing stock. Are you using the stock cable from your phone? Also, try flashing root66 file first, then triangle away, then stock.
Sent from my SGH-T999 using xda app-developers app
could always flash a stock rooted Rom and hide super user in a folder
Sent from my SGH-T999 using xda premium
Maisum said:
I have a T-Mobile Galaxy S3 and I'm trying to go back to stock or any rom at this point. I've tried Odin 3.04/3.06/3.07 and it keeps failing and on the phone it says "Unsupported dev_type". I've tried 3 different file types, two fail almost immediately and one goes all the way to the end and then says FAIL. My Custom Binary Download now is up to count 6. At this point I'm not too sure what to do. Any help would be appreciated guys, thanks!
Click to expand...
Click to collapse
What exactly are you trying to flash in odin?
Sent from my SGH-T999 using xda app-developers app
So as an update, I tried the root66 one, it went through all the way but it's stuck at the samsung screen. It doesn't boot loop per say, it loops the animation but doesn't turn off and on like a boot loop would. I'm going to try another time and see if it will work. I also decided if this wasn't going to work to try UVALJ4 from here.
Can I get links to things I should try? I understand I can search for it but then there's always different versions and different carriers. Thanks for all the help guys!
Did you factory reset?
I suggest getting all your fw from that thread!
Sent from my SGH-T999 using xda app-developers app
allright i just got a S3 sgh-i747m and i wanted to root it. i have alot of experience with jailbreaking apple devices but this was my first android product. and ofcourse i messed up. i used a root for a different model of my phone (the international version) and not i am stuck at the "firmware upgrade encountered an issue, please select recovery mode in kies and try again", so i tried that, and kies will not pick it up. so now i ask., what can i do to make this thing go back to normal?, i dont mind if i have to wipe the thing. please let me know here asap
sorry
allright guys, this would be really appreciated asap. sorry.
I have the same model and I encountered the issue my self. Just download the stock rom and download odin 3.07 and using odin update to the stock rom, If you want the links to stock just go to http://www.sammobile.com/firmware/?page=3 and select your device and download the firmware.
mrmicc said:
allright i just got a S3 sgh-i747m and i wanted to root it. i have alot of experience with jailbreaking apple devices but this was my first android product. and ofcourse i messed up. i used a root for a different model of my phone (the international version) and not i am stuck at the "firmware upgrade encountered an issue, please select recovery mode in kies and try again", so i tried that, and kies will not pick it up. so now i ask., what can i do to make this thing go back to normal?, i dont mind if i have to wipe the thing. please let me know here asap
Click to expand...
Click to collapse
I wish the XDA team was here to help you. I'm new to the android lifestyle also. I was a bug apple fan and switched like you.. Sorry I can't help.
Samsung Galaxy S3 i717 (AT&T) - Rooted - C10 Mod
thankyou
DaveenJay said:
I have the same model and I encountered the issue my self. Just download the stock rom and download odin 3.07 and using odin update to the stock rom, If you want the links to stock just go to and select your device and download the firmware.
Click to expand...
Click to collapse
thank you very much. when i made the mistake i was running oden 1.85, should i use that to fix the problem also? or update for the fix?
mrmicc said:
thank you very much. when i made the mistake i was running oden 1.85, should i use that to fix the problem also? or update for the fix?
Click to expand...
Click to collapse
Don't use 1.85. It's incompatible with this. Update.
Sent from my SGH-T999 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1739426 follow instructions here
Sent from my SAMSUNG-SGH-I747 using xda premium
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
NYCguy2020 said:
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
Click to expand...
Click to collapse
If you can still get into Odin mode, there's still hope. Have you tried using Odin to flash a stock image instead of Kies?
NYCguy2020 said:
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
Dont use Pit thats why Use pda
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
Click to expand...
Click to collapse
Don't use and dont need pit file.
Find the stock shipped tar file (aka) 4.1.2 Rom
Load in pda leave everything checkedbin odin thats checked.
Rooting isnt hard at all just got my s4 3 hrs ago rooted in 5 minutes soon as I walked in the door.
You need the Root_m919uvuamdl.zip
And then flash MDB setUIDoff .zip
Then flash superuser.
Thats it.
If u have odin Booted its 1000% NOT BRICKED
Sent from my SGH-M919 using xda app-developers app
lojak29 said:
Don't use and dont need pit file.
Find the stock shipped tar file (aka) 4.1.2 Rom
Load in pda leave everything checkedbin odin thats checked.
Rooting isnt hard at all just got my s4 3 hrs ago rooted in 5 minutes soon as I walked in the door.
You need the Root_m919uvuamdl.zip
And then flash MDB setUIDoff .zip
Then flash superuser.
Thats it.
If u have odin Booted its 1000% NOT BRICKED
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Had that and tried flashing it thru Odin several times and I keep getting the same error message. "there is no PIT partition"
Let me ask you one thing. .. is the com port in odin coming up recognize the phone ...if so you are not bricked. . The two vital things u need to see is com port turn on usually blue color and download mode..
The problem def lies somewhere else possibly bad tar file .
Try to find another source for the stock rom tar file another option is boot into recovery and flash a stock rom if you have recovery still
Sent from my SGH-M919 using xda app-developers app
Change cable, change PC, download latest Odin version, and reflash stock TMO ROM
Yes cable and USB port can affect Odin's ability to flash
Sent from my Nexus 7 using Tapatalk 4
Gunkk said:
Yes cable and USB port can affect Odin's ability to flash
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks guys. Finally got it resolved. Rooted and rocking Wicked V5.1
Id at least like to know what resolved it and if anyones opinion? We told ya it wasnt bricked. ..
Bricked is No pc to usb recognition and or phone wont boot into anything ..Black screen of death
Sent from my SGH-M919 using xda app-developers app
I bet he changed USB port or cable.
extrem0 said:
I bet he changed USB port or cable.
Click to expand...
Click to collapse
Uninstalled and reinstalled drivers and Odin, rebooted my comp and used the Sammy USB cable.
Well glad you got it.... but i still find it hard to believe any usb was the issue Usb recognition is usb recognition. .if odin seen the phone usb was working. ..its literally that simple... the problem initially explained was that the pit error was coming up... that all relates usually to a file error .
But glad it worked out and u didnt loose a 600$ phone.
Sent from my SGH-M919 using xda app-developers app
When I read this post, my stomach felt like it felt the first time I almost bricked my brand new s2 when it first came out, glad you got it to work
lojak29 said:
Well glad you got it.... but i still find it hard to believe any usb was the issue Usb recognition is usb recognition. .if odin seen the phone usb was working. ..its literally that simple... the problem initially explained was that the pit error was coming up... that all relates usually to a file error .
But glad it worked out and u didnt loose a 600$ phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I own three Samsung devices, and my sgs2 will not transfer files or work with adb when I use a generic best buy rocketfish usb cable. The original Samsung cable works every time.
Sent from my Xiaomi MI2S
I have seen that a lot.
I actually bought a few spare Samsung ones from eBay to make sure I would always have a good cable.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Well... one case to the next is different. .. ive never had issue using a lg cord moto cord or htc on a samsung device. .
I just think that the op post if you read his initial problem and how it was stated i think it had to do with trying to odin in the pit section instead of pda.
Ive seen this issue before.
Once again glad its fixed
Sent from my SGH-M919 using xda app-developers app
Nope, it was in the PDA section. I'm familiar with Odin and used it several time in the past (on my Note 8.0) . I believe the error message was either due to corrupt download and/or the USB cable. Anyway so glad it was solved quickly and thanks again for your help.
NYCguy2020 said:
Nope, it was in the PDA section. I'm familiar with Odin and used it several time in the past (on my Note 8.0) . I believe the error message was either due to corrupt download and/or the USB cable. Anyway so glad it was solved quickly and thanks again for your help.
Click to expand...
Click to collapse
+1 for the corrupt dload.
:thumbdown:Usb not likely since Odin seen the phone ill leave it at that.
Sent from my SGH-M919 using xda app-developers app
lojak29 said:
+1 for the corrupt dload.
:thumbdown:Usb not likely since Odin seen the phone ill leave it at that.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Pit file. That solved my problems. Flash it alone, then flash a good stock rom.
Im having issues flashing roms thru odin. I keep getting an error message saying
E/sbin/runatboot. sh process ended with ERROR-1
When i try to flash thru odin i get a failed and on my download mode, top left, it says something about a magic string failed.
Can anyone tell me whats going on? I have tried to search it but came up with nothing.
Any help is appreciated. Thanks in advance.
AT&T i317
NJ1
Anyone?
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
First error in my experience is irrelevant to the ROM and doesn't affect flashing. I always get that error using TWRP 2.8.7.0 and have wondered what's the chase myself. I rarely use Odin so I can't really say, maybe the ROM needs to be specially formatted to be flashed through Odin?
xBkKx said:
First error in my experience is irrelevant to the ROM and doesn't affect flashing. I always get that error using TWRP 2.8.7.0 and have wondered what's the chase myself. I rarely use Odin so I can't really say, maybe the ROM needs to be specially formatted to be flashed through Odin?
Click to expand...
Click to collapse
Thanks for the reply. I guess we'll have to sit around to see if someone can shed some light. I thought maybe that was a reason why i couldnt flash roms successfully.
Sent from my SAMSUNG-SM-N910A using XDA
The vast majority of problems flashing with Odin can be traced to the connection between the phone and the pc, either the cable or one of the ports. If Odin recognizes the phone and you can start the flash but it fails, then it is very likely a connection problem.