PLEASE READ EVERYTHING FOR BETTER UNDERSTANDING
Hey fellow LG Owner(s) I am writing this asking for some help. I know that majority of LG Phones use the same software and flashing tools regarding taking your phone back to stock. I currently own an LG G Flex (LS995 Sprint Variant) and I managed to soft brick my phone. I have posted this same message over at the LG G Flex Threads but so far I have gotten no one to provide me some sort of solution on how to un-brick or factory reset my phone.
The status of my phone before it got bricked was it had Root (IOROOT method), Busy-Box (by Jrummy), Build.Prop was edited to display as a Nexus 5, and boot-loader locked along with no custom recovery. If you’re wondering why my boot-loader was locked and why there wasn’t any type of custom recovery was due to the sad fact that Developers are having a hard time on cracking it.
Now to explain on how I soft bricked my phone. I was changing my font style by using a tool called ROM Toolbox (by Jrummy). I managed to change my font once and I attempted to change it a second time, since I was looking for something that displayed it wider and bolder. So as I applied install on the new font I got an automatic reboot.
The reboot consisted of the normal LG Logo display, followed by a black screen and staying as a black screen. On the upper left of my phone the notification indicator was flashing multiple colors (red, white, blue etc). This is the current state of my phone, black screen with a multicolor notification.
My attempts to fix:
- Simple reboot of the phone ((fail))
- Let the phones battery drain out then charge for a few minutes and restart ((fail))
- Managed to get into STOCK recovery and perform clean partition ((fail)
- Managed to get into STOCK recovery and apply factory reset ((fail))
- I got into some weird mode which also gave me the option to apply factory reset ((fail))
- I followed this tutorial (LG Flash Tool) on how to revert back to stock (by hyelton) ((fail))
Link to tutorial: http://forum.xda-developers.com/showthread.php?t=2644083
The tutorial by hyelton was almost successful to reverting back to stock firmware until I got to the last step (Number 6). The error that occurred by using the LG Flash Tool was when the tool attempted to flash the stock firmware it gave me a Download FAIL!! “Device Model is different“ notification (Images below). I did this tutorial at least seven times and I got no luck. Every single time that I attempted to do this I kept getting the same notification. I have now ran out if ideas on what to do.
My theory, I believe that by changing my build prop to display as a nexus 5 is the reason why I keep getting this fail notification. On the phone it-self when I put it into download mode it even displays as a Nexus 5 (Images below).
I was wondering since it’s possible to get into STOCK RECOVERY, I saw that it had an option for “ADB SIDELOAD” is it possible to push something thru ADB??? Any type of help is greatly appreciated and thanked. Please do not get upset that you see this in multiple LG threads, I am just trying to find a solution to UNBRICK this very expensive phone that I bought and I cannot afford to just use it as a paper weight. THANK YOU AND GOD BLESS
Here is a Link to all my files regarding STOCK tot,dll,lg flash tools,aboot, buildprop, lg usb drivers and adb drivers that are for my phone
Link: https://drive.google.com/folderview?id=0B1D8UNLjuTB6TWpCQ1pJME5qWk0&usp=sharing
i hope these files help anyone that are attempting to help me put my phone back to stock
Alright yall, I am almost official screwed. I purchased this phone about a month ago from Best Buy and they stated that I am out of there 15 day window so I cannot exchange or replace for the same phone. I then went to Sprint on whom I have phone insurance for and they stated that they cannot do anything and that I have to go to one of their Sprint repair stores. I went to one of the repair stores and the gentlemen that assisted me plugged my phone to his computer and immediately knew that my phone was rooted. So from there I played the dumb blonde card acting like I don’t know what he’s talking about and from there he directed me to call LG and see what they can do. So now the current status is I filed a repair request and now I am awaiting a reply from LG. Does anyone have any suggestion???
**SOLUTION** hey yall i got the solution to my problem and it was simply by downloading this universal custom .dll from
http://forum.xda-developers.com/show....php?t=2663369
and i managed to flash back to stock recovery using this guide. instead using the dll on the the guide i used the custom one.
*GUIDE BACK TO STOCK*
http://forum.xda-developers.com/show....php?t=2644083
BUMP
well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app
can you link me to where I can find the dll you are using?
XxZombiePikachu said:
can you link me to where I can find the dll you are using?
Click to expand...
Click to collapse
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/
lingarajug said:
well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
thanks for your response but unfortunately there is only one firmware for the sprint flex at the current moment.
christiam.coronado said:
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/
Click to expand...
Click to collapse
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk
XxZombiePikachu said:
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk
Click to expand...
Click to collapse
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications
christiam.coronado said:
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications
Click to expand...
Click to collapse
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know
XxZombiePikachu said:
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know
Click to expand...
Click to collapse
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.
christiam.coronado said:
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.
Click to expand...
Click to collapse
what did you add to your build prop to make it think it was a nexus 5?
XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
all that i did to the build prop was change the model to Nexus 5. luckily i have copied my original build prop to my computer. here is the ling to my google drive which i have saved my original build prop
https://drive.google.com/file/d/0B1D8UNLjuTB6UVBGZnhIaWEwNjg/edit?usp=sharing
XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
attached below is an image of what my original build prop looked like with its original model as ro.product.model = LG-LS995
the LG-LS995 was the part that i replaced with Nexus 5
Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app
harrymason37 said:
Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
how remember that my bootloader is still locked and this model does not have a custom recovery. but i am able to access the stock recovery with an option to ADB SIDELOAD. I got word from a DEV stating that:
"Factory recovery won't let you adb sideload a package without a LG verified updater script so it won't work." (by XDA justinswidebody)
but if he is incorrect i wouldn't mind attempting trial and error. what do you think???
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
ok ill try it out give me a minute
XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()
christiam.coronado said:
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()
Click to expand...
Click to collapse
what's the version of your flash tool
edit: after some reading to flash nexus tots you need lg flash tool 1.8
re-edit: I believe that the dll needs to be modified so that it accepts the device as a nexus 5 but once it's done flashing it needs to make the device and ls995 again, but for now it's 1am and I need to be up early later so I'll work on something later, also just some extra information on ther stuff: as for flashing the build prop if you can manage to make it into a flashable update.zip(which also places it in corresponding directory) which is also signed and you can sideload it should flash or just give an error, and another thing that could work with above method is flashing a corrupted kernel which will throw your phone into fastboot mode and with correct files and commands you can repartition the entire device to stock(this one is very dangerous/risky would not recommend it)
XxZombiePikachu said:
what's the version of your flash tool
Click to expand...
Click to collapse
Setup_LGFlashTool_1.6.01.0529
its on my drive should i downgrade??? https://drive.google.com/file/d/0B1D8UNLjuTB6ekthOGRVMWE3ejA/edit?usp=sharing
Related
Hi Everyone,
I rooted and used TWRP. Everything was fine, got SU installed and what not. Then I downloaded CM 10.2 Snapshot and Gapps and flashed them for the G2. I got the fastboot error. After trying to erase and replace the recovery, I found this thread http://forum.xda-developers.com/showthread.php?t=2448960
I get all the way to the last step when I use the LG flash tool and it says "Dowload FAIL!" It says Device Model is different! The LG Flash Tool shows I have a D802, but my phone is branded Verizon and I had LTE working on it earlier today...so I assume it isn't the GSM version...Anybody have any idea what to do?
I'm a new user, so I can't post external links, but here is an imgur address Ea8zgf7.jpg to a photo of the issue
Text on phone in the download screen says "VUSER S0.0 AS0.0 B82 UHS (New line) S US LG-D802 04.3.1 Hrev_10 (new line) VS98010B
Unfortunately I keep running into tons of dead links for different ways of dealing with this issue. Now I'm really concerned that I'm going to get screen burn in because I cannot shut the phone off. It either sits in the fastboot/error screen or in the download screen / firmware update screen.
I would really appreciate anyone's input. I tried to use this link http://forum.xda-developers.com/showthread.php?t=2432476 But almost all of the links are dead.
bobbyt2012 said:
Hi Everyone,
I rooted and used TWRP. Everything was fine, got SU installed and what not. Then I downloaded CM 10.2 Snapshot and Gapps and flashed them for the G2. I got the fastboot error. After trying to erase and replace the recovery, I found this thread http://forum.xda-developers.com/showthread.php?t=2448960
I get all the way to the last step when I use the LG flash tool and it says "Dowload FAIL!" It says Device Model is different! The LG Flash Tool shows I have a D802, but my phone is branded Verizon and I had LTE working on it earlier today...so I assume it isn't the GSM version...Anybody have any idea what to do?
I'm a new user, so I can't post external links, but here is an imgur address Ea8zgf7.jpg to a photo of the issue
Text on phone in the download screen says "VUSER S0.0 AS0.0 B82 UHS (New line) S US LG-D802 04.3.1 Hrev_10 (new line) VS98010B
Unfortunately I keep running into tons of dead links for different ways of dealing with this issue. Now I'm really concerned that I'm going to get screen burn in because I cannot shut the phone off. It either sits in the fastboot/error screen or in the download screen / firmware update screen.
I would really appreciate anyone's input. I tried to use this link http://forum.xda-developers.com/showthread.php?t=2432476 But almost all of the links are dead.
Click to expand...
Click to collapse
See if this will help: http://forum.xda-developers.com/show....php?t=2471370
or this: http://forum.xda-developers.com/show....php?t=2477595
rfarrah said:
See if this will help: http://forum.xda-developers.com/show....php?t=2471370
or this: http://forum.xda-developers.com/show....php?t=2477595
Click to expand...
Click to collapse
Both 404'd
Thy the link below, if anything it will bring you back to Stock.
http://forum.xda-developers.com/showthread.php?t=2471370
bobbyt2012 said:
Both 404'd
Click to expand...
Click to collapse
Let's try that again. I don't know why it copied like that. Anyway:
http://forum.xda-developers.com/showthread.php?t=2471370
and
http://forum.xda-developers.com/showthread.php?t=2477595
Was this ever solved? I have the same problem as the OP except with my ATT LG G2 D800. The lg flash tool shows my device as a D802. I have even tried downloading the D802 firmware, but got an error about the laf memory.
Like the OP I have followed other posts, but never found a solution. Please help.
I have an update: I used the procedure to do a factory reset by pressing the power and vol down until the lg logo appeared then release the power and immediately press the power button again. This prompted me to press the power button to do a factory reset. It came up with an error, but then booted into the CWM which I was using to flash CM on my device.
Hope this helps others.
Hi, I know this has been way back from 2 years ago. But is there any solution yet? Mine is ls980 and I'm having the same problem. Somehow trying ti factory reset does not work as after I released the power and volume down button the screen goes dark immediately and if I press it too long it just turns off.
Flash a different ROM
Ok, I hope this will help others:
I have an LG-H500F from Telcel Mexico, it got the security error bull after rooting and uninstalling bloatware, I could not find the original ROM anywhere but I found one for LG-H502F which is basically the same phone but for two sims and tv tunner.
Anyway, trying to flash the 502F Rom to the 500F kept giving me a download error complaining about not being the same model so what I did was, opened the dll file in an hex editor and found the model part H502F so I changed to H500F and saved it, also I changed the name of the tot file to H500F and Boom! It flashed it and revived my bricked little toy!!!
Hope this helps...
supermauro said:
Ok, I hope this will help others:
I have an LG-H500F from Telcel Mexico, it got the security error bull after rooting and uninstalling bloatware, I could not find the original ROM anywhere but I found one for LG-H502F which is basically the same phone but for two sims and tv tunner.
Anyway, trying to flash the 502F Rom to the 500F kept giving me a download error complaining about not being the same model so what I did was, opened the dll file in an hex editor and found the model part H502F so I changed to H500F and saved it, also I changed the name of the tot file to H500F and Boom! It flashed it and revived my bricked little toy!!!
Hope this helps...
Click to expand...
Click to collapse
Hello, friend. Did you actually root your device? And if so, how did you made it? Please, I've looked everywhere and found nothing. Would like to read you. Thanks in advance and greetings from Mexico too.
Root H500F
Jhakob said:
Hello, friend. Did you actually root your device? And if so, how did you made it? Please, I've looked everywhere and found nothing. Would like to read you. Thanks in advance and greetings from Mexico too.
Click to expand...
Click to collapse
Yes, I did root the device, here is how I did it:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Cheers
guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.
I hope you have a custom ROM or the ROM you have already flashed. Just make a flashable zip with the build.prop placed in /system/ .
flash it through recovery and you are back again..
Or just flash your Rom again. Should fix the issue
Sent from my VS980 4G using XDA Premium 4 mobile app
Guys I am a complete newbie. Can you please explain it more to me.
I am currently downloading the .kdz file via this software
http://forum.xda-developers.com/showthread.php?t=1073827
also i did found this http://forums.whirlpool.net.au/forum-replies.cfm?t=2186883&p=6&#r106
so i am pretty sure I am downloading the right rom right now because the software pickup the same name.
So am I right about flashing my phone by following the steps on the topic I mentioned in my first post?
Is this what you mean by flashing trought recovery because that dude says download mode.
BTW I cant flash trought lg's utility I dont know if its related or not but windows cant install CDC driver.
Also when I flash the rom am I going to lose my data.
Thanks for your answers guys really appericate it.
Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.
Steamer86 said:
Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.
Click to expand...
Click to collapse
How can I adb the build.prop ?
I can only go into LG G2 Stock recovery mode and download mode. There is no custom recovery installed so I cant open debugging and adb doesnt recognize the device.
Am i doing something wrong? and believe me I have been reading for hours
I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.
Steamer86 said:
I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.
Click to expand...
Click to collapse
but even that needs custom recovery I dont have custom recovery unfortunately ((
It does not...
capuagenclik said:
guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.
Click to expand...
Click to collapse
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.
Howie Dub said:
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.
Click to expand...
Click to collapse
Ahh mate it would probably helped because my support tool couldnt recognize my device as d802 but instead l02e or l20e sth like that with united driver but I reckon those are the drivers I was looking for unfortunately I dont have the phone anymore.
I turned the phone back to the warranty today not giving any explanation to try my luck. they may just do this same procedure and just flash stock rom on the service and send it back to me or they might just say this is rooted its out of warranty either case I will let them deal with it if they say this is out of warranty I will ask them to fix it and I am willing to pay if they quote me something reasonable if they dont I will try this.
Thank you very much for your answer.
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Thank you heaps man how nice of you. I would let you guys know how it goes. Its only soft bricked so i think technical support would be able to flash the stock firmware on it but I hope they wont decide to give me hard time. If they do i am planning to play the fool
I will definitely pm you if I get it back unfixed. Thank you for the offer.
Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot
pilo99 said:
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot
Click to expand...
Click to collapse
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app
Jishnu Sur™ said:
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen
pilo99 said:
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen
Click to expand...
Click to collapse
Check PM!
Jishnu Sur™ said:
Check PM!
Click to expand...
Click to collapse
cool am online now
Guys I just wanted to give you update on the matter. Today I called the repair centre and they told me they have fixed the phone and send it back yesterday so I should be able to get it in couple of days maybe this friday or next week monday something like that. They didnt say anything about root or warranty or stuff like that. When I get the phone back what can I do prevent this from happening again? Do I need to flash a custom recovery on the phone? What is the risk of doing that? Or should I just root the phone and not mess with the system files ever again
Thanks heaps for all your inputs.
Got the phone today they changed the motherboard. I am not sure if it is a good thing or a bad thing :/ On the good side it is fixed for good on the flipside the phone has been opened now so thats not so good. I have checked the body coudlnt find too many stracthes or sth like that they did a clean job but still.
Anyway that was the last update.
my ls980 thinks it is the d800 and I can't seem to flash it back to the ls980.
I flashed a custom ROM thru twrp and I got an error. I tried restoring the backup and the system partition would not mount. after poking around for quite some time I tried restoring the phone in download mode. apparently the computer thought it was the d800 and flashed the system for that phone. when it restarted I saw the at&t boot screen and when it started up it was not working correctly.
I put it back in download mode and tried flashing the phone again. the computer was sure it was the d800. then I tried flashing manually using the DLL intended to convert this and the tot file for the ls980. I get the error saying I can't convert from the d800 to the ls980.
I then tried flashing thru adb from both windows and linux. both say they cannot find the phone regardless how I try connecting.
since I flashed the factory files the phone will not start in recovery mode I have no clue why.
so now I have a phone that:
will not flash the ls980 tot file,
will not connect to adb,
and will not boot into recovery.
now what?
-boxorandyos
<sent from my nexus4>
Dang dude. Harsh. I almost ended up in this same situation after downloading files for the wrong device and noticed literally at the last second and was able to pull the plug, literally, and save my device.
I've been looking for ways to fix it in case it happens again and I don't catch it in time, so if I find the answer I'll let you know. There has to be a way to trick the computer into thinking it's a LS980 like it's supposed to be the same way it thought the phone was a d800.
Sent from my LG-LS980 using XDA Premium 4 mobile app
I was told that there was a DLL file that could be used when flashing it to trick it into thinking it's the ls980 but all I get is an error message I forget exactly what the message says but something to the extent that I don't have the right files for the phone that I have.
-boxorandyos
<sent from my nexus4>
yo
boxorandyos said:
I was told that there was a DLL file that could be used when flashing it to trick it into thinking it's the ls980 but all I get is an error message I forget exactly what the message says but something to the extent that I don't have the right files for the phone that I have.
-boxorandyos
<sent from my nexus4>
Click to expand...
Click to collapse
yo man have you tried using LGNPST, we're in the same boat, i'm waiting for my some downloads on firmwares to try, i'm using LS980 but it thinks it's a VS980 still working on figuring out from my end. i've also heard that the LG mobile support tools can be used to restore the firmware but you gotta do some funny hot swap lol
vegito6 said:
yo man have you tried using LGNPST, we're in the same boat, i'm waiting for my some downloads on firmwares to try, i'm using LS980 but it thinks it's a VS980 still working on figuring out from my end. i've also heard that the LG mobile support tools can be used to restore the firmware but you gotta do some funny hot swap lol
Click to expand...
Click to collapse
woops im a little slow here. what is LGNPST ? I solved the issue by manually editing the build.prop file and that tells the lg mobile support tool that it is a different phone. that was a whole different complicated story of its own but it worked.
sorry I didnt see your comment until now.
def sounds like you used the wrong dll or just the stock lg dll which works with some phones, but others need their specific dll to match the tot and such to make a proper bootloader flash over i believe.
So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits
Hendrickson said:
So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits
Click to expand...
Click to collapse
Sorry but I disagree with you. I had an f400l and editing buildi prop I was abile to change firmware, reflashing it more than one time using tot and dll files
Hendrickson said:
So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits
Click to expand...
Click to collapse
I also agree with lukemo. I have reflashed my F400S at least 4 times now (and edited build.prop in 3 of em). Maybe elaborate on your description a little more. If a device is capable of connecting to a PC through USB Debugging, then pulling the build.prop and editing it for the purposes of (re)flashing should not be an issue. Also, it definitely does not hurt to keep a copy of it on hand as a spare (if push comes to shove and TOT, DLL combo is the only way to restore).
Ok maybe its not the case on the F400 now but myself and a few others ran into a big issue with this on the Korea G2 F320. Flashing one of the first roms a F320 CN V1 rom it did some build.prop edits and if you bricked it. It was a mission to get the phone back. A brick meaning boot loop and no other modes apart from download mode. KDZ did not let us flash it as it wanted that model in the edit.
It was all caused by edits to
ro.build.model
ro.build.version.incremental
ro.build.id
Might have messed with the boot.img, but i'm sure they didn't in the beginning.
Can somebody tell me what all needs to be edited in my build.prop to get it back to my original firmware, here is the summary of my case
I have F400K model, flashed VT V6 which changed my model to F400L, applied ART and it gave my android.system.com errors on boot, has do flash F400L stock TOT as F400K tot gave an error, I am now on F400L with VT V6 and want to go back to my 400K firmware.
Thanks in advance,
Bad luck since I saw this now, after I edited the build prop to make the LG G3 think it was an GTI9500 for the Samsung Gear 2 pairing, since I did it in the M8 i thought I could get away with it. Now the phone boots, LG logo comes on, then the screen goes dark fray and the notification light switches from color to color. Nothing happens, it seems as its booting but it never goes through. So I cannot TOT or similar since the phone does not boot up.
Can anyone advice? Is Odin an option? I am on D855 custom rom
Did you try flashing GTI9500 firmware? My 400k didn't take its tot as I was switched to 400k, I had to eventually flash 400l to boot it properly
Sent from my LG-F400L using Tapatalk
Diamond777 said:
Bad luck since I saw this now, after I edited the build prop to make the LG G3 think it was an GTI9500 for the Samsung Gear 2 pairing, since I did it in the M8 i thought I could get away with it. Now the phone boots, LG logo comes on, then the screen goes dark fray and the notification light switches from color to color. Nothing happens, it seems as its booting but it never goes through. So I cannot TOT or similar since the phone does not boot up.
Can anyone advice? Is Odin an option? I am on D855 custom rom
Click to expand...
Click to collapse
Edit the tot with a hex editor to match your build prob do it in lunix also make sure you have the dll that does with your phone.
D-FUSE said:
Edit the tot with a hex editor to match your build prob do it in lunix also make sure you have the dll that does with your phone.
Click to expand...
Click to collapse
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?
Diamond777 said:
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?
Click to expand...
Click to collapse
Open the tot file with a hex editor in ubuntu then do a search for your model number the 1st line will be it. Change that to what ever you changed the build.prob too then going to download mode and use flash tool like you would normally. I've done this 100 time on my g flex. It works man.
Hi
D-FUSE said:
Open the tot file with a hex editor in ubuntu then do a search for your model number the 1st line will be it. Change that to what ever you changed the build.prob too then going to download mode and use flash tool like you would normally. I've done this 100 time on my g flex. It works man.
Click to expand...
Click to collapse
I have the same problem and this HEX editor idea sounds good, I only have a PC so how to I get ubuntu?? and what hex editor would i use?
aviduser said:
I have the same problem and this HEX editor idea sounds good, I only have a PC so how to I get ubuntu?? and what hex editor would i use?
Click to expand...
Click to collapse
You're gonna have to Google ubuntu and install it along side windows and then get an hex editor in the software center
ok done that
D-FUSE said:
You're gonna have to Google ubuntu and install it along side windows and then get an hex editor in the software center
Click to expand...
Click to collapse
Have ubuntu now loaded on a usb. Can open the tot with hex editor but where do I search for my product model. When I search d800 I get a thousand results. I then click on one and I can see garbled text in the right hand display box of the hex editor.
Which hex editor do you use?is that important?
And what settings perhaps am I missing. Not used any of this before but ubuntu seems straight forward
Many thanks
Chris
Diamond777 said:
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?
Click to expand...
Click to collapse
Can u use adb? If the answer is yes i can show u how to restore build.prop...
Skin1980 said:
Can u use adb? If the answer is yes i can show u how to restore build.prop...
Click to expand...
Click to collapse
Hi, I can't do sh**!
I am stuck in bootloop, I cannot adb because it does not get detected???
This is stressful, thanks for your help
Diamond777 said:
Hi, I can't do sh**!
I am stuck in bootloop, I cannot adb because it does not get detected???
This is stressful, thanks for your help
Click to expand...
Click to collapse
What version of g3 have u got?
If someone can give me the original build.prop for your version i will make a flashable zip that u can flash in stock recovery
Skin1980 said:
What version of g3 have u got?
If someone can give me the original build.prop for your version i will make a flashable zip that u can flash in stock recovery
Click to expand...
Click to collapse
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Diamond777 said:
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
give me 1 hour...
Diamond777 said:
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
here u go... u have to:
1- go in recovery;
2- select update from adb;
3- from the pc
Code:
adb sideload restore-signed.zip
4- reboot
This will copy the original build.prop to ur device... if this not help write me pls.. we can find other way
A live cd/dvd of ubuntu or any linux distro should work too. Good hex editors to use are bless and 010.
010 runs on windows/linux/osx. You can try editing on windows, but I suggest only doing so if your pc is a good one.
And on the subject of the OP, one really shouldn't be editing the device model, build #, nor versioning of the rom.
i just received my new G2 D802 16GB,
i tried to upgrade to kitkat with this guide
(flashed Switzerland 16GB D80220F_00.kdz)
i ended up with a phone that wont boot, it got stuck it fastboot mode, i messed with fastboot until i got to the point i had download mode again, (i messed with the partitions: sb1,tz,laf...)
i tried flashing many roms (Europe Open D80210A_00,UK Open 16GB D80210B_00,Hungary OPEN 16GB KitKat D80220B)
the roms load fine, but now the touch response is unusable (touching a point is being registered in another spot altogether).
this happened with every rom i have tried.
i tried with the tot method from the same thread, i got memory Size mismatch 32G! error (i have a 16GB model),
i tried the tot again with the 32GB rom and it passed, but the problem remains (the bad touch response).
what do i need to do?
Why didn't you just use the PC program to update?
Do it
guynaa said:
i just received my new G2 D802 16GB,
i tried to upgrade to kitkat with this guide
(flashed Switzerland 16GB D80220F_00.kdz)
i ended up with a phone that wont boot, it got stuck it fastboot mode, i messed with fastboot until i got to the point i had download mode again, (i messed with the partitions: sb1,tz,laf...)
i tried flashing many roms (Europe Open D80210A_00,UK Open 16GB D80210B_00,Hungary OPEN 16GB KitKat D80220B)
the roms load fine, but now the touch response is unusable (touching a point is being registered in another spot altogether).
this happened with every rom i have tried.
i tried with the tot method from the same thread, i got memory Size mismatch 32G! error (i have a 16GB model),
i tried the tot again with the 32GB rom and it passed, but the problem remains (the bad touch response).
what do i need to do?
Click to expand...
Click to collapse
Maybe you can try that thing from update touch driver or whut from hidden menu.
I also read that some people also had this issue on kitkat but not on jellybean stock
So try some things and report back :silly:
TheHaso said:
Why didn't you just use the PC program to update?
Do it
Click to expand...
Click to collapse
i tried, but the update failed using the official lg software (i was on 4.2..2)
wulsic said:
Maybe you can try that thing from update touch driver or whut from hidden menu.
I also read that some people also had this issue on kitkat but not on jellybean stock
So try some things and report back :silly:
Click to expand...
Click to collapse
i think you meant this
i cant do it because the touch is crazy and i cant even open the dialer using current touch response...
i was able to get adb running if that helps
guynaa said:
i tried, but the update failed using the official lg software (i was on 4.2..2)
i think you meant this
i cant do it because the touch is crazy and i cant even open the dialer using current touch response...
i was able to get adb running if that helps
Click to expand...
Click to collapse
Yes I meant that Step3 from that url.
What you can do is 3 things.
Downgrade to 4.2.2 :/
Connect an Usb OTG mouse to your phone.
Try or OSP(On screen phone) works.
If these things don't work then you must try to find something else cause further then this I don't have any Idea at the moment, maybe later...
Goodluck:good:
wulsic said:
Yes I meant that Step3 from that url.
What you can do is 3 things.
Downgrade to 4.2.2 :/
Connect an Usb OTG mouse to your phone.
Try or OSP(On screen phone) works.
If these things don't work then you must try to find something else cause further then this I don't have any Idea at the moment, maybe later...
Goodluck:good:
Click to expand...
Click to collapse
thanks,those are 2 great ideas i wish i had thought about!,
i sent the phone to be serviced, i will post here the outcome if that matters.
Ahh okay, sorry for late reaction was busy with school.
If your phone gets serviced then they will also probably ship it back with 4.4.2 stock and also with normal working touch .
you can post the outcome if you want I think
Just wait for it till you get your phone back, then you will be happy again
Update your touch software from service menu and you should be okay.
Check xda for. Service menu code
Sent from my LG-D802 using xda premium
i managed to solve this.
i bought this "d802" online, the box, phone sticker and "about" all said it was a d802 (normal back panel, no "ATT" logo),
after i opened the phone i discovered the logic board is actually a d800.
i managed to change the model number in build.prop (to d800), and flash the d800 with the tot method, the phone works fine now,
if anyone have the same problem and finds this thread, contact me and i will try to help
guynaa said:
i managed to solve this.
i bought this "d802" online, the box, phone sticker and "about" all said it was a d802 (normal back panel, no "ATT" logo),
after i opened the phone i discovered the logic board is actually a d800.
i managed to change the model number in build.prop (to d800), and flash the d800 with the tot method, the phone works fine now,
if anyone have the same problem and finds this thread, contact me and i will try to help
Click to expand...
Click to collapse
I had same issue.. I had touch problem and I got it repaired and paid 4500PKR = around 45USD and it was D800 .. Why didnt I see this before (
OKay one question , If i root it and update it to Kitkat and edit build.prop to D802 , will it show D802 again ? if yes then I can do that and return it to the local shop where I bought the phone from..
-iNCEPTiON- said:
I had same issue.. I had touch problem and I got it repaired and paid 4500PKR = around 45USD and it was D800 .. Why didnt I see this before (
OKay one question , If i root it and update it to Kitkat and edit build.prop to D802 , will it show D802 again ? if yes then I can do that and return it to the local shop where I bought the phone from..
Click to expand...
Click to collapse
no, the d800 cant run firmware built for the d802,
you should flash this tot and upgrade to kitkat (if you want) using this method
guynaa said:
no, the d800 cant run firmware built for the d802,
you should flash this tot and upgrade to kitkat (if you want) using this method
Click to expand...
Click to collapse
Yes I am asking if I use tot method to update to kitkat and root it .. then edit build.prop and change to D802 , will it show D802 in About Phone?
-iNCEPTiON- said:
Yes I am asking if I use tot method to update to kitkat and root it .. then edit build.prop and change to D802 , will it show D802 in About Phone?
Click to expand...
Click to collapse
i am not sure, but i believe that the phone wont boot into android if you do that (i have the reverse case),
why would you want to do that?
guynaa said:
i am not sure, but i believe that the phone wont boot into android if you do that (i have the reverse case),
why would you want to do that?
Click to expand...
Click to collapse
Hmm i want to do that coz when i got the phone from him it showed d802 in about phone and back of the phone as well ...so i want to do that again to get it replaced as i need d802
Sent from my LG-D802 using Tapatalk