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?
Related
I have read a lot of posts by Mediatek MT65XX wizards on this forum, so hopefully one of you sees this.
I have a MT6582 based phone (Freetel Priori2) which is now hard-bricked. This started as a soft-bricked device which would not boot due to some software update, and became hard-bricked after I mistakenly flashed the wrong firmware.
Before flashing, the phone would power on, Windows saw a 'Mediatek Preloader USB VCOM Port' and the SP Flash Tool could read the chipset information. After flashing, the phone does not power on or charge and Windows sees a 'MTK USB Port' instead; the SP tool cannot read the phone model and gives the following error: 'Storage type mismatch ! scatter storage type is HW_STORAGE_EMMC, device storage type is HW_STORAGE_NAND'.
I have tried to put it in 'meta' mode by plugging it in while holding different buttons, as well as by grounding the various test points on the mainboard. The port type and error message remain the same. I cannot post an image of the board because of some new user restriction.
Any ideas are welcome, since it is otherwise headed for the trash can.
Flashing wrong firmware has corrupte the partitions.
Can only be fixed using linux and fixing every partitions .then only sp flash tool will recognize
aditya0070 said:
Flashing wrong firmware has corrupte the partitions.
Can only be fixed using linux and fixing every partitions .then only sp flash tool will recognize
Click to expand...
Click to collapse
Hey, thanks for the idea. I'm quite comfortable with Linux, but I don't see any way of accessing the flash once I plug the phone in. Could you give me some more details ?
dooser said:
Hey, thanks for the idea. I'm quite comfortable with Linux, but I don't see any way of accessing the flash once I plug the phone in. Could you give me some more details ?
Click to expand...
Click to collapse
When you read back Recovery, does it look like a valid partition (has "ANDROID!" magic word at the start)? If it does, try erasing MBR and EBRs (if many), then download original MBR, EBR and Recovery. Try to boot into recovery.
If it does not, modify scatter to HW_STORAGE_NAND (according to SPF tool's xml, NAND and EMMC differ by addressing) and try readback again. If Recovery's magic word appeared now, then your Emmc really became Nand
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
Please help, a few days ago my phone decided to stop working for no reason, so I thought it was a ROM problem(I was running Android Pie AOSP Extended). So I reset it, after resetting it the phone was stuck at the LeEco logo, so I decided to use the 9008 mode flashing it, but no matter what I do it always come up with the error Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I don't know what to do, please help.
Did you tried flashing Twrp first in instead of qsahara sometime they give error
They show error also when partitions are messed up so may be u changed partition settings
So try installing Twrp and rewriting partitions then use a pendrive and mount it in Twrp and install a simple room for example AEX and try to boot otherwise try side loading the rom
If u r possible to boot into twrp format device and install any ROM zip through pendrive
I cannot even exit 9008 mode, the phone is completely dead with no respond when pressing any button combination, but it shows up as Qualcomm HS-USB QDLoader 9008 when I plugged in to my PC, and it also doesn't show up when using the ADB devices command. And thanks for replying
Can you add photos of what error it is showing when trying to boot into fastboot mode
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
MrNotJeff said:
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
Click to expand...
Click to collapse
Ok, first, dont give up, 2nd have you put phone into qfil mode as program told you? 3rd check if inside this zip is not 2nd zip, some packages are "double zipped".
MrNotJeff said:
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
Click to expand...
Click to collapse
I had a practically the same problem with Xiaomi Redmi Note 5 Pro (Chinese model)
Inside the zip file there is a file (or two of them) responsible for uploading the ROM. It first sends one of those files and the Qualcomm loader puts it in RAM and boots that file.
If successful, the upload continues, but if that file is wrong, it will not boot it and will not load. So the zip file you have may not be for the exact model of your phone. Try to find another one, maybe a different version...
Hope this helps.
Sent from my GM1900 using Tapatalk
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?
Hi everyone, I bought this phone working from second hand but the seller told me he tried to unlock the bootloader without success and the phone still loose the fingerprint sensor, so I decided to unlock the bootloader successfully following THIS thread and made a downgrade to Android 9 according to THIS other tutorial hopping to get it work again but I wasn't able to do it, so I decided to just use LGUP to install the same Android 12 that I had but the problem started at this point because once the KDZ was installed successfully, the deviced got a bootloop but I still was able to get into EDL, Fastboot and Download Mode, so I tried the steps from THIS other thread to unbrick it but it got even worse at this point, I flashed all the abl, xbl, etc. partitions and the "rawprograme files" via QFIL and then the phone won't even gave any life signals. I contacted someone that some months ago had the same problem and he told me that I could get into EDL by short pining the test point on the motherboard, which actually worked, so I extracted the KDZ Android 9 rom that I flashed in the first place to get the original abl, xbl, etc. partitions that I crossflashed from a v50 (Which I downloaded from the corresponding thread for unbrick), in other words I flashed the same partitions with the correct v50s files instead other model ones. So now this is where I'm right now, the phone don't turns on at all but when I connect it to the PC it gets recognized as LGE Android Platform USB Serial Port (COM11) and the buttons combinations don't work at all, so still can't get into Download mode by any method or even turn off the device, but I still can disconnect the battery and short pin the Qualcomm 9008 mode to use QFIL.
Would someone please be so kind of telling me how could I recover the Download Mode to use the COM4 and COM5 ports to flash the phone via LGUP?. According to THIS other thread, I could get the correct XML "rawprograme files" for my device (which I crossflashed with the v50) from a KDZ using some tools and Python, but I have to be honest: I DON'T KNOW HOW, even with the step by step tutorial.
At this point I think this would be the right step, to flash all the original files for my model and get the Download Mode back to be able to flash the KDZ rom via LGUP and update via OTA to Android 12 again to avoid the bootloop problem.
try to reflash(QFIL method) modified abl should get the download mode back
darrelama said:
try to reflash(QFIL method) modified abl should get the download mode back
Click to expand...
Click to collapse
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
iMarzateD said:
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
Click to expand...
Click to collapse
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
darrelama said:
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
Click to expand...
Click to collapse
Hello again, already tried flashing the engineering abl but I still can't get into download mode. The phone keeps off the whole time and by plugging in the USB cable, no matter what button combination, the PC always recognizes it as the same LGE Android Patform USB Serial Port (COM11), the only other state of the device is the Qualcomm 9008 by pinning the motherboard. This specific COM11 state never was able to flash anything by PC, I don't know what actual mode is, but when I was able to set the devide in Download Mode the PC always showed 2 devices in the Device Manager, the COM5 and the COM4, that way I knew I was able to use the LGUP to flash. I'm thinking that I'm not setting the phone on the correct state to flash by any method, but since the buttons seems not to work, I don't know how could I do it.
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
ardian1899 said:
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
Click to expand...
Click to collapse
Thanks, I'll try that for sure to see if I can get into the Download Mode or something. I would appreciate so much if you could share your backup, since I think I could restore the whole firmware with it, but I don't have any experience on the "LUNs" tho. I'm any case, I don't have too much time every week to give it a try, so I hope tomorrow I could test the combo you say.