LG Tribute 5 | LS675 | K7 | M1

[RolandStoner]

Device: LG Tribute 5 LS675
Android Version: 5.1.1
Kernal Version: 3.10.49-gecffe94
Build-ID: LMY47V
Root Method: King Root | SuperSUMe to change from kingroot to SuperSU |
CPU: armeabi-v7a (qualcomm) 4-core 1ghz Qualcomm MSM8909
GSM:MICRO SIM | (ALSO) HSDPA CDMA EvDO LTE
Storage: 8GB
OS: Android 5.1.1

Download Mode:
Power off
Hold Vol Up
Plug in USB

Recovery Mode:
Hold Power and Vol Down at the same time

Enable Developer Options:
Settings > About Phone > Software Info > *TAP Build Number 7 Times* Congratulations your now a developer!

One Click Root via KINGROOT | https://goo.gl/FbBi6y | > Remove & Replace KINGROOT with SuperSU via SuperSUME | https://goo.gl/Ox5Xw9 |

DO NOT FLASH BOOT IMAGE OR CUSTOM ROM YOU WILL BRICK

What we can do is flash the XPOSED framework therefor eliminating the need for a custom rom.
What is the Xposed Framework? https://www.youtube.com/watch?v=uRR0Flqx9M8


Thanks to chainfire we can use his app flashfire > ||| goo.gl/jdybPK ||| to flash the xposed framework ||| goo.gl/xhl5zt ||| and then install the xposed APK ||| goo.gl/xv3Rqs |||

I have just found out that we can set SELinux to Permissive and have it persist on reboot with superSU.
Basically enter these commands in terminal emulator as superuser or via adb shell as superuser:

su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh

For Some Reason I have two fstab files. /fstab.m1 & fstab.fota
This is /fstab.m1

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

#<src>                                                <mnt_point>  <type>  <mnt_flags and options>                     <fs_mgr_flags>
/dev/block/bootdevice/by-name/system         /system      ext4    ro,barrier=1,noatime,discard                         wait,check
/dev/block/bootdevice/by-name/userdata       /data        ext4    nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue,discard    wait,check,encryptable=/dev/block/bootdevice/by-name/encrypt
/dev/block/zram0             none         swap    defaults zramsize=268435456
/devices/soc.0/7864900.sdhci/mmc_host        /storage/external_SD   vfat    nosuid,nodev         wait,voldmanaged=external_SD:auto

/fstab.fota

# Copyright (c) 2011, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
#     * Redistributions of source code must retain the above copyright
#       notice, this list of conditions and the following disclaimer.
#     * Redistributions in binary form must reproduce the above
#       copyright notice, this list of conditions and the following
#       disclaimer in the documentation and/or other materials provided
#       with the distribution.
#     * Neither the name of The Linux Foundation nor the names of its
#       contributors may be used to endorse or promote products derived
#       from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# mount point	fstype		device			[device2] [length=]

/dev/block/bootdevice/by-name/system       /system        ext4     rw,barrier=1                                                       wait
/dev/block/bootdevice/by-name/cache        /cache          ext4    rw,noatime,nodev,barrier=1,data=ordered                     wait,check

PARTITIONS

root@m1:/ # cat /proc/partitions
major minor  #blocks  name

 253        0     229776 zram0
 179        0    7634944 mmcblk0
 179        1      65536 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3       1024 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5       2048 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7       1024 mmcblk0p7
 179        8        512 mmcblk0p8
 179        9       2048 mmcblk0p9
 179       10       1536 mmcblk0p10
 179       11       1536 mmcblk0p11
 179       12        512 mmcblk0p12
 179       13        512 mmcblk0p13
 179       14       1536 mmcblk0p14
 179       15        512 mmcblk0p15
 179       16        512 mmcblk0p16
 179       17        512 mmcblk0p17
 179       18        512 mmcblk0p18
 179       19        512 mmcblk0p19
 179       20       1024 mmcblk0p20
 179       21        512 mmcblk0p21
 179       22       6656 mmcblk0p22
 179       23       6144 mmcblk0p23
 179       24        512 mmcblk0p24
 179       25       1536 mmcblk0p25
 179       26       1024 mmcblk0p26
 179       27       1024 mmcblk0p27
 179       28       6144 mmcblk0p28
 179       29       6144 mmcblk0p29
 179       30      10240 mmcblk0p30
 179       31      40960 mmcblk0p31
 259        0       8192 mmcblk0p32
 259        1      16384 mmcblk0p33
 259        2      16384 mmcblk0p34
 259        3      16384 mmcblk0p35
 259        4      24576 mmcblk0p36
 259        5       8192 mmcblk0p37
 259        6    2818048 mmcblk0p38
 259        7     204800 mmcblk0p39
 259        8    4341760 mmcblk0p40
 259        9       8175 mmcblk0p41
 179       32       4096 mmcblk0rpmb
 179       64   15632384 mmcblk1
 179       65    7820312 mmcblk1p1
 179       66    7810048 mmcblk1p2

root@m1:/dev/block/platform/7864900.sdhci # ls -al
drwxr-xr-x root     root              1970-01-21 00:48 by-num
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk1p1 -> /dev/block/mmcblk1p1
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk1p2 -> /dev/block/mmcblk1p2

root@m1:/dev/block/platform/7824900.sdhci # ls -al
drwxr-xr-x root     root              1970-01-21 00:48 by-name
drwxr-xr-x root     root              1970-01-21 00:48 by-num
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-01-21 00:48 mmcblk0rpmb -> /dev/block/mmcblk0rpmb

recovery.fstab

#device         mount point      fstype        [device2] [length=]

/dev/block/bootdevice/by-name/system       /system         ext4    ro,barrier=1                                                    wait
/dev/block/bootdevice/by-name/cache        /cache          ext4    noatime,nosuid,nodev,barrier=1,data=ordered                     wait,check
/dev/block/bootdevice/by-name/userdata     /data           ext4    noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc     wait,check
/dev/block/mmcblk1p1                       /sdcard         vfat    nosuid,nodev,barrier=1,data=ordered,nodelalloc                  wait
/dev/block/bootdevice/by-name/boot         /boot           emmc    defaults                                                        defaults
/dev/block/bootdevice/by-name/recovery     /recovery       emmc    defaults                                                        defaults
/dev/block/bootdevice/by-name/misc         /misc           emmc    defaults                                                        defaults
/dev/block/bootdevice/by-name/config       /persistent     emmc    defaults                                                        defaults
/dev/block/bootdevice/by-name/encrypt      /encrypt        raw     defaults                                                        defaults
/dev/block/bootdevice/by-name/eksst        /eksst          raw     defaults                                                        defaults
/dev/block/bootdevice/by-name/carrier      /carrier        ext4    nodev,barrier=1,noauto_da_alloc                                 defaults
/dev/block/bootdevice/by-name/drm          /persist-lg     ext4    nosuid,nodev,barrier=1,noauto_da_alloc                          wait,check

The code 5689#*675# entered in dialer reveals a secret menu

Here is my LS675 folder as of now https://drive.google.com/open?id=0B1rIKS0CqR_3ZmFXRjNHR1poaGM

LS675 Source > http://opensource.lge.com/osSch/list?types=ALL&search=Ls675

FCC Documentation: https://apps.fcc.gov/oetcf/eas/reports/GenericSearchResult.cfm?RequestTimeout=30

 

[glen5678]

I recently got a LG Tribute 5 (LS675) I can not find any development threads about it and have gotten deeper into Android development so I decided to create an account on XDA.

This is all the info I have been able to obtain about the Tribute


Device: LS675
Android Version: 5.1.1
Kernel Version: 3.10.49 (Source)
Linux Version: 3.10.49-gecffe94
Build-ID: LMY47V
Root Method: King Root | SuperSUMe to change from kingroot to SuperSU |
Architecture: 32-bit
CPU: armeabi-v7a (qualcomm) 4-core 1ghz

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

#<src>                                                <mnt_point>  <type>  <mnt_flags and options>                     <fs_mgr_flags>
/dev/block/bootdevice/by-name/system         /system      ext4    ro,barrier=1,noatime,discard                         wait,check
/dev/block/bootdevice/by-name/userdata       /data        ext4    nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue,discard    wait,check,encryptable=/dev/block/bootdevice/by-name/encrypt
/dev/block/zram0             none         swap    defaults zramsize=268435456
/devices/soc.0/7864900.sdhci/mmc_host        /storage/external_SD   vfat    nosuid,nodev         wait,voldmanaged=external_SD:auto

Download Mode:
Power off
plug usb in
hold power and volume up at the same time

Recovery Mode:
hold power and volume down at the same time

So far I have been able to:

Root w/ Kingroot
Switch Kingroot to SuperSU via SuperSUME
Flash the Xposed Framework via Flashfire

DO NOT FLASH BOOT IMAGE OR CUSTOM ROM YOU WILL BRICK


I will upload the files I used to root and flash XPOSED if I can

Any luck on your LG Tribute 5 Boost phone?

I'm thinking of getting one or two for $20 new, but they're Boost locked pre-paid and I'd like to use them on TMO if I can unlock them and load a custom ROM...

 

[RolandStoner]

As of now I have been able to enable OEM unlock with android settings but It seems like its just for show. I have been unable to reboot to or flash the bootloader. Just bricks the device. Although even without a custom rom, the XPOSED framework takes care of most of my rom needs. All around this phone is a nice one imo. Im not sure if it can be used on T-Mobile, I will try to swap sims with my buddie when he gets out of work.

 

[glen5678]

As of now I have been able to enable OEM unlock with android settings but It seems like its just for show. I have been unable to reboot to or flash the bootloader. Just bricks the device. Although even without a custom rom, the XPOSED framework takes care of most of my rom needs. All around this phone is a nice one imo. Im not sure if it can be used on T-Mobile, I will try to swap sims with my buddie when he gets out of work.

That sux!
I just wanna use it on TMO for my mom because she's complaining about her Win10 phone not having many apps available. Lol

How did you OEM unlock the phone?

 

[RolandStoner]

That sux!
I just wanna use it on TMO for my mom because she's complaining about her Win10 phone not having many apps available. Lol

How did you OEM unlock the phone?

Open settings > about phone > software info (then tap build number 7 times after that go back and open developer options its right there, OEM Unlock.)

 

[wei2k16]

Hi, I just got this phone today. how do you unlock it? do you need to unlock it first before rooting it? where can I find this LG universal unlock calculator that might be able to unlock it?

 

[petermg]

Just quick FYI, I posted files to return this phone to stock here:
http://xdaforums.com/general/general/unbrick-stock-rom-lg-tribute-5-ls675-t3425408
Took me a while to find them so thought I'd share

 

[guest_2011]

Tribute 5 is the same as tracfone Treasure L51AL. Metro/tmob version has 1.5gb ram, everything else seems the same. Can i use latest Kingroot and then delete it and install Supersu Pro? I have the Treasure model.

 

[RolandStoner]

Tribute 5 is the same as tracfone Treasure L51AL. Metro/tmob version has 1.5gb ram, everything else seems the same. Can i use latest Kingroot and then delete it and install Supersu Pro? I have the Treasure model.

Yes, you can use kingroot to root the device, then SuperSUME to use supersu instead of kingroot.
Here are the files

Kingroot:
https://mega.nz/#!iZFGhSiS!91QXELuqzhrwp7edx3ZJp9I-4yJzkil9SwrSTVv0yTo
SuperSUME:
https://mega.nz/#!3IEQkAIY!rQV8MwhcY6ufdJER3K6JDsIfkrg02Zp3PqXnkeJCdZw

 

[RolandStoner]

Just quick FYI, I posted files to return this phone to stock here:
http://xdaforums.com/general/general/unbrick-stock-rom-lg-tribute-5-ls675-t3425408
Took me a while to find them so thought I'd share

Awesome, Thanks!

 

[guest_2011]

