Everything was okay until I tried to flash logo.bin with fastboot because when i was trying to flash it took to so long so i had remove the cable. Since than it is stuck on AP Fastboot screen with fastboot reason
Fastboot reason : Flash Failure
Now my phone is not detected with RSD lite even if gets detected it can't flash stock and the operation stops with some error like USB error reading writing. I still can use the custom recovery is there anyway to flash all the stock rom files with custom recovery.
More Info
Pc used for operation Windows 7 64bit
Phone Bootloader KK (Unlocked)
Last usable rom was CM 11
Thanks
Fastboot dose recognize my phone but when i try to flash a file it gives error
"data transfer failure too many links"
Problem solved Changed the cable and used RSD to flash back the stock firmware.
Related
i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
ishamm said:
i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
Click to expand...
Click to collapse
Reflash the gingerbread pudding .sbf, you're bootloader isn't unlocked anymore.
Sent from my MB860 using xda premium
the sbf i flashed was from the pudding page, and i unlocked the bootloader again fine, have the unlock sign on the Moto boot logo, just cant get any further than that with ROMs anymore..
EDIT: i am also getting the issue when flashing any kernels,
I can flash a recovery through fastboot, which it says is successful, but when i try to boot into recovery i get failed to boot 2, entering RSD mode.
so this is status of my device
bootloader ...locked
recovery....ok
fastboot mode .....ok
so i tried two options make ota zips and flash them via stock recovery (i coded update script and signed it but it says verfication failed ).
and i tried all fastboot options.
i tried flashing with ost.
i tried QFIL but it dosent recognize my devize .
edl cable just boots device in download mode,
Dear members, this is my first post and the problem is very complicted, so please bear with the long post
Device details:
LeEco Le1s (x500)
MTK6795 chipset
3 GB + 32 GB (Everybody knows )
Background:
I downgraded my ROM from 19s to 14s with SP Flash tool and the phone booted normally. I went through the initial setup, unlocked Developer mode and USB debugging. Then I opened the adb toolkit on Win 7 x86 machine to unlock bootloader and install twrp custom recovery at single go (instead of letting phone rebot after bootloader unlock and then proceeding with recovery flashing).
Now phone went to soft brick, to overcome which I needed to flash userdata with sp flash tool (I have done this in past also following a tutorial, the same files were used this time). But flashing process resulted in BROM error and I was not successful.
So, I re-flashed the original 14s rom via SP flash tool to get the things back to working, but phone didn't boot properly and bootloop situation was still there. I again reflashed the same ROM and this timephone entered red light of death mode, and didn't boot up after flashing original rom.
Now, I again googled this problem and found that we need to format flash with bootloader. Here the problem complicated further.
As soon as I formatted the flash and the bootloader, laptop stopped detecting the phone via usb cable. Now I can't flash any rom using SP flash tool as the phone is not detectable.
I have reinstalled my windows 7 32 bit operating system and reinstalled all the drivers for MTK smartphone. I have another Le1s phone running on 19s version of EUI marshmallow with stock recovery and locked bootloader which is detecting fine without problems.
Please guide me how can I resolve the problem.
Also guide if the other phone can anyhow help in this matter in terms of software backup for SP flash tool (I couldn't find a way of backing stock rom using SP flash tools.
Problem summary:
1) Flash with bootloader formatted
2) Phone is not detectable on Windows 7 32 bit OS and latest SP flash tools
3) Red LED turns on when phone connected to charger or laptop via usb cable,nothing on LCD display
4) Can't reach bootloader or recovery either
Help will be really appreciated. You all know the value of data stored on smartphones.
Thanks in advance!!
can explain how you were able to solve it?
facing a similar issue would ne helpful.
thanks.
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile
I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks
1st Try to Flash with latest RAW,
If fail, Try with CSC
If still fail try with EDL File (Unbrick) - ZE552KL Libra_QFIL_8953_01020_20170714_Aboot.7z
eemmiirr said:
I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks
Click to expand...
Click to collapse
I have this problem too. How did you fix it ?