2019-09-18, 18:39 (This post was last modified: 2019-09-19, 19:11 by mydest994.)
(2019-09-18, 15:44)mydest994 Wrote: I've got some firmware file on similar model from some one who bought it. I'm just try, may be usable.
Now I'm on my way to find the best and correct files for it.
I feel disappoint with the contribution of this big community,
many people but rare contribution and I shall do so
Most of all the quality of "MADE-IN-CHINA" tablet made me feel so bad.
2019-09-20, 10:09 (This post was last modified: 2019-09-20, 10:17 by Dhamma Bodhisuttha.)
What else shall I try?
Now I can boot T906 , the main screen looks like this
But I can use touch menu and copy screenshot are ok, came in original chinese language
My PC can see the T906 as "Phone storage" with all directories and all files inside
From the build.properties, I shows that this tablet has display id of "ALPS.KK1.MP1.V2.10"
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP1.V2.10
ro.build.version.incremental=vEN0B82
ro.custom.build.version=vEN0B82
Came with OS Android 4.4.2
ro.build.version.sdk=19
(2019-09-20, 10:09)Dhamma Bodhisuttha Wrote: What else shall I try?
Now I can boot T906 , the main screen looks like this
But I can use touch menu and copy screenshot are ok, came in original chinese language
My PC can see the T906 as "Phone storage" with all directories and all files inside
From the build.properties, I shows that this tablet has display id of "ALPS.KK1.MP1.V2.10"
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP1.V2.10
ro.build.version.incremental=vEN0B82
ro.custom.build.version=vEN0B82
Came with OS Android 4.4.2
ro.build.version.sdk=19
Hey, common everybody , I need your comments, your additional info,
or what ever you have learned from my case.
please make some or any comment,
so I may have ideas to solve the problem and I will share all info.
2019-09-20, 22:56 (This post was last modified: 2019-09-20, 23:00 by Loewe78.)
(2019-09-20, 18:58)Dhamma Bodhisuttha Wrote: Hey, common everybody , I need your comments, your additional info,
or what ever you have learned from my case.
please make some or any comment,
so I may have ideas to solve the problem and I will share all info.
You're great! I was puzzeling for days to find a way to figure out how to get informations from the screen. If necessary, we can enable usb debugging now and do lots of stuff via adb.
Thanks a lot for the information.
Did you flash another firmware and is this causing the behaviour?
If yes: I think, we'll need to find out where little kernel / uboot gets its display driver or display information from. I didn't manage to solve that one yet.
I tried a lot and as soon as I changed the lk-file, I got a different (sadly, still wrong) behaviour on my machine.
And I was able to locate screen resolution information that differs from what I found in the remnains of my lk file. I didn't find a way to change the code, though. Guess it has to be recompiled - but I don't know how.
I think, we need to find out how to implement these informations or drivers the correct way. Sadly, I didn't find a thread to even start with.
It's somewhat complicated, even more as it's an MTK-device which works with little kernel (lk) to boot from.
I ended up with searching "little kernel AND mtk AND display".
Another possibility is that little kernel gets its information from boot.img or boot.img has a different set of informations. I don't know yet.
2019-09-21, 02:23 (This post was last modified: 2019-09-21, 02:25 by Dhamma Bodhisuttha.)
(2019-09-20, 22:56)Loewe78 Wrote: You're great! I was puzzeling for days to find a way to figure out how to get informations from the screen. If necessary, we can enable usb debugging now and do lots of stuff via adb.
Thanks a lot for the information.
Did you flash another firmware and is this causing the behaviour?
If yes: I think, we'll need to find out where little kernel / uboot gets its display driver or display information from. I didn't manage to solve that one yet.
I tried a lot and as soon as I changed the lk-file, I got a different (sadly, still wrong) behaviour on my machine.
And I was able to locate screen resolution information that differs from what I found in the remnains of my lk file. I didn't find a way to change the code, though. Guess it has to be recompiled - but I don't know how.
I think, we need to find out how to implement these informations or drivers the correct way. Sadly, I didn't find a thread to even start with.
It's somewhat complicated, even more as it's an MTK-device which works with little kernel (lk) to boot from.
I ended up with searching "little kernel AND mtk AND display".
Another possibility is that little kernel gets its information from boot.img or boot.img has a different set of informations. I don't know yet.
Thanks for your comment, we shall find the way together.
The point is file lk.bin and may be nvram.bin together control the resolution of screen. We exactly know that the right screen resolution of HYD T906 is 1280 x 800, it's not 2560 * 1600 as advertised.
The most difficult point is how to compile and make preloader.bin with data of correct resolution.
It seem that I have to start to learn abouth each block of files again, just to find out where to insert a line of code.
There is someone told me that the right way is to edit file build.properties with program build-editor then re-compile it,
the problem is that I'm not even know where and how to start, since I'm not a programmer at all.
It may be wise to start from build editor as the frst step to modify parameter of all files.
2019-09-21, 03:40 (This post was last modified: 2019-09-21, 07:33 by Loewe78.)
(2019-09-21, 02:23)Dhamma Bodhisuttha Wrote: [Only registered and activated users can see links Click here to register]
Edit: I'm quite sure it's not "only" a screen resolution issue. With a bazillion of screenshots, I managed to activate developer options and to change screen resolution via simulated second display. It's all the same, except I cannot take screenshots any more and will have to reflash :p.
Edit II: As I'll be packing tomorrow and departing for holiday the day after, I split my ROM-dump into smaller pieces and uploaded it to the web drive. It's not all of the 2 GB data, much of it is empty space and in smaller pieces, you can look through it with an edior. If you want to follow the instructions I posted above, use a good editor like vim and scroll through the bits and pieces, piece together and resplit as you think is good. At the beginning, there seem to be big parts of nvram and four drivers for different screens. One of them might work for each of us. It's nasty work, I tried to extract the lk-file before. It didn't work at all, unfortunately. One bit too much or too short - maybe it was because I used Windows Editor and it changed the file while saving it - I don't know at all.
(2019-09-21, 03:40)Loewe78 Wrote: [Only registered and activated users can see links Click here to register]
Edit: I'm quite sure it's not "only" a screen resolution issue. With a bazillion of screenshots, I managed to activate developer options and to change screen resolution via simulated second display. It's all the same, except I cannot take screenshots any more and will have to reflash :p.
Edit II: As I'll be packing tomorrow and departing for holiday the day after, I split my ROM-dump into smaller pieces and uploaded it to the web drive. It's not all of the 2 GB data, much of it is empty space and in smaller pieces, you can look through it with an edior. If you want to follow the instructions I posted above, use a good editor like vim and scroll through the bits and pieces, piece together and resplit as you think is good. At the beginning, there seem to be big parts of nvram and four drivers for different screens. One of them might work for each of us. It's nasty work, I tried to extract the lk-file before. It didn't work at all, unfortunately. One bit too much or too short - maybe it was because I used Windows Editor and it changed the file while saving it - I don't know at all.
Good news, I found similar firmware vEN0B71 at [Only registered and activated users can see links Click here to register] but our needed rom is vEN0B82, so I continue of looking thought the ftp and hope to find the right firmawre soon.
For the issue of how to edit file buil.properties for T906, I got a linkl download the apk file for you to try, you may may use it. [Only registered and activated users can see links Click here to register]
last point, the manufacture of T906 screen is alps company build.dusplay.id = ALPS.KK1.MP1.V2.10
file to look for is ro.build.description=zh960-user 4.4.2 KOT49H vEN0B82
2019-09-21, 18:26 (This post was last modified: 2019-09-21, 18:43 by Dhamma Bodhisuttha.)
(2019-09-21, 17:10)Dhamma Bodhisuttha Wrote: [Only registered and activated users can see links Click here to register] but our needed rom is vEN0B82, so I continue of looking thought the ftp and hope to find the right firmawre soon.
For the issue of how to edit file buil.properties for T906, I got a linkl download the apk file for you to try, you may may use it. [Only registered and activated users can see links Click here to register]
last point, the manufacture of T906 screen is alps company build.dusplay.id = ALPS.KK1.MP1.V2.10
file to look for is ro.build.description=zh960-user 4.4.2 KOT49H vEN0B82
This is the ftp web I found similar firmware (vEN0B70 and vEN0B71) but our needed firmware is vEN0B82 [Only registered and activated users can see links Click here to register]
(2019-09-21, 17:10)Dhamma Bodhisuttha Wrote: [Only registered and activated users can see links Click here to register] but our needed rom is vEN0B82, so I continue of looking thought the ftp and hope to find the right firmawre soon.
For the issue of how to edit file buil.properties for T906, I got a linkl download the apk file for you to try, you may may use it. [Only registered and activated users can see links Click here to register]
last point, the manufacture of T906 screen is alps company build.dusplay.id = ALPS.KK1.MP1.V2.10
file to look for is ro.build.description=zh960-user 4.4.2 KOT49H vEN0B82
As far as I understood, build.display-id is the identity of the build the device shows. In my build.prop, it's specified T906_D3_31PIN .
This is what the device tells when you look for the properties in Android system settings.
ALPS is a commonly used build identity in China and as far as I read it, it's not a manufacturer of devices, but a common software for all kinds of devices.
If you want to learn about your screen manufacturer, you need to disassemble the device - or look in the code for a manufacturer. The ones I found in my file are Chinese. I didn't find the drivers, but I didn't look that carefully, though.
2019-09-22, 19:57 (This post was last modified: 2019-09-23, 15:01 by mydest994.)
(2019-09-22, 02:08)Loewe78 Wrote: As far as I understood, build.display-id is the identity of the build the device shows. In my build.prop, it's specified T906_D3_31PIN .
This is what the device tells when you look for the properties in Android system settings.
ALPS is a commonly used build identity in China and as far as I read it, it's not a manufacturer of devices, but a common software for all kinds of devices.
If you want to learn about your screen manufacturer, you need to disassemble the device - or look in the code for a manufacturer. The ones I found in my file are Chinese. I didn't find the drivers, but I didn't look that carefully, though.
I think that T906_D3_31PIN is the name of custom build version of software for this tablet, not the display driver id. I also did an experiment of adb/fastboot command to unlock the bootloader. I finished command but failed to unlock bootloader adb device adb reboot bootloader fastboot devices fastboot oem unlock
![[-]](https://www.chinaphonearena.com/forum/images/collapse.png "[-]")
