Database Users

LG G4 (all variants) Unlock and Root Discussion/News (ONLY)

Hoyo folks.
So I'm sure you've all seen the plethora of "Do we haz root?" "How 2 unlok?" "unlok guide here"(which doesn't work) ect. Here in this thread I will attempt to summarize the current status of Unlock, Custom Recovery, and Root for each model.
Some of our devs now have Devices in hand, THANK YOU TO ALL THAT HAVE DONATED! It REALLY helps the entire G4 community! Now we wait with baited breath. (No pressure guys)
So without Further ado, here is a list of the status of all devices.
CURRENT Unlock/Recovery/Root Status, in order of success:
H815 (Europe Open model ONLY) -
Unlocked? - YES (Via LG's Official Unlocker)
Custom Recovery? - YES (TWRP info)
Root? - YES (Root Info)
NOTE: LG's offcial unlocker is a PERMANENT change. You cannot Re-lock, if you wanted to send in for a warranty claim. If you aren't willing to do that, lets wait and see if the dev's efforts will pay off with a more friendly unlock (which it may or may not)
H815 (Asia) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (USA) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (France) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815TR (Turkey) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818P (Thailand) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818N -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H811 (T-Mobile) -
NO to all - and "adb reboot bootloader" doesn't work
H810 (AT&T) -
NO to all - and "adb reboot bootloader" doesn't work
LS991 (Sprint) -
NO to all - and "adb reboot bootloader" doesn't work
F500S -
NO to all - and "adb reboot bootloader" doesn't work
F500K -
NO to all - and "adb reboot bootloader" doesn't work
F500L -
NO to all - and "adb reboot bootloader" doesn't work
VS986 (Verizon) -
No to all - and "adb reboot bootloader" doesn't work, AND no "Enable OEM Unlock" in developer settings.

I suggest editing the thread title to be more concise/official since that is the intent of this thread:
Something like "LG G4 (all variants) Root Discussion/News"

After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!

For any one that ones the source code is available from LG.
T-Mobile
International
Both kernels are compile-able with a little finagling.
On Root:
From what I can see in the International code is there are the defprefs for all of the p1 versions, and it doesn't "Appear" to have ping pong patched.
I have heard "rumors" that jcase , autoprime and thecubed, are working on a root for the device, but I have not heard from either of them. They did just release pingping v6 which supports the M9, a 64-bit kernel, meaning they have made one that works with the 64-bit linux kernel. For any one curious about their progress you can always check them out on twitter. For those of you posting about root and such, you can always see if there is anything you can do to support them in their efforts.
Thanks for making the thread, I think this phone will be a fun one, and I do expect to see some great things happen.
Have a good day all!

H818P Thailand can use adb reboot boot loader

MicroMod777 said:
After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!
Click to expand...
Click to collapse
Thanks for confirming. Same behavior on my TMo G4.

Not as skilled as some but I do currently maintain the HTC One M8 for DirtyUnicorns.
I have my G4 pre-ordered from Verizon. It has shipped today and current tracking has it arriving Tuesday 6/2. If no one beats me to it, I will post at least the basics of how that variant functions in terms of adb and fastboot. Anything else needed I will gladly try to provide from the VZW variant.

Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Yes

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.

barcodelinux said:
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.
Click to expand...
Click to collapse
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
I know with the last LG I had, the Optimus L90, there was a LAF partition the you had to zero out to get to fastboot. Once that was done, you could:
Code:
fastboot oem unlock
Now this was on a T-Mobile device, and T-Mobile is known for not locking bootloaders. I don't remember having an unlock.bin file, but I could be mistaken.

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
Well we have 14 days to return it if LG doesn't give us what we need!

MicroMod777 said:
Well we have 14 days to return it if LG doesn't give us what we need!
Click to expand...
Click to collapse
That's true. I actually haven't purchased mine yet but I had high hopes for this device. Was going to be my first carrier-supplied phone. I guess I'll wait for the oneplus 2 if this doesn't get sorted out.

Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.

barcodelinux said:
Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.
Click to expand...
Click to collapse
You need to install the LG device drivers first

has anyone tried to get into the bootloader on linux? a couple phones i had, you had to use sudo, then type the absolute path to platform-tools, even if you open terminal within the sdk, I.E.,
sudo /home/username/SDK/platformtools/fastboot oem unlock " or adb reboot-bootloader"
sometimes had to use su, im sure you could do the same on windows.
anyway worth a shot.

H815 - International variant here with me can officially use adb reboot bootloader
fw: V.10A

So far i got this but after this pc won't recognize phone have to reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imageshack.us/i/exlSOF19j

Worked for me on my LG-H815... It's possible to check the status of the bootloder.
Mine says it's locked. Now there's an option to: "fastboot flash unlock unlock.bin"
But where is the unlock.bin file?

[Be Aware] LG G3 bootloader unlock might come soon

G4 test devices came with a option called "Enable OEM Unlock" and when i searched for it in v20i there was no such information. but guess what it has changed!
from v20i > v20p LG has added much Enable OEM Unlock "aka bootloader unlock" code in the settings & framework that wasn't there before (and yes we can "dirty enable that option" but it's for now just a placebo so i rather won't share it.
Note: it seems like LG is implementing a bootloader unlock similar to Sony! Once you unlock your DRM partition will be broken! before (once available) make sure to backup your DRM partition!
.*Unlocking the phone will disable certain functions of your phone.
When unlocking the bootloader, the DRM protection of your phone will become untrusted.
Some applications which require DRM protection may not work anymore or block certain functions due to this untrusted DRM.
Common examples are applications which offer download/streaming of paid multimedia content like music and movies.
Click to expand...
Click to collapse
But if you want to check for yourself.
add this line to in the end of build.prop
Code:
ro.frp.pst=true
The discovery make's the LG's "words" about letting G3 users unlock their bootloader in the near future possible. (hopefully) They can whenever they wan't decide to just forget about it. But as it seems they are going to implement this feature to the G3 as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I doubt many firmware versions before v20p has this info (v20i) should not include this info.
What does this do?
Pretty much lets you enable fastboot without breaking the download mode and letting you select if you want to unlock your bootloader.
How did I get this on G3?
Simple buildprop edit after I discovered the systemproperties;->get
Simply added the info which it looks for and it is visible in developer settings
But as of now it doesn't do anything. But its a preparation by LG
Sent from my LG-D855 using Tapatalk

Sweet, that's awesome!

What is the benefit of the boot loader؟؟

The positive thing when unlock
bootloader is
1. No bump needed since you have agreed to the unlock EULA*
2. All images that is unsigned can be flashed with fastboot and won't give you error if not signed.
The con
3. It will void your warranty (as you agree when unlocking) however if you're still satisfied with bump (unless you aren't locked out from it) you wouldn't need the BL unlock but for thus "who updated" and Lost bump functionality. this is the way to go. (If you don't care about warranty or if you have a insurance that covers it up)
* EULA
*Once your phone is unlocked, it will no longer be covered by LG warranty.
As we cannot guarantee the proper operation of our hardware with custom software, we are not able to maintain the full scope of warranty for your device after you have unlocked the bootloader.
Because of that we have a responsibility to let you know that defects which may result from, or were caused by custom device-software may not be covered by LG warranty.
LG can no longer guarantee the full functionality of your device after you unlock the bootloader. Unlocking your device may cause unexpected side effects that may include but are not limited to the following:
** -*Your device may stop working.
** -*Certain features and functionalities may be disabled.*
** -*Your device may become unsafe to the point of causing you harm.
** -*Your device becomes physically damaged due to overheating.
** -*The behavior of your device may be altered.
** -*Some content on your device may no longer be accessible or playable due to invalid DRM keys.*
** -*All your user data, settings, and accounts may disappear. (Therefore, we recommend that*you*backup all your data).
** -*Software updates delivered via LG FOTA (Firmware Over the Air) or Web Download services may not work on your device anymore.
*
LG will not be responsible for the damages caused by any*custom software being flashed to your phone
Read more at: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once its available for the G3 in the mean time. Get prepared ?
Sent from my LG-D855 using Tapatalk

Edit bummer
Name:
aaay shinRegistered:
16-OCT-2012Post: 75
Re: LG G3 Bootloader
Posted : 20-JUL-2015 in response to :*SmokeyVR
Hello,*
Currently, only LG G4 (H815) for the European open market supports unlocking the bootloader and we have no plan to support bootloader unlock in previously launched models.*
We apologize for any inconvenience that this may cause.
Thank you.
That's really not cool
Edit more bummer?
jeongeun.jeon[http://developer]Name:
Ragina JeonRegistered:
29-OCT-2012Post: 58
Re: Re: Re: Re: Re: Re: Re: Re: Re: Camera2 api /driver support
Posted : 23-APR-2015 in response to :*
Hi,
We won't fully support camera2 apis in G2 and G3.*
It is a chipset issue, and the vendor does not support those APIs on their previous chipsets.
Thanks.
But its is said nexus 5 that has same chipset fully supports it? Is that true
Sent from my LG-D855 using Tapatalk

Nexus has imx179
Sent from my LG-D855 using Tapatalk

I really hope that they will unlock it, because bump is not stable on my device

LastStandingDroid said:
G4 test devices came with a option called "Enable OEM Unlock" and when i searched for it in v20i there was no such information. but guess what it has changed!
from v20i > v20p LG has added much Enable OEM Unlock "aka bootloader unlock" code in the settings & framework that wasn't there before (and yes we can "dirty enable that option" but it's for now just a placebo so i rather won't share it.
Note: it seems like LG is implementing a bootloader unlock similar to Sony! Once you unlock your DRM partition will be broken! before (once available) make sure to backup your DRM partition!
But if you want to check for yourself.
add this line to in the end of build.prop
Code:
ro.frp.pst=true
The discovery make's the LG's "words" about letting G3 users unlock their bootloader in the near future possible. (hopefully) They can whenever they wan't decide to just forget about it. But as it seems they are going to implement this feature to the G3 as well.
View attachment 3386474
I doubt many firmware versions before v20p has this info (v20i) should not include this info.
What does this do?
Pretty much lets you enable fastboot without breaking the download mode and letting you select if you want to unlock your bootloader.
How did I get this on G3?
Simple buildprop edit after I discovered the systemproperties;->get
Simply added the info which it looks for and it is visible in developer settings
But as of now it doesn't do anything. But its a preparation by LG
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
I got something figured out by playing brick my device (d855) Marshmallow... Maybe it's usefull to get a step closer to an unofficial bootloader unlock.
But first i have to say doing so, will brick your device and you can only bring back using the willcracker tool by short-circuit the board. And flashing the aboot back!
I have edited the build.prop and added the string from first post. And began to link different partitions like so
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/aboot
After reboot i can mark the check box oem unlock in development menu.
With =true instead the string you can't do this. This changes something at the aboot partition what makes the aboot invalid. And ending in a dead mobile.
I am now at work, i have both aboot files to compare them later to see what changed.
Maybe it is for some one interesting and will help to figuring more things out.
I did this with untouched partitions.. Only SU to get the rights for editing the build.prop
Greets
SnXo

Could you clarify if the D851 which comes with an unlocked bootloader has a trusted DRM partition?

rzracer2 said:
Could you clarify if the D851 which comes with an unlocked bootloader has a trusted DRM partition?
Click to expand...
Click to collapse
No i can't... Sorry... I do not have a D851 only a D855 maybe some others can.

SnXo said:
I got something figured out by playing brick my device (d855) Marshmallow... Maybe it's usefull to get a step closer to an unofficial bootloader unlock.
But first i have to say doing so, will brick your device and you can only bring back using the willcracker tool by short-circuit the board. And flashing the aboot back!
I have edited the build.prop and added the string from first post. And began to link different partitions like so
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/aboot
After reboot i can mark the check box oem unlock in development menu.
With =true instead the string you can't do this. This changes something at the aboot partition what makes the aboot invalid. And ending in a dead mobile.
I am now at work, i have both aboot files to compare them later to see what changed.
Maybe it is for some one interesting and will help to figuring more things out.
I did this with untouched partitions.. Only SU to get the rights for editing the build.prop
Greets
SnXo
Click to expand...
Click to collapse
What you mean with ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/aboot
?
The ro.frp shouldn't be linked there it should be in build.prop. also what could be done (eventually, hopefully) is to get it like my s5 neo.
Once trigger OEM unlock it will allow you to flash modified firmwares.
But is this really needed or is it like they said, that the bootloader locked on 5.0 or later? Is that the reason? Because using bump isn't really hard and I don't see why it's needed if it isn't locked on later bootloader.
Sent from my SM-G903F using Tapatalk

You have me miss understand.. My English is not the best.. Sry for that..of course this string have to be in build.prop... But only if i link the aboot like this ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/aboot , the Oem Unlock Check box stays checked.
Instead ro.frp.pst=true
And something is happen with the aboot after doing so then it is no more valid and device stick in qhsusb mode. After trying reboot or adb reboot oem unlock.
I'll playing with this further und looking do figure more out about this. Brick my device is a funny thing

Can you backup the aboot?
Poslano sa mog LG-H815 koristeći Tapatalk

SnXo said:
You have me miss understand.. My English is not the best.. Sry for that..of course this string have to be in build.prop... But only if i link the aboot like this ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/aboot , the Oem Unlock Check box stays checked.
Instead ro.frp.pst=true
And something is happen with the aboot after doing so then it is no more valid and device stick in qhsusb mode. After trying reboot or adb reboot oem unlock.
I'll playing with this further und looking do figure more out about this. Brick my device is a funny thing
Click to expand...
Click to collapse
Hmm that's rather interesting. Don't know if that's needed. Will check one thing later
Sent from my SM-G903F using Tapatalk

bender_007 said:
Can you backup the aboot?
Poslano sa mog LG-H815 koristeći Tapatalk
Click to expand...
Click to collapse
aboot after mark oem unlock and the original one....klick
Greetings
SnXo

SnXo said:
aboot after mark oem unlock and the original one....klick
Greetings
SnXo
Click to expand...
Click to collapse
Thank you , will dload and check out
Poslano sa mog LG-H815 koristeći Tapatalk

@SnXo have you tried ro.frp.pst=/dev/block/persistent
edit
according to G4 build prop it should be
ro.frp.pst=/dev/block/bootdevice/by-name/persistent
it's the path on Samsung can be the same on G3 can't tell :3
not sure if that partition is existing on LG
good luck.
Sent from my SM-G903F using Tapatalk

We have a persist partition on our mobile.
I have tried by linking this part: /dev/block/bootdevice/by-name/persist but this does nothing.
greets
SnXo

SnXo said:
We have a persist partition on our mobile.
I have tried by linking this part: /dev/block/bootdevice/by-name/persist but this does nothing.
greets
SnXo
Click to expand...
Click to collapse
hmm strange that's how it's done on the G4
Sent from my SM-G903F using Tapatalk

[UNBRICKING] Research on Unbricking Method for Zenfone 2

TESTERS NEEDED
The main intention of the threat was to find a way to restore a completely bricked zenfone 2. It is apparent that we are not having a spare bricked device to test upon.
Anyone with a Bricked Zenfone 2, A PC, and willingness to devote time, please participate.
Otherwise, this thread is going no where as we people who are searching for methods do not have bricked devices(And do not want to specially brick them for testing)(Obviously!!!) and all talks are in taking us nowhere.
Click to expand...
Click to collapse
"Bricked Devices" is a regularly heard phrase on XDA. Sadly, Asus devices dont come with a dedicated PC Companion or PC Suite software which can safely unbrick a Zenfone just in case someone is able to damage fastboot.
That Said, there have been Zenfone 2's that have been Hard Bricked in the past months. Fortunately, many of them may have got replaced as the device comes with a One Year Warranty. But what after that...???
So, i wanted to do some research upon this unexplored topic.
On successfully Hard Bricking your device, you will see something like this :highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( credit to the one who bricked and clicked)
I do not have a bricked device, but if anyone can get one and test stuff, we may end up getting something concrete to restore in future.
So, i came across a page: http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
But soon i understood that all these things are foreign to me ( So far ).
Also, The drivers for the SOC are for CloverView Plus Devices.
It would be seriously great if we can successfully recover from corrupt fastboot. As without fastboot we can do absolutely nothing.
I request senior members, Devs and all others to provide inputs and links and keep this thread productive.
Who knows, someday we may end up in a situation without warranty and with a corrupt fastboot.
I will keep on updating this thread with updates from your side
Lets Start.

So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.

cmendonc2 said:
So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.
Click to expand...
Click to collapse
Exactly!!. We need something that works on Moorefield

[email protected] said:
Exactly!!. We need something that works on Moorefield
Click to expand...
Click to collapse
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.

cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.

Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other

tactician10 said:
Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other
Click to expand...
Click to collapse
Well, thats what XDA is here for.
Learning is a never ending process. And i have learnt a lot from others in this place.
And regarding this thread being inactive.
I have got a few things, but they seem irrelevant to me. Searching for something really solid in this regard. No point in posting irrelevant findings from my side and bumping up the thread.
I am going to get a bricked Zenfone 5 (Sure) and Zenfone 2(Hopefully) from a local repair shop.
Will try doing serious software damage to the Zenny 2 and will then try to recover. Lets See!!

i have this problem, broke my fastboot

Does your phone bootup???? Does Android bootup?
If it doesnt, you are currently out of luck
As already said by @cmendonc2 , we need someone senior to extract some files

@edit@
I solved it.
I reflashed recovery via Adb in screen selection "recovery mode/bootloader/normal"
I'm very happy

test subject..
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks

Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??

Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
[email protected] said:
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??
Click to expand...
Click to collapse
ZE551ML / ZOOA
It bootloops when i try to boot it. I get the usb symbol when i try to fastboot. I wanna try using intel phone flash tool but require .xml flash file within a stock Rom .zip file. I looked everywhere but i can't find a zip with .xml flash file.

moorefield driver
[email protected] said:
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.
Click to expand...
Click to collapse
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.

We need some experienced dev to extract these files for us
Without that, there is no option

levi1232005 said:
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.
Click to expand...
Click to collapse
Hey there!!
Check out this page: http://forum.xda-developers.com/general/xda-assist/intel-phone-flash-tool-t3129091. Its for Zenfone 5
The Guy has stated that he found the Necessary files by unpaking the boot.img,which can be found in the firmware zip available on Asus Support website.
Alternatively, you can get it from Here. But these are older ones. I would recommend the Asus website though.
The Intel Phone falsh tool is available at https://01.org/android-ia/downloads/intel-phone-flash-tool-lite . Try it out.
I have wiped my Linux and windows partitions as i am installing Windows 10. So this is all i can help you with. If you need any information, Just Ask. I will do my best to help.
As for extracting the boot.img, do a quick google search. XDA has a thread for that. You need either Linux or cygwin.
All the best!!!!
Disclaimer: I have not tested these things. Try at your own risk

cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
Hey,
I just stumbled upon something.
I downloaded the latest OTA zip package (20MB) of the ze551ml
I opened the ifwi folder
And i found the bin files. DNX FW etc of various zenfone variants.
Can you throw some light on this???
P.S.
Folder screenshot attached!!

Here's some more info I found on the IFWI images:
Two special IFWI images are used for booting in this mode: _dnx_fwr.bin and _dnx_osr.bin. These comprise a simple flash tool that writes a raw image to the eMMC boot partitions and another to the main eMMC space. xFSTK is provided with paths to the IFWI image and a eMMC image. The eMMC image contains an OSIP header (location/size of U-Boot in eMMC, load address, and entry point), a partition table, and partitions with U-Boot and the U-Boot environment.
Click to expand...
Click to collapse
So the dnx_fwr.bin is probably this file:
Code:
dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
The ifwi.bin is probably this file:
Code:
ifwi_ann_a0-mofd_v1-ze551ml.bin
I checked the MD5sums of the different versions and they are different. I guess we need a bricked ZF2 to test and see. Although we still don't have the OSR files. Perhaps @shakalaca can help us.

Okay right
I just had one last week. I tried everything i could. Finally i gave it back.
And Today i stumbled upon this.
Ill see if the guy still has that bricked zen.
Thanks for your reply
Sent from my ASUS_Z00AD using XDA Free mobile app

Good day sir, i was just wondering if this reseach is still going. Still unable to find any solution to my hard bricked zenfone 2 ZE200ml. Im somehow counting on this. Goodluck!

Unlocking Bands in MOTO G 2015 (PARTIALLY WORKING)

SORRY FOR MY ENGLISH !
Guys i just found i way to connect the phone with QPST and modify the RF BC CONFIG (1877). It actually made changes because i see new bands when check it with 4636 code . But the radio turns off and on constantly.
Maybe i'm doing something wrong and with you guys can make this working
Here is a tutorial how i make this parcially working
1- Download Unlock_bands_of_your_qualcomm_device!.zip (i can't post it is illegal) and install QPST
2- Then reboot your phone to Bootloader and select BP Codes
3-The phone will boot normally and you will see in your "Device manager" three new devices with a exclamation mark, there is one that is the correct in my case is ID-HARDWARE USB\VID_22B8&PID_2EC1&REV_????&MI_00, so you need to force a driver install like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4-Once you finish the driver install, you go to QPST Configuration, press "Add New Port", select COM1 and manually rename it with the port that corresponds to your phone. So if you do it correctly you will see in the ACTIVE PHONES tab something like this:
5- From this step you can follow this guides
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031

You probably need a modem.img that will support the frequency you are using. It could be theoretically possible to have the mother of all modems which supports every frequency and then we may be able to actually have fully region-free devices for roms, as well, since an improper match between a region's rom and modem will cause a forced bootloop.

hp420 said:
You probably need a modem.img that will support the frequency you are using. It could be theoretically possible to have the mother of all modems which supports every frequency and then we may be able to actually have fully region-free devices for roms, as well, since an improper match between a region's rom and modem will cause a forced bootloop.
Click to expand...
Click to collapse
so probably the locked frequencies are soft-coded ?. And the only way to unlock bands at least in this phone is with a modded modem.img ? . I hope someone can figure out :fingers-crossed:

Couldn't get mine to work.
@dannygoround

dannygoround said:
Couldn't get mine to work.
@dannygoround
Click to expand...
Click to collapse
What problem do you have ?

lexer98 said:
so probably the locked frequencies are soft-coded ?. And the only way to unlock bands at least in this phone is with a modded modem.img ? . I hope someone can figure out :fingers-crossed:
Click to expand...
Click to collapse
modem.img is just a ZIP file filesystem for the modem partition... On the old Nexus 4 we used to take an old data modem radio (0.33) that supported LTE and use it with a new WiFi radio (1.07) and it worked perfectly. The key was we could get a data radio that supported LTE.
The problem is the radio files themselves inside the image are binary (soft)firmware images, you can't just edit it to enable this or that. To make additional bands work we would need to get a mobile data radio file that has support for all bands, likely the only one in existence, if it exists, are in the hands of Motorola R&D.
Without some kind of an "all bands" region-free engineering radio file, we are probably SOL unless someone can figure out how to stop the forced bootloop if the modem and the ROM image don't match regions.

Would it be possible not to unlock all the bands but only to convert to a different version (say from xt1540 to xt1541 ...)? Flash the region appropriate modem, unlock only the bands that should be supported by that modem and get a stable moto g working on different bands than the ones we used to have?

mandibitola said:
Would it be possible not to unlock all the bands but only to convert to a different version (say from xt1540 to xt1541 ...)? Flash the region appropriate modem, unlock only the bands that should be supported by that modem and get a stable moto g working on different bands than the ones we used to have?
Click to expand...
Click to collapse
TBH, I don't know... perhaps... I am not sure EXACTLY what is being checked for a region match, if it is just the radio image, it will probably work. If it is checking something in the EFS partition, you might be out of luck.
Either way, if I was going to be playing with this, I would be unlocked and have a backup of the EFS partition just in case. Your chances of bricking are low, but better safe than sorry.

Moto G has a EFS partition ? @lost101 there a risk of bricking the device by flashing a modem from another phone with similar specs ? Like a XT1043 modem on a XT1550 (both dual sim)

lexer98 said:
Moto G has a EFS partition ? @lost101 there a risk of bricking the device by flashing a modem from another phone with similar specs ? Like a XT1043 modem on a XT1550 (both dual sim)
Click to expand...
Click to collapse
There should be no risk flashing Modems from different Osprey models.
No Motorola devices have an EFS partition. It would really be worth starting a thread on the subject of Backing up Osprey's IMEI - as there may be partition differences unique to the handset. With the Original Moto G, key partitions appear to be:
/dev/block/platform/msm_sdcc.1/by-name/hob
/dev/block/platform/msm_sdcc.1/by-name/dhob
/dev/block/platform/msm_sdcc.1/by-name/fsc​
Related post: http://forum.xda-developers.com/showpost.php?p=63894196&postcount=311

Hi - I signed up just so I could join this thread. I have the same problem: I have an xt1541 (UK) and live in an xt1542 area (Argentina). I went through dozens, if not hundreds, of posts before making any changes to my G3. As I already have a working LTE Samsung (it really does run like the wind!) I decided to play around with my G3, as I'd rather brick it than have a partially working phone.
Briefly, absolutely nothing I have tried so far has enabled the bands I need. But on the brighter side of things, I have flashed so many images (just about all of them, excluding the Zoom versions), combinations of images (Latam system with UK radio and fsg, the reverse of that, 2GB models on my 1GB phone and on and on), tried dozens QPST and QXDM values etc etc and *nothing* has bricked it. The key is to always make sure that you have access to TWRP and a backup.
I'm not encouraging anybody to go ahead and be reckless but, so far, I've been crazy reckless and I've always eventually wound up with a working phone. These days I've given up for a while, as I'm bored of toying with the phone. I am, however, convinced that the real solution is buried somewhere in the phone's built-in system, as I've run out of ideas when it comes to flashing images. And, let's be honest, though I've learnt a few things, I'm just a noob following instructions Right now I'm using UK NON-HLOS.bin and fsg.mbn, the rest of the image I flashed is Canadian retail which, for some reason, seems to work best in my phone (?) By using the method I describe below, I managed to get a consistent 2G connection (and, let's face it, LTE is incredible, it's frustrating not to have it on such a nice phone, but it's not something I absolutely need - I ditched the LTE Samsung I was using in favour of the G3).
Some random stuff:
CM 12.1 worked great but the phone's radio needed to be in working order before flashing.
It's my understanding that the values that need to be changed in QXDM's NV browser is not limited to 01877, but also include 00946, 02954, 0041 and 06828.
http://forum.xda-developers.com/showpost.php?p=56577252&postcount=455
2G radio can be improved dramatically using QPST's Service Programming application (after doing this, I decided to use the G3 as my main phone because it got my puny EDGE connection to work consistently): connect phone as described above, run QPST config and Service Programming, in the "UMTS System" tab select "read from phone", then tick all the 2Preferred Band" options, write to phone, reboot. Which reminds me of:
Go through the trouble of rebooting every time you tinker with your phone.
Ok, I'll try to keep an eye on this thread. Feel free to ask me about any changes I made to my phone. I hope I didn't break any forum rules.
Hope this kelps

No luck i flashed a xt1043 modem on my XT1550 using this commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
The device just boot up fine but i have the same problem when i modify the bands in NV-MANAGER .... the radio just turn on and off continuously.
I have 3G signal but is a bit poor in some areas because the XT1550 only has the 850mhz band ....
Well I can't complain so much about it. I get the device for half of the price xD

Perhaps using the term EFI partition was a misnomer, my point was to backup the IMEI number and special data before delving too deep into messing with radios, although per the previous poster it probably doesn't matter.
Sent from my MotoG3 using Tapatalk

To flash Radio Firmware, the following commands are required:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​

lost101 said:
To flash Radio Firmware, the following commands are required:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
Click to expand...
Click to collapse
Oh i forgot the FSG .... well i typed all of them and the device seems to works fine, i have a new code on the 1877 line ...
but how i know what band is using the phone ? In 4636 there isn't any information about that .... maybe QSPT ?

lexer98 said:
Oh i forgot the FSG .... well i typed all of them and the device seems to works fine, i have a new code on the 1877 line ...
but how i know what band is using the phone ? In 4636 there isn't any information about that .... maybe QSPT ?
Click to expand...
Click to collapse
Check this thread for original Moto G: http://forum.xda-developers.com/moto-g/general/unlock-hspa-bands-moto-g-1700mhz-xt1032-t2878441
Included screen-shots display bands supported info via mzTool.

I was wrong with the new code in the 1877 line ... still the same and the radio goes crazy when i do a change on that parameter .
But i just found something curious when i flash the XT1043 Modem restores the original 1877 code from the XT1550 ! .... Maybe is the same modem for all devices ?

Lexer, did you change all the values properly? (01877, 00946, 02954, 0041 and 06828) You need to "read from phone". Then write "0" in each one, "read from phone" again to make sure the 0s stuck. Reboot the phone, then read the values again, then enter the values you want.
I'm not sure QXDM even works with the G3. I think the bands are programmed into the phone's memory or -even worse- into the chipset.

speedy197 said:
Lexer, did you change all the values properly? (01877, 00946, 02954, 0041 and 06828) You need to "read from phone". Then write "0" in each one, "read from phone" again to make sure the 0s stuck. Reboot the phone, then read the values again, then enter the values you want.
I'm not sure QXDM even works with the G3. I think the bands are programmed into the phone's memory or -even worse- into the chipset.
Click to expand...
Click to collapse
I have a XT1550 dual sim Moto G3. What I want is to flash the stock rom of XT1540. I already tried flashing it,the mobile boots fine. The only issue is there is no RIL. Then I tried by flashing the XT1540 stock + radio of XT1550(NON-HLOS & fsg).
Same result-no RIL.
So,is there anyway that the QPST method will work?

theincognito said:
I have a XT1550 dual sim Moto G3. What I want is to flash the stock rom of XT1540. I already tried flashing it,the mobile boots fine. The only issue is there is no RIL. Then I tried by flashing the XT1540 stock + radio of XT1550(NON-HLOS & fsg).
Same result-no RIL.
So,is there anyway that the QPST method will work?
Click to expand...
Click to collapse
Try flashing XT1043 stock rom, that device has the same specs of the XT1550 ... so probably will work

[UNBRICK][STOCK] LG K7 K330 & MS330 Stock ROM MetroPCS & T-Mobile + IMGS & AS330

[UNBRICK][STOCK] LG K7 K330 & MS330 Stock ROM MetroPCS & T-Mobile + IMGS & AS330
*******thread is dated, i do not own the device any more*********
If anyone has firmware for any other model please PM to me.
USERS ARE IN NEED OF LG K7 AS330 KDZ If you have this model or know of KDZ file PLEASE PM me.
I have obtained the stock boot and recovery imgs for the AS330 from user maxmotos!
I have obtained the KDZ for the Walmart Family Mobile version of the K7 from user theseeker2654!
I have obtained an unofficial version of the AS330 firmware from lechicuong creation credit goes to tungkick!
Downloads and guide below.
*I AM NOT RESPONSIBLE FOR ANY LOSS OR GAIN AS A RESULT OF THIS GUIDE*
This method may cause FAILURE or HARDBRICK (as always with flashing firmware) Use at own risk.
LG Has made it harder for us to download KDZ's from their website. So now we have to glitch it out for KDZ to download.
TO INITIATE DOWNLOAD OF MIRRORED KDZ DO THIS
Click link. Refresh the page. Then your download should start after that.
If that does not work try pasting the link into this website.
Then rename the file to *.KDZ.
Or if you have Linux, you can copy the link and run wget command to download.
Download drivers & tools HERE
LG UP MIRROR
DRIVER MIRROR
Please DO NOT flash a KDZ that is not meant for your model. It may lead to a hardbrick. It may flash fine but will be irreversible.
Download KDZs here (Each file can be downloaded individually, don't click the top button that says download, it downloads ALL the KDZs in that folder. It's 23 GBs! Please try not to kill my servers by downloading unnecessary files!)
Mirrors for KDZs
T-Mobile MIRRORS
K33010h KDZ MIRROR
K33010h KDZ MIRROR 2
K33010i KDZ MIRROR
K33010j KDZ MIRROR
K33010j KDZ MIRROR 2
K33010k KDZ MIRROR
LGUP_K330.msi MIRROR
MetroPCS MIRRORS
MS33010g KDZ MIRROR
MS33010g KDZ MIRROR 2
MS33010h KDZ MIRROR
MS33010i KDZ MIRROR
LGUP_MS330.msi MIRROR
Walmart Family Mobile MIRRORS
K33011e MIRROR
K33011e MIRROR 2
Pretty Sure it uses the LGUP_K330.msi
K332 (India) MIRRRORS
K33210e KDZ MIRROR
AS330 MIRRORS
AS33010c (ROOTED+VIETNAMESE_LANUAGE_PACK) UNOFFICIAL TOT MIRROR
Extracted KDZ bins. Fastboot flashable imgs.
*Due to lack of storage space, I have chosen to compress older firmware versions in a 7z file. Please download 7-Zip to extract.*
HERE - MIRROR HERE
Please Post Results On Poll Above.
Unbrick with fastboot at bottom of page.
Unbrick Using KDZ
Install LG UP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install LG Drivers
Install LGUP_K330.msi or LGUP_MS330.msi (Depending on your model.)
Plug in phone and reboot into download mode (Hold volume up while powered off then plug in usb while holding)
Open LGUP
Select UPGRADE
Use 3 dots to find KDZ
Click START
Post results on poll above.
Unbrick using LG Bridge (Mac & Windows)
(If there is no KDZ available for your model or LG UP failed, try this)
(Official way to unbrick. If it fails, blame LG)
Download LG Bridge from here.
Install LG Bridge
Open LG Bridge
Connect device to computer and let LG Bridge install drivers
Go to the Software update tab
Click "Update error recovery" on bottom right
LG Bridge will download and flash the KDZ for you.
Unbrick with fastboot
This is for people that have no LAF partition (No download mode)
*You must have Bootloader Unlocked.*
If you did not enable OEM unlocking in your phone's settings prior to the phone getting bricked, you may not be able to recovery with this method.
If you don't have download mode enter fastboot by trying to enter download mode.(Hold volume up while powered off then plug in usb while holding)
Download LAF.BIN MIRROR file for your model.
Download ADB & Fastboot as zip
Unzip ADB & Fastboot and enter the folder.
Hold Shift and Right click in folder.
Open Command Windows here
Move LAF.BIN to that folder
If you have not unlocked your bootloader do this. (Will wipe phone)
Code:
fastboot oem unlock
Next, enter this command
Code:
fastboot flash laf laf.bin
Reboot into download mode and follow guide above
Or continue by flashing system, recovery, and kernel
Code:
fastboot flash boot boot.bin
fastboot flash recovery recovery.bin
fastboot flash system system.img
This method may cause FAILURE or HARDBRICK (as always with flashing firmware) Use at own risk.

Billybobjoe13245 said:
As of August 2nd 2016, T-Mobile has pushed an OTA of version K33010h. If anyone has firmware for any other model please PM to me. This is all official LG Firmware.
Downloads and guides below.
*I AM NOT RESPONSIBLE FOR ANY LOSS OR GAIN AS A RESULT OF THIS GUIDE*
Prerequisites
LG Driver
LG UP
All downloads can be found HERE
T-Mobile MIRROR
KDZ MIRROR
MetroPCS MIRROR
KDZ MIRROR
Steps
Install LG UP
Install LG Drivers
Install LGUP_K330.msi or LGUP_MS330.msi
Plug in phone and reboot into download mode (Hold volume up while powered off then plug in usb while holding)
Open LGUP
Select UPGRADE
Use 3 dots to find KDZ
Click START
This method is untested and may cause failure or hardbrick (as always with flashing firmware) use at own risk.
Click to expand...
Click to collapse
anyway you can post a TWRP flash-able zip for the new t mobile update? i dont want to risk LGUP using tmobile firmware on a metro phone. thanks for the downloads by the way, most of the soft-bricks needed this to get there stuff working.

jaykoerner said:
anyway you can post a TWRP flash-able zip for the new t mobile update? i dont want to risk LGUP using tmobile firmware on a metro phone. thanks for the downloads by the way, most of the soft-bricks needed this to get there stuff working.
Click to expand...
Click to collapse
I have both MetroPcs and t mobile. If you want you can try using LG Bridge to update the phone, basically does same thing but it's more user friendly and it always downloads right package. But to recover from brick I think LG UP only way to it.

Billybobjoe13245 said:
I have both MetroPcs and t mobile. If you want you can try using LG Bridge to update the phone, basically does same thing but it's more user friendly and it always downloads right package. But to recover from brick I think LG UP only way to it.
Click to expand...
Click to collapse
i wanted to give the t mobile firmware a shot and i don't think it would work though any official tools, 1) i haven't got the update that t mobile has as far as i can tell(is it just a security patch? or a os update?) 2) i'm really hoping the flash will let me bypass the metro hotspot check, right now i can only use pdanet+ works great but i want proper hotspot past my 8GB. it's up to you i'm just asking if i can be posted, any help is good help dont want to ask for to much.

jaykoerner said:
i wanted to give the t mobile firmware a shot and i don't think it would work though any official tools, 1) i haven't got the update that t mobile has as far as i can tell(is it just a security patch? or a os update?) 2) i'm really hoping the flash will make the bypass the metro check, right now i can only use pdanet+ work great but i want proper hotspot past my 8GB. it's up to you i'm just asking if i can be posted, any help is good help dont want to ask for to much.
Click to expand...
Click to collapse
That does not seem safe at all. That sounds like you could brick your phone. You should never try firmwares for different models. If you want upgrade use correct model. MetroPcs is k7ms330.

Billybobjoe13245 said:
That does not seem safe at all. That sounds like you could brick your phone. You should never try firmwares for different models. If you want upgrade use correct model. MetroPcs is k7ms330.
Click to expand...
Click to collapse
yeah i know thats why i wanted to use twrp, i already have the version with the button combo and as long as i dont flash the recovery i wont have a issue with restoring, hardware wise they are the same and i've done the same with galaxy s3's and 4's between [email protected] and T-mobile also done this with some LG optimus F(and some number 90?) between boost and sprint so i know it's possible and as long as recovery is accessible it should be alright

jaykoerner said:
yeah i know thats why i wanted to use twrp, i already have the version with the button combo and as long as i dont flash the recovery i wont have a issue with restoring, hardware wise they are the same and i've done the same with galaxy s3's and 4's between [email protected] and T-mobile also done this with some LG optimus F(and some number 90?) between boost and sprint so i know it's possible and as long as recovery is accessible it should be alright
Click to expand...
Click to collapse
Do you want boot and system? I can only give you a rooted and with xposed. I have twrp backups and that's it. I don't think there's a way to flash stock with twrp.

Billybobjoe13245 said:
Do you want boot and system? I can only give you a rooted and with xposed. I have twrp backups and that's it. I don't think there's a way to flash stock with twrp.
Click to expand...
Click to collapse
yeah thats all i wanted, is one clean? if not i don't want to inconvenience you and i dont think either of us want to share files with google info on it.

jaykoerner said:
yeah thats all i wanted, is one clean? if not i don't want to inconvenience you and i dont think either of us want to share files with google info on it.
Click to expand...
Click to collapse
Yeah it would be really hard to get system image from kdz.

Billybobjoe13245 said:
Yeah it would be really hard to get system image from kdz.
Click to expand...
Click to collapse
yeah i know that's why i was asking if you had one you had backed up before you logged into google, on another note no one else has posted "stock" recovery flashable zips and it would be helpful for people that dont have backups and have become soft bricked without having to re-root flash TWRP and unlock the bootloader.

you're a lifesaver man! Just had a new update had me stuck on bootloop.

Billybobjoe13245 said:
I have both MetroPcs and t mobile. If you want you can try using LG Bridge to update the phone, basically does same thing but it's more user friendly and it always downloads right package. But to recover from brick I think LG UP only way to it.
Click to expand...
Click to collapse
i have the k7 AS330 unlocked version but the LG Bridge doesnt want to update it. it keep saying no internet connection. is it that i dont have internet connection on the phone or it is referring to the lg bridge software because my AS330 got messed up and WiFi and data connection doesnt work anymore

realstinger_oxs said:
i have the k7 AS330 unlocked version but the LG Bridge doesnt want to update it. it keep saying no internet connection. is it that i dont have internet connection on the phone or it is referring to the lg bridge software because my AS330 got messed up and WiFi and data connection doesnt work anymore
Click to expand...
Click to collapse
I think it's on the PC. Why would it need internet on the phone? If you can get the download link from the log, that would be great. I still need for that model. I'll search for it.

d_jones456 said:
you're a lifesaver man! Just had a new update had me stuck on bootloop.
Click to expand...
Click to collapse
what did you use to update, i have the AS330

Billybobjoe13245 said:
As of July 30th, T-Mobile and MetroPCS has released KDZ updates for the LG K7 . If anyone has firmware for any other model please PM to me. This is all official LG Firmware
Click to expand...
Click to collapse
DUDE!!! thank you so much, a friend gave me the metro version and said it was trash to throw it away... guess we got the last laugh this time ha ha. thanks man for the post... i would have never known, just last month i was killing my self trying to get this thing unbricked... not sure where they messed up but it was saying Bootloader:Unlock! then hanging up at the metro logo... and nothing else worked.... until now. <3 :good::highfive:
and yes i made an account for the forums JUST to post this... so i guess im officially one of yous guys now.

