okay, i want to go back to stock (turning in my G3 Friday for repairs.) im currently on Eclipse rom. now, i have the lg flash tool downloaded, and the 10b and 12b KDZ files downloaded, and am currently backing up my internal storage to my PC.
that being said, i do have TWRP and i am rooted. do i still just follow this: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140 ?
im actually going to try the .tot method. i read that otas wont work with the 10b kdz..i got the 12b kdz.. gonna run it instead of .tot to 10b
will that put the stock recovery and stuff back on it? im assuming so.
mods, you can delete this if you wish..
zakkyzombie said:
okay, i want to go back to stock (turning in my G3 Friday for repairs.) im currently on Eclipse rom. now, i have the lg flash tool downloaded, and the 10b and 12b KDZ files downloaded, and am currently backing up my internal storage to my PC.
that being said, i do have TWRP and i am rooted. do i still just follow this: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140 ?
im actually going to try the .tot method. i read that otas wont work with the 10b kdz..i got the 12b kdz.. gonna run it instead of .tot to 10b
will that put the stock recovery and stuff back on it? im assuming so.
mods, you can delete this if you wish..
Click to expand...
Click to collapse
Hi! Yes, that's exactly what you still need to do. All you need is the 12B KDZ. 10B is only needed when you're going to root/re-root.
If you use the 12B KDZ you don't have to bother with OTAs. Personally, and not to dissuade you entirely - it's up to you, but the TOT method is VERY finicky. Much more so than flashing KDZs in my experience, but that's just my two cents. I've never had a problem flashing KDZs.
Yes, any KDZ will put the phone completely back to stock including wiping internal storage as long as you choose "CSE" when it gives you the choice between that and "Normal". CSE *is* what you want. "Normal" is like a dirty flash, FYI and can come in handy in different situations.
Good luck!
Related
i got my g3 in mail today. looks a great phone in hand. just make sure this is the proper thing i m going to do to flash some rom. current software build is 11c. it needs to downgrade to 10b with kdz method. stump root then. install twrp recovery with flashify. then i could pick any rom i like to flash? is there anything wrong or i missed? anything i need to take care during flashing rom?
thank you for the advice.
Sounds about right.
Unless you want to run plain stock for some reason, then don't use the kdz to downgrade. I downgraded using the stock 10b, rooted and then took each OTA making sure SU had keep root checked. I have a rooted stock 11C nandroid just in case I want it. Just a thought.
Schaweet said:
Unless you want to run plain stock for some reason, then don't use the kdz to downgrade. I downgraded using the stock 10b, rooted and then took each OTA making sure SU had keep root checked. I have a rooted stock 11C nandroid just in case I want it. Just a thought.
Click to expand...
Click to collapse
downgrading with the kdz method you'd still be able to update by flashing the stock rooted 11c & 12b and the appropriate modem.
BladeRunner said:
downgrading with the kdz method you'd still be able to update by flashing the stock rooted 11c & 12b and the appropriate modem.
Click to expand...
Click to collapse
Sure but you wouldn't be able to take an OTA which some people like to do. Plus, can you get the VoLTE update on the VZW model? Not sure.
Anyway, to not have to worry about flashing separate modems, it's not really a huge deal to downgrade with the stock files.
Either way works which is why Android rocks. Options!
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
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.
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
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.