LG L3 II bricked/broken? - LG Optimus L3 II, L5 II, L7 II, L9 II

Hi folks,
i got a LG L3 II E430 and rooted it. It worked great for some days, but now it just turned off and wont turn on again. When i replace the battery and start, the home button lights in different colours, after a while it stops, the screen is on but black, the menu and back button react but there is no sign of a function.
When i hard reset it (battery out, then starting with home and Vol- button pressed), the same happens. After some times, the screen had a few thin vertical stripes and you could JUST guess that the LG-symbol is there when starting.
Before all that, i just hat titanium backup save Data and apps and installed Xposed framework and xprivacy. I had both (xposed and xprivacy) installed a couple of days before all that and had no problem.
Does anyone know what happend or even better has an idea what i could do to save the phone?
thanks in advance,
Simon
EDIT: After a couple of tries, the hard reset worked!

Hi again,
after i managed to hard reset the phone, i did not reinstall Xprivacy or Greenify. It worked for 3 days, but now the screen turned black again. Sometimes there were some very thin vertical lines in some places.
It seemed to work, because the menu and back button lighted up when i touched them. also i could shut down the phone when staying on the power on button for a long time.
After 3 restarts, this time the phone managed to wakeup again, just as normal.
Does anybody know what the problem might be, or if there is a way to check a failure log or something like that? To me, it looks like a hardware problem. In that case, i could send it back since i bought it a week ago..
I got Kingroot and Titanium Backup Pro installed, if that helps.
Thanks a lot, Simon

Related

8125 stuck on 3 color boot screen

It says only ipl 2.25.0001 and spl 2.25.0001
I try a hard reset, but when it asks me to confirm by pressing SEND, I press SEND and nothing happens.. press any key and nothing happens, just sits there saying press SEND to confirm...
I tried flashing Cingular/AT&T's rom on to it, it was successful on the screen, but after rebooting, just went back into the 3 color screen...
Does anyone have any suggestions?
Additional info
I just wanted to add, I have searched threads here on xda-dev and other sites, and have found similar issues - normally the other issues have been resolved in one way or another involving a hard reset, which my phone will not complete. When it asks me to press send, the phone freezes at that point and does not accept any key entries (except reset). I would really appreciate any input. I also have a theory-that I may attempt this evening-If you hold the camera button down and reset, it brings up the boot loader screen (if my information is correct)... could my problem be caused by a faulty camera button? Maybe internally the button is remaining closed, which could prevent it from doing anything on a reset outside of the boot screen? Any engineers around that may know this? I am going to attempt (hopefully with low heat) to remove the button this evening... possibly even repair or replace it if the phone works with the button removed...(these thoughts are based on my phone being dropped in the sand at the beach...maybe a grain of sand worked it's way into the camera's button housing and is holding the contact closed)
problem's almost fixed
well thanks for no advice... i desoldered and removed the camera button (button 3). powered it on and the phone works. I reprogrammed the camera to button 5. (i also loaded a new WM6 rom and some other stuff) The last time I opened up the phone, I broke the itsy bitsy super micro tiny lock on the keyboard ribbon cable socket... so now my slide out keyboard doesn't work. I installed a full screen keyboard and set it to the messaging button (button 1) - the messaging button still brings up messaging with just a touch, but a long hold brings up a full screen touch keyboard that works fantastically!!! I am going to dismantle the very tiny micro switch and repair it, then resolder it back on the mainboard to make my camera work like it should again...and find a way to get the keyboard ribbon cable to lock into the socket...then my phone will be as good as new!
umm... thanks???
well congratulations on getting it working again.
tiny switch
I have taken the tiny little switch apart without breaking anything... one tiny grain of sand stuck under the button pressing on the switch plate... now i have to find a way to put the little switch back together... then attempt to solder it back onto the board without over heating nearby components. I have been playing around with Byka's cube... took a bit of tweaking to get it to work well.... not sure if I want to keep it or not... I have been trying to find htc cube, but no luck outside of a rom... which I may consider...but I just spent the past week reinstalling all of the software I use... Would like to just design my own windows for my phone if I had the time... Been working on an ion motor for an electric car...
I would like to thank everyone here at xda-dev. for all the information. Could not have learned so much, so quickly, if it weren't for this site.
oh... and I am using an 8125 (G4) with Faria Crossbow
Have the same problem...
Hi!
I have the same problem (but I don't have much tech know how).
It all started when phone got wet (inc. in battery compartment).
My phone would not soft reset beyond the Bootloader, unless I leave the battery out for a few hours. Then once it loads up, after a short amount of usage 2 things happen: 1) every time I would turn it on (or get a call) it starts in Camera (you didn't report it but you must have had the same experience). 2) the buttons don't work properly.
It finally dawned on me the camera button might be stuck, I set the button to "none", and no more more automatic camera. I still need to free the button altogether as still causing button freezeup and also allow soft resets.
I don't know much about soldering.
Any ideas?
Thanks

Problem with touch screen

Hi, I both an HTC 8525 from eBay and it worked fine for first few days but yesterday a had first problem. At first his touch screen stopped reacting on touch, i tried rebooting, restoring on factory settings but every time he works for few minutes from the moment i start him and then again the same. My screen doesn't react on touch or if it reacts he opens a program and close it right away by it self, now he started doing that and when i start a program with buttons (not on touch screen). Please tell me is there a way to fix that by my self or should i return it? Please answer quick, thank you...
Factory default? Did it means hard reset? Had You done it? There are 2 ways :
1. Launch clear storage,
2. Handser OFF, press and hold right and left softkey, then do softreset with stylus..
If it still exist, i'm affraid of it's hardware problem, i hope not

[Q] Problem when my phone is recovering from Sleep mode

Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service

S6 won't respond then will, just received it today.

Today I got my phone in. I was on the first set up page and it wouldn't respond to any of my touches. The buttons would glow like I was touching them but it wouldn't type or input. I soft reset it. It worked when I used assist touch. I hard reset it, wiped cache and factory reset. It fixed and I installed all my apps and when I plugged it into the charger it stopped working again. I can open the camera by double pressing the home button to unlock my phone but i can't open anything. It will glow like I'm pressing it but it won't open. I can pull down my notifications bar but none of my toggles or setting icon will work, again, they will glow just not open. I came back to my room and randomly it was working again, after 5 mins it stopped again.
Thank you for your attention.
ATT 64 GB
Galaxy S6 (not edge)
I don't know if this is the cause/solution to your problem, but I know S Voice can cause lag issues. By default, double pressing the home button (when device is unlocked) opens the S Voice. Frankly, it's redundant and pointless, as it's a mediocre attempt at Google Now. Open it, then go into the settings, and disable it. It causes lag because it's waiting to see if you're going to press it again or not.
But if that doesn't fix it, and it's doing that stuff before you've even set it up, I'd tend to think you've got a faulty unit. The capacitive buttons are part of the screen/digitizer, so maybe you've got a bum one.

So here's a new one, a keyguard/lockscreen missing problem

OK, here's the situation. sometime last night my phone decided it was going to play a late April fool's joke on me. I had set it down, and the screen timed out as usual. Only when I hit the power button again, it came right back to the home screen instead of the lock screen. Granted I only have it set to swipe, but that's beside the point (I think). I thought it's been a while since I rebooted, maybe that'll help. When it came back up, straight to the home screen again, only this time was way interesting! Not only did the lock screen get skipped, I had no haptic feedback like usual, the home button wasn't working for short press or long press, and with it plugged in and notifications waiting turning the screen off by the power button didn't do anything as far as the notification light.
Now here's the kicker: DOUBLE pressing the home button and bringing up the s-voice actually worked, and after that everything else worked too! Only thing is the problem comes back after every reboot so far. Oh and I've lost the ability to write to the external SD card. I've even tried reauthorizing it, no joy.
Anybody got any ideas about what I could try? If not, at least I hope I made some of you start or end the day with a chuckle and a solid Wtf? ?
My next step is gonna be clearing the dalvik/art from twrp.. Worst case scenario I factory reset and restore my week old backup..
I'm running stock rooted 5.0 with ph1 as my latest update. And if somebody is interested enough to want a logcat from boot to couple minutes in, I'll reboot now, capture the log and post it in a few.
Confused but amused,
I am
The Dude
The log.. I had Logcat Extreme running at info priority, and stopped it after around 8 minutes and just under 22,000 lines. Is that a lot? It seems like a lot. There are a couple power button hits, a menu and a back button press, and also at the end is where I double pressed home and got things back to normal..
Yes, I use xposed, minminguard, unbeloved hosts, and lucky patcher. You'll see them in the log, as well as my Wi-Fi ssid.. I dunno what else might be in there.. Hopefully nothing juicy though. Lol
If there's a way to filter stuff out, or just log the important things let me know and I'll give it another go.

Categories

Resources