Hello, Before everything, sorry my english. I will go to tell my problem.
All start when i want change my rom MIUI10 to Pixel Expirience.
I used The method of ADB terminal, but in my stupidity, i flash preloader image,
and the cellphone.. is dead. It not Power Up :crying:
If i connecting the cellphone with the computer this is recognize like "Unknow Device" i Search in Internet and I install Mtk and Qualcom Drivers.
In Mi Flash the only that recognize was Qualcom driver "Qualcom HS-USB QD-Loader 9008". I download the Flash Imagen of Redmi 6a Cactus on Oficial Web of Xiaomi.
SP Flash:
In my First Try i Use SP Flash. I download the DA and Auth Files: "MTK_AllInOne_DA_4-19_-signed.bin" And "auth_sv5.auth"
I put this in SP Flash, and selecct the Scatter in the rom folder.
I click in Download and connect the cellphone, The program show the error:
"ERROR: STATUS_BROM_CMD_FAIL (0xC0060005)"
In the options
General: I uncheck "Check Lib Da Match" becose in the moment when i set the Da file, show: "Lib Da not Match".
Connection: I try all method (Uart Port, USB port: High and Full speed, With or W/O Battery)
Mi Flash:
In My Second Try i use Mi Flash
I select the folder room, clear all and refresh and install.
The Error: "Cannot receive hello packet,MiFlash is trying to reset status" follow of "Object reference not set to an instance of an object."
The LOG:
[17:44:41 COM13]:MiFlash 2018.11.15.0
[17:44:42 COM13]:flash in thread name:COM13,id:9
[17:44:42 COM13]:sw in images
[17:44:42 COM13]:flash in thread name:COM13,id:9
[17:44:42 COM13]:[COM13]:start flash.
[17:44:42 COM13]:cannot receive hello packet,MiFlash is trying to reset status!
[17:44:43 COM13]:try to reset status.
[17:44:43 COM13]:Switch mode back
[17:44:43 COM13]:cannot receive hello packet,MiFlash is trying to reset status!
[17:44:43 COM13]:System.NullReferenceException: Object reference not set to an instance of an object.
at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer()
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[17:44:43 COM13]:no provision exit:COM13
[17:44:44 COM13]:flashSuccess False
[17:44:44 COM13]:isFactory False CheckCPUID False
[17:44:44 COM13]:before:flashSuccess is False set IsUpdate:True set IsDone True
[17:44:44 COM13]:after:flashSuccess is False set IsUpdate:false set IsDone true
On MTK drivers don't recognize in the list. I try Change chip: mediatek in options, nothing happen, the mi flash was crashed.
Update: I try with mediatek drivers in onther pc the default driver is "MTK Usb Port", I try all again, and nothign i try install manual above the driver, MTK Preloader Port, MTK VCom Port, and Nothing..
I Try Mt65XX and MT67XX version of this driver.
Update 2: I Try everything with holding Power + Vol Up, Power + Vol -, Vol+, Vol -, the same but connecting the cellphone after hold :v
Update 3: I try with Deep Usb and nothing..
I don't know what to do, help me.
Note: The Port of qualcomm are Connected and disconnected every threty seconds aprox.
THX for Read and Help me :V, Again Sorry my English.
The error is caused by lack of authentication. pay some indian 10$ and he'll be happy to enter his info over teamviewer and flash a brand new image on the device. How do i know? i had this happen to me. The guy's whatsapp is +880 1771-989858 but i don't remember the site for repair he hosted.
Hey, did this guy managed to fix your problem. I have a pretty same issue, except when i start sp flash tool nothing is happening, and from my phone only vibration is working..
Related
Hi,
i have bricked my P780 after flashing with new firmware. Now the Phone is dead with black screen and doesn't start after pressing Power button. After a few trials with SPflash (3.x) i recognized that SPflash had a problem with reading the Scatter-file i.e. the adress mapping. The adresses were set for all areas from 0x0000 to 0x0000. When flashing the phone i didn't see that and i think this is the reason for the dead phone (stupid old man
With Spflash 5.x the Scatterfile was read correctly.
Anyway: Now the phone was detected by the Win7 device manager as Mediatek USB Modem but it works not correctly with SPflash (3.x or 5.x).
I could neither download new firmware nor format the flash. I get always the error: "BROM error DA download to Baseband SRAM failed".
Sometimes i get the message that the power up sequence was problay to short and the bootmonitor sequence didn't work.
Both states are reached after pressing the reset button on the backside when the phone is connected to the PC.
Is there any chance to get the phone working with SPflash again or do i have to use a JTAG-Tool ( if there is one for Mediatek-chips)?
Mattes12345 said:
Hi,
i have bricked my P780 after flashing with new firmware. Now the Phone is dead with black screen and doesn't start after pressing Power button. After a few trials with SPflash (3.x) i recognized that SPflash had a problem with reading the Scatter-file i.e. the adress mapping. The adresses were set for all areas from 0x0000 to 0x0000. When flashing the phone i didn't see that and i think this is the reason for the dead phone (stupid old man
With Spflash 5.x the Scatterfile was read correctly.
Anyway: Now the phone was detected by the Win7 device manager as Mediatek USB Modem but it works not correctly with SPflash (3.x or 5.x).
I could neither download new firmware nor format the flash. I get always the error: "BROM error DA download to Baseband SRAM failed".
Sometimes i get the message that the power up sequence was problay to short and the bootmonitor sequence didn't work.
Both states are reached after pressing the reset button on the backside when the phone is connected to the PC.
Is there any chance to get the phone working with SPflash again or do i have to use a JTAG-Tool ( if there is one for Mediatek-chips)?
Click to expand...
Click to collapse
Hi. First look on the box of the phone. Iff there is something with a date that is something like 03.2014 or more like 09.2014 look what you must do:
1. download SPFlash Tool from here. This are the correct tools for Lenovo P780. DO NOT USE OTHERS.
2. now download the preloader file from here and the drivers from here. And yes, you must reinstall the drivers because your preloader is messed up.
3. unzip preloader file, go to target_bin folder and delete existing preloader(preloader_prada_row.bin), and add the preloader you downloaded, and delete any file from target_bin directory with the name Checksum.ini.
4. now load scatter file from ROM directory(should be target_bin directory)
5. check DA,DL WITH CHECKSUM (NOT OPTIONAL)
6. press Firmware Upgrade button (NOT DOWNLOAD BUTTON)
7. now just now plug usb cable to your phone.
8. firmware flash should start.(some red and other color lines should appear)
9. iff the firmware is not starting remove the back case of your phone and hold pressed the little red button from the right side, for about 20 seconds then release. All this must be done with cable pluged in to your phone.
10. after flash is done a green circle should appear
11. disconect your phone and power on your phone
12. lenovo logo should appear. then you should be pacient because it will took some time before android boots for the first time.
13. Good luck. Hope This Helps You. If not post here again.
Hi stympy,
sorry for the delayed feedback but i had no time to test it until now.
But you where completely right! It was the wrong preloader and the wrong drivers.
Now the phone is running again! Thanks a lot!
Best regards!
Dear DEV, my Lenovo A6000 Dead to chase into device manager computer port and COM 9006 and 24 states Lokl hard disk appeared about 11 Computer format due Security region on computer repeatedly asks you to format is not. Qfil to flash the flasher download fail switch to edl () download fail switch to edl fail system exception: firehose is having trouble such as fail. 'i am very upset right to some measure,a assist me soon sir,please.
Hello
I'm new on this website, my name is François, and I'm french (sorry for my english).
I have a problem with my NO.1 M2 phone. Sunday 7, I'm using it, play with app, at the same time, I received a call and a sms. I answer call, after this I answer sms and come back on app. At this moment, my phone freeze, screen stay on, nothing work. I wait some minutes, unscrew back and shut down 1 mn with the switch. Restart and I only have the NO.1 logo.
If I start with vol+ , I have menu with recovery, fastboot, normal. I can't access recovery (never try before this problem). I access fastboot and try to flash with fastboot command, but I have this answer: "FAILED (remote: download for partition "tried partition" is not allowed. I try format, but "formatting is not supported for file system with type "raw data".
I try sp flash tool. I download the 3 firmware on official website. Driver are installed, sp flash tool see my phone like mediatek preloader usb vcom, or mediatek usb port (if I hold vol+ when connect).
Test with or without battery, change in spft option with, w/o, auto detect battery, download only, firmware upgrade, format all + download, nothing work. With download only, I have only "download DA" (100%) and after BROM ERROR: S_FT_DOWNLOAD_FAIL (4008). With upgrade or other, I have "download DA" next "format" and it's stay at 0% and message "BROM ERROR: S_FT_FORMAT_FAIL (4010).
I use a windows seven laptop, spft from link in post, try with and without xp compatibility, try 3 usb cable, all usb port from my laptop (4), It's allways the same.
I notice, I have this phone from april 2015, come with android 4.4. August 2015, I firmware update with android 5 from july download link, and work perfect all this time.
I have search some answer with my friend Google, try some version of SPFT, try with 3pc (two win 7 and one xp), but nothing work
Thank you for your help.
François
EDIT: Is it possible that is a hardware problem? Like EMMC dead?
So i installed TWRP and flashed a xiaomi android one
It worked ok, some apps were weird
Tried to do the latest update for flyme with TWRP
It installed ok, but after restart it would boot to logo screen and turn off
Fastboot or recovery do not work
All phone does is turn on on 10 sec pwr button press and nothing else
Meizu M6 Note M721H is the version, tried qualcom but gives all bunch of errors and i cannot seem to find a way out
Requesting assistance please
Thankyou in advance
+1
Same problem here.
Folks, "a bunch of errors" is not exactly an accurate description that allows anyone to help you out.
However. Today, after I've tried to restore the TWRP backup of my "devinfo" partition with the intention of relocking my bootloader, I've bricked my Meizu M6 Note (unable to boot OS or the recovery) and subsequently spent about 3 hours googling for a working solution, I've tried reflashing the stock firmware using QFIL (also QPST and a few other tools), but I either got the infamous "Switch to EDL" errors:
Switch To EDL
Code:
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
This was due to the fact that my device was recognized as the Qualcomm (...) 900E device, so I had to go to Device Manager and "Update driver", then manually select the correct one from the list, which was "Qualcomm HS-USB QDLoader 9008" (version 2.1.2.2, but older ones might work as well). After that, QFIL gave me the also infamous "Sahara protocol" errors:
Code:
ERROR: function: is_ack_successful:1121 SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED
ERROR: function: sahara_start:895 Exiting abruptly
ERROR: function: sahara_main:924 Sahara protocol error
ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
However when this error occured, I was able to go to fastboot mode, by pressing the Volume down (-) key and trying to flash the stock firmware again. After this, my phone displayed "fastboot mode" at the bottom of the screen in green. However because bootloader was locked again, I wasn't able to run or flash a TWRP recovery. At this point I was out of ideas.
Thankfully, I've ended up finding an excellent Russian guide by VladimirVVK of 4PDA fame (thanks Vladimir!):
Code:
hxxps://4pda.ru/forum/index.php?showtopic=843179&st=5620#entry69341915
...where a certain UnbreakM6NoteMinimum.rar was uploaded, that included everything I needed to get out of the boot loop. I've reuploaded the file, so hopefully you'll be able to download it, and follow the instructions inside INSTRUCTIONS.TXT (there's a Russian and English version as well):
Code:
hxxps://mega.nz/#!N5ZEFaAb!ez3F4pCJPPs9jFODI2a9_QH8tiGD3GQfDtOP4xkEuDo
My only tip is, that if you find it difficult to put your device into "download mode" (which is NOT fastboot mode) because you're not able to turn it off properly and you can't get into the "Partition manager", do this:
1. Start QFIL
2. Choose Flat Build under "Select build type"
3. Click browse under "Select programmer", select prog_emmc_firehose_8953_ddr.mbn (you can use the file from UnbreakM6NoteMinimum.rar)
4. Connect your device, wait until it shows up as "9008"
5. Start pressing Volume up (+) and Volume down (-) at the same time
6. In upper menu go to "Tools" - "Partition manager", confirm the dialog.
7. Repeat process 5 and 6 until you see the partition manager.
8. Continue the guide in INSTRUCTIONS.TXT (steps 5 and 6 there).
After that, my device was out of the bootloop, however the OS still didn't boot completely (I was running crDroid before the whole kerfuffle), the boot animation started and continued for a couple of minutes then I saw a blank screen. However, now that the original Meizu recovery was restored and I was able to boot into it by holding down Volume up and the Power button. The Meizu recovery mounted an empty 2GB partition on my PC, I was able to copy the stock Flyme 7.0.1.0G stock ROM update.zip on it and flash it after that. My phone is now working again.
Good luck everyone!
Sorry about the "hxxp" links, but I'm not (yet) allowed to link external URLs per xda-developers policy.
meizu m6 note stuck on fast boot
plz help me
I fouund the solution
The 8953ddrmbn file not worked for me so i tried another mbn file from this pack and it worked fine :
mega.nz/#!5cwEWbTa!JQtI1mQslzUMNOgJd13DpxpmLjXTdA6V6tWWp5I0kng
My phone Not Showing 9008 in QFIL
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Tinyhafij001 said:
i have connected and followd all instruction but My phone Not Showing 9008 in QFIL its showing 900E its not happening plzz help me
Click to expand...
Click to collapse
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
geekborg said:
Hi,
When it shows 900E in the windows device manager you must force the installation of the 9008 driver.
Choose "update driver" and "select a driver from a list" and select the 9008 driver even if Windows warns you that this driver is not signed.
Then you will be able to connect to QFIL again and restore the "devinfo" partition.
TWRP SHOULD NEVER BE INSTALLED ON THE "DEVINFO" PARTITION BUT RATHER ON THE "RECOVERY" PARTITION.
I saved some of my partitions of my phone (Meizu M6 Note M721H global firmware)
the files contains "_original" in their filename are the original ones from Meizu (FlymeOS)
https://drive.google.com/drive/folders/1Fc8s5khlz95cXIT0m2kLhqzZXn8yoBdG?usp=sharing
Click to expand...
Click to collapse
Unfortunately I replaced devcfg with devinfo and after that i cant start my device again or switch it to edl 9008
any help ????plz
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?