"FAILED (remote: flash write failure)" - Android Q&A, Help & Troubleshooting

Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on Yu website using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !

nitin27902 said:
Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on Yu website using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !
Click to expand...
Click to collapse
Did you got it solved ??

Related

[Q] Lenovo P780 Boot loop help pls!

Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Axis76 said:
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Click to expand...
Click to collapse
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
droidinterest said:
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
Click to expand...
Click to collapse
Yep. Tried using several versions of the drivers downloaded from different places and used USBDeview to remove/reinstall them. The error still comes back and haunt me.
maybe this can help you
No luck.... formatting is not working in sp flash tool (4010 error) and the preloader in the thread is not for my phone.....
Anyone able to help pls....?
Axis76 said:
Anyone able to help pls....?
Click to expand...
Click to collapse
have you use google my brother ? google is our true friend.
but i glad if i can help you:angel:
you can visit this for factory rom
or you can visit lenovo forum
or you can go to needrom
Yeah. Google had been my fren, but no more after googling for 2 weeks without a solution. Trust me. I had looked thru most solutions found in google and had tried without any success before I post here.
All those stock roms of all release numbers I had already tried as mentioned above, with sp flash tools (tried many versions of that also.) ALL attempts are stucked with the errors mentioned above. The sp flashtool simply just fills the red status bar, and stopped with one of the errors in my 1st post.
I've even checked the chinese forums. My situation seems to be this:
The partition table of the flash memory had been reformatted thanks to the custom rom flashed via sd card. That's why it always returns a format flash error when I attempt to flash back to the stock rom which uses a different format range using sp flash tools. The only way out is to do a clean format of the flash memory. But I haven't find a way to do that via sp flash tool or mtk droid tool.
My only recourse is on of the following:
1. If I can restore the custom recovery (via adb in recovery mode(no fastboot) or meta mode) and make it workable to do another sd card flash with a custom rom. I have no idea why the options in my custom recovery went missing. It was working before I flashed the custom rom. I guess that accursed rom somehow erased my custom recovery during boot.
2. If I can somehow be able to do a complete flash format with the correct format parameters using some tools. Sp flash tools had failed me so far.
Anyone is able to help in these directions? Many thanks....
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
anyone can help......?
Axis76 said:
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
Click to expand...
Click to collapse
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
droidinterest said:
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
Click to expand...
Click to collapse
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Axis76 said:
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Click to expand...
Click to collapse
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
droidinterest said:
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
Click to expand...
Click to collapse
Already tried this. I had tried on 2 pcs. Windows 7 and windows xp (no digital signature). Same errors occur in both pcs. I really don't know what is going on with this phone. Nothing seems to work.
PS: Have been running the program as administrator all along also.
Sent to a phone repair shop and its at worst state than before now. Unable to power on. Connecting phone to computer and tried using sp flashtool now gives 4032 error (Enable Dram failed).
Any hope with reviving this phone now?
leno p780 in bootloop
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
AshishKhalkho2013 said:
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
Click to expand...
Click to collapse
Hi, first, do you have SP Flash Tool installed on your PC and have the drivers installed? If yes, download the stock ROM of your choice from here and flash it with via SP Flash Tool, and your phone should be revived.
Flashing methods are clearly stated in case if you don't know how to do it.
lenovo p780 not booting
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
somu12345 said:
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-brick-t2782696/post53395430
WHAT CAN I DO___???
hardware
Axis76 said:
anyone can help......?
Click to expand...
Click to collapse
check on hardware, there must be trouble with your flash chip ic, try to rehot it first.
if doesn't work that mean your flash chip ic completely dead

Mate 7 (MT7-L09) Bootloop, unable to flash roms via recovery, fastboot not working

Hello guys,
I tried to update my phone to marshmellow, it got stuck at 95% and after it it entered a bootloop, I thought on just installing a custom recovery and take it from there but when I use fastboot it gives me a Remote: command not allowed error, I have my bootloader unlocked, I am thinking this has to do with not having USB debugging enabled, I can´t access the phone to activate it though. I have also tried to flash lots of stock roms through sd putting them on dload folder on Sds root but it fails right away at 5% it says update install failed, at this point Im not sure what to do... Any ideas?
thanks

Error: Reading Hello Packet

Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Try rebooting into edl mode again and flash back the rom
neme2k said:
Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Click to expand...
Click to collapse
Hi gus! have you solved your problem
Provide me your solution please, i'm in the same situation now with my Redmi note 3 Dual Sim
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
karkand said:
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
Click to expand...
Click to collapse
already try this step but still same error.
Windows must be 64bit (windows 7 or later),connect your phone to rear usb ports. In my case this was the problem (same error as yours).
Sent from my Redmi Note 3 using Tapatalk
I've the same problem. There is a solution? I've the virtualisation of Windows 7 64bit on linux, i don't know if this is the problem or not.
Got the solution....
I got the solution for all xiaomi users...
You just have to factory reset the device an then you are ready to go
if your device doesn't start then go to the fastboot menu and open cmd in the pc after connecting the phone to the pc...
then follow my steps
1. go to the adb folder.......
2. Then hold shift and right click there and click on "Open Command Prompt Here" it will open cmd .
3. The check if the device is detected or not if not the go to device manager and update the driver...
to check type : fastboot devices
4. then type fastboot -w it will wipe your whole data and do not start the phone firstly just flash the stock rom and then turn it on...
5. hurray i hope your problem will be solved.....
Thank you............​

Device unable to boot: Error - mdtp image is corrupted

So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system. :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could possibly do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: FAILED: (write to device failed(unknown error)). If there is a fix, please reply. I would be crying if it works.
MAJOR UPDATE: Yes, it's fixed! I've waited until the battery completely drain out, then plug it back in, it loaded into the original fastboot screen! I can flash the stock ROM and use it again! I'm literally happy rn.

Help pls. RedmNote 4 bootloop.fastboot flash gives error. sec partition write failure

Hi guys. Any help would be very appreciated.
I have a redmi note 4 Mido.
I was on a conference call and the phone's screen and buttons stopped working. The call was still going on fine, but I couldn't unmute. So I long pressed the power to reboot.
The phone went into bootloop.
I tried to do a factory wipe from recovery but it stops at 99.99%.
I tried to flash using flash_all.bat but there is a sec.dat write failure error which stops the process.
MiFlash tools also gives an error and suddenly closes.
I manually tried to flash the sec partition using "fastboot flash sec sec.dat" but I get the same flash write failure.
I tried to format the sec partition but I get an error "fastboot: error: Formatting is not supported for file system with type ''.
Erasing the sec partion does work. but still can't write to it.
I tried to flash boot.img and recovery.img and it works.
The bootloader is unlocked.
I have stock recovery. I tried to boot, "fastboot boot twrp.img(twrp3.1.1-0)" but it gets stuck on teamwin logo screen.
How should I proceed?
I think you have try to flash fastboot rom
satyam0236 said:
I think you have try to flash fastboot rom
Click to expand...
Click to collapse
I tried it multiple times, but it gets stuck on sec partition write failure.
I added 'fastboot unlock' in the bat file before the flash sec line ane it flashes without error. But still the phone doesn't boot.
Hi, I have the same problem, did you find a solution?

Categories

Resources