G3 stuck in boot loop - Verizon LG G3

I had my G3 replaced by verizon after a hardware failure. The new one shipped with 47A, and I attempted to roll back to 10B using the TOT method, but it gave me the dreaded "there is no ks version" error. I checked and it's NOT one of the K revision phones. Anyway, I gave up on flashing it for now but decided to try rooting it with Kingroot. That failed as well. In the meantime I've received the notification to upgrade to 48A and since it kept bugging me about it, I went ahead and told it to upgrade. It failed with an error code and just sat there, unresponsive. So I pulled the battery and now it's stuck in a boot loop. It turns on, vibrates, and shows the LG splash screen. Then it reboots. So it's definitely bricked at the moment. I tried rolling back to 47A with the kdz method, which appeared to work but it's still doing the same thing. Tried the 48A kdz, same effect.
Does anyone have any suggestions or is this thing toast?

With the TOT method, were you using the newer .DLL that's extracted from the 35B KDZ? This is necessary from a completely stock 35B or higher VS985.
When you flashed the KDZ, did you choose the CSE option (you should)?
Try a wipe Cache or Factory Reset from the stock recovery, even though those shouldn't be necessary if you used the CSE option.
Like stock Factory Reset, the CSE option wipes everything including internal storage.
Lastly, although this doesn't help at the moment until you can successfully flash the TOT, flashing TOTs fixes more things than flashing KDZs. They contain more partitions than KDZs and I've witnessed the difference myself.
If you were still successfully on 47A and KingRoot worked for you, I'd direct you to my KS error thread and guide with a workaround in the General section. I wonder if in more recent versions of KingRoot if they broke their own method because the slightly older versions of KingRoot I have, have never failed to temporarily root the phone. Even then, it always required re-rooting after every reboot, and my workaround is a last resort that is merely to enable downgrading so you can still root etc the right way (SuperSU).

roirraW "edor" ehT said:
With the TOT method, were you using the newer .DLL that's extracted from the 35B KDZ? This is necessary from a completely stock 35B or higher VS985.
When you flashed the KDZ, did you choose the CSE option (you should)?
Try a wipe Cache or Factory Reset from the stock recovery, even though those shouldn't be necessary if you used the CSE option.
Like stock Factory Reset, the CSE option wipes everything including internal storage.
Lastly, although this doesn't help at the moment until you can successfully flash the TOT, flashing TOTs fixes more things than flashing KDZs. They contain more partitions than KDZs and I've witnessed the difference myself.
If you were still successfully on 47A and KingRoot worked for you, I'd direct you to my KS error thread and guide with a workaround in the General section. I wonder if in more recent versions of KingRoot if they broke their own method because the slightly older versions of KingRoot I have, have never failed to temporarily root the phone. Even then, it always required re-rooting after every reboot, and my workaround is a last resort that is merely to enable downgrading so you can still root etc the right way (SuperSU).
Click to expand...
Click to collapse
The file you're talking about for .TOT is LGUP9784.dll, right? I did download that one before attempting to apply the TOT.
For the KDZ, I did use the CSE option, but just for good measure tried wiping the cache and factory reset. Still in the same loop.
I wouldn't be surprised at all if Kingroot is broken though. I'm pretty sure that if I could successfully flash the TOT, everything would be fine. I have a replacement G3 on the way but I'm still going to try to tinker with this one for a few days before shipping it back. If the new one ships with 47A, I'll try Kingroot again and follow the directions on your thread.

pirho451 said:
The file you're talking about for .TOT is LGUP9784.dll, right? I did download that one before attempting to apply the TOT.
For the KDZ, I did use the CSE option, but just for good measure tried wiping the cache and factory reset. Still in the same loop.
I wouldn't be surprised at all if Kingroot is broken though. I'm pretty sure that if I could successfully flash the TOT, everything would be fine. I have a replacement G3 on the way but I'm still going to try to tinker with this one for a few days before shipping it back. If the new one ships with 47A, I'll try Kingroot again and follow the directions on your thread.
Click to expand...
Click to collapse
The filename of the .DLL is generic - all the .DLLs from each stock release KDZ is named the same or very similar. I have the .DLL from 35B at my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section - a link to his thread is also in my signature below.
Just to be clear, the my alternative KS Error thread is definitely a last resort. Some people have bricked their phones doing it, and those of us that it's worked everytime have no idea why it has bricked for others. From what I know, everyone who's bricked was able to either flash the 10B KDZ or 10B TOT after, or using the QHSUSB_BULK 9008 mode recovery instructions if the device shows up as QHSUSB_BULK 9008 in Device Manager, though (even though the phone's bricked, the process downgrades certain partitions which enable flashing any KDZ). TOTs are still preferred, of course. I'm just saying when you get the replacement, try the TOT method again before doing anything else.
If you do end up trying the KingRoot method and it fails to root, let me know in that thread and I'll upload the older versions of KingRoot that worked for me on 46A and 47A (but no version works on 48A last time I checked).
The 48A OTA likely failed due to KingRoot's attempt at rooting although normally if something's modified an OTA these days just refuses to install but doesn't leave a bricked device. I'd chalk it up to how invasive KingRoot is.
FYI, weirder things have happened than this - try keeping your MicroSD card ejected. For that matter, when attempting flashing the TOT, I'd eject both the MicroSD card and SIM card when you think of it. Once in 9-10 blue moons, a MicroSD card is keeping the phone from booting correctly. I doubt if this is the case but its worth a try.

Related

Help with stock upgrade from 23c to 46a

Hey XDA,
I had my LG G3 on the liquidsmooth ROM, for quite a long time, and am resetting it to factory and upgrading to 46a Marshmallow.
I have been using LG Flash Tool 2014 and got the 23c Normal Flash completed successfully, but have been unable to get the 24b KDZ to flash (LG Flash Tool 2014 keeps crashing). Tried on multiple Windows 7 computers and one windows 10 computer with compatibility for LG Flash Tool 2014 without any success.
I also tried getting the OTA updates with a verizon SIM installed and no luck there either.
I would love to find a .dlpkgfile of 24b, 35b and 46a to get my phone updated to current software.
If anyone can help, it would be much appreciated. And of course I have searched high and low for answers with no success as well.
You could root and put TWRP on and flash the 46A ROM in the Development section. I've only seen 2-3 people mention actually getting an OTA to 46A so even if you OTA to 35B it's not certain when or if you'll see the OTA to Marshmallow.
FYI it's easiest to root and put TWRP on by flashing the 10B KDZ first. Use the Stump app to root and TWRP Manager to put TWRP on. Rooting and putting TWRP on gets more complicated after 10B.
Sometimes it can take a day or two for an OTA to show up.
Even if you got the .dlpkgfile files you needed, I wasn't able to use the same method that worked to manually apply the OTA from 12B to 23C, to do the same thing to go from 23C to 24B. And since only a few people have reported getting the 46A OTA, and I'm sure they weren't rooted (because otherwise the 46A OTA wouldn't have actually worked), and without root there's no way to capture the OTA file. Once everyone starts getting the OTA, assuming this is the final official Marshmallow, then someone with root and OTA enabled would be able to capture it if they thought about it.
roirraW "edor" ehT said:
You could root and put TWRP on and flash the 46A ROM in the Development section. I've only seen 2-3 people mention actually getting an OTA to 46A so even if you OTA to 35B it's not certain when or if you'll see the OTA to Marshmallow.
FYI it's easiest to root and put TWRP on by flashing the 10B KDZ first. Use the Stump app to root and TWRP Manager to put TWRP on. Rooting and putting TWRP on gets more complicated after 10B.
Sometimes it can take a day or two for an OTA to show up.
Even if you got the .dlpkgfile files you needed, I wasn't able to use the same method that worked to manually apply the OTA from 12B to 23C, to do the same thing to go from 23C to 24B. And since only a few people have reported getting the 46A OTA, and I'm sure they weren't rooted (because otherwise the 46A OTA wouldn't have actually worked), and without root there's no way to capture the OTA file. Once everyone starts getting the OTA, assuming this is the final official Marshmallow, then someone with root and OTA enabled would be able to capture it if they thought about it.
Click to expand...
Click to collapse
I have the intention of selling the phone and having on OFFICIAL status.
j1999t said:
I have the intention of selling the phone and having on OFFICIAL status.
Click to expand...
Click to collapse
Ah. Afraid flashing the 35B KDZ and letting it OTA on its own whenever/if the OTA actually spreads to everyone would be your best bet. Assuming they'll put a Verizon SIM in it, that is. 35B works really great anyway.
roirraW "edor" ehT said:
Ah. Afraid flashing the 35B KDZ and letting it OTA on its own whenever/if the OTA actually spreads to everyone would be your best bet. Assuming they'll put a Verizon SIM in it, that is. 35B works really great anyway.
Click to expand...
Click to collapse
I tried that, the LG Flash Tool 2014 continuously crashes when getting phone information, so I am essentially stuck at the moment
j1999t said:
I tried that, the LG Flash Tool 2014 continuously crashes when getting phone information, so I am essentially stuck at the moment
Click to expand...
Click to collapse
Are you manually selecting the "Read Phone Information" button? You don't have to do that if you are, and has often crashed for me too. Just click "Start".
Otherwise, you could:
1. Root.
2. Put TWRP on.
3. Get the completely stock 35B aboot (bootloader), laf (Download mode), boot (kernel), system and recovery partition images from @bweN diorD 's stickied thread in the General section.
4. Take @xdabbeb 's 35B bootstack zip, replace the aboot and laf in there, which are 12B's, with the ones from 35B.
5. Modify the updater-script in the bootstack zip to also flash the boot, system, and recovery partitions.
6. Flash the zip in TWRP.
You should be 100% completely stock 35B with no root or custom recovery at this point.
I am not responsible if you mess up the commands in the updater-script, or any other issue and you end up bricking your phone, however.
Just sayin', you could.
FYI - I took the route of flashing the 46A rom in the developer section. I'm rooted, running xposed and my status shows "official"
If you're wanting to sell it, why not just slap 35B on there and call it a day? 46A is not current software for the masses

