Long story short, I updated to ZVF (thats what it said I was on when I tried to flash back to stock with flashtool) a while back, I have been running resurrection remix for a while now and everything was fine. Then about three days ago I got stuck in a boot loop out of nowhere and my phone wouldn't go on to recovery mode, it would give me the message and ask if I was sure like it normally would do when booting in to recovery, but then it would just go back to bootlooping. So I attempted to flash back to stock ZVA, because ZVA was the most recent firmware I could find in TOT format, but alas, the flash failed, assumingly because it's not the firmware version I was previously running. So now I'm stuck in a bootloop again, and I really don't know where to go from here. Is there a ZVF TOT that I can flash? Is there anything else I can do to fix this? Is the phone totally screwed?? Any answer/advice would be greatly appreciated.
Have you found a solution? Did you try any other TOT files? or maybe KDZ method?
poog said:
Have you found a solution? Did you try any other TOT files? or maybe KDZ method?
Click to expand...
Click to collapse
Nothing yet. I've tried ZVA and ZV8, neither worked. I've never tried the kdz method, how would I do this?
golpeen420 said:
Nothing yet. I've tried ZVA and ZV8, neither worked. I've never tried the kdz method, how would I do this?
Click to expand...
Click to collapse
First try using the "Generic LG G3 DLL" here https://forum.xda-developers.com/sp...de-how-to-restore-sprint-lg-g3-ls990-t2852042
...............instead of the other DLL for for the sprint LG G3.....................with FLASHTOOL and whatever TOT file.
Related
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
after removing root, you need to flash back to stock to get it working again with the exploit.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Jimi Mack said:
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Click to expand...
Click to collapse
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Andorew said:
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Click to expand...
Click to collapse
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Jimi Mack said:
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Click to expand...
Click to collapse
Yes, I have 10b, but it fails to update to 11c
Andorew said:
Yes, I have 10b, but it fails to update to 11c
Click to expand...
Click to collapse
Did you disable anything ?
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
trent999 said:
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
How can I flash a newer version such as 11c(Or upcoming Android L)? Without .tot
You can't. You kdz back to keep from getting the update so you can root and bump and flash roms. You tot to get to the right version to take the update
Once L is released OTA, our noble developers will make it possible for us who have root and recovery to flash the OTA components safely, retaining root and custom recovery.
We hope.
Why would you want to take the current locked OTA?
If you TOT you can still root. Before you take the update.
Trying to do the same I have always done. Trying to downgrade from 23c. I use the tot file back to 10b then tried to use stump. Says device not supported but has always worked before. Any ideas why it doesnt work now? It said there was an error at the end of reflash but still booted up. Should I redo the flash again and then try?
blueis300 said:
Trying to do the same I have always done. Trying to downgrade from 23c. I use the tot file back to 10b then tried to use stump. Says device not supported but has always worked before. Any ideas why it doesnt work now? It said there was an error at the end of reflash but still booted up. Should I redo the flash again and then try?
Click to expand...
Click to collapse
Why make it difficult? Ues the one-click root method now. It works on anything including 23C:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
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 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.
Hey XDA, I'm having a bit of a problem. I got my G5 just recently and I wanted to go ahead and unlock the bootloader so I could install some custom ROMS (I'm not a fan of LG's ux), but I ran into a sticky situation. I was trying to flash the TOT file for rooting h830 with LGUP when I found out that it doesn't work on Nougat. I tried to cancel it but now I'm just stuck in firmware update at 0%. The code at the bottom says 633A B50. I can get into fastboot but I can't really go anywhere from there and I've gotten to stock recovery but all it does is factory reset and boot me straight back to firmware update. I downloaded the stock nougat kdz file but LGUP won't flash it; sometimes it says invalid, other times it gives me the error code 0x2000 CEFS::Initialize. This is a brand new (kind of expensive) phone and I can't send it to LG for repairs since I unlocked the bootloader and probably voided warranty so I'm really desperate for a solution. Can anyone help me out?
shadowcreed159 said:
Hey XDA, I'm having a bit of a problem. I got my G5 just recently and I wanted to go ahead and unlock the bootloader so I could install some custom ROMS (I'm not a fan of LG's ux), but I ran into a sticky situation. I was trying to flash the TOT file for rooting h830 with LGUP when I found out that it doesn't work on Nougat. I tried to cancel it but now I'm just stuck in firmware update at 0%. The code at the bottom says 633A B50. I can get into fastboot but I can't really go anywhere from there and I've gotten to stock recovery but all it does is factory reset and boot me straight back to firmware update. I downloaded the stock nougat kdz file but LGUP won't flash it; sometimes it says invalid, other times it gives me the error code 0x2000 CEFS::Initialize. This is a brand new (kind of expensive) phone and I can't send it to LG for repairs since I unlocked the bootloader and probably voided warranty so I'm really desperate for a solution. Can anyone help me out?
Click to expand...
Click to collapse
Was your phone on the 20a version before you tried flashing the 10d root tot file and did you actually cancel the process within LGUP while it was flashing the phone?
Another user had a similar problem but he flashed the 20a version before he accidentally flashed the 10d root tot and he fixed it by just flashing the stock 20a within LGUP.
Assuming you can still get into download mode you should be able to fix your device.
Try flashing this kdz uploaded by @autoprime
downloads.codefi.re/autoprime/LG/LG_G5/H830/H83020a/H83020a_00_1107.kdz
If flashing is successful factory reset your phone from the stock recovery after.
Thanks, that worked but I had to do a little tinkering before it did. LGUP wouldn't flash it because it kept saying invalid and some other random reasons but I found a program called uppercut that allowed it to flash. I was able to get back to stock and then I used the dirtycow exploit to flash TWRP. All's good now on XenonHD.
so I thought I had a grasp on the unlocking rooting myself. I was getting the error in lgup where it doesn't recognize my device at all. I unlocked the oem and it did its own flash afterwards then I had to go and reset unknown sources. then I tried to do the lg up flash assuming all I needed from my 20i was the v10d arb01 may 23, I picked the upgrade and in the middle of it it failed. then it rolled back. so I tried it several more times in lgup and it failed so I tried the arb 01 march 4 with full root and it failed.
Edit: okay lI found uppercut and it reconnected me to LGUP then I used the flashable 20a file and that patched me right up. But no root, I can do a 1 click now I guess but what about a flashable twrp or can I just install it like the old cwm or x-parts? where to now? do I try the 10d one with root? I'm really tired of looking and blindly downloading tot and kdz files hoping they work? My main goal is to slap RR remix on this for anyone that would give me a hand