Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
flashing recovery the fastboot way
Dwait said:
Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
Click to expand...
Click to collapse
Hi,
You may be able to wipe your tears .This worked for me on the Huawei Ascend y300 which was rooted and had its bootloader unlocked first. Since I got a similar error to you using flash_image these steps might work for you too:
disconnect usb cable from phone
Boot into the bootloader mode (usually power and volume down).
reattach usb cable to phone
Download fastboot
get a dos prompt
navigate to the fastboot directory
do these commands followed by pressing enter:
fastboot devices
(your device should be listed)
copy and paste your recovery.img into the fastboot folder in windows.
fastboot flash recovery recovery.img
fastboot reboot.
Now make sure your phone boots normally.
Now power it off. Hold down volume up while pressing power, it should put you in your custom recovery.
Keiichicom.
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
Somehow I ****ed up my Oneplus One pretty badly.
I can't load in fastboot at all (either with pushing the vol+ key & power key nor with adb reboot-fastboot)
I already flashed the oneplus one recovery tool image and even tried the colouros image.
Nothing worked and I even can't adb push any file on my sdcard nor can I sideload any file to it (error can't find media)
every restart bring me directly to the recovery. (earlier i still had twrp running and tried wiping and flashing zips. even the stockroms didn't work. there was nothing else on the internal space but the gapps/rom zip files)
Isn't there a way I can force a complete image on my phone like I could on my Samsung with odin?
Did i accidently delete my boot partition?
How can I install the fastboot mode?
I will pay via paypal.
Hi everybody,
Sorry if my post already exists and if my english is bad but i really need help...
I tried to root my honor 7 so first i unlocked bootloader successfuly, i installed TWRP too and everything seemed work very good until last step where my phone didn't boot, i stayed stuck in boot logo... Then I done a factory reset with wipe cache, dalvik, data etc...
Now the only things i'm able to do are boot on recovery mode, eRecovery and on fastboot&rescue mode. I lost adb and fastboot and i'm not able to acess to the phone so i can't put a rom on the phone to install it...
If anyone could help me it would be very nice because I'm going crazy. Thank you !
My phone was up-to-date, i can't remember witch firmware i had but i think it was Android 6.0.1
samhot66 said:
Hi everybody,
Sorry if my post already exists and if my english is bad but i really need help...
I tried to root my honor 7 so first i unlocked bootloader successfuly, i installed TWRP too and everything seemed work very good until last step where my phone didn't boot, i stayed stuck in boot logo... Then I done a factory reset with wipe cache, dalvik, data etc...
Now the only things i'm able to do are boot on recovery mode, eRecovery and on fastboot&rescue mode. I lost adb and fastboot and i'm not able to acess to the phone so i can't put a rom on the phone to install it...
If anyone could help me it would be very nice because I'm going crazy. Thank you !
My phone was up-to-date, i can't remember witch firmware i had but i think it was Android 6.0.1
Click to expand...
Click to collapse
You didnt make any twrp backup??
If you have fastboot you can use Huawei update extractor to extract UPDATE.APP and flash boot.img and system.img directly to your device
Rayan19997 said:
If you have fastboot you can use Huawei update extractor to extract UPDATE.APP and flash boot.img and system.img directly to your device
Click to expand...
Click to collapse
Thank you for your reply. I'm able to enter in fastboot, i extracted boot.img and system.img from UPDATE.APP but i don't know what you mean by flash them because i have no link between the phone and the computer. I can't write on the phone, HiSuite tells that the phone is disconnected and explorer doesn't display the phone neither...
samhot66 said:
Thank you for your reply. I'm able to enter in fastboot, i extracted boot.img and system.img from UPDATE.APP but i don't know what you mean by flash them because i have no link between the phone and the computer. I can't write on the phone, HiSuite tells that the phone is disconnected and explorer doesn't display the phone neither...
Click to expand...
Click to collapse
OK it's good it works
I flashed with fastboot in command line and the reboot was magnificient !
Thank you !!!
I'm glad to see that you succeeded bro :cyclops:
how can u flash with fastboot while no connection to pc
samhot66 said:
OK it's good it works
I flashed with fastboot in command line and the reboot was magnificient !
Thank you !!!
Click to expand...
Click to collapse
how can u flash with fastboot while no connection to pc (as u said earlier)
if u did manage to connect to pc, please share how
thanks in advance
I'm not sure I understand the question but i'll try to explain.
I was not able to connect to PC apart with fastboot (reboot in fastboot mode and connect to PC). Once done, just open a terminal and type "fastboot flash boot <boot image file name>.img" then do the same with IMG (as said in this page .
Hope it will help you !
samhot66 said:
I'm not sure I understand the question but i'll try to explain.
I was not able to connect to PC apart with fastboot (reboot in fastboot mode and connect to PC). Once done, just open a terminal and type "fastboot flash boot <boot image file name>.img" then do the same with IMG (as said in this page .
Hope it will help you !
Click to expand...
Click to collapse
Read this carefully, this will restore youre phone:
1*.)No matter what youve done with this phone it will be cleanly installed like its fresh new, cause i had couple of problems and this method worked
1.)Download the latest b396 firmware
2.)format youre SD card with basic settings via Windows ( if you have a usb stick to connect youre SD card to computer like i do, if you cant connect youre SD card to computer, use another smartphone and format youre SD card with basic settings)- simply talking just format youre SD card
3.)create --->>>dload<<<--- folder like i wrote down without the --->>><<<--- stuff on youre SD card
4.)paste the update.app file to the dload folder
5.)insert youre SD card to phone
6.)this is the moment of truth hold down volume + & - key and power key all in once until the emui logo appears WARNING: remove all keys after logo appearing WARNING: if the logo doesnt appear even after 30sec. keep still holding until the logo appears
***If you get somekind of error i can help, if it worked youre a lucky guy
First of all, thanks for the great guides published here and all the work that went into them. They help resolve a lot of issues.
Unfortunately I encountered an issue today on my KIW-L21 that I can't find a solution for in the published guides. Today a stock update (installed via TWRP) got stuck on first boot and somehow managed to break the DLOAD recovery option (accessed by pressing Vol Up+Down when powering up the phone). Whenever I try to enter the DLOAD recovery mode now, the phone is not flashing the UPDATE.APP from the dload folder on the SD card anymore, but is showing an update screen (looks like a usb plug in a circle). This process stays on 5% for a while and then just reboots the phone into the regular system. So no option to recover from the UPDATE.APP anymore. Otherwise the phone still seems to be working fine.
Here's what I did to run into the problem:
- Successfully flash 5.1_EMUI 3.1_C432B140 firmware found in the Honor 5X repository on XDA via DLOAD recovery
- Flash TWRP (twrp-3.3.1-0-kiwi) via fastboot
- Download update to 6.0.1_EMUI 4.0_C432B350CUSTC432D003 via the regular update option
- After download the phone automatically booted into TWRP to install the update
- Reboot after TWRP flashed the update got stuck on boot and the DLOAD recovery got replaced by that update feature
Since then I booted into TWRP recovery again and installed AOSiP 9.0 + Magisk after wiping data/system/cache. This worked fine and AOSiP is booting and working correctly. The only issue now is that the DLOAD recovery did not get restored that way. That behavior stayed the same.
I tried eRecovery (reports an error after connecting to the wifi network, but this did not work before either) and stock recovery (extracted from B140 firmware and flashed via fastboot) without success. Both stock recovery options failed with an error message but did not provide any details regarding the issue.
Is the lost DLOAD recovery a known issue? Not sure if a partial update is stuck somewhere and needs to be deleted or if the DLOAD recovery function can be flashed via fastboot to fix this.
*** UPDATE 1
Here's some additional things I tried to fix the issue and that I noticed during those attempts:
- Recovery via HiSuite unfortunately does not seem to work. When booted into the bootloader HiSuite does not recognize the device. When booted into AOSiP, the phone is recognized, but the HiSuite app installed on the phone fails to work due to missing location authorizations. It doesn't ask for them though, just displays an error pop-up that leads to settings where I don't have the option to enable location access for the app. When manually checking the location permission for apps HiSuite is not among those that I can enable/disable this for.
- TWRP recovery can't be accessed from the phone despite flashing it via "fastboot flash recovery twrp.img". When launching recovery on the phone I end up in EMUI stock recovery. I can access and use TWRP via "fastboot boot twrp.img" though.
- I tried using the DLOAD update with the dload folder copied to the internal storage (local SD card). This did not change the phone getting stuck at a 5% update instead of the EMUI firmware flash.
- The local dload folder however seemed to have an impact on the stock recovery. While the stock recovery failed with an error before, it now gets the stuck at 99% done and a reboot just restarts the stock factory reset. I did find a way to exit this loop without waiting for the battery to drain (reboot with both volume buttons pressed into the update mode I don't want, reboot regularly once it stops on 5%) that got me back into a running/reset AOSiP.
- I can't boot into EDL mode via ADB (adb reboot edl). I was hoping HiSuite might help in that mode, but the command just rebooted the phone into AOSiP.
- The 5% update issue does not get resolved by disconnecting the phone from a cable during the operation. I read on XDA that this solved the issue for other HUAWEI devices, did unfortunately not work for mine.
- I noticed the bootloader does not show the FRP info anymore on the screen of the phone. It just shows "PHONE Unlocked". Not sure if that is important or just changed to this after unlocking the bootloader a few days ago.
The fact the flashing the recovery partition with TWRP does not seem to work properly suggests a partitioning issue to me. Is there a way to repartition the device and manually flash the relevant partitions via fastboot or some other tool?
If anyone knows how to fix the issue, a pointer in the right direction would be appreciated.
[SOLVED]
I finally managed to fix the issue by reverting to stock in several steps.
Tools required:
- Stock Firmware (I used the C432B140 I downloaded from the XDA Honor 5X repository)
- ADB/Fastboot toolset
- Huawei Update Extractor
- Stock firmware UPDATE.APP in dload folder on SD card installed in phone
1. I extracted BOOT.IMG, RECOVERY.IMG and SYSTEM.IMG from the full stock firmware
2. I rebooted the phone into bootloader (using command "adb reboot bootloader")
3. I flashed the stock recovery image (using command "fastboot flash recovery RECOVERY.IMG)
4. I flashed the stock system image (using command "fastboot flash system SYSTEM.IMG)
5. I flashed the stock boot image (using command "fastboot flash boot BOOT.IMG")
6. I rebooted the phone (using command "fastboot reboot"), this rebooted the phone in a stock B140 / B350 hybrid stock EMUI
7. I entered the ProjectMenu by entering *#*#2846579#*#* on in the phone app and chose "4. Software Upgrade" > "1. SDCard Upgrade" and confirmed that I want to perform the update.
8. The phone finally rebooted into the regular EMUI dload updater and reflashed stock firmware C432B140 to my phone
Afterwards the recovery from dload could also be started via Vol Up+Down when powering up the phone.
Hope this helps someone else fix the issue in case anyone encounters this.
I am facing a very similar issue on a KIW-L21 (running a custom ROM though).
Can anyone guide me to whether the steps presented can be modified to work coming from a custom ROM?