Database Users

Kies Mini not recognizing Vibrant

Hi,
I am attempting the Froyo update on Vibrant through Kies Mini following the T-Mobile Instructions at the following location provuded by twitter account galaxyssupport
I am able to download and install Kies Mini successfully. The drivers seems to be correctly installed because Windows 7 or Windows Vista is able recognize the device. At Stage 3 as instructed I open Kies Mini. It asks me to connect my Vibrant to the computer. I complete this step and that is it. Kies Mini is not able to recognize that the Vibrant has been plugged into the computer though Windows is able to.
I tried this on three different laptops Windows 7 64 Bit and 2 different Windows Vista 32-bit. All to the same result. After going through some of the forums, I set the USB debugging mode on on my Vibrant and connected the device to the computer. On all the three laptops the Kies Mini Crashed with the following error "MiniApplication Launcher has stopped Working".
BTW I even tried by removing my SD card as some forums suggest. No luck
Anyone who has gone though similar troubles and could come up with a solution to get Froyo on Vibrant.
I called T-Mobile they said it is Samsung's problem and then I called Samsung. The CSR who picked up the call asked me few mundane questions some of them same questions repeatedly. Then she said she will connect me to an high level support and WOW that Number does not work and the call ended with the message "EXITING THE SYSTEM" !!!! Samsung and T-Mobile is a dead end now.
Any help would be greatly appreciated.
Thanks & Regards,
TMax

Mini Kies wont recognize it with USB Debug on...it has to be off and try running it as administrator, with the stock TWLauncher..not LauncherPro, Zeam, or anything like that or you'll get a "Need idle screen warning" if your using one of those.

I'm having the same issue... i've did a factory reset... removed sd card... tried debug on and off... Still nothing. keeps showing "Unregistered Device"

You could just learn ODIN (not hard) and ODIN to this.
http://forum.xda-developers.com/showthread.php?t=919687
That'll be the same as getting it via mini kies.

FlameEffex said:
I'm having the same issue... i've did a factory reset... removed sd card... tried debug on and off... Still nothing. keeps showing "Unregistered Device"
Click to expand...
Click to collapse
I have "Unregistered Device" issue, it seems like all the exchanged/refurbished units cannot be updated for now.

lexluthor said:
You could just learn ODIN (not hard) and ODIN to this.
http://forum.xda-developers.com/showthread.php?t=919687
That'll be the same as getting it via mini kies.
Click to expand...
Click to collapse
Where can I download the official KA6 rom? forget Kies, I want to do it via ODIN.

parahelium said:
Where can I download the official KA6 rom? forget Kies, I want to do it via ODIN.
Click to expand...
Click to collapse
Look in this thread...
http://forum.xda-developers.com/showthread.php?t=919687

parahelium said:
I have "Unregistered Device" issue, it seems like all the exchanged/refurbished units cannot be updated for now.
Click to expand...
Click to collapse
what would that have to do with anything?

Damn, I have the same problem here.
Using TWLauncher (cleared Zeam defaults), not on debug mode...

I had the same problem. I was using a very thin gage usb cable. I then switched to a heavy gage cable and it worked just fine. Give that a shot.
Sent from my SGH-T959 using XDA App

I'm using the original cable. Got back to home (TW Launcher) and it worked.

I've spent a bunch of time on the phone with T-Mobile and Samsung; 7 hours. I believe the issue is with the KA2 update that was released a couple of days before the KA6. Neither Level 3 reps knew anything about it and kept referencing JI6. Used both Mini Kies received an unregistered device error (I registered my device through Samsung) and used the full version of Kies 1.5.1.1 and it said my firmware version was not available for an update. Use Odin it works and took about 5 to 10 minutes and I didn't lose my user preferences, apps, contacts, etc. Everything works great even GPS.

Ahhh
I am not a techy in any sense of the word so I have been waiting for the official release of 2.2 instead of rooting, because I'm scared ******** to try it. Now release date rolls around, finally, and I can't seem to get it to work. I am having the same issue, well first it was the 16 character file extension issue, but now it is this. My phone is plugged in, Kies is up and running, in my computer it shows my phone, by name, but no update. I have NO idea what so ever what usb "debugging," "touchwiz," or anything of the sort. Hell I am proud of myself for knowing what rooting is. Is there anyone who can help me get froyo on my phone?

Kies wont connect to tab.

I have searched and tried a few things I found but with no luck. Makes me think the driver is screwed up. I have the US/Sprint tab if that makes any difference. I keep getting the Error Kies cannot connect and needs to be in PC Studio mode. Thx for any help.

make sure you havent enabled usb debugging mode and left it on

Some times restarting the tab fixes the kies connection problem.

FWIW, I wasted the better part of yesterday trying to get Kies to connect with no luck. Some of the remedies I tried were a utility to locate long file names on the Tab and installing a UK version of Kies.
I believe the general consensus is that for many of us, Kies is a POS. Since I can't get it to connect, I seem to be stymied in my attempt to regain root access until another fix comes along.

Have you used adb? Or odin? I have flashed 5 tabs and never used the kies program.

Have not tried those. Is there a link on how to use? I really want to get my Root back.

"Have you used adb? Or odin? I have flashed 5 tabs and never used the kies program."
Haven't tried adb, although I used it when I originally rooted my MotoDroid. However, I don't recall seeing anything for using it on the SGT.
I have a Sprint Tab, so I thought odin would not work on it.

Please note that the US version of the Tab are not currently supported by the full version of Kies. You can only use the mini version of Kies with the tabs to do firmware upgrades only. Also of note, I can connect and get Kies-mini to recognize my T-Mobile tab, but no firmware upgrades have been made available.

Failed root with odin, cannot detect with Kies 3

recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.

vivek318795 said:
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
Click to expand...
Click to collapse
I'm running into the exact same issue, did you ever find a solution?

Same issue
I have the same issue. Is there no help? Chainfire? do you have a CF-Root for SM-N900V yet?
Thanks. any help is appreciated.

Problems rooting s5 SM-G900F G900FXXU1ANG8 uk vodafone.

I have spent hours over the last few days trying to root my Galaxy S5
It have firmware G900FXXU1ANG8 and is model SM-G900F
I have tried towelroot
it failed
i have tried Heimdall Suite
it detects the device but gives failure when trying to save pit file or do anything else
I checked several forums and they say use different driver so i use the zadig and installed libusbK and still problem.
I have tried Odin3_v3.07 Odin3_v3.09 and Odin3_v3.10 and they all dont pick up my phone.
i have tried two different cables and still nothing.
Anything else you can recommend and i have literally spent hours reboot and trying different drivers, restarting computer and looking for different fixes.

wbb1 said:
I have spent hours over the last few days trying to root my Galaxy S5
It have firmware G900FXXU1ANG8 and is model SM-G900F
I have tried towelroot
it failed
i have tried Heimdall Suite
it detects the device but gives failure when trying to save pit file or do anything else
I checked several forums and they say use different driver so i use the zadig and installed libusbK and still problem.
I have tried Odin3_v3.07 Odin3_v3.09 and Odin3_v3.10 and they all dont pick up my phone.
i have tried two different cables and still nothing.
Anything else you can recommend and i have literally spent hours reboot and trying different drivers, restarting computer and looking for different fixes.
Click to expand...
Click to collapse
flash this http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip u have to install samsung drivers u can find them in folder of kies. there is a folder with the name "USB driver" install this and odin will recognize your phone in download mode

Odin doesn't recognize my s7 edge (trying CF auto root)

Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)

Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap

skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.

cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc

skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!

I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also

Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?

which OS?

S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread