Galaxy S5 SM-G900F partition table

Search This thread

thehacker911

Inactive Recognized Developer
Jan 15, 2013
486
1,301
Gangkofen
Google Pixel 7 Pro
Build with Gcc 4.7 -- kernel not booting.

Build with Gcc 4.8.3 -- kernel not booting.

Build with Gcc 4.9 -- kernel not booting.

Build with Graphit enable -- kernel not booting.

Build without Graphite -- kernel not booting.
@Gnome:

Not booting...

Gesendet von meinem SM-G900F mit Tapatalk
 
Last edited:

Gnome

Senior Member
Jul 2, 2013
2,799
7,304
Red Light District
Build with Gcc 4.7 -- kernel not booting.

Build with Gcc 4.8.3 -- kernel not booting.

Build with Gcc 4.9 -- kernel not booting.

Build with Graphit enable -- kernel not booting.

Build without Graphite -- kernel not booting.

Gesendet von meinem SM-G900F mit Tapatalk

So it just goes to download mode automatically? Or just a black screen, cause if it goes to download mode, something is definitely wrong.
 

friedrich420

Senior Member
Dec 25, 2011
8,698
24,008
The Land of Whatever
This is what I did..
Compiled the zimage from the G900F sources using Linaro 4.7
I grabbed stock G900F NCE kernel, unpacked it, replaced zimage with my newly compiled one, made changes to ramdisk, repacked it and it booted...
 

Gnome

Senior Member
Jul 2, 2013
2,799
7,304
Red Light District
it boots? zImage only right?

Can someone try this please: Link

I made an anykernel format, here's the kernel link, this should use current ROM's Ramdisk: Link
 
Last edited:

thehacker911

Inactive Recognized Developer
Jan 15, 2013
486
1,301
Gangkofen
Google Pixel 7 Pro
Only zimage use this for default.prop

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.security.ams.enforcing=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.adb.secure=0
persist.sys.strict_op_enable=false
persist.sys.whitelist=/system/etc/whitelist_appops.xml
persist.sys.usb.config=mtp,adb
ro.securestorage.support=false
androidboot.selinux=0



Gesendet von meinem SM-G900F mit Tapatalk
 
  • Like
Reactions: Gnome

Gnome

Senior Member
Jul 2, 2013
2,799
7,304
Red Light District
Only zimage use this for default.prop

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.security.ams.enforcing=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.adb.secure=0
persist.sys.strict_op_enable=false
persist.sys.whitelist=/system/etc/whitelist_appops.xml
persist.sys.usb.config=mtp,adb
ro.securestorage.support=false
androidboot.selinux=0



Gesendet von meinem SM-G900F mit Tapatalk

Weird, my kernel still wont boot with this changed on my default.prop, It seems it might be a toolchain issue. I'll lower it down to 4.9 and see what happens.
 

Jhowlett

Senior Member
Feb 6, 2009
266
39
Well, here it is. I hope this would help. Currently I dont know where to post but Moderators feel free to move the thread anywhere he wants.

Code:
 1|shell@klte:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root     root              2014-01-03 03:34 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2014-01-03 03:34 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2014-01-03 03:34 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2014-01-03 03:34 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2014-01-03 03:34 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2014-01-03 03:34 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2014-01-03 03:34 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2014-01-03 03:34 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2014-01-03 03:34 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2014-01-03 03:34 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2014-01-03 03:34 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2014-01-03 03:34 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2014-01-03 03:34 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2014-01-03 03:34 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2014-01-03 03:34 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2014-01-03 03:34 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2014-01-03 03:34 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2014-01-03 03:34 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2014-01-03 03:34 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2014-01-03 03:34 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2014-01-03 03:34 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2014-01-03 03:34 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2014-01-03 03:34 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2014-01-03 03:34 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2014-01-03 03:34 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2014-01-03 03:34 userdata -> /dev/block/mm
cblk0p26
shell@klte:/ $

As of now, there is no root, so there is no way for me to dump those partitions. Any help is welcome! Please PM's if interested!

Hi' !
Good job but... Miss the /data partition information no ?
 

tdunham

Inactive Recognized Contributor
Jun 21, 2008
13,686
36,465
TampaBay
Just wanted to add that the partition table for the US Sprint SM-G900P variant is identical.
 
Last edited:
  • Like
Reactions: leoaudio13

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Well, here it is. I hope this would help. Currently I dont know where to post but Moderators feel free to move the thread anywhere he wants.

    Code:
     1|shell@klte:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
    ls -al /dev/block/platform/msm_sdcc.1/by-name
    lrwxrwxrwx root     root              2014-01-03 03:34 aboot -> /dev/block/mmcblk0p6
    lrwxrwxrwx root     root              2014-01-03 03:34 apnhlos -> /dev/block/mmcblk0p1
    lrwxrwxrwx root     root              2014-01-03 03:34 backup -> /dev/block/mmcblk0p18
    lrwxrwxrwx root     root              2014-01-03 03:34 boot -> /dev/block/mmcblk0p15
    lrwxrwxrwx root     root              2014-01-03 03:34 cache -> /dev/block/mmcblk0p24
    lrwxrwxrwx root     root              2014-01-03 03:34 dbi -> /dev/block/mmcblk0p4
    lrwxrwxrwx root     root              2014-01-03 03:34 ddr -> /dev/block/mmcblk0p5
    lrwxrwxrwx root     root              2014-01-03 03:34 efs -> /dev/block/mmcblk0p12
    lrwxrwxrwx root     root              2014-01-03 03:34 fota -> /dev/block/mmcblk0p17
    lrwxrwxrwx root     root              2014-01-03 03:34 fsc -> /dev/block/mmcblk0p19
    lrwxrwxrwx root     root              2014-01-03 03:34 fsg -> /dev/block/mmcblk0p9
    lrwxrwxrwx root     root              2014-01-03 03:34 hidden -> /dev/block/mmcblk0p25
    lrwxrwxrwx root     root              2014-01-03 03:34 modem -> /dev/block/mmcblk0p2
    lrwxrwxrwx root     root              2014-01-03 03:34 modemst1 -> /dev/block/mmcblk0p13
    lrwxrwxrwx root     root              2014-01-03 03:34 modemst2 -> /dev/block/mmcblk0p14
    lrwxrwxrwx root     root              2014-01-03 03:34 pad -> /dev/block/mmcblk0p10
    lrwxrwxrwx root     root              2014-01-03 03:34 param -> /dev/block/mmcblk0p11
    lrwxrwxrwx root     root              2014-01-03 03:34 persdata -> /dev/block/mmcblk0p22
    lrwxrwxrwx root     root              2014-01-03 03:34 persist -> /dev/block/mmcblk0p21
    lrwxrwxrwx root     root              2014-01-03 03:34 recovery -> /dev/block/mmcblk0p16
    lrwxrwxrwx root     root              2014-01-03 03:34 rpm -> /dev/block/mmcblk0p7
    lrwxrwxrwx root     root              2014-01-03 03:34 sbl1 -> /dev/block/mmcblk0p3
    lrwxrwxrwx root     root              2014-01-03 03:34 ssd -> /dev/block/mmcblk0p20
    lrwxrwxrwx root     root              2014-01-03 03:34 system -> /dev/block/mmcblk0p23
    lrwxrwxrwx root     root              2014-01-03 03:34 tz -> /dev/block/mmcblk0p8
    lrwxrwxrwx root     root              2014-01-03 03:34 userdata -> /dev/block/mm
    cblk0p26
    shell@klte:/ $

    As of now, there is no root, so there is no way for me to dump those partitions. Any help is welcome! Please PM's if interested!
    2
    Thank you. The parameters of SM-G900F? Is important to then I can take the test kernel ready!

    Gesendet von meinem Nexus 5 mit Tapatalk
    2
    Use you zimage or zImage-dtb? Thanks for help!

    Gesendet von meinem SM-G900F mit Tapatalk

    z-image
    1
    I can test if you finished compiling the kernel!

    you've tested one compiled kernel already ;)

    lol it remained stock, but was compiled from src. :)
    1
    hey guys just wanted conformation as im working blind and dont own G900F but trying to build for a friend does this look ok plz

    kernel -> /dev/block/platform/msm_sdcc.1/by-name/boot

    modem -> /dev/block/mmcblk0p2

    Hi BBB,

    I'm not an expert on partitions, but kernel is boot.img, and boot is /dev/block/mmcblk0p15.

    For the modem I found:
    modem -> /dev/block/mmcblk0p2
    modemst1 -> /dev/block/mmcblk0p13
    modemst2 -> /dev/block/mmcblk0p14

    So your modem is correct, but there are modemst1 and modemst2 (for the GSM and LTE modem I think).
    IDK if you need those partitions too.