[RESTORE][TOT][OFFICIAL][M] Sprint LG LS991 ZV9 TOT - Sprint LG G4

Update 12/17/2015: This is now official since Sprint has announced the release.
Well, you got it here before even it was announced. M has come to our G4 and you can flash it now using this TOT.
Read the second post for further information on how to downgrade and use LGUP. Once you're on ZV9 it's the only way to downgrade and should be your preferred flash method.
And with that said, here's the fluffy Marshmallow goodness!.
If you need the steps, use them as provided by Autoprime here.
Enjoy!
<LINK REMOVED>
Happy holidays everyone!

very nice
OK so lets do an overview of how to flash TOTs from now on. Steps below will allow you to flash ZV9 (or higher) and also downgrade back to ZV6. Don't flash ZV5 TOT if you're on ZV6 or higher! ZV5 is qfuse v1.. ZV6 and ZV9 are qfuse v2. You can only flash equal or higher qfuse versions... NEVER lower. I mean, technically you can flash ZV5... but you will not be able to boot the phone after doing so.
Thanks to some testing from @Awesomeslayerg I think we've worked out all the kinks. I don't have a Sprint G4, so without him the specific details laid out below would not have come so quickly.
1. Download both LGUP msi files HERE and install them on your PC.
2. Boot your phone into Download Mode [Remove USB cable in phone. Power off phone. Hold Volume Up then plug in USB cable]
3. Open LGUP, select your phone model. If it says unknown, disconnect phone/reopen LGUP and try again.
4. With LGUP now opened, select the "Upgrade" option. Then below that.. select the TOT you wish to flash then hit START.
5. That's it! Just wait for it to finish flashing. LGUP makes things quite simple. You don't even have to use COM port 41 any more. Always use the upgrade option.. even when downgrading.
If LGUP doesn't wipe your data and you'd prefer to have it wiped for some reason or another... simply boot into stock recovery after the TOT flash and run a factory reset.
If you have ignored the steps above and decided to use the old "LG Flash" method, forgot to check off "Board DL" and are now stuck on the "2" screen..
1. Use LGUP to flash ZV6 and get stuck at blue screen with red "2".
2. Power off phone and close LGUP.
3. Boot into Download Mode again.
4. This time.. instead of using LGUP.. use the original LG Flash method HERE.
5. Make sure you set LG Flash to use "Board DL" at the bottom of the screen where u select DLL and TOT.
6. Should be able to flash either ZV6 or ZV9 using LG Flash (with Board DL option).
LGUP FTW! :victory:

would anybody be willing to DD a backup of the system and modem and kernel (boot) partition? is 6.0 root able?
if we can get backups we can just flash those three and should be good...

So as of now, there is no OTA zip to install via recovery?
I can't wait!

awwwweesome!

andrewwm said:
So as of now, there is no OTA zip to install via recovery?
I can't wait!
Click to expand...
Click to collapse
No OTA if it's not an official build. AFAIK there is no mention of this anywhere... except here.

Root
I sent a pm to chainfire i think there may be a way to root this from within the tot with some modifying.

I should've waited. The file flashed the first time and then my phone rebooted. Now I'm just stuck on a factory reset 2 screen.
I've tried multiple times to flash it again and it just leads to download failed in the LG Flash Tool.
Am I screwed, for lack of a better word?

s049031 said:
I should've waited. The file flashed the first time and then my phone rebooted. Now I'm just stuck on a factory reset 2 screen.
I've tried multiple times to flash it again and it just leads to download failed in the LG Flash Tool.
Am I screwed, for lack of a better word?
Click to expand...
Click to collapse
Simple mistake and easy fix...you just missed selecting "upgrade board dl" as shown in step 8 here: http://forum.xda-developers.com/showthread.php?p=63041565
Now to fix....pull the battery. Put the phone back into download mode (vol up + plug in usb) and just repeat the steps only don't forget to select UPGRADE BOARD DL. [emoji2]
Sent from my LGLS991 using Tapatalk

No thoughts or comments on this yet? I figured it would be a bigger deal but I guess a few people already jumped ship. I'm super excited to try it just wanna know if it's daily driver status. I hate upgrading then downgrading.

Swetnes said:
Simple mistake and easy fix...you just missed selecting "upgrade board dl" as shown in step 8 here: http://forum.xda-developers.com/showthread.php?p=63041565
Now to fix....pull the battery. Put the phone back into download mode (vol up + plug in usb) and just repeat the steps only don't forget to select UPGRADE BOARD DL. [emoji2]
Click to expand...
Click to collapse
And just to be on the right page. Which dll file should I be using?
I'll give it another go when I'm home. Thanks for the help.

s049031 said:
And just to be on the right page. Which dll file should I be using?
I'll give it another go when I'm home. Thanks for the help.
Click to expand...
Click to collapse
The one on step 2.
Sent from my LGLS991 using Tapatalk
---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------
The ONLY issue that I have found so far is with Android Pay...it says that it cannot verify if I am running a compatible version of Android...really kind of ironic! My only thought is ZV9 is not official yet so maybe that's why.
Sent from my LGLS991 using Tapatalk

Okay, thank you! I'll let you know if it works.
Sent from my Nexus 5 using XDA Free mobile app

Reporting back. Just got through my first day with is. So far everything works flawlessly and smooth. But I'm at 13% at typing this and it's only had about 8 hours of life with abou a 1/3 of that actual SoT with auto brightness. I got about 28 hours with full brightness before the update and more SoT I'm stuck for my love for marshmallow so far but the battery life might be a deal breaker for me. Haven't tested Android pay get. Waiting for a new credit cerd in the mail. Will report back.

Giston141 said:
Reporting back. Just got through my first day with is. So far everything works flawlessly and smooth. But I'm at 13% at typing this and it's only had about 8 hours of life with abou a 1/3 of that actual SoT with auto brightness. I got about 28 hours with full brightness before the update and more SoT I'm stuck for my love for marshmallow so far but the battery life might be a deal breaker for me. Haven't tested Android pay get. Waiting for a new credit cerd in the mail. Will report back.
Click to expand...
Click to collapse
That sucks about the battery life. But it's a start

We already have reports of not being able to TOT back to LP5.1 after taking this TOT 6.0M update.
Also, i have gotten to fastboot mode and done some testing, from ZV6
http://forum.xda-developers.com/showpost.php?p=64167865&postcount=330

I followed the steps above and still getting an error. Here's a screenshot: http://i.imgur.com/19gg1Tm.jpg

s049031 said:
I followed the steps above and still getting an error. Here's a screenshot: http://i.imgur.com/19gg1Tm.jpg
Click to expand...
Click to collapse
That's the error I get when I kept trying to TOT back to 5.1. I do believe, as @Agimax said, once updated, you're stuck. I'm willing to do any testing anybody needs me to do. @Agimax just lemme no if there is anything I can do. I'm willing to do whatever it takes!

s049031 said:
I followed the steps above and still getting an error. Here's a screenshot: http://i.imgur.com/19gg1Tm.jpg
Click to expand...
Click to collapse
When did it give you that error? Did the phone reboot into miniOS? If you do get into miniOS you'll be fine. I also get the error, but only after rebooting after the initial flash.
Sent from my LGLS991 using Tapatalk

I get to the miniOS just fine. The error shows up anytime I try to flash the TOT and DLL. I tried a different computer and it did the same thing.
I'm on my backup phone right now, I figure I'll just have to wait for the official release or something.
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
The first time I flashed, everything went fine and the phone rebooted, but went straight into the red 2 screen.

Related

[Q] LG Thrill GB w/ClockworkMod Recovery

(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think

Update from zip aborted

In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol
I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.
well i just bricked my self on the update lol
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2
azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)

Hard bricked??

I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
waylo said:
I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
Click to expand...
Click to collapse
Did u pull battery?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Did u pull battery?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
waylo said:
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
Click to expand...
Click to collapse
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
waylo said:
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
Click to expand...
Click to collapse
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yeah, next time I will go the KDZ route to return to stock. Bummer!
Look up G2 unbrick.
Sent from my LG-H811 using Tapatalk
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
MrSteelX said:
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
Click to expand...
Click to collapse
Thank you all for the education.
10N hadn't been out for a day, so I was concerned this would raise some red flags at the store. Otherwise would have kept it on--a vast improvement over 10H.
I haven't been on LG at all previously, so all this info would have been nice to know beforehand. =/
Oh well, live and learn.
Of course it's similar with most phones (i.e. Samsung won't let you downgrade bootloaders/modem), but typically it will just not take, rather than brick. As I recall, what happened to me is an inherent danger with TWRP zip flashing.
Yeah, the KDZ failed 10h flash would have been a nicer way to let me know I am trying to do something very very bad.
I looked at some LG2 unbrick notes. Most of them talk about the connected computer showing several hard drives when connected. At this point, I can't even get the computer to show the qhsusb_bulk driver install attempt again. Any tips on how to get the phone to power on the right way to allow for this?
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Biker1 said:
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Click to expand...
Click to collapse
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
waylo said:
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
Click to expand...
Click to collapse
I hear ya.
I needed to make an updated 10h Nandroid anyway.
Don't hold me to it but from what i can tell we aren't being locked out of downgrading in future updates, just in 10n as it's main purpose was to patch stage fright which was a massive security flaw and they felt it unsafe to allow downgrade to an insecure state
so uh huge question here...i got my phone from tmobile aand it was 10h....so i flashed twrp and it worked...but now no matter what rom i run i get a hang until i reboot..then when i reboot the phone spazzes the **** out...help anyone thanks
Your problem is unrelated to this thread. Your phone is buggy but not bricked.
Last night I tried to root my phone. I pushed a rooted image. It completed and rebooted. Then I got a security error 11. I then pushed a factory image using the KDZ method. Now it's completely dead. Pulled battery a few times. Nothing. Held down power and volume down a few times. Nothing. Plugged it in to charge. No LED light, no battery charging animation, no security error. No nothing. I also connected it to my PC with a usb cable while holding in volume up. Nothing. A whole lot of nothing. I contacted LG and they sent me a fedex label. It's now in the mail.
Question: I have the naughty image on there, but as far as I know it never actually took so I never had root. Also, presumably the factory image is what is currently loaded. So will they be able to detect that the phone is rooted? If they find the naughty file will they consider that in the same way as if I had succeeded in rooting it?
I knew at the time that I was doing something that would void the warranty so I can't complain too much. So then in the process of finding that I was naughty will they unbrick it at least to the point where I can pray for a future fix? I can say "gosh darn just send it back as is" and hope that they helped me out while detecting my naughtiness. Or if I say, "ok you got me, what's it gonna cost for you to unbrick my phone?" will they fix it at a reasonable price? If not, can I run it over with my car and pay the $150 deductible on my insurance? Basically, where am I at?
this is lg we are talking about. They will do 1 of 2 things to fix it, 1. reflash the whole emmc chip call it done. 2. swap out the mother board and call it done.
So sorry, it was not a bad flash I did this exact thing tried to revert. You are hard bricked I just turned my phone in though because I did it on day 2 I had it and got a new one. Just warning people you upgrade and try to go back you will get a hard brick.
I did the same thing as smkyle, but I haven't turned mine in yet. Is there any hope for fixing it.
Edit: In device manager it showed "QHSUSB_BULK" and then stopped. I have a spare battery and charger so after swapping out the battery the computer read the phone again, but this time installed drives and now shows "Qualcomm HS-USB QDLoader 9008 (COM7)".

ZV6 Update Discussion

Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.
Agimax said:
Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.
Click to expand...
Click to collapse
Will the old root method still work?
SantinoInc said:
Will the old root method still work?
Click to expand...
Click to collapse
The factory reset protection has me curious. I think the better question is can then somehow block TOT flashing.
We won't know if the old root method will mess things up. I would just wait for a v6 image to be released. Someone did make a post as a how-to root the image yourself if you can get it off the phone. I would just wait.
someone needs to capture the OTA and get it to me so I can check it out.
I'd suggest holding off on actually applying the update until we know what's what.
Thx in advance.
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Much thanks to you guys! Work some magic for us!
mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.
mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
So I can install this in the stock recovery (I am not rooted) because there is an option?
(I am doing it now but it seems to be stuck on "patching system files", uh oh)
edit: I am fine now, it installed fine. Was a little un-patient
I notice now the icons at the top are more stock android like with the "!" point if there is no internet. Pictures
Also the phone "feels" faster, I hope we can uncover what is under this update.
I hope this doesn't fix my free hotspot trick.
So if the OTA pops up, I can download and install it and still have root? Or has that been undetermined to to this point?
autoprime said:
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.
Click to expand...
Click to collapse
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?
SantinoInc said:
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?
Click to expand...
Click to collapse
I dont think you'd be able to keep it. You'd most likely have to re-root with a ZV6 rooted system.img... same way you rooted ZV5.
How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe somebody can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol
argh2000 said:
I est gues is that the game is not meant for VGA screen
Click to expand...
Click to collapse
How do you create a ZV6 rooted boot image?
KillerDisturbed said:
How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe you can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol
I have Skype also if that's something that you could do, cause I'd really appreciate the help
Click to expand...
Click to collapse
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk
Swetnes said:
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
SantinoInc said:
How do you create a ZV6 rooted boot image?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62369954
Sent from my LGLS991 using Tapatalk
---------- Post added at 11:36 PM ---------- Previous post was at 11:33 PM ----------
This update does include the Stagefright fix.
Sent from my LGLS991 using Tapatalk
KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Can this be done even on rooted ZV5?
Probably. I installed the update and have noticed a few small touches in the UI, but notably a more responsive keyboard and overall faster phone. Knock code is also a bit more consistent and snappier for me as well, so I'll probably be using that from now on. Great update from the looks of it so far.
Sent from my LGLS991 using XDA Free mobile app
KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk
stam27 said:
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
You may need to pull the card out and put it on a computer and format it using SD CARD FORMATER. If you Google it you will find it. I know with other phones I've had that solved recovery being able to read it. You are copying to the "external" sd card?
Sent from my LGLS991 using Tapatalk

H811 completely dead

Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.

Categories

Resources