Develop Bugs

unknown device no matter what but was working fine

Yesterday i wanted to tranfer pictures to my Epic 4g and it showed up fine for a few seconds then disapeared and now all I get is unknown device in device manager on Windows 7 x64. Phone has been working since I bought 4 months ago. I did upgrade to FC05 modem in the morning without problems on Calkulin's 2.8.1
1. Tried different PCs and cables with same result
2. Wife's Epic 4g works on same computer and same cable
3. Reinstalled Samsung drivers and KIES in different configurations, no luck
4. Used kies to transfer Calkulin's 2.9.2 with CWM using format all no luck
5. Restored back up from last week no luck
6. PDAnet did not help
7. Messed with USB debugging and USB utilities no luck
Phone does not have any problems working, just pc won't recognize. I can install new ROMS that already have CWM if I transfer via KIES to internal storage and run from CWM, ODIN/Download mode does not recognize my phone. Is there any way to install ROMS without CWM and add it later if I can't connect to PC? Any ideas how to fix. Charging works and pc recognizes phone each time but does not know what it is.
Thank you.

You can use mobile Odin to flash kernel and get cwm ...there is a free lite version on xda
Sent from my SPH-D710 using xda premium

Thank you, I'll give Mobile Odin Pro a shot. Is it reliable or anything to watch out for as in the last bricks. In time I think I'll just replace the phone as I think the port went bad not sure how.

[Q] help please ¡¡¡¡¡ Kies does not sync i747 samsung galaxy s3

this great forum friends please ask them to help me with samsung kies, this damn program does not synchronize my samsung i747 s3 having root.
I did everything for me to recognize it, how to install the drivers manually and still nothing.
What I want is to upgrade to 4.1.1 official jelly bean that just came out for s3 i747, but the upgrade is through the stupid kies.
I thank you for your great help.
Greetings ¡¡¡¡¡¡¡¡

http://forum.xda-developers.com/showthread.php?t=1739426

I couldn't sync with kies because I forgot to change the hidden USB settings back to MTB + ADB from when I was doing the root with ODIN. I changed it back to that and it worked
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Well unfortunately im at work right now so I dont have my computer to walk you through the steps. I remember that you have to type *.config, in search, while you are in in the keys folder on your computer. Which will show the configuration files and then double-click on the file that says Kies without anything else in the name. In there you will find a line that looks like this: <somethingsomethinglol 4.0>
The problem is that the Kies program is trying to connect to the 2.0 version of that line AND the 4.0 version so when you copy/save that line and delete it then kies can connect.

Kies don't recognize SGH-T989D

Good day,
I am trying to connect my wifes SGH-T989D Samsung Galaxy S IIx Koodo phone to Kies. The phone is stock and not modified. Running Stock ICS 4.04 Android. Kies don't recognize the phone connected. I tried the debugging method. Nothing and I am really peeved. Anyone have suggestions????

ern88 said:
Good day,
I am trying to connect my wifes SGH-T989D Samsung Galaxy S IIx Koodo phone to Kies. The phone is stock and not modified. Running Stock ICS 4.04 Android. Kies don't recognize the phone connected. I tried the debugging method. Nothing and I am really peeved. Anyone have suggestions????
Click to expand...
Click to collapse
why would someone use kies ? it is completely useless
try uninstalling (I recommend "your uninstaller") for a clean uninstall , then install the samsung usb drivers , the kies

nabilbek said:
why would someone use kies ? it is completely useless
try uninstalling (I recommend "your uninstaller") for a clean uninstall , then install the samsung usb drivers , the kies
Click to expand...
Click to collapse
To update the phone. Since this version don't have over the air Update Like my HTC One has. Wish Samsung would have done that!!!!

ern88 said:
To update the phone. Since this version don't have over the air Update Like my HTC One has. Wish Samsung would have done that!!!!
Click to expand...
Click to collapse
still, I would grab the stock rom from here or sammobile.com and odin flash it
I hate OTAs

nabilbek said:
still, I would grab the stock rom from here or sammobile.com and odin flash it
I hate OTAs
Click to expand...
Click to collapse
Well, I don't have OTA option. And lies is the only way to check and install updates. This is my wife's phone and I rather not use unofficial updates. Sammobile doesn't have updates for canadian phones.

ern88 said:
Well, I don't have OTA option. And lies is the only way to check and install updates. This is my wife's phone and I rather not use unofficial updates. Sammobile doesn't have updates for canadian phones.
Click to expand...
Click to collapse
here is the latest update that u would get from kies, grabbed from sammobile : http://www.hotfile.com/dl/180851941/242c562/T989DTLLG2_T989DKDOLG2_KDO.zip.html

nabilbek said:
here is the latest update that u would get from kies, grabbed from sammobile : http://www.hotfile.com/dl/180851941/242c562/T989DTLLG2_T989DKDOLG2_KDO.zip.html
Click to expand...
Click to collapse
Well after hours of searching I found what the problem was. I had to dial *#7284# and turn on PDA mode on the USB section. And I connected it to Kies and it worked. I am sure this will solve the problem lots of ppl have had with connection issues.

ern88 said:
Well after hours of searching I found what the problem was. I had to dial *#7284# abd turn on PDA mode on the USB section. And I connected it to Kies and it worked. I am sure this will solve the problem lots of ppl have had with connection issues.
Click to expand...
Click to collapse
well this is new to me, take my thanks

Thanks
ern88 said:
Well after hours of searching I found what the problem was. I had to dial *#7284# and turn on PDA mode on the USB section. And I connected it to Kies and it worked. I am sure this will solve the problem lots of ppl have had with connection issues.
Click to expand...
Click to collapse
this solved the Kies problem with recognizing the T989D

Having Trouble updating to Jellybean via Kies
Hello guys! As my username implies, I've been the owner of a Samsung T989D Heracles for about 8 months or so. I've had so many **** ups when it comes to doing any exploits with my phone and most recently I've had issues upgrading my firmware with Kies. Twice now there's been this notice of this box that appears to say "PC can't recognize my phone" and that was due to my phone being in download mode. Tried unchecking and checking USB debugging resulting in the same **** happening again. Not comfortable with installing Jellybean unofficially because I don't wanna deal with my wireless carrier(the sales people in the store are a bunch of idiots). Any advice or suggestion?

Noob_Android_User said:
Hello guys! As my username implies, I've been the owner of a Samsung T989D Heracles for about 8 months or so. I've had so many **** ups when it comes to doing any exploits with my phone and most recently I've had issues upgrading my firmware with Kies. Twice now there's been this notice of this box that appears to say "PC can't recognize my phone" and that was due to my phone being in download mode. Tried unchecking and checking USB debugging resulting in the same **** happening again. Not comfortable with installing Jellybean unofficially because I don't wanna deal with my wireless carrier(the sales people in the store are a bunch of idiots). Any advice or suggestion?
Click to expand...
Click to collapse
Download mode is used to install packages, Kies put your phone in download mode only if he installs any update, so it means you shouldn't put your phone on download mode to make it recognized by Kies. Did you install the specific drivers for your phone?

Noob_Android_User said:
Hello guys! As my username implies, I've been the owner of a Samsung T989D Heracles for about 8 months or so. I've had so many **** ups when it comes to doing any exploits with my phone and most recently I've had issues upgrading my firmware with Kies. Twice now there's been this notice of this box that appears to say "PC can't recognize my phone" and that was due to my phone being in download mode. Tried unchecking and checking USB debugging resulting in the same **** happening again. Not comfortable with installing Jellybean unofficially because I don't wanna deal with my wireless carrier(the sales people in the store are a bunch of idiots). Any advice or suggestion?
Click to expand...
Click to collapse
A lot of the time this is due to your PC not installing the drivers correctly.. Either that or you should try different USB ports.
Try downloading the newest Odin connecting your phone and put it in download mode. If Odin does not recognize your phone then the drivers got borked up during installation .. And if Odin does see your phone ..then just use that instead.
**** kies !
Sent from my SGH-T989 using xda premium

jonmassot said:
Download mode is used to install packages, Kies put your phone in download mode only if he installs any update, so it means you shouldn't put your phone on download mode to make it recognized by Kies. Did you install the specific drivers for your phone?
Click to expand...
Click to collapse
Did install specific drivers so which one of these drivers do i use?

Noob_Android_User said:
Did install specific drivers so which one of these drivers do i use?
Click to expand...
Click to collapse
The only drivers you need to concern yourself with called Samsung USB driver for mobile phones
Sent from my SGH-T989 using xda premium

HELP! Firmware Won't Upgrade!

I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul

premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped

Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul

Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium

use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like

sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul

[Q] galaxy note 8 factory restore

Hi guys. Im a noob, first post here and need some help. Be searching all day for how to load a stock rom to my device GT-N5110.
Heres the low down.
Purchased in Australia. No updates applied.
Success rooted with framaroot.Was running framaroot for more than a month
Install busy box today in normal mode I think. I chose the safe option.
Edited build.prop product model so I could install Navigon
Navigon working fine
Now..........
Unable to change the product name back using es explorer or file expert.
Thought it would change after restart but device entered bootloop. I think busybox was the culprit.
Discovered recovery mode and did factory data reset. Can acces odin screen on device too.
Device boots but hangs on language selection screen
I have found and downloaded stock rom for it that I found here somehow
I tried "Mrjraider" tutorial "how to flash back to a stock rom"
but odin crashes whenever I load the rom file and it wont recognize my GN8.0
Computer runs on windows 8. Kies is up to date too. Kies reconizes device but is unable to update or anything
Was running odin in win xp sp3 with administrator
can try on a win7 computer tomorrow.
This is the name of the file its about 1.2 Gb....... N5110UEDMD1_N5110XARDMD1_HOME.tar.md5 do I need to rename this or something
There was also a .dll that was in the package, wtf with that?????
be looking through this forum all day and night and cant quite find what im looking for. If what I seek is here please point me to it. Or if any one here in Brisbane, can fix it for me,What are your thoghts? PM me.
Just want my baby back working again.
Sorry, wrong section please delete mod

If I'm not mistaken, remove Kies, then try using Odin. Also, dll is a Windows file. I could be wrong about Kies, but I think I remember reading that it conflicts with Odin.
Sent from my SGH-T889 using Xparent Skyblue Tapatalk 2

Yesterday I installed same firmware in my computer runing win7 with Odin and Kies installed at the same time without problems. You don't need to rename the file, dll is a library for windows and needs to be on the same folder as the md5 file. Just remember to put the Note in download mode in order to get the firmware installed by Odin.

I have a thread in the development forum with the only file you need just flash in odin and done.
Sent from my GT-N5110 using Tapatalk 2

Tutorial is ok, problem seems to be elsewhere.
I have Windows 8 (x64) too, and Odin works i my case, i successfully flashed (and restored counter) N5110 before returning tablet to shop (it was exchange for N5100). Kill all Kies components via task manager, i have two more things in processes when i quit Kies. Next, try another version of Odin, but I remember one ROM from SamMobile, which crashed every Odin i had, so its may be this problem. Try another version of ROM - older, if exists. If crashes Odin too or not exists, try uninstall both Kies and Samsung USB driver, dowload toolkit from xda (http://forum.xda-developers.com/showthread.php?t=2251033) and install new driver via toolkit.
In rare cases may be problem in your computer, so try another one without installing Kies. I wish you luck.
Edit - That big file is ROM, dll is not needed for Odin. Run Odin, press PDA, select your rom. Turn tablet off, connect to comupter by original or hi-quality short cable, set tablet into download mode (hold vol- and home, press power on for 2 secs, select continue by pressing vol+). If all is ok, first field in Odin change color to yellow (i think), then press "Start".

Thanks to all. Let you know how I go. Odin 4.43 keeps crashing when loading the rom, on both my win8 laptop and fresh installed win 7 pc. Uninstalled everything from laptop except nero. Nothing installed on pc except modem drivers and Samsung drivers. I will redownload the rom. I think it may have become corrupt. Cheers
ok success. this is what I did. eventually got the rom to sit in odin without crashing it by simply renaming file by deleting the .tar.md5 extention. clicked off the file to save the rename. Right click on it again to rename and type the extension back in. Loaded it in odin and it worked. File name in odin showed up with duplicate file extention eg .tar.md5.tar.md5 but it worked. Odin 4.43 would not detect my device. Senior Moderator Mskip toolkit for Samsung galaxy note 8 would not detect my device .This was very frustrating
Used odin 3.07
loaded rom in pda. Found in janjannsen99 development thread.
connected device ,odin 3.07 detected it, unlike 4.43 for some reason.
clicked start.
Walla. Im a happy man.

This is the kind of story that are the most scary. Now I am kind afraid of root my note 8 or do anything unofficial.
Anyway, best wishes to you.

mickatron said:
Thanks to all. Let you know how I go. Odin 4.43 keeps crashing when loading the rom, on both my win8 laptop and fresh installed win 7 pc. Uninstalled everything from laptop except nero. Nothing installed on pc except modem drivers and Samsung drivers. I will redownload the rom. I think it may have become corrupt. Cheers
ok success. this is what I did. eventually got the rom to sit in odin without crashing it by simply renaming file by deleting the .tar.md5 extention. clicked off the file to save the rename. Right click on it again to rename and type the extension back in. Loaded it in odin and it worked. File name in odin showed up with duplicate file extention eg .tar.md5.tar.md5 but it worked. Odin 4.43 would not detect my device. Senior Moderator Mskip toolkit for Samsung galaxy note 8 would not detect my device .This was very frustrating
Used odin 3.07
loaded rom in pda. Found in janjannsen99 development thread.
connected device ,odin 3.07 detected it, unlike 4.43 for some reason.
clicked start.
Walla. Im a happy man.
Click to expand...
Click to collapse
That's what I use odin 3.07 . Don't use the other versions for some reason they don't work
Secondly guys when you download that file in my thread tO your computer it has to be extracted first you only Click PDA In ODIN and use the file you just extracted with the tar md5 extension. Thats it. That ss.dll file has no purpose its just there and you need not even bother with it.
Sent from my GT-N5110 using Tapatalk 2

I am also trying to restore my US-based Note 8.0 WIFI (still on 4.1.2), but couldn't figured out which ROM file I need to download.
Could you tell me the filename? I am using the Note 8.0 toolkit.

ROM
lanwarrior said:
I am also trying to restore my US-based Note 8.0 WIFI (still on 4.1.2), but couldn't figured out which ROM file I need to download.
Could you tell me the filename? I am using the Note 8.0 toolkit.
Click to expand...
Click to collapse
Will these two links help you:
Link 1
Link 2

AkiOrpheus said:
Will these two links help you:
Link 1
Link 2
Click to expand...
Click to collapse
I have checked that, but I don't see US Note 8.0. The search seems broken to, since United States is not shown in the list of country for Note 8.0

No one knows how to get the stock US based ROM?

lanwarrior said:
No one knows how to get the stock US based ROM?
Click to expand...
Click to collapse
@lanwarrior
U have to register on sammobile.com to download firmwares (stock ROM). Put the model as SGH-i467 and u will the file

AkiOrpheus said:
Will these two links help you:
Click to expand...
Click to collapse
people keep posting to go to sammobile but every time i look there isn't a rom labeled for the US, and they dont give an explanation of what rom would be the equivilant or even if any of them would be. Should I use UK version? is it the same as the US?
I'm having the same exact issue as OP and I can get into download mode and i have odin 3.07 but i am just looking for the exact rom to load and cant find an exact answer so far. I've already messed up my tablet enough today so I don't want to flash the wrong rom and make things worse lol.
K
O
F
ps I looked for janjansen's thread in development and did not see it, am I missing something? anyone got a link?

ok I did some more reading around the web and found that a lot of people used the UK version as I kinda suspected. Would have been nice to get confirmation on that but its cool, I flashed it, no problem, and now I'm setting up the chainfire root and getting back all my apps. So all in all it took a few days but I'm back on my feet *sigh of relief*
K
O
F