I purchased the HTC one from a sprint store. It is the M7_wls hboot 1.44.00. I promptly rooted it by unlocking the bootloader with fastboot and installed TWRP and cyanogenmod 10, since I used and loved cyanogenmod7 for 3 years on my EVO before physical damage and processing inferiority finally made me throw in the towel. It was perfect. beautiful. best device and ROM combo I ever saw. The HTC one and cyanogen 10, a match made in heaven. But then, quite unexpectedly, after allowing the phone to die on a job site one day, it would not take a charge. The good news is that sprint will not attempt to open the phone and so no unrooting was necessary to replace it. In fact they did it there in the sore since I was within fourteen days of the original purchase date. No removable battery! It was their contention, and I tend to agree, that it simply became unseated within the case, although I hadn't dropped it. fine. new phone. I once again unlocked the bootloader and installed TWRP and cyanogenmod 10. used it for a day (which was quite cold and humid, but I was inside primarily) and the audio stopped working. No music, no in-call audio. While frantically texting customers, I managed to download the nightly cyanogen update and flash it. My in-call audio came back, but ringtones, notifications, music, games and all other possible audio remained null.
I unrooted it yesterday by running the RUU in a virtual machine (I use a mac) and, even returned to stock, no sound. In-call audio remained (thank god). I took it in again and after the obligatory sea of clerical errors, sprint ordered me a new one. I really don't want to go through this again. I love the phone, but business is suffering. Is it possible that either of these issues were my fault? I've heard the inside of the M7 is quite convoluted and littered with coaxial cables like older HTCs and I did drop the second one twice. It had a nice case and simply slid out of the angled, inside breast pocket of my coat maybe three feet onto the floor each time. No such occurrence on the first. It makes sense what some are saying that the sound card simply became disconnected inside the case, but now I'm wondering if I'm mussing the root up somehow. My new phone will be here in a few days and I'm simply never going to use Sense 5. I'd rather eat discarded blowpops out of a sandbox. How can I make sure this doesn't happen again? Is it possible that these are both hardware defects and I'm the most unlucky customer ever? I see minimal cases of the latter issue occurring on the stock ROM, but it does happen. Usually it is fixable however. Mine was definitely not. Are these phones as unreliable as they have been for me? They seem to really impress even the picky crowd, so I'm thinking no.
Related
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
Hello my fellow android hackers, I need your help. Recently, my touchscreen has been completely unresponsive at the top of the screen, near the notifications bar area, but three times as thick. The problem with this (Besides having to go to my homescreen every time I need to access my notifications, or having to go into landscape mode) is that It often renders my phone useless. Often times when I select an object or slide across homescreens, the UI will select an object at the top of the screen. Shortly after, I will be unable to select anything on the screen, and if I try, the UI will select something at the top of the screen and will begin erratic movements around the homescreens, web browser, and almost any touchscreen interaction. This movement will occur whenever I try to interact with the phone's touchscreen whenever it is in this state.
This is not native to any rom, I've tried reflashing and trying many different roms. I know the touchscreen malfunction is native to the hardware, since I've tried reflashing the 2.xx.x.x.xx.6 and the 2.xx.x.x.xx.5 ruu. I think I will need to replace the touchscreen, so could anyone direct me to where to buy the part, a website to install the part, or both. I'm pretty sure I can find how to install the part, just not where to get it. Also, I'm not sure if it's a problem with the inner or outer lcd screen.
ANYWAYS, this problem is more common with the HTC Hero GSM, but HTC has said that some hero's have bad touchscreens.
Heres a link to a video demonstrating the problem. (I am running CM 6.0.0 test 2, it's a great rom)
http://www.youtube.com/watch?v=1ORe2rjWt7A&feature=related
This is with the hero cdma, but the broken area is on the side of the screen, not top.
http://www.youtube.com/watch?v=JYQnCOAtTLs&feature=related
This is to the GSM hero, but the issue is with the bottom of the screen.
This is a problem native to the HARDWARE, and occurred during normal use of the phone, just shortly after watching youtube videos and browsing the web.
Could anyone even direct me to a location to get this repaired, since the Sprint store said there was no way to fix it, but online many people had this issue and got it repaired by HTC customer care. Could anyone confirm this, or state the time length of a cdma sprint hero warranty purchased from Sprint in the US?
(Occassionally the phone works, but only for a short while and then It starts acting up again, usally during data use, like web browsing or using several apps)
Any help would be appreciated.
Is it humid where you live? Do you use a screen protector?
Sent from my HERO200 using XDA App
Yes, it is humid, and I don't use a screen protector. I think the processor was overheating during heavy use (watching video, etc) and I left the screen on for a while. I think that this damaged the screen.
Have you tried a different rom, or maybe flashing one of the new any kernels for your current rom? Almost sounds like it could be a driver issue. I did have a friend that had this problem on his stock hero, and sprint replaced it for him. If you ruu and it still does it, make a scene, they will replace it.
had the same problem with my hero, unresponsive directly below notification bar, as well as becoming completely useless randomly. took it into sprint, and the tech seemed to know exactly what the problem was. an hour later, it was fixed as well as my peeling buttons replaced...free. apparently the touch sensor was going out and it must happen more often than not considering the tech new what the issue was immediately.
Ok, I will not start another rant and rave I promise, BUT, I will say be very careful going to Sprint with a problem. I just had the same exact problem, I had to go to FOUR different stores, and finally instead of fixing my SPOTLESS Hero, they ordered me a "new" one, it has scratches all over the screen, the back cover hangs off, my hardware buttons(home,menu,ect...)are lose, and the metal where the ear speaker is is sticking out, be very careful dealing with sprint.Oh, yes this all happened in the last 4 days, they didnt give me a loner phone, and it took me 3 days to get this piece of **** they call a new phone. Just my experience.
So, I bought my wife a nook Color. She's an English teacher and she's embraced technology as a teaching aid, so I figured it would be perfect.
I did not modify the nook AT ALL. All I did was put some ebooks on it from around the web, loaded onto an SD card. Nothing unusual beyond it being a few THOUSAND files in .epub and .pdf format.
ANYHOW, she's seen issues.
First, she saw issues where the nook thought she was tapping constantly in the exact same spot. To be exact, the spot where the 'b' is. If we hit the nook home button, it kept clicking the book that was in the exact same spot as the 'b' button was. Shutting the nook off entirely fixed it.
Second, frequent lockups during normal use. Sometimes in the browser. Other times flipping through PDFs. Android itself usually wasn't locked up since we could hold the power button and get the dialog asking us if we REALLY wanted to shut it down, but the nook overlay GUI was certainly dead to us. Again, a hard reset (power button until it shut down) and power up fixed this without a problem.
At this point, we thought it would be a good idea to swap this out as a potential hardware issue. We bought it from Best Buy, so back to BB we went and swapped it out for another nookColor.
Now, we're seeing more issues, but different ones.
Third, the power cable doesn't seem to want to fit properly into the USB port like the last one did. A little play and it slides in ok, so no big deal.
Fourth, buttons are sensitive to where it thinks we tapped twice. I don't think this is a real issue since it's a matter of learning the device I think.
Fifth, and fairly important... this only happened once. It lost all sound. We have a child who's just over 1 year old, so the B&N's stance to try to set a high focus on that aspect was awesome, especially the childrens' books with the professional voice actors.
Now, it's my opinion that it's just an OS that was released prematurely. I think many of these issues will be fixed with the first update. Am I alone in these issues? Has anybody else seen anything similar?
For the record, I've taken a very hands-off experience with this since I'm extremely technologically savvy, and I wanted my wife to be able to run it without needing me there. None of these issues have persisted throughout a shutdown-reboot except for the sound issue. It required an 'erase and unregister' through the device info in settings.
I bought a NC for myself and a day later my wife bought one at the same B&N. The one she bought had terrible screen flicker so we exchanged it for another. The second NC would FC on her ebooks, drop wifi, and would make a cheap plastic creak when pressed to tight on the left side. Thinking the bad batch idea we exchanged the NC at a different B&N and the third one had the same screen flicker the first one had so we turned around and went back and exchanged it for a fourth one. Finally. The fourth one worked fine and does not creak at all.
I wouldn't necessarily say your problems are OS related. Android has been running on a lot of portable devices for quite some time now. I think it can be considered a mature OS. The ebooks we have that caused the second NC to FC work flawlessly on my NC and the new fourth one. Rebooting the second NC didn't help with the FC'ing and wifi dropping. So we felt the problem was hardware related like the screen flickering. Our feeling was we didn't want to mess around, it's $250, we were determined to keep exchanging until we found one that worked.
You might want to think about exchanging it for another. Who knows how many will remain to be in stock as the date gets closer to Christmas. I wouldn't recommend trying to exchange it after Christmas, you may end up getting a re-shrink wrapped one that was returned for some unknown reason.
android is becoming mature but the nook is oem'dto death. This os is crap by all accounts! Once something better is available we will see improvements
The screen thing is turning out to be kinda common.
Good news is.... its being blamed on an oversensitive screen, dirt and or moisture. Any tiny bit of the latter two. Usually fixes itself right up with a wiping or a screen protector and a lock/unlock of the device.
I have experienced and read about the charger cord too.....have yet to see any problems because of it but do worry about having to re-solder something sooner or later.
I have to wonder about the usefulness of a Nook Color as "a teaching tool" right outta the box though?? Besides making your wife a walking reference that is.
was it plugged in? There are issues when plugged in and tapping.
I also had to "wiggle" the USB cord to get it to fit into my Nook as well.
I had the creak on the left side as well. Haven't had a chance to exchange it yet, but it's on the radar.
I don't mean a tool to use with the students, I figured it may make things easier on her if she's got ALL of the books she uses with her students on a single table that she can carry around the classroom referencing instead of needing 30 different books. I don't know if it was a fool's idea yet or not! It's the thought that counts.
Defiantly save on the back!!
Nice one, guess I just want mine to do everything
Galaxy Tabs.....Worth every penny!!
My first nook had the sound problem, except it would happen every 15 minutes and only hard reboot would fix it.
I replaced it and the second works flawlessly (as far as I can tell).
So I purchased an HTC one for my girlfriend via Swappa so she wouldn't lose her data plan. She was coming from an iPhone 4s so I picked the HTC one for a similar size/feel but desired the Android platform. Anyway, I've had nothing but complaints from her. She says the screen will "freak out" (I'm assuming random clicks/movements) and that sometimes, she loses all control completely and the phone will do whatever it wants. It has randomly dialed her recent calls, and the big complaint this morning was that the alarm didn't go off. Also, I watched (with an aftermarket charger) the continue to beep on and beep off (charging indication) until the phone just shut down.
I have it running a 4.4.2 stock root, done through the firewater method and all that garbage. TWRP is installed, but I haven't tried flashing a new rom yet as I am out of the state for awhile.
Has anyone had similar problems? With all the complaints, I can't tell if it's a hardware issue or software or both. My intent is to make a video to show her how to flash CM, but I figured I'd feel out the community first to see if I'd just be better off getting her a G2 or S5.
All help is appreciated, and I'm sorry I cannot provide software, kernel and other details, as I mentioned I'm out of town for awihle.
Thanks much.
Never encountered any of these things, and these definitely do not seem like software problems. I'm betting that its a faulty One, not sure how swappa works but id get it exchanged as quickly as possible before your girlfriend kills you.
Lemon for sure. You should contact the swappa seller, but if they don't want to do anything (they technically don't have to), ATT or whatever carrier the phone is branded to will fix it. If it's a generic one, HTC will fix it.
I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........
I say FASCINATING! How do you get it apart to get the main board out? Mine never gets LTE anymore, which sounds to me like an antenna came disconnected. Heating up the antenna connections might be worth a shot.
fatboyRICH said:
I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........
Click to expand...
Click to collapse
You will never be able to truly reflow any electronic devices in your typical household oven as they do not get hot enough. Standard leadfree reflow temperatures peak around 500F, after a ramp up and ramp down time that prevents thermal stresses from destroying the parts. Even with the proper equipment, reflowing BGA/CSP parts is difficult without removing the parts first and then re-balling them as the flux has already been cured during the initial solder process.
I would seriously caution anyone from attempting this without the proper tools and knowledge as you could permanently damage any one of a number of components - I've seen IC packages literally explode after absorbed moisture in the device's resin packaging vaporized by ramping too fast.
T
I care Rich, I care. I loved my G2 but it crapped out on me at school one day. No warning just froze and shut down. Got it back up long enough at one point to pull whatever data I could from it. I ended up getting an S6 Active after jumping between a few crap phones, and the G2 sat in a drawer until tonight when I was looking for some standoff screws in the drawer, and I saw my old flame. The pain from losing her never really went away, and for some reason, I think because I recently did a bit of soldering on a RPi, I thought what if I tried to re-flow this thing? What do I have to lose at this point. Googled g2 mainboard reflow, and your post lit up my life. I baked at 380F for some amount of time re-assembled and I have my G2 again! I may have tried it eventually, but your post inspired me to tear that **** out and turn on the oven right away. I mean, obviously I'm not going to ditch my S6 for the G2, but I'm happy to have it back. Maybe I'll use it for things. Thank you, Rich.
I care!
Mine stopped working.
Was getting pretty hot on a regular basis.
When plugged-in, no lights, just heating up.
Read about "solder re-flow" - don't know how to.