Yesterday my phone froze and shut down on me. I restarted the phone but It won't load past the LG screen before turning back off. Then it won't turn back on unless I do a battery pull but that still doesnt get me past the LG logo screen. I was running Resurrection Rom MM and before that JasmineRom 35b.
I am able to put it into download mode but nothing else(not even TWRP)
Which is the correct method to getting back to a rooted 35b and what files, tools and programs do I need? Keep in mind I was on 35b. KDZ? TOT? LGUP? LGFlashTool?
I appreciate any help and links...
Edit: Just tried the LgFlashTool TOT method using the lgup8974dll and the 10b TOT file.
Phone disconnected and turned off while at 6% (on the LGFLashTool program not on my phone), Got a bunch of can't communicate with port errors and a big Download FAIL. Not sure if it's battery related or not but I ordered a spare and a charger just to be sure as I am unable to tell if the phone is even charging the battery right now or how much charge it has left (Notification light stays off while plugged in and the charging animation freezes and then the phone shuts back down)
cali4nia831 said:
Yesterday my phone froze and shut down on me. I restarted the phone but It won't load past the LG screen before turning back off. Then it won't turn back on unless I do a battery pull but that still doesnt get me past the LG logo screen. I was running Resurrection Rom MM and before that JasmineRom 35b.
I am able to put it into download mode but nothing else(not even TWRP)
Which is the correct method to getting back to a rooted 35b and what files, tools and programs do I need? Keep in mind I was on 35b. KDZ? TOT? LGUP? LGFlashTool?
I appreciate any help and links...
Edit: Just tried the LgFlashTool TOT method using the lgup8974dll and the 10b TOT file.
Phone disconnected and turned off while at 6% (on the LGFLashTool program not on my phone), Got a bunch of can't communicate with port errors and a big Download FAIL. Not sure if it's battery related or not but I ordered a spare and a charger just to be sure as I am unable to tell if the phone is even charging the battery right now or how much charge it has left (Notification light stays off while plugged in and the charging animation freezes and then the phone shuts back down)
Click to expand...
Click to collapse
Not 100% sure but sounds like you do not have the correct drivers installed on your PC. Here is a link to the LG drivers http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black. Other problems could be USB cable or USB port. Here is a link to a thread in G3 general that might help http://forum.xda-developers.com/showthread.php?t=2785089. Hope some of this helps.
mopartonyg said:
Not 100% sure but sounds like you do not have the correct drivers installed on your PC. Here is a link to the LG drivers http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black. Other problems could be USB cable or USB port. Here is a link to a thread in G3 general that might help http://forum.xda-developers.com/showthread.php?t=2785089. Hope some of this helps.
Click to expand...
Click to collapse
I will definitely look into this, thanks! I still think Im gonna wait for the battery to get here before I try anything since I don't want it to die on me my while flashing and cause more headaches.
So the TOT method is what I should be doing?
cali4nia831 said:
I will definitely look into this, thanks! I still think Im gonna wait for the battery to get here before I try anything since I don't want it to die on me my while flashing and cause more headaches.
So the TOT method is what I should be doing?
Click to expand...
Click to collapse
If i am having issues I always start with the 10B tot method,, it restores more partions than the kdz way. 10BBB is also easier to root and install twrp.
mopartonyg said:
Not 100% sure but sounds like you do not have the correct drivers installed on your PC. Here is a link to the LG drivers http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black. Other problems could be USB cable or USB port. Here is a link to a thread in G3 general that might help http://forum.xda-developers.com/showthread.php?t=2785089. Hope some of this helps.
Click to expand...
Click to collapse
mopartonyg said:
If i am having issues I always start with the 10B tot method,, it restores more partions than the kdz way. 10BBB is also easier to root and install twrp.
Click to expand...
Click to collapse
Thanks for the info. I really appreciate it!
Well I think I officially bricked my phone guys :/
Don't know how but it stopped going in to download mode. My guess is when I removed the battery and accidentally pressed the power button while it was off as after that It would just pop up as qualcom husb qloader 9008. Then after a couple more times trying, it stopped turning on all together. Shame as I really loved this phone but more than that I am now phoneless for a good while. Thanks for all your help, I really do appreciate it...
All is not lost. The hard brick option works. I had a similar issue a few days ago when I accepted the latest 97a OTA. After seeing how it caused problems with my SD card, I was tot flashing back to 10b when I bumped my desk the phone was on which caused my USB connection to get interrupted during the sync. No download mode.
The hard brick recovery appears scary but it really isn't. If you don't want to solder, then the hardest part is using the wire to make two connections with one hand so you can plug and unplug the USB cord with the other hand after you manually flash each partition. But it works. I just did it for the first time. Just read the instructions over and over until you're sure you understand what is needed. The instructions are in the general forum. Here's the link:
http://forum.xda-developers.com/showthread.php?p=64446369
Do a search on how to get to the g3 motherboard. There are YouTube videos that show how to do it. It's really not that difficult. After that, there is a silver cover over the CPU. Use a small plastic tool to carefully pry it off. It snaps back on. You do NOT unhook any other connections and you leave the motherboard in the case as you'll be flashing each partition manually using the 10b tot. I couldn't get the final partition to flash (sbl1) using the tool supplied in the instructions, but that's fine. I was able to boot into download mode without flashing sbl1 and then flashed the 10b tot using the LG tools and I was back up and operational.
Sent from my VS985 4G using Tapatalk
iBolski said:
All is not lost. The hard brick option works. I had a similar issue a few days ago when I accepted the latest 97a OTA. After seeing how it caused problems with my SD card, I was tot flashing back to 10b when I bumped my desk the phone was on which caused my USB connection to get interrupted during the sync. No download mode.
The hard brick recovery appears scary but it really isn't. If you don't want to solder, then the hardest part is using the wire to make two connections with one hand so you can plug and unplug the USB cord with the other hand after you manually flash each partition. But it works. I just did it for the first time. Just read the instructions over and over until you're sure you understand what is needed. The instructions are in the general forum. Here's the link:
http://forum.xda-developers.com/showthread.php?p=64446369
Do a search on how to get to the g3 motherboard. There are YouTube videos that show how to do it. It's really not that difficult. After that, there is a silver cover over the CPU. Use a small plastic tool to carefully pry it off. It snaps back on. You do NOT unhook any other connections and you leave the motherboard in the case as you'll be flashing each partition manually using the 10b tot. I couldn't get the final partition to flash (sbl1) using the tool supplied in the instructions, but that's fine. I was able to boot into download mode without flashing sbl1 and then flashed the 10b tot using the LG tools and I was back up and operational.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thank you so much for the info. Gives me hope I can get this back up and running. It actually doesn't sound to hard compared to the things I do to fix other phones, So I hope this will get my G3 back up and running again!
Thanks!
iBolski said:
All is not lost. The hard brick option works. I had a similar issue a few days ago when I accepted the latest 97a OTA. After seeing how it caused problems with my SD card, I was tot flashing back to 10b when I bumped my desk the phone was on which caused my USB connection to get interrupted during the sync. No download mode.
The hard brick recovery appears scary but it really isn't. If you don't want to solder, then the hardest part is using the wire to make two connections with one hand so you can plug and unplug the USB cord with the other hand after you manually flash each partition. But it works. I just did it for the first time. Just read the instructions over and over until you're sure you understand what is needed. The instructions are in the general forum. Here's the link:
http://forum.xda-developers.com/showthread.php?p=64446369
Do a search on how to get to the g3 motherboard. There are YouTube videos that show how to do it. It's really not that difficult. After that, there is a silver cover over the CPU. Use a small plastic tool to carefully pry it off. It snaps back on. You do NOT unhook any other connections and you leave the motherboard in the case as you'll be flashing each partition manually using the 10b tot. I couldn't get the final partition to flash (sbl1) using the tool supplied in the instructions, but that's fine. I was able to boot into download mode without flashing sbl1 and then flashed the 10b tot using the LG tools and I was back up and operational.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Sorry for the late response but I've been busy and had to put off my attempt until now but did you keep getting a device not in download mode error while flashing? It passed the ap check and emmc test at first but when I tried to flash the first (aboot) partition it gave me that warning. Is this what you meant about that you had to keep forcing it in to Dload mode by shorting the pins everytime you flashed each new partitions?
Thanks I can't believe I actually pulled off shorting the pins that first time, It took me forever!
cali4nia831 said:
Sorry for the late response but I've been busy and had to put off my attempt until now but did you keep getting a device not in download mode error while flashing? It passed the ap check and emmc test at first but when I tried to flash the first (aboot) partition it gave me that warning. Is this what you meant about that you had to keep forcing it in to Dload mode by shorting the pins everytime you flashed each new partitions?
Thanks I can't believe I actually pulled off shorting the pins that first time, It took me forever!
Click to expand...
Click to collapse
Yup. You have to short it again after each flash. Also once I got to the sbl1 partition, I couldn't get that to flash so I rebooted into download mode and flashed the 10b tot. You're almost there.
Sent from my VS985 4G using Tapatalk
Related
So, you've been flashing stuff and now for whatever reason, your phone won't boot.
Now you're trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Bubbajoe40356 said:
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Click to expand...
Click to collapse
I kind of like seeing everything written out several times . . . it's like deja-vu all over again.
Good job cris, lets hope this gets used!
Lol... I kinda made it for me to use.
I've typed this out a couple dozen times... now I can just link to here
studacris said:
So, you've been flashing stuff and now for whatever reason, you're phone won't boot.
Now you"re trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Click to expand...
Click to collapse
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
What does it mean to Odin? I kdd....great work
rquiett said:
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Show off
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Awesomeness bump. Great read.
Sent from The Bacon Pope's Oppo Find 5
Phone stuck
Hi, I'm hoping maybe someone can help me figure out what the problem is.
I'm trying to flash CWM Recovery on GTI9105p. I've actually done this before on the same device, but this time it doesn't work. Odin seems to work fine and shows PASS! after 32 seconds, but my phone stays on "Downloading..." with the blue bar full. If I manually reboot the device and try to go to recovery, it stays on Samsung model logo. Otherwise I can boot the phone just fine. What could be the issue?
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
ChiefIlliniwek5 said:
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
Click to expand...
Click to collapse
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
netookska05 said:
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
ChiefIlliniwek5 said:
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
Click to expand...
Click to collapse
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
netookska05 said:
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
Click to expand...
Click to collapse
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
ChiefIlliniwek5 said:
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
Click to expand...
Click to collapse
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
netookska05 said:
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
ChiefIlliniwek5 said:
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
Click to expand...
Click to collapse
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Also, were you already rooted and wanted to go back to stock or what version of software were you downgrading from ( ex. 46A,47A what).
netookska05 said:
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Click to expand...
Click to collapse
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
ChiefIlliniwek5 said:
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
Click to expand...
Click to collapse
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
So the long story is that I was originally running 47A stock with root and TWRP recovery. I was having TERRIBLE battery life and it got to the point where I couldn't take it any more so I decided to flash a CM13 nightly. I was going to test the waters to see if I could use a systemless SuperSU version with CM13 so when I flashed CM13 I also flashed SuperSU 2.68 at the same time. It turns out that's a big no-no. So when I tried to reboot, I got the error message that the secure boot failed, or something to that effect. So after looking at posts on XDA I intended on doing the "revert to 10B from 47A" method with a TOT file and the flash tool. Everything with that was working great...it got to 94% complete and got the point in the process where the phone reboots, but when the phone left download mode it never came back and the flash tool never made a re-connection with the phone to complete the end of the process. From that point on, I could not even load into download mode, thus here I am.
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
Ok so I used the androidbrick tool in that link you sent me and the process seems to have gone through correctly. After re-installing my battery the phone booted to the LG screen, then showed the little android guy with a progress bar, but that screen didn''t last long before the phone rebooted again and this time after the LG screen I got a screen that said "miniOS" and following that came a blue screen with the words "Factory Reset Status" and a big red number 2. So that's where I'm at now and I'm going to look up info on that to see what I do next. If you have any experience with this step please let me know.
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
Ok, this is where I was earlier today and when it got to about 94% complete and commanded the phone to reboot, the phone never came back to a state that allowed the flash tool to complete. I've seen some sites talk about having to hold the up volume button at a certain juncture around the time that it failed for me last time. Is there some trick to this?
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
ChiefIlliniwek5 said:
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
Click to expand...
Click to collapse
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
netookska05 said:
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
Click to expand...
Click to collapse
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
roirraW "edor" ehT said:
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
Click to expand...
Click to collapse
@roirraW "edor" ehT Good idea I may just do that myself.
Hello,
Unsure if it is something new or what needs to happen. Essentially when I put the phone in recovery by holding the up button when I replace the battery and it being hooked the computer, it does go into recovery mode, but when I choose the DLL and the TOT file for an earlier version of android, it wont program and just errors.
The phone is just stock and isnt rooted or anything else. Does it need to be rooted before you can even use the tools?
Any help is appreciated. My friend's phone flashed successfully with the same files and program, but mine I got just errors with Model Information Check Error .
Thanks.
Roadwarrior is the man to ask as he guided me from 6.0 back to 4.4 then up to 5.1..it can be done..
Sent from my VS985 4G using Tapatalk
Good to know! I thought I was doomed with 6.0.
The strange thing is, the older versions of android the camera worked great. 60FPS recording was awesome. Now those options are long gone and no way to restore them. It may be possible once again if infact things can be downgraded.
I gave the guide a go listed in his signature,
It stops at 4% and loses the connection. You can see the progress bar on the phone flash a few times, but that it is, stays at 0%
Wonder if something was put new on the phone which stops a bunch of these methods to change the phone's firmware.
Are you using the newer .DLL with the 10B TOT? Coming from 100% stock 35B you need to use the new one. It can be gotten from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section.
roirraW "edor" ehT said:
Are you using the newer .DLL with the 10B TOT? Coming from 100% stock 35B you need to use the new one. It can be gotten from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section.
Click to expand...
Click to collapse
I will give them a try. Hoping that this particular TOT will do it. Did notice the newer DLL as I already had it, but the TOT I have it may not of liked.
Give me a moment, downloading now and see what the verdict is.
k,
Turns out the TOT I redownloaded from the link is infact the same one I had. I tried it with the new dll, and still comes back as Protocol Not Matching, there is no ks version 00000064
This phone was shipped to me not even a week ago straight from Verizon.
doffo said:
I gave the guide a go listed in his signature,
It stops at 4% and loses the connection. You can see the progress bar on the phone flash a few times, but that it is, stays at 0%
Wonder if something was put new on the phone which stops a bunch of these methods to change the phone's firmware.
Click to expand...
Click to collapse
Just checking, what guide do you mean in my signature? I don't have a link to a TOT flashing guide in there, only KDZ. For KDZs, from 100% stock 35B and higher, you can only flash 35B or higher KDZs.
doffo said:
k,
Turns out the TOT I redownloaded from the link is infact the same one I had. I tried it with the new dll, and still comes back as Protocol Not Matching, there is no ks version 00000064
This phone was shipped to me not even a week ago straight from Verizon.
Click to expand...
Click to collapse
Look at the KS Error guide I have in my sig. Just note that by me observations, 50% of the people who follow that guide it works perfectly for them and the other half of doesn't. The other half I would break down into most (45%?) were able to then flash the TOT or at least the 10B KDZ afterwards to recover, and the remaining very few were never able to downgrade in any way at all.
These are just estimates and based only on those who reported success or failure.
Just don't blame me if you permanently brick your phone. The method worked without a hitch for myself 2-3 times and for some others. I don't think those who can't get it to work are necessarily doing anything wrong.
Ahhh. I may of made a mistake and tried to use a wrong kdz file. 35B or newer you say?
It was a 10B one, so that may be my problem. The guide I meant was the first link in your signature, I used it for the KDZ stuff.
Ok, even after trying the 35B KDZ, still no luck.. Same error comes up saying Upgrade Stopped Due to an Error on the LG Flash Tool 2014.
Here are some random numbers that show up on my phone in the little grey outlined box:
633A S0.0 AS0.0 B60
S U VS985 4G O6.0 Hrev_10
VS98547A
All that I can come up with, is that something has really changed in either software/hardware which is preventing any kind of downgrading at the moment.
doffo said:
Ok, even after trying the 35B KDZ, still no luck.. Same error comes up saying Upgrade Stopped Due to an Error on the LG Flash Tool 2014.
Here are some random numbers that show up on my phone in the little grey outlined box:
633A S0.0 AS0.0 B60
S U VS985 4G O6.0 Hrev_10
VS98547A
Click to expand...
Click to collapse
LG Flash Tool 2014 normally throws one or two errors up. Look at, I believe, post #2 of that thread with my Android File Host link, it gives some examples of errors that come up but basically just ignore all errors and 99% of the time within 5-10 minutes you'll find your phone has been flashed.
You can drag error dialogs out of your way as long as you don't click any buttons inside the dialogs.
Also, check under your battery and look for a "K" at the end of the VS985 model #, like VS985K or VS985WK. @R-T-B has strong evidence that these are a newer revision that he hasn't had any luck downgrading at all via any method, has bricked his trying several times, and has modified current recovery methods so that he could at least recover at to stock 47A Marshmallow.
I do appreciate your time for helping me troubleshoot, but unfortunately it just isn't gonna happen.
I did check the sticker underneath the battery, and its actually not that far up from the one I used to have, and its just a V985W, nothing else after that.
Again, thank you very much sir!
doffo said:
I do appreciate your time for helping me troubleshoot, but unfortunately it just isn't gonna happen.
I did check the sticker underneath the battery, and its actually not that far up from the one I used to have, and its just a V985W, nothing else after that.
Again, thank you very much sir!
Click to expand...
Click to collapse
You're welcome. Sometimes a different PC makes the difference. Using the original USB cable with a USB 2.0 port that comes directly off of your PC's motherboard, and not a USB 3.x port or through a USB hub?
roirraW "edor" ehT said:
You're welcome. Sometimes a different PC makes the difference. Using the original USB cable with a USB 2.0 port that comes directly off of your PC's motherboard, and not a USB 3.x port or through a USB hub?
Click to expand...
Click to collapse
I did try to use even my media PC. Still the same error came up and the progress stays to 0 on the phone and never moves even after leaving things for 10 minutes.
I made sure it was a USB 2.0 port and not a 3.0. I will try to brainstorm more possibilities. Luckily the phone doesn't brick as it still works.
doffo said:
I did try to use even my media PC. Still the same error came up and the progress stays to 0 on the phone and never moves even after leaving things for 10 minutes.
I made sure it was a USB 2.0 port and not a 3.0. I will try to brainstorm more possibilities. Luckily the phone doesn't brick as it still works.
Click to expand...
Click to collapse
A few things I don't think I asked (forgive me if we already addressed this earlier and I forgot - helping multiple people in multiple threads I lose track of what all we discussed):
1. You do have the latest right drivers installed, correct? I always go straight to the manufacturer's website for drivers for everything. http://www.lg.com/us/support-mobile/lg-LGVS985, Software & Firmware tab. Leave the phone disconnected from the PC, then install the latest driver and reboot the PC with the phone still disconnected. Then plug the phone into the PC and put it in Download mode, and check in Windows' Device Manager to see if the "LGE..." device shows up in the Port section.
Every time you plug a USB device into a new/different USB port (and/or have installed different/newer drivers, or I've found the first time you do this after each time you flash a KDZ or TOT because the PC sees it as a "new" device), it can take Windows 5-10 minutes to load the driver you previously installed, so if it doesn't show up right away, wait up to 10 minutes and if it doesn't show up, you've got something else to solve before trying to flash again. There's also a "LGE..." device that should show up in the Modem section - I think that's for flashing via KDZ, but TOT is what you want.
2. When you put your phone in Download mode, you did open WIndows' Device Manager to change the Port # for the "LGE..." device listed in the Port section to change it to Port # 41, right? Even if it says "In Use", I've found that it's usually still okay. After changing the port # I would go ahead and leave the phone connected while in Download mode and reboot the PC, and then try flashing the TOT.
3. When in the TOT flashing software, once you click the final button to actually flash, it's normal to need to temporarily unplug the cable from the phone, wait five seconds and then plug it back in, and that's when the TOT actually starts flashing (with a slight hesitation long enough for the PC to recognize the phone is plugged back in).
Thanks again for the troubleshooting tips,
I did make sure I downloaded the latest drivers, and let them install. Everything does show up correctly in the device manager, and I did infact set the port to 41. The software starts but then it still has the error, and it doesnt resume. I did have to unplug and plug it in to get the software to start doing its magic, but still errors out.
Scary to think maybe they done something else to the phone that prevents it. Wonder if there is a 100% 6.0 TOT to try out to see if it will flash that instead since its 6.0 or newer?
I will try again in a few days, gonna go to my old man's to visit and enjoy the weekend. Have a good day! I will report back once I come back home to try again.
I would caution you against using the "DD" method to downgrade that is available as a "last resort" mentioned above. It can brick your phone pretty hard. Not unbrickable, but close. It seems to do this to very new phones, and yours might fit the bill. If you have a "K" in your model number under the battery compartment, you are even more likely to brick it in my experience.
Sadly, these newer devices are very difficult to downgrade, if not outright impossible.
EDIT: I need to read, lol. Sorry, you can ignore the above as you are way ahead of me.
doffo said:
Thanks again for the troubleshooting tips,
Wonder if there is a 100% 6.0 TOT to try out to see if it will flash that instead since its 6.0 or newer?
I will try again in a few days, gonna go to my old man's to visit and enjoy the weekend. Have a good day! I will report back once I come back home to try again.
Click to expand...
Click to collapse
You're welcome again! Thanks for the details about what you did try and experience. No, there's no 6.0 (46A or 47A) TOT but there is a 47A KDZ.
I am by no means all-experienced with LG but from what I have seen, there's commonly only at the most one TOT for every LG model at least that's been "made available". I don't think there was ever any official manner to get - we depend on someone to leak them, and it's usually most useful to have a TOT of an earlier rather than later release since it's often the case the earlier release can be rooted and install TWRP more easily. It's probably enough of a risk or pain for someone leaking one TOT.
In the case of my LG G Pad 8.3 VK810.4G tablet, the only TOT we have is for our 22B release, which was the first KitKat one for that device - the previous stock ROM was Jellybean. It wasn't freely available until another kind user shared it after he had bought it from a Chinese website that sells things like that for about $10 an item, and he confirmed it works - I've since used that TOT with success as well.
I knew the website advertised that TOT file but I didn't know if it was trustworthy otherwise I wouldn't probably bought it for our use earlier.
I just checked the website the other day and I did again just now, and no, they don't have any new VS985 files.
They do mysteriously sell a purported 10B_04 KDZ, which is odd. The 10B TOT is 10B_03, which was the official first stock ROM of the VS985 from the factory and can receive OTAs (so long as Verizon doesn't stop sending the earlier OTAs - that could happen). The 10B KDZ we have is actually 10B_01 and can't take OTAs although it'll try to. It must have been leaked to us and would've been a test version of what became final for the VS985.
The first OTA was from 10C_03 to 11C. I don't recall the "_##" for 11C, if we ever knew since that information is only in one or two places - the filenames of KDZs/TOTs, and sometimes on LG's website for downloading the open source portion of their stock ROMs, and we don't have an 11C KDZ and I don't recall if source code for 11C was on the website.
Have a great weekend and be safe!
Good day,
I tried the 47A 6.0 KDZ file, and that one in fact did flash over with LG Tools 2014. Least we know that the drivers and program is working. I did try the downgrade again, but still errors out and loses the connection.
Strange, now the chase is on as to why it prevents anything under 47A 6.0 MM.
I tried updating to Marshmallow using the flash tool, but have run into problems. The flash didn't work and my phone won't boot normally or into download mode. I am able to get into recovery mode and have initiated a factory reset. The phone had been on the Verizon screen with the status light flashing green and blue for an hour now.
My question is how long does this process normally take? How long should I let it keep running? The phone is getting pretty hot to the touch.
Shouldn't take more than a minute if that, but not having Download mode I suspect you have a more serious problem than what a factory reset would help with.
What does your phone show up as in Windows' Device Manager in the Port section? LGE... or something else?
After the Boot Mode fails, if I press up on the phone, it is detected as:
Qualcomm HS-USB QDLoader 9008 (COM5)
If it is hanging on the Verizon boot screen, it shows up as:
LGE Mobile for VZW USB Serial Port (COM4)
Google QHSUSB_BULK 9008 mode. You'll find the special instructions to recover, including a different Windows program called BoardDiag and a special driver. You'll need the 10B TOT.
Having trouble doing any of this. I'm not able to find a 10B TOT file that doesn't give me an error when I unzip it, also not passing md5 checks.
My phone is still under warranty, perhaps I should send it in while it still is stuck on the Verizon boot screen? I've never rooted it.
Nate Wrigley said:
Having trouble doing any of this. I'm not able to find a 10B TOT file that doesn't give me an error when I unzip it, also not passing md5 checks.
My phone is still under warranty, perhaps I should send it in while it still is stuck on the Verizon boot screen? I've never rooted it.
Click to expand...
Click to collapse
Are you trying to unzip my 10B TOT 7z with a regular zip program or are you using the free 7-Zip, which is different from just regular zip? 7-zip.org is what you need.
Up to you. LG warranty service is awesome, seriously. Just FYI you might get a newer "K" variant VS985 that is impossible to downgrade and root and harder to recover from problems like these on your own than the older variants.
I'm using 7-zip. Figured out my problems and was able to get my phone working with boot mode and eventually loaded the latest KDZ successfully!
The first main clue was that I was getting corrupted zip files from multiple sources. What I originally assumed was a problem with my phone and update methods appears to have actually been a problem with either my ISP or my computer that was causing large (1.5 gigs and up) to be corrupt. I was able to download the files using a different computer on a different connection, bring them over to my main computer, and unzip them without error. They also passed md5 checks.
I believe that what happened was the original KDZ that I downloaded from LG was itself corrupt, which caused all of my issues. I was able to get my phone back into Boot Mode with the 10B TOT files and the willcracker
BoardDiag. After that, I flashed the latest KDZ using the exact same steps that originally soft-bricked my phone, but this time with a KDZ downloaded from your source and verified with a md5 check (which I wasn't able to do when downloading from LG directly).
Everything is working well now and I am very happy with the Marshmallow update.
This just goes to show the importance of md5 checks with this kind of operation. So, download files from sources that provide a md5 checksum value!
Nate Wrigley said:
I'm using 7-zip. Figured out my problems and was able to get my phone working with boot mode and eventually loaded the latest KDZ successfully!
Everything is working well now and I am very happy with the Marshmallow update.
This just goes to show the importance of md5 checks with this kind of operation. So, download files from sources that provide a md5 checksum value!
Click to expand...
Click to collapse
Awesome! Glad you figured it out and thanks for reporting back.
roirraW "edor" ehT said:
Awesome! Glad you figured it out and thanks for reporting back.
Click to expand...
Click to collapse
No problem! Hopefully my experience might help others.
Steps:
1. Turn Off Any Virus Protection Software
2. Download MP26010j_00_0316.kdz To Flash Your Phone Back To Stock
3. Install LGMobileDriver_WHQL_Ver_4.2.0.exe
4. Next Install LGUP_Store_Frame_Ver_1_14_3.msi
5. Make Sure That You Have Your Phone Connected (Take Battery Out Then Put It Back In Hold Volume Up And Connect With Micro USB) So LGUP Can Be Able To Recognize It
6. Then Double Click UPPERCUT.exe to open up LGUP Now But Only Thing Is That Uppercut will try to verify just ignore and if it doesn't open up just open lgup from desktop and its going to view phone as unknown
7. Unplug Phone But Keep LG Download Mode On And Exit LGUP
8. Open LGUP First And Then Connect Phone Which Should Recognize Phone As MP260
9. Click Upgrade, Make Sure That Bin Is Checked And Select File MP26010j_00_0316.kdz To Flash And Click Start
10. Your Done! Video Coming Soon
Links: https://mega.nz/#!EZcURRSD!NF_5MU4dJUpTknRcPMQWFVoYo4ePsGkoA0ndkkzVsmI https://mega.nz/#!dFNWFZZa!Rl3P7tJs7J51TtjcnaLwR3RHgGdRSco8NcJ9yog86J0 https://mega.nz/#!oVNSnYTB!3y9-P4t_8P-lj5sCXhFjO0R8J3j4Z_US-XCjVGysgEI https://mega.nz/#!pAUgGAwC!j5d3C8pUdQR5XMpqWBgLDu2O3tE99yWNa2nwXud3OSo
The Only Thing Im Disappointed Is That Every Time You Reboot Phone or Turn It On It Keeps Saying Lock Bootloader But Just Press The Power Button To Continue Repeating The Process Does Not Remove That Message
I Made This Tutorial For Some People That Have Trouble With Apps That Detect Root
Phone dont turn on at all
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
shaneg79 said:
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
Click to expand...
Click to collapse
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
New Optimus said:
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
Click to expand...
Click to collapse
Correct but this thread was about removing root
shaneg79 said:
Correct but this thread was about removing root
Click to expand...
Click to collapse
ah, I thought that was in the original post or implied if completely unrooting.
New Optimus said:
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
meazz1 said:
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
Click to expand...
Click to collapse
Here
kc6wke said:
Here
Click to expand...
Click to collapse
Thanks
meazz1 said:
Thanks
Click to expand...
Click to collapse
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
meazz1 said:
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
Click to expand...
Click to collapse
Not sure about TMI, use TMO North America
I figured I'd post this here to, because I am thinking about getting this phone. It's $99 at metro pcs right now, that's really hard to pass up.
In a twrp+root thread there are some that cannot get root, with the last LG firmware update, so I'm guessing this is a soft brick as apposed to a hard brick.
So, had a question.
If in the case of the like 10% of the people that do this root, the phone won't root or bricks, if I get this phone and and that happens, is it possible to flash the phone via the LG program, with a KDZ file and go back to stock like in this thread? If so I will probably buy this phone tomorrow (crosses fingers the kdz trick will work)
From looking at the videos, it looks as if the LG program is similar to the Samsung Odin program as far as flashing goes, am I correct in this?
...
Sent from my [device_name] using XDA-Developers Legacy app
I know this thread has not been active for a while. However I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
Stoner101 said:
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Click to expand...
Click to collapse
Did you find any answers to this? I have one that is bricked. It will not show up when connected to a computer at all
Virus warning from Avira in Uppercut
lg k20 plus soft bricked?
So I've searched high and low and have tried suggestion after suggestion with no avail. To start things off, I have a soft bricked LG k20 plus. Everything was working fine until the other day when I went to flash a kernel, and when the phone restarted, the screen was a dark grey/black color. I rooted the devices using massis method, removed SU and then rooted using Magisk. Like I said everything was working fine and for whatever reason I decided to try a different kernel. That's when it all went downhill. So now when I turn the phone on, the screen is still blank but it vibrates. When I've connected it to a computer, on my Mac it doesn't show up with ADB or FASTBOOT but in my device tree it comes up as LGE Android device. I borrowed my friends laptop since it runs windows, and my Mac is a dinosaur. ADB doesn't pick it up either, but in a USB hub it says the same thing, LGE Android device and lower down it comes up as TP-LINK. Now tryin to use LG Flash tools doesn't work, LGUP doesn't see my device, and when I tried to extract the KZD file, when I go to select it from the list there is no file to choose. Since I can't see anything on my screen, I can't tell if I'm in download mode, bootloader, etc, but in my device tree sometimes my phone will pop up an bootloader interface and I can use fastboot commands. When I was last able to see my screen, yes, USB debugging was on, I had a recovery, but since I can't see anything on my screen I can't seem to boot into recovery. If I could I would wipe cache and all. I think I may have read too many article and suggestions as to what to do because nothing seems to be working, and don't seem to find anything else related closely enough to my issue. Anyone have a clue as to where I should start? I'll have to give my friend back her laptop soon, and since my mac is so old, and the whole PC vs Mac feud, my computer won't be of much help. Any advice my hair strands would greatly appreciate before they rest are pulled out lol