So this is a very odd problem that I have here and any help/input would be greatly appreciated. I am not completely a noob and I know- pretty much what I am doing. I've rooted and "rom'd" /de-"rom'd" many many devices in the past. So I figured this wouldn't be much different. Boy was I wrong. For starters, I bought this phone through Craigslist (always a great start right). Long story short, I didn't do my research right and upon putting my metro Pcs Sim card in the phone, nothing happened. Usually this is a good thing, but I was waiting for the network unlock prompt, the usual for any phone. Well, I quickly learned that LG and various others have a new security function allowing users to unlock their phones straight through an app conveniently located on the phone. Even longer story shorter, i found out the first owner still hasn't paid t-mobile their money, great. I woke up the next day, put on my android glasses and got to work. So, for starters I wiped the phone and them used the TWRP one click tool to install TWRP through adb this worked wonderfully. Then I wiped the phone again and flashed a rom (of which I can't recall, there aren't many so it shouldn't be hard to identify, it had a couple sevens in it if I remember properly) and a patch for t-mobile phones designed by one of the members here by xda. It basically enables the phone to use any Sim other than t-mobile. This solved my first problem. Once I did that I then transfered a very hefty TiT Backup file to the phone which (while on the wall charger) drained the phones battery. I very quickly came across my second problem. Apparently G4's don't have much charging abilities, of course without the quick charge charger that DOESN'T come with the phone. Great, so after tons of digging around, I found a charger that puts out a little over 1.6 amps ; just enough to hold a charge. I sat in anticipation waiting for a good thirty minutes for the phone to turn on, and to no avail it kept the same dull "0% charge battery more" screen (this of course was better than the "0% charge battery more" screen that would flash because the phone wouldn't keep a charge with the original charger). Eventually after what seemed like an hour, I caught a glimpse of the LG screen and lost control of myself, I reached over at my phone like it was my life line and quickly read the most unappealing error message ever. "LG SECURITY ERROR" in bold white letters with a small line of white text that reads "authentication error #2.". Now I've dealt with problems up the who-ha (I've owned an HTC one M7 for two years now, that's a load of problems right there:angel::angel: ) but this is, what I would like to translate as, a sign from up above saying that I should not try and take matters into my own hands here. Which is why I'm turning to this wonderful forum. Sorry for the long post, but if there is anything I've learned in my long time of Android development it's that you need to be as specific as possible. THINGS TO NOTE: the phone still does not hold a charge and continues to gain enough power to cycle through the 0% screen, to the LG screen, off, and back again. Lastly I have looked EVERYWHERE to find out what the authentication code 2 was and I didn't find jack-****. So any input at all is appreciated guys. I know I'm not bricked (or if I am it's definitely still fixable) and I love doing this stuff, so hit me with what you got, I've got a six pack of beer so I'll be here all night. Please and as always, thanks for any input at all, your effort and your time is without a doubt appreciated (I know after this I'm going to owe a lot of people a couple of drinks )
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.
So I decided that i wanted to try hero the other day so i did some searching and made sure i had everything required ....newest radio... check.....pvt board...check...rom ready to flash...check...i went through the whole proccess and got KiNgxKxROM up and running for at least a day and a half...then lastnight i was playing around with the phone and it reboot on its own (kinda like the random reboots i used to get when i first got the phone)...it went to the G1 screen then just went black..so i pulled the battery and tried to reboot...now i have no response from the phone what so ever...its totally dead as far as i can tell
i saw that someone had success by putting another sd card in and trying to boot but that does nothing for me
I am trying everything i can because somehow enough moisture crept into the phone to cause the little "your not getting another g1" sticker to turn red
any way i am hoping that some how my situation has a remedy but i doubt it does
newspeak said:
So I decided that i wanted to try hero the other day so i did some searching and made sure i had everything required ....newest radio... check.....pvt board...check...rom ready to flash...check...i went through the whole proccess and got KiNgxKxROM up and running for at least a day and a half...then lastnight i was playing around with the phone and it reboot on its own (kinda like the random reboots i used to get when i first got the phone)...it went to the G1 screen then just went black..so i pulled the battery and tried to reboot...now i have no response from the phone what so ever...its totally dead as far as i can tell
i saw that someone had success by putting another sd card in and trying to boot but that does nothing for me
I am trying everything i can because somehow enough moisture crept into the phone to cause the little "your not getting another g1" sticker to turn red
any way i am hoping that some how my situation has a remedy but i doubt it does
Click to expand...
Click to collapse
this is not caused by the software sounds like your phone got a little wet some how and it messed up. try putting it in bowl of rice and if that does not work try a new battery.
tried a battery today at the store
i guess if it did get wet it could manifest itself a long time after the fact
well worth a shot regardless thanks for the advice
newspeak said:
tried a battery today at the store
i guess if it did get wet it could manifest itself a long time after the fact
well worth a shot regardless thanks for the advice
Click to expand...
Click to collapse
yeah i split soda on a keyboard once it did not start acting strange for 3 or 4 days after that. and pull the battery and take it out then complete submerge it for at least a day. but the damage is most likely done
Hey, something similar happened to me a few months back.
I use to get a lot of random reboots and it was quiet annoying and then one day my phone rebooted and it had a black screen, I took the battery out and put it back in and the phone was unresponsive.
When you plug in the charger does the red LED turn on or is it dead?
Mine, the led never turned on but it go warm because it still charged the battery.
My motherboard in the phone was fried somehow, I can assure you this isn't from the Hero rom at all because my phone died before I was even into roms.
Call HTC America (or where ever your from) and then tell them your problem and ask for an RMA repair, if the same thing happened to your phone as mine then you don't have to worry about them finding any "illegal software" (Root, and anything else that didn't come on the phone besides apps) I had root enabled and that voids the warranty but there would be no way for them to check so they would just replace the mainboard and send it back. In total it cost me 8 dollars to ship the phone and I had it back within a week - two weeks.
I hope this helped out!
EDIT: Is your water damage sticker red? I wasn't able to understand weither it was or not. I think it is and I just spent this entire time typing this long post for nothing then eeep! If it is, get an LG Vu Battery and replace the sticker with the one on the battery, I'm pretty sure they are identical.
Eh both stickers are red
thanks again ...it actually makes me feel better that it wasn't me messing around with hero that got me here
It just sucks having to pay the same amount as they are currently charging new customers for the phone under contract through the stupid insurance
My GFs HTC One, for the second time now (two different phones), has gone dead out of nowhere.
The first time she plugged it in and went to bed. All was well with it when it was plugged in. Woke up and nothing worked. No charging lights, nothing. Sent it in for warranty repair and T-Mobile/HTC said that the LCD screen was broke and that it was due to user damage (basically trying to say the phone was dropped, which it wasn't). They sent out a new phone, we sent back the broken one. A week later they charged our bill for the repairs and I had to call in 3 times in order to get them to finally waive those charges.
Now, a few months later, this new phone does the same thing. In the middle of using it, while it had plenty of battery, the screen went black. Same exact thing, would not power back on. Now we are in the process of waiting for the next phone to be shipped so we can ship this one back. And I'm fairly certain that they're going to try and use the same excuse again.
The only response that we get from the phone is when it is plugged into a computer and it asks to install the QHSUSB_DLOAD driver (which does nothing upon trying to install). After searching these forums, and Google, I noticed that everyone with this exact problem was trying to install a custom ROM. That is not the case with us. The OS on the phone's were never altered. The phone's were never unlocked. Nothing like that at all.
I don't really have a question that I'm asking here. From what I've read, it looks like the phone is basically bricked and there's nothing that can fix it. I just wanted to make this post so others know that this can happen to non-rooted phones too.
I'll follow up here once T-Moble/HTC give me the outcome of this second phone.
Exact same problem here.
Edge611 said:
Exact same problem here.
Click to expand...
Click to collapse
QHSUSB_DLOAD = hard brick, needs motherboard to be replaced
Had same thing with HTC Sensation. Need to replase the main memory chip where OS stored.
Time for a new girlfriend, not a new phone.
Just in case anybody is able to help out:
My SAMSUNG SGH-T899M (retail-configuration factory-unlocked ATIV S, originally branded for Telus Mobility in Canada), which ran the last build of WP8.0 (it failed to upgrade to 8.1 the times I tried), has apparently stopped working (possibly for good). In the middle of normal operation (listening to music while checking my email), the phone (and music) just stopped, screen went completely black, etc. Power button had no effect on tap or a normal power-on two-second press. My first thought was that the battery had somehow come loose or stopped working - its capacity had dropped alarmingly over the last few months - but that was not the case and plugging the phone in didn't help either. I do get a vibration (like the phone booting) if I press and hold the power button long enough, but only after I release it (which is odd).
Plugging the phone into my PC revealed that it now reports itself as a "Qualcomm HS-USB QDLoader 9008", for which Windows happily downloaded and installed a driver (so it's set as COM12). I don't know how to take advantage of this, though, or if it's even possible. The screen has never come on again since the phone died; I get no icons or text.
My most hopeful outcome would be to get the phone working again by somehow repairing whatever went wrong. In addition to being my day-to-day phone, it also is one of my hacking and testing devices. I was planning to upgrade to a new phone for day-to-day use but would like to be able to keep the ATIV S around as a development target and research aid.
The next best outcome would be getting my data off the phone. There's only a little on there that's truly irreplaceable, and none of that is terribly important, but I would like to get it back if at all possible. I had the standard backup features enabled, but they don't cover everything.
Anyhow, I'd appreciate any help people can provide. I've done a little bit of research and it sounds like this kind of failure has been known to happen to Samsung Android phones before (same Qualcomm USB device and everything), and most of the stories are not encouraging. Still, I figured it would be worthwhile to ask. I know almost nothing about this side of phone hacking; if there's a tool I can use to access the device and possibly fix it, or if there's a repairable hardware fault that causes this, that would be great!
Thank you.
Hi,
First of all, Sorry for Bad English, Bear with me.
Long Story, Short!
It keeps happening!
It would turn off, won't reboot
Won't take charging
I will leave it for a while
If I leave it off after when I am tired trying to turn it on, a few hours later It will be WARM like it was being used, Then I would plugin again and THIS TIME IT WOULD TAKE CHARGE and EVEN REBOOT!!
After when I am using it for a while (10-12min) GOES BACK TO POINT 1
I ERASE EVERYTHING, FACTORY RESET IT, and This time.. IT would work for more than 10-12min,
I will install apps, login into the account, and then again... The same thing would start to happen! !
What Really Happen? Day ZERO!
I bought this Red Magic 3 phone 3 months ago and it was working super awesome and everything was great until last week after a 30-40 min gaming session on this phone, I went back to sleep and kept the phone on the table.
The next morning I noticed that the mobile is turned off, I thought Maybe battery drained so I plugged in to charge and continued with my morning routine.
After an hour I noticed that mobile is still not charging I tried plugging in and out multiple times and it didn't start charging, I checked the Data Cable on my MI MAX 2 (that also supports Type C) and Cable and Adapter were working fine.
I immediately realized that SOMETHING IS WRONG!!!
I saw some youtube video and I tried that Vol Key + Power Key thing and that Bios look alike menu opened up, I can see all the reboot, recovery boot, etc option but nothing worked.
So I picked the WIPE DATA option and It worked, Formatted the Phone and IT REBOOTED.
I figured maybe some software issue was causing it.
BUT SINCE THAT DAY it keeps happening!
It would turn off, won't reboot
Won't take charge when I plugin
I will leave it for a while
a few hours later It will be WARM like it was being used, Then I would plug in again and THIS TIME IT WOULD TAKE CHARGE and EVEN REBOOT!!
After when I am using it for a while (10-12min) GOES BACK TO POINT 1
Service Center
They are no help! They don't know what is wrong with it, Even they formatted it in front of me they did the Factory RESET it, I tried using it in Front of them for a while and the SAME THING HAPPENED!
then they installed some updates using some official package.
But still,
IT would work for more than 10-12min,
I will install apps, login in the account
suddenly... The same thing would start happening again!
Their Resolution is :
Motherboard issue and I will have to get the motherboard replaced.
This simply means EVEN THEY DON'T KNOW WHAT IS WRONG WITH IT and CHANGING EVERYTHING is their SOLUTION!
and they said it won't be covered on the warranty! Because the warranty has been voided BECAUSE THERE IS A SMALL CHIP on the phone! -_- which happens to be 40-50 days old.
I know is their Excuse to get money from me! Now I don't know what to do with it.
For me it was my first expensive mobile. I never bought a mobile for more than 200$.
Same thing for me.
Germany, Europe.
Download Ampere.
What's your battery health at, voltage, and how many ma draw when just sitting in that app.
I've learned my lesson with this company. A couple of extra capacitative buttons and a large battery are not a reason to buy a phone. The build quality is ok, the software abysmal (I still get random **** getting pressed when I unlock the phone), and support horrendous. Do yourself a favor, threaten to speak with the governing authority in your country regarding warranties. Tell them a small crack on the screen is not indicative of internal damage. Tell them you will post a youtube review of the company and phone if they do not abide by their warranty and fix your phone.
Once you fix your phone, sell it and cut your losses.
When will people learn YouTube won't do anything. You need subscribers to have any kind of weight. I'm at 2.4m lol.
I don't know the warranty laws in your country. I know here they have to prove that what you did was the cause. Nubia is really shady and not only scams but will flat out lie all the time. I seen people had bad battery's and they say they need a replacement board.
Just let me know what I asked and we can start going in a little deeper. Start off with the basics then move into some other stuff. Could be a simple easy fix.
Some off topic posts are removed. Please remember our rules and post constructive content. Thank you.
Any update?
I'm curious to see if this is a battery issue or something else
Mineapple said:
Same thing for me.
Germany, Europe.
Click to expand...
Click to collapse
So What did You do....!
Ok I attempted to help you trouble shoot this issue and get it fixed but it's pretty clear this is an uphill battle and a waste of my time.
bignazpwns said:
Ok I attempted to help you troubleshoot this issue and get it fixed but it's pretty clear this is an uphill battle and a waste of my time.
Click to expand...
Click to collapse
Thanks for your time.
I got the Battery Replaced thinking it was the issue but right after the installation. I turned it on to use it and it didn't work... I am still facing the same issue.. Meaning Battery was fine.. there is something else that causing it to turn off like this..!
Still, it acts like in COMA, then it heats up, I will charge it, It will boot.. If I will try using it ..it will turn off and won't turn back on!
bignazpwns said:
Any update?
I'm curious to see if this is a battery issue or something else
Click to expand...
Click to collapse
Well.. I got the battery replaced and it was a waste of another 2,000INR. Still Facing the same issue. This means this Turning Off issue is not caused by the Battery.. It is due to something else..! :crying: