We are working on unbricking HTC Desire HD (Qualcomm 8255 chip) in QHSUSB_DLOAD mode. So far we found the HEX file which we can load to phone and move the phone to Streaming_DLoad mode, however we got error when attempting loading a MBN file so we need the Streaming_DLoad mode protocol doc to fix it.
I found this post (thanks E:V:A) but the download is dead. Can you help by sharing to us if you have any of the following documents:
80-V5348-1_J_Streaming_DLoad_Protocol.pdf
80-39912-1_E_DMSS_Download_Protocol.pdf (this one I do have 80-39912-1_Rev_A_DMSS_Download_Protocol.pdf but hopefully your rev-E has more info)
Thank you!
Thanks darkspr1te uploaded the docs in this and this post.
hi,everyone,i am new here,i have opened the diag port on pixel,and installed the qualcom driver.But when i add the diag port in qpst,always say this port may not working,anyone can help me?my qpst version is 2.7.434
Qualcomm 9008 bricked Pixel-diag port
Hi, I know that this is an old post, but I have a bricked pixel phone and have been trying to use qpst to reinstall os. So far no luck since the elf and XML files can't be found. One of the other ways I was going to try was to open the diag port and then try to use Linux to write the os files to the partitions. However, I haven't been able get the diag port open. How did you get the port opened?
Many have faced this problem while using a new phone (Lollipop, Marshmallow and later) with MTKDroid Tools.
Here is the issue - MTKDROID ships with an older version of ADB. (The program hasn't been updated for a few years but it still works.)
This ADB cannot recognize the newer phones. So the obvious solution is to replace the older adb.exe from the 'adb' folder of MTKDroid Tools. But MTKDroid recognizes this and refuses to start, showing us the 'It is impossible to start ADB' error.
I have made a workaround which starts MTKDroid with the older adb and immediately when it finds everything to be OK, replaces it with a newer one. It worked for me. So I hope it will for you too.
Download the zip in attachment.
Instructions.
Goto your MTKDroid/adb folder and delete everything in it.
Open the zip file you have downloaded with winrar or 7zip or anything.
Inside the zip file, there will be 8 files. Copy all these files to the adb folder.
Now you can double click StartMTKDROIDTOOLS.bat and press enter to start MTKDroid Tools. A few black console windows will come and ask you to wait 10 seconds (this is to make sure MTKDroid is loaded completely), wait and don't worry it will close itself when the work is done.
There you go problem fixed and MTKDroid is ready for your command!
NOTE: This fix will help you to start MTKDroidTools and use it to create a scatter file for flashing and backup purposes with SPFlash tool. From what I learned, you can't use this to root your phone unless you enable the temporary root shell from Engineering Mode.
To do that, open your phone dialer, dial *#*#3646633#*#* .
Swipe left to reach Log and Debugging section, there select user2root, in it enable root shell and now connect your phone using the above method.
This method is not guaranteed to work on every phones out there and I still recommend flashing SuperSU the old fashioned way.
Please reply back with any of your troubles or suggestions.
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
pig_slay said:
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
Click to expand...
Click to collapse
I hope it lives.. :fingers-crossed:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
DMcRitchie said:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
Click to expand...
Click to collapse
You're welcome.
I have included the changes you suggested.
Also I found this on stackoverflow which might help on w32.mal.heur detections.
W32 is the platform: Windows 32
Malware is the Category
Heur (Heuristic) might refer to what usually is the family or might be some specific naming of your AV
The heuristic term usually refers to detections based on generic signatures which look suspicious.
That detection looks very generic and might be a false positive.
Click to expand...
Click to collapse
Since the nature of the tool is indeed a hack itself your AV might be showing a false positive.
Still it's all up to you to decide.
All the very best.
Post updated.
Added a 2 sec delay to call MTKDroidTools. (Thanks @DMcRitchie)
Added a guide on rooting.
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Edit: Fixed it. I had to turn off then back on UBS Debugging, simply revoking the USB did not work. It's seeing my device now but says it can't root my device and sends me to an html page with lots more instructions. The tool tells me my device can be rooted this way. https://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 Grrr.. time to spend days jumping through more hoops.
Divergent Droid said:
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
So this didn't fix it, just made it worse. Is there another way to fix? I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Click to expand...
Click to collapse
This was supposed to fix the 'impossible to start error'. You shouldn't have used it if you were not facing that issue.
Don't worry you can just redownload MTK Droid Tools to fix that.
As for rooting, MTK Droid Tools CAN NOT ROOT phones newer than kitkat. Your best bet is to flash a custom recovery and flashing super su.
This guide is for those people who can't use SP Flash Tools because they need a scatter file which MTK Droid Tools can't make for newer androids.
All the best.
Thanks.
You gave me the most detailed answer so far. I got the info to use MTK Droid Tools from a website claiming it will work for Android 6.0 Marshmallow. That's why I tried it. If you are very knowledgeable about rooting in general, perhaps you'll answer my other thread asking someone to help me understand these things better. it seems according to you, i would be able to flash a new rom and SuperSU? See my other post and answer there. https://forum.xda-developers.com/general/help/guru-to-discuss-rooting-t3683594 - I did try the folks at the SuperSU sub forum and they cant help me.
When i connect Infinix Note 4 Pro X571 (bricked) to pc for Mtk to detect, it just boots to recovery mode (twrp)
tried using Maui Meta, it automatically installed vcom drivers then it said "it cannot find Kernal USB comport for AP and Modem handshake. Please check the usb driver version or find the driver owner to check"
thank you so much!! it works
I Get This Only :/ What's wrong? Noob Mistake?
qounik said:
I Get This Only :/ What's wrong? Noob Mistake?
Click to expand...
Click to collapse
I have the same issue. I just want to backup some stuff.
EDIT: this worked for me https://forum.xda-developers.com/showpost.php?p=75722412&postcount=14
Hi
Great fix but I still have a problem, I only have the hardware and baseband detected nothing else, so I can not save.
An idea ?
Thanks
Hi All
I have an Alcatel Pixi 4 (5) 4g 5045Y model and while formatting/downloading a new rom it looks like I accidently formatted the preloader as well resulting in a bricked device. Is there any way to force load the preloader back through spft or anything else ? I do have a rom available from reading it back in spft but as yet unable to split it into the separate files/images.
After searching around it looks like there is a method by joining the GND to a Test point so windows device manager recognises the phone properly but these points are not marked up on the pcb and trying with a multi-meter doesn't appear to keep it connected through the usb connection.
Any help appreciated.
@ Praia
https://forum.xda-developers.com/showpost.php?p=75478190&postcount=2712
Not sure how but I do have a working phone once more which has been flashed with a ROM downloaded from the net with SPFT although I would preferably like to return it back to its original setup.
I do have a full backup ROM made with the readback tab in SPFT (v5.1708.00) but it is in one large file (around 2.5Gb) which I have NOT been unable to create a scatter file for or split into the various partitions from it.
You mention using the "Write Memory" tab but I don't see that tab in SPFT but have just found a Parameter tab where there is some kind of read / write setting but it won't accept the file and not sure of the write length either.
If you mean using the download tab it looks like it is wanting the file split into the different partitions and think I would need a scatter file from the readback file.
I have tried with miracle box and MTK tools to try and create a scatter file but didn't have much luck with either of those.
Is there any other way of getting the large readback file back onto the phone as I don't want to use the current ROM and its scatter file as it is for a 5045x and not a 5045Y and seems there are a few odd bits that don't seem right.
Again and further help appreciated.
Many Thanks
Hello all,
I'm working in a repair center for some manufacturers of professionals PDA.
Sometimes we are facing to hard bricked devices, the devices are simply seen as a "Qualcomm HS QDloader 9008", and so, can't boot.
One of the manufacturers don't want send the files for save the device, so I want to search on my side the solution for save the devices without replacing the Main boards.
Device (android 5-6-7-8-9):
Touch Mobile Computer EF500
The Proven Innovation of Enterprise Mobility
www.bluebirdcorp.com
We have the ROM files for a standard installation, but not the files for use with QFil for example.
So, how can generate the files, if possible, for use QFil ?
- A dump from a working device ? But I can't root these devices...
- Use the standard ROM files for generate the Firehose files ?
- Or use a box like "Magique box" (or other) for send files ?
Thx for your help !