Q&A for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
MicroMod777 said:
Sweet. Did you post you tried the bumped twrp on the 39a and it didn't work. Last time I remember they had to rebuild twrp based on 26a. It might need to be rebuild on 39a sources.
Click to expand...
Click to collapse
xdabbeb said:
Nope. No idea what the point of that is.
Click to expand...
Click to collapse
Following the links, it looks like there's a new root exploit using download mode for a number of LG devices - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Help
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
protfire said:
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
Click to expand...
Click to collapse
You can, but when switching between different based roms you'll often need to flash stock to get your sensors working again.
Sent from my LG-VS980 using XDA Free mobile app
Looking for some guidance
Having some issues with getting setup to flash VS982.5
Had a replacement phone sent from Verizon because of a dead digitizer. The phone shipped with 27A. I was able to get it rooted and got recovery installed, but then started running into issues. From there, I used the 11A tot. Got rooted, used Autorec for recovery and then tried flashing 28A, but am now getting a secure boot error.
Anyone have any advice?
@xdabbeb ???
noob question
Ok been flashing for a while nexus 7 - nexus 7 2013 and nexus 10 but this lg is a diiferent animal so im on broadbase 26a and can flash all cloudys roms but cant get lollipop roms to flash tried flashing the 39a and it rebooted but no data so went back to 26a broadbaseand all worked again so my question is can i flash 39a with the 26a modem and make flashing lollipop Possibly. Im on the verizon vs 980 model. Thanks in advance
Help please!
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
---------- Post added at 04:37 AM ---------- Previous post was at 04:27 AM ----------
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
kongo101 said:
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
Click to expand...
Click to collapse
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
kongo101 said:
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
Click to expand...
Click to collapse
The answer was to simply rebooting into recovery after flashing the bootstack, rather that rebooting the system. That would have prevented the secure boot error. Lesson learned the hard way.
Hey, tryna get my head to stop spinning after the loads of info I just memorized trying to figure all this stuff out. I'm trying to flash a CM12 official nightly on stock 5.02 and TWRP 2.8.5.1. I just used bouchigo's little guide to get the 28A aboot and bumped boot and recovery to see if that would let me flash CM12/the updated TWRP 2.8.6.0 and neither worked (I'm assuming because it's not 12b still). So now I'm about to try to use the 39A zip in here and then flash the 12b bootloader, but I'm not sure exactly how to do it. Do I just flash both in TWRP and then do the reboot to recovery? I tried to flash the new TWRP (2.8.6.0) in TWRP and it gave me the same loki error as CM12 did so not sure it will work that way with this? Also will it mess anything up with the bouchigo images I have installed/should i flash my stock backup before I flash the 39A? And once I install the boot stack can I just flash 12b boot loader and be good to go to install CM12?
Also is there anything major to be concerned about while messing with this boot stack stuff or will it mostly be recoverable problems where you can just flash your backup? Sorry for the general question. You don't have to go into too much detail or anything, just tryna make sure there's not something you would be more likely to do (like rebooting to system instead of recovery) trying to configure the boot stack to work for your needs. Thought it may be helpful for others also as I haven't seen too many (more specific and/or general) caution tips in the threads I've visited in the last few days, especially in the OP's. No offense to any of you developers or anything, just something I thought might be helpful in future posts (especially for semi-casual's and noob's like me lol). With that said I'm very grateful for all the information on this site and the devs for their time. Keep up the amazing work. And thank you in advance for the knowledge!
I'm confused with an issue I'm facing with my Vs980 on Tmobile, so might as well ask this here before I mess up the phone any further.
After flashing 39a kdz I was able to get LTE connectivity, but battery lifetime was kinda poor. A few posts reported improvements with a factory reset ... so I did just that. Battery lifetime was even worse ... so why not another factory reset? I did just that and LTE wouldn't come back on. The phone starts, shows full network, and 4G for a second ... then network connectivity becomes glitchy going on/off constantly. The only way to get a stable network connection was to go into the settings and change the network connectivity to UMTS/HSPA instead of the LTE/3GPP .
I tried flashing 27a kdz, but the same issue keeps on happening. Now I'm debating whether I should be flashing just the 39a modem from this post after a clean 39a kdz flash ... but I can't make much sense out of this thought.
Any ideas on what could be done to resolve this problem?
It works perfectly. Congrats!!!!
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Kilroy245 said:
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I flashed the rom without bootstacks but in twrp, if it goes into sleep, i get a dead screen with lines which I need to reset with adb command
adb reboot
On 39A rooted and twrp
vs980 39a Bootstack lollipop no cell signal or service
i have this lg g2 vs980, i was running an old xdabbeb 24a bootstack with a KK lg g2 rom on cricket service everything worked good besides bluetooth. (rooted&twrp recovery)
since then i have flashed twrp 2.8.6.3 bump-blastgator. i followed xdabbeb instructions for flashing 39a bootstack and xdabbeb_vs980_312.zip but i have no cell signal. i also tried LP-TMO-Extreme rom with a t-mobile simcard and apn and it didn’t work either. i was wondering if someone here can help, i tried flashing this rom and bootstack in every combination i could imagine, and still no signal.
i also flashed the 24a bootstack back and KK rom back and now still no signal. can someone please help me, I’m out of ideas.
thanks in advance!
Error loki-ifying
Hello, following your directions at http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560, I was trying to flash the 39a bootstack zip from CWM on a VS980 10B. After the extractions, I got this message:
Code:
Finished!
script succeeded: result was [Finished]Checki
ng if loki-fying is needed/dev/block/platform/
msm_sdcc.1/by-name/boot needs lokifying.
[-] Failed to find function to patch.
Error loki-ifying the boot image.
I'm confused because it both says the script succeeded and that there was an error.
When I rebooted, I went into a bootloop. I got back into recovery. My recovery is now TWRP. I went ahead and flashed the 38A firmware, and everything seems to have worked out just fine.
Do I need to worry about the error I got flashing the bootstack?
Related
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
matt99017d said:
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
jayboyyyy said:
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
Click to expand...
Click to collapse
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
matt99017d said:
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
next time just flash the system.img as well and you should have been good to go without losing any data.
[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.
Q&A for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
Same thing for me...
Sent from my Droid Turbo
Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
getupandbeit said:
Same thing for me...
Sent from my Droid Turbo
Click to expand...
Click to collapse
At the recovery which reads "no command" hold power and press volume up.
Works on
What's going to happen if I push 5.1 and Android M comes out officially?
Am I better off holding until that time or is there a way to get there once I do all of this
Hello, Ive been reading on here about mofo for the last month, and Ive been waiting to see how lollipop goes over. After reading all the success stories, I bought mofo.
My phone has never been rooted, is there a specific guide for going to computerfreek274's loliipop image from a stock kitkat ? All the guides seem to assume Im already rooted on kitkat. Or should I root on kitkat first?
thanks
In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!
turpindm said:
In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!
Click to expand...
Click to collapse
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.
firstEncounter said:
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.
Click to expand...
Click to collapse
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.
turk2333 said:
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.
Click to expand...
Click to collapse
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.
firstEncounter said:
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.
Click to expand...
Click to collapse
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.
turk2333 said:
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.
Click to expand...
Click to collapse
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.
firstEncounter said:
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.
Click to expand...
Click to collapse
This is not being stuck this was no service at all would to G then I could not make calls or anything - totally screwed up - I have a new phone on the way from Assurion if this keeps happening. As I posted - I flashed all commands per instructions and that seem to do the trick I hope.
Thanks to everyone who keeps the updates updated... 23.11.39 Root went well... Thanks again!!!
Fastboot Command
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.
Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app
Quick question
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?
SkiiinZ said:
Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
because mofo can't write the kernel/boot partition
Sent from my XT1254 using Tapatalk
Tap053 said:
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?
Click to expand...
Click to collapse
Either one should work if you follow the instructions but only the "extra" versions have tethering enabled. At this point, I'd use the image labeled "Extras 5.1 system image (rooted v2 + extras v4)". You can always start with the stock rooted, then dirty flash the extras version with mofo.
Sent from my XT1254 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
Rag Man said:
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.
Click to expand...
Click to collapse
Nowhere in the OP for this ROM does it mention flashing files with ADB. You can only flash the system image with the mofo tool. We do not have a custom recovery on the Turbo so you cannot flash ZIP files. We do not have a writable system partition so you cannot push files to it via ADB.
Fastboot is used to upgrade some of the other partitions to the 5.1 versions and is described in the OP.
Sent from my XT1254 using Tapatalk
I've browsed the threads and searched and can't find a for sure answer. Is it possible to flash a Rom like XDABBEB's by downgrading or any other relatively safe process if I'm on 3aa? I'm trying not to even soft brick because my home internet is very slow and it would possibly take me hours to download necessary files to recover from a soft brick. If it,is possible can you point me to where the directions are or help me out?
Always best to have a way back should anything go wrong.
Return to stock
http://forum.xda-developers.com/showthread.php?t=2448960
Don't think you need to downgrade, just root, autorec twrp, and you're all set.
Oh, and read, a lot.
Sent from my Nexus 6 using XDA-Developers mobile app
Dork6243 said:
Always best to have a way back should anything go wrong.
Return to stock
http://forum.xda-developers.com/showthread.php?t=2448960
Don't think you need to downgrade, just root, autorec twrp, and you're all set.
Oh, and read, a lot.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the reply. I must be doing something wrong if I don;'t need to downgrade to flash his rom from 3aa. I did exactly that above, rooted, autorec'd twrp and then tried flashing his rom with the 39a bootstack flashed first. Got a secure boot error, so tried it without the 39a bootstack after restoring my twrp backup and received the same secure boot error
Problem solved by flashing 12b bootloader. Saw it mentioned this: 12B Bootloader - needed for older kernel/boot images (and firmware that contains a kernel) that ONLY support loki.
SO decided to give it a try (ive bricked a phone or two flashing bootloaders so wasn't too comfortable trying this) AND it worked....
But im running into all kinds of crazy issues. Phone signal drops and reconnects between 3g, 4g lte, and no signal every 10 seconds or so. WHen i try to go to the settings to switch it off global mode, that screen flickers like crazy and cant click anything.... but it booted, so tahts a start
Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.
T-Mobile G6 H872 20D Stock Collection
Based on OEM 20d KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
20d Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
SysBoot ROMs will only work with 20a or 20d bootloaders
FILE BREAKDOWN
The following Zips DO NOT include stock LAF or Recovery
You must flash the provided LAF separately if you wish to go back to stock DL mode.
Bootloader: 20d Stock Bootloader ONLY
SysBoot: 20d Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 20d Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
If you are already on my 11g/h or 20a SysBoot ROMs with root and you are able to mount System in TWRP, you should not need to Format Data.
If you are asked for a passcode in TWRP or are unable to mount System, Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:d4035f43f0dcf47d818a234077f9e7f1
SysBoot ROM - md5:778994866d440676aea146ac289e3852
SysBoot w/Patched Kernel + Magisk Root - md5:f1398a45581b7ab8a90d48a9c6bed81f
FullStock ROM - md5:ff9d7a22a70abd0caf83377308778fe4
StockLAF - md5:785a64b6b4a25d01df0d25a09c0f6f73
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11G Stock Collection
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87220d, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 20d KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-10-18
Created 2018-10-18
Last Updated 2018-10-19
@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.
weakNPCdotCom said:
@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.
Click to expand...
Click to collapse
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk
Ken C said:
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem
weakNPCdotCom said:
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem
Click to expand...
Click to collapse
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk
Ken C said:
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
sweet. should have debloated 20d sysboot posted later tonight
Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you
weakNPCdotCom said:
sweet. should have debloated 20d sysboot posted later tonight
Click to expand...
Click to collapse
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
aquinoer said:
Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you
Click to expand...
Click to collapse
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Sent from my LG-H872 using Tapatalk
Ken C said:
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Click to expand...
Click to collapse
I have h872 I just want to get security patch and have root lol
I'm going to assume that you've already looked into the root thread for the device.
If you have fwul on a thumb drive and know how to boot to it from your pc you really should be good to go. Just to make your life easier put twrp and magisk on your external SD card before you do anything.
Perform the laf switch in lgup.
Go through step 1 in fwul, but when you come to step 2 you'll be better off flashing it manually.
Rooting will put twrp on your laf partition and allow you to access it from there (using the method you used to get into download mode) to flash twrp to recovery and magisk to keep root. Op has these files set to not have to worry about some of this stuff but, first time through I'd want to do it by the book.
Theoretically if you have TWRP on recovery you should be able to flash one of his prerooted roms making the whole mess easier but I've not discussed that option with him. So don't try it unless you're adventurous.
This is from the op and takes place after you do step 1 through fwul (which seems to be all you really need that for)
https://forum.xda-developers.com/showthread.php?p=77811927
Biggest piece of advice I could give you would be to do a dry run of fwul and see what you get. That way you can work out any hang ups before you commit. And get a feel for how it operates.
The dangerous part is where you change the laf on the phone through the patched lgup program and have to do that cord pull deal. It seems to be good at the 10% mark. But to be safe once you get it set to go have the phone in one hand and cord in other. As soon as it goes from laf to the next partition
AS SOON AS YOU SEE IT CHANGE, PULL THE CORD!!!
Then boot into fwul and perform follow step one. Don't worry if unpacking seems to take forever, it jumped to 31% for me and felt like it got hung up. Be patient, like really patient and it'll eventually run through. Then finish out the commands that put twrp on laf.
You could if you want to do the reading, look through anything with my name attached. I had a hell of a time getting things right. Also just in case I missed something.
I'm still waking up but this should be what you need. I screwed it up a bunch of times and was probably lucky with no brick but like I said before it seems the laf switch is the dangerous part. I've been able to recover from everything else.
The link I posted is really specific and may help you more than me telling you from memory. So I'd read that after making sure you got the first part worked out procedure Wise from the root thread itself. (make sure you understand what you need to do for that part) Sometimes it's worth it to read through a whole thread to see the screw ups everybody else made plus there's a video some guy posted that shows it being done. Not to mention I could've missed something by accident.
Also just in case if you've got another sim card device hanging around I'd put the card in that and use it until you get this worked out correctly. Just so in the worst case you've got a working phone to use.
And honestly if anything I posted makes you uncomfortable hold off until you are. Things can be fixed but why stress if you don't need to?
@weakNPCdotCom
Did I miss anything?
Sent from my LG-H872 using Tapatalk
aquinoer said:
I have h872 I just want to get security patch and have root lol
Click to expand...
Click to collapse
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk
Ken C said:
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.
weakNPCdotCom said:
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.
Click to expand...
Click to collapse
Thanks man,
Something I've noticed on the 20d build. The "my places" app has been repeatedly closing. Not crashing and freezing it stops it. But when it would close it would close out settings at the same time.
Not sure if it was me or not. I been tweaking whatever I can. More curious if you'd seen it before yourself.
Saw you pm'ed me so I'll look at that. Feel like I live in a Morton's Salt label at the moment.
Sent from my LG-H872 using Tapatalk
LG G6 H872 - Software version H87220e
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?
can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?
Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!
usmras said:
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?
Click to expand...
Click to collapse
macg13702 said:
can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?
Click to expand...
Click to collapse
Versions 11g - 20e are ARB01 and interchangeable. If you are rooted and/or already have TWRP on your phone then yes, you can flash the FullStock zip to downgrade. Otherwise, you will need to follow @runningnak3d 's root procedure which will require the KDZ for whatever version you want to end up on.
BUT.. I will put a 20e collection out for you guys asap.
RashaMatt said:
Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!
Click to expand...
Click to collapse
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.
weakNPCdotCom said:
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.
Click to expand...
Click to collapse
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!
RashaMatt said:
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!
Click to expand...
Click to collapse
No problem m8! And yeah, if you want to download the KDZ I would use the patched LGUP that is linked in the H872 root thread
weakNPCdotCom said:
And yeah, if you want to download the KDZ I would use the flashed LGUP that is linked in the H872 root thread
Click to expand...
Click to collapse
Meaning this? LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF)