Usb brick! Lg l3 optimus e400 - Optimus L3, L5, L7 Q&A, Help & Troubleshooting

Hello guys! I need some help
I was flashing a stock firmware with kdz updater on my LG E400, following all instructions
Flashing goes through all the way and at the end i get:
Upgrade
error WParam: 100, LParam: 6
Phone boots and all but when i fix in my USB cable i don't see the icon in the status bar hence can't send files from computer or do Adb commands
I guess its USB bricked
Looked for solutions all over but they don't seem device specific and i fear bricking my phone for good
Any help is much appreciated!
Sent from my LG-E400 using xda app-developers app

have you try to do a hard reset after kdz flashing?
Code:
in off position, press n hold home + vol down + power buttons together. be sure you press that power button at the last one...
will be wipe your data, cache and internal sd partitions by doing this. if you have any important files in int-sd, then back it up first ( move it to ext-sd )
let see if it work or not.....

Cool. I'd done a factory reset and didn't fix it, let me the hard reset and see what comes out of it
Sent from my LG-E400 using xda app-developers app

Nah, factory reset doesn't do the trick. I'm stumped ..
Sent from my LG-E400 using xda app-developers app

let's hope that'd software problem. you just install any custom roms you like, and your problem should be fixed. but if it's not, then you have to send it to service center for fix that hardware....
good luck

OK. Thanks
Sent from my LG-E400 using xda app-developers app

Fixed it!
finally managed to fix it. Problem was with the firmware I was installing. I chose a firmware from another country of origin with a version that wasn't released for my phone's country. got the right kdz for my country and flashed it successfully fixing the brick.
I even managed to root it this time round! (the whole reason I flashed a different firmware in thw first place was because of failure to root)
Everything is good now. thanks to all that replied

tarnoldinho said:
finally managed to fix it. Problem was with the firmware I was installing. I chose a firmware from another country of origin with a version that wasn't released for my phone's country. got the right kdz for my country and flashed it successfully fixing the brick.
I even managed to root it this time round! (the whole reason I flashed a different firmware in thw first place was because of failure to root)
Everything is good now. thanks to all that replied
Click to expand...
Click to collapse
Can you elaborate? I am having the exact same problem.

install again the msxml before using kdz.. hope it works
★★★ [jellycast_forever] ★★★

DebanjanSahu said:
Can you elaborate? I am having the exact same problem.
Click to expand...
Click to collapse
if u did what I did and got USB brick, its from flashing the wrong kdz file. there's an app for finding the right kdz file by giving it just your serial number of the phone. it's what I used cause I wasn't sure of the right country of origin of my phone. try using that app, and flash the kdz like before. and make sure its a COMPLETE download. watch it all the way. try that

Using advice from http://forum.xda-developers.com/showpost.php?p=34700586&postcount=4 you can determine which firmware version to use based on your phone IMEI.

Related

[Q] Note 3 N900W8 soft bricked, backup not working.. can't find a compatible firmware

I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Yorgo1982 said:
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Click to expand...
Click to collapse
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Apra24 said:
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Click to expand...
Click to collapse
wait sammobile if u r with rogers bell telus fido vmc koodo, and if with other carrier contact them with ur phone model and serial num so they will upload it ..
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
Did you restore from CWM/TWRP?
Pikezer1337 said:
Did you restore from CWM/TWRP?
Click to expand...
Click to collapse
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Apra24 said:
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Click to expand...
Click to collapse
If you restored through TWRP there is a good chance that you are softbricked. There are restoring issues that mess with the system partition.
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Apra24 said:
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Click to expand...
Click to collapse
can u give the file name?
plz
Yorgo1982 said:
can u give the file name?
plz
Click to expand...
Click to collapse
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Apra24 said:
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Click to expand...
Click to collapse
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Yorgo1982 said:
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Click to expand...
Click to collapse
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I'm wondering if the official Bell/Rogers firmware will be available any time soon? Does it typically get released soon after the phone launch, or are they withholding it for some reason?
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
eklipse1 said:
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
Click to expand...
Click to collapse
I was trying the Peru one for a while, but it kept hanging up during the bootup. The message was in a foreign language, but I'm assuming it was "initializing". It would initialize for about 3 minutes then an error message would pop up saying something is not responding.
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
eklipse1 said:
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have been trying to. When I flash the firmware in odin, it reinstalls the stock recovery mod. Right after flashing firmware, it won't go into recovery mode on the first boot (first does some android robot install thing, then boots up). I attempted to install the TWRP recovery directly after the firmware, and then booting directly into recovery to factory reset, but I'm still getting a boot loop.
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Yorgo1982 said:
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Click to expand...
Click to collapse
do they know it's rooted/void? Or did you somehow not trigger the knox/warranty void switch? I may just have to do the same thing...

LG G2 boot loop after editing build.prop What to do?

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.

[Q] Soft Brick help me please!!!

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

[Q] Why I bricked my phone with LG Flash tool?

I have LG G2 D802 32GB. When I bought it, there was Android 4.4.2 KitKat installed.
Then I rooted it using ioroot25 and installed custom recovery using AutoRec.
I flashed CloudyG3 v1.2 rom by @Cloudyfa using TWRP.
It was working really good except the VOIP calls, thus I wanted to revert back to stock.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2432476
I tried to flash it using some Europe Open KDZ from this page: http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2F
The flashing started and stucked at I think 4%. I rebooted the phone and it appeared as qhsusb_dload.
I can't remember if I clicked on Normal or CFE flash. But I think it was normal.
I tried to unbrick it with this guide: http://forum.xda-developers.com/showthread.php?t=2582142
After that I got only LG logo and no recovery, no fastboot, no download mode, no qhsusb_dload mode, no nothing.
Now I got board replacement. The board have rooted Android 4.2.2 Jelly Bean installed.
As I want to have CloudyG3 installed. I tried to do that by installing custom recovery and then flashing the CloudyG3 rom and KitKat baseband. But I think I have a battery drain issue, as Cludyfa already said. I also tried with flashing the Cust and Persist partitions from the KitKat KDZ, but my battery didn't got any better.
The question is, why I bricked my phone with LG flash tool? What should I do to make sure that this won't happen again?
I made backup of entire phone nand (mmcblk0). Should I DD it if I get the bulk mode (qhsusb_dload) again?
Thank you in advance for your answers.
@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.
wulsic said:
@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.
Click to expand...
Click to collapse
When phone stucked there was also some message box on LG Flash Tool. Something like that: ?????? ??? ????????.
Sent from my LG-D802 using XDA Free mobile app
Broken usb cable or port? Problems on pc?
siggey said:
Broken usb cable or port? Problems on pc?
Click to expand...
Click to collapse
As far as I know none of that.
Sent from my LG-D802 using XDA Free mobile app
That something like ????? Was probably in some asian language which your pc couldnt read. Some pc's makes boxes from it some ?. I cant tell you what that ???? Means since they have no meaning without any real symbols from some language of asia (I dont know where the dev comes from)
If it was stuck at 4% you could ask it on the thread of the lg flashtool since the dev of it and or other users may know the problem.
mss1988 said:
What should I do to make sure that this won't happen again?
Click to expand...
Click to collapse
Read the tutorial in detail & HAVE some patience man.

[Q] Did I brick my phone?

