i posted this already before but the forum didnt show it, so again:
i tried the custom flashtool, even with correct checksum, but result is the same: Storage not match. Every button combo i tried didnt work, with/without battery, phone is always recognised the same MTK USB Port.
So i tried this hardware unbrick method:
[Only registered and activated users can see links Click here to register]
(2016-07-06, 18:40)emmes Wrote: [ -> ]i.......................
So i tried this hardware unbrick method:
Good tut but put it aside. Try this
In SP flash tool check for download only, for example, first three files,-> "Download' -> connect phone with Vol+ button down in Dev. Manager must appear "MTK USB Port" (another name for this device "MediaTek USB Port" as on tut video). If download OK try check all files ->Download If download(yellow stripe) begin but stop at something about 4% -> Stop-> disconnect phone. Try download all in SP MultiportDownload
Explanation: downloading three or less files Flashtool must create on flash new GPT for all partitions with real size(space) according to scat file
(2016-07-06, 23:27)kodor665 Wrote: [ -> ] (2016-07-06, 18:40)emmes Wrote: [ -> ]i.......................
So i tried this hardware unbrick method:
Good tut but put it aside. Try this
In SP flash tool check for download only, for example, first three files,-> "Download' -> connect phone with Vol+ button down in Dev. Manager must appear "MTK USB Port" (another name for this device "MediaTek USB Port" as on tut video). If download OK try check all files ->Download If download(yellow stripe) begin but stop at something about 4% -> Stop-> disconnect phone. Try download all in SP MultiportDownload
Explanation: downloading three or less files Flashtool must create on flash new GPT for all partitions with real size(space) according to scat file
Thanks, but the didnt work.
Let me explain again:
It makes no difference if i push the Volume + Button and plug the usb cable afterwards Or plug it with battery or without buttonpush, it always connects the same MTK USB Port.
Anyway, when i download all or just 3 lines i get this message: STORAGE NOT MATCH
So my conclusion is that Volume + (or Vol- or Power & Vol +) is not working on my device and if this is not working the solution is just with hardware ressurection, i guess
(2016-07-07, 00:14)emmes Wrote: [ -> ]......................................
So my conclusion is that Volume + (or Vol- or Power & Vol +) is not working on my device and if this is not working the solution is just with hardware ressurection, i guess
NO ... When on flash valid boot region (GPT) then is 1) default connection when in DM appears Preloader VCOM Port which used valid data from GPT for further work with phone 2) so called GPIO Boot(the same KCOL0 to GND) in DM appears Mediatek USB Port (BootRom hardcoded loader) when connect with some down button.
When boot region(GPT) on flash invalid(or empty) in DM always appear only Mediatek USB Port wich must use data(files) from loading in Flash Tool SW(scat file) then make(downloading) valid boot region on flash and further download other files according to scat . while slow Mediatek USB Port(USB 1.0 for compatibility) changes to fast Preloader VCOM Port(USB 2.0+) in the notification area(inscription at the bottom right)
So the problem might be that the phone isnt detected as MTK USB Port, it is detected as "Serial USB Port". After i rightclick on device manager, i updated with the MTK USB Port driver, then it is written as MTK USB PORT, but not really i guess.
and the real problem is, i guess, that the firmware which was preinstalled on my phone (v.1.1.3) is not published or leaked at all, maybe this firmware has another preloader. So i just wanna try if i flash the preloader from v.1.1.3 my phone is back again, so i would need somebody (with preinstalled v.1.1.3) who makes a backup via mtk droid tools or similiar so that i can flash the preloader with scatter
Phone request driver by vid / pid not by name
Mediatek USB Port have (see .inf file in driver package)
my file cdc-acm.inf -->
DriverVer=09/11/2014,3.0.1437.1
.........................................................................
%VCOM_BOOTROM%=DriverInstall, USB\Vid_0e8d&Pid_0003
............................................................
VCOM_BOOTROM = "MediaTek USB Port"
I think you can use official v1.1.2 and if download is OK phone will start without problem. This error is not point to preloader.
(2016-07-07, 02:26)kodor665 Wrote: [ -> ]Phone request driver by vid / pid not by name
Mediatek USB Port have (see .inf file in driver package)
my file cdc-acm.inf -->
DriverVer=09/11/2014,3.0.1437.1
.........................................................................
%VCOM_BOOTROM%=DriverInstall, USB\Vid_0e8d&Pid_0003
............................................................
VCOM_BOOTROM = "MediaTek USB Port"
I think you can use official v1.1.2 and if download is OK phone will start without problem. This error is not point to preloader.
mtk driver version:
DriverVer=01/22/2015,3.0.1504.0
CatalogFile=cdc-acm.cat
that's not the problem, been spending now a lot of days with this problem, i even reinstalled win 10 to begin from new
when i connect the phone with Vol + without the battery it connects exactly the same as connected without Vol+ or with afterwards inserted battery
As mention above this mean only one flash hav'nt valid boot(GPT) and FT must do it on flash. Try at first only preloader(not only 3 lines)
(2016-07-07, 04:30)kodor665 Wrote: [ -> ]As mention above this mean only one flash hav'nt valid boot(GPT) and FT must do it on flash. Try at first only preloader(not only 3 lines)
I ve tried that hundred times, it doesnt work. Because the phone doesnt activate the boot/download mode, that Vol+ Button doesnt trigger that!
Time to analyze. I suppose you can do now backup(readback) in SP FT. But as drive backup will do slow brom loader "Mediatek USB Port " it wiil more time than high speed Vcom "Preloader Port" As example when i do my full bicked ht6 backup length 2242445312 (0x85a90000 in hex include system.img) it took ~35min. To you is not necessary do so long back. I
In arch proga ROM_Backup-Splitter It split SP_FT backup(default name ROM_0) into files according to scatter file(as in SW) To choose backup length(end address) see inset "Map of Rom_"
In folder ht6 my important files extraсting from my alive(!) ROM_0 Compare with yours (better in WinHex) . It should look something like mine File pgpt exactly GPT (in which is why there is not enough space ??)
Very intresting to see SP FT log files when occurs error "No Space". See path to yours folder[ Date-Time] in SP FT option
[Only registered and activated users can see links Click here to register]