Hi everyone!
Just wanted to share some steps in case you brick your Realme.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES
Some prerequisites you will need:
mtkclient + python
spft (sp flash tool)
ofp extractor
Your stock rom in OFP format.
Step 1. Download all of the things mentioned above.
Step 1a. Make sure your device is turned off. DO NOT PLUG IT IN.
Step 2. Install mtkclient using the guide on GitHub.
Step 3. Run
Bash:
$ py mtk payload
in your terminal.
Step 3a. When it says ***waiting for device*** hold both volume buttons and plug in your device.
This will enter BROM mode.
Step 4. Extract and open ofp extractor and extract your ofp.
Step 5. Open SPFT and click DOWNLOAD ONLY (do not I MEAN DO NOT PRESS FORMAT ALL.)
Step 6. In scatter, look for your scatter file. It should be (MTxxxxScatter.txt etc) Then select it.
Step 7. Select your auth file if you have one.
Step 8. Press Download and if the progress bar starts going the flash is going. DO NOT UNPLUG.
Step 9. Reboot after it says 'Download Ok'
Step 10. Enjoy your unbricked device!
NOTE In most cases the rom will be for android 10. Update if required through OZIP.
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
czaroslaw said:
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MYKI Tool
Click to expand...
Click to collapse
What more.info about the error code do you have? Also are you on windows because spft buggy on linux
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
czaroslaw said:
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
Click to expand...
Click to collapse
Then you haven't bypassed brom, try mtkclient again and don't unplug your device
Mtk client gives error: Preloader - [LIB]: ←[31mStatus: Handshake failed
Install mtk drivers and Libusb, also pyserial
All above mentioned was installed. I tried different pack from droidwin and I get this:
Code:
Port - Device detected :)
Preloader - CPU: MT6853(Dimensity 720 5G)
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: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x996
Preloader - Target config: 0xe5
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: 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: 3EFFEA531AB22A57AB0240D8421E92B4
Preloader - SOC_ID: DAA82CB9D5E03916132A0BE2A479C0CC0FFD2B10
1E00173F9EA9FCB44C88FC8E
PLTools - Loading payload from mt6853_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: D:\Apk\MTK Bypass Tools\mtkclient-main\mtkc
lient\payloads\mt6853_payload.bin
Be sure to use in SPFT, in connection check USB full speed, and in general settings, uncheck the options Check LIB DA Match and Storage Life Cycle Check.
If this doesn't work, try to flash only preloader firstly, and then flash the rest, upload some screenshot if the error persists.
That means it worked
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
do
Code:
fastboot flash --disable-verity --disable-verification vbmeta {your vbmeta.img}
czaroslaw said:
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
Click to expand...
Click to collapse
If it says DM-verity error, reflash with spft and on mtkclient, relock BL by using
Code:
Py mtk da seccfg lock
I cannot enter fastboot mode so I cannot use fastboot flash.
Second advice: I do not want to lock bootloader.
If you are able to boot to stock, do ADB reboot fastboot
Does not work. It gives the same as VolUP+PWR. Orange state message and reboot.
I cannot enter fastboot in any way.
Should I flash something in brom mode? Recovery partition? Something else to get rid of dm_varity?
Reflash firmware then try, idk this hasn't happened to me
Also send the link of the firmware U got
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
czaroslaw said:
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
Click to expand...
Click to collapse
Relock bootloader and try using this to reunlock bl
Related
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Strephon Alkhalikoi said:
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Click to expand...
Click to collapse
Thanks mate! I will do my best.
baba_baba said:
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
Click to expand...
Click to collapse
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
nsrpani said:
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
Click to expand...
Click to collapse
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
baba_baba said:
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
Click to expand...
Click to collapse
Thanks for your quick response. While clicking on first link, it is going to Lenovo site - http://support.lenovo.com/en_ZA/ . Suggest me on this.
Update
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
baba_baba said:
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
Click to expand...
Click to collapse
Driver
jakmal said:
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
Click to expand...
Click to collapse
Please try the following:
http://www.driverscape.com/download/qualcomm-cdma-technologies-msm
i got stuck here after following every single steps........
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Jan 27 10:09:21 2014
Check image DBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A1355B00
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
ERROR[DA1]: download AMSS Fail!
whalesplaho said:
i got stuck here after following every single steps........
Code:
................
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
Click to expand...
Click to collapse
same happen to me
is there any body ???
HELPPP !!!
After installing right ADB driver now another error
......................
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A140614
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
sending 'AMSS' (15708 KB)... FAILED (status read failed (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...
sending 'boot' (3180 KB)... FAILED (command write failed (Too many links))
ERROR[DA1]: download boot Fail!
Best of luck!! There are tons of info for Streak. I switch between moto x and streak.
Sent from my XT1053 using xda app-developers app
Did someone have same problem as me ?
My Dell was keep restarting on Dell logo and there was no access to recovery and fastboot.
I tried with QDL and everything went good , but still no access to fastboot and recovery.
Only change is that Dell is no more restarting , only stays on Dell logo.
Please help
Streak 5 - Cannot copy system via QDL
Dear all,
I have a DELL streak 5 and having already stoned at DELL logo.
I tried QDL yet it ends like below:
HW:
Board ID:
Comment:
--
LOG
--
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sat Aug 08 07:49:43 2015
Check image DBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A130500
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
sending 'system' (212695 KB)... FAILED (unknown status code)
ERROR[DA1]: download system Fail!
Download Fail! - 2015/08/08 07:52:14
Elapsed Time: 151.30 sec
Please tell me what to do.
thank you.
@jayanthap: http://forum.xda-developers.com/showpost.php?p=62244448&postcount=3
Hi guys,
i try rooting my z5c with this tutorial.
I'm stuck on 5.7 (Flash your patched Kernel to your phone with this command: fastboot flash boot kernel-patched.elf)
The Process always stops at " <waiting for device> "
fastboot devices has no output
flashtool output:
05/044/2016 20:44:55 - INFO - Starting phone detection
05/044/2016 20:44:59 - INFO - Device connected in fastboot mode
05/045/2016 20:45:08 - INFO - List of connected devices (Device Id) :
05/045/2016 20:45:08 - INFO - - USB\VID_0FCE&PID_0DDE\CB5A2B7F8N Driver installed : true
05/045/2016 20:45:08 - INFO - List of ADB devices :
05/045/2016 20:45:08 - INFO - - none
05/045/2016 20:45:08 - INFO - List of fastboot devices :
05/045/2016 20:45:08 - INFO - - CB5A2B7F8N
OS: Win10
Flashtool drivers installed: Fastboot, Flashmode, Xperia Z5c
I installed them skipping the untrusted driver signature warning, ohterwise it would have failed.
The devicemanagement says: Android Device > Sony Fastboot Interface
Would be nice if someone could help
Edit: It worked now but I have absolutely now idea why. I was away for a few hours and simply tried again. OS not rebooted and phone off during this time. Just turned it into fastboot mode again but i did this several times earlier without any effect.
Nice to see you solved, in my experience it's usually driver problems looking in Device Management.
i Have Lenovo S60-a when i upgrade it to 5.0 then it cause some problem
it load nothing i tried all combinition of button then i tried it through test point and it work it load Qualcomm HS-USB QDLoader 9008 and connected to my pc now when i try to flash it through QFil it give me error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
And some time it give
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
Hello my personal x400 positixo this rom with damaged did not find support firmware conpativel any possibility of find compatible firmware
BB_CPU_PID : 6582
BB_CPU_NME : [MediaTek] MT6582_S00
BB_CPU_EXT : 0xCA01 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x0005
BLVersion : 0x00FE
PreLoader : NOT Active [ Erased ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x87
NAND Flash : 00B000B000B000B000B0000000000000
eMMC Flash : NOT INSTALLED
Initialize Memory ...
Hello I got Cat s52 phone and it is restarting all the time and getting this error "your device has failed verification and may not work properly"
I will appreciate any help! Thanks in advance!
xDaemon said:
Hello I got Cat s52 phone and it is restarting all the time and getting this error "your device has failed verification and may not work properly"
I will appreciate any help! Thanks in advance!
Click to expand...
Click to collapse
If you have a warranty and you have not made any modifications to the firmware, please contact support.
If there is no warranty or you have modified the firmware, then follow the steps described below.
1. Install mtkclient (or use live dvd).
2. Make a backup of all partitions.
3. Find the firmware dump.The dump can be found here or here. Also I can make dump from my device if needed.
(Only firmware from first link tested by me).
4. Flash the partitions you need (it may be enough to flash only the boot partition).
More detailed instructions how dump and flash are on the mtkclient page.
Lesosek said:
If you have a warranty and you have not made any modifications to the firmware, please contact support.
If there is no warranty or you have modified the firmware, then follow the steps described below.
1. Install mtkclient (or use live dvd).
2. Make a backup of all partitions.
3. Find the firmware dump.The dump can be found here or here. Also I can make dump from my device if needed.
(Only firmware from first link tested by me).
4. Flash the partitions you need (it may be enough to flash only the boot partition).
More detailed instructions how dump and flash are on the mtkclient page.
Click to expand...
Click to collapse
Spoiler
C:\Users\Admin\mtkclient>PYTHON mtk_gui
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
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.
...........
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.
...........
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.
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: 0xe5
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: 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: 921E4FBF578455DEEC50F9EBA448BD88
Preloader - SOC_ID: 0240DFE71E5D62B444C450A856A7E8C3A5B6C2A94C1F9C7EFDA8A7838803CD98
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
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: 0xe5
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: 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: 921E4FBF578455DEEC50F9EBA448BD88
Preloader - SOC_ID: 0240DFE71E5D62B444C450A856A7E8C3A5B6C2A94C1F9C7EFDA8A7838803CD98
Port - Device detected
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2152.bin
xflashext - Patching da1 ...
xflashext
xflashext - [LIB]: ←[33mError on patching da1 version check...←[0m
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DeviceClass - USBError(5, 'Input/Output Error')
None
Traceback (most recent call last):
File "C:\Users\Admin\mtkclient\mtkclient\gui\toolkit.py", line 113, in run
self.function(self, self.parameters)
File "C:\Users\Admin\mtkclient\mtk_gui", line 87, in getDevInfo
mtkClass = da_handler.configure_da(mtkClass, preloader=None)
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 112, in configure_da
if not mtk.daloader.upload_da(preloader=preloader):
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daloader.py", line 209, in upload_da
return self.da.upload_da()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 1143, in upload_da
connagent = self.get_connection_agent()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 383, in get_connection_agent
res = self.send_devctrl(self.Cmd.GET_CONNECTION_AGENT)
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 267, in send_devctrl
status[0] = self.status()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 215, in status
magic, datatype, length = unpack("<III", hdr)
struct.error: unpack requires a buffer of 12 bytes
Thats is the longest way which i can go . . . . .
xDaemon said:
Thats is the longest way which i can go . . . . .
Click to expand...
Click to collapse
It's most likely an installation or incompatibility issue. The python version must be 3.9. requirements,drivers,usbdk must be installed. If the problem cannot be solved, you can use LiveDVD where all the necessary software is preinstalled.
Lesosek said:
It's most likely an installation or incompatibility issue. The python version must be 3.9. requirements,drivers,usbdk must be installed. If the problem cannot be solved, you can use LiveDVD where all the necessary software is preinstalled.
Click to expand...
Click to collapse
I tried with LiveDVD but it is not recognized, can you make some guide with commands for LiveDVD if you have time, Please! I am real noob with Linux.
And the phone is restarting every 5 seconds, I have to press all 3 buttons and hold them but after some time I hear sound from connecting and disconnecting USB . . . .
Sorry for wasting your time!
xDaemon said:
I tried with LiveDVD but it is not recognized, can you make some guide with commands for LiveDVD if you have time, Please! I am real noob with Linux.
And the phone is restarting every 5 seconds, I have to press all 3 buttons and hold them but after some time I hear sound from connecting and disconnecting USB . . . .
Sorry for wasting your time!
Click to expand...
Click to collapse
Latest LiveDVD has user interface for MTKClient.
Lesosek said:
Latest LiveDVD has user interface for MTKClient.
Click to expand...
Click to collapse
I know, but when i click on it does nothing . . . . .
xDaemon said:
I know, but when i click on it does nothing . . . . .
Click to expand...
Click to collapse
"python mtk" command should print list of commands with description
Code:
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
-----------------------------------
Available commands are:
printgpt: Print GPT Table information
gpt: Save gpt table to given directory
r: Read flash to filename
rl: Read all partitions from flash to a directory
rf: Read whole flash to file
rs: Read sectors starting at start_sector to filename
ro: Read flash starting at offset to filename
w: Write partition from filename
wf: Write flash from filename
wl: Write partitions from directory path to flash
wo: Write flash starting at offset from filename
e: Erase partition
es: Erase partition with sector count
footer: Read crypto footer from flash
reset: Send mtk reset command
dumpbrom: Try to dump the bootrom
dumppreloader: Try to dump the preloader
payload: Run a specific kamakiri / da payload, if no filename is given, generic patcher is used
crash: Try to crash the preloader
brute: Bruteforce the kamakiri var1
gettargetconfig: Get target config (sbc, daa, etc.)
peek: Read memory in patched preloader mode
stage: Run stage2 payload via boot rom mode (kamakiri)
plstage: Run stage2 payload via preloader mode (send_da)
xflash: Run da xflash special commands
You can solve your problem using these commands:
"python mtk rl <dump directory name>" - dump all partitions, you shold have free 64GB, process may take few hours
"python mtk printgpt" - partition list
"python mtk r <partition name> <path to file>" - dump partition to file
"python mtk w <partition name> <path to file>" - write partition from file
"python mtk e <partition name>" - erase partition
Also you have to be careful with write or erase commands so a backup of all partitions should be done!