Related
Disclaimer​
Code:
Neither Me Nor XDA Are Responsible If You Lose Your Job/Break Your Device.
Your Warranty Is Now Void
Downloads :
WIP
Instructions :
Extract The .rar
Open The Setup File And Install LG Flashtool
Right Click On The Shortcut Created On Your Desktop And Open File Location.
Copy The .dll Files From The DLL Folder To The Previously Opened Location And Replace The .dll In Flash Tool Folder If Any.
Open The Flashtool,Select The .dll Then The .tot/.bin File And You Are Ready To Flash The Firmware,Connect The Phone In Download Mode When Asked.
Note :
I Don't Know Whether It Works For N4 Converted Devices.I Had Successfully Flashed Stock .20 .bin File With It.But I Suggest To Use This Only When LGNPST Does Not Work/Fails To Flash The FW As For Me.Please Don't Perform Unwanted Experiments With Your Device Or It Will Result In A Hard Brick.
This Guide Was Originally Created By madmack @ Optimus G Pro Section So Thanks To Him.
I was Searching For The .dll File For Our Device And Found It So Decided To Create A Thread.And Those Who Are Thinking That The Required .dll Is The Same That We Use For LGNPST,NO,This Is A Different .dll
It Did Not Ask For Unlock Code When I Flashed The Stock JB FW.But As Posted By madmack there is A Possibility That It Can Ask For Your Unlock Code.So Proceed With Caution.
Again This Is A Alternate To LGNPST And Only I Have Successfully Flashed The Stock FW.It Is Recommended That Unless It Is Tested By 4-5 Experienced Users,Its A No Go For Noobs/New Users.
And Be Advised That This Process Will Wipe Your Internal Storage.
Enjoy!
Regards,
acervenky,
XPT
reserved
Thanks for sharing.
Edit: There are many more things to do in his (madmack) thread... Did u follow them all? Or for us we do not need all those steps? Let us know before someone bricks.. I use LGNPST but if anyone tries this.. at least they have a better understanding. thanks again for sharing.
just a heads up.. TeenyBin does not work in LG Flash. There are extra CRC checks which I haven't been able to bypass yet. This may change in the future.
also, not sure if this version of LG Flash is same as the newer one I use but I have to set the COM port to 40+ for LG flash to see my device.. altho maybe I'm missing something. I have to go into windows device manager and manually change the COM port used for the phone ( its in properties ).
LG Flash is no better or worse than LGNPST in my opinion. On the plus side.. there's no dll to register... and options are good
Googler_1976 said:
Thanks for sharing.
Edit: There are many more things to do in his (madmack) thread... Did u follow them all? Or for us we do not need all those steps? Let us know before someone bricks.. I use LGNPST but if anyone tries this.. at least they have a better understanding. thanks again for sharing.
Click to expand...
Click to collapse
Changed The Status To WIP.
Will Search For The Info And Update The Thread Soon
Regards,
acervenky,
XPT
autoprime said:
just a heads up.. TeenyBin does not work in LG Flash. There are extra CRC checks which I haven't been able to bypass yet. This may change in the future.
also, not sure if this version of LG Flash is same as the newer one I use but I have to set the COM port to 40+ for LG flash to see my device.. altho maybe I'm missing something. I have to go into windows device manager and manually change the COM port used for the phone ( its in properties ).
LG Flash is no better or worse than LGNPST in my opinion. On the plus side.. there's no dll to register... and options are good
Click to expand...
Click to collapse
Yup.
Regards,
acervenky,
XPT
Download link is missing.
I've try to found the download link for the Lg Flash tool on this page, but i haven't. Can you fix it or explain? Thanks anyway.
Which .TOT and .DLL files will you be providing? I need the .DLL and .TOT file for, of course, the AT&T Optimus G E-970 US version! I flashed my wifes phone cause it boot looped and the .TOT used was SUPPOSED to be this file but it is the Korean FW. Now my wifes phone will not update via OTA because it changed her IMEI number. I need to get her phone back to stock 4.1.2 US VERSION!
cougar214 said:
Which .TOT and .DLL files will you be providing? I need the .DLL and .TOT file for, of course, the AT&T Optimus G E-970 US version! I flashed my wifes phone cause it boot looped and the .TOT used was SUPPOSED to be this file but it is the Korean FW. Now my wifes phone will not update via OTA because it changed her IMEI number. I need to get her phone back to stock 4.1.2 US VERSION!
Click to expand...
Click to collapse
Here is the file you need to get her phone back to STOCK U.S: http://downloads.codefi.re/g33k3r/LGE970AT-01-V20j-310-410-MAR-08-2013.zip I'm not sure on the DLL file, I use LGNPST so not sure if they are the same but attached it also just incase you can use it.. stock firmware file above is a .tot file so if you need to you can just change it to .bin if you need to.
Thank you blake but no. That is the fw file that turned her phone Korean. So may people are under the impression this is the stock US fw but it isn't. I even had another person here check their phone and his too in fact says "Lg Electronics Korea".
cougar214 said:
Thank you blake but no. That is the fw file that turned her phone Korean. So may people are under the impression this is the stock US fw but it isn't. I even had another person here check their phone and his too in fact says "Lg Electronics Korea".
Click to expand...
Click to collapse
Where do you go check to see if its U.S or Korean?
All settings--> about phone -->phone Identity.
It's under settings-->about phone-->phone identity.
I had another person tell me that's normal because it's only the "manufacturer" info. Which im told this phone is manufactured in Korea. I don't know. All I do know is everyone is saying this is the stock fw for this phone but my wifes phone has changed. The start up screen is different and so is the shut down screen. Example, when her phone would shut down, she would get the AT&T logo and sound. After flashing this file she gets the blue circle and no sound. I do know that 4.1.2 is different depending on the region the phone is in. I don't know anything else that would explain this. Maybe this FW file WAS a different region but it was stripped out and converted somehow?
cougar214 said:
It's under settings-->about phone-->phone identity.
I had another person tell me that's normal because it's only the "manufacturer" info. Which im told this phone is manufactured in Korea. I don't know. All I do know is everyone is saying this is the stock fw for this phone but my wifes phone has changed. The start up screen is different and so is the shut down screen. Example, when her phone would shut down, she would get the AT&T logo and sound. After flashing this file she gets the blue circle and no sound. I do know that 4.1.2 is different depending on the region the phone is in. I don't know anything else that would explain this. Maybe this FW file WAS a different region but it was stripped out and converted somehow?
Click to expand...
Click to collapse
After a little checking I found out the same thing, It was normal as it was the place of manufacturer. I'm not sure what the problem might be but as far as I know that's the stock firmware for the phone.. You might try this one out http://www.androidfilehost.com/?fid=22901594685177912 you just boot into recovery do the normal wipes and flash through recovery, its supposed to be stock except for being rooted and as far as I know those are the only two stock files floating around for the phone...
Thanks Blake. Can you confirm for me that this phone will NOT get OTA updates if it's changed in any way, including rooting? It's what I was told by someone else. If that's the case then I guess there really is nothing wrong with the phone except those weird unexplained small changes.
I've got all the correct files download and I made it so far as to try to actually flash the phone, but it fails and gives me a wrong model number message because it's detecting my phone as a E960 (it's an E970). Any ideas? I had installed the latest CM11 ROM over some encrypted data and now I'm locked out (old encryption PIN doesn't work) and I can't restore it to stock.
can someone help me with a .tot or .bin stock for lg l70 d320n? cuz i"ve looked for it everywhere but couldn"t find anything
need help bad.
i got this phone from a friend and it originally had cm11 on it. the phone in question is the lg e970. i wanted to get back to stock. so i downloaded the correct firmware and added it to my external sd card. using twrp before i proceeded to wipe the phone via twrp. when it was finished i restarted the phone into twrp and went to install the stock firmware and i could not find my exsd card. twrp does not recognize it at all. so now im stuck with a phone with no os on it. i can ge into twrp and download mode, and when i just boot the phone it goes to lg logo and stays there. i need help in trying to figure out how to get stock firmware back on phone. i am used to samsung phones and odin. so im a noob when it comes to lg. i am very tech savy when it comes to computers. plzzzzzz any help would be great!!!!!!!! and appreciated
I can not add .tot file in LG flash tool
I have unrooted my lg g3 before on another computer. But i can't add the .tot file with my new computer. I am doing everything the same.
Does anyone have any ideas?
Hello, please help me.
I rooted my phone few months back and it was working fine.
I had the brilliant idea of trying to back everything up so i can install the stock rom to get the new 4.1.2 update on my note 2 from verizon.
I downloaded this recommended back up app that only works on rooted phones.
After i downloaded and installed, it went blank and it said i had an invalid system something and i needed to take to the verizon store.
I did that, they told me they cant help obviously because its a rooted phone
i tried following steps in installing the stock rom such as:
Getting odin:
Installing the driver:
But when i download the file from various sources and extract, it does not become a valid file name to load into odin.
I tried many roms and none of them work.
I tried extracting with 7zip win zip winrar, and nothing works.
I keep getting the file .xz
someone please help me get my phone back to work.
I cant do anything...now i get a new message saying the firware is invalid or something.
Im so desperate im not sure what else to do.
Thank you for reading this.
the .xz is fine. click on pda, then click on file extension and types, select all, the file should show up. select it, hit start and odin will verify the md5.
I was not able to find the game NFS Most wanted in the play store.
So I edited the prop file changing the LG G3 to HTC M8 model.
Restarted the phone and now it looped in the verizon logo.
So i downloaded all the right files to restore to stock.
But the LG FLASH TOOL gives me an error saying wrong phone model.
Is there any way to edit the prop file while the phone is in its condition or am I toast?
If yes can you please walk me through it?
TIA!!
Are you hooking the phone up in Download mode? I can't believe a borked build prop edit would prevent you from flashing back to stock.
Use Odin to flash it back to stock
ChinoHang said:
Use Odin to flash it back to stock
Click to expand...
Click to collapse
Odin is for Samsung devices... The LG Flash Tool he mentioned is the LG equivalent.
JasjarMan said:
I was not able to find the game NFS Most wanted in the play store.
So I edited the prop file changing the LG G3 to HTC M8 model.
Restarted the phone and now it looped in the verizon logo.
So i downloaded all the right files to restore to stock.
But the LG FLASH TOOL gives me an error saying wrong phone model.
Is there any way to edit the prop file while the phone is in its condition or am I toast?
If yes can you please walk me through it?
TIA!!
Click to expand...
Click to collapse
I believe there's a thread in the AT&T or the regular G3 forums that touches on this. I haven't had to do it yet *knock on wood* but I believe it's some way to bypass checking the model when using the flash tool. I just saw it the other day, so check the Q&A and/or General and the thread you need should be there.
Also, when editing the build.prop did you use Root Explorer? Apparently since the G3 build.prop is so massive most mobile file editors can't open the whole thing so when you try to save your changes it's saving an incomplete build.prop, which is what caused my bootloop the first night the phone came out when I was changing the DPI right after I had everything else set up... If you have another phone or device handy you can download any of the apps that it says are incompatible for the G3 and just side load them. I had to do that with my Note II and several apps.
Hello!
It seems like I am one of the few people to have a RS987 variant of the V10. I love everything about this phone, but it's killing me not having root access. I've avoided making a topic dedicated to this variant by posting in other threads and PMing people, but I've gotten nowhere.
I'm unable to unlock the bootloader like the T-Mobile variant even though I have to ability to enable "OEM Unlock" in the dev settings, and I've attempted to flash the Verizon VS990 5.1.1 KDZ to my phone in hopes I could root it after flashing it but it failed.
I'm willing to donate $40 to anybody that can provide a root method for RS987 variant of the V10.
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
SoulAce1290 said:
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
Click to expand...
Click to collapse
This just the KDZ for stock 5.1.1, which I provided
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
https://mega.nz/#!8k1UyCyC!Z2NIKvNOEkXBiElMLrXkv0RyPKhCN2q0KvlI1OH6ImY
this DZ file with
https://mega.nz/#!xgMgBIQD!VHtXeIlzpPydKRICtGfBUjXvtdN-KNtqX6U9bu3bY8Y
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Succeeded in flashing out.dz ... but
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
WillyPillow said:
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
LINK REMOVED
this DZ file with
LINK REMOVED
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Click to expand...
Click to collapse
joatamonk said:
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
Click to expand...
Click to collapse
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Pre-rooted system.img file for RS987 LG V10
WillyPillow said:
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Click to expand...
Click to collapse
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
@joatamonk
I just remembered what the problem is. I forgot a critical step in making the DZ
Unfortunately, I'm a bit busy recently, and I might not be able to fix this until next week. Sorry to keep you waiting.
joatamonk said:
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
Click to expand...
Click to collapse
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
No luck
WillyPillow said:
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
Click to expand...
Click to collapse
I thank you greatly for your efforts, however this .dz file didn't work. It got farther than the last one you had made. After flashing it with LG UP 1.14 the phone would reboot, show the android guy (the one with a spinning gear in it's belly), that screen would stay for about 5 seconds, phone would restart again, and then get stuck on the initial LG power up screen, it never played the startup sound or showed the animated LG logo.
RS987 must be a little different than the Verizon version? Perhaps it only loads signed kernels, or signed images or something?
Is this .dz file made from the pre-rooted image I had uploaded? Is there software that can be used to pack .DZ files from the .img file? So that I can try different methods of rooting system.img and flashing that to the phone?
The good news is the phone works fine after I flashed the stock RS98712a file back to the phone.
Thank you again for your efforts, they're appreciated.
Joata
Subscribed
Hello all,
In the process of rooting the phone and flashing careless i managed to flash a H901 ROM on a H960 phone. After noticing the horrible mistake i tried to get back to H960 using several methods but to no avail. Here's a list of what i tried so far, followed by what i think i can try next.
1. Tried getting back to stock using this tutorial. LGUP detects my phone as H901 and won't let me flash H960 kdz saying "KDZ file is invalid".
2. Tried using a hex editor on the KDZ file to change any H960 to H901 thinking it might trick LGUP into thinking it is flashing the correct thing. Didn't work either.
3. Tried flashing KDZ file with LG Flash Tool but it says it can't connect to server and stops.
4. Tried updating it with LG Bridge but that also failed (can't remeber the exact error message, but it wasn't anything specific, just something ambiguous about not being able and how i can try to reconnect the phone)
Now, the good parts:
- i still have access to download mode
- have TWRP installed and working
What i think would work is to get a flashable H960A .zip file so that LGUP will see it as it is. Another idea i thought about is to ask any of you who is willing to help me out with a TWRP backup from a H960 model.
If you guys have any other ideas, i'm willing to follow your instructions.
Thank you for taking the time to read about my mess.
Same problem here, really hoping to get it fixed too
Hex editing will work. Can you ss on how you edit it?
@devcon69 Sure, here: https://imgur.com/a/m5dMg are 2 examples of versions i modified in hex(from H960 to H901) all instances of H960 i found were replaced.
Hi all, i finally managed to undo the damage by editing the hex data on a different KDZ file. Either the first time i tried was on a wrong file or i did it incorrectly. The file i edited now is THIS one. I will edit the post with the modified file for H901 in case anyone else needs it.
Thank you all for the help and attention offered
EDIT: https://1drv.ms/u/s!AurbfgIx--Amk0Q7_l6fX60b0T0Y
Hi.i get Error: Error Code= 0x81300302, MD5 checksum error when i try with u hex editored file. Maybe i have to try to download u file again and try ?
Sorry my foult. Its okay now
Could you enlighten us as to the steps you took that accidentally loaded a H901 firmware onto a H960A device?
Loading H901 firmware onto other V10 devices has been suggested as a potential method for unlocking the bootloader of other devices. This seems risky, but I'd very much like to hear reports of success/failure.
Did your H960A have an unlocked bootloader prior to accidentally installing the H901 firmware?
Hi
Can u make a simple tutorial to how we can change the model in the tot file and what app u use to install the firmware?
i have H961N (Dual SIM) and need to install rooted MM but my model still not rooted, just lollipop, so need to install H960a or any other model has a rooted MM.
Thanks in advance.
What you've typed worries me. There are 3 spots in the file that you modified and changing the third could well cause oddities. I would suggest you try running the command `adb shell getprop ro.lge.factoryversion`.
What is the output of that command? If it is a string that begins "LGH960" then my concern isn't an issue. If it is a string that begins "LGH901" then you've still got a problem.
For folks who wish to get this done by computer, try the "chkdzdev" tool from my LGEtools. This is simply a tool to modify the fields mentioned and should make it possible to accomplish this task without a binary editor.