Hello,
My phone is dead ! after I flashed a wrong ROM. The problem is that now the following error appears when I try to flash another ROM:
BROM ERROR : S_FT-ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.
i tried a lot of roms but keep saying Enable DRAM FAILED.
if anyone can help with the proper scatter files.
Thanks for your concern.
ERROR - SPFLASHTOOLS - "status brom cmd send da fail" wthat to do?
delet recovery, framwere! it true fastboot
http://forum.xda-developers.com/android/development/guide-meizu-m3-m3s-unbrick-t3515231
For download agent select DA_PL.BIN
hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Had this problem for weeks.
Only thing that actually worked is to flash the developer rom, try, it will complete.
Then flash back to the stable rom, pain in the arse I know, but save your time and try it.
en.miui.com/download-299.html
Make sure that you are on the developer ROM .
And it took me 2-3 days more to unlock my phone after getting confirmation from Xiaomi. Wait for 2-3 days so that their server gets updated.
edhahaha said:
hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Click to expand...
Click to collapse
What ROM do you have?
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
edhahaha said:
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
Click to expand...
Click to collapse
Did you tried with developer global ?
If don't work, try with developer global MIUI7 . Worked for me.
You must be signed into the MIUI account on your device that you are using on the unlock application also.
Here are the steps i followed
1. I was on global stable ROM, flashed global developer ROM
2. login with Mi Account Id, not email or mobile number on phone as well as the unlock tool
3. Now I'm able to unlock the bootloader
4. Install Stable rom again if needed, I flashed it and my bootloader remained unlocked
The thing is,
Maybe you can try to check the lock status as well,
Mine showing 50% error several times,
But when i do "fastboot oem device-info"
It said that the BL was unlocked already,
I dont know how, but it seems the unlock was actually went through even when it show error
You have to be on a developer ROM, chinese or global doesn't matter.
If you're currently on chinese stable, you can switch to chinese developer. But if you're on Global stable, you can only switch to Global developer.
Hello. I had the same problem and I assume you have checked every single guide out there as well. I got around it when I changed my computer and unlock using the new computer. Maybe you can try doing the same thing and use your friend's laptop to unlock BL. To make sure there's no computer issue make sure to install ADB and Fastboot driver and check if your computer can detect your device in Fastboot mode (there has to be a guide out there, try google). Cheers
Hi, I run into the same issue on win 10 and also installed the android sdk to get the drivers.
Device Mi5 Pro
Latest chinese dev 6.10.20 (MIUI8)
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
Thus the mi unlocker tool runs into the same issues:
Code:
DEBUG <11:15:16.127,T:5796> : Initializing native downloader...
INFO <11:15:16.127,T:5796> : init resource C:\Users\ose\Downloads\MiFlashUnlock_1.1.0317.1_en\res\ language:en region:
ERROR <11:15:17.003,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:17.648,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:18.294,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : Can't identify device in fastboot mode.(num=0)
INFO <11:15:34.057,T:4264> : to login by name:XXX pwd:XXX sid:XXX verify:EMPTY sec_token:EMPTY
INFO <11:15:34.090,T:4264> : LoginStep1
DEBUG <11:15:37.791,T:4264> : OnAccountLoggedIn
DEBUG <11:15:43.173,T:4264> : OnNewServiceCookies
DEBUG <11:15:43.173,T:4264> : Login success and get user detail
INFO <11:15:49.223,T:2032> : status result: {
"applyStatus" : 2,
"code" : 0,
"description" : null,
"shouldApply" : true,
"uid" : 1554152998
}
DEBUG <11:15:49.223,T:2032> : unlock status: 2
DEBUG <11:15:49.223,T:2032> : should apply:true
INFO <11:15:53.357,T:5796> : connected
DEBUG <11:15:56.569,T:10612> : VerifyDeviceInfo
ERROR <11:15:57.230,T:10612> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:57.873,T:10612> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:58.516,T:10612> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : Can't identify device in fastboot mode.(num=0)
WARNING<11:15:59.215,T:10612> : cannot get product info again
ERROR <11:18:15.927,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:16.589,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:17.233,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:17.935,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:17.936,T:2000> : Can't identify device in fastboot mode.(num=0)
ERROR <11:18:19.035,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:19.677,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:20.319,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : Can't identify device in fastboot mode.(num=0)
I also cannot go back to a Global stable/dev rom, using the updater.
Any advises?
Hi -
was trying to root my Note 10 lite and unfortunately i am now getting the following error. have gone back to stock firmware but anyone have any ideas why? followed these instructions androidinfotech.com/root-samsung-galaxy-note-10-lite-android-10
- Odin Mode (AVB Fail)
- vbmeta: error verifying vbmeta image: OK_NOT_Signed(3)
- vbmeta: VERIFICATION_DISABLED bit is set.
- vbmeta: NO sign info
- vbmeta
thanks
Rambam81 said:
Hi -
was trying to root my Note 10 lite and unfortunately i am now getting the following error. have gone back to stock firmware but anyone have any ideas why? followed these instructions androidinfotech.com/root-samsung-galaxy-note-10-lite-android-10
- Odin Mode (AVB Fail)
- vbmeta: error verifying vbmeta image: OK_NOT_Signed(3)
- vbmeta: VERIFICATION_DISABLED bit is set.
- vbmeta: NO sign info
- vbmeta
thanks
Click to expand...
Click to collapse
where abe to solve problem.. i am into the same situation
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