im having a problem in which my touch pro will not sync or be recognized by ANY type of usb connection (ie, advanced network functionallity unchecked, disk drive mode) it syncs via bluetooth just fine, and when connected to the computer via usb the dialog box asking which type of connection still pops up and it still charges, but no type of connection will go through, i have tried everything except for a hard reset which is what im really avoiding because i have it finally running exactly how i wanted (complete with manila 2.1 on wm6.1 htc 2.01 rom which took me an hour to get working exactly how i wanted), any suggestions, im going crazy here
eric12341 said:
im having a problem in which my touch pro will not sync or be recognized by ANY type of usb connection (ie, advanced network functionallity unchecked, disk drive mode) it syncs via bluetooth just fine, and when connected to the computer via usb the dialog box asking which type of connection still pops up and it still charges, but no type of connection will go through, i have tried everything except for a hard reset which is what im really avoiding because i have it finally running exactly how i wanted (complete with manila 2.1 on wm6.1 htc 2.01 rom which took me an hour to get working exactly how i wanted), any suggestions, im going crazy here
Click to expand...
Click to collapse
from where i sit, it sounds like u've spent more time fussing with the no-usb problem more than the hour it'd take to "setup" your phone lol.
can you provide any more info? when did it start happening? have you tried from a couple different computers? cables? please give as much information as you have on the entire subject so we dont have to "drag it out of you" as you are the one requesting assistance dont make us do all the work
I have been having same issue with my Touch Pro. It was working great a few weeks ago...then it just stopped...my pc can't sync or recognized the device. I have been doing extensive reading on so many posts...but nothing seems to work. I finally gave up and a did a hard reset last week...guess what? It still did not work. I suspect it might be a hardware failure. Here is what i did and it was unsuccessful:
Install and then uninstall WMD...nothing, bought new OEM data cables (2 to a pack)...nothing, unchecked the advance network functionaility...nothing, someone recommend to swipe the connection inside the phone for possible dust...nothing, tried on my laptop, desktop PC, work PC and my UMPC (all worked before)...nothing, i tried different usb ports on ALL pcs...nothing, started up ICS and connect (supposedly it will install drivers needed)...nothing.
I also notice that some of the chargers I had for it-also stopped working. Only OEM chargers work now.
Also, there are MANY people complaining about this problem as well...
so I use this program, WIFI Remote Access v1 beta 4, freeware to add apps or make changes via wifi. Works great.
http://www.julien-manici.com/
Wish I could find a "fix" for this issue...I can't sent it to Sprint or have a warranty since I flashed it over to Metro PCS...like I said it was working for the past 5 months or so...
drdrewdown said:
from where i sit, it sounds like u've spent more time fussing with the no-usb problem more than the hour it'd take to "setup" your phone lol.
can you provide any more info? when did it start happening? have you tried from a couple different computers? cables? please give as much information as you have on the entire subject so we dont have to "drag it out of you" as you are the one requesting assistance dont make us do all the work
Click to expand...
Click to collapse
well probably last weekend it started happening in which WMDC would just drop the connection and wouldnt reconnect until i rebooted the PC and yesterday morning it also wouldnt connect till i rebooted the pc then it synced and added songs just fine, then i went to school and sat down on one of the computers there and worked on a paper i had to do, this was the last time it worked at all, i got back home and when i connected it to the PC no connections accepted at all, ive rebotted and soft resetted about several times to no avail.
**UPDATE**
i just bit the bullet and did a hard reset and guess what?...........still not working so im resyncing everything through bluetooth and soon will reinstall manilla2.1, after this i will be going to sprint tech support, maybe i can have it exchanged for a TP2
well so yesterday i went up to the sprint store, explained my situation to them and said that ive even done hard resets, they guy had me turn in my phone to him and said that the repair would only take 45mins well 70 passed before i saw my phone again and when i got it back they told me that the reason it wouldnt sync is due to all the 3rd party programs i had installed (only 3rd party program was spb pocket plus) all other installed programs were made by microsoft,sprint and htc. so they did a hard reset and told me it synced their computer fine and that it may be a problem with my computer so got home and it STILL DID NOT WORK!! i even plugged in my axim x51v and it synced without problems,i cant believe i wasted 5 hours of my time and pay an extra $7 for such unprofessional service. they didnt even offer me a new USB cable.
Hey eric,
I have been to other sites and there other members experiencing the same thing. This is the first time hearing it was a 3rd party app...you know it isn't an app if you do a hard reset, which I DID...and it still my pc doesn't recognize it. In my case, it was working great one day...and the next day- it just stopped working.
Now my wif also went haywire. And a hard reset didn't fix that either...
I will be getting the Touch Pro2 soon. I never experience any issues when I had the HTC Mogul...my HTC Pro...well I love it...but i can't deal with the hardware issues...I just replaced my keyboard not to long ago.
Sorry to hear Sprint gave you the run around...
edit: I read somewhere in another post...that sometimes the wifi wire can get unplugged after installing a new keyboard...I opened it up and found the wifi wire (on the back side) plugged in the wrong connector. I must have unplugged it accidentally and then plugged in on the wrong connector. Found the error...now wifi works great.
I've began to have the same issues as well. Last week I flashed vet's ROM and thats when it died. I tried hard resets and other ROMS and its still the same thing so I dont believe it was vet's ROM but more of a hardware issue.
I have no activesync functionality, no flash ability over USB, but charging and disk drive work fine.
hemirunner426 said:
I've began to have the same issues as well. Last week I flashed vet's ROM and thats when it died. I tried hard resets and other ROMS and its still the same thing so I dont believe it was vet's ROM but more of a hardware issue.
I have no activesync functionality, no flash ability over USB, but charging and disk drive work fine.
Click to expand...
Click to collapse
I never had this issue. Only internet stops working with the weather updates and skyfire, Im on metro, I just reflash the cab for the internet and that fixes that. But did anyone else try flashing a new rom like hemirunner426 did? Could be worth a shot to get it working. Sounds like urs is F'ed dood sorry.
well I bought a new usb cable from ebay for only $3.xx and since it arrived my usb functionality was restored.
Its usually a problem with the usb cord. I had this same problem before. Just go to the sprint store and they will exchange the cord for free, they also redesigned the cord do it doesnt keep breaking.
ravioli817 said:
Its usually a problem with the usb cord. I had this same problem before. Just go to the sprint store and they will exchange the cord for free, they also redesigned the cord do it doesnt keep breaking.
Click to expand...
Click to collapse
well they didnt exchange it for me,they wanted me to pay $25 for one ,descarados!!
me too
I have been testing energy and veito roms and started to get the same problem as everyone here having to reboot both tp and pc to get it to connect I get it to sync but if I leave it on it disconnects and I get usb device malfunctioning or unable to reconise device so I called sprint they told me to go to the repair center I pay my tep for 7 buck he told me it I had damaged the usb port the plastic in side was broken it had been like that from when I got it new he said it would cost me 100.00 for the Insurance to get a new one I went to the other repair center said almost the same thing the bull about this is the tep they are suppost just fix the phone no matter how the phone is broke even tho it was not broken so I called sprint they put me thru to tech support they offered me several replacement all junk phones or a refub tp so I took the tp wouldn't give me a tp2 think I am going to call retention and complaine now that I see I am not alone with this problem
I'm suddenly having this problem now.....I have switched to 2 different computers (freshly formatted), flashed to 2 other ROMs via SD card but still no luck with the sync through WMDC.....It charges the phone but will not sync. Any ideas from the gurus??
eric12341 said:
well I bought a new usb cable from ebay for only $3.xx and since it arrived my usb functionality was restored.
Click to expand...
Click to collapse
I also bought the OEM data cable for the TP....no cigar...still doesn't work. Happy to hear you got yours working.
Related
I just tried WM2003SE upgrade, but after erasing message, it just gave connection 101 error!
i tried, hard reset, soft, etc, but no lock it just says:
Serial
v 1.01
if i put it in the cradle, it will show "USB" instead of "Serial",
is this dead? i just bought it and like a hero, tried upgrading
It's not dead.
Put it in the cradle and try the upgrade again.
Don't forget to connect the power charger to the cradle for in case the battry is drained during upgrade.
Regards,
Mark
and if that doenst work try to upgrade it on another pc with active sync
Finally, my advice starts to stick!! :lol:
Have you done lots of upgrading on that particular PC? If so, then it's definitely worth trying a diff PC.
Cheers
Ant
It Worked!
Hi, thanks everyone for your replies, i managed to get it working today on a another PC, looks like its time for me to get another laptop, this one is dying.
It worked sometimes, then cuts off in the middle, then stops working, i tried it all night yesterday, though i lost it all, only had about 2 hours sleep because of that but i tried today on another pc, and it worked the first time.
Probably onboard usb is faulty (although it works with my cable modem, external dvd-rw, etc), but it seems to me, the update/upgrade program needs error-free connection and mine might be ill.
anyway, i downloaded the rom from o2 xda website and updated to that(wanted to upgrade to WM2003SE before it went in coma), i cant afford another crisis , i like my xda 2 too much! :wink:
Thanks for your replies, appreciate it 8)
I don't think it's anything wrong with the hardware. My advice would be to ensure you backup any backup files then uninstall ActiveSync, before removing all registry and folder references to it. Then, reinstall and then see how things go from then on. Glad it's working though now!
Cheers
Ant
Backups
Yup, i've done a backup of the ROM and also the Extended Rom, don't know how to backup or where the Radio Stack is, so i'm assuming its in the main Rom.
The reason i think its the hardware fault is because things like cable modem, dvd rewriters, etc work beneath the drivers, and they do all checksums and checking, with Him upgrade program, it uses ActiveSync APIs, so any hic cups in activesync would be passed down to him upgrade, if activesync did proper data checking and resend data (or might be that the bootloader is limited so it might be limited on what it can do) then the errors could be rectified.
These are all my assumptions. thinking out loud.. etc
I tried reinstalling activesync, etc also created new admin user, tried safe mode with networking (without networking gives TCP/IP error message).
All failed.
i wanted to fix it yesterday night with this laptop, and didnt have access to any other computer, so ended up staying up til late and trying all possibilities, but all failed so i gave up and waited for the next day. came back from work and then tried it on another computer and it went smoothly.
Also tried resetting the xda2 many times, taking the battery out, soft hard cold hot yellow green, tried all, but no luck. :roll:
So i assumed it was a hardware fault, or XP sp2 fault (the other one is a desktop with win2k).
anyway i'll be formatting this xp sp2 soon and putting windows 2k, seems more stable, trying to get maximum mileage out of this laptop.
thanks for the tip though.
Thanks in advance if anyone can come up with something that helps... I can't imagine what that might be though!
This morning I had a stock Mogul... original ROM, no hacks, even had the Sprint S/W on it. It worked fine.
I downloaded the new Sprint ROM 3.35.651.2 and ran it. While running the Mogul rebooted, went to bootloader, then failed. It was then stuck in bootloader mode. I read up and found that a successful flash should bring it out gracefully so didn't troubleshoot much. I tried a couple of times more to no effect. It was still in bootloader mode.
I then downloaded the old 2.17.651.0 ROM from HTC and that wouldn't work either. Still in boot loader mode.
I read somewhere that a guy got the 3.16.651.0 leaked ROM to update even when the others would not. So, I downloaded and tried it. Everything looked good! It was loading the ROM, the bar went across the screen to 100% and then...
nothing. A black screen. Vista loaded some new drivers and seemed to know there was a USB device attached but I couldn't connect to it in any useful way through Explorer and it didn't show up in the Mobile Device Center.
I thought I'd try flashing it again but since the screen was black I was just guessing. I did a hard reset (both soft keys plus soft reset button) and I got nothing... not even the same connection I'd had after the 3.16 update.
Now, I plug in the device and get no USB connect sound or notification in Windows. I get a orange light on the right LED for maybe 15 seconds then it goes out. Other than that one brief LED the thing is a brick as far as I can tell.
Any ideas? I plan on taking it in to Sprint tomorrow and telling them they bricked my phone with their update if I can't figure anything out tonight.
Thanks!
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Geckotek said:
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Click to expand...
Click to collapse
Yes.
FYI... I just left the battery out for about 5 minutes (what the heck, worth a try right?) and put it back in. I get no lights, buttons do nothing, soft & hard reset do nothing, forced bootloader does nothing. The only way I can get the phone to do anything is to plug it in to a USB cable. The orange light comes on for about 15 seconds then goes out. The computer never recognized there is a new USB device attached.
I loaded many custom ROMs on my old 6700 and never had a problem. I leave my new 6800 alone and wait for the upgraded stock ROM and look what happens! Guess I shoulda used a custom ROM instead, eh?
lol sounds like a legitimate "brick" to me. Very strange, and congrats on your new mogul paperweight (i also have one that was a victim of water) haha, good for holding things down on the windy days.
Yup, bricked.
Sprint couldn't figure out how to unbrick it and just gave me a new phone. The new one upgraded nicely and now I have GPS!
Everyone enjoy the upgrade!
same problem
no need to retype what you said. i had the EXACT same problem. phone was completely bricked and continued to crash at 11%. I went to my local store (i work for sprint, and i know a smart tech there) and was told it was kaput. Hard reset, tried to reload other roms, the whole 9 yards. It's a goner, and now i have a new mogul in my hand. I'm afraid to try it again. I'm running vista, and im wondering if that's the problem.
Anyone with vista have the same bricking problem? Is it an issue to directly upgrade from factory rom to the 3.35? My old brick had the current 2.17 or whatever... HALP
Vista
The first time I tried the update I connected the Mogul to my Vista Business 64bit Thinkpad T61p.
The second time I tried it (on the new Mogul) was from my Vista Business 32bit desktop (white box).
I don't know if that helps or not. The second time went smoothly.
On another note... an entertaining one... while I was in the Sprint store today waiting for their tech to confirm that the phone was bricked another guy came in with a Mogul and complained of the same thing. I took the last Mogul they had in stock. Poor guy. I hope they get more soon... there are a lot of people who want GPS and are upgrading their phones. That means there are gonna be some more bricks I'd think.
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
Hello all,
I've been reading this forum for quite a while now, but never registered to post. I was wondering if anyone else's TP died suddenly?
I managed to get my grubby hands on one two days ago at one of our local Best Buy's, and was loving the tablet for the amount of time it worked.
Out of the box, I charged it, installed the 3.02 update, and Preware. I then disabled logging, overclocked it to 1.5 ghz, installed suggested tweaks to speed it up, and a handful of useful applications off of preware.
I also installed the hulu fix off of the preware alpha release channel.
With all of these installed, I had a pretty speedy device that responded quickly and worked great as a browsing device, media player, email client, etc.
This afternoon, I was browsing on another forum, when the TP suddenly froze, and then turned itself off. It did not respond to charging, connecting to a computer, or the hard reset trick (center and top buttons held down). I also tried the instructions on how to unbrick the TP, and they did not work. WebOS doctor also didn't find it because it wasn't being recognized by the computer.
I called HP support, and the agent took 55 minutes to determine that it was totally dead -- eliminating the charger, LCD backlight, and low battery as problems. We tried a couple of resets, and they all failed. HP is sending me a box to ship it back to them for warranty service.
Has something similar happened to anyone else? Hopefully they won't disqualify it for Preware and tweaks being on it, if they ever get it booted. I'm hoping that I'm not SOL, because I don't know if I will be able to get my hands on one anymore.
neel2004 said:
Hello all,
I've been reading this forum for quite a while now, but never registered to post. I was wondering if anyone else's TP died suddenly?
I managed to get my grubby hands on one two days ago at one of our local Best Buy's, and was loving the tablet for the amount of time it worked.
Out of the box, I charged it, installed the 3.02 update, and Preware. I then disabled logging, overclocked it to 1.5 ghz, installed suggested tweaks to speed it up, and a handful of useful applications off of preware.
I also installed the hulu fix off of the preware alpha release channel.
With all of these installed, I had a pretty speedy device that responded quickly and worked great as a browsing device, media player, email client, etc.
This afternoon, I was browsing on another forum, when the TP suddenly froze, and then turned itself off. It did not respond to charging, connecting to a computer, or the hard reset trick (center and top buttons held down). I also tried the instructions on how to unbrick the TP, and they did not work. WebOS doctor also didn't find it because it wasn't being recognized by the computer.
I called HP support, and the agent took 55 minutes to determine that it was totally dead -- eliminating the charger, LCD backlight, and low battery as problems. We tried a couple of resets, and they all failed. HP is sending me a box to ship it back to them for warranty service.
Has something similar happened to anyone else? Hopefully they won't disqualify it for Preware and tweaks being on it, if they ever get it booted. I'm hoping that I'm not SOL, because I don't know if I will be able to get my hands on one anymore.
Click to expand...
Click to collapse
i spoke to an hp rep before the touchpads were killed off and they said that they have no issues with preware being installed and that they will not kill the warranty on it.
Hamspiced said:
i spoke to an hp rep before the touchpads were killed off and they said that they have no issues with preware being installed and that they will not kill the warranty on it.
Click to expand...
Click to collapse
Thanks, that is reassuring. It seems like developer mode is quite easy to access, so I'm hoping they aren't too strict on modifications.
It wouldn't make sense for them to do that. Its not like you rooted it, just some widely used homebrew.
Sent from my PC36100 using XDA App
I was reading in another forum that there are issues with the chargers that come slightly apart during shipping (I guess they separate to allow different ends) and if that is not secure it will not charge... and since it does not charge when its plugged into the PC uses were thinking their touchpads had died.
after the hard reset do you push power on and volume up to get into developer mode for the webdoctor?
jpierson said:
I was reading in another forum that there are issues with the chargers that come slightly apart during shipping (I guess they separate to allow different ends) and if that is not secure it will not charge... and since it does not charge when its plugged into the PC uses were thinking their touchpads had died.
Click to expand...
Click to collapse
I checked to make sure the prong part had not come off of the barrel -- this was not the problem, but thanks for the idea. The battery was showing 80% before the tablet froze and turned itself off.
jlove said:
after the hard reset do you push power on and volume up to get into developer mode for the webdoctor?
Click to expand...
Click to collapse
Yes I did, but neither the hard reset nor the developer mode seemed to take.
It's off to TRC today to El Paso, TX by 2nd day UPS air. I got a UPS box in the mail this morning, took really good pictures of the tablet's pristine condition before sending, and then packed and sent it as instructed.
Sounds like some bad luck. I have the same setup on mine, with the exception that I'm running Warthog's 1.7ghz OC, and I haven't had any troubles.
I wonder how long it will take to get your replacement? I'd appreciate it if you kept this thread updated with how the return process goes.
seboj said:
Sounds like some bad luck. I have the same setup on mine, with the exception that I'm running Warthog's 1.7ghz OC, and I haven't had any troubles.
I wonder how long it will take to get your replacement? I'd appreciate it if you kept this thread updated with how the return process goes.
Click to expand...
Click to collapse
I'll certainly keep the thread updated with how the return progresses.
So far, it's been two days since I called and the rep determined that it needed to go in for service. I received an empty box via UPS this morning, and it looks like it's going to a 3rd party service center in Texas.
any word back yet?
I am also interested. Be sure to let us know how it goes.
I'm also interested in this, do you think they'll be able to tell you overclocked it?
maaaan, think this has happened to mine just last night. it was on about 18% battery, I shut it down iirc, plugged it in to charge and I went to sleep. today it seems to be as dead as yours was
Mines stock though, all I've done was the 3.02 update a week or so ago.
EDIT: Solved thanks to this thread, just had to hold power + home for about 25 seconds and it came back to life.
No updates yet -- I called HP last week, and all the rep was able to say was that there is a 7-10 day processing/repair time, and they could not give any information within that period. Tomorrow will be the 11th business day since they received it, so I'll try to give them a call in the afternoon and see what's up. If I don't get a chance to call them tomorrow, I will on Tuesday.
I returned mine last Friday but they told me the estimated turn around time would be 3 to 5 business days. I'll update when I get it back.
I called HP yesterday (12th business day), and all they could tell me was that it was still under repair. They could not tell me when it would be done, but told me they would keep me up to date (which I doubt).
On another note, it seems like HP's reps (at least the WebOS Butler line I've been calling) seem to barely function in English. I really don't mind when tech support people have a strong accent, but the last two reps I talked to could barely communicate what was going on with my Touchpad or take down any information I have them. The second to last rep actually used the word "negro" to verify the "N" in my email address.
Mine died today too. OCed with Warthog to 1.5. Yesterday before it died, battery was all the way to 0% but it was charging and i got it to turn on. It was charging all night on the dock. Today when i got home, it just completely died. Did the entire troubleshooting with HP support and determined that its completely dead. They are sending a box for me to return for a repair.
is it really safe to overclock then?
warthog, f4 and f15 are for beta testing purpose.
when you install one of these, you accept the risks.
only uberkernel is a public kernel that OC the touchpad without risks.
I got my Touchpad back today! It looks like I think I got a refurbished one, since the serial number on the device (in the sim-like slot) isn't the same as on my original box.
However, it seems to be working nicely.
It ended up taking much more than the promised 7-10 turnaround time HP promised, but I do have a touchpad again. There was no sort of report or invoice in the box, so I do not know that happened with the old one that caused it to shut off and not turn back on again.
I don't know if they ever restored power to the old one, so I don't know if HP knew I had preware on it and that it was overclocked to 1.5 ghz, but there is no indication that HP had a problem with my old tablet I sent it.
I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
TallgeeseIV said:
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
Click to expand...
Click to collapse
This topic can be closed now. I looked up a video (http://www.youtube.com/watch?v=FfvOTFssDMM) of the swapping process and saw how easy it is, so i just went ahead and tried it, and it totally worked, so now it's charging fine again. Thank you to anyone who viewed this and hopefully this can help someone in the future.
I didn't read all of that. I was at a concert last night. But here what I know about the not charging thing.
In my experience
1.all the good galaxy phones do it.
2. Its not that it wasn't charging. Its that vzw turned the power up on the modems. If your in a low service or weak signal area your phone will actually drain the batter faster then you can charge it.
So if you notice this is happening. Switch your phone into airplane mode. Or turn off mobile data and let it charge for a while.
I have read about a few case's where the usb ports where disconnected. But I think the crazy fast radio battery drain is way more common.
I don't know if its the same for other carriers but I know a note guy a s4 guy and 2 other note 2 guys we all had the same problem with it.we are all Verizon too.
The original modem flash helps a lot but the 2nd one that went out ota is stronger in weak signal areas so we all use it and turn off our data if it gets to much.