Hey guys, fairly new user here. Prepare for rambling explanation, skip a paragraph if you don't care but the background info may be useful
Had some issues twice in the past 4 months, had to send in the phone and get a replacement (thank God for JUMP insurance) ; I used purpledrake to root my G3 shortly after it was released, it is my first Android device and I had a lot of experience with jailbreaking and unbricking iPhones so I thought I could handle it. After rooting I didn't go crazy, mostly cosmetic changes and preset apps like G3Tweakbox, I stopped google services from running because I couldn't find another way to get rid of the OTA notification. Less than a month after I did it, I was starting to have issues that I read were fixed by the OTA update, so I went online and found the process to unroot so I could update, then re-root once it was possible. Ended up getting stuck in the download mode screen and the phone wasn't even recognized by the LGFlashTool as being in DL mode. Spent a good 16 hours playing with it, gave up, hard factory reset and convinced T-Mobile that I'm a helpless college student and my phone broke. Got a new one, rooted and didn't bother. Now, stupidly, I assumed I had just made a silly mistake along the way and decided to try again o Monday, day before my birthday. Same thing happens. Send it in, got another today. I'm kinda frustrated because I really want to root it and get things looking the way I want to again, but I want to make sure I can unroot it properly if need be. I don't think I'd be interested in using custom roms just yet, maybe if I get an older device to play with and experiment. I just want root access for file management and minor visual/technical changes.
TL;DR
-Rooted using PurpleDrake : http://forum.xda-developers.com/tmobile-lg-g3/development/root-twrp-root-twrp-tmo-lg-g3-t2821005
-Phone was having issues, wanted to unroot/restore/reroot, followed this to the letter : http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
-Phone got stuck in DL mode. Sent it in, got another. I want to root again but not until someone can figure out what I did wrong or what went wrong and I know exactly what to do to be able to unroot properly.
It could be your usb is disconnecting mid flash. Just to be safe you shouldn't use that pc for flashing tots or kdzs again. On the same note if you install TWRP you can use the linked guide to unroot/reinstall/downgrade/upgrade with root via twrp. Almost no risk of hard bricking if you used supplied files and guide. The only thing that could hard brick you in the twrp method is the rpm partition but that most likely wont happen, almost can't happen unless you loose battery power at the time it flashes the rpm partition. The tot and kdz method have about 20 partitions that could hard brick you. Http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
ThePagel said:
It could be your usb is disconnecting mid flash. Just to be safe you shouldn't use that pc for flashing tots or kdzs again. On the same note if you install TWRP you can use the linked guide to unroot/reinstall/downgrade/upgrade with root via twrp. Almost no risk of hard bricking if you used supplied files and guide. The only thing that could hard brick you in the twrp method is the rpm partition but that most likely wont happen, almost can't happen unless you loose battery power at the time it flashes the rpm partition. The tot and kdz method have about 20 partitions that could hard brick you. Http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
Okay, thank you Page, I'll do some research with what you linked before I try anything again. Guess it would be a good idea to learn my way around the twrp, seems like the best custom recovery for the G3
Related
I'm posting this just because it might be helpful for others, as well as providing some warning for anyone else who might one day get into the same situation.
I was rooted and had installed TWRP on my new Gpad 7.0 V410 and everything was running just fine. I've been modding Android devices for years and thought I knew what I was doing. I didn't like the AT&T boot animation and thought I'd replace it. I found the stock animation in system/media, and replaced it (with a Nexus 7 ani) just like I'd done on previous devices.
When I rebooted, the animation started and ran. But then it hung, and rebooted. It was now stuck in a bootloop. Well, no problem, I thought, I'll just get back into recovery and restore the stock ani.
That was when I discovered how locked down the firmware is on this device. No fastboot. No standard Android bootloader. Not even, as far as I could tell, anyway of rebooting into recovery using the hardware buttons.
I could get to the factory reset screen and download mode, but neither have any way to get to recovery. ADB could not connect. The LG support tool found it, but did nothing but tell me the firmware was up to date. Lots of searching and reading turned up similar tales of woe. I began to worry that there was no way out.
Having no other ideas, I tried doing a factory reset. It ran, and lo and behold, kicked me into TWRP. From here, I confirmed that the device was wiped.
However! I had had the foresight to create a TWRP backup on my external sdcard, and that was still there. Restoring it got everything back in working order.
The moral: If you're up and running now, make an external backup. It could save your butt just as it did mine.
Amen
I'd just like to add that you can enable fastboot on this tablet for anyone who might read this thread. If you follow the method described here you'll lose download mode, but the tablet will fall back to fastboot when download mode fails. :good:
Without a kdz file released for the V410 the download mode isn't really good for anything, but fastboot gives you a fighting chance of being able to flash your way out of trouble if you brick your V410. Probably advisable to keep a backup of the laf partition just in case you need it someday.
Aha, thanks, I had seen that referenced several times, but wasn't sure where to go with it, and wanted to try less extreme methods before attempting something like that.
I've been spoiled by modding HTC and Nexus devices up to now, so this is a bit of a culture shock over here.
Edit: Decided to bite the bullet in case of future problems and nuked laf. Ah, sweet fastboot. :highfive:
HI guys, I found the low-effort rooting tutorial written by thecubed but I need a little assistance.
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
I'm at the step where you have to put the phone into download mode and it's now just sitting here doing nothing -- stuck at 0 % for the past 10 min. I'm pretty sure i have the ~4 GB image in the correct location. I took a screenshot here, so you can see. http://i.imgur.com/AiuSX33.png
After scratching my head I realized that I needed to install the LG G4 drivers on my laptop (Verizon version). So I did that, rebooted my laptop and tried it again. NOTTA. Download mode, still stuck at 0% and phone isn't doing anything at all.
Just before I started all this rooting the phone was nagging me about an "update" so of course I took the update *derp*. (bad move)
Before: V98611A. Now it's at 13B
Do I need to find an image for 13B? Is that why the download mode is stuck at zero percent? I'm very new to modding/rooting so I may have completely misunderstood the directions.
Sorry no one has responded to you.
That's never been my experience here at XDA.
I wish I could offer you some assistance, but I have no idea how to help you.
This thread managed to come across my feed on Tapatalk.
Maybe someone will come along that has your device and can help you figure it out.
I just wanted to acknowledge your post.
Buttersman,
Be more specific on where you are in the process, step #, etc.
Buttersman said:
HI guys, I found the low-effort rooting tutorial written by thecubed but I need a little assistance.
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
I'm at the step where you have to put the phone into download mode and it's now just sitting here doing nothing -- stuck at 0 % for the past 10 min. I'm pretty sure i have the ~4 GB image in the correct location. I took a screenshot here, so you can see. http://i.imgur.com/AiuSX33.png
After scratching my head I realized that I needed to install the LG G4 drivers on my laptop (Verizon version). So I did that, rebooted my laptop and tried it again. NOTTA. Download mode, still stuck at 0% and phone isn't doing anything at all.
Just before I started all this rooting the phone was nagging me about an "update" so of course I took the update *derp*. (bad move)
Before: V98611A. Now it's at 13B
Do I need to find an image for 13B? Is that why the download mode is stuck at zero percent? I'm very new to modding/rooting so I may have completely misunderstood the directions.
Click to expand...
Click to collapse
First, will the phone boot properly if you leave download mode? If so, you may want to follow these directions http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This will allow you to pull your stock system image, make a backup copy of it on your internal memory, root it, and then place it back on your phone. You could even take on of the pre-rooted system images floating around the forums and push it to you device following the last steps of the tutorial I linked, and skip the necessity of pulling and rooting your own system. With that said, I highly advise you to follow the tutorial step by step and root your own image. That will provide you a backup to flash in case something goes wrong, so you could go back to stock and it will also teach you a good deal about the process.
Finally.. since you are on 13B you are stuck on 13B. Never, never, never try to downgrade to an earlier version (11a, 12b, etc) because it will result in a bricked device. Hope this helps.
Having the same problem
Still trying to figure out the cause of it, but I think it's related to PC driver, as device manager is now showing "device cannot start (Code 10)" in download mode.
dcorrea said:
First, will the phone boot properly if you leave download mode? If so, you may want to follow these directions http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This will allow you to pull your stock system image, make a backup copy of it on your internal memory, root it, and then place it back on your phone. You could even take on of the pre-rooted system images floating around the forums and push it to you device following the last steps of the tutorial I linked, and skip the necessity of pulling and rooting your own system. With that said, I highly advise you to follow the tutorial step by step and root your own image. That will provide you a backup to flash in case something goes wrong, so you could go back to stock and it will also teach you a good deal about the process.
Finally.. since you are on 13B you are stuck on 13B. Never, never, never try to downgrade to an earlier version (11a, 12b, etc) because it will result in a bricked device. Hope this helps.
Click to expand...
Click to collapse
ck9068 said:
Still trying to figure out the cause of it, but I think it's related to PC driver, as device manager is now showing "device cannot start (Code 10)" in download mode.
Click to expand...
Click to collapse
If your using Windows you could download USBDeview http://www.nirsoft.net/utils/usb_devices_view.html. This will allow you to see all your drivers and delete all of the installed drivers for you G4. Then reinstall the proper drivers and see if it works. Another option is if you access to a Linux machine since it will natively see the LG G4 without needing to install drivers.
Has anyone rooted a model AS986? I cant seem to find any information on rooting and AS986, from what I've gathered its close the the VS986 but I don't want to brick my device.
scarda said:
Has anyone rooted a model AS986? I cant seem to find any information on rooting and AS986, from what I've gathered its close the the VS986 but I don't want to brick my device.
Click to expand...
Click to collapse
Don't do it. I have the AS986 version too and it will not work. What happens is that it will boot, then quickly for about two seconds flash a warning that says LG Security Issue or something like that, and then you will see the Verizon boot animation. Then, about a minute later it just randomly shuts off. It will do this every time you try to boot the phone. Luckily, before I did this root procedure, I created a backup image and just flashed that the same way I did the root method and my phone was back to normal. Still no root though.
SysPA1N1C said:
Don't do it. I have the AS986 version too and it will not work. What happens is that it will boot, then quickly for about two seconds flash a warning that says LG Security Issue or something like that, and then you will see the Verizon boot animation. Then, about a minute later it just randomly shuts off. It will do this every time you try to boot the phone. Luckily, before I did this root procedure, I created a backup image and just flashed that the same way I did the root method and my phone was back to normal. Still no root though.
Click to expand...
Click to collapse
Do you still have that back up? I just bricked mine being stubborn and need a backup img
SLLogan said:
Do you still have that back up? I just bricked mine being stubborn and need a backup img
Click to expand...
Click to collapse
I do still have the backup but I'm not sure if it would work or not. I'm not sure (you probably can) if you can transfer files using download mode or Send_Command Mode. The file is also 4.18GB so I'll provide a link when I do get this uploaded. But if all else fails this is what I did when one of my backups didn't work (I have the AS986 Version by the way): MAKE SURE YOU HAVE THE AS986 OR THE VS986 BEFORE DOING THIS. I'M ALSO NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE.
When you messed yours up, were you on 11a or 10b? If you were on 11a, go ahead and try this. If you were on 10b, I'm not sure what to do. Sorry.
1. You should use this guide: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
2. When you go to download the KDZ you'll notice that the AS986 KDZ isn't there. Just download the VS98611a KDZ. It's close enough.
3. Follow the guide that I gave you in step 1.
4. You should bootup like nothing happened.
Somethings may be different because you flashed a Verizon KDZ but at least you have your phone back right?
This worked for me but it may be different for you.
MAKE SURE YOU HAVE THE AS986 OR THE VS986 BEFORE DOING THIS. I'M ALSO NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE.
If you need more help or clarification, just let me know.
Hope I Helped!
Also, as a side note, stay away from the Verizon Updater. It hard bricked my G4. (I sent it in for repair already) So just resort to the safe LG Bridge Updater.
I rooted an AS986 the other day by injecting the phone's system image with root on Linux, and flashed in download mode. Did not use the Verizon image or KDZ.
shoes22 said:
I rooted an AS986 the other day by injecting the phone's system image with root on Linux, and flashed in download mode. Did not use the Verizon image or KDZ.
Click to expand...
Click to collapse
That's what I did too.
I got this phone about a year ago unlocked and it came with V20a-EUR-XX. I try and update from the update center and it says I am up to date. When I plug it into my PC and go to LG PC suite it says there is a update but it fails to install it and says to remove the USB and battery and restart and then put it back a try again. I have tried this many times and it hasn't worked. The only thing I can think of is to try and update it with .kdz but I am not sure how safe this is and would it mess up my phone. The phone isn't under warranty any more. I haven't modified the phone in any way like rooting it.
So here are my questions
How safe is it to flash a .kdz and is it likely to mess up my phone?
Do you have any other suggestions?
It is safe as updating the phone the official way. You have nothing to be afraid. Download the latest v30n marshmallow kdz file and flash away. no reason to stay on lolipop. Follow the instructions and make sure you do a full factory reset after.
Tutorial
do you have a link to a good tutorial which guides through the whole process of flashing
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
JuSkoch said:
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
Click to expand...
Click to collapse
Sounds like you might just need to reverse what you did to try to get twrp. If you have the boot partition for Arrow flash that back, if you don't have it should be pretty easy to get it from someone.
If that doesn't work can always use qfil and flash the necessary partitions to get LGUP to work, then flash or crossflash to a kdz and start again with stock.
You're in good company. I went down the same path and have become adept at repeatedly bricking and un-bricking my G8. (LM-G820QM5) I picked up 2 tidbits of info that have been helpful. The first is that my G8 ThinQ will not boot Android when the engineering abl_a.bin has been flashed on to it to enable fastboot. Sure it will fastboot, and go into EDL or download mode, but in order to boot the OS, I have to put the normal abl_a.bin and abl_b.bin back.
The second lesson I learned the hard way is that sometime LGUP fails to flash when the phone is in download mode. I was searching around XDA and came across a very helpful post from starlyn1232. They posted a command line utility that has been successful in un-bricking my G8 when LGUP failed.
I downloaded the appropriate kdz from lg-firmwares.com and the starlyn1232's utility from https://forum.xda-developers.com/t/lgup-flash-utility-based-on-lgup-1-16-cmd-and-lgup-1-17-lgup_common-dll.4112121/
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
JuSkoch said:
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
Click to expand...
Click to collapse
I would highly recommend looking at bkerler edl utilities. You can easily find his git page which has the download option for an iso linux boot which has everything installed.
It's a bit involved / complicated figuring out the command line interface, but once done you can backup everything and it will create the xml files needed to reload it.
I would suggest this for everyone but especially for those with sprint or att devices, as there is no kdz available for them.
I've recovered from various issues too many times to count with backups I've made for v40, v35, and now G8 (2 of them).
cheers
Could you pass the tutorial on how to install TWRP?
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Ashfaq Ahmed spsc said:
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Click to expand...
Click to collapse
So the rawprogram xml will be for ea lun, and it will vary by which rom you're trying to flash, it will also vary by segment starting positions for the partitions. IE, there is no generic version of it.
2nd, you don't need a patch xml, just click cancel or skip for that entry. Note; the rawprogram xml is usually generated when a backup of the binaries is made, and it will be for that specific backup.
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
MR_ZenR0 said:
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
Click to expand...
Click to collapse
Hello, I Managed to Fix it by loading my backed-up original boot_a.bin and boot_b.bin using QFIL, I have successfully passed that Verizon logo now and should be able to go from here, not that anybody asked, I just thought someone in the future might have some use out of this information here. so if you are from the future and you read this, you are welcome and good luck