Decrypting misc to get model number for TWRP/ROMs - LG V30 Questions & Answers

Hey everyone,
I need some community help. I wanna find out which part of the misc partition tells the kernel the model (and also the color lol). Stock kernel logs this on boot (even on non stock based roms), but i couldnt find where it reads it in the kernel source
Thats where i need the community. It logs that it reads the hwinfo from the misc partition, but unlike older phones, it isnt in plain text anymore.
I need some more samples of misc partitions from various devices (and colors, if possible) to find out which bit in that partitions is for what.
My goal with this:
Make the recovery set on boot which model it is running on
Do the same for future ROMs
But misc should (or atleast in the past) contain also wifi/bt mac adresses. Just giving you the information here, in case you dont want that to be publicy shared.
Instructions on how to get the image:
Open terminal app (any will do, even adb would work)
su <enter> (and grant permissions)
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_<model>_<color>.img
Examples:
Code:
su
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930_blue.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930_silver.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930g_black.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_us998_silver.img
If you dont care about your wifi/bt mac possibly be made public, attach it on a post, otherwise send me a PM
Thanks in advance

---

It doesn't get that info from misc, it gets it from the bootloader.
-- Brian

---

runningnak3d said:
It doesn't get that info from misc, it gets it from the bootloader.
-- Brian
Click to expand...
Click to collapse
Ohhh. You sure about that though?
have this in my logs:
Code:
03-04 01:28:10.053 0 0 I [ 0.788138 / 01-01 00:00:00.779][4] 0: ftm_get_item.
03-04 01:28:10.053 0 0 I [ 0.788170 / 01-01 00:00:00.779][4] suffix: LGH930.ADECBL, suffix_length : 13
03-04 01:28:10.053 0 0 I [ 0.788198 / 01-01 00:00:00.779][4] suffix: LGH930.ADECBL, Color :BL
03-04 01:28:10.053 0 0 I [ 0.788211 / 01-01 00:00:00.779][4] BL: color.
03-04 01:28:10.053 0 0 I : [ 0.788224 / 01-01 00:00:00.779][4] UFS SAMSUNG
03-04 01:28:10.053 0 0 I [ 0.788276 / 01-01 00:00:00.779][4] bootcmd_set_one_binary: bootcmd_set_one_binary ** bootcmd_set_one_binary
03-04 01:28:10.053 0 0 I [ 0.788321 / 01-01 00:00:00.779][4] lge_one_binary_read_flex_gpio: [FLEX_GPIO] flex_gpio_sum[0]
03-04 01:28:10.053 0 0 I : [ 0.788350 / 01-01 00:00:00.779][4] id = 103 get_ftm_one_binary_hwinfo()
03-04 01:28:10.053 0 0 I [ 0.788393 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: HWINFO from misc partition (2)
03-04 01:28:10.053 0 0 I [ 0.788428 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: version = 0x10004
03-04 01:28:10.053 0 0 I [ 0.788465 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: model_name = LG-H930
03-04 01:28:10.053 0 0 I [ 0.788518 / 01-01 00:00:00.779][4] lge_one_binary_copy_hwinfo: model_name = LG-H930 , misc.model_name = LG-H930
03-04 01:28:10.053 0 0 I [ 0.788557 / 01-01 00:00:00.779][4] lge_one_binary_init: use HWINFO from misc partition
03-04 01:28:10.053 0 0 I [ 0.788595 / 01-01 00:00:00.779][4] lge_one_binary_init: Model Name = LG-H9 -> LG-H930
03-04 01:28:10.053 0 0 I [ 0.788640 / 01-01 00:00:00.779][4] bootcmd_add_pair: already exist key & value(model.name, LG-H930)
03-04 01:28:10.053 0 0 I [ 0.788681 / 01-01 00:00:00.779][4] lge_one_binary_get_sim_num: sim_num return value = 1
Thats why i thought its still in misc, but instead of plain text, just kinda encrypted.
But i suppose that would make things way easier
(as long as /proc/cmdline is always and as early as possible available)
Just checked that on my H930, has model number and so on set, just have to make sure it also gets set appropriate on the LOS builds (and twrp)

---

You are definitely correct. I apologise, my info is out of date when it comes to the V30. I do know that (as you saw) the information is available from the bootloader as well.
You should be able to parse /proc immediately after the kernel boots and init starts, so I still think that is the way to go.
-- Brian

---

Yeah, will do it that way
probably just gonna do it with an init script... getting familiar with shell scripts now xD
Annoying though i have to use sh and cant use bash commands... Most solutions i find are for bash, but i guess i found something that works with sh