Hovatek Forum MOBILE Android [Please help] Looking for an MT8117 scatter file that works with SP_Flash OR just general advice.
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


[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.

Pages (4): Previous 1 2 3 4 Next
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
14-02-2018, 06:14 AM
#11



Well it looks like the flash didn't take. I'm thinking it's got to be the fact that the mtk tools isn't really made to create an 8117 scatter file. I did pull up what I think might be the scatter info from my working device

Part_Name Size StartAddr Type MapTo Region
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 USER
bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER
recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0 USER
sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4 USER
misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0 USER
logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0 USER
ebr2 0x0000000000080000 0x0000000004700000 2 /dev/block/mmcblk0 USER
expdb 0x0000000000a00000 0x0000000004780000 2 /dev/block/mmcblk0 USER
tee1 0x0000000000500000 0x0000000005180000 2 /dev/block/mmcblk0 USER
tee2 0x0000000000500000 0x0000000005680000 2 /dev/block/mmcblk0 USER
kb 0x0000000000100000 0x0000000005b80000 2 /dev/block/mmcblk0 USER
dkb 0x0000000000100000 0x0000000005c80000 2 /dev/block/mmcblk0 USER
android 0x0000000040000000 0x0000000005d80000 2 /dev/block/mmcblk0p5 USER
cache 0x0000000007e00000 0x0000000045d80000 2 /dev/block/mmcblk0p6 USER
usrdata 0x0000000080000000 0x000000004db80000 2 /dev/block/mmcblk0p7 USER
fat 0x0000000104480000 0x00000000cdb80000 2 /dev/block/mmcblk0p8 USER
bmtpool 0x0000000001500000 0x00000000ffff0000 2 /dev/block/mmcblk0 USER

I'm going to parse through it and see if I can match it up.
This post was last modified: 14-02-2018, 06:18 AM by mcfuddlebutt.
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
14-02-2018, 07:14 AM
#12
More chain posts but if anyone comes across this problem I'm sure it will be helpful.

digging around and found a emmc@custom reference in ls -la

Could this be throwing my partitions off?

lrwxrwxrwx root root 1970-01-01 00:00 emmc@android -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 00:00 emmc@cache -> /dev/block/mmcblk0p6
-rw-r--r-- root root 0 2018-02-14 05:08 emmc@custom
lrwxrwxrwx root root 1970-01-01 00:00 emmc@ebr1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 00:00 emmc@fat -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 00:00 emmc@protect_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 00:00 emmc@protect_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 00:00 emmc@sec_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 00:00 emmc@usrdata -> /dev/block/mmcblk0p7
hovatek
hovatek
hovatek
Administrator
49,570
14-02-2018, 11:26 AM
#13
(14-02-2018, 03:56 AM)mcfuddlebutt Sorry for the chain posts. I flashed the firmware I pulled from a working unit but now the machine isn't showing anything on the screen. It is still visible on Windows but nothing in terms of action from the box itself. Can't boot into bootloader or recovery either. 

Re-formatting and reflashing to make sure I didn't goof anything up.

What was the state of this phone before you flashed with the backup?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
14-02-2018, 05:40 PM
#14
(14-02-2018, 11:26 AM)hovatek
(14-02-2018, 03:56 AM)mcfuddlebutt Sorry for the chain posts. I flashed the firmware I pulled from a working unit but now the machine isn't showing anything on the screen. It is still visible on Windows but nothing in terms of action from the box itself. Can't boot into bootloader or recovery either. 

Re-formatting and reflashing to make sure I didn't goof anything up.

What was the state of this phone before you flashed with the backup?

Not working because I flashed it with another bad backup. Before that it was a regular tablet with a locked down OS.
X3non
X3non
X3non
Recognized Contributor
22,062
14-02-2018, 06:17 PM
#15



(14-02-2018, 05:40 PM)mcfuddlebutt Not working because I flashed it with another bad backup. Before that it was a regular tablet with a locked down OS.

you seem to be testing so many things at once but lets properly verify one thing
after flashing the rom you got from backing up one of the working tabs onto the faulty tab, is the faulty tab totally dead [doesnt power on at all] OR it powers on but with a black screen?
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
15-02-2018, 01:20 AM
#16
(14-02-2018, 06:17 PM)X3non
(14-02-2018, 05:40 PM)mcfuddlebutt Not working because I flashed it with another bad backup. Before that it was a regular tablet with a locked down OS.

you seem to be testing so many things at once but lets properly verify one thing
after flashing the rom you got from backing up one of the working tabs onto the faulty tab, is the faulty tab totally dead [doesnt power on at all] OR it powers on but with a black screen?

I have a bad habit of doing that  Dodgy

It's difficult to tell if the unit powers on because it doesn't make any noses when it boots. I would say that it is powering on but with a black screen. It does come up in the device manager when I power it on
hovatek
hovatek
hovatek
Administrator
49,570
15-02-2018, 09:02 AM
#17
(15-02-2018, 01:20 AM)mcfuddlebutt I have a bad habit of doing that  Dodgy

It's difficult to tell if the unit powers on because it doesn't make any noses when it boots. I would say that it is powering on but with a black screen. It does come up in the device manager when I power it on

That sounds like an incompatible lk.bin

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
15-02-2018, 09:27 AM
#18
(15-02-2018, 09:02 AM)hovatek
(15-02-2018, 01:20 AM)mcfuddlebutt I have a bad habit of doing that  Dodgy

It's difficult to tell if the unit powers on because it doesn't make any noses when it boots. I would say that it is powering on but with a black screen. It does come up in the device manager when I power it on

That sounds like an incompatible lk.bin

What would you think could make it incompatible with a unit that is exactly the same?
X3non
X3non
X3non
Recognized Contributor
22,062
15-02-2018, 03:41 PM
#19
(15-02-2018, 09:27 AM)mcfuddlebutt What would you think could make it incompatible with a unit that is exactly the same?

for power on, on most mtk devices there is usually a short vibration then the screen lights come up [once you can see if the screen lights even if the screen is still black, then the device is ON]

back to the incompatible LK.bin
devices might bear the same model but can be what we call variants and interflashing their files usually doesn't go down well. build number usually helps identify these variants

from the rom you pulled, there should be a system.img,
use method 4 @ https://www.hovatek.com/forum/thread-16005.html to get the build number, then do the same for all the other tabs you have to see if you can get another tab with a different build. if you get one, then try the rom from it on the faulty tab
mcfuddlebutt
mcfuddlebutt
mcfuddlebutt
Junior Member
23
15-02-2018, 07:15 PM
#20



(15-02-2018, 03:41 PM)X3non
(15-02-2018, 09:27 AM)mcfuddlebutt What would you think could make it incompatible with a unit that is exactly the same?

for power on, on most mtk devices there is usually a short vibration then the screen lights come up [once you can see if the screen lights even if the screen is still black, then the device is ON]

back to the incompatible LK.bin
devices might bear the same model but can be what we call variants and interflashing their files usually doesn't go down well. build number usually helps identify these variants

from the rom you pulled, there should be a system.img,
use method 4 @ https://www.hovatek.com/forum/thread-16005.html to get the build number, then do the same for all the other tabs you have to see if you can get another tab with a different build. if you get one, then try the rom from it on the faulty tab

Thanks for that explanation, it makes much more sense. Here is the info the build.prop extracted

# 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

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.
Pages (4): Previous 1 2 3 4 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram