Related
I got an LG G3 that came packaged with 35B (5.1.1), and nothing seemed to be working to get TWRP installed. I couldn't use LG Flash Tools to downgrade using the "TOT" method, because it'd stop with an "no ks version" error. I finally found something that works, and I'm now running AICP (nice ROM) with TWRP installed!
The trick is to follow these instructions (make sure you use VS985 components for our Verizon LG G3s, not D855):
http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977
Overwrite aboot.img (12B version) & recovery (TWRP image) using dd commands via an adb shell, after rooting with KingRoot, while Android is running. I then used adb commands to reboot into recovery, and volia! I was in! I had AICP on my internal card, and the 12b bootstack, which I flashed in that order.
After seeing AICP successfully boot, I went back and flashed the 35B bootstack. Success!
Stock images (aboot 12B etc.): http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Bootstacks: http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
KingRoot: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Great news for you and others. Thanks for sharing!
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
fast69mopar said:
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
Click to expand...
Click to collapse
Weird... this is what I did (nothing more):
1) Pick a ROM I wanted to use. I went with AICP nightly for VS985 (MM 6.0.1). Put that ROM zip to be flashed by TWRP on your internal memory.
2) Put the 12B bootstack on internal memory.
3) Put the 12B aboot.img & latest TWRP img on internal memory.
4) Root with KingRoot
5) Open up an "adb shell" and use "su" to get a root shell.
6) Use dd commands (like in the original post's link) to zero, flash aboot & the recovery image to their proper partitions.
7) Use "adb reboot recovery" to boot into TWRP
8) Factory reset
9) Flash ROM (AICP etc.)
10) Flash 12B bootstack (not 100% sure needed, but whatever)
11) Wipe cache/dalvik (not 100% sure needed, but whatever)
12) Reboot & profit!
After seeing successful boot, I did go back into TWRP & flash the 35B bootstack, just to have the latest stuff that still does work.
I *did* have one oddity where my screen went black, but NOTHING was responsive (not even the LED). Phone just appeared completely dead -- no response to anything. I pulled the battery, and it booted up fine. Hasn't happened again...
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
fast69mopar said:
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
Click to expand...
Click to collapse
I was on a "fresh", unrooted flash of the 35B KDZ after some previous failed attempts to get TWRP installed. Then, I started my steps listed above. I didn't swap out KingRoot to SuperSU (since I knew it'd just be overwritten when AICP gets installed). Just needed root to flash aboot & recovery.
What command did you run to flash the twrp img, in the other link with the commands of says he used flashify but you used terminal to flash yours. Thanks.
It works.
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
jimtom1948 said:
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
Click to expand...
Click to collapse
You mind giving m the exact commands you used and the order you did everything in? Got a little confused going from thread to thread to get everything downloaded. Think I read too much.lol confused myself
Evohog
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
jimtom1948 said:
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
Click to expand...
Click to collapse
One last question, where in the commands it says "block/name/a boot" so I enter vs985 where it says name or do I enter name. I'm so rusty,it's been a couple years since I've even rooted anything. Thanks again for the hand holding.
Evohog
If you are talking about the commands that you type into the terminal emulator, you enter them just as they are written, except for what is in quotes. Don't change them. Good Luck.
Hey guys, Tried this and now im hard bricked. Could anyone give me a hand? I have everything posted here.
http://forum.xda-developers.com/verizon-lg-g3/help/kdz-restore-t3315170/post65328929#post65328929
johnny567
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
jimtom1948 said:
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
Click to expand...
Click to collapse
It doesnt seem to be working for me. It is pulling up as the Qualcomm 9008 and i have tried with and without wire. It keeps failing and I end up with the error "No response from the device. Check PMIC first and if still boot problem replace AP." I noticed that I have a vs985k. Do you think that could contribute to the failure?
If you are on 35b (rooted or unrooted) without TWRP here is a simple guide to get TWRP and rooted Marshmallow 46A on your phone. This is all info available in various threads here on XDA (typically mentioned by roirraW "edor" ehT) and I take no credit for any of this work. After going thru the process yesterday I simply thought it would make it easy for others to find everything in one place with links. Standard disclaimer : use this method at your own risk
1.Use the TOT method to return to 10B (backup your data, this will wipe your phone) http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
The most helpful posts in this thread were the OP, #9 and #236 note: if this doesn't work for you look here http://forum.xda-developers.com/verizon-lg-g3/general/ks-version-error-downgrade-trouble-t3306028
2. Root your phone (now on 10B) using Stump http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
3. After rooted Install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
4. After SuperSU is installed install TWRP using TWRP manager https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
5. Reboot into TWRP recovery and factory reset (just to be safe)
6. Flash 35B bootstack from TWRP recovery http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
7. Wipe data/cache within TWRP
8. Flash 46A in TWRP link to stock http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365 Or use the rom of your choice
9. Reboot to system (do not install superSU from TWRP if using the link above)
For ease of installation I suggest downloading everything to your PC first then create a folder on your SD card called flash and copying the needed apk and zip files to that folder before you get started. This way you won’t have to sign into your google account in 10B to download the APK for SuperSu and TWRP manager. Use apkmirror or a similar site to download what you need.
Any issues to report on running 46A? Any issues with having an SD card?
No issues, I flashed stock 46A yesterday and everything has worked perfectly so far. No problems with SD card, (Sony 32Gb Class 10-UHS1) I mostly have it for photos and music. I have only disabled/uninstalled some preinstalled apps and flashed the hotspot mod so far. Can't comment on battery life, needs a few days to settle.
Are you still able to downgrade back to 35B, if need be?
Not sure haven't tried but I assume this method would work
someguyatx said:
Not sure haven't tried but I assume this method would work
Click to expand...
Click to collapse
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
I don't know, you will probably get a better answer in one of the other threads. You may also have to try the alternate method of the tot method doesn't work.
chadhoard said:
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
Click to expand...
Click to collapse
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
roirraW "edor" ehT said:
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
Click to expand...
Click to collapse
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
chadhoard said:
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
Click to expand...
Click to collapse
Great, glad to hear it. Xposed works for me. I always have to Google for:
Code:
xposed lollipop
I'm pretty sure the Marshmallow xposed can be reached that way too. I think SDK23 is Marshmallow, so that's what you'll look for in the different Xposed flashables.
I have an issue and I had it before I did the above steps I was just hoping upgrading to 6.0 would fix the problem. My G3 boots into the fine but the wireless says "turning On" for about 1 minute and then it finally turns on and asks to connect to my home wireless, I enter the password and within 2 minutes the phone shuts down and will not go past the Red V Verizon screen, it just keeps rebooting. I can go back into TWRP and wipe it and it will boot back into 6.0 again. I was able to turn the wireless off before it went on and side loaded 25 diffenent apps and was able to use the phone for 4 hours without any issues but then I thought I would try the wireless again and it took like 4 minutes to finally turn on then as soon as I connected to a wireless network (office network this time) within 2 minutes it shut down. I was able surf the web and get on Google play store before it shut down but then it went back to the endless reboot loop..
My thoughts are that I might be able to flash a bootstrap update and I am not completely sure if a new one came in the 6.0 Android updated listed above actually came with one and if not I am not sure which one to use.
This all started in middle of December when the daily CM updates went from 5.1 to 6.0 overnight and everything got messed up. I was over trying to fix it so I ordered myself a Nexus 6P for Christmas and then life was good till I ran over it yesterday with my Jeep and destroyed it.. So back to trying to get the G3 working...
thanks for the help
Doug
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
I can confirm this method works and I had no issues except for steps that i misread and had to repeat..
I used to be on Rooted on 35B with no Recovery. Now I am on 46A rooted with Recovery.
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Nesbocaj said:
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Click to expand...
Click to collapse
Did you verify the md5 on your pc before copying to your sd card?
someguyatx said:
Did you verify the md5 on your pc before copying to your sd card?
Click to expand...
Click to collapse
Yes.
Second try: I d-loaded directly into the phone mem and flashed that, seems to have done the job overnight (!!! ), restoring applications right now.
Thank you for the most excellent guide, not that simple (for me), but very well done.
The phone has become un-rooted with this last flash, TWRP app will not load. OK reloaded and back.
Glad it helped you. I spent several hours reading the forums and installing and wanted to save others some time. Everything was here already just not easy to put the pieces together.
someguyatx said:
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
Click to expand...
Click to collapse
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
duglas said:
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
Click to expand...
Click to collapse
Hardware issue perhaps.
wait how do you know if you are on 35b?
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
Ok. If you're wanting to do 100% stock, download the complete zip for 20c from http://downloads.codefi.re/autoprime/LG/LG_G5/H830/H83020c/LG-H83020c-Flashable.COMPLETE-ARB01.zip there. Put it on your extsd card. Backup everything that is on your internal sd (phone memory) like pictures, videos, SMS, etc. Once you've done that, boot to TWRP. Once in TWRP wipe everything except externalsd card, I also recommend using the format option to format the internal sd. Once you've wiped and preferably formatted data go to install and install the 20c complete zip you put on your extsd card. After it's done installing just reboot. This will overwrite TWRP and you will NOT have root. Your bootloader will still be unlocked though, so you still need a PC to relock your bootloader. Also I don't think encryption will be re enabled unless you flash the kdz though. Anyways that's your best way to return to stock without using PC.
mlatelcom said:
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
Click to expand...
Click to collapse
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Click to expand...
Click to collapse
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
mlatelcom said:
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
Click to expand...
Click to collapse
Thanks bro. I totally believe it because past phones had exact issue.
Sent from my LGE LG-H830 using XDA Labs
Just for clarification, if you're on Android 7, you can not downgrade to Android 6 without first downgrading your bootloader as it won't flash correctly. Also just something to always keep in mind with LG phone's at least, is that LG uses a antirollback system. Never attempt to downgrade from a higher ARB # to a lower ARB #, if you're somehow successful it will lead to a hard brick. Every firmware that autoprime has posted states what antirollback number it is on, so always check that. On h830, every firmware since 10D has been ARB01, only 10A or earlier was ARB0. While lgup shouldn't allow you to flash (should error out), no reason to take that chance. Hopefully that helps clarify
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
water- said:
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
Click to expand...
Click to collapse
Early on with the verizon V30 roms I found that uninstalling some of the bloatware caused boot loops. From then on I just froze them; doesnt help your space situatuon though...
If no other suggestions, you could try a dirty flash of the ROM you were running (assuming you flashed TWRP zip).
I believe you'll need MyVerizon anyway, as this is what enables VOLTE and VOWIFI on Verizon (for me, at least). So I would not recommend removing it anyway.
Granted, you're past that. I would think that dirty-flashing the ROM should restore it, potentially? That could be one way to get back to running. Another way might be to reload the APK somehow. You might need to use TWRP to do that, unless there's another way to do it from a TiBu backup? If I can help in some way (I'm on VS996) I'm happy to try.
Unless you actually deleted the apps from System, it's almost certain that a Factory Reset will solve it. But I can understand your reluctance.
I'm not sure a dirty flash will help, since the problem is your data partition. You already tried deleting cache (I presume in TWRP).
And I agree that if you could somehow reload the apk, that might do it. Does ADB install work in TWRP, despite no OS? If so, that's worth trying. First pull the apks you removed from System to your computer, then run adb install apk-filename.
But FIRST make a full TWRP data backup of what you have now!
If you have to Factory Reset, you can use TiBu to restore your user apps from that backup. I haven't tried that in years, but I assume TiBu still has this feature.
Fingers crossed for you :fingers-crossed:
And for others who see this: Careful, selective debloating IS possible, but it always starts with a full backup: TWRP if rooted, otherwise LG Backup, (which saves app data and most OS settings).
Thanks all for responses, appreciated so much. In a bit of a pinch as I needed my phone for a backpacking trip last weekend, I just moved forward as best I could on Friday. Generally I tweak my phone enough to unlock/root then let it be. I guess I got greedy/complacent try trying to de-verizonify it and clear some space as much as possible.
Two things
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
I'm on 30c version of PIE and keep getting bugged to install a system update which I keep putting off because I'm leery of that..but I can't freeze the process without root.
Also because I flashed the stock OS, that means I lost the custom recovery, I don't have TWRP anymore (this seems so, but looking for confirmation), right?
2) retrospect, and a question for future reference
After all this I realized like an idiot I had a TWRP backup made in 2018 after I first unlocked and rooted it. Just hanging out on my SD card, which I could have accessed via TWRP before I flashed the KDZ. If I would have restored that it would have re-installed the OS and retained my data. Is that considered a dirty flash though, like it might not have worked or had subsequent problems?
And secondly on the SD card, I found all the 'dank memes' and other downloads I was worried I'd lost, so most of the data loss tragedy :silly: was averted (main pics backup to cloud, learned that lesson after lg g4 hardware bootloop pain).
water- said:
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
Click to expand...
Click to collapse
With unlocked bootloader on Pie, here's how you reinstall TWRP (IF you are on firmware with fastboot flash commands). Yes, I made a standalone post for this -- but if you read it it's basically just Section 6 of WTF Instructions. However, I had to make a standalone post because too many people kept thinking they had to downgrade back to Oreo, etc.
So, you can reinstall TWRP on Pie if you have unlocked bootloader. The problem is you need to fastboot flash commands to do that. VS996 firmware does not have that, which is why VS996 owners have to TEMPORARILY convert to US998 in the first place to unlock bootloader, install TWRP and root. Yes, your bootloader is already unlocked, but on VS996 you don't have the necessary fastboot flash commands to reinstall TWRP.
Thus, you will need to go back to US998 firmware (flashing KDZ via Dev Patched LGUP) to get fastboot flash commands. You can do it the hard way (US998 Pie KDZ) or you can do it the easy way (US998 Oreo KDZ). With already unlocked bootloader, you don't need to go back early Oreo, you can go to last Oreo. I don't recommend flashing US998 Pie for this, as there's too many people who have trouble with US998 Pie (stuck on LG logo, etc). You just need to temporarily get fastboot flash commands, and get TWRP reinstalled.
That post I have linked in the first sentence is for unlocked Bootloader with fastboot flash commands, on any stock firmware (Pie, Oreo, even Nougat if you wanted that for some reason).
Once you reinstall TWRP, then you can go back to VS996 Pie firmware via TWRP flashable zip.
Thanks for your response, now and two years ago.. super appreciated
I only need to get to the point to put the phone in debug mode (with access to fastboot) to get TWRP installed after flashing the recent oreo kdz. After TWRP installed follow your instructions (thanks!) to flash TWRP pie..
I'll probably give it a go this weekend or tomorrow evening, but do you have a recommended link to US998 Oreo kdz? https://androidfilehost.com/?fid=1395089523397933445 is fine?
Whereafter I'll follow your instructions for installing it (using LGUP patched) at: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
In the ROM section, go to ChazzMatt's US998 Pie KDZ thread. It also has instructions for rolling back to Oreo. Follow them to the t.
Make sure to use the Pie-compatible LGUP version in there when you roll back, and install it exactly as described in that thread.
His US998 Oreo thread will have a download link for Oreo 20h (the latest Oreo). Otherwise it's easy to find on lg-firmwares.com.
Good luck to you
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
2) maybe related to the above, maybe (probably not) not.. and I realize magisk and other avenues might cover it these days but I'm trying to debloat the TWRP flashed VS996 ROM with Titanium Backup.. stuff like NFL and slacker radio, google music.. like I did on Oreo. But Titanium keeps giving me an error about 'can't find the apk' -- Ti says I have root. I have read a bit that Android 10 really packages the apps in there so it's not like you can just remove the ones you want. is this the case for 9 too?
suggestions for alternative tool if Titanium is kind of a dinosaur in that regard?
Thanks
Well done!
1) It's best to use Format Data in TWRP to avoid that mounting error. Unless you are certain you have no mounting problems, I would recommend doing that before spending more time setting up the OS.
2) Before trying to freeze apps with TiBu, see if they can be Disabled in the regular Apps menu. Most of the "optional" bloatware can. Of course make a TWRP backup before freezing anything with TWRP!
Water-, there is already a debloated Verizon 99630c rom out there somewhere, if you would like to try it. I'm on it now.
Sorry, I can't link it. It was made by micromod777. So do a search for him.
I also use tibu, but there is another app (?) out there called migrate that backs everything up. You might look for it and try it. (I did use it a month or so ago myself just to try it - - worked for me).
water- said:
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
Click to expand...
Click to collapse
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
ChazzMatt said:
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
Click to expand...
Click to collapse
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
water- said:
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
Click to expand...
Click to collapse
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
ChazzMatt said:
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
Click to expand...
Click to collapse
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
water- said:
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
Click to expand...
Click to collapse
Do you have encryption on? TWRP will show a mount error upon start, and prior to the passcode being entered.