Hi guys would be grateful for any help in this matter. I have recently purchased a HTC Wildifire which was functioning perfectly until I attempted to upgrade to android 2.2, when I did the touchscreen and buttons now refuse to respond to any input, both were working fine before the update was installed. I have tired Hard Reset and Recovery Mode both to no avail. I was wondering if you had any suggestions of how to fix this. The phone is currently not rooted and is running a T-mobile branded rom version 1.25.110.1
...
I have exactly the same problem. Neither touch-screen nor any buttons work after installing Android 2.2 on my Wildfire. Interestingly, I am also with T-Mobile. Does anyone know how to deal with this fault?
Still no luck trying to fix this. I've tired to reflash the stock T-Mobile Rom RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe but everytime i'm faced with the bootloader version 140 error. I can't create a goldcard because the touchscreen doesn't work hence can't enable USB debugging. I'm really at wits end dunno what to do, seems i'm just going to have to send it to HTC for repair =/
Related
Helo all - I could really use a hand here. This is the second time I have faced this issue.
When trying to make a call on my 614c when the battery is low, it crashes. Upon reboot, the radio no longer works and I cannot make any calls. It just goes into a permanent "Seaching" mode.
What I've tried:
Reboots - warm and cold
Removing the battery for 30 mins
Reset to defaults
Multiple different ROMs including upgrading and downgrading the Radio
No luck.
Last time (3 months ago) I ended up sending it to ipaqrepair to be fixed.
They said:
"the un-official hacked ROM installed in combination with a corrupt / mismatched GSM Radio ROM, these are the root cause of the issues"
I had actually NOT installed a non-official ROM until after it stopped working in a desperate attempt to fix it. But when they got it, it was a 6.5 ROM.
This time, I had upgraded it to 6.5....but I have since downgraded to the official ROM an installed the. .89 Radio update.
It wont work at all and I can't justify mailing it away for another expensive repair.
Any ideas or assistance would be greatly appreciated. Thanks.....
Any ideas? How can I effectively "blow away" all the software/drivers and set the device up as new? IpaqRepair said it was corrupt software last time....
I've installed different ROMs via flash.dio and I tried the HP radio upgrade RUU_1.8.0_081208_MP_M089_WWE. Are their files or settings that the installs I am doing do not affect - and if so, how do I repair/replace them?
Using Sim Manager, it says the phone is not ready. It's just like the phone radio won't initialize...
This phone originated overseas (Europe) - could that be somehow causing this issue since I'm using it in the USA? Something locking or changing and no longer compatible?
Not sure what else I can do and am missing my phone. Any ideas or assistance would be greatly appreciated.
Still fighting with this....maybe onto something now?
When I get the asset viewer information for the phone it shows the radio is present and the firmware number.
the Stack Version, Bootloader Version, Filesystem Verions and Radio GDFS versions are blank.
It does show the IMEI.
I'm guessing I'm missing file/data for the radio....but reinstalling the Radio ROM HP offers has not helped (maybe not complete - just an upgrade?)
Thoughts?
Anyone have a copy of the original ROM and .81 Radio ROM?
Maybe rolling it all the way back might get it operational again....
Official Drivers/Rom/Radio for 614c
Hi,
You can download official drivers from HP website. The forum does not allow me to post the link. Just search for "official 614c drivers" in google and you wil get the link.
Also note, please install using WINDOWS XP os as installing this using other os such windows 7, windows vista etc is not possible.
Okay - I tried installing the software from the HP Website using XP - but it still isn't working. It's just like the software for the radio is corrupted and it won't replace it (does not list the versions like it should when you look at the software inventory).
Is there any way to manually do this? Any advice or help would be greatly appreciated.
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
-Alpha- said:
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
Click to expand...
Click to collapse
Just bumping this thread...would love to have this phone back.
Bumping once again - still in hopes of fixing this phone. Can anyone help?
-Alpha- said:
Bumping once again - still in hopes of fixing this phone. Can anyone help?
Click to expand...
Click to collapse
I guess, you will get enlightenment for the problem on your device at http://forum.xda-developers.com/showthread.php?t=455840
Bump.....
Still hoping for a solution. I have gone to a Glisten now, but do not like it as much as the 614c.
I'm open to any suggestions.
Hi, guys im having some issues and would like some expertise. Okay so i have an s4 the model is m919v but the model is unrelated to the problem. I was running custom roms and have been for a few months and i have a phone that has a locked sim. I heard from someone that i can flash an older version of my modem and get the service menu to unlock... point is i did it and it didnt unlock BUT THATS NOT MY ISSUE. I decided to then revert to stock because my phone was being really glitchy after i tried the unlock. Now i restored my phone and got a custom recovery installed a custom rom that was working flawlessly before is now also being glitchy the same way after i tried to unlock it,
These are some glitches im experiencing:
1) phone app is taking a long time to load and it doesnt type in numbers fast
2) when i call someone it just freezes and i cant go to the call screen
3) no notification sounds coming from my phone it just vibrates but doesnt ring
and im sure a few more
IM SURE THESE HAPPENED AFTER I WENT INTO THE SERVICE MENU AND TRIED TO UNLOCK MY DEVICE.
Someone please tell me what i can do to fix this because ive already reverted to stock once.
zee24 said:
Hi, guys im having some issues and would like some expertise. Okay so i have an s4 the model is m919v but the model is unrelated to the problem. I was running custom roms and have been for a few months and i have a phone that has a locked sim. I heard from someone that i can flash an older version of my modem and get the service menu to unlock... point is i did it and it didnt unlock BUT THATS NOT MY ISSUE. I decided to then revert to stock because my phone was being really glitchy after i tried the unlock. Now i restored my phone and got a custom recovery installed a custom rom that was working flawlessly before is now also being glitchy the same way after i tried to unlock it,
These are some glitches im experiencing:
1) phone app is taking a long time to load and it doesnt type in numbers fast
2) when i call someone it just freezes and i cant go to the call screen
3) no notification sounds coming from my phone it just vibrates but doesnt ring
and im sure a few more
IM SURE THESE HAPPENED AFTER I WENT INTO THE SERVICE MENU AND TRIED TO UNLOCK MY DEVICE.
Someone please tell me what i can do to fix this because ive already reverted to stock once.
Click to expand...
Click to collapse
..
I would Odin back to stock firmware. Start over with a fresh install of the latest stock firmware available for your device. Then root, install recovery & backup stock rom so if something weird happens you can restore back. Once this is done, then it makes since to do a custom rom. Good luck.
Hi all,
A quick peek of touchscreen issues attached:
http://youtu.be/Hhuiv1SdsDQ
I enabled show touch options in usb debugging and took this video. Every touch on the screen is registering atleast two and mostly three touches as you can see in the vid. Any way to resolve it? I have tried to downgrade OS to 4.2 using LG Flash tool, and that doesn't work.
How do I fix this? Is it a hardware issue?
Baseband problem:
When I downgrade the phone to a D802 v10B or 10A, I lose baseband. Currently has India KitKat D802T20A_00.KDZ installed and baseband is present. Even downgrading to D802T10A_00.kdz loses baseband. Any thoughts why this is happening?
Try to go to hiddenmenu by dialing the number and then find update touch or something like that and or check your screen for dirt and clean it
fix found ?
I ran an update on my g2 from lg, and ended up with the same issue. Have you found a fix?
Same issue on my G2 (see my thread) but yesterday I gave up and send it to LG to fix it.
I tried nearly everyting I guess but nothing did help. Also the way into the hidden menu was without any result.
So I wish you good luck.
Me too!
I have the same issue. (VS980) It's impossible to use the phone while this is happening.
Now that I think about it, I didn't have any issues with this until after I installed the latest OTA
Anyone have any ideas to fix this??
Update
Finding out stock firmware and calling lg tech in the morning. Will update if I make any progress.
Reinstalled "out of the box" original rom ver. VS980-24A (.kdz) using LG Flash Tool. Problem gone - worked fine for several hours. Phone asked to install Verizon update VS980-26A, problem has returned. Called tech support, they couldn't understand the issue and decided my device was broken. They are sending me a replacement under LG warranty.
I used this for returning to "out of the box":
http://forum.xda-developers.com/showthread.php?t=2432476
Hi there,
I realy need your help on my problems with the G2 32GB D802.
I bought it on ebay and instead of getting it from GB it came from HongKong and I didn't think about it that it does not have a european ROM.
First I wanted to root and flash custom recovery and cloudyG3 rom. After rooting with ioroot and installing the TWRP I stuck in the fastboot mode. First problem I did not make a backup because I never reached TWRP. Download mode only appeared for a second an then disappeared again.
After a lot of searching I found that probably the 802autorec.apk was wrong, since I don't have a european model. So I installed via fastboot a laf.img for a D800. After that the download mode was working again and I installed different roms via flashtool2014. The installation worked again but after rebooting the phone I had a lot of trouble with it. That the reason for trying different roms as I sad befor.
First, the fingertip points at different areas of the screen but not there where you are touching the screen. So you can not reach the buttons or write on the keyboard.
Second, after connection to pc I recognized that my 32GB model had only 10GB internal memory.
Finaly I can not use the phone. For me it seems that I burned my partitions and need your help to get it right again.
Please give me a chance.
Best regards an thanks for helping me.
p.s.: I tried to go to the settings menu in the phone and reached it after a lot of confusing taps on the screen. All the phones informations like IMEI and all the other disappeared. Something realy went wrong with it.
No one an idea how to get back to normal?
frankhell said:
No one an idea how to get back to normal?
Click to expand...
Click to collapse
I have the same problem. Bought LG G2 D802, wifi connection was weak. I downloaded Lg PC Suite and upgraded the system. After upgrade have the same touchscreen problem. Have tested for 5-6 firmwares, but the problem is.
Do not exactly know what firmware need to install.
Please help us.
enter enginnering mode and update the touch firmware may work for you?
frankhell said:
Hi there,
I realy need your help on my problems with the G2 32GB D802.
I bought it on ebay and instead of getting it from GB it came from HongKong and I didn't think about it that it does not have a european ROM.
First I wanted to root and flash custom recovery and cloudyG3 rom. After rooting with ioroot and installing the TWRP I stuck in the fastboot mode. First problem I did not make a backup because I never reached TWRP. Download mode only appeared for a second an then disappeared again.
After a lot of searching I found that probably the 802autorec.apk was wrong, since I don't have a european model. So I installed via fastboot a laf.img for a D800. After that the download mode was working again and I installed different roms via flashtool2014. The installation worked again but after rebooting the phone I had a lot of trouble with it. That the reason for trying different roms as I sad befor.
First, the fingertip points at different areas of the screen but not there where you are touching the screen. So you can not reach the buttons or write on the keyboard.
Second, after connection to pc I recognized that my 32GB model had only 10GB internal memory.
Finaly I can not use the phone. For me it seems that I burned my partitions and need your help to get it right again.
Please give me a chance.
Best regards an thanks for helping me.
p.s.: I tried to go to the settings menu in the phone and reached it after a lot of confusing taps on the screen. All the phones informations like IMEI and all the other disappeared. Something realy went wrong with it.
Click to expand...
Click to collapse
I now have the answer from the dealer that my G2 has the Firmware D80220B.
Just try and test it. Good luck.
@Angryyolk
I just ask myself how to enter engeniering mode?
Thanks for your help.
I walked one step forward now.
But there is still no solution for my problem. I found a link to LG "http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI" to get the information about the version of my stock ROM. Just replace IMEI by your real number and you will get it.
In the meantime I flashed the rom with flashtool but the screen behaviour is still the same.
I later rooted the phone with towleroot and then installed the correct autorek.apk for the D802. That worked properly. I reached TWRP but in fact of the weired screen behaviour I couldnt do something. I tried to fix my IMEI problem with QPST but this tool showed only empty tables on my PC when I connected my G2 with usb.
I tried an update of the screen firmware as posted above. The code that has to be entered on the dialer is 3845#*802# but it wont work for me since I can't enter "settings" the service menu. That's because of the weired behaviour.
Beste regards
I now was able to enter the hidden menu. And I was able to get to the menu point "update touch firmware" but nothing happend.
What is wrong?
touch screen problem
The same problem occurred on my phone. how did you do it. please help.
I installed the software and touch screen freaked out.
It's because its a Refurbished Models..
You have to check your Mother board for exact Model
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Recently I replaced the USB port on an i337 that was previously my daughter's phone. I used a replacement part for an i9505. I noticed that the soft keys don't work. I can't say if they were working before I repaired the USB port since I didn't pay that much attention, and it was my daughter's phone.
So, is there anyway that the complete loss of the soft keys is related to the repair? Is there a way to tell if this is software related or a hardware issue? I have done a factory reset with no resolution. The phone is running the stock Samsung/AT&T ROM 5.0.1. After searching, I've read a few scattered ideas, but I haven't found any good guide yet.
TIA
lekmedm said:
Recently I replaced the USB port on an i337 that was previously my daughter's phone. I used a replacement part for an i9505. I noticed that the soft keys don't work. I can't say if they were working before I repaired the USB port since I didn't pay that much attention, and it was my daughter's phone.
So, is there anyway that the complete loss of the soft keys is related to the repair? Is there a way to tell if this is software related or a hardware issue? I have done a factory reset with no resolution. The phone is running the stock Samsung/AT&T ROM 5.0.1. After searching, I've read a few scattered ideas, but I haven't found any good guide yet.
TIA
Click to expand...
Click to collapse
Actually, I think this phone was previously carrier unlocked with a code from cellunlocker. I don't know if that info is helpful.
lekmedm said:
Recently I replaced the USB port on an i337 that was previously my daughter's phone. I used a replacement part for an i9505. I noticed that the soft keys don't work. I can't say if they were working before I repaired the USB port since I didn't pay that much attention, and it was my daughter's phone.
So, is there anyway that the complete loss of the soft keys is related to the repair? Is there a way to tell if this is software related or a hardware issue? I have done a factory reset with no resolution. The phone is running the stock Samsung/AT&T ROM 5.0.1. After searching, I've read a few scattered ideas, but I haven't found any good guide yet.
TIA
Click to expand...
Click to collapse
I have never replace the USB port before so I could not answer whether the softkey problem related to the hardware replacement. However, I ran into the softkeys problem when I updated my phone to OK2 version of lollipop. I solved the problem by installing the OC4 version of lollipop. If your stock AT&T rom is OK2 then softkey problem might be related to the software problem.
I won't dismiss any ideas about this being a ROM version issue, but the phone was working fine until my daughter destroyed the USB port. At least she didn't say anything about the soft keys not working. That's why I'm wondering about how to get to diagnosing this.