After flashing the preloader, the device is listed as "unknown" with a message "device descriptor request failed" in the device manager. That makes flashing it impossible, since SPFlashTool will not detect it. I have tried (re-)installing all the drivers, but with no success. I believe the phone is currently empty with only the preloader installed. Any help on this would be appreciated.
Processor : MTK6763
Device: Ulefone Power 5
(Supposed) Android version: 8.1
Related
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNEx-tkoU1eacV3YJWSk3s0DdY0eAQ
Hello guys, I have a HiSense U970 with the MT6589 chipset which got hard bricked a week ago. The phone is running a stock 4.2.1 JB and rooted. The problem is that whenever I try to flash anything using SP Flash Tool it shows this error:
BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM failed
I am hopeful the phone isn't totally dead since it can be:
- Detected by the computer WITHOUT the battery while holding vol down
- In Device Manager, it would show MTK USB Port (ComX) under Ports when vol down is held.
This is what happens now:
- Charging does not do anything.
- Cannot boot into recovery
- Cannot be detected by MTK Droid Tools (but I think this app needs a powered up phone to be detected by its system)
- Cannot flash anything using SPFT v3.1320.0.174 and v5.1524.00
I have searched the internet for fixes and solutions but, everything that I have found leads to that error.
Here was what I had done before the problem arose.
- Installed Preloader driver
- Used the latest version of SPFT
- Formatted whole flash except bootloader as I cannot flash the cwm rom found here without formatting
- Flashed ONLY the recovery and then downloaded it.
Green circle appears and after that, it cannot boot anymore. Cannot charge. Cannot boot into recovery.
I have tried the following with no luck:
- Used SPFT v5.1524.00 and v3.1320.0.174
- Flashing only the preloader
- Flashing only the recovery
- Format whole flash
- Formatting whole flash except bootloader
- Format all + download (v5)
- Firmware upgrade + upgrade (v3)
- Using the write memory method for writing preloader
- Flashing stock preloader
- Doing a memory test
All of which goes to the error 4032.
I have also tried using different USB ports with the same results.
If it helps, I used the scatter file for MT6589 and not my own scatter file. Using my own scatter file does not do anything before I flashed the recovery rom so, I used the MT6589 scatter file instead. Also, my scatter file was different from the MT6589.
- This was the scatter file I used.
- And this is my log from MTK Droid Tools which hopefully contains the addresses for the scatter file (I accidentally replaced my own [yea i know, stupid me])
I also cannot find the same scatter file that I had created anywhere on the internet.
I am willing to supply you with anything as long as I have access to it (hoping I have the file/information you need:fingers-crossed.
I am hoping that you know or at least the very least, can guide me out of mine and others misery. Thank you. :fingers-crossed:
[Solved] Officially Unlocked, Custom Rom flashed. Will I ever need "EDL Mode"?
Officially Unlocked, Custom Rom flashed. Will I ever need "EDL Mode"?
Device: - RN3 Pro Rom: - xiaomi.eu 6.8.11 Kernel: - Radon V2.2
Note: - Device is fully operational and not bricked at present.
Edit: I believe my device was already installed properly, wasn't looking under "Ports" for it but other devices.
When I unplugged the device and reconnected I was getting the error below.
Been playing around to see if I could setup "Windows 10 AU" to see my device while in "EDL Mode".
It doesn't recognize the device in this mode. Device manager reports "Unknown USB Device (Device Descriptor Request Failed)" under USB controllers. Updating the driver doesn't work either.
I have both MiPCSuite and MiFlash installed.
Will I ever need EDL Mode in the future under the above conditions?
Above post updated.
Hello all good souls over here.
Could you please help me out with flashing back the original stock ROM to Mediatek MT6737M phone?
UMAX VisionBook P50 LTE, Mediatek MT6737M, 2GB RAM, 16GB internal memory.
What happened:
Before I was trying Oukitel P5 Pro ROM as well as Lineage OS and flashing with SP Flash Tool was working just perfectly.
But then I tried to flash Oukitel P5 Pro Andorid 7 stock ROM. (Oukitel P5 Pro and UMAX VisionBook P50 LTE are completely the same phones. Just different branding)
(And from now on I am not sure if I remember correctly)
When I loaded in scatter file, SP Flash Tool said something about something .... and recommended to do "Format all + Download" and I have done so.
Clicked on the Download button, flashing started instntly when I connected the phone while holding Volume - button.
Flashing stopped in maybe one second with the error which I do not remember as I closed the error window way too quickly. :-(
Later on I noticed that the preloader file is different in this Android 7 ROM then Android 6 ROM.
What is the current behavior:
When the phone is connected (with the battery inside) to the computer phone keeps connecting and disconnecting (appearing in Device manager as Mediatek USB Port) if I click Download button it starts doing "something" instantly which stops at Download DA 100% and after the while ERROR: S_FT_ENABLE_DRAM_FAIL (4032) pop up windows shows up.
The same error happens if I try to Format it and all other combinations in Download tab (Firmware upgrade, Format All + Download)
If I plug in the phone to the computer while pressing Volume - button phone will show up in the Device manager after about 20 seconds.
(Just to note - When the phone was working OK, I started flashing instantly when I plug the phone into the computer while pressing the Volume - button
So that kind of leads me that if nothing will show up in Device manager when I plug the phone to the computer while pressing Volume - button, then there might be the issue with the phone not switching into META mode? Not sure, just what I have read. But I cannot move any forward at this point.)
What I have tried:
- Correct stock ROM and Oukitel stock ROM (both Android 6 and both I was able to flash correctly and was able to boot them, until I tried Android 7 ROM)
- various SP Flash Tools 5.xxxx (and 3.xxxx too, but version 3 does not accept scatter file at all)
- USBDeview and removing all related USB devices from Windows and re-install them back again.
- Various VCOM drivers I have found on the Internet
- Flashing with SP Flash Tools on Linux (ends up with the exact same result - 4032)
- I tried shorting test point to ground on the phone main board. (The result was the same like when I plug the phone in while holding the Volume - button - Phone would not show up in Device manager for about 20 seconds)
- Tried flashing with the battery inside and outside the phone. (When the battery is outside flashing would not start, but the error about incorrect chip type will show up)
- Read many articles about this error all over the Internet
Do any of you think there is a change to bring the phone back to live? Or do you know what actually might happen to the phone? It does not seems to be completele bricked, but I cannot say in what state the phone is.
Thank you very much for your help and have a nice day.
Hi. I need this rom for this phone. I have umax p50 lte too . Please give me link if you can. Thx
@oukitel654
Look inside here:
Common SP Flash Tools error and Solutions - ROM-Provider
Common SP Flash Tools error and Solutions: Hello guys if you are facing a SP Flash tools error code issue then this page is for you where we share solutions for for almost all SP Flash tools error. Common SP Flash Tools error Code: Error 5054, 4032, 8038, 5069, 4001, 4008, 3149, 3168, 2004, 1013, …
romprovider.com
Device model: Motorola G51 5G
Android Version: Android 12
I need assistance, please. After I restarted my phone, I get this message saying "No valid operating system could be found. The device will not boot." My device is rooted through Magisk, by the way.
I searched & I found that flashing it with a stock firmware would resolve it. Motorola's Rescue And Smart Assistance isn't working for me, it says that "Some key information cannot be read from the device, please unplug and reconnect your device with fastboot" when I plug it in my laptop. Manually selecting my device's model name is giving me the message, "The model associated with the IMEI for your device is currently not supported by Rescue And Smart Assistant.
Then I tried using ADB but my device doesn't show up when I type the command "adb devices." ("fastboot devices" command work though, it shows my device). I installed Android SDK, Google USB Drivers & Motorola Drivers but it still doesn't show up. I tried connecting a different phone & it shows up but not the G51.
Hoping for assistance, thank you.
*EDIT*
Nevermind. I was able to fix my phone successfully through ADB somehow. Please delete this thread.