Hi to all,
Been here for a while and every time i log here in XDA (O3D forum), I always see new people bricking their newly bought O3D (stuck on LG Screen..., rebooting only to cwm recovery.., etc..etc..). If you got into a situation just do the search thing before posting a new topic which is already been posted because our forum (O3D Community) is still small so searching wouldn’t be a problem and there’s no need for a dig yet when reading all the topics posted here. All i can say is for all the people who just bought O3D always remember this "If it aint broke then don’t fix it" you will just end up voiding your warranty,
if there’s an update don’t try to push it on your warranted device, try to check first if the update is applicable to your device (country or region) because we all know that LG only released O3D in Europe so if you are in that place and check that your devices have an update, go grab it, but when it fails always call LG Europe (because you have a warranted device and they will assist you) and explain to them that you are experiencing difficulties in updating your unit, and for everyone else who is not in Europe (like me were my unit is not warranted)be very careful if you want to forcefully push that update to your unit (v10b, v10d or even cwm 4.0.0.9) because me i already bricked my device 3 times were i end up booting only in LG and nothing follows, the other is booting only to CWM again and again, and the last one is after unbricking the device and setting everything then when rebooting the unit it will end up stuck at the LG original android recovery system <3e>menu.
Note: Do this procedure at your own risk, i repeat "AT YOUR OWN RISK", its your unit so its your responsibility, you've been warned, i myself grab that risk and now I’m happy with my unbricked O3D (v10d July, 8, 2011 with fully working CWM 4.0.0.9), all the tools we need are here at XDA so there will be no problem getting those tools.
Ok enough about nonsense(hahaha), lets go down to business. As what the Title says, here we go.
Requirements:
This method will only work in WINDOWS XP MACHINE, i have tried it in Vista and Windows 7 but it will just hung.
I assume that all the necessary drivers are already installed from your machine because without them you can’t bricked your O3D. If by any means you don’t have it, just grab it from http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp and click the download link save it then run it after installing, it will run automatically, then do the following:
1. Go to Customer Support ---> Application, Manual & USB Driver Download.
2. Enter you IMEI then click the Search button.
3. After Searching, it will list two files form the File List, double click any of those file (me, i choose the file with divX converter)
4. After downloading, it will extract its content to C:\LGP920
5. Go to this directory C:\LGP920\USB_Driver, and double click LGUnitedMobileDriver_S4981MAN33AP22_ML_WHQL_Ver_3.3
6. Let it finish then if it ask to restart your pc, do it.
7. Optionally you can install the LGPCSuite, it can be found in c:\LGP920\LGPCSuite\, just double click the LG_PCSuiteIV_Setup.exe and follow the instruction.
Now that we have installed the drivers for O3D, we can move on to the next instruction.
Make sure to follow the instruction carefully and proceed if you know what your doing.
I have edited nikhil4186 and victortangocharlie post (Original thread: http://forum.xda-developers.com/showthread.php?t=1060121)
1. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
2. [IMPORTANT] Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.).
3. Remove the Micro SD from your O3D.
4. Download the KDZ rom v10b_00 posted by Fab985 : http://forum.xda-developers.com/showthread.php?t=1155874
(v10d_00 is already available but this method is only tested with the v10b_00 rom, so if you wanna try your luck, its up to you)
5. Download the KDZ updater - http://forum.xda-developers.com/showpost.php?p=8651505&postcount=1
6. Extract it, then run the msxml.msi
7. Now the next step will be crucial because you need a full battery (for safety of course if you don’t want your unit to die while in the middle of the unbricking process) and you will put your unit in emergency mode (by pressing the power button and the volume up button), here’s how you will do it.
Case A. (This is my Case)
If your O3D can boot but only in CWM, charge it (me, i charge mine for 3hours in cwm), you wont see a charging status but you will feel your battery getting warmer.
Case B. (Never happen to me)
If your unit is just stuck at LG logo, try to charge it too and see if your battery is getting warmer, if not, better find another way to charge your battery or a friend who has O3D and borrow the battery.
Once everything is ok proceed to step 8.
8. Open Device Manager and under Modems check if you really disable the LGE Virtual Modem, if it is already disabled don’t close Device Manager, we will need it on the next step. Make sure you can see your Device Manager window and your modems devices are expanded (were you can see the disabled LGE Virtual Modem)
(THIS IS THE TRICKY PART AND YOUR O3D WILL JUST STAY BLACK SCREEN)
9. Plug your USB cable to your pc and then plug it to your phone then enter Emergency MODE (power button plus volume up button) This step is very tricky (me, i tried it several times before it detect my O3D as LG USB modem).
First when your pc detects your O3D, it will detect as OMAP4 then it will look for its drivers, just cancel it, then another device will be detected, if you successfully entered Emergency mode, your O3D will be detected as LG USB Modem, this modem should stay, if it disappear then you failed to enter the emergency mode correctly, try it again before continuing to the next step.
10. Run KDZ_FW_UPD.exe from the extracted folder.
11. Put the following settings:
Type : 3GQCT PhoneMode : DIAG
12. Under the KDZ File, choose the KDZ file you've downloaded from Fab985 post (v10b_00)
13. Press the Launch software update. (this part will take time because it will extract the kdz file into cab file, it took me 15 to 20 mins before it proceed to the updating process)
14. Once updating has started you will encounter this message:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
This message will come out from 1 to 100 counts:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
CDMA: wPrama = 2004, IParam = 2
Model Dll Msg Not Found(2004, 2)
And so on till:
CDMA: wPrama = 2004, IParam = 100
Model Dll Msg Not Found(2004, 100)
(Note: This message is case to case because i experienced diff counts then the LG USB MODEM disappear from the device manager list, first attempt count 64 then LG USB Modem disappear from the list, the kdz flasher stops from count 64, waited up to 10 minutes but nothing happens so tried it again from the enter emergency mode step, second attempt count 76 LG USB modem disappear but after a while kdz flasher still continues up to 100 counts then it stop there, waited for 5 minutes nothing happens so decided to remove my device and turn it on and viola it booted to LG original Android system recovery <3e>)
15. After you reach the 100 counts, the process is done, the LG USB modem from the Device manager will be gone, but don’t remove yet your phone to reboot it, try to wait up to 5 minutes before disconnecting your phone.
16. Turn on your O3D, if it boots in LG original android recovery, just choose the wipe data/factory reset, then reboot system now. Then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 17.
17. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition then reboot system now.
18. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 19.
19. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition, and lastly wipe nv dynamic partition then reboot system now. (this part resolve my rebooting issue)
20. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not I guess it’s the end of the line for now.
Sorry for this very long instruction. If it helps you I don’t have a beer fund because I’m not a dev. but a simple hit with thanks will do.....
TIPS NOT RELATED TO UNBRICKING:
Rooting:
Run SuperOneClick as Administrator, before clicking Root, click first the Driver Check and if no problem has been detected, no more settings is required just click the Root button then wait until it says done or finish.
ClockWorkMod:
After rooting, download rom manager from the market, after the install run it and tap Flash ClockworkMod Recovery (4.0.0.9), once successful you may now backup your current rom before you mess again with it, since I installed cwm in my O3D I never use the buttons to boot with it(power button plus volume down button), I always use the menu's with the rom manager to boot into or backup or restore or flash in CWM.
Upgrading:
For safety purposes, if you have a warranted device and then an update pops out, always do a fresh start, what I mean is if you already rooted your device and installed CWM, better removed it first before updating your O3D so when things goes wrong from your update process you can always call LG for it to be fix eliminating the needs to post something like “Help I brick my O3D and I can’t bring it to LG because I installed CWM blah blah blah etc.. etc…”, got the point so be responsible.
For the Mod: Sir if my post will violate something feel free to removed this post. more power XDA!!!!!
Many thanks to the following:
Aremcee
Renegade_Rules
Fab985
ik911
nikhil4186
victortangocharlie
and everyone here at XDA....
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
wuper said:
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
Click to expand...
Click to collapse
Did you follow the whole step, I know its a long process and it work with me, just follow everything and when you are in step 9 were you need to enter emergency mode,its a tricky step,make sure LG Mobile update is not running completely,open your pc device manager and expand the modems,try to remove the battery then press volume up and power button, put the usb cable then put back the battery,it will vibrate then your xp machine will detect it as omap4 device just cancel it but don't de-press the volume up and power button,then after a while it will vibrate again check if you see LG usb modem in the device manager,once you saw it and it stays,it means you successfully entered emergency mode then that will be the time you will run the kdz flasher and follow the succeeding steps.
Sent from my unbricked LG-P920 using XDA Premium App
bro I tried it with lg mobile modem disabled lg virtual modem disabled both are not disabled both are disabled but none of them make sense. Model Dll Msg Not Found(2001, 0)
is written and lg mobile driver gone but the phone does not reboot both 10d and 10b tried I restarted manually and it opens with fw update screen
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
wuper said:
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
Click to expand...
Click to collapse
I have bricked my phone numerous times, and in many imaginative ways. The above instructions are pretty much what I do whenever it gets stuck in some non-functional mode.
I tried this way like 30 times during the last week, I just got back from holiday and I just tried it on a Win XP machine and it's always the same it flashes and it never reboots, V10B/D doesn't matter... After flashing I manually power it on, and only get the Firmware update screen and it hangs there forever... I called LG today waiting for a replacement.
@aremcee
Sir thanks for confirming that this method really works.
@wuper @renegade_rulez
Are you doing it in xp machine, if you run it in Windows 7 the process will just fail. Only disable the LG virtual modem from your pc device manager and completely exit LG PcSuite and LG Mobile update. Make sure your xp machine detects your O3D as LG USB MODEM and not omap4 device, the detected LG usb modem should stay in your device manager under modem and it should be enable then you can now start kdz flasher. Will try to investigate what causing your O3D not to flash using the kdz flasher and if I have time will upload a video on how to properly enter emergency mode.
@all
Thanks for reading this, if you have a question just post it here and will try to answer it back as knowledgeable as I can.
Sent from my unbricked LG-P920 using XDA Premium App
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
wuper said:
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
Click to expand...
Click to collapse
Hi wuper,
Can you try after flashing then turn on your device to recovery by pressing volume down + power button, or remove your battery then put it back while pressing those buttons, will it go to android recovery system <3e>?, if yes try to wipe everything then reboot. let me know. thanks.
Like wuper just told, mine is the same... It's not fixable in that way. Again this morning I tried on my XP pc and it's always the same. Just called LG again they will replace it within 24h we will see
update:
You cannot get into the recovery system, holding power + volume down the phone will power on and off again, releasing power when it boots and keeping volume down pressed gets the Firmware update screen.
same for me cannot enter recovery
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
Hi Zirowe,
Hmm thats strange, you and dnardz have the same problem, wiping the nv dynamic partition solved my rebooting issues and didnt experience this battery not charging problem, try to root your phone and install clockwork recovery 4.0.0.9 then reboot to cwm and full wipe your O3D including the battery stats, then charge your phone again and see if it is charging(maybe two hours), if it still doesn't work, download the v101d cmw rom by PUAJohn and restore it. Let me know
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
try deleting batterystats.bin then rebooting.
Thank you, I will try it.
Will try it too..thanks Johnance17.
hefonthefjords said:
try deleting batterystats.bin then rebooting.
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately, everything is the same..
hi,
It's strange what happens to you.
Have you tried this?
-Turn device off
-Take out batery
-Wait 5 min
-Re-insert battery
-do a hard-reset
-boot up device completly
-Turn device off
-plug-in charger (NOT USB-PC)
-Wait 1 hour
sorry I do not see much solution
It didn't work on mine also...restoring 10d and erasing battery stats..
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
As u mentioned, I think that your phone has gone to a Soft Brick. I don't know much about the Korean build, so Google it to solve the Soft Brick. Try flashing the stock rom via odin but I don't recommend it since it may cause your phone to be hard bricked if not done properly.
So go to the service centre, you'll get more help there
Sushant Rohan said:
As u mentioned, I think that your phone has gone to a Hard Brick. I don't know much about the Korean build, so Google it to solve the Hard Brick. But it is very hard to solve
Click to expand...
Click to collapse
I thank you sir for responding to this. From what you have said, I think the best decision is to take it to Samsung service center. (For I have tried to google it but I couldn't get a solution). I would also like to know if it is repairable, and about the cost, is it worth repairing or should I think of buying a new phone?
I am stranded.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
Download stock firmware (like xxxx.tar.md5 full Odin package) of ur device ,enter into Download mode of ur device & flash stock firmware with Odin.
Try this...
Hey all!
Long-time lurker, first-time poster in this subforum (as I have a G3 now). It's late and I'm writing this up here in case someone here has problems with their D850. Long story short: I downloaded CM 13 for the D855 and changed the updater-script and replaced d855 with d850. It flashed, but then it immediatelly rebooted and left me with fastboot, while it said it was receiving commands, they didn't complete. True bogus. LGFlashTool said the BIN file was for D850 but the model was D855 (which was wrong anyways).
Solution (it's late and I need to go to bed):
1. Download TOT (inside ZIP file) from this guide: http://forum.xda-developers.com/showpost.php?p=64624324&postcount=2
2. Use THIS DLL FILE (yeah, it's for LGUP, but it works): http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3 (The LGUP_LG_G3.zip - 16.9 Mb).
3. Open LGFlashTool using the first guide and whatnot. However, IN DLL FILE, use the DLL installed from the MSI file in the 2nd guide. In my computer, it was located here: C:\Program Files (x86)\LG Electronics\LGUP\model\8974\LGUP_8974.dll
4. Follow the flash guide. Hopefully it'll work up to the Factory Reset Status 3. Then, after a while LGFlashTool will be in red and say DOWNLOAD FAIL. OMG IT'S ALL OVER... Nope. Take your phone's battery out and place it back in...
Voilá! problem fixed!.
If I helped you get your phone back after the same trouble I went through and this post was useful, please send me a beer! (use the donate button at the left) I'll really appreciate it
Note: I don't know much about LG flashing, I only had this issue and figured I'd share the solution and pay back the favor
Thanks for contributing. This probably would have fixed my messed up G2 that I had to get rid of. I was also stuck in fastboot with no commands getting executed.
I'm not sure if your also able to help me on this one problem. After the flash tool reaches about 80% - 83% it says "waiting for reset 40 sec" and also resets my phone and briefly shows the android with small, blue loading bar under it. A second after it resets again and into a bootloop. If I leave it alone for awhile it goes into a blue screen with a red number 2.
rockertflip said:
I'm not sure if your also able to help me on this one problem. After the flash tool reaches about 80% - 83% it says "waiting for reset 40 sec" and also resets my phone and briefly shows the android with small, blue loading bar under it. A second after it resets again and into a bootloop. If I leave it alone for awhile it goes into a blue screen with a red number 2.
Click to expand...
Click to collapse
No idea man, but I think you should wait until it reaches 3, then when it's at 3 you should take the battery out and then it should revive. That's what I did to mine anyways. Also, it takes a long while to reach 3, let it sit for about 30 minutes max I guess. I think I waited about 5, but your case may vary.
i have the same exact issue the .tot flashes suxcessfully and then the robot on reboot and then bootloop..but i dont ever get a red2 it just keeps rebooting
Sent from my SAMSUNG-SM-N920A using Tapatalk
thnx
I accidentally flashed a D851 version of Stock MM ROM in my D850 Phone. Now i can boot into recovery
Customer Recovery TWRP :3.0.0 installed
Nandroid backups of Stock MM ROM ( Tekcafe ROM ) is available through booting into recovery.
how can i boot into recovery?
farroo said:
I accidentally flashed a D851 version of Stock MM ROM in my D850 Phone. Now i can boot into recovery
Customer Recovery TWRP :3.0.0 installed
Nandroid backups of Stock MM ROM ( Tekcafe ROM ) is available through booting into recovery.
how can i boot into recovery?
Click to expand...
Click to collapse
If you can't get into recovery you need to use LG Flash Tool to flash a stock ROM, this method may help.
darkguy2008 said:
If you can't get into recovery you need to use LG Flash Tool to flash a stock ROM, this method may help.
Click to expand...
Click to collapse
thanks for the reply. yes I can enter into download mode with battery pulled off and connecting to pc with cable.
Hi Everyone, I realized this is a very old thread, but I have an old G3 phone that could only boot into the download mode. LG Flash tool expects fastboot mode, while LGUP tool showed unknow model and refused to proceed. Is there a way to force flash regardless in download mode?
Backgrond: my phone boot into fastboot mode before, but I might have flashed the wrong .img files and now it coud only boot into the download mode.
Thanks!
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
power off ur device !!!
open msm software and connect ur phone through usb and press up volume + power button and u will see it getting connected to the msm software and leave it till ur phone starts booting ito OOS 5.1.5
Here is the Link to the MsmDownloadTool V4.0:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
With this Tool, you get your Phone working again.
StandBrik said:
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
Click to expand...
Click to collapse
I hope u fixed it by now, but if you still haven't fixed it yet, you can go back to slot b by using this commands "fastboot --set-active=B" without the quotes
Because I messed up my slot a, so i used that command to boot using slot b and it worked. So, if the problem is with your slot a and everything with your slot b is fine, then you just need to change to slot b with that command and all should go well :highfive:
just noticed that you're having a problem accessing the bootloader. First, make sure your device is not connected to your pc or anything. Then, whether your device is off or stuck in that black screen, just hold vol up and power off at the same time and wait until it eventually boots into the bootloader mode.
Problem solved with MSM software. Thanks everyone. If someone has the same issue. Just download MSM software and use the following guide :
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
It is actually quite impossible to totally hardbrick a device like this one.
Cheers
Glad to hear that.
Just in case i got into that problem, could you lead me to the files you downloaded since the ones in that link seem to be for OnePlus 5
In my situation, I have a black screen, and a fixed blue LED.
I want to put the LineageOS ROM, but it's impossible, even though it performs the installation of the ROM correctly, when you restart it that happens, and then it doesn't even let you install or start the TWRP again.
It only remains to use MSMDownloadTool, to return to the Stock rom.