Can't get to marshmallow

My friend has a verizon LG G3. It is currently running 5.1.1 lollipop 35b. It was having a bunch of random reboots, we put in a new battery and the reboots stopped. The phone is working fine, except it keeps downloading the 46a 6.0 marshmallow update, but when it reboots to install, it gets to 2% and says error and reboots and I am back in 5.1.1 lollipop still. I checked software status, and it said "official" and I even used the Lg upgrade and repair assistant from verizon and chose to repair, which downloaded a 1.64 gb file (the 35b software kdz I'm pretty sure) and flashed it to the phone. I have also used lg flash tool 2014 to flash the 35b kdz. It always flashes the 35b kdz just fine, but still fails to take the marshmallow update.
I don't need root. All I'm trying to do is get from stock 35b lollipop to 46a marshmallow since it keeps failing. Since it didn't work even after successfully flashing the kdz, do I have to go all the way back to 10b and then just take a bunch of software updates ota until I get to 46a? I helped her get this phone on ebay, and it wasn't rooted when we got it, but for some reason it just won't take the update.
I understand there is no 46a kdz available right? I have been reading around about downgrading to 10b and whatnot here on xda, but I would prefer to not have to go through all that extra hassle if I don't have to. I don't need root, just need to update.
Any tips / ideas would be great! thanks.
steven_computer_guy said:
Since it didn't work even after successfully flashing the kdz, do I have to go all the way back to 10b and then just take a bunch of software updates ota until I get to 46a?
Click to expand...
Click to collapse
I doubt if that would make any difference - OTAing to 35B gets you the same thing as flashing the 35B KDZ, but this is such a weird problem, I don't know... Try it and let us know.
You could try any extra factory reset even though flushing the KDZ with the official tool does that.
The only other thing I can think of is to try taking the OTA without the Micro SD card in.
I understand there is no 46a kdz available right?
Click to expand...
Click to collapse
Correct, haven't seen it. The tool you used should've downloaded the 46A KDZ if it had been available.

How to get to 47A from new phone?

My LG G3 seems to have died tonight.
See here: http://forum.xda-developers.com/verizon-lg-g3/help/phone-dying-t3347199
I really do like this phone so I ordered a cheap refurb replacement off ebay.
What's the process to go to from whatever it shipped with to xdabbeb's 47A version found here w/TWRP?
http://forum.xda-developers.com/showthread.php?t=3304365
Bump. Can't imagine it's that hard to get from new phone to 47A rooted with TWRP, but want to do it right the first time.
Does anyone have the steps I should follow?
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
iBolski said:
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
Click to expand...
Click to collapse
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Again, there is a topic exactly for what you need in this specific forum:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-manually-downgrade-partitions-t3326775
Hope that helps! I myself haven't done this as I'm fully satisfied being on stock 47A unrooted at this point. Once I can verify that the latest CM is pretty stable (which it appears to be but there are still a few nagging issues), I'll probably eventually go to that, but I want to wait and see if LG and VZW are done with updating this phone.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
roirraW "edor" ehT said:
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
Click to expand...
Click to collapse
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?), stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
lexluthor said:
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?),
Click to expand...
Click to collapse
My Android File host link at the bottom of the first post of the other thread by @annoyingduck has both the 10B_3 TOT (don't accidentally get the 10B_01 KDZ) and the 35B .DLL you need.
stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
Click to expand...
Click to collapse
Correct.
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
Click to expand...
Click to collapse
Yes.
47a kdz just came out as another easy option if you want stock
Sent from my VS985 4G using Tapatalk
gspinelli said:
47a kdz just came out as another easy option if you want stock
Click to expand...
Click to collapse
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
lexluthor said:
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
Click to expand...
Click to collapse
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
You can temporarily root 47A with Kingroot. You have to re-root whenever you reboot, and Kingroot is very invasive. You don't want to use Kingroot. The only times I recommend it is as a temporary solution, as for my alternate way of installing TWRP which you're already aware of.
Flashing newer KDZs is more for those people who want to stay 100% stock unrooted, especially for those who don't actually use Verizon so they don't receive OTAs.
roirraW "edor" ehT said:
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
Click to expand...
Click to collapse
Yes xdabbab's 47A is the way to go for me.
Just got the new phone and its on 35B. I'm trying to TOT to 10B with the 35B DLL. I did the COM41 in device manager. I've got the phone in download mode. I'm running the LG Flash tool as admin in Windows 10. I load the 2 files and click the start arrow. It goes through some things where it says BIN CRC check or something like than and then it just sits and says READY!! in yellow, but nothing ever happens.
Am I doing something wrong?
EDIT: Unlplugged USB and plugged it back in and it's going now. Stand by, could maybe use some more help getting through this
Optimizing apps on 47A (hopefully). I'm sure finding my Titanium folder on the external drive will be a pain as always, but hopefully smooth sailing from there.
The process worked great. East to TOT, install stump root, then TWRP and then flashed 35b bootstack and 47a xdabbeb with some wiping data/caches in between.
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Back up and running on my replacement phone today. The ebay listing said it was B+ condition. Screen is in great shape, some scraping on the sides, but I don't care about that. I used my back cover that I had put an NFC sticker on when I got the original phone. All working great so far.
Thanks for the help here.
Thanks!
David
lexluthor said:
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Thanks for the help here.
Thanks!
David
Click to expand...
Click to collapse
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
roirraW "edor" ehT said:
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
Click to expand...
Click to collapse
I've never gotten LG Backup to work right for me. Never seems to restore nearly everything or get errors when backing up. Not worth looking into it more as I don't start fresh much.
I was using the phone much of the time TiBU was working, so that didn't help, but still slow going even if I plugged it in and let it sit. It missed about 30 apps the first time around that I did in a 2nd pass. Didn't get hung too much in the main batch, at least. And if It does hang, no need to reboot. Just FC TiBU and then start it back up and leave the hung app off to do as a one by at the end.
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
lexluthor said:
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
Click to expand...
Click to collapse
It's a common problem on this phone. There's no particular known reason why it happens, nor any solution - there's only been a ton of speculation without any strong evidence other than a thread I had made about this subject, during which I made a detailed test of rebooting the phone about 140 times under different circumstances (10 times in a row in each specific circumstance). I'm fairly certain I would have to at minimum do about 1500 more reboots in various circumstances to only possibly get closer to narrowing down the problem.
Some people will tell you they think it's caused by a particular (35B) bootstack. I don't believe it because I had 70 reboots in a row while on the 35B bootstack without having the problem during part of my testing.
I also have had the problem before 35B even came out. I haven't had the problem happen at all in the past couple of months - since the last time I had TOT'd back to 10B (and I've done various KDZ flashes since then when testing things for myself and for others).
Rebooting
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo. I'm on Jasmine 9.1
Circlesqr said:
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo.
Click to expand...
Click to collapse
Definitely not my issue. My phone was rebooting in download mode without even a SIM or memory card installed.

Root for LG G3 VS985 Android 6.0 47A

I found this one click root tutorial for my phone on ibtimes website (can't post the link because I'm a new member) but it's for Lollipop. Will it work for Marshmallow 6.0 (software version 47A)? I'm afraid it will brick my phone (again - my last phone was a G2 that I bricked from enabling 16-bit transparency to improve performance)
If it doesn't, how can I root it and install custom recovery? I can't find a root for this phone on Marshmallow, and I don't know how to roll back to Lollipop.
I am willing to factory reset if I need to.
Hi! Google for the TOT method, in order to flash the 10B TOT from a Windows PC. You can find the 10B TOT and the .DLL that's extracted from the 35B KDZ at my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first thread in my signature below. The thread itself is for the KDZ method which is why I say you'll have to Google for the TOT instructions. Even if you find TOT instructions for another device, the method should be identical or very similar, just using a different TOT file and .DLL than the ones they specify.
In case you're wondering, from stock unrooted 35B or higher you can only flash the 35B or higher KDZ.
Once you're on 10B, root using the Stump app (again, Google for it), then install TWRP Manager from the Play Store and use that to flash the latest TWRP. Reboot to TWRP, then if you want to be back on stock but rooted and optionally debloated 47A Marshmallow, flash the 35B Bootstack that you can get from @xdabbeb 's VS985 v2.0 thread in the Development section, then flash his stock 47A firmware also in that section, and any optional debloat zips from the third post of the 47A firmware thread or my signature below, and Xposed if you want, etc.
Rooting gets more difficult after 10B, and putting TWRP gets harder after 12B.
Flashing the 10B TOT will wipe all your user apps, user and system data, and your internal storage and put it back to 100% stock KitKat.
roirraW "edor" ehT said:
Hi! Google for the TOT method, in order to flash the 10B TOT from a Windows PC. You can find the 10B TOT and the .DLL that's extracted from the 35B KDZ at my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first thread in my signature below. The thread itself is for the KDZ method which is why I say you'll have to Google for the TOT instructions. Even if you find TOT instructions for another device, the method should be identical or very similar, just using a different TOT file and .DLL than the ones they specify.
In case you're wondering, from stock unrooted 35B or higher you can only flash the 35B or higher KDZ.
Once you're on 10B, root using the Stump app (again, Google for it), then install TWRP Manager from the Play Store and use that to flash the latest TWRP. Reboot to TWRP, then if you want to be back on stock but rooted and optionally debloated 47A Marshmallow, flash the 35B Bootstack that you can get from @xdabbeb 's VS985 v2.0 thread in the Development section, then flash his stock 47A firmware also in that section, and any optional debloat zips from the third post of the 47A firmware thread or my signature below, and Xposed if you want, etc.
Rooting gets more difficult after 10B, and putting TWRP gets harder after 12B.
Flashing the 10B TOT will wipe all your user apps, user and system data, and your internal storage and put it back to 100% stock KitKat.
Click to expand...
Click to collapse
Thanks. I'll try to do this next time I have WiFi access.
Dangers in downgrading newer G3?
Though I have successfully done in the past, the last time I tried to flash my G3 down to 10b, the IMEI got reset to all zeros, and even after finding a tool to reset the IMEI, it would never reliably connect to the network. I have no idea what I did differently this time.
I was fortunate to be able to get the phone replaced, but I'm hesitant to flash it again just for the few things I want root for.
I've seen reports on other forums of others having problems with downgrading "newer G3s."
Does anyone here have any knowledge of such problems?
I wish Kingroot wasn't apparently at war with the SuperSu-Me folks.
Kos1 said:
Though I have successfully done in the past, the last time I tried to flash my G3 down to 10b, the IMEI got reset to all zeros, and even after finding a tool to reset the IMEI, it would never reliably connect to the network. I have no idea what I did differently this time.
I was fortunate to be able to get the phone replaced, but I'm hesitant to flash it again just for the few things I want root for.
I've seen reports on other forums of others having problems with downgrading "newer G3s."
Does anyone here have any knowledge of such problems?
I wish Kingroot wasn't apparently at war with the SuperSu-Me folks.
Click to expand...
Click to collapse
Thanks for the warning. Luckily I was hesitant to do that and I decided not to root my phone. However, yesterday my screen started messing up - it occasionally flickers off and freezes and fades out, and usually if I turn the screen off and put a little pressure on the back for the phone, it works again for a couple hours. I don't know how long my screen will last, if this means it's dying for good. I found a post about it on reddit where a bunch of people with the VS985 had the same problem, and after sending it in, replacing the screen and connections didn't work, so they thought it was an issue with the main board. So I think I'm going to get a new phone, and then I'll be able to mess around with this without worrying about breaking it since I got a new phone.
But I don't want to get another G3 because I don't want to get this problem again. I only have about $340 to spend on a new phone, and am thinking about getting a refurbished G4 or Nexus phone.
67129067
millicow said:
I found this one click root tutorial for my phone on ibtimes website (can't post the link because I'm a new member) but it's for Lollipop. Will it work for Marshmallow 6.0 (software version 47A)? I'm afraid it will brick my phone (again - my last phone was a G2 that I bricked from enabling 16-bit transparency to improve performance)
If it doesn't, how can I root it and install custom recovery? I can't find a root for this phone on Marshmallow, and I don't know how to roll back to Lollipop.
I am willing to factory reset if I need to.
Click to expand...
Click to collapse
good

VS985 LG Verizon G3 - Uknown Baseband

I don't have a backup because I am an idiot. I had a null IMEI and an unknown baseband after going to XDABBEB's 3.1.1, I tried many things including going back to 10B, 35B boostack, 47A xdabbeb "stock", nothing working. I ended up using QPST to fix my IMEI but I still have an unknown baseband. Any advice that will help would be greatly appreciated.
From @xdabbeb 's ROM, at least the last few versions, I've had to first flash any KDZ (probably preferred to flash the 10B_01 KDZ) before I could flash the 10B_03 TOT. I suspect the no IMEI/baseband problem is merely related to some kind of mismatch between all the partitions that are currently on your phone and that being able to successfully flash the TOT will fix it. Once I found that if I flash a KDZ before trying to TOT from his ROM, that TOT worked 100% every time, I never had another problem.
Don't touch anything having to do with your IMEI again until you are able to flash the TOT, and you may already know but just in case you don't, even once you successfully flash a KDZ, definitely still flash the TOT as TOTs can fix weird issues that KDZs can't.
Good luck and let me know if this helps!
roirraW "edor" ehT said:
From @xdabbeb 's ROM, at least the last few versions, I've had to first flash any KDZ (probably preferred to flash the 10B_01 KDZ) before I could flash the 10B_03 TOT. I suspect the no IMEI/baseband problem is merely related to some kind of mismatch between all the partitions that are currently on your phone and that being able to successfully flash the TOT will fix it. Once I found that if I flash a KDZ before trying to TOT from his ROM, that TOT worked 100% every time, I never had another problem.
Don't touch anything having to do with your IMEI again until you are able to flash the TOT, and you may already know but just in case you don't, even once you successfully flash a KDZ, definitely still flash the TOT as TOTs can fix weird issues that KDZs can't.
Good luck and let me know if this helps!
Click to expand...
Click to collapse
I flashed 10B_01 KDZ with LG Flash 2014
Then I flashed 10B_3 TOT with LG Flash
Then I stumped, rebooted, supersu, rebooted, twrp recovery reboot
Then I flashed 35B with twrp and when I did I lost my baseband, and cannot get data service.
I flashed 3.1.1 even though I had unkown baseband, still have unknown baseband and also have "com.android.phone" has stopped errors.
Helltech said:
I flashed 10B_01 KDZ with LG Flash 2014
Then I flashed 10B_3 TOT with LG Flash
Then I stumped, rebooted, supersu, rebooted, twrp recovery reboot
Then I flashed 35B with twrp and when I did I lost my baseband, and cannot get data service.
I flashed 3.1.1 even though I had unkown baseband, still have unknown baseband and also have "com.android.phone" has stopped errors.
Click to expand...
Click to collapse
I don't think the 35B Bootstack works at all on the 10B ROM; that's why you're having problems at least without flashing a 35B+ ROM before booting. The 24B and 12B Bootstacks are available, and 12B would work on the 10B ROM. I wouldn't flash the 35B Bootstack and then boot the 10B ROM before flashing @xdabbeb 's 3.1.1 ROM.
Did you do a factory reset/wipe of data, cache and Dalvik/ART before flashing 3.1.1? If not, did you try one after flashing the ROM? Did you check the MD5 hash of any of the files that you're flashing? Did you try wiping both internal storage and ejecting the MicroSD card, and do the factory reset and try booting without the SD card in?
roirraW "edor" ehT said:
From @xdabbeb 's ROM, at least the last few versions, I've had to first flash any KDZ (probably preferred to flash the 10B_01 KDZ) before I could flash the 10B_03 TOT. I suspect the no IMEI/baseband problem is merely related to some kind of mismatch between all the partitions that are currently on your phone and that being able to successfully flash the TOT will fix it. Once I found that if I flash a KDZ before trying to TOT from his ROM, that TOT worked 100% every time, I never had another problem.
Don't touch anything having to do with your IMEI again until you are able to flash the TOT, and you may already know but just in case you don't, even once you successfully flash a KDZ, definitely still flash the TOT as TOTs can fix weird issues that KDZs can't.
Good luck and let me know if this helps!
Click to expand...
Click to collapse
roirraW "edor" ehT said:
I don't think the 35B Bootstack works at all on the 10B ROM; that's why you're having problems at least without flashing a 35B+ ROM before booting. The 24B and 12B Bootstacks are available, and 12B would work on the 10B ROM. I wouldn't flash the 35B Bootstack and then boot the 10B ROM before flashing @xdabbeb 's 3.1.1 ROM.
Did you do a factory reset/wipe of data, cache and Dalvik/ART before flashing 3.1.1? If not, did you try one after flashing the ROM? Did you check the MD5 hash of any of the files that you're flashing? Did you try wiping both internal storage and ejecting the MicroSD card, and do the factory reset and try booting without the SD card in?
Click to expand...
Click to collapse
I don't have an SD with this phone.
So what should my very next step be after 10B_3 TOT? To Stump>SuperSU>TWRP> flash 12B and then either 47A or 3.1.1? I thought I thought couldn't flash them unless I was on 35B.
Helltech said:
I don't have an SD with this phone.
So what should my very next step be after 10B_3 TOT? To Stump>SuperSU>TWRP> flash 12B and then either 47A or 3.1.1? I thought I thought couldn't flash them unless I was on 35B.
Click to expand...
Click to collapse
Absolutely, flash the 35B Bootstack if you're going to flash a 35B or higher ROM right after it, just know that if you flash the 35B Bootstack on top of the 10B ROM and you boot it, it's expected that the 10B ROM won't see a baseband because of the incorrect Bootstack, besides which, I just wouldn't boot 10B before flashing the 35B+ ROM.
Personally, I always told people to flashed the bootstack after the ROM, but there was a reason: not because of @xdabbeb 's ROM, and in his ROM's case it should be the same whether flashed before or after - I just always made it a rule to flash after and to tell people to do that because two other ROMs not by @xdabbeb , if you flashed the ROM after the bootstack you'd only get a black screen afterwards and you'd at minimum have to TOT or you might have to use the QHSUSB_BULK recovery method.
It certainly won't hurt to try flashing the bootstack after the ROM instead of before in this case, either. I don't expect it to make a difference. Did you check the MD5 hashes of everything you're flashing to make sure your downloads aren't corrupt?
roirraW "edor" ehT said:
Absolutely, flash the 35B Bootstack if you're going to flash a 35B or higher ROM right after it, just know that if you flash the 35B Bootstack on top of the 10B ROM and you boot it, it's expected that the 10B ROM won't see a baseband because of the incorrect Bootstack, besides which, I just wouldn't boot 10B before flashing the 35B+ ROM.
Personally, I always told people to flashed the bootstack after the ROM, but there was a reason: not because of @xdabbeb 's ROM, and in his ROM's case it should be the same whether flashed before or after - I just always made it a rule to flash after and to tell people to do that because two other ROMs not by @xdabbeb , if you flashed the ROM after the bootstack you'd only get a black screen afterwards and you'd at minimum have to TOT or you might have to use the QHSUSB_BULK recovery method.
It certainly won't hurt to try flashing the bootstack after the ROM instead of before in this case, either. I don't expect it to make a difference. Did you check the MD5 hashes of everything you're flashing to make sure your downloads aren't corrupt?
Click to expand...
Click to collapse
MD5 hashes are fine. I flashed 3.1.1 after 35B without booting into the phone at all and still had the baseband and com.android.phone errors. At which point am I supposed to wipe data?
Helltech said:
MD5 hashes are fine. I flashed 3.1.1 after 35B without booting into the phone at all and still had the baseband and com.android.phone errors. At which point am I supposed to wipe data?
Click to expand...
Click to collapse
I would try the factory reset, but I would only expect that to possibly help with the FCs; I don't know how that could help with the baseband.
I have no idea what the TWRP situation is on the VS985 anymore, so I don't know if there's a chance a recent version could be borking things when flashing. You could always try going back to an older version.
If it were my phone, I would next:
Flash the 10B TOT (flashing the 10B KDZ first if necessary)
Boot the phone, see if everything seems to work including the baseband.
If so, flash the 35B KDZ (CSE option to wipe all). Verify if everything works again.
If it does work under fully stock 35B and yet won't work after Stump, etc, I don't know what else to suggest. There's a guy on here who I believe goes by @R-T-B who at least used to do software work on people's VS985s. You could always see if he has any ideas or if you would want him to see if he can get anything to work on it.
roirraW "edor" ehT said:
I would try the factory reset, but I would only expect that to possibly help with the FCs; I don't know how that could help with the baseband.
I have no idea what the TWRP situation is on the VS985 anymore, so I don't know if there's a chance a recent version could be borking things when flashing. You could always try going back to an older version.
If it were my phone, I would next:
Flash the 10B TOT (flashing the 10B KDZ first if necessary)
Boot the phone, see if everything seems to work including the baseband.
If so, flash the 35B KDZ (CSE option to wipe all). Verify if everything works again.
If it does work under fully stock 35B and yet won't work after Stump, etc, I don't know what else to suggest. There's a guy on here who I believe goes by @R-T-B who at least used to do software work on people's VS985s. You could always see if he has any ideas or if you would want him to see if he can get anything to work on it.
Click to expand...
Click to collapse
Well everything worked, I just redid what you told me again in the previous post and I got 3.1.1 working with baseband, and no com.android.phone errors, but my IMEI is null again. Is there anyway to permanently fix this without going back to 10B again.
Helltech said:
Well everything worked, I just redid what you told me again in the previous post and I got 3.1.1 working with baseband, and no com.android.phone errors, but my IMEI is null again. Is there anyway to permanently fix this without going back to 10B again.
Click to expand...
Click to collapse
Do you have an IMEI when you boot up 10B after flashing the TOT? Either way, though, I've never had to fix an IMEI problem so I can't help there. I'm glad you're having some progress.
roirraW "edor" ehT said:
Do you have an IMEI when you boot up 10B after flashing the TOT? Either way, though, I've never had to fix an IMEI problem so I can't help there. I'm glad you're having some progress.
Click to expand...
Click to collapse
Not sure about after flashing, I did have it after flashing KDZ though.
roirraW "edor" ehT said:
Do you have an IMEI when you boot up 10B after flashing the TOT? Either way, though, I've never had to fix an IMEI problem so I can't help there. I'm glad you're having some progress.
Click to expand...
Click to collapse
IMEI is now fine though after getting to 3.1.1 however when I get to 3.1.1 I lose root now. Sigh. Not sure what I'm doing wrong.
Helltech said:
IMEI is now fine though after getting to 3.1.1 however when I get to 3.1.1 I lose root now. Sigh. Not sure what I'm doing wrong.
Click to expand...
Click to collapse
Try dirty flashing the ROM. Have you checked out TWRP's log after flashing?
roirraW "edor" ehT said:
Try dirty flashing the ROM. Have you checked out TWRP's log after flashing?
Click to expand...
Click to collapse
The dirty flashes were what was causing my com.android.phone error. However I will try again. Not sure why but I lost TWRP recovery and now just have stock official system recovery? Ugh... not sure why this went so smoothly before, just followed your guide and everything worked, same phone.
EDIT -> So I dirty flashed 3.1.1 over stock 10_3, got the com.android.phone errors. So I clean flashed 3.1.1 over that 3.1.1 and I lost the com.android.phone errors, but also lost root. At a loss of what to do to retain root at this point.
Helltech said:
The dirty flashes were what was causing my com.android.phone error. However I will try again. Not sure why but I lost TWRP recovery and now just have stock official system recovery? Ugh... not sure why this went so smoothly before, just followed your guide and everything worked, same phone.
EDIT -> So I dirty flashed 3.1.1 over stock 10_3, got the com.android.phone errors. So I clean flashed 3.1.1 over that 3.1.1 and I lost the com.android.phone errors, but also lost root. At a loss of what to do to retain root at this point.
Click to expand...
Click to collapse
When you clean flashed 3.1.1 and lost root, did you do anything else after flashing 3.1.1 and booting? Wipe anything? I just remembered that performing some kinds of wipes after 3.1.1 will lose root. Sorry, forgot, it had to do with a change in how SuperSU works on Lollipop.
To maintain root, flash the Mr.bump.zip following supersu.zip install to keep your bootloader unlocked.
Through my own experience, I would suggest rooting any M ROM that does not have root baked in with
supersu.zip (or whatever the dev suggests) and avoid the supersu app altogether. Gotta bump that bootloader though.
I lost phone identity recently as well (what's plaguing our phones?) I fixed my imei with the imei repair tool for Qualcomm devices. Entered imei into meid field after a failed attempt through the imei field. That got it working again. While the Sim wasn't reading, I had known baseband. Now The Sim is recognized, the meid (has both letters and numbers (hexadecimal)) and imei are both correct, but baseband is unknown, yet the g3 has complete functionality.
roirraW "edor" ehT said:
I would try the factory reset, but I would only expect that to possibly help with the FCs; I don't know how that could help with the baseband.
I have no idea what the TWRP situation is on the VS985 anymore, so I don't know if there's a chance a recent version could be borking things when flashing. You could always try going back to an older version.
If it were my phone, I would next:
Flash the 10B TOT (flashing the 10B KDZ first if necessary)
Boot the phone, see if everything seems to work including the baseband.
If so, flash the 35B KDZ (CSE option to wipe all). Verify if everything works again.
If it does work under fully stock 35B and yet won't work after Stump, etc, I don't know what else to suggest. There's a guy on here who I believe goes by @R-T-B who at least used to do software work on people's VS985s. You could always see if he has any ideas or if you would want him to see if he can get anything to work on it.
Click to expand...
Click to collapse
Hello.
I used to offer this yes, and I really appreciate all the references you provided me on this forum, don't get me wrong... I did indeed debrick many phones and had many happy customers. Unfortunately I moved recently and most of my debricking hardware was thrown out or sold when I did that. As such, I really can't offer the service anymore.
Plus, I'm on an LG V20 now. Can't exactly say I'm up to speed with firmware anymore.
Best of luck all the same to all you G3 people out there. The G3 was and is a great phone in many aspects, and I still look on it fondly.
PS: I know this is sort of a necrobump, but I did not feel it justified it's own thread.
R-T-B said:
Hello.
I used to offer this yes, and I really appreciate all the references you provided me on this forum, don't get me wrong... I did indeed debrick many phones and had many happy customers. Unfortunately I moved recently and most of my debricking hardware was thrown out or sold when I did that. As such, I really can't offer the service anymore.
Plus, I'm on an LG V20 now. Can't exactly say I'm up to speed with firmware anymore.
Best of luck all the same to all you G3 people out there. The G3 was and is a great phone in many aspects, and I still look on it fondly.
PS: I know this is sort of a necrobump, but I did not feel it justified it's own thread.
Click to expand...
Click to collapse
The best of luck to you too! I'll try to remember not to throw your name out there anymore. LOL! Thanks for letting us know.

Categories

Resources