[STOCK] [H872] [11g] T-Mobile G6 Stock Collection

[weakNPCdotCom]

T-Mobile G6 H872 11G Stock Collection
Based on OEM 11g KDZ. Extracted and Repacked.

DISCLAIMER

• Proceed at your own risk. I am not responsible for any damage to your device.
• SysBoot ROMs were test flashed over 11g and 20a bootloaders. 11h has not been tested.
• 11G Firmware is ARB01
• Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode

FILE BREAKDOWN

• The following Zips DO NOT include stock LAF.
• You must flash the provided LAF separately if you wish to go back to stock DL mode

​

• Bootloader: 11g Stock Bootloader ONLY
• SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
• FullStock: Full 11g 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.
• 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:43dcc7f82c501147da6500efdd594d5c
• SysBoot ROM - md5:2ac20008794eb74523a442da7b8bafdc
• SysBoot Deodexed - md5:b92fcb7649bddf934ff9be0246c9fab6
• SysBoot w/Patched Kernel + Magisk Root - md5:ae4bab194a69b2044f3aee69ba495464
• FullStock ROM - md5:e919fe16852b5f0b830a48cda914003a
• StockLAF - md5:ce70b36e4d293e183544a18409a526de
• TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa

These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!​

Other H872 Projects

• H872 11H Stock Collection
• H872 20A SysBoot ROMs (Stock and Rooted)
• H872 20D Stock Collection

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] h87211g, ROM for the T-Mobile LG G6

Contributors
weakNPCdotCom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11g KDZ

Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-09-30
Current Beta Version: 0.9
Beta Release Date: 2018-09-30

Created 2018-09-29
Last Updated 2018-10-19

 

[DmytroPitenko]

Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?

 

[weakNPCdotCom]

Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?

very welcome. if you flash the bootloader only it will leave whatever laf you have untouched, and yes fingerprint scanner will work with custom ROMs like AOSP Extended.

However, I have not tested running stock 20a with the 11g bootloader. But it doesn't sound like that's what you are wanting to do

*edit*
if you have already flashed a custom Rom and FP doesn't work, simply flashing the 11g bootloader zip will fix it. it is not necessary to reflash the rom

also, not sure why anybody would want to, but 11g bootloader with stock 20a rom will not work. it will hang on the boot logo indefinitely which can be dangerous for your phone. so please make sure you are using a custom Rom or stock 11g with this bootloader

 

[Ken C]

Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.

Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.

Not hounding ya just thought I'd prefer over here and see what you been up to.

When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)

I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.

Sent from my XT1575 using Tapatalk

 

[weakNPCdotCom]

Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.

Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.

Not hounding ya just thought I'd prefer over here and see what you been up to.

When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)

I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.

Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks

put the laf.img file on your sdcard and rename it to laf.bin, and run these

adb shell
su
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/laf
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/lafbak

that will restore stock laf

 

[Ken C]

Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks

put the laf.img file in the folder with adb.exe, rename it to laf.bin, and run these

adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/laf
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/lafbak

that will restore stock laf

Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.

Sorry man just thinking through things.

When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere

Sent from my XT1575 using Tapatalk

 

[weakNPCdotCom]

Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.

Sorry man just thinking through things.

When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere

Sent from my XT1575 using Tapatalk

Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.

and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak

 

[Ken C]

Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.

and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak

Ok. Figured it was something like that. Always meant to ask somebody, just never did


Sent from my XT1575 using Tapatalk

 

[ryanrod]

FILE BREAKDOWN

• The following Zips DO NOT include stock LAF.
• You must flash the provided LAF separately if you wish to go back to stock DL mode

[/CENTER]

• Bootloader: 11g Stock Bootloader ONLY
• SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
• FullStock: Full 11g Firmware Installation
• StockLAF: Individual LAF image for returning to stock DL mode
• Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.

Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).

 

[weakNPCdotCom]

Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).

Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.

 

[ryanrod]

Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.

Awesome. Yeah, I am going to give it a flash tomorrow morning. I do not think I will need the stock recovery at this time, but thanks for offering! I have been stuck with the whole twrp on LAF issue, not being able to use LGUP, and this just a godsend to get back to 11g. Thanks again! :good:

 

[ryanrod]

Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.

IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!

I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.

 

[weakNPCdotCom]

IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!

I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.

You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.

Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.

 

[Ken C]

If I were to downgrade if able to, would that have a chance? I still am getting stuck in fastboot mode unless I'm hooked up to the pic and let lgup do it's thing.
It detects the device, does it's thing, reboots it and gives me a factory reset phone back just no dl mode.

It's not bricked yet lol.

Sent from my XT1575 using Tapatalk

 

[ryanrod]

You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.

Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.

Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.

1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).

I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.

Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.

So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...

Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)

So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.

Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:

 

[weakNPCdotCom]

Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.

1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).

I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.

Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.

So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...

Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)

So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.

Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:

I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.

The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.

I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.

As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.

The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.

Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.

Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.

 

[ryanrod]

I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.

The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.

I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.

As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.

The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.

Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.

Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.

Ahh yes this makes sense. Maybe it was a stock recovery repair due to magisk failure as you mentioned? I still don't understand why with these LG phones (ever since the G3 I think), when you boot into recovery using the hardware buttons, it asks if you want to factory reset the device. Then if you say yes, it doesn't reset/format anything, and it boots right into twrp recovery after that. So weird. I can boot directly into recovery just fine from a reboot app or adb from a running system without getting that factory reset screen...

I'm sure your laf zip with twrp works for the reasons you mention. Luckily I don't have to find out since my laf partition is fine and still has twrp!

Regarding bluetooth, I will give the sysboot flash a try and update you with the results. First I want to wait until my backup phone is running again. I bent the sim pins on the backup phone due to those ****ty plastic adapters that catch the pins (an old E980 w/ the larger sim size) so I ordered another sim reader to fix that. I also read in some forums that wiping cache and dalvik cache resolved others bluetooth issues with the G6. I will try that too.

Either way, I will update soon. I am happy to share my notes as I really appreciate the help!

 

[Ken C]

@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.

I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?

Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.

Sent from my LG-H872 using Tapatalk

 

[weakNPCdotCom]

@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.

I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?

Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.

Sent from my LG-H872 using Tapatalk

What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?

So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.

The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.

 

[Ken C]

What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?

So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.

The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.

What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?

So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.

The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.

Yes that's the message I get. So your saying not to worry about it for the moment? I only see it regularly on a stock rom when going into recovery not aex.

I just wanted to make sure. With the mess I been going through.

So, I can flash this stock build you have and if I wanted normal download back flash the laf zip and I'll have DL mode on laf, twrp on recovery and everything should Mount correctly and all that?

And if I go to flash something custom FP will work? I know I'm a pain I just want to "know" my setup isn't weird somehow. Probably over thinking it, but I think I'm good, except that when I rooted I was getting that message off & on, on the stock build of 20a. I'm hoping that running this build I can get that worked out. Maybe that deal is a 20a thing? Reading through the root thread it seemed to happen less to people on a lower numbered build and it would stop after the format.

I can make backups Burt I've yet to try to restore one.



Sent from my LG-H872 using Tapatalk