Yes, you can use kingroot to root the device, then SuperSUME to use supersu instead of kingroot.
Here are the files

Kingroot:
https://mega.nz/#!iZFGhSiS!91QXELuqzhrwp7edx3ZJp9I-4yJzkil9SwrSTVv0yTo
SuperSUME:
https://mega.nz/#!3IEQkAIY!rQV8MwhcY6ufdJER3K6JDsIfkrg02Zp3PqXnkeJCdZw

I tried the latest KR but it could not root. Don't understand how Tracfone can cripple it to make it different from K7/Tribute 5. I used v4.9.5 build 20160726 xda release (one click root)

 

[petermg]

Yes, you can use kingroot to root the device, then SuperSUME to use supersu instead of kingroot.
Here are the files

Kingroot:
https://mega.nz/#!iZFGhSiS!91QXELuqzhrwp7edx3ZJp9I-4yJzkil9SwrSTVv0yTo
SuperSUME:
https://mega.nz/#!3IEQkAIY!rQV8MwhcY6ufdJER3K6JDsIfkrg02Zp3PqXnkeJCdZw

I would recommend to NOT use SuperSUME! When I tried it, it made my phone unusable! That's why I had to find the stock ROM to fix my phone! After I fixed my phone by flashing the stock ROM I used KingRoot again to root my phone then I used the files and root.sh script with all the instructions found on this page
http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/
And was successful at replacing KingRoot with SuperSU. Just don't use the SuperSUME method!

 

[RolandStoner]

[/QRCODE][/QRCODE]

I would recommend to NOT use SuperSUME! When I tried it, it made my phone unusable! That's why I had to find the stock ROM to fix my phone! After I fixed my phone by flashing the stock ROM I used KingRoot again to root my phone then I used the files and root.sh script with all the instructions found on this page
http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/
And was successful at replacing KingRoot with SuperSU. Just don't use the SuperSUME method!

I just did a factory data reset and re-rooted / swapped. Worked for me? little bit of trouble getting kingroot to wipe tho.

 

[Thedarkwolf123]

Late

I would recommend to NOT use SuperSUME! When I tried it, it made my phone unusable! That's why I had to find the stock ROM to fix my phone! After I fixed my phone by flashing the stock ROM I used KingRoot again to root my phone then I used the files and root.sh script with all the instructions found on this page
~Omitted Due To New User Status~
And was successful at replacing KingRoot with SuperSU. Just don't use the SuperSUME method!

I didn't see this post until after i used SuperSU, The problem is I cant use FlashFire to install the exposed framework, plus the terminal editor method of replacing Kingroot didn't work, it kept telling me the path was invalid, no matter how many times i used it. Is there a way to Root the phone that doesn't even involve kingroot? Or a third way to replace Kingroot?

 

[RolandStoner]

I didn't see this post until after i used SuperSU, The problem is I cant use FlashFire to install the exposed framework, plus the terminal editor method of replacing Kingroot didn't work, it kept telling me the path was invalid, no matter how many times i used it. Is there a way to Root the phone that doesn't even involve kingroot? Or a third way to replace Kingroot?

Did you try SuperSUME? It replaces kingroot with one click. Super Effective. I will keep updating the first post on page 1 of this thread as I find out more about the device. I just discovered how that its possible to set SELinux to permissive on boot. SuperSUMe is right here http://goo.gl/Ox5Xw9

 

[Thedarkwolf123]

Did you try SuperSUME? It replaces kingroot with one click. Super Effective. I will keep updating the first post on page 1 of this thread as I find out more about the device. I just discovered how that its possible to set SELinux to permissive on boot. SuperSUMe is right here ~Ommitted due to New User Status~

I did use SuperSUME, But then I couldn't get rid of Kingroot, not even with Rom Toolbox Pro, Afterwards the phone became unresponsive and laggy and when I factory reset it, it was soft-bricked. I literally just flashed the stock firmware back onto it using petermg's method and it's like i just got it out the box (aside from Google verification)

---------- Post added at 07:18 PM ---------- Previous post was at 07:14 PM ----------

