Please help everyone.
my device is in a bootloop state and restarts continuously until I have to unplug the battery so that my device can turn off, as I am trying to install TWRP via CMD.
I'm currently flashing my device infinix note 7,
on SP FLASH TOOL I always encounter the problem "BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)",
my device was detected on a USB drive as "Mediatek preloader usb vcom (android)"
it looks like my smartphone is not in edl mode, I've tried by pressing the top volume, the bottom volume, the top + bottom volume,
But still always get the problem "BROM ERROR: STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)"
Maybe someone can help me with my problem, Because I'm a beginner in this.
thanks
Adit
Related
Everything I've done as need sp flashtoolem, at the end of the show, a green check mark.
I disconnected the phone, try on and a button. Nothing responds to the charger, USB cable, or turning on Power.
After connecting the computer it does not detect it. Only when I press the volume down without batteries -It then begins installing drivers but every now and then connects to and disconnects the wilderness as a button hangs up pretty. On the Windows7 installs drivers and any Alcatel is device manager tab network adapters.
Under Windows XP, as the same thing I'll do is I choose the drivers and install mtk usb driver or something like that.If I hold the button volume down sees it but every now and then hangs up and connects. Turn on the SP flash rom going and what I did not press does not react, just as without battery and vol -, the program reacts goes red bar and pops up an error
bromine error s_ft_enable_dram_fail (4032)
I tried this rom with Jiayu Poland and pulled like Stocka F1WW-20140714-200639 -PC-update-foreign language
Previously , he was compiling 20150426 ,Nowhere can I find such romu
So much is happening with the phone. More I can not demented and I do not want him quite a blow.
ps. sorry for my English
No one can help? Where to find this rom?
Hello everyone! I brought a Lenovo Vibe X3 (x3a40) 3 months ago. And I updated it to MM 6.0.1 and the bootloader was unlocked and the device was rooted. TWRP was also installed. So I installed this CyanogenMod 13 from HERE.
Then I missed some stock features and decided to revert back to stock MM. And I used QFIL to flash the official stock ROM. But it turned out that QFIL suddenly stopped working and my device got stuck in EDL mode. Once I turned it off completely to flash it again, the device wouldn't boot up. In my case the device should get into EDL when I connect the USB cable and immediately hold the power key for a second. But there is no response.
Usually while booting the device vibrates but now there is no vibration nor is there anything on the display. The screen keeps completely off and it wouldn't boot into any mode, like no download/no recovery/no EDL/no bootloop, just cold.
And when I connect it to the USB all I get is the "Device not recognized" error. In device manager I get this "Unknown USB device (Device Descriptor Request Failed)".
Please note that I've tried switching the USB cable and the port as well as on a different PC and also checked with the drivers. Still the same. If someone could help me, it would be a great help.... :crying:
Further info on the device is here!
Hi,
I bricked my phone while I tried to root it.
Now the preloader seems to be missing so the phone does not connect to my computer in download more anymore as it did before I bricked it.
When I'm connecting it in Meta-Mode (by pressing Power+Volume Up) it connects and gets detected as Mediatek USB Device. Then Flashtool is loading the red process bar to 100% and remains silent. After some time an error message pops up that says:
BROM ERROR: STATUS_EXT_RAM_EXCEPTION (-1073414139)
I tried many different versions of the Flashtool - always the same problem
Do you guys have any idea ?
XDA Visitor said:
Hi,
I bricked my phone while I tried to root it.
Now the preloader seems to be missing so the phone does not connect to my computer in download more anymore as it did before I bricked it.
When I'm connecting it in Meta-Mode (by pressing Power+Volume Up) it connects and gets detected as Mediatek USB Device. Then Flashtool is loading the red process bar to 100% and remains silent. After some time an error message pops up that says:
BROM ERROR: STATUS_EXT_RAM_EXCEPTION (-1073414139)
I tried many different versions of the Flashtool - always the same problem
Do you guys have any idea ?
Click to expand...
Click to collapse
Hi and welcome to XDA.
Try posting your query in:
> Android Development and Hacking > Android Q&A,Help and Troubleshooting.
You'll have to create an account to post in the main forums.
Good luck
STUCK using msm tool for oneplus 6t at 9% " firehosecheckrsp failed " errno258
STUCK using msm tool for oneplus 6t at 9% " firehosecheckrsp failed " errno258
pls help
I CAN ONLY ENTER FASTBOOT MODE
DEVICE STATE 'LOCKED''
@sAmboy13
Once you are in fastboot mode at the screen that reads "START" use your volume rockers to navigate up or down and go to screen that reads "POWER" and use your power button to then select that and your device should turn off and you can then connect your device how the directions say and your PC should see your phone and in device manager your OnePlus 6t will be labeled Qualcomm USB driver or something like that.
User who commented after my post here is correct. And any time your using crappy windows best believe the Qualcomm USB drivers are not going to install smoothly. I had to uninstall mine and reinstall to get them to work.
I believe firehose has something to do with the connection between your device and the computer, like a connection. I know on Motorola devices firehose means your PC is attempting to communicate with your device...
(Edit)
The thread for that tool specifies to hold the volume up button for 5 seconds before connecting however I found I needed to hold both volume up and volume down to get the tool to work. Make sure to go to fastboot and then turn the phone off before this as it won't work if you've already tried connecting using the volume up method while off. Gotta start fresh. Hope this helps.
FirehoseCheckRSP
Hello. How to solve this problem?
Use one of the Fastboot roms there pretty much foolproof.
I am facing the same issue in my OP6T
> Device issue (Stuck at Boot Logo)
> Fastboot Accessible
> Recovery Inaccessible (stuck at boot logo)
> Device Detected Successfully in EDL Mode
> Bootloader Locked
While flashing stock rom using msm tool
It stuck at:
Firehorse Check Rsp Failed Err 258
I also tried flashing through fastboot mode but Bootloader is locked, so failed
Help please
I haven't seen a solution posted yet about this issue anywhere, but if anyone comes across this, I was able to solve this using a different usb cable and port. I was hitting this error midway when using a usb-c to usb-c cable on my laptop's thunderbolt port, and it worked when I used the original usb-a to usb-c connected to my laptop's USB 3 A port.
Same here. Worked with usb-a to usb-c, but not with usb-c to usb-c. Thank you!
I entered fastboot in my gionee F205 through ADB and entered the command 'fastboot continue' which I got a error FAILED (remote: not support on security).
So I tried to unlock OEM and did the same through fastboot. Now when I reboot my device it is stuck in a bootloop with a message 'orange state your device has been unlocked and can't be trusted your device will boot in 5 seconds'. It reboots again after that 5 secs.I have not yet rooted my devicee. Please help
Edit:
Okay, I solved it. The issue was solved when I removed all unnecessary VCOM drivers from my PC and mainly the MTK USB driver since it was the problem(I suppose). My phone was switching between the preloader driver and MTK USB driver and this was causing SP FLASH TOOLS to think my device disconnected, giving me the error(The flashing is happening only when the PC detects my phone as VCOM PRELOADER driver. So I uninstalled that driver and the problem was solved. I also had to plug my USB in at moment when my phone would be recognized as PRELOADER DRIVER in my pc.
So it is now well and running
Hint: Add Gionee F205 to this thread's title thus mainly owners of such device get addressed.