The message below is a message I sent to the HTC Customerservice. Tomorrow I'll go back to the store and again try to get a new magic or maybe a hero. I'm fed up with this complete inusability and was wondering if any of you had a clue what the problem was.
I'm having big problems with my HTC Magic again, so i'll include a copy of a post I made on a forum the last time:
Yesterday I got my phone from the Vodafone store @ Groningen, Netherlands. I used it normally, installed one or two mainstream programs from the market and did nothing else to it. Yesterday @ about 20:00 the trackball lit up putting out a continous bright white light. I searched the internet for a feature that could do this because I could still use the phone. Besides the trackball there was nothing noticeably wrong with it. Because I found no such features I decided to turn the device off and on again. Once I pressed on the red button to get it on, the trackball immediately lit up. When the red button was pressed for about 3 seconds a blue led lit up at the top of the device and the screen stayed black, nothing happened. I pulled out the battery, put it in again and pushed the red button for 1 sec. The trackball, again, lit up but the blue light didn't pop up. Now when I ticked the red button the blue led would flash and go off..
The vodafone store said I was the first to bring back a HTC magic, they contacted the repairservice and they said they didn't even know the magic had a code in which the rainbow led emitted blue. They treated it as DOA and gave me a new one. This one works fine, I'm very happy with this phone but still wondering what was wrong with my last.
Anyone any guesses?
Today:
Now I'm having the above problem for the second time! I'm getting really tired with the complete inusability of these units. I know a thing or two about computers but I'm afraid to 'flash' or 'fastboot' the phone as many forums say online in fear of losing warranty.
The only clue I have is the one resemblance to the first time I had this problem. I work at a restaurant and at this restaurant I tried to connect to the wireless network that is used for our pda's that are connected to our register which we use to take orders right at the tables. The phone recognizes this as an open network but when it tries to connect it does nothing. You don't even see that it fails, it simply doesn't do anything to connect. A while after connecting the trackball lits up and the above problems occurs.
Tomorrow (monday) I'm going back to the store and again try to get a new one or replace it for a hero, hoping these units won't have this annoying problem.
Please help me in finding out a solution for this problem!
Click to expand...
Click to collapse
Wrong forum, and try a static IP instead of getting one through DHCP on a probably cheap and stupid router/AP.
Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or i will be forced to ban you for 3 days or till you learn.
Thanks
Thread Trashed!!
Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or i will be forced to ban you for 3 days or till you learn.
Thanks
Thread Trashed!!
Related
hi,
newbie in this forum and newbie in using a phone running an operating system. please help.
bought the phone in late June 2008, received it before the month ended, installed TomTom Navigator 6 on it and tested the various hotspot around my place, happy with it and stashed the phone on a safe place in the closet as T-Mobile don't have 3G service. then last week I decided to get an ATT plan (can't stand the iPhone 3G ad) so I can tasted the blazing HSDPA speed.
last week on Wednesday I use the phone as a GPS to get me to a hotel I'm staying near the White House. it got me there no problem. then the next day, the horror started. I was trying to plot a walking course to many of the nearby "stuff to see" and the phone just sits there saying that it can't get a valid GPS signal. then I tried to go to Google Maps using IE. the screen started scrolling, literally scrolling, then when it stopped, whatever usually on the top ended up in the middle of the screen, the bottom ended up on the top, and the screen was "split" in 2 with the edges staying dead center. so I thought, ah, this phone is just too tired, it ran out of memory (as all windows always does ignoring how much ram you put, at least in my experience), so I press the power button to let it do the light sleep. when I turned it back on, the phone seems to work the problem out and I tested it by going online.... guess what, the screen started scrolling again and even adding "I can play dead". the screen is not responding to anything (touch, tap, swipe, rotating the scroll wheel, pressing the buttons) beside the power button that seemed to turn the display off. when I turned it back on, the screen just gives off some light on the sides, but that's it, the screen is blank. taking out the battery doesn't even fix the "blank" screen thing. the device seemed to work out the problem after I left it unused for about 2-4 hours, but then it started again when I tried to do anything (all I ever do with my Touch Cruise is going online via wifi and/or att data plan, plus using the phone as GPS).
even after resetting the phone to a factory default doesn't help (did it this morning via a representative guidance). so I'm stumped. within a week, the phone basically broke, then how about another year? will it become bits and dust?
anyone can give me advise? one representative I talked to said that I can get a replacement for the phone but the last one I talked to said that HTC only have an option of repairing the phone but not replacing one.
thank you to all who reads.
Really weird.
Try to get replacement, if not possible, get it repaired.
If hard reset / factory default did not help... It does sound to me like malfunctioning device.
On the other hand... is it provider locked device or unlocked one?
I guess it's unlocked, but I'm bit confused since you mention both T-Mo and AT&T...
I do hope that there's original ROM on it...
For what it's worth, my XDA Orbit II has just developed the exact same fault. I tries soft and hard resets, re-flashed with 6.5 rom and then a 6.1 version, all to no avail. It goes through the boot sequence and asks for a screen calibration - if you ignore the scrolling screen and tap in the right places, the calibration is accepted (which makes me think it's not the digitizer. The screen itself seems to be fine - no missing pixels, cracks, - it displays everything it should only with a constant vertical scroll. If it had a vertical hold knob, I could fix the problem.
Really weird, it was working fine this morning and after sitting in its cradle for a couple of hours it is now like this.
Any ideas as to how I might cure the problem would be gratefully received.
Hello,
I read several threads over the span of five hours to still be left where I started (almost). I will explain the background to the situation I'm in; and the question will be clear towards the end.
A few days ago; my phone would not turn on UNLESS it was plugged in (wall/computer). I found this very unusual of course, and contacted Rogers. They explained that it would be a software or hardware issue; and to check if it's a software first.
I quickly backed up all my photos and things onto my computer, and began the Factory Restore tool. However; it did nothing besides clear me of all my apps; and settings (of course), yet I still remained at 2.3.3 Firmware.
Rogers continued to say to use Kies, and try to fix it through there. Then I completely forgot that my Infuse is with "EZUpdate" which is not even being picked up by the program itself which I later downloaded. I sat back in my chair to think for a bit, and thought; oh my goodness; a firmware update could have been a jail break I installed a few months ago (learning it's called Rooted for Androids). I instantly began looking online which led me to this site, and eventually learned that I can "un-root" my phone.
Now I'm in bigger trouble. PRIMARY QUESTION/CONCERN BELOW
I downloaded the GTG_s_Ultimate_Unbrick, and it actually worked. My phone turned on without the USB wire or anything. Then a sweat quickly rolled down the side of my face when I saw "AT&T" with a bright white screen. Shortly after it followed to the white "Samsung" with black screen background. After that, nothing else happens.
I am losing hours of sleep, and I work in three to four hours from now trying to figure out how to return this back to a Rogers phone.
Everything I'm trying from links like http://forum.xda-developers.com/showthread.php?t=1326143 and it's failing. I'm on the verge of tears that I have actually lost a phone that barely lasted me six months; and it's too costly to replace.
________________
Please help, I beg of you. If there is a solution; or a step by step process; please post here. I will get back to you as soon as possible when I return from work. I have already pinned my thread, and will be returning to it regularly.
Thank you very much for any future assistance, and have a wonderful day/evening in the meantime.
~ Yujiza
-.- go back to android development and download the rogers firmware. you used att firmware.
Sent from my SGH-I997 using xda premium
Yujiza said:
Hello,
I read several threads over the span of five hours to still be left where I started (almost). I will explain the background to the situation I'm in; and the question will be clear towards the end.
A few days ago; my phone would not turn on UNLESS it was plugged in (wall/computer). I found this very unusual of course, and contacted Rogers. They explained that it would be a software or hardware issue; and to check if it's a software first.
I quickly backed up all my photos and things onto my computer, and began the Factory Restore tool. However; it did nothing besides clear me of all my apps; and settings (of course), yet I still remained at 2.3.3 Firmware.
Rogers continued to say to use Kies, and try to fix it through there. Then I completely forgot that my Infuse is with "EZUpdate" which is not even being picked up by the program itself which I later downloaded. I sat back in my chair to think for a bit, and thought; oh my goodness; a firmware update could have been a jail break I installed a few months ago (learning it's called Rooted for Androids). I instantly began looking online which led me to this site, and eventually learned that I can "un-root" my phone.
Now I'm in bigger trouble. PRIMARY QUESTION/CONCERN BELOW
I downloaded the GTG_s_Ultimate_Unbrick, and it actually worked. My phone turned on without the USB wire or anything. Then a sweat quickly rolled down the side of my face when I saw "AT&T" with a bright white screen. Shortly after it followed to the white "Samsung" with black screen background. After that, nothing else happens.
I am losing hours of sleep, and I work in three to four hours from now trying to figure out how to return this back to a Rogers phone.
Everything I'm trying from links like http://forum.xda-developers.com/showthread.php?t=1326143 and it's failing. I'm on the verge of tears that I have actually lost a phone that barely lasted me six months; and it's too costly to replace.
________________
Please help, I beg of you. If there is a solution; or a step by step process; please post here. I will get back to you as soon as possible when I return from work. I have already pinned my thread, and will be returning to it regularly.
Thank you very much for any future assistance, and have a wonderful day/evening in the meantime.
~ Yujiza
Click to expand...
Click to collapse
Although after a little searching you would no doubt find this here is what you need:
http://forum.xda-developers.com/showthread.php?t=1326143
Thank you for the assistance you two!
I'm on the search for a retail version of gingerbread 2.3.3 for Roger's Infuse 4g.
Thanks once again,
~ Yujiza
Been a watcher on the forums for awhile, now I actually had to sign up and get some help, LOL.
Anyway, dropped my s2 skyrocket, noticed that it kept trying to reboot every now and then when I used it the same day. The next day, I plugged it in in the evening, and shut off, rebooted, but the screen would go black and the phone would vibrate with 2 seconds in between vibrations. It gets to the "Samsung" word, then the screen goes black in the style of an old tube TV (with the thin white line at the end). Then the vibrations start. So far a useless phone. Took it apart and checked connections carefully (I'm used to working with processor boards quite a bit).
What do you guys suggest? Damaged memory? Should I attempt to reflash? Stuck power button (seemed ok, though)? Bad screen?
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
creepyncrawly said:
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
Click to expand...
Click to collapse
Oh, thanks for the heads up. Yeah I just figured out that the i727 isn't in "Top Devices" or "Legacy," so you have to go to all forums. Ugg. Already moved. Thanks to whoever notified mod.
Anyway, yeah, any help would be AWESOME. What physical damage would prevent booting past the "Samsung" screen and default to a black screen that intermittently vibrates?
I'll be honest, if ur asking that question probably something u don't have the current skill set to fix. Try to Odin back stock, but if it started post-drop you may be SOL and in need of a new phone.
Got it into download mode after multiple failed attempts. Each time I would get it into download mode, the screen would shut off after about 5 seconds of being on. I tried several combinations of plugging it in first, then installing the battery, or holding down the button while I plugged it in with no battery, etc. I had just given up after getting it into download mode briefly for the 20th time, when I gave it one more go while rocking the on and off button. Technically that is recovery mode, but I let off right before plugging the phone in and it hit download mode and stuck.
So what I am thinking is the power button got jammed internally. I have heard of it happening on other forums. Even though it looks good and clicks upon external examination, the pressure circuit on the inside might be in contact. Anyway, just one theory.
For future though, I did discover that you don't HAVE to have the USB unplugged prior to getting into download mode. On the contrary, a power source must be present in order to register that the keys are pressed PRIOR to initiating USB input. Thus, you can actually remove the battery, plug in the USB (power source), then hold the volume keys while replacing the battery. Goes into download mode that way, too.
Will keep you guys updated. Might need a bit more help if the phone starts acting up again.
At this point, if the Download mode still holds ok, should I consider CyanogenMod, or is it easier to get back a good ROM from stock?
icenight:
Thanks for the reply. I don't understand much about smart phones or how they work, but trust me when I say I have had AMPLE experience with electronics, circuit boards, hardware, etc., particularly in the computer/laptop world. I code quite a bit of websites, and understand almost all things networking and OS. Just never really got into it with the phones.
Getting super excited to see the sheer amount of modding you can do though. Would love to break into a hardware modding world if it ever comes available. That's where it's at with electronics for me.
Well glad u got it sorted, lucky guy you are lol.
As for boards and the like, if it didn't work I would've suggested replacing the motherboard and/or power daughter board. But for a skyrocket may not be worth the money.
Since you're a hardware guy, maybe mess around with the phone and JTAG? Finding a way to unbrick without it would be very helpful
Since the problems started after a physical damage (fall) , I wonder how would Odin or wipe and flash might work !
Definitely a hardware damage...
Yeah, it kinda puzzled me, too. I believe the power button might have been internally stuck, but that's just one idea. Could have been a loose connection, too.
Can you lose some solid state memory with firmware on it, but the SS memory still be OK to right another copy on?
More than likely it was your power button
Sent from my SAMSUNG-SGH-I727 using xda premium
Alright guys, I had a conversation in Ax's "Run ROMs on different Carriers" thread, but I really want to get to the bottom of my issue, whether it be a hardware issue, ROM related, OR user related.
I've been having an issue with my phone the past few days. Started out it would read "invalid sim, need to reboot" or something along that. Anyways this was after flashing a nightly and I figured, OK, it's a nightly i'll live with it. Eventually my phone just started to power off/reboot all by itself; not real consistent but it was happening more than I would like. Today, the S*&% really hit the fan. I flashed a nightly Wednesday night(i'm not going to say which one, because i'm not sure if it was from the ROM itself or if this was a hardware issue). Anyways, Friday at about noon or so, I open a game to play on my lunch break, I get distracted so I lock my phone to attend to something else. I go back to my phone and it is powered off, now totally unresponsive to anything. I pull battery and try to restart, when I place the battery back in the phone it automatically reboots(WITHOUT ANY BUTTON PRESS) I thought to myself ok this is kind of weird. I try rebooting by using power+vol up...absolutely nothing, it's just a brick. Well, I pull the battery again, hold vol up thinking it will go into recovery...nope, it will boot for a sec or two, just enough to get the blue lettering on the top left of the screen then shuts off again. OK, let's put this b*&*h into download mode and see what happens. it goes into DL mode, all the way to the point of where it says " do not turn target off" then shuts down. I did both of these multiple times, with different batteries as well, plugged in and not. It won't stay on for a computer to recognize it. Someone suggested a stuck power button, I don't think so; it feels the same as it always has.
I was fortunate enough to be able to get another S4 with a busted screen so I switched out motherboards. I have a working phone again...which is all I was worried about. I've flashed quite a few ROMs, I follow procedure to the T when flashing... What do you guys think...hardware issue...user issue...ROM issue? I'm very curious to know because I don't want this happening again, obviously. I would even send the phone out to someone to play with(mind you, the screen doesn't work and the silver bezel is crappy because I just used my original one).
I would say stay away from whatever ROM you flashed. This could also be a hardware issue. I had my old note just randomly shut off on me and was unresponsive as well. Finally got it to boot and reset it. But in your case I would stay away from that ROM and maybe find something more stable. So as this is unknown to what happened I would not blame either. Sorry to hear about your bad experience.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Soup_Nazi said:
Alright guys, I had a conversation in Ax's "Run ROMs on different Carriers" thread, but I really want to get to the bottom of my issue, whether it be a hardware issue, ROM related, OR user related.
I've been having an issue with my phone the past few days. Started out it would read "invalid sim, need to reboot" or something along that. Anyways this was after flashing a nightly and I figured, OK, it's a nightly i'll live with it. Eventually my phone just started to power off/reboot all by itself; not real consistent but it was happening more than I would like. Today, the S*&% really hit the fan. I flashed a nightly Wednesday night(i'm not going to say which one, because i'm not sure if it was from the ROM itself or if this was a hardware issue). Anyways, Friday at about noon or so, I open a game to play on my lunch break, I get distracted so I lock my phone to attend to something else. I go back to my phone and it is powered off, now totally unresponsive to anything. I pull battery and try to restart, when I place the battery back in the phone it automatically reboots(WITHOUT ANY BUTTON PRESS) I thought to myself ok this is kind of weird. I try rebooting by using power+vol up...absolutely nothing, it's just a brick. Well, I pull the battery again, hold vol up thinking it will go into recovery...nope, it will boot for a sec or two, just enough to get the blue lettering on the top left of the screen then shuts off again. OK, let's put this b*&*h into download mode and see what happens. it goes into DL mode, all the way to the point of where it says " do not turn target off" then shuts down. I did both of these multiple times, with different batteries as well, plugged in and not. It won't stay on for a computer to recognize it. Someone suggested a stuck power button, I don't think so; it feels the same as it always has.
I was fortunate enough to be able to get another S4 with a busted screen so I switched out motherboards. I have a working phone again...which is all I was worried about. I've flashed quite a few ROMs, I follow procedure to the T when flashing... What do you guys think...hardware issue...user issue...ROM issue? I'm very curious to know because I don't want this happening again, obviously. I would even send the phone out to someone to play with(mind you, the screen doesn't work and the silver bezel is crappy because I just used my original one).
Click to expand...
Click to collapse
Im saying nothing for sure, but a stuck power button feels just like normal. I had this issue on two separate samsung phones (they are known for this issue). I thought it was just bs, but i decided to tear it down and check. I used a q-tip and everclear and got plenty in there, wiggled and pressed the button for around five minutes. Re assembled, put the battery in and sure enough, the problem was gone. You cant always feel the button sticking. But hey, if you are offering the remains up, ill take em! I would gladly pay $200 for a replacement screen for it to test on.
Sent from my Nexus 7 using XDA Premium 4 mobile app
rebel1699 said:
Im saying nothing for sure, but a stuck power button feels just like normal. I had this issue on two separate samsung phones (they are known for this issue). I thought it was just bs, but i decided to tear it down and check. I used a q-tip and everclear and got plenty in there, wiggled and pressed the button for around five minutes. Re assembled, put the battery in and sure enough, the problem was gone. You cant always feel the button sticking. But hey, if you are offering the remains up, ill take em! I would gladly pay $200 for a replacement screen for it to test on.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Someone beat you to it, Rebel, sorry...just took the first poster or PM that I got. I got the message overnight otherwise I would have posted in here.
I kinda played with the power button when it was tore down, however I didn't use any alcohol on it but that is a good idea.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Edit: Used some IPA on the power button this morning, soaked it pretty well, pressed the button many many times with varying pressure, with a hard pointy object etc. etc., jiggled side to side, tried every option I could to get it unstuck (if that's what it is) and still doing the exact same thing.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Mods, I'd like to politely request this thread to be closed...no use for it now. Thanks.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey y'all, so I'm not sure how well hardware related questions go down on here usually, but not sure where else to ask. So I have about 2.5 Samsung Galaxy s6's. All were given to me at different stages slash periods of time and none of them exactly work fully. Where I am at now is sort of realizing that either: 1. I have to faulty digitizers, or 2. the one battery I have between them is completely shots, or 3. a combination of one and two as well as some other s*** going on.
So what I have for parts AR, two motherboards two digitizers, three bodies, and one battery. I get kind of the same issue switching between the motherboards which is this: I will plug the phones in to my computer and it will read them and say something like SM and then the numbers that represent the s6, and I'll have a either red l LED for a while which will then turn green after a while charging, or a blue LED from the get-go which I believe just stays blue the entire time. Now, the weird thing is that neither of the phones will turn on, however, whenever I push the home button with either digitizer or either motherboard, it will cause the LED to turn off, but will not cause the phone to stop being recognized by the computer. When I say recognized by the computer I don't mean it shows up in the my PC folder, like where I can access the files and such, it just shows up in the device manager, thus giving me the impression that it never actually turns on. This also happens if I end a press up on the volume at any point in time. Also worth noting whenever I unplug it from the computer or just from the charger, the phone will power off completely as in not be recognized by the computer. So, any ideas? I'm thinking of just selling the phones as is maybe for a 150 total for everything but I'd like to fix that myself if it's just something as small as a battery issue. the volume up button and the home button turn the phones off though, is what really perplexes me. Thanks for any insight, much appreciated for the read and have a good Thanksgiving.
DeepPuddles666 said:
Hey y'all, so I'm not sure how well hardware related questions go down on here usually, but not sure where else to ask. So I have about 2.5 Samsung Galaxy s6's. All were given to me at different stages slash periods of time and none of them exactly work fully. Where I am at now is sort of realizing that either: 1. I have to faulty digitizers, or 2. the one battery I have between them is completely shots, or 3. a combination of one and two as well as some other s*** going on.
So what I have for parts AR, two motherboards two digitizers, three bodies, and one battery. I get kind of the same issue switching between the motherboards which is this: I will plug the phones in to my computer and it will read them and say something like SM and then the numbers that represent the s6, and I'll have a either red l LED for a while which will then turn green after a while charging, or a blue LED from the get-go which I believe just stays blue the entire time. Now, the weird thing is that neither of the phones will turn on, however, whenever I push the home button with either digitizer or either motherboard, it will cause the LED to turn off, but will not cause the phone to stop being recognized by the computer. When I say recognized by the computer I don't mean it shows up in the my PC folder, like where I can access the files and such, it just shows up in the device manager, thus giving me the impression that it never actually turns on. This also happens if I end a press up on the volume at any point in time. Also worth noting whenever I unplug it from the computer or just from the charger, the phone will power off completely as in not be recognized by the computer. So, any ideas? I'm thinking of just selling the phones as is maybe for a 150 total for everything but I'd like to fix that myself if it's just something as small as a battery issue. the volume up button and the home button turn the phones off though, is what really perplexes me. Thanks for any insight, much appreciated for the read and have a good Thanksgiving.
Click to expand...
Click to collapse
dang man, id just sell em unless you want a winter project. I just bought a Sunfire sub that has some issues for a winter project, but thats because im a dork and i like that kind of stuff. Anyways, my opinion is just to sell it and get something else that works. I had a buddy offer me a HUGE pile of phones and their respective parts to fix them for like $200 and i gave a hard no.
Damn never heard of such an issue? I'd had hoped that the volume up key as well as the home button both restarting (or, turning the LED off for about ten seconds at least) would have been some kind of dead giveaway, if not just a straight up common occurrence, haha. I even got ANOTHER S6 last night from a homie (asked her if I could borrow the battery lol, she just gives me the whole broken phone) to try and switch out parts, which I'm gonna give a quick shot at tonight at least. But man, no responses other than hours has me quite discouraged :') lol thanks for the time to read at least tho my dude ?