LG K7 Custom ROM?

goitalone · Oct 5, 2016 at 12:34 AM

Just about guarantee there will be no ROMs for this phone

czarsuperstar@gmail.com · Oct 6, 2016 at 9:26 PM

goitalone said:
Just about guarantee there will be no ROMs for this phone

I sold my phone. I was tired of all the complaining. Before getting this phone I never knew about building recoveries but I am a pro now. I have 3 Twrps for the k7 ,surnia and the ms345
Reading is the key. @Goatitalone you have been so helpful in these forums. You should be a recognized contributor. I had to get rid of the phone. Twrp team never got back to me even after I follow procedure. So I am finished. But if anyone wants to take over I'm all for it. I have a test twrp because I may have figured out the problem @TheOddTaco was having. The K7 is a soc.0 device (system on chip) but the paths are not set right. The K7 is a /dev/block/platform/7824900.sdhci/by-name/system so I hope this helps anyone. Czar

TheOddTaco · Oct 8, 2016 at 2:32 AM

[email protected] said:
I sold my phone. I was tired of all the complaining. Before getting this phone I never knew about building recoveries but I am a pro now. I have 3 Twrps for the k7 ,surnia and the ms345
Reading is the key. @Goatitalone you have been so helpful in these forums. You should be a recognized contributor. I had to get rid of the phone. Twrp team never got back to me even after I follow procedure. So I am finished. But if anyone wants to take over I'm all for it. I have a test twrp because I may have figured out the problem @TheOddTaco was having. The K7 is a soc.0 device (system on chip) but the paths are not set right. The K7 is a /dev/block/platform/7824900.sdhci/by-name/system so I hope this helps anyone. Czar

in the fstab?

czarsuperstar@gmail.com · Oct 8, 2016 at 2:39 AM

TheOddTaco said:
in the fstab?

Yes the test image is with this path. Did you make a log?

czarsuperstar@gmail.com · Oct 8, 2016 at 5:49 PM

I don't have the phone anymore will one of the testers please let me know about any issues.

Flintstone796 · Sep 20, 2016 5 1 0

jonthenome said:
wh weat do you mean bootloader cannot be unlocked. Mine has been unlocked for months. I rooted at that point using lingo then replacing with SuperSU. I hAve linked apps to do and partitioned as so now I have 6 gigs of usable internal and 15 or so on external with large chunk for swapping. I have made recoveries. Broke Google apps. Fixed gapps. Restored to my recovery twice all while phone says bootloader status unlocked on bootloader. Is this just half added or something? I did most though AFB and it did fight me....

weDo you happen to have a copy of the google play services for this model? Having issues with it after flash to cm13

pikagunmike2 · Oct 13, 2016 at 4:01 PM

Flintstone796 said:
weDo you happen to have a copy of the google play services for this model? Having issues with it after flash to cm13

You have cm13 running on lg k7? Is everything working?

BigBxcks · Oct 13, 2016 at 9:44 PM

Flintstone796 said:
weDo you happen to have a copy of the google play services for this model? Having issues with it after flash to cm13

can I have a crack at that CM I would like to test please...

Sent from my LGE LGMS330 using XDA Labs

pikagunmike2 · Oct 13, 2016 at 9:50 PM

Yeah me too, and also what xda app are you using? There's a few of em

BigBxcks · Oct 13, 2016 at 10:06 PM

pikagunmike2 said:
Yeah me too, and also what xda app are you using? There's a few of em

I use the one from the Play Store if you were asking me

Sent from my LGE LGMS330 using XDA Labs

pikagunmike2 · Dec 28, 2015 296 30 0

BigBxcks said:
I use the one from the Play Store if you were asking me

Lol yeah I know but there's like 3 of em that I've seen

pikagunmike2 · Oct 15, 2016 at 2:17 AM

Flintstone796 said:
weDo you happen to have a copy of the google play services for this model? Having issues with it after flash to cm13

Do you have a running cm13 on lg k7????

WoodEe23 · Oct 17, 2016 at 5:46 PM

Arent u glad thats wrong now

goitalone said:
Can't unlock bootloader on this version, so there will never be a custom ROM, because TWRP cannot be flashed, because bootloader cannot be unlocked : (

Sent from my LGMS330 using XDA-Developers mobile app

Now the bootloaders unlocked...TWRP...XPOSED YAY

pikagunmike2 · Dec 28, 2015 296 30 0

WoodEe23 said:
Now the bootloaders unlocked...TWRP...XPOSED YAY

Can someone please tell what the he'll xposed is for? Cuz so far I've only seen it change the icons on my notifications bar and nothing else except for colors of some stuff, I though exposed was supposed to be like the Cydia of Android that can give you a new ui type **** lol

Bughora · Oct 16, 2016 26 8 0

If anyone is working on the development of anything LG K7-specific, I made a Discord:

discord (dot) gg/PVtCy7A
(Can't post links until 10 posts)

I'm currently trying to get CM13 working on it but so far no luck, if anyone else has figured it out, please let me know.

TheOddTaco · Oct 19, 2016 at 7:44 PM

Bughora said:
If anyone is working on the development of anything LG K7-specific, I made a Discord:

discord (dot) gg/PVtCy7A
(Can't post links until 10 posts)

I'm currently trying to get CM13 working on it but so far no luck, if anyone else has figured it out, please let me know.

u stuck at the LG Logo when flashed?
cuz thats the issue im havin for a long time.

Bughora · Oct 19, 2016

TheOddTaco said:
u stuck at the LG Logo when flashed?
cuz thats the issue im havin for a long time.

Damn, bro I've been trying to find you but I guess you changed your Twitter name. Nah I'm stuck at trying to get all the partition sizes so that I can build the recoveryimage and kernel.

Also, I was looking at your source and was wondering how you got the proprietary blobs? I was looking at your extract_files.sh but I seemed to be for a different device

Anyway my issue is BoardConfig.mk is asking for:

Code:

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072

There is no /proc/mtd but there is /proc/partitions which looks like this:

Code:

major minor  #blocks  name

 253        0     359144 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       8192 mmcblk0p31
 259        0      16384 mmcblk0p32
 259        1      16384 mmcblk0p33
 259        2      16384 mmcblk0p34
 259        3      24576 mmcblk0p35
 259        4       8192 mmcblk0p36
 259        5    2584576 mmcblk0p37
 259        6     204800 mmcblk0p38
 259        7    4616192 mmcblk0p39
 259        8       8175 mmcblk0p40
 179       32       4096 mmcblk0rpmb
 179       64   31166976 mmcblk1
 179       65   31162880 mmcblk1p1

And according to "ls -l /dev/block/platform/7824900.sdhci/by-name/ " the scheme is

Code:

lrwxrwxrwx root     root              1970-01-04 06:41 DDR -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              1970-01-04 06:41 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-01-04 06:41 abootbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-01-04 06:41 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root     root              1970-01-04 06:41 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root     root              1970-01-04 06:41 config -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-01-04 06:41 devinfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-01-04 06:41 drm -> /dev/block/mmcblk0p28
lrwxrwxrwx root     root              1970-01-04 06:41 eksst -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-01-04 06:41 encrypt -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-01-04 06:41 factory -> /dev/block/mmcblk0p35
lrwxrwxrwx root     root              1970-01-04 06:41 fota -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-01-04 06:41 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-01-04 06:41 fsg -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-01-04 06:41 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root     root              1970-01-04 06:41 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-01-04 06:41 laf -> /dev/block/mmcblk0p32
lrwxrwxrwx root     root              1970-01-04 06:41 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root     root              1970-01-04 06:41 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-04 06:41 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-01-04 06:41 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-01-04 06:41 mpt -> /dev/block/mmcblk0p36
lrwxrwxrwx root     root              1970-01-04 06:41 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root     root              1970-01-04 06:41 raw_resources -> /dev/block/mmcblk0p26
lrwxrwxrwx root     root              1970-01-04 06:41 raw_resourcesbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root     root              1970-01-04 06:41 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              1970-01-04 06:41 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root     root              1970-01-04 06:41 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-04 06:41 rpmbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-04 06:41 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-04 06:41 sbl1bak -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              1970-01-04 06:41 sec -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-01-04 06:41 sns -> /dev/block/mmcblk0p29
lrwxrwxrwx root     root              1970-01-04 06:41 spare1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-01-04 06:41 spare2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              1970-01-04 06:41 ssd -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-01-04 06:41 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root     root              1970-01-04 06:41 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-04 06:41 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-01-04 06:41 userdata -> /dev/block/mmcblk0p39

TheOddTaco · Oct 19, 2016 at 7:56 PM

Bughora said:
Damn, bro I've been trying to find you but I guess you changed your Twitter name. Nah I'm stuck at trying to get all the partition sizes so that I can build the recoveryimage and kernel.

Also, I was looking at your source and was wondering how you got the proprietary blobs? I was looking at your extract_files.sh but I seemed to be for a different device

really? i still have the old files on google drive ill changed the extract-files.sh on github.

Bughora · Oct 16, 2016 26 8 0

TheOddTaco said:
really? i still have the old files on google drive ill changed the extract-files.sh on github.

Thanks, that would help me out a lot. So stressful trying to make sense of all this. Pleas let me know if you can help me make sense of this:

Code:

build/core/tasks/kernel.mk:361: warning: overriding recipe for target '/home/sven/android/system/out/target/product/m1/kernel'
build/core/Makefile:46: warning: ignoring old recipe for target '/home/sven/android/system/out/target/product/m1/kernel'
Target boot image: /home/sven/android/system/out/target/product/m1/boot.img
/home/sven/android/system/out/target/product/m1/boot.img maxsize=-253440 blocksize=135168 total=8388608 reserve=270336
error: /home/sven/android/system/out/target/product/m1/boot.img too large (8388608 > [16896 - 270336])
build/core/Makefile:583: recipe for target '/home/sven/android/system/out/target/product/m1/boot.img' failed
make: *** [/home/sven/android/system/out/target/product/m1/boot.img] Error 1
make: *** Deleting file '/home/sven/android/system/out/target/product/m1/boot.img'

#### make failed to build some targets (57 seconds) ####

Is the output from "make recoveryimage"

TheOddTaco · Oct 19, 2016 at 8:10 PM

Bughora said:

Thanks, that would help me out a lot. So stressful trying to make sense of all this. Pleas let me know if you can help me make sense of this:

Code:

build/core/tasks/kernel.mk:361: warning: overriding recipe for target '/home/sven/android/system/out/target/product/m1/kernel'
build/core/Makefile:46: warning: ignoring old recipe for target '/home/sven/android/system/out/target/product/m1/kernel'
Target boot image: /home/sven/android/system/out/target/product/m1/boot.img
/home/sven/android/system/out/target/product/m1/boot.img maxsize=-253440 blocksize=135168 total=8388608 reserve=270336
error: /home/sven/android/system/out/target/product/m1/boot.img too large (8388608 > [16896 - 270336])
build/core/Makefile:583: recipe for target '/home/sven/android/system/out/target/product/m1/boot.img' failed
make: *** [/home/sven/android/system/out/target/product/m1/boot.img] Error 1
make: *** Deleting file '/home/sven/android/system/out/target/product/m1/boot.img'

#### make failed to build some targets (57 seconds) ####

Is the output from "make recoveryimage"

on your BoardConfig.mk, change your BOARD_BOOTIMAGE_PARTITION_SIZE to 25165824

i updated the extract-files.sh and setup files.sh on github

LG K7 Custom ROM?

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member