Related
I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.
christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.
O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.
Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?
waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.
serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
Owner trashed the blankflash file. Can anyone hook me up please?
Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]
Win 10 waiting for device message and nothing more.
and no 9008 port
moved
Tryng to root my device (XT1929-6), I bricked the phone. After installing the motorola device manager, i tried to blankflash the phone, but thats the log
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 204 (0xcc)
[ 0.000] ...cpu.sn = 3748563624 (0xdf6e8aa8)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] Failed identify board. Wrong package?
[ 0.016] ERROR: error loading package
[ 0.016] Check qboot_log.txt for more details
[ 0.016] Total time: 0.031s
FAILED: qb_flash_singleimage()->error loading package
Please help! I am not 100% certain where this thread must to be, if I am wrong tell me.
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Teto Balsámico said:
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Click to expand...
Click to collapse
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
Willy33 said:
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Click to expand...
Click to collapse
And how do i get those drivers? And where i can see how the computer recognises the mobile as Qualcomm 9008? just for the time being.
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Willy33 said:
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Click to expand...
Click to collapse
Thanks for your help!
I have the same problem. Could you fix the error?
Do I have to do something else for linux to detect my moto z3? Windows detects it without problem, but it always shows an error when reading the storage
Help..
E:\Descargas\qualkom dri>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.002] Opening device: \\.\COM4
[ 0.238] Detecting device
[ 0.248] ...cpu.id = 204 (0xcc)
[ 0.248] ...cpu.sn = 2761611797 (0xa49ada15)
[ 0.249] Opening singleimage
[ 0.594] Loading package
[ 0.603] ...filename = pkg.xml
[ 0.606] Loading programmer
[ 0.637] ...filename = programmer.elf
[ 0.638] Sending programmer
[ 0.832] Handling things over to programmer
[ 0.833] Identifying CPU version
[ 0.833] Waiting for firehose to get ready
[ 4.132] ...SDM636 1.0
[ 4.134] Determining target secure state
[ 4.137] ...secure = yes
[ 4.200] Configuring device...
[ 4.211] Flashing GPT...
[ 4.212] Flashing partition with gpt.bin
[ 4.221] Initializing storage
[ 4.300] ...blksz = 512
[ 4.521] Target NAK!
[ 4.521] ...ERROR: SDCC Error 29 (3)
[ 4.521] ...ERROR: Write Failed sector 0, size 48
[ 4.522] ...ERROR: Failed to write 1 slot 0, partition 0, start_sector 48 num_sectors 0, error 3
[ 4.522] ...Finished programming start_sector 48 and TotalSectorsToProgram 48
[ 4.522] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
[ 4.523] Check qboot_log.txt for more details
[ 4.524] Total time: 4.538s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.
Hey will this work on vivo y91i with mt6762
Is there a possibility of phone getting bricked
This is not working on Redmi Note 11t 5g
belkaliz said:
Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.
Click to expand...
Click to collapse
Will Try for unlocking FRP
belkaliz said:
Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.
Click to expand...
Click to collapse
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.
Anonymous V said:
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.
Click to expand...
Click to collapse
the message "orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds...." is normal for bootloader unlocked mtk devices
yeah i know that but in my case it cause a boot loop, after i unlock the bootloader and boot my phone because of the bootloop do you know how to fix it?
$cronos_ said:
the message "orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds...." is normal for bootloader unlocked mtk devices
Click to expand...
Click to collapse
yeah i know that but in my case it cause a boot loop, after i unlock the bootloader and boot my phone because of the bootloop do you know how to fix it?
Anonymous V said:
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.
Click to expand...
Click to collapse
You just have to go to recovery mode and wipe all data and then just reboot the phone will boot normally
St4rh4ck3r said:
You just have to go to recovery mode and wipe all data and then just reboot the phone will boot normally
Click to expand...
Click to collapse
thanks for the answer !but i manage to unlock it without losing any data
Seems not working for vivo y72 5g, any help?
The command python mtk xflash seccfg unlock seems not to be working for mtk client also
Incomtus said:
Seems not working for vivo y72 5g, any help?
The command python mtk xflash seccfg unlock seems not to be working for mtk client also
Click to expand...
Click to collapse
Did you try the other comand??
This command -----------> python mtk da seccfg unlock
Because we have the same problen and this one solves it try it!
Anonymous V said:
Did you try the other comand??
This command -----------> python mtk da seccfg unlock
Because we have the same problen and this one solves it try it!
Click to expand...
Click to collapse
I already tried it, mtk client ask to plug the phone, I do it, it detects it, BUT two possibilities are happening every time I tried : it says the phone has been unplugged or it remains stuck on "trying kamakiri2" and nothing happens....
I installed mtk client again i tried again and it does the same. Sometimea it gets stuck on "jumping on 0x0"
Incomtus said:
I already tried it, mtk client ask to plug the phone, I do it, it detects it, BUT two possibilities are happening every time I tried : it says the phone has been unplugged or it remains stuck on "trying kamakiri2" and nothing happens....
I installed mtk client again i tried again and it does the same. Sometimea it gets stuck on "jumping on 0x0"
Click to expand...
Click to collapse
In developers option did you turn on the oem unlock option?? The error (trying kamakiri2) hhappened to me what i did is i reinstalled everything from python to preloader driver
Anonymous V said:
In developers option did you turn on the oem unlock option?? The error (trying kamakiri2) hhappened to me what i did is i reinstalled everything from python to preloader driver
Click to expand...
Click to collapse
Yes oem unlock is activated. okay you think that comes from python preloader driver? Can you give a little more details? It will be very nice
Incomtus said:
Yes oem unlock is activated. okay you think that comes from python preloader driver? Can you give a little more details? It will be very nice
Click to expand...
Click to collapse
Im not quite sure why but i think kamakiri2 uses python to operate the whole proccess thats why if the python is not working the whole process will not work too, while in preloader(its a substitute of fastboot)helps the mtk client connect or communicate with ur phone thats why if the drivers is corrupted or something wrong happened mtk client wont work correctly, btw while you are unlocking your bootloader did you see something like (DA failed to send or offset error)?
Anonymous V said:
Im not quite sure why but i think kamakiri2 uses python to operate the whole proccess thats why if the python is not working the whole process will not work too, while in preloader(its a substitute of fastboot)helps the mtk client connect or communicate with ur phone thats why if the drivers is corrupted or something wrong happened mtk client wont work correctly, btw while you are unlocking your bootloader did you see something like (DA failed to send or offset error)?
Click to expand...
Click to collapse
I am not sure bro, I will try again in the evening
Incomtus said:
I am not sure bro, I will try again in the evening
Click to expand...
Click to collapse
Ok bro and to be sure pls put your mtk client log, in here as well sowe can all se the problem.
Anonymous V said:
Ok bro and to be sure pls put your mtk client log, in here as well sowe can all se the problem.
Click to expand...
Click to collapse
Here is the logs
the first is when i try without touching any hw bouton :
Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Mtk - We're not in bootrom, trying to crash da...
PLTools - Crashing da...
Preloader
Preloader - [LIB]: upload_data failed with error: DAA_SIG_VERIFY_FAILED (0x7024)
Preloader
Preloader - [LIB]: Error on uploading da data
Preloader - Jumping to 0x0
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
second with all butons (just detect and lost it)
..Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
PLTools - Crashing da...
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
Preloader
Preloader - [LIB]: Error on DA_Send cmd
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Last try when i pushed vol- and on/off button got stuck on kamakiri2:
Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
PLTools - Loading payload from mt6833_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
<
Hello i have problem with the mi9 of my friend
her phone seems to be block in boot process...we can see the Mi logo and the android power up with 3 points moving like if it is starting but nothing happens...
we let it starting for one complete night nothing has changed.
I can access to recovery mode pushing volume up + start button...i could do swap data but she doesn't want to loose some phone call records cause their is the voice of her last chat with her mum passed away some months ago...
for now what i know :
- her phone doesn't have the usb debugging options activated ;(
- when i connect the phone to my pc it doesn't recognized and appears on my pc
- i tried the miassitsant option in the recovery mode but mipcsuite doesn't see it too...
- not sure a mi account was created on her phone...she said she think we did one but the infos( id andpass was kept on a sms on her phone LOL)
so for now the only thing i see is that, in adb, when i typed .\adb devices i can see a number with "sideload" written beside it....does it help to find a way to modify the boot.img for an update or to transferts files from the phone to my pc?
question more : what is the path for phone calls recorded in a MI9? maybe i could use a push or pull option in adb?
i thought aboput contacting xiaomi for unlock the phone but as it seems to be blocked in boot mode i don't now if it would change something
i hope you understood well my poor english
please help ...
If it can help here is what i have when i used the miflash program
""""""""""""""""""""""""""""""""""""""
AGMService.exe AGSService.exe Adobe CEF Helper.exe Adobe Desktop Service.exe AdobeIPCBroker.exe AdobeUpdateService.exe ApplicationFrameHost.exe AudialsNotifier.exe BdVpnService.exe CCXProcess.exe CCleaner64.exe CCleanerBrowserCrashHandler.exe CCleanerBrowserCrashHandler64.exe Calculator.exe CefSharp.BrowserSubprocess.exe Creative Cloud.exe Dashboard.Service.exe Dashboard.exe DiscoverySrv.exe EpicGamesLauncher.exe EpicWebHelper.exe HPPrintScanDoctorService.exe LockApp.exe Memory Compression MiPhoneHelper.exe MoUsoCoreWorker.exe Music.UI.exe NVDisplay.Container.exe OfficeClickToRun.exe OneDrive.exe ProductAgentService.exe Registry RtkNGUI64.exe RuntimeBroker.exe ScanToPCActivationApp.exe Scheduler.exe ScpService.exe ScpTrayApp.exe SearchApp.exe SearchFilterHost.exe SearchIndexer.exe SearchProtocolHost.exe SecurityHealthService.exe SecurityHealthSystray.exe SettingSyncHost.exe SgrmBroker.exe ShellExperienceHost.exe StartMenuExperienceHost.exe SwUSB.exe System SystemSettings.exe TextInputHost.exe UserOOBEBroker.exe Video.UI.exe WUDFHost.exe WmiPrvSE.exe YourPhone.exe [System Process] adb.exe armsvc.exe audiodg.exe bdagent.exe bdntwrk.exe bdredline.exe bdservicehost.exe bdvpnapp.exe conhost.exe csrss.exe ctfmon.exe dasHost.exe dllhost.exe dwm.exe ensserver.exe explorer.exe fontdrvhost.exe lsass.exe lync.exe miflash_unlock.exe node.exe runSW.exe services.exe sihost.exe smartscreen.exe smss.exe spoolsv.exe svchost.exe taskhostw.exe unsecapp.exe updatesrv.exe wininit.exe winlogon.exe
DEBUG <10:37:18.136,T:16292> : miflash_unlock start
DEBUG <10:37:18.684,T:13176> : auto refresh device list
DEBUG <10:37:18.699,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
DEBUG <10:37:18.715,T:13176> : new usb\vid_18d1&pid_4e11\d9995836
INFO <10:37:18.715,T:13176> : fastboot devices
WARNING<10:37:24.212,T:16292> : account loading error:-21
DEBUG <10:37:24.946,T:16292> : [0]End: data:text/html,chromewebdata
DEBUG <10:37:25.261,T:13176> : auto refresh device list
DEBUG <10:37:25.268,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
INFO <10:37:25.272,T:13176> : fastboot devices
ERROR <10:37:31.387,T:13168> : http get error code[curl]:6
INFO <10:37:48.319,T:1116> : new app version:6.5.406.31 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.406.31/miflash_unlock-en-6.5.406.31.zip
DEBUG <10:37:50.540,T:13176> : auto refresh device list
DEBUG <10:37:50.556,T:13176> : use desp:Android Bootloader Interface instead of Android
DEBUG <10:37:50.571,T:13176> : remove usb\vid_18d1&pid_4e11\d9995836
DEBUG <10:37:50.571,T:13176> : new usb\vid_18d1&pid_d00d\d9995836
INFO <10:37:50.571,T:13176> : fastboot devices
DEBUG <10:37:50.656,T:15372> : -s d9995836 oem device-info
DEBUG <10:37:50.756,T:15372> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
DEBUG <10:37:50.756,T:15372> : getvar product -s d9995836
DEBUG <10:37:50.841,T:15372> : product: cepheus
finished. total time: 0.000s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""
i tried to download files from devices but not sure of the path where the voice records are saved :
adb pull [-l] /internal share storage/MIUI/sound_recorder/call_rec/
adb pull [-l] /MIUI/sound_recorder/call_rec/
is the path correct?
I have a Xiaomi Redmi 9 (cattail) device
I am trying to use mtkclient to unbrick my device but i am getting this error:
Code:
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Here is the entire output:
Code:
MTK Flash/Exploit Client V1.6.0 (c) B.Kerler 2018-2022
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
Port - Device detected :)
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe7
Preloader - SBC enabled: True
Preloader - SLA enabled: True
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: BEA9E2CD55FC2EB3794A2835E280608C
Preloader - SOC_ID: 27976D1C1A81DBCDB0FC5383E67CB00ADF62A75E37C7066C28E877FFDB8AC544
PLTools - Loading payload from mt6765_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /home/kyeboard/MIUI_FIX/mtkclient/mtkclient/payloads/mt6765_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
xflashext - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
xflashext
xflashext - [LIB]: Error on patching da1 version check...
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "get_vfy_policy" in preloader
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - DRAM config needed for : 150100434a544434
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Hey @LiaFourté, can you please help me?
here with the same problem
If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin
bretjoseph said:
If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin
Click to expand...
Click to collapse
didnt work
maybe write partition to boot_b or boot if you dont have a/b device
kuubichan said:
I have a Xiaomi Redmi 9 (cattail) device
I am trying to use mtkclient to unbrick my device but i am getting this error:
Code:
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Here is the entire output:
Code:
MTK Flash/Exploit Client V1.6.0 (c) B.Kerler 2018-2022
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
Port - Device detected :)
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe7
Preloader - SBC enabled: True
Preloader - SLA enabled: True
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: BEA9E2CD55FC2EB3794A2835E280608C
Preloader - SOC_ID: 27976D1C1A81DBCDB0FC5383E67CB00ADF62A75E37C7066C28E877FFDB8AC544
PLTools - Loading payload from mt6765_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /home/kyeboard/MIUI_FIX/mtkclient/mtkclient/payloads/mt6765_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
xflashext - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
xflashext
xflashext - [LIB]: Error on patching da1 version check...
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "get_vfy_policy" in preloader
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - DRAM config needed for : 150100434a544434
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Click to expand...
Click to collapse
I can flash your device if you want to.
Let me know.
bretjoseph said:
If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin
Click to expand...
Click to collapse
From where do you get this, the one for R9a is preloader_k62v1_64_bsp
mvikrant97 said:
I can flash your device if you want to.
Let me know.
Click to expand...
Click to collapse
How? if the issue is with drivers or tool.
SubwayChamp said:
How? if the issue is with drivers or tool.
Click to expand...
Click to collapse
I'll use a paid software to flash the device.
Don't worry you don't need to pay for it.
mvikrant97 said:
I'll use a paid software to flash the device.
Don't worry you don't need to pay for it.
Click to expand...
Click to collapse
Good, and how we can do?, I have all the firmware for Redmi 9a, but I can´t get it to work as of now.
SubwayChamp said:
From where do you get this, the one for R9a is preloader_k62v1_64_bsp
Click to expand...
Click to collapse
try doing a boot.img dump it should also download the preloader when it fetches the boot.img in the folder where you dump
bretjoseph said:
try doing a boot.img dump it should also download the preloader when it fetches the boot.img in the folder where you dump
Click to expand...
Click to collapse
Thanks for replying, I´m not getting to work the mtk-client, it´s keeping throwing errors like DAXFlash - [LIB]: Error on sending DA, so I thought that the other way around could solve it, I could flash nor read any partition. It worked perfectly for my previous devices though.
SubwayChamp said:
Thanks for replying, I´m not getting to work the mtk-client, it´s keeping throwing errors like DAXFlash - [LIB]: Error on sending DA, so I thought that the other way around could solve it, flash nor read any partition. It worked perfectly for my previous devices though.
Click to expand...
Click to collapse
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.
Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..
Ank Sak said:
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.
Click to expand...
Click to collapse
Ank Sak said:
Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..
Click to expand...
Click to collapse
which phone is it?
mvikrant97 said:
which phone is it?
Click to expand...
Click to collapse
Lenevo K8 note , mtk6797 mediatek cpu
Ank Sak said:
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.
Click to expand...
Click to collapse
Thanks, in SPFT it throws "EXT_RAM_EXCEPTION" error.
Ank Sak said:
Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..
Click to expand...
Click to collapse
Maybe, It´s possible that the preloader is the culprit, probably the preloader is corrupt.
But the funniest is that some days ago, with those errors, I taken to a service center, with Unlock tool, without the need to do nothing more than pressing both volume buttons (device off) it started to flash, and solved it, I re-bricked it by flashing the firmware (the latest), it´s suppose to not cause damage but it bricked. So the eMMC is not damaged.
SubwayChamp said:
Thanks, in SPFT it throws "EXT_RAM_EXCEPTION" error.
Maybe, It´s possible that the preloader is the culprit, probably the preloader is corrupt.
But the funniest is that some days ago, with those errors, I taken to a service center, with Unlock tool, without the need to do nothing more than pressing both volume buttons (device off) it started to flash, and solved it, I re-bricked it by flashing the firmware (the latest), it´s suppose to not cause damage but it bricked. So the eMMC is not damaged.
Click to expand...
Click to collapse
service center don't use unlock tool but third party repair shop does
mvikrant97 said:
service center don't use unlock tool but third party repair shop does
Click to expand...
Click to collapse
A Service Center can be authorized or non authorized. Specialization and/or segmentation in the matter/product is what the Marketing inclines this or that name to give as proper, and client consider correct both. Where I live, there are a lot of Official Repair Shops along the country, they´re called too, Service Center/Repair Center, same way, there are a lot of Service Center of a specific product, this is where plays a role the segmentation and specialization. Just to add, that some large enterprises have both department in the hierarchy.