Hello xda community,
I recently bought a Doogee mix phone from a friend who said it was, "messed up" I charged it up at home and was greeted with the image tagged below. I tried to flash it with sp but the phone would not be reconized even after I force set the driver as mtp (0xc0060003) Looking for further help to get this phone up and running
Thanks
imgur (dot) com/a/4kOh5
(Sorry forum masters but this is the only way to host images )
I read somewhere that software bricking Doogee Mix is often due to a corrupted preloader_hct6757_66_n.bin: Question I'm asking is: 1. Has anyone recovered by somehow reinstalling this file?
2. Are there any recovery processes for Bricked Doogee Mix that don't utilize SP Flash Tool?
3. How to deal with Battery Icon Coming on changing phone status while connecting USB Cable to Linux PC?
4. Has anyone used SP_Flash_Tool successfully on Slackware64-14.1?
Related
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
hungtrauvang said:
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
Click to expand...
Click to collapse
Flash a new rom
Watch this video...
hungtrauvang said:
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
Click to expand...
Click to collapse
What happens if you power it on while holding down the up and down buttons?
Frogmanstar said:
What happens if you power it on while holding down the up and down buttons?
Click to expand...
Click to collapse
Nothing happens. Really sad.
hungtrauvang said:
Nothing happens. Really sad.
Click to expand...
Click to collapse
This just means you don't have a recovery.. just flash a new rom.
hi XDA community i have a problem regarding my a850 and i hope u or anybody can reply this comment in an instance cuz im in emergency...
IM EXPLAINING MY PROBLEM VERY DETAILED SO IT'S GONNA BE VERY LONG COMPOSITION, INCLUDING FROM IM ROOTING THE PHONE UNTIL I TYPED THIS COMPOSITION
so recently i "Framarooted" my device and was working properly as i expected,then i want to install TWRP, i see my baseband version does not have ROW or CN in there, it kinda like "A850.V13 ...(cant remember)", but i flashed anyway using the ROW version of TWRP and Mobileuncle MTK Tools. When I want to enter recovery (via MTK Tools) it doesnt show up, just stuck at white,big "Lenovo" logo (it probably doesnt work) but i was able to boot back to normal. Then i used System App Remover from Play and attempted to delete some chinese apps, and I DID a mistake... i was so clumsy enough to delete all chinese apps that origins from the rom i accidently deleted the file "classical" (which i guess the entire system ui, launcher etc) . Upon after deletion of that file I SHOULD HAVE NOT DELETE , it suddenly booted off with the startup sound muted halfway (its like, the boot startup sound have like 4 second duration and i heard the sound just for 1 sec).
Then it boots up again, but stuck at the logo "Lenovo For Those Who Do" after startup animation, so i assume this is bootloop or soft brick
Realising this incident i GOOGLED " a850 bootloop","a850 unbrick","a850 stock rom","a850 emergency reset" and "a850 emergency backup", then I found a website which describes how to flash stock rom to a850, so i did that, as it might work, but actually not for my case. I followed and downloaded exactly steps and files from that website and loaded Flashtool with its scatter file, then ticked PRELOAD and selected the preload.img, followed by checking USB mode ,clicking "Forced High Speed", checked the DA DL thingy, clicked Firmware Upgrade and the progress bar moved, after that i plugged my phone, without battery, to the pc via usb. I heard the hardware insert sound, but, Flashtool did not start flashing, it;'s still SEARCHING.
Then I read that u need the USB drivers, so I assume i do not have drivers for this phone. I used the Device Manager step and when I plug my phone, it pops up "MT65xx Preloader"(or MTK i dont remember) then I quickly rightclick and "Update Driver". It has two selections, ONLINE or BROWSE, so i clicked the online solution, but Windows seems cant find the driver i need,
so i used BROWSE option, which i used your usb driver by entering the directory of the driver in your file in "C:\Users\User\Downloads\Compressed\Lenovo_Drivers_SP_Flash_Tool_v3.1316.0.150\Drivers" clicked install then it pops up an error "The third party INF does not contain digital signature information", so it doesnt install. So I used USBDeview and plugged my phone again without battery, it pops up "MT65xx Preloaded" with a purple dot, and if you need, i rightclicked that purple dot and clicked PROPERTIES, and here's information it gave:
Device Name: MT65xx Preloader
Device Type: CDC Data
Description: MT65xx Preloader
Connected: Yes
Safe to Unplug: NO
Disabled: NO
USB Hub: NO
Drive Letter:*blank
Serial Number:*blank
Created Date: 12/10/2014 2:01:15 AM
Last Plug/Unplug Date:12/10/2014 2:01:15 AM
VendorID: 0e8d
ProductID :2000
Firmware Revision : 1.00
USBClass: 0a
USBSubClass:00
USBProtocol: 00
"Hub Port" until "DeviceMfg" is blank
Power: 500mA
USB Version: 2.00
Driver Description: *blank
Driver Version:*blank
Instance ID: USB\VID_0E8D&PID_2000\5&9ec43f0&0&9
After checked, i resorted to HARD RESET via recovery (i tried to go to recovery again to see there's hope in there) and it BOOTED TO RECOVERY! (yay) but again problem strikes, the recovery I see now is FULLY CHINESE i dont understand even a single option i gave there.
So now my phone condition is still cant boot to launcher, and my very last resort is to use the JTAG option
pls help me u all and pls reply ASAP
thank you
irfanadli97 said:
...clicked install then it pops up an error "The third party INF does not contain digital signature information", so it doesnt install.
Click to expand...
Click to collapse
You should log in to windows with out drivers verification in order to install the drivers. Tutorial on how to do than on windows 8 here. Then flashtool should regognize the phone... (you should fix this problem because you may also need it in the future)
There is also a way to fix your phone (if the classic theme is the problem) using ADB. Go to this page and scroll down to ADB method(tutorial) in order to install the classic.apk as a system apk through ADB.
(i am attaching you the apk: View attachment Theme_classic.apk)
Very thanks though cuz this actually solves my problem on my previous devices which doesn't detect upon connection, but I've actually resorted
to do unsoftbrick by a more professional person in my town (he sells and services phones) and it charged me RM50 ($15). Now my phone is back to normal with a rooted state (Chinese superuser app)
Again thanks for replying.
PS:also can somebody redirect me to lenovo a850 modding page? anybody
irfanadli97 said:
Very thanks though cuz this actually solves my problem on my previous devices which doesn't detect upon connection, but I've actually resorted
to do unsoftbrick by a more professional person in my town (he sells and services phones) and it charged me RM50 ($15). Now my phone is back to normal with a rooted state (Chinese superuser app)
Again thanks for replying.
PS:also can somebody redirect me to lenovo a850 modding page? anybody
Click to expand...
Click to collapse
You did good going to a shop...
What do you mean by "Lenovo a850 modding page"?
u know, where rooted users mod their phone with frameworks, custom roms, installing awesome stuff in theirs'
Sent from my Lenovo A850 using XDA Free mobile app
irfanadli97 said:
u know, where rooted users mod their phone with frameworks, custom roms, installing awesome stuff in theirs'
Sent from my Lenovo A850 using XDA Free mobile app
Click to expand...
Click to collapse
This is such a forum
Tried Installing a custom rom using Flashtool. Now the phone can't come and can't be dected by my pc. Installed the Drivers and they Installed. At first first I was having a Brom Error report Now nothing happens when I p,lug the phone.
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
Hi there,
I somehow hard bricked my Jiayu F1 WCDMA smartphone (MTK6572) by flashing a wrong ROM (event though it was supposed to be good).
Now, I can connect the phone to the PC and it get's recognised (the bell rings), but I can't flash anything (nor format) through SP Flash Tool, which keeps bumping the "Enable DRAM FAILED" annoying error, no matter what ROM I'm trying to feed it.
I really could use some help, or at least getting a working scatter file, preloader, etc, just to rule out a fault on the flashed files' side.
Thanks a lot.
barbas66 said:
Hi there,
I somehow hard bricked my Jiayu F1 WCDMA smartphone (MTK6572) by flashing a wrong ROM (event though it was supposed to be good).
Now, I can connect the phone to the PC and it get's recognised (the bell rings), but I can't flash anything (nor format) through SP Flash Tool, which keeps bumping the "Enable DRAM FAILED" annoying error, no matter what ROM I'm trying to feed it.
I really could use some help, or at least getting a working scatter file, preloader, etc, just to rule out a fault on the flashed files' side.
Thanks a lot.
Click to expand...
Click to collapse
1. Uninstall all vcom,preloader and MTK drivers using USBdeview then manually install vcom drivers (you can see how to manually install MT65xx (MediaTek) USB VCOM drivers on Windows if you need help doing this)
2. Once you have vcom drivers installed, delete the SP flash tool folder then re-extract a fresh copy
3. I believe you should have go the correct backup now so go ahead and flash it using sp flash tool. you can try meta mode (flash without battery while holding volume up button) if you're still getting the error
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.
Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient
Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore
The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers
you should be able to repair preloader from bootrom mode (BROM)
How to enter bootrom mode. I am sorry if it is a noob question
Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html
Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved
you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.