so apparently boost simply renamed the LG k7 to Tribute 5, I'm wondering if the recovery and bootloader unlock methods are the same? So far the only rooting method is still using Kingroot

 

[RolandStoner]

I did use SuperSUME, But then I couldn't get rid of Kingroot, not even with Rom Toolbox Pro, Afterwards the phone became unresponsive and laggy and when I factory reset it, it was soft-bricked. I literally just flashed the stock firmware back onto it using petermg's method and it's like i just got it out the box (aside from Google verification)

---------- Post added at 07:18 PM ---------- Previous post was at 07:14 PM ----------

so apparently boost simply renamed the LG k7 to Tribute 5, I'm wondering if the recovery and bootloader unlock methods are the same? So far the only rooting method is still using Kingroot

All I could find from LG was their unlock tool for the g2 and g3. Flashing the recovery results in a hard brick. I have only recovered from it once, thanks to SELinux, but I think that it was also the cause of the issue. I am playing with SELinux now to see if I can bypass it and flash a custom recovery. It seems to me like I would need to build a device custom boot.img recovery.img and a custom rom myself. If anybody knows what they are doing in that area I would help all I could. I tried using flashfire to flash a nightly for the G2 and failed. Flashfire tried it just got a flag saying that it was for the g2 and not the M1 (Thats the device ID i guess) Maybe building a custom cyanogenmod for the Lg Tribute so flashfire actually tries to flash. Ideas? recommendations?

 

[Thedarkwolf123]

All I could find from LG was their unlock tool for the g2 and g3. Flashing the recovery results in a hard brick. I have only recovered from it once, thanks to SELinux, but I think that it was also the cause of the issue. I am playing with SELinux now to see if I can bypass it and flash a custom recovery. It seems to me like I would need to build a device custom boot.img recovery.img and a custom rom myself. If anybody knows what they are doing in that area I would help all I could. I tried using flashfire to flash a nightly for the G2 and failed. Flashfire tried it just got a flag saying that it was for the g2 and not the M1 (Thats the device ID i guess) Maybe building a custom cyanogenmod for the Lg Tribute so flashfire actually tries to flash. Ideas? recommendations?

There's a thread on here that has TWRP working for the K7, a few people are saying it works for the tribute 5 as well, you should be able to find it by searching~ [REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies] ~ since im a new member I cant post the exact link.

 

[RolandStoner]

There's a thread on here that has TWRP working for the K7, a few people are saying it works for the tribute 5 as well, you should be able to find it by searching~ [REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies] ~ since im a new member I cant post the exact link.

I just attempted their method to no avail, Im thinking boost mobile is doing something to their phones, Bootloader always shows black and the device reboots normaly. Flashing the boot.img will result in a brick.. I have contacted boost mobile and they have told me that it is the manufacturers issue. I am thinking about trying to port cyanogenmod to our device and flashing it with flashfire, but need some help starting. I have time to devote to doing so and am looking for anyone else that wants to try with me for I have never ported a ROM before. Im not the most advanced user but I think I can do it with Cyanogenmods guides, They are very well documented.

Anybody Interested in this device and development PM me. Ill make an IRC channel if I get people to help. Will be fun!

 

[Thedarkwolf123]

Bootloader?

So I'm trying to unlock the bootloader, rerooted with kingroot (still unable to remove it btw) and have been trying to unlock the bootloader. But for some reason everything i try, from using recovery into it, using the rom toolbox and quickboot, the phone just resets normally. is there a button combination that can force it to load bootloader? or is my phone extremely special?

---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------

So I'm trying to unlock the bootloader, rerooted with kingroot (still unable to remove it btw) and have been trying to unlock the bootloader. But for some reason everything i try, from using recovery into it, using the rom toolbox and quickboot, the phone just resets normally. is there a button combination that can force it to load bootloader? or is my phone extremely special?

naturally im too late once again. but i still cant remove kingroot. I'd love to help port the recovery but i dont have steady access to a computer. pleas keep the thread updated though:good::good: