[Q] Crazy USB Problem - Desire HD Q&A, Help & Troubleshooting

Hi,
My DHD is only 2 months old, just recently it has started behaving oddly. When i plug in the usb to a computer the phone starts to open applications such as dialer and tries to phone people. Tried clean install of CM7 and CM6.2 and same thing happens. Tried on different computers, same thing. Tried different cable, same thing.
Anyone anys ideas if something that loads before the rom could be corrupted, before i restore it to stock rom/radio and take it for repair?
thing that is confusing me is that usb seems to be fine in fastboot, i can send and flash a radio, but from recovery it also selects options.

If it was Windows PC, you would think a virus.
There are a few virus's out there for Android, maybe DL a free antivirus app (such as AVG or Lookout), update it and run a full scan (They will detect Superuser, but ignore this one). I don't think it's the problem, but worth a quick check.
What about a flashing a different kernel from CM7 or LeeDrOiD etc?
Edit: And what about a different custom non- CM7 ROM? If you try, don't forget a nan-backup & TB of app data etc.

Agreed with UpInTheAir. It's the virus.
Just full wipe and install back rom. your phone can be use like normal

yes i thought about a virus. AVG shows no virus, also scanning the sdcard with Clamxav an my mac shows no virus. Phone has not been plugged into a PC for a long time.
Since this is happening when in Recovery it would mean that a virus would have to be installed at a level pre ROM...
I will do some more testing, the only thing i can think so far is a hardware problem, where maybe a bad ground if interfering with the touchscreen operation which would account for fastboot being ok..

Related

Activesync not working (always connecting..)

