Hovatek Forum MOBILE Android Need Scatter file for Micromax Canvas P290 (1GB ROM, 8GB internal Memory, MTK8127 cpu
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Need Scatter file for Micromax Canvas P290 (1GB ROM, 8GB internal Memory, MTK8127 cpu

Need Scatter file for Micromax Canvas P290 (1GB ROM, 8GB internal Memory, MTK8127 cpu

Pages (2): 1 2 Next
raj555
raj555
raj555
Junior Member
16
09-02-2017, 06:37 AM
#1



Sir, I have soft-bricked my tablet 7inch-micromax-P290 (1GB RAM, 8GB internal sd).

I have obtained a "P290" ROM on internet (unsubstantiated source not the official) and extracted it. There is a scatter (*.sca) file in it. But the readings in the file do not tally with the readings in the scatter file created by MTK droid tools v2.5.3, which i used to extract my present ROM before the phone soft-bricked (in my attempt to flash recovery i must have formatted some critical partition in the phone). I also used adb commands to obtain mtd partitions before it soft-bricked and have them separately from the MTK droid tools backup directory too.

MTK droid tools did not create scatter file (the button was greyed out) i think this is because this tablet uses MT8127 cpu which Droid tools does not support. HOwever i used firmware.info in backup directory of droid tools to use option "save as text file" and it created a scatter file. Lets call it "droid tools scatter file.txt". but the ROM i downloaded , the .sca file it has differences in start address blocks even though other parts of file are same. ie, the lengths of blocks are same but start addresses differ. Block size is shown as 4k in both scatter files, and file lengths are same. Now i am unable to flash the pre-loader (which i must have over-written) using SP flash tools and i also tried with wise link tool (which was included in the ROM i downloaded for P290, total ROM was 1.6GB download). with wise link tool i get ERROR  code 5054 (there does not exist the MTK_ROM_INFO structure in the ROM, does not exist MTK_BOOTLOADER_STRUCTURE in the bootloader, it is not NFB booting).
also, previously in device manager i could see Mediatek Preloader USB VCOM driver (Android) but now i see only Mediatek USB port (COM19). I tried using SP flash tool also to download pre-loader to tablet without success, it too gives errors.

I would really appreciate some help at this point ! I want to recover the tablet to working and install CWM or TWRP ( i prefer CWM as i used it a lot in my previous phones too and its smaller more reliable) on it. I enclose the scatter file from the ROM in .sca format, and the one i got from MTK droid when firmware.info was saved as .txt file. there is also a screenshot of droid tools when it showed the partitions on phone (scatter file save button greyed out, ) before i bricked it a day later .
This post was last modified: 09-02-2017, 07:00 AM by raj555. Edit Reason: enclose scatter files
Attached Files
.txt
MT6572_Android_scatter.txt
Size: 7.85 KB / Downloads: 30
.jpg
blocksMap-P290.jpg
Size: 289.41 KB / Downloads: 15
hovatek
hovatek
hovatek
Administrator
49,570
09-02-2017, 12:06 PM
#2
(09-02-2017, 06:37 AM)raj555 Sir, I have soft-bricked my tablet 7inch-micromax-P290 (1GB RAM, 8GB internal sd).

I have obtained a "P290" ROM on internet (unsubstantiated source not the official) and extracted it. There is a scatter (*.sca) file in it. But the readings in the file do not tally with the readings in the scatter file created by MTK droid tools v2.5.3, which i used to extract my present ROM before the phone soft-bricked (in my attempt to flash recovery i must have formatted some critical partition in the phone). I also used adb commands to obtain mtd partitions before it soft-bricked and have them separately from the MTK droid tools backup directory too.

MTK droid tools did not create scatter file (the button was greyed out) i think this is because this tablet uses MT8127 cpu which Droid tools does not support. HOwever i used firmware.info in backup directory of droid tools to use option "save as text file" and it created a scatter file. Lets call it "droid tools scatter file.txt". but the ROM i downloaded , the .sca file it has differences in start address blocks even though other parts of file are same. ie, the lengths of blocks are same but start addresses differ. Block size is shown as 4k in both scatter files, and file lengths are same. Now i am unable to flash the pre-loader (which i must have over-written) using SP flash tools and i also tried with wise link tool (which was included in the ROM i downloaded for P290, total ROM was 1.6GB download). with wise link tool i get ERROR  code 5054 (there does not exist the MTK_ROM_INFO structure in the ROM, does not exist MTK_BOOTLOADER_STRUCTURE in the bootloader, it is not NFB booting).
also, previously in device manager i could see Mediatek Preloader USB VCOM driver (Android) but now i see only Mediatek USB port (COM19). I tried using SP flash tool also to download pre-loader to tablet without success, it too gives errors.

I would really appreciate some help at this point ! I want to recover the tablet to working and install CWM or TWRP ( i prefer CWM as i used it a lot in my previous phones too and its smaller more reliable) on it. I enclose the scatter file from the ROM in .sca format, and the one i got from MTK droid when firmware.info was saved as .txt file. there is also a screenshot of droid tools when it showed the partitions on phone (scatter file save button greyed out, ) before i bricked it a day later .

That sounds like the No Space error.
I need to know some things:
1. Try flashing the .sca ROM using Wiselink Tool @ https://www.hovatek.com/forum/thread-5603.html and attach a screenshot of the error message
2. The firmware.info method of creating scatter files isn't reliable so I would advise that you put that scatter file aside
3. What's the present condition of the phone (i.e totally dead, stuck at logo, bootloop etc)
4. Which partitions were you able to dump (MTD)
5. How exactly did you attempt flashing recovery (that bricked the phone) and where was the scatter file obtained from (if you'd used SP flash tool)
This post was last modified: 09-02-2017, 12:07 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
raj555
raj555
raj555
Junior Member
16
09-02-2017, 09:06 PM
#3
(09-02-2017, 12:06 PM)hovatek
(09-02-2017, 06:37 AM)raj555 That sounds like the No Space error.
I need to know some things:
1. Try flashing the .sca ROM using Wiselink Tool @ https://www.hovatek.com/forum/thread-5603.html and attach a screenshot of the error message
2. The firmware.info method of creating scatter files isn't reliable so I would advise that you put that scatter file aside
3. What's the present condition of the phone (i.e totally dead, stuck at logo, bootloop etc)
4. Which partitions were you able to dump (MTD)
5. How exactly did you attempt flashing recovery (that bricked the phone) and where was the scatter file obtained from (if you'd used SP flash tool

The link on hovatek for Wise link tool 5.8 could not be used, it takes me to adfly only if i use a proxy and the proxy seems to be blocking some ads because adfly pops up a "you seem to be using an ad blocker" and this popup blocks the "click after 5 sec " window. I tried with different proxys too. the proxy given on hovatek page is down for maintenance it says. so I obtained the Wiselink tool 5.8.0.56 from needrom.com , but after installing i realized its same as the version of wise link i already have.

In wise link tool window in DOWNLOAD tab, it says to select the "project" first. The first list item is KR076. I an not sure if i should select this project or another below it in the list that opens on clicking. Maybe selecting the right project is important ?

In my scatter file (.sca) the project name is at the opening lines as "r712_nand"

------
- general: MTK_PLATFORM_CFG
  info:
    - config_version: V1.1.1
      platform: MT8127
      platform: MT8127
      project: r712_nand
      storage: NAND    
      boot_channel: NONE
      block_size: 0x400000
############################################################################################################
#
#  Layout Setting
#
############################################################################################################
- partition_index: SYS0
  partition_name: PRELOADER
  file_name: preloader_r712_nand.bin
  is_download: true
  type: SV5_BL_BIN
  linear_start_addr: 0x0
  physical_start_addr: 0x0
  partition_size: 0x1000000
  region: NONE
  storage: HW_STORAGE_NAND
  boundary_check: true
  is_reserved: false
  operation_type: BOOTLOADERS
  d_type: LOW_PAGE
  reserve: 0x00

- partition_index: SYS1
  partition_name: PRO_INFO
  file_name: NONE
  is_download: false
  type: NONE
  linear_start_addr: 0x2000000
  physical_start_addr: 0x2000000
  partition_size: 0x1000000
  region: NONE
  storage: HW_STORAGE_NAND
  boundary_check: true
  is_reserved: false
  operation_type: PROTECTED
  d_type: LOW_PAGE
  reserve: 0x00
---etc----

I have already tried this project KR076 option in Wise Link Tool, tried to download preloader image only, and obtained the error code 5054 as given in my introduction post.

I'm enclosing the log file from Droid tools which gives information about the partitions and details of the operations conducted by it. Its rather large and i was using it few days earlier too, so i extracted the tail end of it for the last day when it got bricked which contain relevant entries. I think droid tools bricked the tablet when i pressed the button to auto prepare and load CWM in the "root and recovery" tab.

About SP flash tool , I checked its log too and it says it flashed secro.img only. it also saved the image of secro in its backup directory.

As you said, Droid tools is not reliable when block sizes change from 512 bytes (i did some reading) and for certain later MTK processors. So i am ignoring the partition info given in firmware.info and in the scatter file created as .txt in it, but are the image files extracted by it reliable ??
I extracted recovery.fstab and a few other files using adb pull commands at one point earlier. I can give a list if needed.
the following image files exist in droid tools backup directory.
===============
02/10/17  00:58    <DIR>          .
02/10/17  00:58    <DIR>          ..
02/07/17  19:21    <DIR>          !Files_to_FlashTool (files prepared by droid tools ready to flash mainly boot.img (boot), lk.bin (uboot) and recovery.img)
02/10/17  00:57    <DIR>          bak (this dir contains more images)
02/03/17  17:58           296,360 blocksMap-P290.jpg
02/08/17  00:58         4,680,800 boot.img
02/03/17  17:48               936 files.md5
02/06/17  09:07               770 firmware.info
02/10/17  00:58                 0 list.txt
02/08/17  00:58           269,077 logo.bin
02/03/17  17:14             3,044 mount.info
02/03/17  17:18         4,194,304 nodl_dkb
02/03/17  17:18         4,194,304 nodl_kb
02/03/17  17:47     1,639,645,184 nodl_nodl_custom.bin
02/03/17  17:15        12,582,912 nodl_protect_f
02/03/17  17:16        12,582,912 nodl_protect_s
02/03/17  17:16         4,194,304 nodl_seccnfg
02/03/17  17:17         8,388,608 nodl_tee1
02/03/17  17:18         8,388,608 nodl_tee2
02/03/17  17:15         3,297,280 nvram.img
02/03/17  17:14               351 phone.info
02/08/17  00:58           115,492 preloader.bin
02/03/17  17:15        16,777,216 pro_info.bin
02/08/17  00:58         5,553,168 recovery.img
02/03/17  17:17         4,194,304 secro.img
02/03/17  17:30       703,299,584 system.img
02/03/17  17:14             2,598 ubi.info
02/08/17  00:58           236,316 uboot.bin
02/03/17  17:14                60 yaffs.info
              25 File(s)  2,432,898,492 bytes
------------------
can these files can be used ? they are from the same tablet before it got bricked.

What is condition of tablet ? No response to pressing of power button. no booting, does not show charging too. when connected to PC the PC rings a bell at one minute intervals and device manager shows "mediatek USB port" for a minute, then disconnects and later again it rings and shows it , this cycle repeats. Before this condition happen, i think SP flash tools flashed secro.img which was ticked for some reason (so its mentioned in its log too).
I assume the tablet is in BOOTROM mode? i checked - its PID is 003 in dev manager. i referred to the help file which gives as below -

----------------------------
"Modes of the VCOM:
    BOOTROM (in device manager show as MTK USB Port with pid=003) . For connection in this mode can it is required :
        to use press of some phone buttons (photo, volume up or down ) at the same time with connection of a cable to PC (phone shall be switched off)
        or to use OTG adapter
        or, if it didn't turn out 1 and 2, use a test point.
    PRELOADER (...MediaTek USB VCOM Port with pid=2000 ) This port appears for only some seconds in case of connection of switched-off phone to PC
    DA_HIGHSPEED (...MediaTek DA USB VCOM Port with pid=2001)This port can appear after phone at first will be connected in the PRELOADER or BOOTROM mode."
------------------------
So i think tablet shows signs when connecting to PC that its in BOOTROM mode.

as for the (unverifiable P290) ROM which i downloaded and extracted in it there is a firmware directory. i see the list of files which is not in familiar form as above ! it consists of .mbn files and when i compare with above list, of standard images, the sizes do not tally. and the naming convention (below) is a puzzle.
here is the list of files in the ROM i downloaded for P290 which also contained the .sca file.
--------------
Directory of D:\MTEK-P290\ROMs-Micromax\ROM-Micromax_P290_V1_14.09.15-differentScatter\Firmware

02/10/17  01:22    <DIR>          .
02/10/17  01:22    <DIR>          ..
09/12/15  14:56           125,012 A1A2001XXXXX12.db
09/12/15  14:53         4,681,728 B1A2001XXXXX12.mbn
09/12/15  14:54       708,837,376 C1A2001XXXXX12.mbn
09/12/15  15:03       497,443,350 C1A2001XXXXX12.zip
02/07/17  17:56    <DIR>          checksum
02/09/17  09:29    <DIR>          factory
02/09/17  10:08             8,398 K1A2001XXXXX12.sca
02/09/17  10:07             8,398 K1A2001XXXXX12.sca.bak
02/07/17  11:39             8,398 K1A2001XXXXX12.txt
09/12/15  14:55           269,077 L1A2001XXXXX12.mbn
09/12/15  14:55           118,924 P1A2001XXXXX12.mbn
09/12/15  14:55         5,552,128 R1A2001XXXXX12.mbn
09/12/15  15:09             2,712 readme.txt
09/12/15  14:55        62,914,560 S1A2001XXXXX12.mbn
09/12/15  14:55           889,600 T1A2001XXXXX12.mbn
09/12/15  14:55           236,316 U1A2001XXXXX12.mbn
09/12/15  14:55           135,168 X1A2001XXXXX12.mbn
09/12/15  14:56       457,179,136 Y1A2001XXXXX12.mbn
09/12/15  15:04       302,984,928 Y1A2001XXXXX12.zip
              19 File(s)  2,041,399,321 bytes
============================
the "readme.txt" that came with the downloaded ROM is partly chinese, cant make anything of it.
here is a part of it
-----
<wangxinmin@topwise3g.com>
17 ):add For_TPW8127_TB_C_L_ALPS.L0.MP1.V1_P29
    负责人:wangxinmin <wangxinmin@topwise3g.com>
18 ):R712 LCM屏闪
    修改类型:项目
    测试重点:LCM
    BugID:11253
    负责人:liuhonghao <liuhonghao@topwise3g.com>
19 ):add For_TPW8127_TB_C_L_ALPS.L0.MP1.V1_P29
    负责人:wangxinmin <wangxinmin@topwise3g.com>
20 ):add For_TPW8127_TB_C_L_ALPS.L0.MP1.V1_P29
    负责人:wangxinmin <wangxinmin@topwise3g.com>
21 ):add For_TPW8127_TB_C_L_ALPS.L0.MP1.V1_P30
    负责人:wangxinmin <wangxinmin@topwise3g.com>

