i'm new on LG Phones.. i've updated my new O2X to 2.3.4 today.. and after install the CWM, my phone vibrates all the time when im on recovery mode.. i've changed the version of the CWM, but no success. same problem
can anyone help me?
ps.: im sorry for my poor english
Some people just have this issue for unknown reason. I have it too. I think there still isn't a solution to this. I'm pretty sure it does not damage the vibrator any way, at least I haven't noticed anything in few months.
I had the same problem, but reinstalling the CWM stopped doing, just try again
Related
Hey Everyone..
Ive always been able to get into both download and recovery mode...but when I was going to apply a ROM to my phone i checked it and now i cant access either of them....
I havent flashed a new firmware or used ROMS or anything yet....it seems like it just stopped working?
Have i done anything to disable it or something????
Should i just do the FIX (http://forum.xda-developers.com/showthread.php?t=785201) to get it back working or is there something else i can do...
I have Froyo 2.2
Baseband-HVJP3
Build-FROYO.HVJP4
Thanks
i would suggest you do the fix, but be patient and read properly, cause one little mistake will brick your phone, and you wont be able to get into download mode to fix it.
i have no idea why your problem has arisen, thats very strange.
perhaps you should invest in a USB JIG as well. a very life saving tool
ahh k then.....
Maybe i should try wiping and reseting my galaxy s ?.. maybe ive installed something that blocks it?
Anyways thanks for your help
I think that my phone is not working completely after i flashed the 4 ics roms.Probably it was because of the hardware accerleration in the ics rom because after i tested out the roms and flashed back to gb roms,strange problems have appeared(the phone completely does not respond for 2 seconds).Its not the problem with the gb roms as i flashed zeus,cm7,miui,lezo roms and still have this problem.Im wondering if anyone have experienced this problem and if anyone knows how to fix this problem,PLEASE HELP !
zyfkurmom said:
I think that my phone is not working completely after i flashed the 4 ics roms.Probably it was because of the hardware accerleration in the ics rom because after i tested out the roms and flashed back to gb roms,strange problems have appeared(the phone completely does not respond for 2 seconds).Its not the problem with the gb roms as i flashed zeus,cm7,miui,lezo roms and still have this problem.Im wondering if anyone have experienced this problem and if anyone knows how to fix this problem,PLEASE HELP !
Click to expand...
Click to collapse
There's currently no hardware accerleration in the ics roms.
http://forum.xda-developers.com/showthread.php?t=1448803
Do this, and your problems should be solved.
After I flashed miui 2.3/ics (I can't remember) my kernel logo is visible for 15 seconds, so the boot process is much longer.
cakebomb said:
There's currently no hardware accerleration in the ics roms.
http://forum.xda-developers.com/showthread.php?t=1448803
Do this, and your problems should be solved.
After I flashed miui 2.3/ics (I can't remember) my kernel logo is visible for 15 seconds, so the boot process is much longer.
Click to expand...
Click to collapse
wtf.....................i think you don't understand my question.I did not brick my phone , it can boot up as normal , just that the phone does not function properly.It just doesn't respond for 2 seconds and then goes back to normal but it happens all the time so im getting frustrated.Don't know if anyone has a solution to my problem....Thank you for responding anyway
I understand your question.
So, if you do this procedure, you phone will be completly restored. (No more SU, Root, CWM etc.)
Then you can completly screen out/exclude software errors.
And if this not works, it's a hardware problem.
cakebomb said:
I understand your question.
So, if you do this procedure, you phone will be completly restored. (No more SU, Root, CWM etc.)
Then you can completly screen out/exclude software errors.
And if this not works, it's a hardware problem.
Click to expand...
Click to collapse
err..............the first thing that i did after i found out the problem was flashing with smartflash and i did it many times.Think its a hardware problem then.But i did not drop it on the floor or did anything like that , not sure what is the cause of the problem.D:
Have you experienced overheat while on ICS ?
Vinzgore said:
Have you experienced overheat while on ICS ?
Click to expand...
Click to collapse
when i use the phone or play games more than 7-10 minutes , it gets hot.
blue screen error
after flashing to ics ,after 3 to 4 hrs of usage blue screen error and CWM not working the error is, its showing an error occured while attempting to run privileged commands !!!
I have happen to see that blue screen that you mentioned but no strange things going on over here, and I have been flashing to ICS and restoring to GB all weekend just to compare. I know it may sound as a silly question but did you do your wipes before all those roms you mentioned?
Hey Guys,
I was installing a weather widget for my O2X and he could'nt find my location.
So i tought I'll reboot my O2.
When i rebooted my phone, the touchscreen wasn't working anymore.
But before I reboot my phone it did.
So now when I turn on my device it boots, and I can see everthing : Statusbar, Lockscreen etc.
But when I try to unlock it it's not responding to my touch.
So i did a full wipe and installed the ROM again but, it wasnt working again.
So then I downloaded CM10.1 for my phone and flashed it but still not working.
Anyone got and idea?
Greetings, Hammief
Exactly what happened to me
Same thing has happened to me
I have the Wind Optimus 2x. So it will be different then what other have experienced.
Basicly I had the latest CM7 installed and I wanted to upgrade to ICS so I used the tool to repartition the device. I got ICS installed fine but the screen doesn't work anymore. I flashed back to stock with nvflash perfect and but screen doesn't work at all.
If anyone can look into these touchscreen problems or has any experience it would be appreciated.
it seems that is not problem in hardware, the problem is in software...
please try to do full wipe in recovery than try, maybe is virus, or something else
help
help.
DevLaw said:
help.
Click to expand...
Click to collapse
No idea what is wrong here.
Please try Progmaq's Full Repair Tool as a last resort.
http://forum.xda-developers.com/showthread.php?t=1975274
Yesterday I went to a party, nothing wrong with the xperia t. When I got home I let it recharge. I think it still worked at that moment. Pretty sure it did. Went to sleep. Woke up. My phone battery was empty lol. Still in the recharger. Did some stuff, let it recharge some more. Got it to boot up again. Now touch screen doesn't work anymore . Tried wiping cache, factory reset. Still not working.
I have cm-10.1.3-RC2-mint installed. I think I might have to update it. This could be the problem.
Any more tips for if it doesn't work? never had this problem before. I hope it is a software thingy.
I updated the firmware but still doesn't work. I think im gonna re-install the stock firmware, and flash a stock kernel which will unroot my mobile. Any tips? please? I can't use my phone at all atm. It just stays at the cyanogenmod install screen..
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
gregbradley said:
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
Click to expand...
Click to collapse
I would like to try that thing with adb, but as I have already reinstalled cyanogenmod, developer options/debugging is turned off. I can't use ADB. Unless you know another way.
So this is totally getting out of hand.. (and I don't know if that is also a english expression lol).
I tried reflashing a stock firmware. Worked, but touchscreen still doesn't work. Then I noticed, that I now don't have cwm anymore... how the f?
SO I probably forgot to exclude the kernel. So now I tried reflashing a kernel with cwm, but flashtool doesn't recognize the kernel files... I don't know what is going on..
Ah already found the problem. Got cwm back phewww..
So here is what needs to be done. I want to try gregbradleys adb shell fix but my usb debugging is off and this means that I can't use adb, as I don't have touchscreen.
So, is there any way, any way at all, to enable usb debugging without touching the screen? Maybe a kernel with that settings automaticly set?
Im getting a bit angry at my phone now.. I didn't even do anything to break it in the first place. Just tried recharging it, and that killed the touchscreen? lol. Help will be appreciated. Im out of ideas.
Get a usbotg cable and attach a usb mouse
Then use that to turn debugging on
When you flash a stock firmware you lose recovery.
Sent from my C6903 using xda premium
thanks, I'll get one tomorrow. I hope it will help. You've helped me before so im pretty confident that you fix my problem again haha. You are a boss.
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
gwodus said:
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
Click to expand...
Click to collapse
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
quinten96 said:
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
Click to expand...
Click to collapse
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Sorry to bump
gwodus said:
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Click to expand...
Click to collapse
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
jmm288 said:
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
Click to expand...
Click to collapse
I have the same problem... I changed touch panel, flex cable and update with pc-companion but it doesn't work
Hi all,
I downloaded the latest TWRP from https://dl.twrp.me/i9305/ - twrp-2.8.7.0-i9305.img.tar 8.1M
I installed it with ODIN. The flash was a success and when the phone rebooted the touchscreen was unresponsive.
I have tried another version of twrp for this phone and I can get into twrp, but the touchscreen doens't work. I tried replugging in the ribbon lead for the digitiser and that made no difference.
Do you think its a software problem or that I have fried something?
Many Thanks
Andrew
Hi,
there are plenty of issues with TWRP and 2.8.7.0. I'm actually surprised you could even boot up your phone. The new recovery messes up with partition sizes and some other things.
I hope you have a backup of the current ROM as I suggest you to install Stock ROM again and stay on TWRP 2.8.5.0 and see if your phones works normally again
Hi,
thanks so much for replying. I still have the stock rom. All I have done is install twrp. I have tried doing a factory reset and it made no difference. I can still use the buttons on the phone, but the touchscreen remains unresponsive.
So if I download the stock rom for the phone and install you think it might make a difference?
Andy
Update:
Downloaded and installed stock rom from samsung (4.4) ... installed with success via odin. The phone boots and the screen is still unresponsive. I just cant believe I have broken the digitiser by installing twrp?!
Andy
Hi,
sorry for the late reply. I didn't get a notification via tapatalk. But anyway to come back to your issue: it's the first time I hear that a "corrupted" recovery could break the digitizer. I did the same mistake with the broken recovery but fortunately no issues afterwards. But apparently it's possible judging by some google search results.
I never had such issues and I don't know how to help you. Maybe there is a possibility to fix it.
Thanks for your reply
I hope there is a way of fixing it. It doesn't seem economical to fix this phone? The digitiser kit is around £60 ... Plus because I can't be 100% why this happened in the first place, it might happen again with a new digitiser?
Thanks
Andrew
I was looking here in Germany right now what I would have to pay for fixing the digitizer - between £50 and £60 as well, some even charging a little more. For £80 I could get a decent looking used S3 4G.
If I were you I'd rather buy another S3 again (or any other device) instead of trying to fix the broken one.
Did you tried to Flash stock recovery