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 ...
Related
Hey guys, i was upgrading from old 2.2 baseband to 2.3 baseband using lgmdp.exe method . described here http://forum.xda-developers.com/showthread.php?t=1149530
however when i did that burning eeprom froze in d middle . it wont progress any further as shown in the image. consequently i had to remove my phone which was in emergency mode at that time. i plugged it again but lgmdp.exe just wont read it.
I panicked removed the battery and then the phone wont start . (earlier i was using cm7 rc1 with old baseband using nightlyfour rom's patch) .howver i was able to get it back into recovery mode by pressing back and volume up keys together while starting the phone. i flashed stock 2.3 using kdz ,IT WORKED my phone gets netwokr and calls as normal but i think my baseband is somewat corrupted as is shown in kdz log.
[13:41:22:694] : =============================================
[13:41:22:694] : Log is started on 24.03.2012, at 13:41:22:694,
executable: E:\Android\ROMS\Original Tools\KDZ_FW_UPD_EN\KDZ_FW_UPD_EN\KDZ_FW_UPD.exe (ProcID: 0x000012ec),
compile time : Sep 13 2010 11:34:51
[13:41:22:694] : Version :
[13:41:22:696] : Get Usb Port
[13:41:22:702] : rsi.strFriendlyName=LGE Bluetooth TransPort (COM4)
[13:41:22:702] : Remove LGE Bluetooth TransPort (COM4)
[13:41:22:702] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM13)
[13:41:22:702] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[13:41:22:702] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM13
[13:41:22:702] : Port = COM13
[13:41:22:705] : UNKNOWN : Req(12) -> Rsp(13)
[13:41:22:706] : UNKNOWN : Req(12) -> Rsp(13)
[13:41:22:707] : UNKNOWN : Req(12) -> Rsp(13)
[13:41:22:707] : >> DIAG_STATUS_F FAILED
[13:41:22:712] : >>Get Model Name [DIAG_VERNO_F]
[13:41:22:713] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:714] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:715] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:716] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:717] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:718] : BAD CONN MODE : Req(0) -> Rsp(3)
[13:41:22:718] : FAIL (No Phone)
[13:41:22:718] : GetModelName() Operation Failed Check Diag CMD
[13:41:22:718] : EMERGENCY Booting Mode
[13:41:22:718] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[13:41:22:719] : BS/P500/7D\ROMS\Original Tools\Tail.exe
[13:41:22:719] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P500
[13:41:22:730] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[13:41:22:730] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[13:41:22:731] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[13:41:22:731] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[13:41:22:742] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[13:41:22:742] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[13:41:22:742] : NV Write Fail : NV ITEM 9028(9028)
[13:41:22:842] : >> GET DLOAD COMM MODE
[13:41:22:843] : [GetCommMode] Communication mode : 2
[13:41:22:843] : Pre Nand Download
[13:41:22:843] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[13:41:22:843] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[13:41:22:844] : [COM13] >>NandFlashInitWithFile(PARTITION TBL)
[13:41:22:844] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[13:41:22:936] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[13:41:22:936] : [COM14] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[13:41:22:936] : [COM13] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[13:41:22:940] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[13:41:22:952] : [COM14] >>Dl_AsyncWrite()
[13:41:22:952] : >> AMSS FLASHING ...
[13:41:22:956] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[13:41:22:956] : Sending Pkt Seq : 0
[13:41:22:957] : Sending Pkt Seq : 1
[13:41:22:958] : Sending Pkt Seq : 2
[13:41:22:958] : Sending Pkt Seq : 3
[13:41:22:958] : Sending Pkt Seq : 4
note that i had taken nv2 backup before upgrading baseband which i cant restore now coz lgmdp.exe doesnt read my phone it detects but is unable to read any info no imei no bluetooth address
Now i am using cm7 rc wid new baseband but sometimes baseband in settings shows wild characters ! any inputs ????
Your basebamd is ok!This bug is from the rom... I have this too
Sent from my LG-P500 using xda premium
can u explain why lgmdp wont read it anymore. i think its coz of some temporary files mayb . also does successful flashing from kdz means baseband is ok ? baseband resides on a separate partition right ?
sarfaraz1989 said:
can u explain why lgmdp wont read it anymore. i think its coz of some temporary files mayb
Click to expand...
Click to collapse
Don't know, doesn't matter
sarfaraz1989 said:
also does successful flashing from kdz means baseband is ok ?
Click to expand...
Click to collapse
Yes
sarfaraz1989 said:
baseband resides on a separate partition right ?
Click to expand...
Click to collapse
Yes, for example:if you flash mik's cm7 or some custom rom made for old bb you won't get signal...
Need Scatter File
Please Help Me !
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
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 : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with SPRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1612.01.01
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x87
NAND Flash : NOT INSTALLED
eMMC Flash : 1501004B3758564D42018874D002211B
Initialize Memory ...
DRAM already initialized by Preloader
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BMVX7
[eMMC] : FLASH_CID : 1501004B3758564D42018874D002211B
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000001D2000000
[eMMC] : FLASH_UCP : 7456 MiB [eMMC 8 GiB]
DEV RID : 13C3F3528A921A594F14348381D36169
INT RAM : 0x00020000
EXT RAM : 0x40000000
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
[AP] : Initial info read Ok!
Brand : Vodafone
ProdName : Vodafone_Smart_Tab_4
ProdModel : Vodafone Smart Tab 4
Device : Vodafone_Smart_Tab_4
AndroidVer: 4.2.2
MTKxCPU : MT6582
MTKxPRJ : ALPS.JB5.TABLET.MP.V1
Done!
Elapsed: 00:00:12
Reconnect Power/Cable!
Operation : Remove Viruses [SmartAV] [ v1.47 ]
SmartAV Conf : 100/80/2000
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
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 : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with SPRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1612.01.01
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x87
NAND Flash : NOT INSTALLED
eMMC Flash : 1501004B3758564D42018874D002211B
Initialize Memory ...
DRAM already initialized by Preloader
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BMVX7
[eMMC] : FLASH_CID : 1501004B3758564D42018874D002211B
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000001D2000000
[eMMC] : FLASH_UCP : 7456 MiB [eMMC 8 GiB]
DEV RID : 13C3F3528A921A594F14348381D36169
INT RAM : 0x00020000
EXT RAM : 0x40000000
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
Nokia 5 TA1053 Error Flashing With Cm2
Wait for phone...
Device Found!
Initialize ...
Handshake passed!
ID_BLOCK_I : SnapDragon 430 [MSM8937]
ID_BLOCK_S : 4838D9EF
ID_BLOCK_L : CDC92C120E8AC04168853E56D89F42B0
ID_BLOCK_L : 4878EF919778A4F339506A9D283CD512
Pickup loader from firmware package
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8937 , FLASH : eMMC , mVER : 1
MemInfo : 0x0003 / 0x0200 / 0x00000003A3E00000 [ eMMC 16 GiB ]
ExtInfo : 0x00004000/00004000/00001000/00001000/00000200
Storage : MFR : 0x15 , VENDOR : SAMSUNG , NAME : QE13MB
Boot Ok!
Flash Chain : 65
Flashing now
Flashing : gpt_main0.bin
Flashing : NON-HLOS.bin
Flashing : sbl1.mbn
Flashing : sbl1.mbn
Flashing : rpm.mbn
Flashing : rpm.mbn
Flashing : tz.mbn
Flashing : tz.mbn
Flashing : devcfg.mbn
Flashing : devcfg.mbn
Flashing : adspso.bin
Flashing : sec.dat
Flashing : splash.img
Flashing : emmc_appsboot.mbn
Flashing : emmc_appsboot.mbn
Flashing : boot.img
Flashing : recovery.img
Flashing : hwconf.cfg
Flashing : sysinfo.cfg
Flashing : splashm.img
Flashing : hidden.img
Flashing : cda.img
Flashing : persist.img
Flashing : misc.img
Flashing : mdtp.img
Flashing : cmnlib.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib64.mbn
Flashing : cmnlib64.mbn
Flashing : keymaster.mbn
Flashing : keymaster.mbn
Flashing : system.img
Flashing : cache.img
Flashing : userdata.img
Invaild pointer opration
please help me
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
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!