Hi!
I have a mediatek MT6765 device which has got its emmc corrupted probably because of my pc shutting down while I was trying to flash stock image. Now, I cannot flash images using MTKClient.
When I am using Mtkclient, I am getting this error while flashing (python mtk w boot boot.img --preloader <preloader_dumped_from_device>):
Code:
Traceback (most recent call last):
File "/home/me/.miui/mtkclient/mtk", line 814, in <module>
mtk = Main(args).run(parser)
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_main.py", line 617, in run
da_handler.handle_da_cmds(mtk, cmd, self.args)
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_da_cmd.py", line 683, in handle_da_cmds
self.da_erase(partitions=partitions, parttype=parttype)
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_da_cmd.py", line 414, in da_erase
res = self.mtk.daloader.detect_partition(partition, parttype)
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_daloader.py", line 169, in detect_partition
data, guid_gpt = self.da.partition.get_gpt(self.mtk.config.gpt_settings, parttype)
File "/home/me/.miui/mtkclient/mtkclient/Library/partition.py", line 60, in get_gpt
data = self.readflash(addr=0, length=sectors * self.config.pagesize, filename="",
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_daxflash.py", line 888, in readflash
if self.cmd_read_data(addr=addr, size=length, storage=storage, parttype=parttype):
File "/home/me/.miui/mtkclient/mtkclient/Library/mtk_daxflash.py", line 868, in cmd_read_data
param = pack("<IIQQ", storage, parttype, addr, size)
struct.error: argument out of range
(Getting the same error while getting the gpt table with python mtk printgpt --preloader <preloader_dumped_from_device>)
Using SPFlash tool, I am getting stuck at Download DA 100% then recieving BROM ERROR: STATUS_EXT_RAM_EXCEPTION (0xC0050005)
Is there a way to fix this error and bring, my device back to life?
Pls help this little noob
noob_developerdfd said:
Pls help this little noob
Click to expand...
Click to collapse
noob_developerdfd said:
Pls help this little noob
Click to expand...
Click to collapse
u need dongle like ufi or easy jtag plus for fixing ur device emmc
it probably have bad health issue
samsujjamanrifat said:
u need dongle like ufi or easy jtag plus for fixing ur device emmc
it probably have bad health issue
Click to expand...
Click to collapse
I did come across them but they are too expensive in India and I am not sure if I am gonna use them again. is it possible to rent for some time and then return back, like second handed, you know?
noob_developerdfd said:
I did come across them but they are too expensive in India and I am not sure if I am gonna use them again. is it possible to rent for some time and then return back, like second handed, you know?
Click to expand...
Click to collapse
no its not possible to rent
go to nearest technician and u must
samsujjamanrifat said:
no its not possible to rent
go to nearest technician and u must
Click to expand...
Click to collapse
Oh, okay welp ig thats the only option left
But still, lemme know if there is any other way to fix it at home, by that time imma gonna find any nearby technician
mediatek devices have two modes.
1) preloader mode is used for SP Flash tool. as long as preloader is detected, you can unbrick any time. it might require special DA.bin and auth_sv5.auth files in case you formatted emmc and lost permissions to flash (like STATUS_SEC_DL_FORBIDDEN or something).
it is also possible to flash without permission.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
2) in case preloader is corrupt, still there is bootrom mode. this requires to open back cover and find KCOL0 test point.
https://forum.hovatek.com/thread-11802.html
if you can't find test point maybe other methods work.
[INFO] How to Boot Mobile Phone to EDL and VCOM Mode
How to Boot Mobile Phone to EDL and VCOM Mode MTK and SPD CPU: Manual boot: (Vol-) or (Vol+) or (Vol-)+(Vol+)+(Power) Boot by Cable: Boot by Testpoint: KCOL0 + GND / CLK+GND ===================================================== Qualcomm...
forum.xda-developers.com
However, SP Flash Tool or mtkclient always come with highest risk to brick, it's your responsibility not to blindly trial or follow random people advice without knowing what you're actually doing. read golden rules
- do not flash preloader
- do not format whole eMMC
- do not use foreign scatter file
guess you did some or all wrong. it's always good idea to do a research what the error code actually means.
List of SP Flash Tool errors, their meanings and their and Resolution – Flash Stock Rom
flashstockrom.com
2) in case preloader is corrupt, still there is bootrom mode. this requires to open back cover and find KCOL0 test point.
https://forum.hovatek.com/thread-11802.html
Click to expand...
Click to collapse
I didnt know about the bootrom mode, I would have a look at that
However, SP Flash Tool or mtkclient always come with highest risk to brick, it's your responsibility not to blindly trial or follow random people advice without knowing what you're actually doing. read golden rules
- do not flash preloader
- do not format whole eMMC
- do not use foreign scatter file
Click to expand...
Click to collapse
Thanks for mentioning those rules, I will make sure to follow them in the future
guess you did some or all wrong. it's always good idea to do a research what the error code actually means.
Click to expand...
Click to collapse
The link that you provided, I already went through it and tried all possible solutions, but none of them worked T-T
noob_developerdfd said:
The link that you provided, I already went through it and tried all possible solutions, but none of them worked T-T
Click to expand...
Click to collapse
according to your error code just found this:
"Error 0xC0050005
Status of error: ERROR STATUS_EXT_RAM_EXCEPTION (0xC0050005)
Meaning: The firmware you're trying to flash is either not compatible with your device or you have selected the wrong flashing settings.
resolution:
Ensure that the file(s) you're trying to flash are actually for your exact phone model
Ensure you tick the boxes for only the files present in the ROM you're about to flash"
aIecxs said:
according to your error code just found this:
"Error 0xC0050005
Status of error: ERROR STATUS_EXT_RAM_EXCEPTION (0xC0050005)
Meaning: The firmware you're trying to flash is either not compatible with your device or you have selected the wrong flashing settings.
resolution:
Ensure that the file(s) you're trying to flash are actually for your exact phone model
Ensure you tick the boxes for only the files present in the ROM you're about to flash"
Click to expand...
Click to collapse
Yeah, I downloaded fastboot ROM from my device from https://xiaomifirmwareupdater.com/ and I selected the scatter file provided with the ROM, so imma pretty sure files are present in the ROM
there are different models 32/64/128GB
aIecxs said:
there are different models 32/64/128GB
Click to expand...
Click to collapse
Yeah, I got the one for my Redmi 9 Activ India (cattail)
there are different models 64/128GB for Redmi 9 Activ (cattail)
Wait wut, really?
Can you send me the link so that I can download the correct one? (I have been using this one: https://xiaomifirmwareupdater.com/miui/cattail/stable/V12.0.18.0.QCTINXM/)
I have the 64 gb one
the firmware is identical but guess there exist two different scatter inside?
see memory section of specifications
https://www.gsmarena.com/compare.php3?idPhone1=10398&idPhone2=11127
aIecxs said:
the firmware is identical but guess there exist two different scatter inside?
see memory section of specifications
https://www.gsmarena.com/compare.php3?idPhone1=10398&idPhone2=11127
Click to expand...
Click to collapse
One is with 4 GB ram and other 6GB
That might be the case, but I used the same firmware the last time (which I linked) my device got bricked and I did fix it by flashing the firmware with SP Flash tool
can you upload scatter file please
Yeah sure
it shows size of userdata 0xc0000000 (48G) so it looks like the right one for 64G storage model.
Related
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
The phone would randomly get a screen freeze, and the half bottom of the screen got distorted like green and pink lines, then slowly, the pixels were turning to black until the whole screen gets black, but the backlight would remain on.
I had to pull the battery out, and sometimes the phone would work again instantly, some other times, it wouldn't turn on, only after some time, and after a lot of battery pulls.
But last time I got this sudden death, the phone never came back.
I had the stock rom and only root.
My model version is: e2001v21_v89_zlh_hd
Most people with this phone have the e2001_v89_zlh_hd, and most roms on needrom.com are for e2001_v89_zlh_hd, there are a lot of roms for e2001v21_v89_zlh_hd though but I tried everything and I got DRAM Failed.
I use windows 8
SP flash tool v3.1304.0.119, v3.1308.0.125, v3.1316.0.150
And several other roms for both versions.
There is a solution from a French guy about the DRAM failed problem here, but I got the S5 rom downloaded as he stated, and can't get pass the first red bar on SP flash tool.
Do you have any idea what is going on with the 2 versions of the phone? People say that they read on chinese forum that v2.1 (e2001v21_v89_zlh_hd) has got different EMMC. So I guess roms from the e2001_v89_zlh_hd wont work.
I would like to know if you guys have any working rom for my e2001v21_v89_zlh_hd because I really need the phone at the moment. I must get it back to life.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Voliminal_8 said:
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Click to expand...
Click to collapse
ok, there is no difference for using window 8 , xp, win 7, as long as u have installed the driver correctly.
as u said u can see the red bar, that mean yr driver was installed correctly.
all u need is the right preloader.bin
as i can understand from my past experiance, i think that the later batch of the phone, the manufacturer might use different DRAM or they might have changed the coding of the ram. that is why we see quite often there is complaint of DRAM fail when u try to flash the official rom for the phone. Not for newer model of the phone ( yr phone has two/three batches).
so may be u could ask the http://www.needrom.com/mobile/star-tengda-x920/ - smartdigi to create a preloader.bin from their phone for u , then u replace the preloader.bin in yr rom and flash it.
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Voliminal_8 said:
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Click to expand...
Click to collapse
i had read tru the needrom wed regarding thier rom, i saw there is a instruction to pass tru the "DRAM fail."
had u tried that before.
they also had rom that match with yr version.
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Voliminal_8 said:
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Click to expand...
Click to collapse
ok, i just want to know if the procedure as they decribe will work, as i cannot test it, as i don.'t have the phone.
did u manage to get the preloder from them.
if u get the preloader from smartdigi , u stilll get the "DRAM fail" , then i think , may be their phone is an older batch,
for me, if u can read back from from the SP flash tool, (version 3.1316, (i justy learn that there is v3.1328 available)), then definitely u can flash yr phone with this preloader.bin
note
since u can't even go to recovery, then there is no way u can flash the rom with card flash rom from smartdigi, the only way to recover yr phone is tru cable flash rom that mean, u have to pass tru the "DRAM fail"
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Voliminal_8 said:
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Click to expand...
Click to collapse
no, it does not matter if it is preloader port or vcom port, actually they don,t make difference if u flash the rom.
that mean yr computer is talking to the phone correctly.
now the most important part is the "preloader.bin" file in yr rom must match the dram in yr phone.
that is why u hve to ask who has yr exactly same model of yr phone to create a preloader.bin.
or just try to download the preloader.bin as many as u can.
if u have a friend who has the phone same as as yours, then i can help to create from his phone, or u can create the preloader.bin from his phone
edit,
try to download the latest sp flas tool v3.1324 or v3.1328 ,flash the rom with it.
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Voliminal_8 said:
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Click to expand...
Click to collapse
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
stevenma61 said:
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
Click to expand...
Click to collapse
Well... installed windows 7 in another partition.
It was like I never did it, exactly the same result. Everything behaved the same.
I don't know... maybe I have crappy mtk drivers, or I'm doing something wrong while installing them.
Let me describe the steps, and if I'm somewhere wrong you can tell me.
Well, after a clean windows 7 install, I connect the phone to the pc (with or without battery,I think I tried both, didn't see something change) it gets to "other devices" as an "unknown device". right click to update driver software, select the folder with vcom drivers.
It gets recognized as a mtk usb port.
Try to flash like that, same results.
Then I go to update driver again, but this time I click "let me pick from a list of device drivers on my computer." I uncheck show compatible hardware, then I choose MTK Preloader USB VCOM Port.
the device now shows up to the device manager as "MTK Preloader USB VCOM Port".
Try to flash, everything is the same...
I read somewhere, that the normal installation of vcom drivers is kinda different, that it get's shown up as "MTK Preloader USB VCOM Port" right away, and I read that when you install the vcom driver correctly, it connect and disconnects the device every 3 seconds.
Well.. I didn't manage to get the preloader.bin yet, I'll ask for it, but why the official rom on needrom.com preloader.bin is not working with my phone? And why would smatdigi preloader.bin would work for me?
I tried roms that are for e2001v21_v89_zlh_hd but even their preloader wouldn't work for me.
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear? okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool. ROM's of new devices are hard to find, even for n9770 (mt6577) there are ROM versions from 06-2012 till now. so, if you got a "newer" device, you need to get the correct firmware and flashtool should flash without problems. also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Chrizzly92 said:
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear?
Click to expand...
Click to collapse
Clear bro, but I never really managed to do a flash. Just never. I only get dram failed.
Chrizzly92 said:
okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
Click to expand...
Click to collapse
I don't think I did any more harm, since nothing really fot flashed.
Not I don't have a backup :/
Chrizzly92 said:
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool.
Click to expand...
Click to collapse
I bought it from focalprice, even if they send me any rom, it will be one of the officials found in needrom.com ... So I don't think they'll handle it.
Chrizzly92 said:
also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Click to expand...
Click to collapse
How can I check that the second drivers is installed correctly?
just open your device manager and check, if the device gets recognized correctly. start a flash and check, if there are any devices gets loaded while trying to flash. if so, install the correct driver. there are some issues with that sometimes.
if this won't work, try using MTD tool. flasing through there should work always, but it got some issues with vcom drivers. you need to assign every vcom port to the mtk device. explaining of this is retty hard since english isn't my motherlanguage, so its best to check google or xda for that.
also, can you start your device into recovery, or is it really "dead"? no bootlogo, nothing?
No the device is hard bricked, no recovery at all. Not anything. :/
I can't use MtkDroidTool, it doesn't detect my device.
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Chrizzly92 said:
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Click to expand...
Click to collapse
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Voliminal_8 said:
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Click to expand...
Click to collapse
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
china phones
stevenma61 said:
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
Click to expand...
Click to collapse
been to a lot off repair phones shop and all stead screen x920 done buy a SquareTrade 2 yr warranty £30.99 ins on phones
So, here is the firmware flash guide for B15Q. It assumes either a Win7 x86 machine or a x64 with driver signature verification disabled (but Win8/8.1 in any variant or W7x64 is NOT RECOMMENDED).
I assume no warranty for bricked devices, especially not if you manage to kill your PRELOADER or DSP_BL. Double and triple check before downloading.
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
In the tab "Download", click on the "Scatter loading" button and select the downloaded file "MT6582_Android_scatter.txt". spFlashTool usually remembers this across restarts.
Unplug the phone at the computer side if you want to work with it later (the MicroUSB ports don't like too many inserts, they wear out physically).
A) ReadBack for backup of existing firmware/userdata
This will involve a ****load of typing for the first readback.
Open the scatterfile using Notepad++ or any editor capable of handling UNIX line endings, NOT notepad
You will see a lot of blocks like
Code:
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xC00000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
In spFlashTool, select the "Readback" tab.
For all the blocks you see in the scatterfile (IDs 0-23), repeat the following:
Click "Add"
Double-click on the newly appeared row
Choose a filename (e.g. preloader.bin for the first block; some blocks will have name = NONE, use the partition_name here for the filename) and click SAVE
A window "Readback block start address" will appear
Choose Type = "hex". Copy (Ctrl+C,Ctrl+V, and take care to exactly select the hex value! Do NOT type the hex values by hand!) the value from linear_start_address (with the 0x) into the "Start address" box and the partition_size value in the "Length" box, press OK.
Unless you are at the SYS23 partition BMTPOOL, proceed to the next block, repeat from above.
The SYS23 partition can not be backed up, because it has invalid lengths. Do not enter it into spFlashTool.
CHECK THE VALUES FOR START ADDRESS AND LENGTH IN THE TABLE. CHECK THEM ANOTHER TIME.
Press "Read back" button at the top.
Plug in the phone with the battery removed(!) and wait. This process will take time and consume approx. 3-4GB of disk space.
Archive the files you created somewhere safe. Do NOT distribute anything to other people except the BOOTIMG, RECOVERY and ANDROID partitions, because the other partitions contain data that is hardcoded to your board (e.g. IMEI/MAC addresses, sensor calibrations,...) or your private data and app data (SYS22/USRDATA).
If you want a full backup to disassemble by hand lateron (aka you trust in nothing going wrong and don't want to do the hard work except when you need it), just create one readback section with start=0x0 and length=0xE5720000 - this backups everything in one file.
B) Download for flashing new firmware
In spFlashTool, select the "Download" tab
In the dropdown box below the scatter file, keep it at "Download only" or set it if this is not the case
Uncheck all the boxes in the table
Double click on the "Location" column of the BOOTIMG, RECOVERY, ANDROID or USRDATA rows which you want to flash, select the appropriate image file.
Check that you selected the correct images for the correct partitions!
CHECK THAT ONLY THE ROWS WHICH YOU WANT TO FLASH ARE CHECKED. ESPECIALLY, NEVER EVER CHECK THE PRELOADER, MBR AND EBR PARTITIONS. YOU HAVE BEEN WARNED.
Press Download
Plug in the phone with the battery removed and wait. spFlashTool will tell you when it's done.
Unplug phone from computer (!) and put in the battery.
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
When you have a running ROM on it, you may also try to keep the battery in the phone during flashing; just press Download on the PC, then select Shutdown in the Android menu that appears after holding Power pressed. Once the phone has shut down, it will vibrate shortly and then be detected by spFlashTool. I also recommend using a high-quality USB cable and not a worn out one because USB cables with worn out plugs may lead to issues during transmission.
NAND reflush?
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
uhuru-meditation said:
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
Click to expand...
Click to collapse
Bigal1337's image should also contain a preloader, but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
harddisk_wp said:
.....but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
Click to expand...
Click to collapse
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
Click to expand...
Click to collapse
I think I have found something... this chinese rooter apparently messed with internal symlinks, and the firmware update broke as it assumed "stock" contents...
Another reason not to trust rooters where one can't even read the description because its chinese...
harddisk_wp said:
Another reason not to trust rooters where one can't even read the description because its chinese...
Click to expand...
Click to collapse
I agree there. I gave up on rooting B15Q.
On the side note: lately I had 2 spontaneous reboots after this reflash and resurrect.
It happened after I used "official" messaging app more precisely after I send a message and close the app..
.
Did anyone noticed this? - it is 1022 I have up and running.
Other than that it works fine.
Hello,
I tried your workaround but haven't succeeded yet. And yes my phone also is bricked, unfortunately.
My phone halts where you have to choose a language after a factory reset. At that moment I get some messages that some services had stopped. Like Google keyboard, Youtube and some more. I can click OK but this doesn't get me passed these messages and they reappear. I only can switch off the phone.
I tried your workaround on a x64 machine (and got the PMT message) because that's what I have. I am preparing a x86 machine which has XP on it but on launching SP Flash Tools I get the message the configuration of the computer is not correct. Will W7 32-bits do the trick?
Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?
Update 19 april 2015.
I managed bringing back my phone to life. I did another attempt by rebooting my 64-bits computer (as you wrote in the beginning) because at that moment I didn't had a 32-bits machine. It worked wonderwell. So, I'm using my phone again. Like uhuru-meditation I give up rooting for the moment. Nevertheless Android 4.4.2 I still like this phone. Hope it won't let me down after this major reset. Keep fingers crossed.
harddisk_wp many thanks for your hard working in making this workaround. It sure has cost you more then an hour's work.
I hope you read my questions and can or will answer them.
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/show....php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/show....php?t=2263455
Best regards,
2 Questions
Good day
I have the same questions as a previous user, but I cannot find any answer to it:
"Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?"
Could you please help with these? Should I use uboot.img as well? And does system.img go to the Android row?
I added this 3d question later: is it safe to flash SS phone with the DS file?
Kind regards
"PMT changed for the ROM" and SP Flash Tool version
Hello,
I'd like to say big thanks and report that my B15Q was saved thanks to this thread, after a failed upgrade to the 1.016.00 firmware (due to the Chinese root app).
Moreover, I would like to point out that the procedure worked only with the v5.1352.01 version of SP Flash Tool. All other versions I've tried bailed out with the "PMT changed for the ROM; it must be downloaded" message. Unfortunately, the thread which is listed in the instructions refers to a version of SP Flash Tool more recent than v5.1352.01. A link to the said version can be found in this post: http://forum.xda-developers.com/showpost.php?p=58810386&postcount=4
Regards,
Aurél
harddisk_wp said:
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
...
...
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
Click to expand...
Click to collapse
my b15 loopboot
Hello such greetings from Venezuela have a cat b15q dual sim to load the firmware with sp flashtool v3 makes the whole process but remains frozen on the logo even doing a wipe and there no moves have the rom that is posted here I can I am doing wrong excuse my English but I use a translator
Thanks on advanced . Worked fine on my b15q cat . Really much apreciated .
Hello, I'd like to say big thanks and report that my B15Q was saved thanks .Thanks this rom launch perfect
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
...
Click to expand...
Click to collapse
Would you please care to share how you achieved that?
(Following some guide which said that upon ""PMT changed for the ROM..." error one should format the device before downloading, we did that (after reading back everything) but unfortunately, spFlashTool doesn't like the readback PRELOADER partition we extracted.)
goodnight I hope will help me have a cat b15q and remained in recovery mode and I need to flash it revive hope help me thank you .. I'm from Venezuela and one who does not get that software. Excuse my English but q use the translator
CAT B15Q - My Rear Camera doesn't work anymore
Good evening everyone.
After a bad update, my rear camera on CAT B15Q doesn't work anymore. I read all the posts here and I'm using Windows Vista Home Premium 32 bits. I downloaded all the necessary files and when I open the SP Flash Tool, I think it didn't recognize my smartphone and when I try to download any file to the phone the status bar on SPFT still stopped, like if anything is going on. I buy this B15Q on Paraguay. Could this fact be my problem? Anyone could help me, please???
I probably bricked my phone by installing wrong software. Smartphone is dead. not booting. When connect it with usb cable I can hear sound. I'm able to flash it as MediaTek PreLoader USB VCOM Port. but it's not booting.
Same problem here. I wanted to install custom recovery but I got a PMT error and poof. Bricked.
mine also seams to be a problem with this phone mine sounds as if its connecting over n over again to SP Flash Tool and the red download bar goes along but then the yellow flash wont work then i get a flash error any thoughts on how to get out of this?
Hi , try this one make sure you have same CPU MT6580 :
http://www.mediafire.com/file/gdej07owllb7wo4/Leagoo_Kiicaa_Power_MT6580_R2_20180129.zip
found a solution for this you must let the battery go flat first then flash the scatter in the normal way
---------- Post added at 10:46 AM ---------- Previous post was at 10:32 AM ----------
Solution
I've been able to find a solution to the problem. First of all, you have to find another firmware for the phone, because as incredible as it may seem, it has two versions, but I can not find anywhere the difference between the two, but continuing after you find another firmware, you let the phone unload completely (in my case were 2 days and a few hours for it to unload, after that you open the spft and open the scatter file the spft will automatically look for the files, you wait for the files to load sea the only option to download and then click download, now just connect the phone on the pc hold the power + volume up buttons and expect to hear a connected noise, after that the spft will hold the flash normally on your phone.
Click to expand...
Click to collapse
posted by Victor Oliveira
pandashoe said:
found a solution for this you must let the battery go flat first then flash the scatter in the normal way
---------- Post added at 10:46 AM ---------- Previous post was at 10:32 AM ----------
posted by Victor Oliveira
Click to expand...
Click to collapse
please can you explain what you meant by "allow the phone to unload completely"
that just mean let the battery die (preloader for flashing works best with battery disconnected)
aIecxs said:
that just mean let the battery die (preloader for flashing works best with battery disconnected)
Click to expand...
Click to collapse
I guess disconnecting the battery is just the same if its a removable one?
yes it's same effect, it is just about the preloader. the preloader comes up for a second only, in this time one must install VCOM preloader drivers. it is not required to let battery go flat or remove battery but it is helpful because without battery one can be sure device is not booting, and the only available mode left is preloader mode (which is required for flashing)
here is a video to demonstrate preloader
https://youtu.be/O2XWTAYmNUo
be aware if you flash a wrong preloader, you won't be able to repair. your device becomes hard-bricked. do not flash preloader it is not necessary, it's only task is to detect boot mode and load the bootloader (lk) and the original preloader works with every ROM. if you follow any flashing tutorial always uncheck preloader
pandashoe said:
found a solution for this you must let the battery go flat first then flash the scatter in the normal way
---------- Post added at 10:46 AM ---------- Previous post was at 10:32 AM ----------
posted by Victor Oliveira
Click to expand...
Click to collapse
aIecxs said:
yes it's same effect, it is just about the preloader. the preloader comes up for a second only, in this time one must install VCOM preloader drivers. it is not required to let battery go flat or remove battery but it is helpful because without battery one can be sure device is not booting, and the only available mode left is preloader mode (which is required for flashing)
be aware if you flash a wrong preloader, you won't be able to repair. your device becomes hard-bricked. do not flash preloader it is not necessary, it's only task is to detect boot mode and load the bootloader (lk) and the original preloader works with every ROM. if you follow any flashing tutorial always uncheck preloader
Click to expand...
Click to collapse
i have done all dis but the phone is still not coming on
i don't know what you have done, and i don't know what is not working. please be more precise than "all this", descripe steps what you have done and what was expected result, what was happen instead
aIecxs said:
i don't know what you have done, and i don't know what is not working. please be more precise than "all this", descripe steps what you have done and what was expected result, what was happen instead
Click to expand...
Click to collapse
what i was trying to say was that i have downloaded another firmware and i have flashed it on the phone but its still not powering on or charging...i early explained that i formatted the flash using SPFT, so that is my situation right now, dont know what else to do.
thx, now i know that
- preloader is still in good condition
- your PC does detect preloader
- VCOM drivers installed
- SP Flash Tool is working
- you know how to use a scatter file
- you formatted your phone with SP Flash Tool
- you flashed Leagoo_Kiicaa_Power_MT6580_20170915_7.0
- phone is not booting
what i don't know is
- which is your phone model (there are different hardware versions T591/T592)
- how exactly did you format emmc with SP Flash Tool (you previously answered you used "Download only" which is NOT formatting whole emmc)
- which other ROM you tried
aIecxs said:
thx, now i know that
- preloader is still in good condition
- your PC does detect preloader
- VCOM drivers installed
- SP Flash Tool is working
- you know how to use a scatter file
- you formatted your phone with SP Flash Tool
- you flashed Leagoo_Kiicaa_Power_MT6580_20170915_7.0
- phone is not booting
what i don't know is
- which is your phone model (there are different hardware versions T591/T592)
- how exactly did you format emmc with SP Flash Tool (you previously answered you used "Download only" which is NOT formatting whole emmc)
- which other ROM you tried
Click to expand...
Click to collapse
thanks for ur response,
my phone model is T592
secondly, i formatted the flash using the format tab and i chose the 'format whole flash' option, it was after the formatting that i now flashed the rom, using the download only option.
i have also tried this ROM Leagoo_Kiicaa_Power_MT6580_R2_20180129 with the latest version of SPFT but the phone still wont come on after flashing.
unfortunately, formatting whole flash results in lost calibration data, MAC address, IMEI, etc ... which was stored in NVRAM partition, also some device-unique data in PERSIST, and Bad Block Management in BMTPOOL. This data is gone forever and not included in stock ROM, but you may able to recreate IMEI with
snwritetool.com
Well that doesn't explain why phone does not even boot in recovery or bootloader mode. Both ROMs have identical firmware and scatter files (T592) and the kernel and OS is different. Maybe try (T591) ROM or figure out what's the difference between (T592) old screen and (T592) new screen
http://4pda.ru/forum/index.php?showtopic=845144
aIecxs said:
unfortunately, formatting whole flash results in lost calibration data, MAC address, IMEI, etc ... which was stored in NVRAM partition, also some device-unique data in PERSIST, and Bad Block Management in BMTPOOL. This data is gone forever and not included in stock ROM, but you may able to recreate IMEI with
snwritetool.com
Well that doesn't explain why phone does not even boot in recovery or bootloader mode. Both ROMs have identical firmware and scatter files (T592) and the kernel and OS is different. Maybe try (T591) ROM or figure out what's the difference between (T592) old screen and (T592) new screen
http://4pda.ru/forum/index.php?showtopic=845144
Click to expand...
Click to collapse
thanks for your time, recently i tried flashing it but it gives error messages somewhere during the flashing process, ive tried to attach screenshots of the error messages but i dont knw how to attach it, also i performed a memory test on it when it got to EMMC pattern test it came up with an error message again. any idea about wat could be wrong?
check the log file C:\ProgramData\SP_FT_Logs\SP_FT_Dump_02-20-2020-02-20-20\BROM_DLL_V5.log and search for errors
if you got STATUS_SEC_DL_FORBIDDEN then you need other *DA.bin or auth_sv5.auth file
So what’s all this talk about Mediatek Secure Boot and DA files
aIecxs said:
check the log file C:\ProgramData\SP_FT_Logs\SP_FT_Dump_02-20-2020-02-20-20\BROM_DLL_V5.log and search for errors
if you got STATUS_SEC_DL_FORBIDDEN then you need other *DA.bin or auth_sv5.auth file
So what’s all this talk about Mediatek Secure Boot and DA files
Click to expand...
Click to collapse
thanks for your help boss, i think its the emmc flash hardware that is faulty.
please do you know how i can extract my files from the backup i made using the recovery mode. there are 6 backup files in ".backup" format. i want to extract my files from it, how can i do that?
it is probably encrypted, so you can't safe your data. you should bring back your device back to life, even if it just boot into TWRP it will helpful to decrypt
the important partitions for your data are userdata + metadata partitions (you can readback from SP Flash Tool)
in case you are lucky and your data isn't encrypted at all, you can extract userdata.backup with bckp2win
Tried rooting my phone, the oukitel k10000 max, with sp flash tool and it hard bricked straight away, download and recovery don't work but windows recognizes it's there when I plug in with usb so theres hope, I just can't seem to find a solution that actually works in any way, also I didn't back up nvram or dram so now when I try to flash it gives me the (4032) error code for dram, seemingly can't flash anything at all. Help would be greatly appreciated, might even wire some paypal dough if someone can help me get it working again? Also my drivers are installed properly as far as i can tell, i installed them in the disable driver signature verification start-up mode.
Hi , try to flash this firmware and use latest version of SP Flash tool .
Firmware
http://www.mediafire.com/file/42go1g2gsfacncc/Oukitel_K10000_Max_MT6737N_20171025.zip
SP -Flash tool
https://spflashtools.com/
Teddy Lo said:
Hi , try to flash this firmware and use latest version of SP Flash tool .
Firmware
http://www.mediafire.com/file/42go1g2gsfacncc/Oukitel_K10000_Max_MT6737N_20171025.zip
SP -Flash tool
https://spflashtools.com/
Click to expand...
Click to collapse
Same as always, get the 4032 DRAM error
BauerBird said:
Same as always, get the 4032 DRAM error
Click to expand...
Click to collapse
Try to select the (W/O Battery) in connection from option . : )
Do not panic
Don't worry, I've had this exact issue for a while and fixed it. Do you have anything I could contact you on? I'm not really often on xda so if you had discord for example it'd be much easier.
SBAPKat said:
Don't worry, I've had this exact issue for a while and fixed it. Do you have anything I could contact you on? I'm not really often on xda so if you had discord for example it'd be much easier.
Click to expand...
Click to collapse
My Discord is BauerBird, thank you i didn't think it was possible to fix it
Anyone wanna help me with my K10000 Max? Tried installing the stock rom with Magisk installed, with the Smart Phone Flash tool and it completely bricked my phone. Black screen and wont even respond to the power button. When connecting it with a PC, Windows complains about not recognizing the USB device. Do i have a 200€ brick now that i can toss in the garbage? Please help before the wife finds out and kicks my head in!
EDIT: Disconnected the battery and the phone gave little signs of life again and was actually recognized by the flasher software. Tried to flash a stock image again and it gave me this:
S_FT_ENABLE_DRAM_FAIL
[Description]
l [EMI] Enable DRAM Failed.
[Solution]
l Please check your images to make sure it matches with your phone and download again.
EDIT 2: Figured it out myself! In a deep despair, i tried like a 1000 different roms but nothing worked. Even the backup rom that i made before i first flashed my phone didn't work, giving me a different error, something about the chipset. Today, i wondered why the scatterfile said my rom was for the 6735 chipset, as the K10000 MAX is a 6753 device. Changed the line in the scatter file manually and tried to flash it afterwards and i nearly **** my pants when it actually started flashing the phone. Flash was successful and now the phone is working again. Now i just need to find a working custom rom for it.
I need your discord ID as well, the numbers after # in your name.
SBAPKat said:
I need your discord ID as well, the numbers after # in your name.
Click to expand...
Click to collapse
#0023
Sorry I don't really use discord
hi
the other day i tried to dd in a bootloader to add fastboot to my K8+ (2018) LMX210ULMA and wiped my preloader. The device uses an mt6750 chipset and i had made a back up so i have the approriate software to restore it, i even have the scatter file.
The problem is that there is no da_pl.bin file for lg phones to use sp flashtool, i have no download mode and no fastboot.
i have two pc`s one running ubuntu the other windows 7.
i would appreciate any help
any help at all
ok so ive found some versions of sp flash tool that are supposed to get around the authorization stuff and i have an auth file but i keep getting brom errors. the same one in fact. on linux ifs 0x00. ive been looking at and following the tutorials ivs made android rules and all kinds of things but i cant get it to flash. it started to befote i added the stuff in the tutorials. The red line would go acrross the bottom but now i just get the brom errots.
Thumb up for boldness... :good:
Now you have some interesting project there.
Keep us update if you manage to find out any solution.
No idea how to help but Good luck!
https://blog.hovatek.com/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files/
https://ifindhub.com/download-mtk-secure-boot-da-loader-files-mtk-devices.html
ill get there eventually. I have been looking at all the config and ini files and i hate to say it but security might be essier than you think to overcome. just have to erase a few lines here and there and teplace some as needed. idk ty. Dont worry ill keep you guys posted
i really think sometime we over think and see past the easiest solutions. but what do i know im trying to flash an mtk preloader on an lg phone.
im actually trying to unbrick a few phones. two qc `s and the mtk. I kinda bricked one of my lmx210`s on purpose not thinking it would brick. well jokes on me.
Im have a couple questions maybe somebody can help with. In the past couple months on my journey through madness i have tried a few hindred different ways and more flashtools than you could imagine. So far nothing has worked but ive learned alot of theory.
so far though i know that the mtk board is in bootrom mode. We will get back to that as i have an idea....
ok on the qc boards we have the dreaded 9008 mode. I made some progress today. i wanted to see if the LMX210 could boot from SD card instead of the internal. I believe it can but im having trouble with what to do next. p
i used dd to flash the gpt on my sdcard then formatted the partitions to the proper filesystem. when i plugged it in to the usb it lit up but did not boot. But it lit up for the first time since bricking.
But it only lights up with usb plugged in. Add the batrery and it goes dead. It also doesnt show 9008 mode any more.
i went back and changed the boot and recovery images to reflect using the mmcblk system and now windows device manager can see it. But no boot. im wondering first if i might need a special boot loader to boit from sd and two if i might be able to use the same trick to get the mtk running
Some LG firmwares include some files for SPFT, like LGX240ARAT and LGX230HAT.
but do they work with MT6750? In LGX240ARAT there is a dll that mentions MT6755,
but not MT6750. Newer versions probably needed. Or maybe you could hack it. ??...
part of my problem is not knowing what scatter file to use. these phones have thier info all twaktup. the mtk gives several different board/chip types. like we have 6722, 6755, 6750, 6736 and so on. im pretty sure though its a 6750 board with 6755 chipset but do i use the scatter for the board or the chipset.
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Duhjoker said:
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Click to expand...
Click to collapse
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
CXZa said:
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
Click to expand...
Click to collapse
Hi,
If you can reach bootROM mode by pressing any of the volume keys while you connect the phone (Mediatek Inc. MT6627) you should be able write and read the EMMC with amonet.
The tool needs some modifications in order to make it work to MT6750. You can probably try with the mt6753 version which may work for MT6750:
https://github.com/Dinolek/amonet
For reference, use this commit:
https://github.com/R0rt1z2/amonet/commit/6b57d0a99f42739d3b3b2ce962b32ecb8fefd950
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Duhjoker said:
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Click to expand...
Click to collapse
PM me if you need help editing the python script
Regards.
I really appreciate your offer for help. I was looking at the reference for porting and now that i can see the things that would need changing why not go ahead and unlock the bootloader while we are at it. We could save a ton of devices and at the same time give them th3 extra value of being able to twrp and root them.
I have been looking for some way to unLock the bootloader on these phones for days and though it will be some work being able to reflash the preloader AND unlock the bootloader which was my main intent when i bricked it would be worth the extra effort.
Rortiz2 said:
PM me if you need help editing the python script
Regards.
Click to expand...
Click to collapse
I couldnt post the main.py script in the pm but i can attach it here. Thank you so much.
Here is the raw preloader extracted using salt on my pc.
Ok so i went through your source code for the meizu m2 amonet to match it with source code for the mt6750 and i only had to change a couple things. Its pretty much identical to the commit you pointed me too.
As far as i can see your amonet should work just fine with the sp200/lm-x210ulma boards. I did add my .img files to the bin folder though.
Any way i keep getting errors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Rortiz2 said:
Hi,
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Click to expand...
Click to collapse
Hi,
Didn't continue experiments but now also @Duhjoker might be interested about this last new development...
[EXPLOIT] [BOOTLOADER] Mediatek based LG K10 2017 M250 bootloader secure boot bypass. by @OficerX
https://forum.xda-developers.com/lg-k10/how-to/exploit-mediatek-based-lg-k10-2017-m250-t4183545
MT6755 and MT6750 are essentially the same, MT6750 is cheaper and slower version of MT6755, these are compatible, you can use tools for 6755 on 6750.
Here (https://github.com/arturkow2000/lgk10exploit) you have tools that can help you flash preloader (write_boot0.py), these should work on your device.
Open config.py set BR_DEV_PATH to /dev/ttyACM0
then write: python write_boot0.py --brom path_to_your_preloader_bin
This is slow process, may take few minutes (you will see progress while flashing).