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
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!
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
Hi all as the title suggests is there anyone who has a fairly detailed Unbricking guide or a way to reflash the stock meizu software via fastboot, QFIL or anything that has worked.
The current problem I face is I have the m6 note with Chinese firmware and wanted to flash global firmware via flash fire as the TWRP APK didn't work for me . I can't enter recovery and fastboot gives me a failed message (remote: partition flashing is not allowed ).
Thank you in advance
its for m3 but you may try http forum flymeos com/forum.php?mod=viewthread&tid=35810&highlight=unbrick
also this one for our phone http://forum flymeos.com/thread-38489-1-1.html
This one is from original flyme os forum FAQ
Q: Recover soft-Bricked device (for those can't access the system)
A: Access the Recovery mode:
1.Turn Off the Phone (ensure that you have more than 20% battery)
2.Press and Hold Volume UP + Power
3.release as soon as you see the Meizu logo
Download firmware from http://www.flymeos.com/firmware.html, Copy the update.zip (naming is important) on your phone and select System Upgrade + Clear Data. As soon as it's connected a "Recovery Drive" will pop up. Now, connect your phone (still in Recovery Mode) to your Windows PC. As soon as you are there, you are just fine.
hi thanks @consumimur , but the first method is for mediatek devices isn't it? The second method doesn't work for me at all because i can't enter my recovery , i need some sort of flashing too QFIL doesn't work for well at the the one i tried (2.0.0.5) as it ask for "Rawprogram.xml" and "patch* " which is not in the update.zip
Yusuf.T said:
hi thanks @consumimur , but the first method is for mediatek devices isn't it? The second method doesn't work for me at all because i can't enter my recovery , i need some sort of flashing too QFIL doesn't work for well at the the one i tried (2.0.0.5) as it ask for "Rawprogram.xml" and "patch* " which is not in the update.zip
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=843179&view=findpost&p=69341915
New https://www.movilesdualsim.com...oros/meizu-m6-note-sd625.1222/
Enviado desde mi M6 Note mediante Tapatalk
i think thats what you are looking for
https://firmwarefile.com/meizu-m6-note-m1721
Folks, today I've had the fortune to brick (corrupting the devinfo partition, screwing up recovery and OS boot as well) and unbrick (stock recovery and OS restored and working perfectly) my Meizu M6 Note without opening it up. If anyone is still interested, instructions are here:
https://forum.xda-developers.com/showpost.php?p=77964079
Hi, I have a problem with my m6 note. I have WIFI MAC address between 2: 00: 00: 00: 00: 00 and I can not turn on wifi. I found a solution to upload persist.img and this should help. However, I can not find the persist.img file anywhere. Can you help?
consumimur said:
This one is from original flyme os forum FAQ
Q: Recover soft-Bricked device (for those can't access the system)
A: Access the Recovery mode:
1.Turn Off the Phone (ensure that you have more than 20% battery)
2.Press and Hold Volume UP + Power
3.release as soon as you see the Meizu logo
Download firmware from http://www.flymeos.com/firmware.html, Copy the update.zip (naming is important) on your phone and select System Upgrade + Clear Data. As soon as it's connected a "Recovery Drive" will pop up. Now, connect your phone (still in Recovery Mode) to your Windows PC. As soon as you are there, you are just fine.
Click to expand...
Click to collapse
thank you so much for this @consumimur. It saved me from going down a rabbit hole, after getting a bootloop with meizu x8 m852h, having followed these instructions:
Meizu X8 - Обсуждение - 4PDA
Meizu X8 - Обсуждение, Смартфон, 6.2"
4pda.to
OP:
ttps://4pda.to/forum/index.php?showtopic=965227
author: 555frost555
Download (litter, files lost) archive and unpack to the root of the C drive
Charge your phone at least 50%
Disable signature verification using the following instructions:
For WINDOWS 7-8: Run Command Prompt as administrator, execute two commands in turn and reboot
Code:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
For WINDOWS 10: press start, hold shift, press shutdown computer. The computer will boot into a recovery screen. Select custom boot options and disable driver signature verification.
PS personally, I recommend installing on win7 or 8.1 - less haemorrhoids
Install QFIL
Install Qualcomm 9008 driver
Install standard drivers from the phone (connect to the computer in the CD-drive mode and install from there)
Run QFIL and select "flat build"
Select programmer: "prog_firehose_ddr.elf"
Select XML: "rawprogram0.xml"
Select XML: "patch0.xml"
Turn off the phone
Clamp VolUp + VolDn + Power
The Meizu icon appears, followed by a black screen. The keys can be released.
Connect your phone to your computer. It should be detected as Qualcomm 9008.
Press DOWNLOAD
QFIL is very moody about the system and drivers. If you did everything correctly, but you get an error while flashing, then you need to try it on another computer. Preferably on where windows was recently installed ...
When FINISH is written in QFIL, you can turn off the phone and restart it by holding down the power key until it vibrates.
For WINDOWS 7-8: Run Command Prompt as Administrator, execute two commands in turn and reboot
Code:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
I did this with the QFIL archive linked in https://4pda.to/forum/index.php?act=findpost&pid=88712568&anchor=Spoil-88712568-6
and received a bootloop on meizu x8 m852h. Then I did what @consumimur wrote
I did this on a windows 10 machine
I did this on a w10 machine
This is unbrick firmware. Enjoy free. Download Unbrick Meizu M6 firmware.
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?
My Redmi 6A was in "System has been destroyed" SOFT BLOCK I could enter fastboot mode and recovery.
I tried to flash the rom by miflash but it gave me error for having the bootbloader locked so I tried with SP Flash Tool and select the "firmware upgrade" option and ended up in a "HARD BRICK BLACK SCREEN" does not enter fastboot mode, or brom mode and when I connect it to the pc recognizes it but disconnects every second.
I force the brom mode with a tool called "MTK META Utility" and I could flash the rom stable global cactus again select "download only" it finished correctly gave the "OK" message, but it does not turn on the phone and it remains the same "HARD BRICK BLACK SCREEN" ... Is there any way to fix it or just already killed my phone?
well, i just fixed my redmi 6a with this method so give me more information and then maybe i can help you.
are you using Windows on your pc?
Suskana said:
I force the brom mode with a tool called "MTK META Utility"
Click to expand...
Click to collapse
i didn't used this one...
but anyhow, according to the result "gave the "OK" message" you managed to bypass the auth?