Hello,
I have a LG G2 (D802). I was busy flashing the stock KDZ, when I got an error. The progress on my phone stopped, and nothing happened anymore. I wanted to try again, so I turned my phone off. Now, when I boot my phone, it gives the LG logo, and then nothing. When I connect it to my pc, I get a lot of format pop-ups.
I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2432476
The KDZ I used: Netherlands Open 16GB KitKat D80220D
Furthermore, also while connected to the pc, I only see a folder called "image".
Can someone help me with getting my phone back to stock? It doesn't matter if everything gets wiped, I already backed up everything.
Thanks in advance!
If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.
The Marionette said:
If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.
Click to expand...
Click to collapse
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png
MistaahD said:
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png
Click to expand...
Click to collapse
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.
The Marionette said:
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.
Click to expand...
Click to collapse
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".
MistaahD said:
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".
Click to expand...
Click to collapse
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?
The Marionette said:
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?
Click to expand...
Click to collapse
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Edit: I will try connecting it to another pc now.
MistaahD said:
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Click to expand...
Click to collapse
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.
The Marionette said:
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.
Click to expand...
Click to collapse
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?
MistaahD said:
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?
Click to expand...
Click to collapse
Download the kdz suitable for your model and flash it with LG Flash Tool.
Follow the "Back to stock" guide which you mentioned in the OP.
There will be a link to the KDZ archive for various models,and make sure that you select the kdz for the 32 GB variant if you have a 32 GB variant. Because it will be dangerous if you flash a 16gb variant kdz on a 32 gb phone.
Sent from my LG-D802 using XDA Forums Pro.
EDIT
And if the same thing happens when flashing,fix it again(if it won't access the download mode) and try to flash while using another PC.
Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!
MistaahD said:
Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!
Click to expand...
Click to collapse
So the kdz flash worked,and the stock rom boots?
Sent from my LG-D802 using XDA Forums Pro.
Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?
MistaahD said:
Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?
Click to expand...
Click to collapse
Yes,excellent job.
To root,download "Towelroot" to your phone,install it and press the "Make it rain" button,then install SuperSU,then look for "AutoRec" and make sure you get the version for your variant.
That is just halfway,I will tell you the rest tomorrow,it is 00:26 and I have to get up at 07:00. xD
Sent from my LG-D802 using XDA Forums Pro.
Haha cheers! I think I got it from there, it's just that I don't want to do it in a wrong order haha ;P
And thanks a lot, again! Get your deserved sleep, I should do that too.. Gotta go up at 06:45 hah!! I WIN! xD
Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot
The Marionette said:
Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot
Click to expand...
Click to collapse
Hey man,
I noticed that Towelroot doesn't work for LG G2 Lollipop. Any idea how to fix this?
Edit: trying it with another root.
Edit 2: rooted. Going to flash now.
Alright it works, thanks! Can you tell me why I need the bumped version? Just curious
MistaahD said:
Alright it works, thanks! Can you tell me why I need the bumped version? Just curious
Click to expand...
Click to collapse
It is complicated,just do it. XD
I was asking the same thing like you.I ignored others,rushed with roms,didnt use the BUMPED TWRP and my phone was bricked.
Basically the TWRP you get with AutoRec is just capable of flashing partitions for the bootloader,not the system partition(the rom is in the system partition).
The BUMPED TWRP has a certain type of an exploit,and lets us install those system partitions.
Shortly:You can't install roms without the BUMPED TWRP.
Sent from my LG-D802 using XDA Forums Pro.
I'm guessing my phone is refurbished?
I bought a D802 from a third-party, with:
- 32GB ROM
- 4.4.2 D80220b firmware
- 2G, 3G, 4G working
- The csmg.lgmobile.com website said that according to my IMEI, my model is the UAE 32GB D802 and gave me the D80230a firmware for manual flash via LG Flash tool.
I used the phone for a while, rooted it and used Xposed. Never got recovery so no backup(wish I'd seen the SRK tool before). Then I downloaded the firmware from the csmg.lgmobile.com website. I flashed it via the Flash tool and everything seemed fine. Then it booted:
- Touchscreen was erratic. Ghost touches, dead spots, phantom touches, whatever.
- The Baseband Version and IMEI in About Phone both say Unknown
- ROM has converted to a 16GB version
- Download mode is fine along with every other feature of the phone
After that I looked around and found a UAE D80220c firmware and flashed that. It flashed fine but all the above issues remained the same.
I browsed around extensively here and found out:
- Refurbished phones have their back cover and firmware changed to imitate D802's.
- My phone is probably some other G2 model with D802 firmware and an altered IMEI
- The actual model of my device is UNDER the motherboard. Which, apparently, I must get hold of so I can flash the appropriate stock kdz. This gets a bit too hardware-y for me.
So, basically, my phone is no more useful than a brick at the moment. Any expert help would be appreciated but here are the main questions that I'd really like answered:
A. Should I try various flashing the kdz files from different models mentioned in the link I gave up ^there until one clicks and then try to do something about the IMEI?
B. Is there any chance that my phone is beyond repair forever?
C. Should I stop messing around with my mediocre knowledge and take it to a repair shop?

Categories

Resources