DjFluxus said:
DUDE!!! thank you so much, a friend gave me the metro version and said it was trash to throw it away... guess we got the last laugh this time ha ha. thanks man for the post... i would have never known, just last month i was killing my self trying to get this thing unbricked... not sure where they messed up but it was saying Bootloader:Unlock! then hanging up at the metro logo... and nothing else worked.... until now. <3 :good::highfive:
and yes i made an account for the forums JUST to post this... so i guess im officially one of yous guys now.
Click to expand...
Click to collapse
Glad I could help you! :highfive:

I hope its not just my phone but...
I have the MS330 (Metro) and i followed the steps. Worked just fine. But im having issues with the phone. Actually its just one MAJOR issue. SEVERE battery drain and, may be bad to say it this way, but i hope someone else is having a problem too. I really hope this is a Metro KDZ problem and not my phone going bad. I know its not the battery itself because i have used 3 different batteries, one being brand new. And this is my only phone. I need to figure out how to fix the problem. I think its ***10g update LG supplied. And i need to find a way to go back to the original stock system before this. I think it was ***10e. Does anyone have a TWRP backup? I cant take this battery drain. Please say something if you had battery drain also.

bwinbig_87 said:
I have the MS330 (Metro) and i followed the steps. Worked just fine. But im having issues with the phone. Actually its just one MAJOR issue. SEVERE battery drain and, may be bad to say it this way, but i hope someone else is having a problem too. I really hope this is a Metro KDZ problem and not my phone going bad. I know its not the battery itself because i have used 3 different batteries, one being brand new. And this is my only phone. I need to figure out how to fix the problem. I think its ***10g update LG supplied. And i need to find a way to go back to the original stock system before this. I think it was ***10e. Does anyone have a TWRP backup? I cant take this battery drain. Please say something if you had battery drain also.
Click to expand...
Click to collapse
I've heard having KingRoot instead of SuperSU kills battery. But I'm not sure. Pm @goitalone I think he knows of unofficial kdz with the old version. If he does, please send it to me so I can post it here.

I always replace kingroot with supersu. It always replaces and fully removes kingroot. I flashed twrp beta 1 and it works just fine. I use adb to restart to recovery and do what needs done. And i have busybox installed and i use xtreme booster. Thank you for that info though. I have seen the battery drain with kingroot. I will pm him and see what can be done thank you.

bwinbig_87 said:
I always replace kingroot with supersu. It always replaces and fully removes kingroot. I flashed twrp beta 1 and it works just fine. I use adb to restart to recovery and do what needs done. And i have busybox installed and i use xtreme booster. Thank you for that info though. I have seen the battery drain with kingroot. I will pm him and see what can be done thank you.
Click to expand...
Click to collapse
You could reflash KDZ and use this method to root, IDK if it will help http://forum.xda-developers.com/android/development/root-lg-k7-install-supersu-kingroot-t3413941 Make sure you boot into recovery instead of flashing. Root it then you can flash.