Related
Hi, I've just registered in this forum, though I've been reading you guys for almost a year. I just want to say that you guys are awesome, i've learned too much about android because of you.
Introduction
Said that, I recently had a problem with my P350g, I'll try to be as clear as possible hoping you can help me out.
The problem came after i installed CM 9 [stable 8] on it, at first it worked perfectly (a very few panics or reboots but i'm used to it :laugh. The next day after taking a photograph the cellphone got stuck, it had done that several times before with some other ROMs so i didn't pay much attention to it, so i took the battery off and put it again, and when I tried to turn it on, there it was, the lg logo with the 4 softkeys blinking.
-- It doesn't enter to recovery (i had recovery installed at that time) pressing [- power send] at the same time, it just stays there with the lg logo blinking.
-- It does enter to the emergency mode (yellow background with "emergency mode" in black letters) pressing [+ - power] at the same time.
-- It does enter to the fastboot mode pressing [+ power send] at the same time.
what i've already tryed:
--- i've read the wiki about this phone and try everything there (and everything found on google which is pretty much the same)
http://forum.xda-developers.com/wiki/LG_Optimus_Me
--- i've tryed using the KDZ updater as somebody on this forum recommended:
http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/
using firmware from here:
http://lg-phone-firmware.com/index.php?id_mod=5
and from somewhere else on the internet, the problem here is, that when it comes to "restart the phone", it doesn't start, it just keeps getting stuck on the lg logo with the 4 softkeys blinking, after some time the KDZ updater shows an error: Upgrade Error WParam: 100 LParam: 6
--- i've tryed flashing the recovery from fastboot mode as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=2131247
it flashes well, everything "succeeded" but whe it comes to reboot (flashboot reboot) the cellphone says on the screen rebooting cellphone (or something like that) but it never reboots. if I take the battery off and put it on again, and then try to turn it on, the cellphone shows at the same problem, the lg logo with 4 softkeys blinking.
--- I've also tryed this tool:
http://forum.xda-developers.com/showthread.php?t=1948326
it hasn't solved my problem either.
Computers' info
I've tried this on 2 computers:
windows 7 x86
windows 8 x64
both of them have the drivers installed, I've disabled the modem on both of them, both of them have the latest android SDK tools
both computers give me the same problems, please i need your help, i'm desperate, I've been with this problem for several days and I can't solve it. I hope you can help me out
bump!
Anybody? please, i'm desperate
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
kD said:
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
Click to expand...
Click to collapse
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
I couldn't fash a rom via fastboot
IsraelMP said:
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
Click to expand...
Click to collapse
Hi everybody, i tried to flash a zip containing the rom on my p350, though i could not flash it. i used the command:
fastboot flash system rom.zip
but it says the file/rom size was smaller than expected. (honestly i can't remember the actual sentence) and then it says (x < y) where x is the suposed size of the rom and y is the expected size.
i tried with several roms, and a backup a user uploaded somewhere which was suposedly legitimate.
Is there something i can do?
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
My Method
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Thanks for replying
MeeDa said:
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
Click to expand...
Click to collapse
thanks for replying, i did that, when i just plug it without pressing any button the cellphone does not get recognized by the software, when i plug it in emergency mode it does get recognized but the software gives me an error.
blazecodester said:
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Click to expand...
Click to collapse
thanks for the answer, I tried that way, though it keeps getting stuck in the LG logo with the 4 blinking softkeys when it comes to reboot the cellphone.
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
edit: sorry missed that, but if you have access to download mode, the flash tool should work i would think..try it again maybe and make sure you didnt miss anything.
i would try following this guide, make sure you use the g flex .tot and .dll though. copied from the lg g2 back to stock guide from hyelton
hyelton said:
RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Download
1. LGFlashTools v1.8 - Download
2. Drivers - Download
3. Download Both Stock Image File and DLL (Both Files) - Download
Credit to @madmack for making most of this Guide for the G Pro Which also works on our G2
3.1 - FOR SPRINT FIRMWARE - Click Here
3.2 FOR International KITKAT TOT`s Click Here
Install
1. Install the LG drivers downloaded above.
2. Install LGFlashTools v1.6 (but don't run it)
3. Extract the TOT file from the ZIP
Drivers initialization
1. Put the phone into download mode. (Turn off device PRESS VOL UP while plugging in the micro usb cable. If this doesn't work, try holding both volume keys instead)
2. Let the phone initialize and install the drivers. Once done, in Device manager, you should see the LG phone listed under COM ports (something along these lines).
3. Find that LG entry in Device Manager, click on Properties, Advanced and then change the COM port to COM41 and close/save.
4. Unplug your phone! Important step.
LGFlashTools
To get this tool to work, you'll need to do a few tricks.
1. Set the computer's date to some time in July 2012 or before.
2. Disconnect the internet
3. Find a serial number or register key from somewhere on the web (a google search for lgflashtools serial will yield some results). Can't help you here and please don't share any keys in this thread or get us in trouble.
4. Execute the LGFlashTools. It should ask you for a key, put it in. Now you should see a dialog where you can load the DLL file and the TOT files that you extracted earlier. Put them both in here. Click ok
Flashing
5. There is a yellow arrow on the top left. Click on it to initialize the process. Once done, it should say "ready/finished" or whatever.
6. Put the phone in download mode again, and plug it into the USB port. LG FLash Tools should start flashing it automatically. When it's done, it'll automatically reboot into your stock AT&T rom and all of your data and internal sdcard files are gone.
Click to expand...
Click to collapse
Does ADB come up on the normal boot? If so maybe you can remount system and force replace build.prop...
Sent from my LG-LS980 using Tapatalk
Link to All Stock Files, Tools and More
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
jmacphee9 said:
edit: sorry missed that, but if you have access to download mode, the flash tool should work i would think..try it again maybe and make sure you didnt miss anything.
i would try following this guide, make sure you use the g flex .tot and .dll though. copied from the lg g2 back to stock guide from hyelton
Click to expand...
Click to collapse
i have followed that guideline but when i go into download mode the phone displays as a nexus 5 instead of lg g flex and from there the lg flash tool fails to flash anything because it displays different model. remember my build prop was edited to display as a nexus 5
garwynn said:
Does ADB come up on the normal boot? If so maybe you can remount system and force replace build.prop...
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
adb sideload comes up as an option on stock recovery. can you please show me the command to push that. also do i have to pull the old build prop and then push the original one???
just a quick thought here, I had kind of the same problem on my G2 LS980 ( it thought it was a model 801) and to get around the error I used the correct .dll for my model phone but renamed it to the reported models .dll name, this should get the LG Tool past that check .dll error,
so for your case, you will need to find the Nexus .dll to get the name of it, then you will make a copy of your LG Flex .dll and rename that copy to the name of the nexus .dll, then when you manually load the .dll into LG Flash Tool use the renamed .dll, hope this helps you out, best of luck!
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???
best of luck to you!
Hey christiam.coronado any luck on fixing this yet? I have the same problem as you do. Someone edited the build.prob before selling me the phone and when i went to factory reset it without knowing it was rooted and build.prob was messed with now my lg g flex ls995 thinks its a d959at whatever that may be
SOLUTION
**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
christiam.coronado said:
**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
Click to expand...
Click to collapse
I have the same problem, but none of the download links work. Anyone have the files that christiam.coronado linked?
bad build.prop
can i use zv5 tot if im on zv6? i cant find a vz6 tot anywhere. can someone upload it please. im frustrated i messed up my phone for messing with the build.prop tryimg to unlock it. sigh...
hmm
garwynn said:
Does ADB come up on the normal boot? If so maybe you can remount system and force replace build.prop...
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
how would i do that on my sprint g flex 2?
christiam.coronado said:
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
Click to expand...
Click to collapse
Help lg flash tool not working
Sent from my R1 HD using Tapatalk
Hi Guys,
yesterday i wanted to update (dirtyflash) my lg g3, because the 2312-Build of CM13 was extremely buggy (Restarts, Blackscreen by ingoing calls, etc.) I´ve done this before about 10thousand times and on 100 other phones, but yesterday after the flash in TWRP the TWRP wasn´t able to delete the cache.
I tried to flash again to delete dalvik and cache afterwards clean, this time it worked. The phone was booting to the PIN-Entry but it freezes - no entry possible.
I want to try flash back an older build, but phone stucks in bootloop - so i have to manually enter recovery to get into twrp. I flashed an older cm13 build 1812 and cache deleting was not possible again.
Yesterday was Xmas so i thought i will fix it today, but on first time when i tried to get manually into recovery mode, the question for deleting all data appeared, but after that TWRP wasn´t starting, just the stuck lg logo again. (Battery was pulled out for the whole night)
Now im not able to boot into recovery mode anymore or do something else. I tried the download mode (Vol+ and then plug in USB) without access.
I cant do something, just look at the beautiful LG Logo - have you guys some advice for me? What could i try?
THX
I have almost the same problem.
Try to charge the battery without starting the phone. After it had 100 percent I was able to start the recovery..
Benni_LC4 said:
I have almost the same problem.
Try to charge the battery without starting the phone. After it had 100 percent I was able to start the recovery..
Click to expand...
Click to collapse
When i plug it in to charge, after 20 Min. fastboot starts automatic!? Is this normal and will the battery get charged in fastboot mode?
I don´t know if it was on 100% battery after about 1 1/2 hour of loading, but the same issue: It asks me for entering in recovery but didnt start TWRP, Logo Bootloop again.
I tried to fix it with adb/fastboot, but no chance. I get the phone listed, but its offline.
Tried to reboot to recovery with the recovery.img (TWRP) and reboot recovery - it starts twrp but stuck on twrp logo.
Somebody help :crying:
Same thing for me on cm13(18-12) with flash other kernel,i get LG Logo and "Security Error" message under it,i couldnt solve it,then flashed stock rom(.kdz) via usb-download mode and solved problem.
Same problem here.
First the phone freezed a couple of times. Pulled the battery out. Then tried to reinstall, the reinstall failed for some reason. And from then on... Stuck in the LG Logo. When I try to charge the phone the battery icon appears but doesn't show progress.. after many be 20 minutes the phone boots in "fastboot mode", but even then when I connect the usb cable it says that the USB cannot be enumerated.
I managed to take some log from the devices right before it freezed the last time.
http://pastebin.com/FjaAZq87
c-non said:
Same thing for me on cm13(18-12) with flash other kernel,i get LG Logo and "Security Error" message under it,i couldnt solve it,then flashed stock rom(.kdz) via usb-download mode and solved problem.
Click to expand...
Click to collapse
Flash stock would be great, but i have no possibility to enter usb-download mode. Just Fastboot - and just with offline device.
I can start TWRP with the newest TWRP in the ADB Folder as "recovery.img", and then reboot recovery.img - but it get stuck at TWRP-Logo. The phone react to the commands.
I would need a solution to do a factory reset or flash stock with adb/fastboot and offline device.
same here.
i want to try this: http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
anyone know which tot file i need and how do i get it?
take a look on this guide:
http://forum.xda-developers.com/showthread.php?t=2785089
I´ll whant to try this in the next few days, too. Hope that fix the problem and bring not more trouble...
omer323 said:
same here.
i want to try this: http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
anyone know which tot file i need and how do i get it?
Click to expand...
Click to collapse
Benni_LC4 said:
take a look on this guide:
http://forum.xda-developers.com/showthread.php?t=2785089
I´ll whant to try this in the next few days, too. Hope that fix the problem and bring not more trouble...
Click to expand...
Click to collapse
Please read carefully before you try and flash something - both methods requires USB-Download-Mode, which is actually in my case NOT possible anymore.
Today ive got time and will try a few things, if it works i let you know.
Ernesto0023 said:
Please read carefully before you try and flash something - both methods requires USB-Download-Mode, which is actually in my case NOT possible anymore.
Today ive got time and will try a few things, if it works i let you know.
Click to expand...
Click to collapse
i've tried both KDZ method and TOT method - both not working cuase my phone can't go to download mode and does not recognize correctly in PC.
but this guide: http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
seems to do a lot more than this guide: http://forum.xda-developers.com/showthread.php?t=2785089
you sure it is also pointless?
you all should also follow @maxauvy posts in this thread: http://forum.xda-developers.com/lg-...ogenmod-13-0-nightlies-lg-g3-t3257951/page102
he claims he had this problem and solved it!
he is writing a guide right now!
omer323 said:
but this guide: http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
seems to do a lot more than this guide: http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Nr. 1 of your link could work, but it´s the last method for me i will try because i have to open my g3 (de-virgin it) :laugh:
Nr. 2 isn´t a option, look at point 4) Enter to Download Mode and plug USB into your PC -> Download Mode isn´t possible on my coma g3
I think this is the "easiest" solution (Click here) (based on your 1st links solution - but without opening the phone), but i´m not sure i have to donate for the files.
I´m still reading the tutorials and will report how it worked for me.
Hi there,
I just posted a how-to, as @omer323 said above. Glad to see there's a dedicated thread, instead of "polluting" CM13's one (even if it's CM13-related, I think).
The guide I wrote is there, we can discuss about it right here if needed.
If I can help, let me know
maxauvy said:
Hi there,
I just posted a how-to, as @omer323 said above. Glad to see there's a dedicated thread, instead of "polluting" CM13's one (even if it's CM13-related, I think).
The guide I wrote is there, we can discuss about it right here if needed.
If I can help, let me know
Click to expand...
Click to collapse
That was the hardest and longest thing i ever done with an android-phone but hey, it really worked, my g3 is alive :victory::victory:
Here are some "impressions":
My motherboard is a little bit different, but i tried it with the 2nd pin and it was magic! Look here
Disassembly the g3 was a little bit tricky-er as i thought, but i´ve done it, maybe some help for somebody to see the parts you can take off, see here: Parts 1
Parts 2
You have mentioned in your guide, that you´ll need a 3rd hand to plug in usb while pointing at gnd and the pin - in my opinion a 4th hand would be better - but i´ve created a "connector" to be able to fix it on ground and on the other side a needle, to be sure just to point just the pin2-solder-point, look here: SelfmadeConnector
Flashtool v1.8 didn´t worked for me (on Win10 64-bit), tried to flash instead .kdz with FlashTool2014 with success. Before that i had to lower the com-port to port 6 - i dont know why but it didn´t worked with port 41. for example com6
:fingers-crossed::good: I wish i could click on "Thank you" twice
One thing left:
I am rooted on stock with TWRP running but no IMEI. (IMEI: 0)
I´ve got an efs-backup of my g3, but no .img-file just folders with about 2GB Data in it - about ~20 .win and .md5 files.
Can i restore the imei and the other stuff i´ve lost through the wipe with this files or should i just restore the imei like mentioned in your guide? (What if I don’t have any EFS backup?)
Thanks for that guide and adventure
Ernesto0023 said:
That was the hardest and longest thing i ever done with an android-phone but hey, it really worked, my g3 is alive :victory::victory:
Here are some "impressions":
My motherboard is a little bit different, but i tried it with the 2nd pin and it was magic! Look here
Disassembly the g3 was a little bit tricky-er as i thought, but i´ve done it, maybe some help for somebody to see the parts you can take off, see here: Parts 1
Parts 2
You have mentioned in your guide, that you´ll need a 3rd hand to plug in usb while pointing at gnd and the pin - in my opinion a 4th hand would be better - but i´ve created a "connector" to be able to fix it on ground and on the other side a needle, to be sure just to point just the pin2-solder-point, look here: SelfmadeConnector
Flashtool v1.8 didn´t worked for me (on Win10 64-bit), tried to flash instead .kdz with FlashTool2014 with success. Before that i had to lower the com-port to port 6 - i dont know why but it didn´t worked with port 41. for example com6
:fingers-crossed::good: I wish i could click on "Thank you" twice
One thing left:
I am rooted on stock with TWRP running but no IMEI. (IMEI: 0)
I´ve got an efs-backup of my g3, but no .img-file just folders with about 2GB Data in it - about ~20 .win and .md5 files.
Can i restore the imei and the other stuff i´ve lost through the wipe with this files or should i just restore the imei like mentioned in your guide? (What if I don’t have any EFS backup?)
Thanks for that guide and adventure
Click to expand...
Click to collapse
happy to know it works for more people!
thanks for the tips!
ill go for it today
omer323 said:
happy to know it works for more people!
thanks for the tips!
ill go for it today
Click to expand...
Click to collapse
Do somebody got an advice for me:
One thing left:
I am rooted on stock with TWRP running but no IMEI. (IMEI: 0)
I´ve got an efs-backup of my g3, but no .img-file just folders with about 2GB Data in it - about ~20 .win and .md5 files.
Can i restore the imei and the other stuff i´ve lost through the wipe with this files or should i just restore the imei like mentioned in your guide? (What if I don’t have any EFS backup?)
THX a lot
Ernesto0023 said:
Do somebody got an advice for me:
One thing left:
I am rooted on stock with TWRP running but no IMEI. (IMEI: 0)
I´ve got an efs-backup of my g3, but no .img-file just folders with about 2GB Data in it - about ~20 .win and .md5 files.
Can i restore the imei and the other stuff i´ve lost through the wipe with this files or should i just restore the imei like mentioned in your guide? (What if I don’t have any EFS backup?)
THX a lot
Click to expand...
Click to collapse
Those files you're talking about, how did you get them ? Using TWRP ? If so, just use the "restore" menu of TWRP and point to the directory where your files are stored. It should recognize the backup.
Happy to hear that you've been able to unbrick your phone
maxauvy said:
If so, just use the "restore" menu of TWRP and point to the directory where your files are stored. It should recognize the backup.
Click to expand...
Click to collapse
Thanks for that advice.
Yes i had these files from a TWRP-EFS-BACKUP, but i wasn´t able to point to something, the list in twrp/restore was just empty.
I moved the files in the TWRP Folder on Internal Storage and voilá it listed the Backup and i was able to restore everything: IMEI, MAC, ....
My G3 is right now not just back from coma, its like re-born :fingers-crossed:
Thank you mate!
This hasn't happened to me but just curious if it has been tested to skip the erasing EMMC part and just rewriting each partition with LG Board Diag?
Partitions to write would be:
PrimaryGPT
modem
aboot
rpm
tz
laf
recovery (I'd replace the stock recovery bin/img with a TWRP img file... this way you can just boot into TWRP after writing everything)
dbi
sbl1 (write sbl1 last if possible)
then boot into TWRP... flash the latest modem/rpm/tz combo required to CM 13... then flash CM 13, gapps, etc...
if you still get stuck at boot up... boot back into TWRP and hit the Wipe button > swipe slider to factory reset data.
I ask because I'm sure there are some who haven't backed up their EFS... this might be a way to avoid that? Of course.. depending on what parts of the emmc were messed up... it may be possible a full wipe is still needed like the guide above mentions. But any chance at avoiding that step would be ideal in my opinion.
maxauvy's guide worked perfectly for me!!
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Psicovirus said:
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Click to expand...
Click to collapse
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Psicovirus said:
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Click to expand...
Click to collapse
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Nicktheprofessor said:
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Click to expand...
Click to collapse
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Psicovirus said:
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Click to expand...
Click to collapse
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Nicktheprofessor said:
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Click to expand...
Click to collapse
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Psicovirus said:
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Click to expand...
Click to collapse
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Nicktheprofessor said:
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Click to expand...
Click to collapse
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Psicovirus said:
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Click to expand...
Click to collapse
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Nicktheprofessor said:
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Click to expand...
Click to collapse
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Psicovirus said:
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Click to expand...
Click to collapse
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Nicktheprofessor said:
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Click to expand...
Click to collapse
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Edit2: Seems like i screwed up stalling stock recovery on top of twrp, sahme on me. How can i short the volume down button?
Psicovirus said:
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Click to expand...
Click to collapse
Reboot to recovery, use adb to sideload the OTA.
Reply to edit2: open it up, find the leads on the circuit board that go up to the vol down circuit breaker, use two needles and insert them into the solder where the breaker connects and while crossing the needles so they connect push power.
OR, fix the broken breaker, most of the time it's just a broken off brass dome that needs realigning, you'll need to fixate it which is just a needle's head worth of superglue on one side and a soldering on the other side (reflowing by heating the dome with a soldering iron usually works).
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Nicktheprofessor said:
Reboot to recovery, use adb to sideload the OTA.
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Click to expand...
Click to collapse
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Psicovirus said:
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Click to expand...
Click to collapse
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Nicktheprofessor said:
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Click to expand...
Click to collapse
Im trying to do that, i already have the phone open, sewing needles will do?
Psicovirus said:
Im trying to do that, i already have the phone open, sewing needles will do?
Click to expand...
Click to collapse
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Nicktheprofessor said:
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Click to expand...
Click to collapse
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Psicovirus said:
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Click to expand...
Click to collapse
You can use a q tip and some acetone to clear eventual lacquer from the solder points but the thing is, it's probably the emmc that is shot.
Your emmc obviously doesn't accept what the recovery the LGUP wrote to it. If it did, you'd be flashing the OTA right now. Why? I have no idea, I'd need to take the phone to the lab to examine what caused the degradation and even then I probably couldn't tell you much more about the actual cause.
And don't worry about it, your case is interesting and not easy to solve by simply doing a search, you weren't an arse about anything either and that is unusual and welcome.
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
redchigh said:
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
Click to expand...
Click to collapse
The LG driver you've installed on your laptop is most likely no longer functional for the phone. If it shows in Device Manager when you're trying to connect it, uninstall it (mine didn't work either after unlocking/using FWUL, or something else, for whatever reason).
Once the current driver is uninstalled, turn off your computer, plug your phone in with the USB cable and then turn on the computer and let Windows install the driver now (It worked on mine).
See the attachment below for a screenshot of the current driver for my LG G4 that is working completely.
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
redchigh said:
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
Click to expand...
Click to collapse
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
sdembiske said:
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Click to expand...
Click to collapse
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
sdembiske said:
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
Click to expand...
Click to collapse
Thanks for the reminder, I'll try to remember.
redchigh said:
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
Thanks for the reminder, I'll try to remember.
Click to expand...
Click to collapse
OK - one last thing to try if you want to try it. Using the power and volume keys, see if you can get into Recovery mode to do a hard factory reset
- refer to this link for the how-to for entering Recovery mode: https://www.androidexplained.com/lg-g4-recovery-mode/