------------------------
i am enclosing this file as an attachment. also enclosing the .sca file renamed as .sca.txt (since this site does not accept if i use .sca ..) in this file, you please see the names given are standard image file names as expected and not  KIA , L1A, P1A ..etc as present in the firmware rom directory listing as above. you may notice that in this sca file the address of next block is given as previous block hex address plus twice the (hex) file lengtht of the block preceding it ! normally we expect it to be (hexadecimal) add the length of each image or binary to previous block HEX start address to get next block address but this file does not follow this convention ! another point of confusion I encountered when trying to analyze this sca file .

Hope i replied to all the things asked.
Thanks for your response.
This post was last modified: 09-02-2017, 09:18 PM by raj555.
Attached Files
.txt
readme.txt
Size: 2.65 KB / Downloads: 3
.txt
K1A2001XXXXX12.sca.txt
Size: 8.2 KB / Downloads: 6
raj555
raj555
raj555
Junior Member
16
10-02-2017, 07:05 AM
#4
(09-02-2017, 09:06 PM)raj555
(09-02-2017, 12:06 PM)hovatek
(09-02-2017, 06:37 AM)raj555 That sounds like the No Space error.
I need to know some things:
1. Try flashing the .sca ROM using Wiselink Tool @ https://www.hovatek.com/forum/thread-5603.html and attach a screenshot of the error message
2. The firmware.info method of creating scatter files isn't reliable so I would advise that you put that scatter file aside
3. What's the present condition of the phone (i.e totally dead, stuck at logo, bootloop etc)
4. Which partitions were you able to dump (MTD)
5. How exactly did you attempt flashing recovery (that bricked the phone) and where was the scatter file obtained from (if you'd used SP flash tool

Quick Update: The Wise Link tool i installed yesterday as i mentioned in response to your advice was ver.5.8.0.56 while the one I had before was ver.5.5.1.53, so this is a correction i make to my previous post. While i got the same error i mentioned, i tried selecting each project in the drop down box starting with KR076. each time i would press DOWNLOAD button in the wise link window and unplug and reconnect the tablet with usb cord. i got the same error i said before.

then i noticed the right side does not have any names of files listed in wise link. i pressed pre-download and it says "pre downloaded" but does not fill in the names of files , even if i tick any of the boxes like pre-loader, uboot, boot etc. even though the .sca file is correctly placed in the same directory as the image files. I had previously clicked in the line  and tried to fill a file name and nothing happened, so i think software will auto find the files as its in same directory as sca file !

today i tried to click on the button on each line at left on the name of image and it took me to select file dialog ! surprised ...! so i selected the pre-loader (first line in wise link tool window ) from the ROM extract i had downloaded, trying each file (wise link would beep at me and give an error code, S_DL_PC_BL_INVALID-GFH_FILE_INFO error code 5066. Only for one file (118,924 bytes P1A2001XXXXX12.mbn) it accepted and did not give the 5066 error. So i assumed this is the pre-loader file . I then ticked uboot and secro lines and pointed to the images i had downloaded earlier prepared by MTK droid tools. I tried preloader from droid tools directory but wise link tool gave 5066 error. so it only accepted from the ROM i had downloaded and extracted for preloader.

I then clicked download button in wise link tool , waited 3 seconds and plugged in the tablet in usb port.
the tool started download and did not give errors, i saw the messages "waiting for port" after preloader was downloaded to tablet, and it stopped downloading other two lines uboot and secro for some time, in meantime a message "installing new device driver software" notification appeared, checked device manager, its now trying to install the MediaTek USB VCOM Port (with pid=2000) whereas earlier only MTK usb port would appear.

after this port appeared in device manager the tool started downloading the other two images.

But it seems to me  now, that the tablet responds to the MediaTek USB VCOM Port too as it now had downloaded to it the preloader image.
now i will try to download other images (tablet is still dead to power button press or even it i connect to charging outlet no display at all) from my old MTK droid tools extract folder (original tablet ROM) and try and will inform what happens in evening !
raj555
raj555
raj555
Junior Member
16
11-02-2017, 04:24 PM
#5



Enclosing the screen shot of WLT where it gave error 5066. then later when i selected
 files it flashed the pre-loader. device manager driver screenshot showing the driver in use MTK serial port is also enclosed.

i checked the log file of WLT too for the session where it flashed preloader.

Incidentally the preloader keeps connecting and disconnecting when i connect the tablet and MTK CDC VCOM driver keeps appearing and disappearing in 3 seconds, repeating every minute or so with bell sound from PC.
I mean its not a steady connection. I tried many times. I think maybe i flash wrong pre-loader ? it was in the ROM i downloaded from link on internet for P290ROM about 117KB in size. (in .sca file 1000,000 hex bytes are allocated for this, this is same size as my original droid tools prepared txt (scatter) file ). however as i said before, the 5066 error went away when i selected one of the files in the ROM i got from a link on internet which i extracted, as i explained earlier but continues to show this error ifi select the pre-loader.bin(113KB size)  from the original droid tools extracted folder for my original ROM. This happens
even if i use original txt file scatter from droid tools which you told me to put aside.

-----
here is WLT log file for when it downloaded pre-loader ( I deleted some repetitive --ATA CLOSE--- lines)
------
2017-02-10 10:41:14 [INFO]    [COM0]'s
2017-02-10 10:41:14 [DEBUG]   [COM19]Remove MTK USB Port (COM19) \\?\usb#vid_0e8d&pid_0003#5&9250d61&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2017-02-10 10:43:06 [INFO]    [COM19]DL_GetBMTBlockCount() , bmt_block_count = 120 ;WLT.cpp 1000
2017-02-10 10:43:06 [INFO]    Nand Flash pagesize = 0x4000
2017-02-10 10:43:06 [INFO]    [COM19] Hardware detecting report:
--------------------------------------------------------------------------------

 BBCHIP: "MT8127_S00", EXT_26M
 CODE(0x8127), VER(0xCA00), SW(0x0000)
--------------------------------------------------------------------------------

0x0008  EXT_RAM_DETECTION: "S_DONE"(0)
--------------------------------------------------------------------------------
 EXT_RAM_TYPE: "DRAM"
 EXT_RAM_CHIP-SEL: "CS_0"
 EXT_RAM_SIZE: 8192Mb (0x40000000)

 INT_SRAM_DETECTION: "(null)"(1643437708)
--------------------------------------------------------------------------------
 INT_SRAM_SIZE: (null) (0x0E2BC020)

2017-02-10 10:43:06 [INFO]    Storage = 1
2017-02-10 10:43:06 [DEBUG]   NAND_ID: 0x45DE949376
2017-02-10 10:43:06 [DEBUG]   [COM19]EnterCriticalSection LoadRomAll()
2017-02-10 10:43:06 [DEBUG]   [COM19]DL Is Ready, no need to LoadRomAll again.
2017-02-10 10:43:06 [DEBUG]   [COM19]LeaveCriticalSection LoadRomAll()
2017-02-10 10:43:06 [INFO]    [COM19]Switch to High speed com port
2017-02-10 10:43:07 [INFO]    [COM19]Waitting for DA USB VCOM Port
2017-02-10 10:43:07 [INFO]    [COM0]'s
2017-02-10 10:43:07 [DEBUG]   [COM19]Remove MTK USB Port (COM19)  (** this is the old port that used to appear in device manager***)
\\?\usb#vid_0e8d&pid_0003#5&9250d61&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2017-02-10 10:44:01 [INFO]    [COM0]'s DA USB VCOM Port (COM6225975) 7956
2017-02-10 10:44:01 [INFO]    [COM20]Change to DA USB VCOM Port (COM20) (it used new port installed? due to new PRELOADER downloaded to tablet ?? **)
2017-02-10 10:44:01 [INFO]    [COM20]Download now...  (*** here is where it downloaded files using that new port DA USB VCOM  ??**)
2017-02-10 10:44:26 [INFO]    [COM20]Download Finish.
2017-02-10 10:44:33 [DEBUG]   FlashTool_Disconnect begin
2017-02-10 10:44:33 [DEBUG]   FlashTool_Disconnect end return:0
2017-02-10 10:44:34 [INFO]    [COM0]'s
2017-02-10 10:44:34 [DEBUG]   [COM20]Remove DA USB VCOM Port (COM20) \\?\usb#vid_0e8d&pid_2001#5&2373ab64&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2017-02-10 10:45:46 [INFO]    ATA Close


2017-02-10 10:45:46 [INFO]    ATA Close
2017-02-10 10:45:46 [INFO]    ATA Close
2017-02-10 11:12:10 [INFO]    -------strart  USB ComPort Thread ------------------------
2017-02-10 11:12:12 [INFO]    ==================================================
2017-02-10 11:12:12 [INFO]    WiseLinkTool v5.8.0.56
2017-02-10 11:12:12 [INFO]    Build 0056 on Nov 10 2015
2017-02-10 11:12:12 [INFO]    Brom library v7.1529.3.0
2017-02-10 11:12:12 [INFO]    Download agent v3.3001.0.2015
2017-02-10 11:12:12 [INFO]    Eboot library v1.1148.0.0
2017-02-10 11:12:12 [INFO]    Meta library v6.1120.0.0
2017-02-10 11:12:12 [INFO]    Inet library v1.4.3.2
2017-02-10 11:12:12 [INFO]    SLA library v1.0.0.15
2017-02-10 11:12:12 [INFO]    CheckAction library v1.3.0.4
2017-02-10 11:12:12 [INFO]    ==================================================
2017-02-10 11:12:40 [INFO]    ATA Close
2017-02-10 11:12:40 [INFO]    ATA Close
--------------
I am also enclosing entire log file (20170210.log.txt) for that session (WLT creates separate log files each session) in case i missed anything.
-----------------
Now the VCOM DA USB port keep appearing and disappearing in device manager. the original MTK USB PORT no longer appears.
Attached Files
.jpg
adm007 2017-02-10, 10_30_36.jpg
Size: 117.83 KB / Downloads: 4
.jpg
adm013 2017-02-10, 10_44_13.jpg
Size: 135.56 KB / Downloads: 4
.jpg
adm015 2017-02-10, 10_44_27.jpg
Size: 135.55 KB / Downloads: 3
.txt
20170210.log.txt
Size: 8.93 KB / Downloads: 2
hovatek
hovatek
hovatek
Administrator
49,570
11-02-2017, 11:03 PM
#6
(11-02-2017, 04:24 PM)raj555 Enclosing the screen shot of WLT where it gave error 5066. then later when i selected
 files it flashed the pre-loader. device manager driver screenshot showing the driver in use MTK serial port is also enclosed.

i checked the log file of WLT too for the session where it flashed preloader.

Incidentally the preloader keeps connecting and disconnecting when i connect the tablet and MTK CDC VCOM driver keeps appearing and disappearing in 3 seconds, repeating every minute or so with bell sound from PC.
I mean its not a steady connection. I tried many times. I think maybe i flash wrong pre-loader ? it was in the ROM i downloaded from link on internet for P290ROM about 117KB in size. (in .sca file 1000,000 hex bytes are allocated for this, this is same size as my original droid tools prepared txt (scatter) file ). however as i said before, the 5066 error went away when i selected one of the files in the ROM i got from a link on internet which i extracted, as i explained earlier but continues to show this error ifi select the pre-loader.bin(113KB size)  from the original droid tools extracted folder for my original ROM. This happens
even if i use original txt file scatter from droid tools which you told me to.

-----

From your screenshots and log, I can see you're mixing files from the downloaded ROM and your previous dump. I would advise you pend that approach too for now.
Let's focus on the WLT and .sca firmware. What other files are you able to load apart from preloader.bin

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
raj555
raj555
raj555
Junior Member
16
12-02-2017, 04:51 AM
#7
(11-02-2017, 11:03 PM)hovatek
(11-02-2017, 04:24 PM)raj555 Enclosing the screen shot of WLT where it gave error 5066. then later when i selected
 files it flashed the pre-loader. device manager driver screenshot showing the driver in use MTK serial port is also enclosed.

i checked the log file of WLT too for the session where it flashed preloader.

Incidentally the preloader keeps connecting and disconnecting when i connect the tablet and MTK CDC VCOM driver keeps appearing and disappearing in 3 seconds, repeating every minute or so with bell sound from PC.
I mean its not a steady connection. I tried many times. I think maybe i flash wrong pre-loader ? it was in the ROM i downloaded from link on internet for P290ROM about 117KB in size. (in .sca file 1000,000 hex bytes are allocated for this, this is same size as my original droid tools prepared txt (scatter) file ). however as i said before, the 5066 error went away when i selected one of the files in the ROM i got from a link on internet which i extracted, as i explained earlier but continues to show this error ifi select the pre-loader.bin(113KB size)  from the original droid tools extracted folder for my original ROM. This happens
even if i use original txt file scatter from droid tools which you told me to.

-----

From your screenshots and log, I can see you're mixing files from the downloaded ROM and your previous dump. I would advise you pend that approach too for now.
Let's focus on the WLT and .sca firmware. What other files are you able to load apart from preloader.bin

Yes, I understand, Thanks! I was doing this (mixing files) only because i did not really fully trust the authenticity of the downloaded ROM for P290 (unofficial source without any user comments validating it) and wanted to use dump files for that reason.  Since WLT did not accept my dumped preloader,  i used the ROM download preloader (checksum issues ? ) and other files it accepted when i used my dumped ROM folder. I will follow your method for now....

-------
here is the phone.info file from rom dump which tells of the general details, I think i have not mentioned this anywhere before. when i should have prefaced this post with these details first.

Hardware : MT8127
Model : Micromax P290
Build number : MMX_P290_SW_V1.0.B_HW_V1.0.0_080915
Build date UTC : 20150923-131607
Android  v : 5.0.1
Baseband v: -----
Kernel v : 3.10.54+ (jenkins@jenkins) (gcc version 4.8 (GCC) ) #1 SMP  Wed Sep 23 21:21:44 CST 2015
Uboot build v : ----- should be  root shell
LCD Driver IC : 1-kr076_ek79007_wsvga_dsi_vdo
------------------

reply to your question is : Nothing else was downloaded i think, looking at log file. only preloader.
that preloader download was ok is seen from fact that when plugging in tablet, device manager shows it to install "MTK 65xx Preloader" in "other devices", previously only "MTK USB port" would appear in Serial ports. However MTK VCOM DA driver is not getting into device manager and code 10 is shown. only "MTK 65xx preloader - CDC data" is detected when connecting the tablet, as confirmed by USBDview.exe program too. (attaching screenshot). problem is it lasts only 3 seconds and goes away from device manager. after a minute it repeats. (unstable). during those 3 seconds it appears in USBDview too with green (connected) dot, with status YES shown in it. Tried with vol dwn pressed and then connect to PC then release vol dwn on tablet, no effect. tried pwr button in similar manner. no effect. only the same thing happens.

explanation: when preloader was downloading in WSL window (i think it was META mode as only MTK USB PORT was appearing, it no longer appears now after the flashing) i observed it was waiting for another port to be ready (VCOM DA port) for driver to be installed, it said "waiting for driver" to download other two images i had ticked (uboot, boot, secro) however it never downloaded those images is my thinking as i was seeing the screen because the other driver it wanted did not install.
Attached Files
.jpg
adm004 2017-02-12, 09_09_06.jpg
Size: 171.67 KB / Downloads: 2
raj555
raj555
raj555
Junior Member
16
12-02-2017, 05:19 AM
#8
Also I opened the file Y1A2001XXXXX12.zip in ROM Folder in effort to check if this is really P290 ROM (!)
obtained build.prop file and peeked into it. (enclosed) the first section shows LRX21M and this is the one i see in my tablet too (before it bricked) and the name jenkins. Also the latter part of this file shows "P290 " etc info which corresponds to my tablet. only in scatter (.sca) file i had doubts because adding the file size in each section hex addition did not get the next section address (problem i already reported in previous post) but adding double the file size did !

#import /custom/cip-build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX21M
ro.build.display.id=LRX21M
ro.build.version.incremental=1442039640
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.1
ro.build.date=Sat Sep 12 14:35:18 CST 2015
ro.build.date.utc=1442039718
ro.build.type=user
ro.build.user=jenkins
ro.build.host=jenkins
ro.build.tags=release-keys
ro.product.model=r712_nand
ro.product.brand=alps
ro.product.name=full_r712_nand
ro.product.device=r712_nand
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt8127
# ro.build.product is obsolete; use ro.product.device
ro.build.product=r712_nand
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_r712_nand-user 5.0.1 LRX21M 1442039640

release-keys
ro.build.fingerprint=alps/full_r712_nand/r712_nand:5.0.1/LRX21M/14420396

40:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/topwise/r712_nand/system.prop
#
#
# system.prop for generic sdk
#

ro.sf.lcd_density=160

latter part of file:
----------
# begin ROCK GOTA properties
ro.rock.gota.brand=Micromax
ro.rock.gota.model=Micromax P290 (*** this iS my table model ****)
ro.rock.gota.version=MMX_P290_SW_V1.0.C_HW_V1.0.0_120915 (** will check this ***)
ro.rock.gota.sd=true
ro.rock.gota.uaver=3.1.2
# end ROCK GOTA properties
----------------
Attached Files
.txt
build.prop.txt
Size: 5.45 KB / Downloads: 2
hovatek
hovatek
hovatek
Administrator
49,570
12-02-2017, 04:44 PM
#9
(12-02-2017, 04:51 AM)raj555 explanation: when preloader was downloading in WSL window (i think it was META mode as only MTK USB PORT was appearing, it no longer appears now after the flashing) i observed it was waiting for another port to be ready (VCOM DA port) for driver to be installed, it said "waiting for driver" to download other two images i had ticked (uboot, boot, secro) however it never downloaded those images is my thinking as i was seeing the screen because the other driver it wanted did not install.

I believe you're using the firmware @ https://docs.google.com/uc?id=0BxU-0vFCR...UlYU0FnUmc
Connect the tab to PC (without holding any button)
Update whatever it gets detected as using the guide @ https://www.hovatek.com/forum/thread-16839.html .
Use the VCOM drivers in the guide
BTW, don't hold any button when connecting to PC for flashing
This post was last modified: 12-02-2017, 04:46 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
raj555
raj555
raj555
Junior Member
16
13-02-2017, 06:49 AM
#10



(12-02-2017, 04:44 PM)hovatek
(12-02-2017, 04:51 AM)raj555 Thanks for the links ! I will use the links and try that, and inform. The adfly gets in the way of proxies i used, and says that i am using ad blocker when its the proxy servers that are using ad blockers ! will try in other ways and get back on results !

I believe you're using the firmware @ https://docs.google.com/uc?id=0BxU-0vFCR...UlYU0FnUmc
Connect the tab to PC (without holding any button)
Update whatever it gets detected as using the guide @ https://www.hovatek.com/forum/thread-16839.html .
Use the VCOM drivers in the guide
BTW, don't hold any button when connecting to PC for flashing
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram