I got a new version of the Diagnosis tool a couple of days ago via the Marketplace. Now the *#9908# password no longer works. Has any got/found out the new password?
Similar question here. What is updated?
I tried to access USB Tethering via *#7284# and received an error about some files. Did not confirm whether USB tethering still worked or not. Instead, I uninstalled the Diagnostics app and reinstalled it via ##634#, which brought back the old version .0923 so I can still get USB tethering.
drtolson said:
I got a new version of the Diagnosis tool a couple of days ago via the Marketplace. Now the *#9908# password no longer works. Has any got/found out the new password?
Click to expand...
Click to collapse
Found it [them] via some 'bing-ing'.
Apparently, it's not a single 'password' (as I had thought) -- it's different codes to take you to different menus.
Related
Hi,
I just got an old (original) Motorola Droid from my son. It was was taken out of service, so it's got no phone service, just WIFI. He flashed it to 2.2 before he gave it to me.
Almost everything seems to work ok on it: I can connect to my WIFI network, browse, etc. Market works, Flash works after I installed from Market.
I installed Netflix from the Market, and it starts up ok, but then I get a popup error that says:
"Please make sure that your device has network connectivity and the Date and Time settings are accurate."
and it kind of just hangs the Netflix app at that point.
Does anyone know what the problem might be, and how to get Netflix working in this case?
I'm guessing that it might be looking for a phone network connection or something?
Thanks,
Jim
Hi,
My son has a friend with a same (original) Droid, with the same firmware, but his phone is still active on Verizon, and he's able to get Netflix app to work on it.
He (my son) said that he thinks that he has another friend that also has a Droid that's deactivated, and he's going to ask him to try to see if Netflix will work on that.
If that latter doesn't work and get that same error message, I'm guessing that it's, as I mentioned above, trying to connect to Netflix via the 3G, rather than over the WIFI.
Anyone know if it's possible to get the Netflix app to use only WIFI?
I had a similar problem with Sipdroid this weekend when I tried to get that to work. It actually, at one point, connected me to a Verizon operator, presumably over the Verizon wireless network. Sipdroid has a configuration setting that allows you to tell it to use only WIFI, and once I set that, Sipdroid worked ok over WIFI. I think that I need to find some kind of setting in the Netflix app to do something similar.
Jim
Hi,
I just got off the phone with Netflix support. I don't know if the person that I spoke to actually knew what he was saying, but he said that the Droid is not "on their list of supported phones", so according to him, it would then try to "connect to their website".
I didn't think that I needed the build.prop changes, because I'm not getting an "unsupported device" message, plus, like I said, my son's friend has it working on his identical (except it's still on Verizon) phone, but I'm going to try some of those build.prop hacks, to see if that makes a difference.
Jim
Hi,
For the record, no joy with changing the build.prop. That seems to be ineffective.
So, I'm still stuck on this...
Anyone?
Thanks,
Jim
Hi,
I had left the phone on the Netflix error screen and it went to sleep last night, and when I woke up this a.m., and woke it, there was a different msg saying that it couldn't access some web site.
So, I started thinking that it was a firewall problem, and I put the phone's IP address in my router's DMZ, and VOILA!!
Got Netflix !!
Jim
My Focus broke, so the insurance replace it with a Focus S, that was great. ATT is my carrier
Now, I have been trying to get the USB Tether working, but is not working. I already get the Diagnosis application and did the code to swithch the USB to "Modem, Tethered Call" and it reboot.
However, after rebooting, the computer did not recognize any new device, a bit acward, as I would expect Windows record this as a new device, not under the same registry of my broken Focus. Anyway, under Devices and Printers I see the Samsung i937 as unspecified device, and under its properties I notice there:
- Samsung Mobile Modem - Type: Modems
- Samsung Mobile Modem Diagnosis Serial Port (WDM) (COM4) - Type: Ports (COM & LPT)
- Samsung USB Composite Device - Type: Universal Serial Bus controllers
on the connection that is created (since my older Focus), I force to use the Samsung modem. but 2 seconds after click, it shows ERROR 628.
have anyone suceed? is there any new drivers?
Wireless ICS works...
Have you tried this? It works on my Focus S.
I've not yet heard of anyone using ICS via usb with the Focus S.
I have not yet try the process you suggest. I would try soon. I just order my Unlock code form cellunlocker, When I receive and apply i will try.
Thanks.
Hey jbedoya,
USB Tethering on the Focus S works - just follow instructions in this thread.
Sounds like the main thing you are missing are the Samsung USB Drivers. There's a link for this on the second page of the thread here.
This post details the setup of your phone as the modem.
Good luck. Working for me
armodons said:
Hey jbedoya,
USB Tethering on the Focus S works - just follow instructions in this thread.
Sounds like the main thing you are missing are the Samsung USB Drivers. There's a link for this on the second page of the thread here.
This post details the setup of your phone as the modem.
Good luck. Working for me
Click to expand...
Click to collapse
THANKS VERY MUCH
I was not aware of the step insite the Advance TAB. now is working.
Glad this is working for you.
I am using Diagnostic ver .0923. Are you also on this version? I ask because of the updated version of this app currently available for the Focus S...
armodons said:
Glad this is working for you.
I am using Diagnostic ver .0923. Are you also on this version? I ask because of the updated version of this app currently available for the Focus S...
Click to expand...
Click to collapse
I had the updated version, and the keys were different. so I factory default my phone, to get back the .0923 in order to use your suggestion.
I have not updated to the next version yet, just avoiding any future inconvenience with the keys within the new version.
Actually, just uninstalling the updated Diagnosis app from the app menu and typing ##634## in the dial pad to reinstall will give you the non-updated v0.923 version of the app
For a few days now, after connecting my usb cable to the pc, i get the "connect" sound on both the PC and the Phone, but it keeps going to charge only, not MTP. I checked the Dev Options, set it to MTP, still didnt work.
I also did a factory reset, nothing. Any ideas?
Also, the notification popup for choosing the connection type via USB, no longer shows up.
EDIT: I tried multiple cables, they are not the problem.
Remove driver on PC > right click on start button > device manager > show disconnected devices and uninstall your mobile driver.
Install again the huawei suite and try connect your phone.
Gazatus said:
Remove driver on PC > right click on start button > device manager > show disconnected devices and uninstall your mobile driver.
Install again the huawei suite and try connect your phone.
Click to expand...
Click to collapse
I've tried all of that obvious stuff, even went trough the registary and got rid of the drivers. I need out of the box ideas.
MisterBlack83 said:
I've tried all of that obvious stuff, even went trough the registary and got rid of the drivers. I need out of the box ideas.
Click to expand...
Click to collapse
Settings > Advanced Settings > Security > Allow HiSuite to use HDB.
Try to connect with HiSuite.
MobileTechArena said:
Settings > Advanced Settings > Security > Allow HiSuite to use HDB.
Try to connect with HiSuite.
Click to expand...
Click to collapse
Again, all of the USUAL stuff I've tried. One thing i have noticed, under the options where i chose what type of connection i want to have, if i change it from one to another, it dosen't update right away, i have to close the options, and reopen them to see it change.
Considering you tried the usual software stuff and that you've tried multiple cables, it may be your phone's port that's damaged or something.
If you don't have any sensible data on the phone I suggest doing a factory reset, just to discard the possibility. But if that seems like too much hassle, I would get an ftp app on the playstore to do all the data transferring between your phone and any windows machine. I personally use the solid explorer plugin.
Hope I helped!
MisterBlack83 said:
Again, all of the USUAL stuff I've tried. One thing i have noticed, under the options where i chose what type of connection i want to have, if i change it from one to another, it dosen't update right away, i have to close the options, and reopen them to see it change.
Click to expand...
Click to collapse
You said you've already performed a factory reset, tried cables, tried reinstalling drivers cleanly, and tried several settings on the phone.
Have you gotten HiSuite installed? If so, does HiSuite recognize your phone at all?
Have you also tried different computers? I would figure you did since you said you tried all the obvious things....
If HiSuite gives no response at all and you've already factory reset before, I feel as though its either a hardware problem like FAFI_1999 has suggested, or it is a very deep rooted software bug (behind repair for a regular user, maybe even in kernel, plus there is no clear way of knowing where the exact problem lies at this point so we wouldn't know where to look in the first place).
In this case, best advice I could give you is to send your phone to a service center.... At least if it still falls under warranty....
Does adb see your phone?
For me it always goes to charge only and I have to manually check (or uncheck and recheck) the Files option in the notifications.
JpegXguy said:
For me it always goes to charge only and I have to manually check (or uncheck and recheck) the Files option in the notifications.
Click to expand...
Click to collapse
The problem is, the notification doesn't even show up, and when i go to options to change it, it dosent want to switch, it just stays the same, no matter what option i choose.
MisterBlack83 said:
... i get the "connect" sound on both the PC and the Phone, but it keeps going to charge only, not MTP. ...
EDIT: I tried multiple cables, they are not the problem.
Click to expand...
Click to collapse
I think i know the issue and i also got the solution.
Maybe the problem is an update KB that was installed on your PC. 3 months ago, Microsoft releasead a KB update that broke MTP ( https://betanews.com/2017/03/10/microsoft-admits-mistake-pulls-problematic-windows-10-driver/ ). Read the article and do what it's recommended for your windows version.
good luck. V
Azzureux said:
I think i know the issue and i also got the solution.
Maybe the problem is an update KB that was installed on your PC. 3 months ago, Microsoft releasead a KB update that broke MTP ( https://betanews.com/2017/03/10/microsoft-admits-mistake-pulls-problematic-windows-10-driver/ ). Read the article and do what it's recommended for your windows version.
good luck. V
Click to expand...
Click to collapse
No luck, but i have noticed something else, http://imgur.com/a/OVVXp this is the usb device, reinstalling dosent help.
MisterBlack83 said:
No luck, but i have noticed something else... .
Click to expand...
Click to collapse
If that KB update is installed, at every reinstall of USB driver its gonna install the wrong one. I had the issue on my laptop and had to uninstall the kb and then plug again the phone in to reinstall the correct usb driver.
If the bug is caused by windows, even if you don't know how it's possible, you should try to repair windows by refresh. It's a long shot, but i had a similar problem, i could not use PPPoE service because my friend unwillingly did something wrong on his laptop. I had to refresh windows to repair the network card driver and finally configure PPPoE service on his laptop.
So... refresh?
best regards, V
I have an Odyssey that currently has 57644 minutes before I can try another code combination. I would like to flash a new ROM on to it that would allow interop unlocking and let me get all the stuff I want off of it. Granted, that isn't a long time to wait to try again, but that is the tail end of a couple years of waiting. I wrote some possible codes down near to the time it got locked, but that is about all I have to go on and I'm not optimistic.
So, I connected the phone to my Windows 10 laptop and it was recognized (eventually.... had to do several soft resets of the phone). In Explorer, however, there was just an empty root directory showing up. I tried MBN_Creator but it also could not see a valid phone to flash to.
In Device Manager, I saw that only a generic (from 2006) USB/phone driver was installed. I have not been able to find a driver (Samsung or otherwise) that will install on Windows 10. I have tried a few on a WIndows 8 Pro system I have, but they also have not worked at showing any kind of file system on the phone. Is there something in the Windows Phone SDK that could be used?
I saw several references to being sure to use the original Samsung cable. I can't find that, but I tried one I did have along with borrowing a newer Samsung. The cable I have shows several folders on the borrowed Samsung (as does the cable my friend's using ... also not a Samsung cable), but neither cable works with the Odyssey.
I've tried soft resetting and power-cycling several times, but no dice.
I'm out of ideas, and would appreciate any insight you can give me.
I stumbled across a 'fix' for the huge number of minutes which was to pull the SIM and reseat it. So, I gave that a try and it came back on with 1.2 million minutes. . not the result I was hoping for.
I repeated the reseat and it was back to the 57k and change.
On the off-chance that the directories would show up, I checked and still nothing.
Once, I got the confirmation pop-up on my laptop for access to photos on the phone, but that had be finished on the phone. It seems weird that I wouldn't have been prompted for that last night, or the other times I tried this morning.
Now I'm thinking what I saw last night with my friend's phone was solely due to one being locked and the other unlocked (so, user error and ignorance). I thought I remembered seeing things when locked and connected to my old computer. I guess I must have allowed access.
From poring over the internet, it looks like what I want to do isn't possible and I'll just have to wait it out and hopefully guess right. If I'm wrong about having to wait, I'd appreciate being corrected.
Rooted stock XT1900-1 with 8.1.0 November patch on T-Mobile here.
This morning, I went to enable USB tethering at my office as part of my daily routine, but couldn't. It got grayed out somehow.
It worked fine last week. The only thing I did over the weekend was install the latest Magisk (v18). I haven't tried rolling this back yet as I couldn't imagine this would be the cause.
I usually use the EasyTether app, but when that didn't work, I checked the stock tethering settings and noticed USB tethering could not be enabled.
I tried 3 different cables to be sure that wasn't it. USB Debugging, ADB, and data transfer work fine.
I found this in a search, leading me to think maybe T-Mobile pushed an APN update over the weekend that may have broken it.
Has anyone else encountered this?
Could any T-Mobile US users share there "APN Type" for their default T-Mobile Access Point Name? Mine says: default,supl,hipri,fota,mms
Before I change it to "default,dun" I wanted to get input from the more knowledgeable folks here.
Thanks All.
Update: I re-tried this during my lunch break today, and USB tethering worked normally. I hadn't even restarted my phone or the computers I was using it with. APN Type never changed. I'm just dumbfounded.
While I wouldn't exactly call this "solved," I'm not gonna waste any more time & space to dig deeper.
Move along everyone! Nothing to see here : )