[Please help] Looking for an MT8117 scatter file that works with SP_Flash OR just general advice.
[Please help] Looking for an MT8117 scatter file that works with SP_Flash OR just general advice.
(15-02-2018, 07:15 PM)mcfuddlebutt Thanks for that explanation, it makes much more sense. Here is the info the build.prop extracted
Code:# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=STM231ALPS.KK1.MP10.V1.52
ro.build.version.incremental=eng.innocomm.1447066301
ro.custom.build.version=STM231
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=一 11月 9 18:53:56 CST 2015
ro.build.date.utc=1447066436
ro.build.type=user
ro.build.user=innocomm
ro.build.host=X58A-UD3R
ro.build.tags=release-keys
ro.product.model=inoco27_tb_stm_kk
ro.product.brand=alps
ro.product.name=inoco27_tb_stm_kk
ro.product.device=inoco27_tb_stm_kk
ro.product.board=inoco27_tb_stm_kk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=inoco27_tb_stm_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=inoco27_tb_stm_kk-user 4.4.2 KOT49H eng.innocomm.1447066301 release-keys
ro.build.fingerprint=alps/inoco27_tb_stm_kk/inoco27_tb_stm_kk:4.4.2/KOT49H/1447066301:user/release-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
I did see in the build.prop
Code:# begin mediatek build properties
ro.mediatek.version.release=STM231ALPS.KK1.MP10.V1.52
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
but the chip on the device is an MT8117, I actually took a photo of the chip to double check what it had printed on it. Is this something that mtk tools would change because of the scatter file? When I try to load an mt8117 file it would say the version is wrong so i'd have to change it to 8127 on the top of the file to get it working.
Thanks again bud.
(15-02-2018, 08:07 PM)X3non(15-02-2018, 07:15 PM)mcfuddlebutt Thanks for that explanation, it makes much more sense. Here is the info the build.prop extracted
Code:# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=STM231ALPS.KK1.MP10.V1.52
ro.build.version.incremental=eng.innocomm.1447066301
ro.custom.build.version=STM231
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=一 11月 9 18:53:56 CST 2015
ro.build.date.utc=1447066436
ro.build.type=user
ro.build.user=innocomm
ro.build.host=X58A-UD3R
ro.build.tags=release-keys
ro.product.model=inoco27_tb_stm_kk
ro.product.brand=alps
ro.product.name=inoco27_tb_stm_kk
ro.product.device=inoco27_tb_stm_kk
ro.product.board=inoco27_tb_stm_kk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=inoco27_tb_stm_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=inoco27_tb_stm_kk-user 4.4.2 KOT49H eng.innocomm.1447066301 release-keys
ro.build.fingerprint=alps/inoco27_tb_stm_kk/inoco27_tb_stm_kk:4.4.2/KOT49H/1447066301:user/release-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
I did see in the build.prop
Code:# begin mediatek build properties
ro.mediatek.version.release=STM231ALPS.KK1.MP10.V1.52
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
but the chip on the device is an MT8117, I actually took a photo of the chip to double check what it had printed on it. Is this something that mtk tools would change because of the scatter file? When I try to load an mt8117 file it would say the version is wrong so i'd have to change it to 8127 on the top of the file to get it working.
Thanks again bud.
the value of ro.build.display.id is the build number "STM231ALPS.KK1.MP10.V1.52" so that's what you'll be looking out for in the other tabs.
how exactly did you verify the chipset to be MT8117 ? ;cause thats not a known chipset type meanwhile MT8127 is known
(15-02-2018, 07:15 PM)mcfuddlebutt Thanks for that explanation, it makes much more sense. Here is the info the build.prop extracted
but the chip on the device is an MT8117, I actually took a photo of the chip to double check what it had printed on it. Is this something that mtk tools would change because of the scatter file? When I try to load an mt8117 file it would say the version is wrong so i'd have to change it to 8127 on the top of the file to get it working.Code:# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=STM231ALPS.KK1.MP10.V1.52
ro.build.version.incremental=eng.innocomm.1447066301
ro.custom.build.version=STM231
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=一 11月 9 18:53:56 CST 2015
ro.build.date.utc=1447066436
ro.build.type=user
ro.build.user=innocomm
ro.build.host=X58A-UD3R
ro.build.tags=release-keys
ro.product.model=inoco27_tb_stm_kk
ro.product.brand=alps
ro.product.name=inoco27_tb_stm_kk
ro.product.device=inoco27_tb_stm_kk
ro.product.board=inoco27_tb_stm_kk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=inoco27_tb_stm_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=inoco27_tb_stm_kk-user 4.4.2 KOT49H eng.innocomm.1447066301 release-keys
ro.build.fingerprint=alps/inoco27_tb_stm_kk/inoco27_tb_stm_kk:4.4.2/KOT49H/1447066301:user/release-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
I did see in the build.prop
# begin mediatek build properties
ro.mediatek.version.release=STM231ALPS.KK1.MP10.V1.52
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
Thanks again bud.
(15-02-2018, 10:45 PM)mcfuddlebutt This might be jumping again but do these photos help anything? I took a bunch when I first got in to the engineering mode thing on the first unit.
..
(16-02-2018, 09:16 AM)hovatek(15-02-2018, 10:45 PM)mcfuddlebutt This might be jumping again but do these photos help anything? I took a bunch when I first got in to the engineering mode thing on the first unit.
..
These are blocks maps. Not much help at the moment but might come in handy later
(16-02-2018, 09:11 AM)hovatek(15-02-2018, 07:15 PM)mcfuddlebutt Thanks for that explanation, it makes much more sense. Here is the info the build.prop extracted
but the chip on the device is an MT8117, I actually took a photo of the chip to double check what it had printed on it. Is this something that mtk tools would change because of the scatter file? When I try to load an mt8117 file it would say the version is wrong so i'd have to change it to 8127 on the top of the file to get it working.Code:# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=STM231ALPS.KK1.MP10.V1.52
ro.build.version.incremental=eng.innocomm.1447066301
ro.custom.build.version=STM231
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=一 11月 9 18:53:56 CST 2015
ro.build.date.utc=1447066436
ro.build.type=user
ro.build.user=innocomm
ro.build.host=X58A-UD3R
ro.build.tags=release-keys
ro.product.model=inoco27_tb_stm_kk
ro.product.brand=alps
ro.product.name=inoco27_tb_stm_kk
ro.product.device=inoco27_tb_stm_kk
ro.product.board=inoco27_tb_stm_kk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=inoco27_tb_stm_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=inoco27_tb_stm_kk-user 4.4.2 KOT49H eng.innocomm.1447066301 release-keys
ro.build.fingerprint=alps/inoco27_tb_stm_kk/inoco27_tb_stm_kk:4.4.2/KOT49H/1447066301:user/release-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
I did see in the build.prop
# begin mediatek build properties
ro.mediatek.version.release=STM231ALPS.KK1.MP10.V1.52
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
Thanks again bud.
Its very possible for you to see one thing on the chip and another when software read the phone. This is because some Mediatek chips (though having different numbers) use the same hardware and are essentially the same. You'll see this even between MT67** and MT81** chips
(16-02-2018, 09:59 AM)mcfuddlebutt Gocha,
So I've opened up another unit and am currently ripping the rom. Is there anything else you can think would work to flash this thing where it might get going again? I've flash it about 5 times with the rom from the second machine but it's still stuck in the black screen.