My activesync just stopped to work since some day, it is just keeping connecting, but never succeed. I've tried to reinstall activesync several times but no luck. Now the version is 4.5, and my rom is a custom made one from the forum (xplode_7.00 6.10.00.WWE). I don't have a clue as it just suddenly stopped to work. Some thing that may be useful for troubleshooting:
1. when connected to pc (winxp), no device showed under " USB controller" in device manager, instead a "windows mobile based device #16" showed up under "Network adapter"
2. When just hooked, a connecting icon will show up at connectivity status(top of the screen) for about one second, then replaced to "two arrows with a cross ".
3. I have Rogers blocked my data service... could that be a reason? (seems not quite likely)
That's all what I could think about so far. I've looked through posts regarding similar issues but still could find a solution. I appreciate any input/insight.
----
Another question, does any one know how to have the youtube app working with wifi. It just showed " Error, Connection problem. Failed to initialize...."
Thanks a lot
your data service theoretically could be the issue, but since you said it worked before, and your device manager says #16, i guess, this will help you:
i don't know if you use the cradle with a pc or maybe a usb cable that is not permanently connected, but it seems, the driver is just installed many times now, so try the following to clean that up:
1. disconnect the cable/cradle
2. on the pc, right click "my computer" or "computer" (depending on whether you use xp or vista/7), and click 'properties'
3. go to the advanced system settings
4. click "environment variables"
5. make a new variable by clicking the upper "New" button
5.1 the name must be "DEVMGR_SHOW_NONPRESENT_DEVICES" without ""
5.2 the value must be "1" without ""
5.3 close all open windows with OK
6. restart the pc
7. start the device manager again, e.g. by right clicking "my computer" or computer and clicking "manage"
8. click "View" and then "Show hidden devices"
9. now you see a lot of new greyed out devices, all devices that were ever connected to the pc.
10. now you can start cleaning up:
10.1 go to "Universal Serial Bus controllers"
10.2 all the greyed out entries named "Unknown device", "USB Mass Storage device", "USB root hub" can be right-clicked and uninstalled, but just the greyed out ones!
10.3 go to the tree "Portable devices" and uninstall anything like BlueAngel, PocketPc and stuff like that.
10.4 go to the tree "mobile devices" and uninstall them all.
10.5 close the device manager
11. connect the cable and the device again.
12. since all the old drivers are uninstalled, it will start searching for new hardware and then connect the device again. if you are in fact using xp and the driver is not found disconnect the device again, uninstall active sync, restart the pc and re-install it. it brings the driver and on the next connect, the "new" hardware will be found.
ok, it seems like a lot of work, but it will seriously speed up all your usb connections, because all the dead links and drivers are cleaned up. if, for any reason, this was not the solution to your problem, at least enjoy the faster usb, you're welome
in that very case, you should use pimbackup from my thread in my signature (the "read first" one) and make a backup of all your pim data and perform a hard reset, that could also help.
btw. when you are in my thread already, there is also a youtube app there, that works extremely well with wi-fi and is a lot faster than the official one.
Thank you very much for this detailed procedure. I've tried it through, but still no luck. I'll see if I could find solution before "a necessary hard reset". One odd thing is I didn't see any "blueangel related item" under Portable devices, and I even don't have "mobile devices" tree..
I also downloaded youtubeplay. I will give it a try later. Also, isn't myphone usable through wifi either?
Thanks a lot for the help.
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Chef_Tony said:
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Click to expand...
Click to collapse
This is why history is important... you learn from it
Here is an extract from xplode's thread (first post)
R7 Release (this does not mean that this is windows mobile 7)
-------------------------------------------------------------------------------
Rapidshare: R7 ROM
Ziddu: R7 ROM
[highlight]Known bug with it , does not want to sync ... (or maybe it is my pc error i will look into this, but now it is 4 AM and i am going to bed[/highlight]
Click to expand...
Click to collapse
I have a simpler solution.... get PIM backup to save any important things out of your phone, flash a newer rom . Remember, xplode's latest version was 7.1 and not 7... and that is for a very special reason... bugs (activesync being one of them). More than likely, you will have to either HR or change roms. I would personally go with the latter since I am gonna have to reinstall everything anyways.
BTW, Chef.... awesome guide!
yeah, i remembered that xplode had some sync issues with some past roms, but i always thought that it if it hit you, sync wouldn't work at all but it seems to have worked before, which is why i didn't blame the rom first. that usb driver issue is trouble though, it could have been the solution this time, since it isn't i will use this to link on, the next time it might be
but i agree, in this case, changing the rom should clear all issues.
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
java218 said:
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
Click to expand...
Click to collapse
There are things that get backed up with 3rd party software (such as Sprite Backup), which will mess things up in the device. It is usually recommended not to use these softwares to back your things up. Instead, you should always try to either use AS, or try PIM Backup, which for some reason doesn't mess things up.
Glad it worked out
same issue with ELF0 100 i can't figure out :-(

[Q] Please help my phone isn't being recognized

It's very strange As it seems to be recognized by the computer but is not found by the AIO 1.13 batch file , I've never used Odin as all I've done is to root and install the SDX Remover. I am able to transfer files to and from my SD Card. I've tried numerous USB Cables including the one which initially allowed me to root, it's the only one of all of my many cables which allows windows to recognize the device and transfer files at usb 2.0 speeds all others either fail recognition or tell me to find a faster port. So I'm at a loss and really, desperately wish to update to froyo. I've tried every tip I've found up to and including shutting down my computer and unplugging it for more than 30 seconds. It's probably something quite simple that I'm overlooking,. I recall having to create a guest account in order to run the batch file and tried that as well. Any tips very much appreciated.
I think I'd like to revert my phone to stock(I think I did a full backup) upgrade to froyo officially than re root or not. I've been way to busy to spend too much time fussing with my phone.
If you are still on stock, which it sounds like you are....just follow the instructions on this post:
http://forum.xda-developers.com/showthread.php?t=963652
since you are already at stock...start from step 11 "download update.zip" and go from there.

[Help] A Myriad of Problems

Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.
Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-

[Q] Successfully rooted phone with AAHK but...

My windows 7 is acting a bit crazy now.
For example, before rooting phone, I could go into folder options and show hidden files, but now that's not available.
After rooting phone, my desktop was a blank, shocked me. Managed to find a solution, which is to copy and paste one directory into another in the windows system32 folder.
When I go into control panel, there are 3 options for viewing, by Category, Large Icon, Small Icon. When I change to Small Icon, it just shows as Large Icons still.
My google chrome now shows "Your preferences cannot be saved" upon running it.
My internet explorer favourites disappeared.
And most importantly, I can't play candy crush saga on all browsers and my wife is scolding me for it!
Appreciate any help. I've tried searching for solutions one by one, regarding the hidden files problem, it seems there might be a virus. But from turning off my anti virus to running AAHK and turning anti virus on, I didn't do anything else in between...
Thanks!
I managed to get everything back to normal by using a system restore.
I restored to a point before installing the HTCdriver found in AAHK.
Now another question is: Is it safe to connect my phone to the computer, since it's restored to a pre-rooted stage. Sounds like a stupid question though. I think it's safe and besides, after successfully rooting, I probably don't need to run AAHK anymore unless I want to restore to stock ROM right?
Would still like to find out what probably went wrong after running AAHK though.
ferns_mccanus said:
Would still like to find out what probably went wrong after running AAHK though.
Click to expand...
Click to collapse
It sounds like too many issues for them to be unrelated.
Most likely, disabling your antivirus for running the AAHK opened up a way for a virus to come in and cause all those problems.
Some of the symptoms fit to a virus behavior perfectly: the virus probably disabled viewing hidden files so you couldn't see the virus' files, you have problems accessing some folders and files (like your Desktop, Favorites, or Chrome data) because the virus probably took your permissions to access them so you wouldn't be able to remove the virus manually, etc, etc..
Regarding your question:
ferns_mccanus said:
Now another question is: Is it safe to connect my phone to the computer, since it's restored to a pre-rooted stage.
Click to expand...
Click to collapse
I don't see any problem with connecting your phone to the PC in its current state. The PC's state is important only to the process of running the AAHK, not to the state of the phone (rooted / unrooted).
And if you're planning to run AAHK again (which, as you said, will be needed only to return your phone to stock), I'd recommend, like the AAHK manual does, to run it from an Ubuntu Live CD. It's very easy, lets you not to worry about your PC's state for the AAHK, and would definitely not affect your PC after running the AAHK.

Internal SDcard Busted, Can't Format or Write (Forever Locked as Read-only)

HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app

Categories

Resources