I bricked (dead boot) (not even charging or power on) my canvas 4 by formating it with sp flash tool without loading preloader file.
Now I m trying to flash a new STOCK ROM with sp flash tool latest version in my phone but i get this error:
"BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] ENABLE DRAM FAILED!
[HINT]: PLEASE CHECK YOUR LOAD MATCHES TO YOUR TARGET DEVICE WHICH OS TO BE DOWNLOADED."
I m flashing the correct ROM and im sure for that dont know where i am going wrong
PLS HELP.
THANK YOU!!!!!
My device(Nubia z11 minis) is hard bricked, i think its a dead bootloader, my computer detects device at 9008(old I think) port no partition of device is visible. I tried Qfil and Nubia studio tool both fail with error Qfil gave me Sahara error couldn't communicate with flash programmer
While Nubia tool gave me file not found error. I need help to fix.
Device has no led
Does anybody here knows about MPRG8953.Mbn
And 8953_msimage.mbn
Nikhil Joshi said:
My device(Nubia z11 minis) is hard bricked, i think its a dead bootloader, my computer detects device at 9008(old I think) port no partition of device is visible. I tried Qfil and Nubia studio tool both fail with error Qfil gave me Sahara error couldn't communicate with flash programmer
While Nubia tool gave me file not found error. I need help to fix.
Device has no led
Click to expand...
Click to collapse
Ok. Folder with raw image (where is rawprogram abd mbn file) should be in root of c: partition.
Also, try miflash if qfil fails
Already tried it's no use
Found a solution but i need two file MPRG8953.mbn and 8953_msimage.mbn
https://gizchina.it/2017/01/nubia-z11-mini-s-unbrick-nubia-studio-tool/
Послато са NX549J уз помоћ Тапатока
Nikhil Joshi said:
Found a solution but i need two file MPRG8953.mbn and 8953_msimage.mbn
Click to expand...
Click to collapse
i want it too.
Anyone try this link?
China or Global ROM?
https://drive.google.com/file/d/1uBnrVo_TfIa8iUWrDGr7j90SojFEs-4z/view
and
https://drive.google.com/file/d/1wM1ymz9CRArNcmqaIjlVZbrWOlis0VqJ/view
My phone is blinking when connected to my system, but no display, no recovery mode.. its just blink.. none of the side keys responded to boot menus/ fastboot menus..
i followed instructions, its getting patched through qfil tool, but still the same problem. phone is not booting to normal.
any clue will help to recovey my phone...
Hello everyone.
my Lenovo TAB3 Plus (tb3-x70f with an mt8161 chip) is bricked an i need some help.
I think i bricked it when i flashed the boot and recovery partitions via fastboot using the wrong images.
To resore it i tried using the sp flash tools and a firmware i found on the internet.
Sadly the flashing process failed with an error from the sp flash tools:
BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
The chioce of firmwares for the tablet is limited and i thought maybe i got the wrong ones.
So i decided to create my own backup from a new, still operating TAB3 Plus.
There for i followed a tutorial on forum.hovatek.com/thread-21970
But this didnt work neither. Sp flash tool failed with BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032).
I installed like every Mediatek driver i could find, tried different usb-ports (some usb3 and some usb2) and cables, operating systems (Windows 10, 7 and ubuntu) and versions of the sp flash tools. Nothing helped.
I got several questions:
What is the DRAM?
Why is the sp flash tool not able to enable it?
Was anyone able to use the sp flash tool with an mt8161?
What might i have done wrong?
Are there other tools i should try?
Thank you all for your comments in advance!
Mo
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM
Moderator Message:
Extreme caution required as this method may erase your IMEI!
Click to expand...
Click to collapse
Welcome
No to monopoly
Sometimes we may encounter a problem when the ROM is finished flashing, and a problem may occur, which is the inability of the device to work and returns to the black screen and the devices go to edl 900E
This file can return the phone to work
The method is as follows
1- You will need the qfile program, you will only choose to delete the files
2- Run miflash, it will flash the file
note :
Consider it the last resort
The possibility of losing imie
upload by badar.albaloshi
unbrick redmagic 5G-5S
pass aa999999
how exactly ccn be delete the files with qfil???