[Q] Another "Stuck on the LG Boot Screen" post... - Sprint LG G2

I rooted, some weeks ago, with Towel Root and have been running fine. Last night, I used something to let me add TWRP and this morning, when i plugged by phone in, the screen went all cross-hatchy, like a tightly woven Irish wool blazer. It would clear up if I rebooted, but would come back when I plugged it in, or if I let it sit.
So.. I did a backup and a hard reset, and it got a little better. But TWRP is still there. So, I made the mistake of choosing format, which I'm guessing wiped all including the current image, and now I can only get to the LG screen, with the notification light up top flashing blue to green and back again.
There are several similar options for re-imaging the device back to stock, but I'm not sure which will work for me. I'm not sure holding the up or down arrows, power button, and plugging in simultaneously, will put me into recovery mode and let me install a stock image.
Is there a magic bullet, like there was for the Galaxy Nexus? Install an App on the PC, plug in the phone, push a button and it just goes?
I'm dead in the water right now, so some direction would be appreciated. Unfortunately, I can't try all the variations to see which works. I'm hoping I gave enough info to go on.
Thanks!

cgedansk said:
I rooted, some weeks ago, with Towel Root and have been running fine. Last night, I used something to let me add TWRP and this morning, when i plugged by phone in, the screen went all cross-hatchy, like a tightly woven Irish wool blazer. It would clear up if I rebooted, but would come back when I plugged it in, or if I let it sit.
So.. I did a backup and a hard reset, and it got a little better. But TWRP is still there. So, I made the mistake of choosing format, which I'm guessing wiped all including the current image, and now I can only get to the LG screen, with the notification light up top flashing blue to green and back again.
There are several similar options for re-imaging the device back to stock, but I'm not sure which will work for me. I'm not sure holding the up or down arrows, power button, and plugging in simultaneously, will put me into recovery mode and let me install a stock image.
Is there a magic bullet, like there was for the Galaxy Nexus? Install an App on the PC, plug in the phone, push a button and it just goes?
I'm dead in the water right now, so some direction would be appreciated. Unfortunately, I can't try all the variations to see which works. I'm hoping I gave enough info to go on.
Thanks!
Click to expand...
Click to collapse
You are going to want to go back to stock using the LG Flash Tool and a .tot file if you have the LS980, all other variants of the G2 use a KDZ file and the updated version of the flash tool.
http://forum.xda-developers.com/showthread.php?t=2656275
Then if you get that cross-hatchy screen (which has been dubbed the "white lines issue") You will want to use Cloudyfa's fix.
http://forum.xda-developers.com/showpost.php?p=52414185&postcount=122

Related

[Q] screen dead - help

Rooted my Dinc. Installed CM7. All was well for 3 weeks. Used it one day until the battery went dead. Charged and tried to boot. It appears that it goes through the boot sequence (it vibrates) but nothing comes up on the screen. Nada, black.
Any ideas?
Screen might have went bad. You should just try your best to unroot it before you send it in
Sent from my Incredible using XDA Premium App
Have you tried pulling the battery?
Sometimes the phone can get stuck in a state where trying to turn it on results in a series of vibrations but nothing else happening. Pulling the battery resolves this.
Unless flashing a radio, when in doubt pull the battery.
Pulled the battery and re-booted. Nada.
Returned to the Verizon store. Their tech had no luck and ordered a replacement. Verizon ordered a replacement and left me with the phone. They said that when the replacement comes in they will switch it out. I'm hoping that means I've dodged the warranty issue.
Sent from my Xoom using XDA Premium App
elcap373 said:
Rooted my Dinc. Installed CM7. All was well for 3 weeks. Used it one day until the battery went dead. Charged and tried to boot. It appears that it goes through the boot sequence (it vibrates) but nothing comes up on the screen. Nada, black.
Any ideas?
Click to expand...
Click to collapse
That's odd. I had this problem when I went to unroot my phone, being that I had an SLCD and it did not like the 2.1 stock ROM. The screen was blank but it would vibrate and continue to boot.
If this is the case, you could always try to unroot it and see...Here are some instructions on how to do this (its what I had to do)
I went to unroot and flashed a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the display on the newer batch of DInc, the SLCD.
What I did was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com/?page_id=108 )
Rename it to PB31IMG.zip and place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes (2 minutes to be safe), like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
You can give this a try and see if it works. I know you did not mention unrooting your phone, but if you have nothing on your screen, you can try this

[Q] Problems after restoring in Clockworkmod

Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?
First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App
omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!
Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!

[Q] Phone constantly reboots before getting to CWM or ODIN

So my S2 is stuck constantly rebooting before I can attempt to get the phone into download mode or back to CWM.
The best luck I've had so far is to rather consistently press the power button while the phone is trying to boot. This keeps the phone booting for the longest, and I've even made it into CWM and ODIN doing so. However anytime I stop tapping the power button, the phone will reboot.
At one point I did do a super wipe of the cache and OS, I just haven't been able to flash the phone back to stock. The same behavior occurs with a charged battery, a battery-less phone plugged into the wall, and a phone plugged into the wall with the battery in it.
I've opened up my phone to take a look at the power button placement. The plastic case is not pressing in the button, and when I press it in myself I hear a distinct click noise as normal. I've even pried away the case with no luck.
What next steps do I have? I do not have insurance with t-mobile or warranty of the phone. I do have the knowledge to solder if needed. Are there more options for me to try, to fix this issue?
EDIT: So this time I was able to get into ODIN, after letting the phone sit and do nothing for a week. No idea why it works now. I flashed back to stock. Will give it a day or two and then flash back to custom.
If you can get a computer to recognize the phone it can be fixed using adb or another method.
Sent from my SGH-T989 using Tapatalk
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
ralewis said:
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
Click to expand...
Click to collapse
what i know for sure is that it should be T-Mobile uvlh1 which im 98% sure is the standard base band when i got my phone
but other than that is your phone already rooted?
also when you go in CWM what does it say?
Does it just freeze?
So I did go through with the link and flashed back to stock. Everything seems to be working great now. I did nothing to the phone and it stopped acting up.
What used to happen is the device would act like I was holding the power button constantly. It would simply reboot, but never freeze. It felt Software independent, which worries me that it'll come back.
The problem started slowly, where my phone would reboot on its own here and there. Gradually getting worse. This happened after applying some OTA updates for CyanogenMod10. Though it didn't happen immediately after applying the updates.

Help! It wants to live, but won't go past splash

Phone's been slowly giving me more and more issues. Today I was using it fine, turned off the screen, a bit later, tried turning it on and nothing. This has been a common occurrence, about once a day I have to do a battery pull or plug it in to make the screen turn on, then all is normal. Battery pull got it to boot to the splash screen, but then nothing. Plugged it in, and nothing. Left it plugged it in for about an hour, tried again, still nothing. Unplugged and tried powering on, nothing. Pulled the battery again, and could only get to the splash screen. I'm running JB Sourcery, and have the one selected where the apple rots and then it spells out droid. I get through that and then it does nothing else.
Info: just tried again, had to pull the battery, then I could get the google logo to pop up, but that was it.
Info the 2nd: plugged it in for 2 hours, the graphic showed it fully charged. So I tried booting it and again, same response..gets through the boot splash screen, but goes black after. Pressing power button does nothing, doesn't even get the charge graphic to show up.
Info the 3rd: I left it be this time thinking maybe it was just really laggy or something, but after 15 minutes, still nothing. But I can feel a bit of heat as if it is on.
Info the 4th: I can get into bootloader and recovery fine. I was even able to make a backup (only thing I could think to do in there that would take some time and not risk screwing it up more) So it's not a battery issue, seems to be something with the rom.
Please help
Even though the phone is rooted and custom rom, can I take it back to Verizon? I've only had the phone since December. If I could do that, is there any way to get all the pics off of it first?
try to flash stock image from google
Cristi_10 said:
try to flash stock image from google
Click to expand...
Click to collapse
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
VooDooCC said:
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
Click to expand...
Click to collapse
deja vu.....million times.
with a little search i found this http://forum.xda-developers.com/showthread.php?t=1626895
Was able to wipe data/cache and re-flash the rom. Seems to be working for now. I think I'll go back to stock (thanks for the link samersh) and see if I'm still having issues.

VM Soft-Bricked...I know...

Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?

Categories

Resources