Porting to Samsung Galaxy Note 4 SM-N910P

doniks · 15 Sept 2017, 17:56

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

So I have made progress, I managed to find an un-official lineageOS repo for my phone, using that and a little trial and error I managed to get Halium to compile.

Niice! Which version?

I follow the halium porting guide, but when I get to the part that tells me to run the halium-install script, I keep getting an error saying that it "cant write 217 blocks, out of space?" Or something along those lines, not in front of my computer atm,

I remember there was another ubports forum conversation about a similar error message. Something about partition size settings ... I can't remember whether it was actually resolved, but see whether you can find that. Maybe it helps.

EDIT: found it
https://forums.ubports.com/topic/481/porting-to-motorola-moto-g-2013-lte
It seems it was related to the filesystem it was being built on. Weird!

tigerpro · 15 Sept 2017, 18:24

@doniks I got Halium 7.1 to build, 5.1 kept giving me the dirtyRect error so I decided against trying to compile that. I actually just found the thread you linked, google is such a pain cause it keeps searching for helium despite me typing halium. I checked the respective files on my system, I did like you had mentioned in that post and deleted the same file and ran make systemimage gave me a file that matches the size of my boardconfig.mk size. I will try flashing again when I get home, ssh can only do soo much when your not in front of the computer your sshed too lol

hans1977se · 15 Sept 2017, 18:45

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

google is such a pain cause it keeps searching for helium

You could give the alternatives a go. This one is quite good:
https://duckduckgo.com/

tigerpro · 15 Sept 2017, 18:47

@hans1977se yea I just usually default to google cause its what I use, duckduckgo is my fallback, someday I wont have to google Halium errors anymore lol

hans1977se · 15 Sept 2017, 18:57

@tigerpro yeah i know, i'm far worse with habits than i think i should be.

tigerpro · 15 Sept 2017, 19:00

@hans1977se arent we all? I am gonna keep searching if this flash attempt fails, I have a feeling my issue might be halium-install trying to copy the image to the wrong partition cause I tried flashing it with TWRP just out of curiosity, and it says the image is bigger than the partition (which explains the out of space) and TWRP only offers boot or recovery when I select the file, but since I just recompiled the system image it might have resolved itself, wont know until I get home to try it

hans1977se · 15 Sept 2017, 20:11

@tigerpro probably so in many cases.

I hope this works out for you. It would be quite nice with some Samsung phones running Ubuntu i think.

tigerpro · 15 Sept 2017, 21:14

@hans1977se thats my sentiment exactly. Dont get me wrong Android is nice and all, but it leaves alot to be desired for an OS, I have a working kernel (hybris-boot.img) so far, just gotta figure out the rest to make it all work now. Keep an eye out for a possible resolution to Halium, Im so close I can taste it lol

tigerpro · 15 Sept 2017, 21:37

Ok, this is weird, I did make systemimage earlier, file size matched at that time, now its 250-ish MB when it should be 300+, think I might have to just use the mkext4 program manually, Im doing make systemimage again just in case something happened when I wasnt looking, but if I have the same issue then I dunno, maybe try a different drive for the code compiling shrugs this is turning into a scooby doo mystery haha

hans1977se · 15 Sept 2017, 21:40

@tigerpro There are a lot of good things in Android, but i think it's not really for technical people who likes it better somewhere nicer off the mainstream.

Also i find it wrong to have someone constantly trying to watch you, 24/7, to find out how to make the most money out of your life.

tigerpro · 15 Sept 2017, 23:12

@hans1977se well the monitoring is easily fixed via VPN, I myself use one whenever Im using a site with sensitive info, an ad blocker like Ad Away works really well too for the ads, I just want something different cause honestly, Im not a big fan of the current mobile OS offerings, anyways, getting slightly OT, if the make systemimage messes up again, Ill use mkext4 (or whatever the command is)

doniks · 16 Sept 2017, 04:40

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

@hans1977se arent we all? I am gonna keep searching if this flash attempt fails, I have a feeling my issue might be halium-install trying to copy the image to the wrong partition cause I tried flashing it with TWRP just out of curiosity, and it says the image is bigger than the partition (which explains the out of space) and TWRP only offers boot or recovery when I select the file, but since I just recompiled the system image it might have resolved itself, wont know until I get home to try it

That reminds me. Did you do this step?

https://docs.halium.org/en/latest/porting/index.html#include-your-device-in-fixup-mountpoints-script

What changes did you make to that script?

hans1977se · 16 Sept 2017, 08:36

@tigerpro I think it is a very complex thing to get the complete view of, but what i wanted to say is that i think it's conceptually wrong to constantly track people to get the most money out of you (or in any other way they might do or be doing in the future). You might forget to use your VPN or did not think it was necessary to use it at a particular time, and once they have your information they have it and once they have it their policy could change or a hacker can get hold of it.

Who knows what will happen, but this is one reason why i'm here and hope that your port as well as other people's ports will be successful and make Ubuntu wider available.

tigerpro · 16 Sept 2017, 11:58

@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

@hans1977se arent we all? I am gonna keep searching if this flash attempt fails, I have a feeling my issue might be halium-install trying to copy the image to the wrong partition cause I tried flashing it with TWRP just out of curiosity, and it says the image is bigger than the partition (which explains the out of space) and TWRP only offers boot or recovery when I select the file, but since I just recompiled the system image it might have resolved itself, wont know until I get home to try it

That reminds me. Did you do this step?

https://docs.halium.org/en/latest/porting/index.html#include-your-device-in-fixup-mountpoints-script

What changes did you make to that script?

@doniks I did do that step, its a bit confusing on which partitions they want cause I used all of the others to try and figure out a pattern, then decided to just put them all in there, Ill post the full section I added when I get a chance.

#=== EDIT ===#

@doniks this is the stuff I added to fix mountpoints, im not sure whats needed and what isnt, but I think I have it entered correctly

"trltespr")
sed -i
-e 's block/platform/msm_sdcc.1/by-name/aboot mmcblk0p7 '
-e 's block/platform/msm_sdcc.1/by-name/apnhlos mmcblk0p1 '
-e 's block/platform/msm_sdcc.1/by-name/boot mmcblk0p17 '
-e 's block/platform/msm_sdcc.1/by-name/cache mmcblk0p25 '
-e 's block/platform/msm_sdcc.1/by-name/carrier mmcblk0p26 '
-e 's block/platform/msm_sdcc.1/by-name/dbi mmcblk0p5 '
-e 's block/platform/msm_sdcc.1/by-name/ddr mmcblk0p6 '
-e 's block/platform/msm_sdcc.1/by-name/efs mmcblk0p13 '
-e 's block/platform/msm_sdcc.1/by-name/fota mmcblk0p19 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs1 mmcblk0p14 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs2 mmcblk0p15 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 mmcblk0p10 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefsc mmcblk0p16 '
-e 's block/platform/msm_sdcc.1/by-name/misc mmcblk0p20 '
-e 's block/platform/msm_sdcc.1/by-name/modem mmcblk0p2 '
-e 's block/platform/msm_sdcc.1/by-name/pad mmcblk0p11 '
-e 's block/platform/msm_sdcc.1/by-name/param mmcblk0p12 '
-e 's block/platform/msm_sdcc.1/by-name/persdata mmcblk0p23 '
-e 's block/platform/msm_sdcc.1/by-name/persist mmcblk0p22 '
-e 's block/platform/msm_sdcc.1/by-name/recovery mmcblk0p18 '
-e 's block/platform/msm_sdcc.1/by-name/rpm mmcblk0p8 '
-e 's block/platform/msm_sdcc.1/by-name/sbl1 mmcblk0p3 '
-e 's block/platform/msm_sdcc.1/by-name/sbl1bak mmcblk0p4 '
-e 's block/platform/msm_sdcc.1/by-name/ssd mmcblk0p21 '
-e 's block/platform/msm_sdcc.1/by-name/system mmcblk0p24 '
-e 's block/platform/msm_sdcc.1/by-name/tz mmcblk0p9 '
-e 's block/platform/msm_sdcc.1/by-name/userdata mmcblk0p27 '
"$@"
;;

Let me know if I should change any of this

doniks · 16 Sept 2017, 14:34

@tigerpro ok. How did you decide which partition number to put where, eg., how did you decide to pick 17, 24 and 27 for boot, system and userdata? What are the partition sizes? Whats the content of your board config file? What is the exact error message you get?

tigerpro · 16 Sept 2017, 14:59

@doniks I was using the Sailfish HADK to figure that out, I forget what the actual command was, but I did "adb shell" then another command which output that info, I copy and pasted from my terminal into the fix mountpoints file then formatted it to the correct format for the file. I tried to manually adb push the system.img to the same destination the script was (/data based on my understanding) which worked, but that juat makes my phone boot loop so I think I might be missing something, I looked at the kmesg file as well, the last entry it had was "booting linux" but thats also not happening otherwise I would be posting files lol

doniks · 16 Sept 2017, 15:47

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

@doniks I was using the Sailfish HADK to figure that out, I forget what the actual command was, but I did "adb shell" then another command which output that info, I copy and pasted from my terminal into the fix mountpoints file then formatted it to the correct format for the file.

Ok

I tried to manually adb push the system.img to the same destination the script was (/data based on my understanding) which worked,

Hang on. So you DO have a system.img file? I thought make systemimage fails?! (Can you still post that error?)

but that juat makes my phone boot loop so I think I might be missing something, I looked at the kmesg file as well, the last entry it had was "booting linux" but thats also not happening otherwise I would be posting files lol

Maybe post the whole kmesg. Boot loop could be all kinds of other problems.

tigerpro · 16 Sept 2017, 15:53

@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:

I tried to manually adb push the system.img to the same destination the script was (/data based on my understanding) which worked,

Hang on. So you DO have a system.img file? I thought make systemimage fails?! (Can you still post that error?)

I originally was having an error with "mka systemimage" I tried it after I did a make clean cause I started to randomly get an error with "mka mkbootimg" so I just did a make clean (which failed, Had to manually delete a file for it to succeed) after that, I repo synced, and everything started to work again, so no idea on that one, but yes it does generate a system.img now, wether or not its correct is a different story.

but that juat makes my phone boot loop so I think I might be missing something, I looked at the kmesg file as well, the last entry it had was "booting linux" but thats also not happening otherwise I would be posting files lol

Maybe post the whole kmesg. Boot loop could be all kinds of other problems.

full kmsg:

daemon not running. starting it now on port 5037 *
daemon started successfully *
{490562} sbl1_ddr_init:: ret[0xffff]
{491080} sbl1_ddr_zi_init:: ret[0xfffe]
{492880} @@ pm power on reason : 0x20000000c1
{492910} @@ reset status : 0x0
{492941} clock_init, Start
{493185} clock_init, Delta
{493185} boot_dload_dump_tz:: Not Allowed!!
{493246} boot_fota_restore_partition, Start
{494740} boot_fota_restore_partition, Delta
{494832} Image Load, Start
{656573} Tz Execution, Start
{821151} Tz Execution, Delta
{821212} boot_fota_close_hdev, Start
{821243} boot_fota_close_hdev, Delta
{821670} RPM loading is successful.
{821700} Image Load, Start
{885689} Signal PBL to Jump to RPM FW
{887092} Image Load, Start
{911431} WDT Execution, Start
{911736} WDT Execution, Delta
{911797} Image Load, Start
{1197247} sbl1_efs_handle_cookies, Start
{1197430} sbl1_efs_handle_cookies, Delta
{1197460} RPM sync cookie updated
{1201242} SBL1, End
welcome to lk

platform_init()
target_init()
HW REV12 : (1, 1, 0, 0)
HW_REV_READ 12
sec_init: Start
check power key with 0x283b389e
Power on status : 0x20000000c1 (HARD RESET, Cable Power on, Keypad Power on)
[MUIC] MUIC initialized !
muic_driver_init
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
[MUIC] init_microusb_ic: CONTROL1:0x00
[MUIC] init_microusb_ic: CONTROL1:0x00
[MUIC] init_microusb_ic: CONTROL2:0x3b
[MUIC] init_microusb_ic: CONTROL2:0x3b
MMC Product Name: R218MA
MMC_FIRMWARE_VERSION: 0x5
eMMC CMD21 tuning DATA error handled. status = 0x20
Done initialization of the card

MODEL_NAME:{{SM-N910P}}
eMMC_SERIAL_NUMBER:{{150100523231384d4100110ddabf1200}}

aboot_init()
REBOOT MODE : 0x283b389e
ENABLE LVS1 for sensorhub
ENABLE LDO9
oem_panel_select panel_id = 3
target_ldo_ctrl ++, enable = 1
Setting LDO26 1
muic_get_device
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
get_charger: hw_rev(0xc)
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
aboot_dev_charging_init : cable_status(1), cable_type(0)
max77823_get_battery_detect : battery(0)
aboot_dev_charging_init, [battery] batt_id_value (0)
max77823_set_charger_state: buck(1), chg(0), reg(0x04)
get_charger: hw_rev(0xc)
[battery] external charger init
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
max77823_set_fast_charging_current_data : fast charging current 460mA(0x09)
max77823_set_charging_current_limit_data : input current limit: reg = c0, 460mA(0x0d)
fuel_gauge_read_vcell: VCELL(3819), data(0xbefa)
max77823_set_charger_state: buck(1), chg(0), reg(0x04)
aboot_dev_charging_init : vcell(3819), count(0)
Setting 12
Setting 2
Setting 22
target_ldo_ctrl --
Panel power on done
target_panel_clock
first_qcom_dload_magic=0xffffffff,second_qcom_dload_magic=0xffffffff
mdp_gdsc_ctrl = 1
ERROR: splash Partition invalid
Config MIPI_CMD_PANEL.
pinfo->mipi.dual_dsi = 1
target_panel_reset ++ enable=1
target_panel_reset ...0
target_panel_reset --
Panel Reset--
target_panel_reset ++ enable=1
target_panel_reset ...0
init_fuelgauge: Start!!
muic_get_jig_status
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
init_fuelgauge: Battery type : SDI, capacity: 6600, status: 128
init_fuelgauge: Already initialized (0x19c8, SDI type)
get_charger: hw_rev(0xc)
max77823_set_charger_state: buck(1), chg(1), reg(0x05)
fuel_gauge_read_vcell: VCELL(3815), data(0xbec0)
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
muic_get_jig_status
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
check_low_power : rb=0, jig=0, ct=1, vcell=3815
skip check low power
vibrator started
set_vibe_tonz
[tspdrv]nForce===7
vibe_set_pwm_freq
VIBRATOR is ENABLED :::
Haptic ENABLED :::
target_panel_reset --
Panel Reset Done---
mdss_dual_dsi_cmds_tx---4
mdss_dual_dsi_cmds_tx---1
mdss_dual_dsi_cmds_tx---1
mdss_dual_read_manufacture_id : id1 : 0x50 id2 : 0x20 id3 : 0x9
mdss_dual_dsi_cmds_tx---19
vibrator stopped
set_vibe_tonz
VIBRATOR is DISABLED :::
sec_init:END
mdss_dual_dsi_cmds_tx---3
mdss_dsi_cmd_mode_config
mdss_dsi_cmd_mode_config
pinfo->mipi.dual_dsi = 1 1
mipi_pinfo.num_of_display_on = 1
mdss_dual_dsi_cmds_tx---1
BOOTLOADER VERSION : N910PVPU4COJ6
before aboot_check_mode() , boot_mode=0x0
Get DATA success.

react_lock flag(id:2)
Get DATA success.

react_lock flag(id:10)
init react lock flag 0x0
init cc mode flag 0x0
check_boot_mode = key Down[0], Up[1]
cable_type =0x0, reboot_mode=0x283b389e
check_ramdump_mode :: k_param.debuglevel[0x574f4c44]::k_param.cp_debuglevel[0x0]
check_pit_integrity: invalid pit magic code.(0x0)
SECURE : Signature verification...
SECURE : Signature verification succeed
before check_lpm_mode
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
is_reboot_case =0
cable_status = 1
enter normal booting mode
AST_POWERON
display_boot_image ++
Corrupt JPEG data: u extraneous bytes before marker 0x02x
Invalid JPEG file structure: two SOI markers
exit
Invalid JPEG file structure: two SOF markers file structure: two SOI markers
exit
Didn't expect more than one scanùú
exit
after aboot_check_mode()
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
fuel_gauge_read_vcell: VCELL(3827), data(0xbf64)
muic_get_jig_status
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
fuel_gauge_read_soc: SOC(45), data(0x2dc6)
check_low_battery : rb=0, jig=0, vcell=3827, soc=45
reboot_mode = 0x283b389e, boot_mode = 3, por = 0xc1
<LP> RECOVERY BOOTING.....
LK Area: 0xF800000 - 0xFA00000
Kernel Addr: 0x8000
Ramdisk Addr: 0x2600000
Second Addr: 0xF00000
Tags Adddr: 0x2400000
use_signed_kernel=0, is_unlocked=0, is_tampered=0.
Loading boot image (11153408): start
Loading boot image (11153408): done
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 0]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 1]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 2]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 3]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 4]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 6]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 7]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 8]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 9]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 10]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 12]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 13]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 14]
board[model_info:03010008, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 15]
ERROR: Unable to find suitable device tree for device model_info:0x03010008
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 0]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 1]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 2]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 3]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 4]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 6]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 7]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 8]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 9]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 10]
board[model_info:b208ff01, sec_rev:12], dtb[dt_model_info:b208ff01, dt_board_rev 12]
matched device tree : b208ff01, rev12
boot image size(14549248)
SECURE: signature check fail. (recovery.img)
init_ddi_data: usable ddi data.
[TIMA boot measurement] : Old/non-CL device - KNOX warranty void
<LP> Set Warranty Bit : recovery
[TIMA trusted boot]: SMC call to set the warranty violation fuse succeeded
SET WV: API Status 0x0
WB : Already SET 2, VER : N910PVPU4COG5
WP 3, 1
Loading keystore failed status 5 cmdline = 'console=null androidboot.hardware=qcom androidboot.bootdevice=msm_sdcc.1 user_debug=31 msm_rtb.filter=0x37 dwc3_msm.cpu_to_affin=1'
PCD Detect GPIO Status = 1
Target_cont_splash=1
PCD Detect GPIO Status = 1
WV: API Status 0x0
WV: API Status 0x0
muic_get_jig_status
[MUIC] microusb_get_attached_device: STATUS1:0x1f, 2:0x41
[MUIC] microusb_get_attached_device: chgtyp+adc: 0x11f
RUSTPROOF : k_param.uartsel = 0x3
RUSTPROOF : Disable uart.
SET HV Charge mode : Disable (0x3)
WV: API Status 0x0
Warranty Bit Set - Blowing KAP_VIOLATION_FUSE

Booting Linux
TZ informed of recovery status: 1
pm8x41_get_is_cold_boot: cold boot
cmdline: console=null androidboot.hardware=qcom androidboot.bootdevice=msm_sdcc.1 user_debug=31 msm_rtb.filter=0x37 dwc3_msm.cpu_to_affin=1 cont_splash=1 androidboot.sec_atd.tty=/dev/ttyHSL0 sec_log=0x100000@0x10000008 sec_dbg=0x80000@0x10100008 sec_debugenable subcmdline
Updating device tree: start
Updating device tree: done
Turn off MIPI_CMD_PANEL.
PCD Detect GPIO Status = 1
Target_cont_splash=1
PCD Detect GPIO Status = 1
Target_cont_splash=1
PCD Detect GPIO Status = 1
Target_cont_splash=1
Continuous splash enabled, keeping panel alive.
booting linux @ 0x8000, ramdisk @ 0x2600000 (4847054), tags/device tree @ 0x2400000
[eMMC] WP status = 0x00, addr = 0x0, (0x01: Temporary WP; 0x02: Power_on WP)
[eMMC] Power on Write Protect set for sector [0 ~ 0x6000000]
[eMMC] WP status = 0x02, addr = 0x0, (0x01: Temporary WP; 0x02: Power_on WP)
WV: API Status 0x0
Booting Linux

let me know if you see something I missed, I never get a splash screen, or anything, it either just sits there and does nothing or boot loops, system.img being manually pushed is the only difference I have noticed, although my last attempt before going to bed last night was just a stuck screen, after I had pushed the system.img manually so I dunno whats going on.

tigerpro · 16 Sept 2017, 20:00

ok so I just played around with the system.img file, if I run "mka systemimage" and try to mount it, it fails saying invalid partition type, if I run the make_ext4fs command on it, i can then mount it, but it is empty, (kind of expected as make_ext4fs is a ext4 format tool) and trying it the way the script has it doesnt work either, so now I think I have it narrowed down to the system.img file being corrupted or not compiling right. @doniks was this the issue you were experiencing with TWRP 3.1.1? if so I might be SOL from here cause my device only has 3.1.0 or 3.1.1 according to the TWRP website.

doniks · 17 Sept 2017, 20:05

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

ok so I just played around with the system.img file, if I run "mka systemimage" and try to mount it, it fails saying invalid partition type,

I think the android system.img is some unusual image format. Read the halium-install script. There you see how they transform it into something else!

if I run the make_ext4fs command on it, i can then mount it, but it is empty, (kind of expected as make_ext4fs is a ext4 format tool)

Well, yeah. It is expected to be empty afterwards.

and trying it the way the script has it doesnt work either, so now I think I have it narrowed down to the system.img file being corrupted or not compiling right.

I could imagine that an incomplete, or corrupt, or even an absent system.img might all lead to a rebooting device. Do you know how far the boot process goes for you so far? Does it enter the rootfs. Do you have telnet access? ssh? Which ip? Can you watch the usb serial number? What values does it go through?

I can't make much sense of your kmesg above. Maybe it is only the "late" part of the boot process after it has switched to the rootfs. If that is the case you can check my thread for how to NOT start the lxc container with the system.img. just as a stepping stone in debugging problems in that container

@doniks was this the issue you were experiencing with TWRP 3.1.1? if so I might be SOL from here cause my device only has 3.1.0 or 3.1.1 according to the TWRP website.

No I don't think you need to worry here. You only need twrp to have ANY recovery that allows you to adb in. You can probably use any other recovery you can dig up on xda for your device. I think my problem was just that the other version wouldn't install or something.