[Q] Error 0017 flashing stock firmware

Search This thread

dunc4n88

Senior Member
Nov 16, 2011
606
222
another suggestion boot into cwm and try to mount everything the data the cache everything and see if it mounts them if it does then that would indicate that the vital partitions are ok if they all mount try installing rom

report back

Sent from my C1905 using XDA Premium 4 mobile app

---------- Post added at 09:19 PM ---------- Previous post was at 09:19 PM ----------

but first flash the cm11 kernel before hand

Sent from my C1905 using XDA Premium 4 mobile app
 

goocreations

Member
Feb 8, 2014
19
4
another suggestion boot into cwm and try to mount everything the data the cache everything and see if it mounts them if it does then that would indicate that the vital partitions are ok if they all mount try installing rom

report back

Sent from my C1905 using XDA Premium 4 mobile app

---------- Post added at 09:19 PM ---------- Previous post was at 09:19 PM ----------

but first flash the cm11 kernel before hand

Sent from my C1905 using XDA Premium 4 mobile app

All partitions can be formatted and mounted - so my partition table might not be the problem.
I think I've now tried every possible combination in CWM. These are the options I've tried:

1. Wipe data and cache, format all partitions (data, system, boot, cahce), unmounted all partitions (), installed zip = symlink error
2. Wipe data and cache, format all partitions, mounted all partitions, installed zip = symlink error
3. Wipe data and cache, mounted all partitions, installed zip = symlink error
4. Wipe data and cache, unmounted all partitions, installed zip = symlink error
5. No wiping or formatting, unmounted all partitions, installed zip = symlink error
6. No wiping or formatting, mounted all partitions, installed zip = symlink error

But now after all this, I viewed the log (under advanced):

Code:
minzip: Extracted file "/system/app/WAPPushManager.apk"
minzip: Extracted file "/system/app/WhisperPush.apk"
minzip: Can't create target file "/system/bin/adb": Read-only file system
symlink: failed to remove /system/bin/su: Read-only file system
symlink: failed to symlink /system/bin/su to ../xbin/su: File exists
script aborted: symlink: some symlink failed
symlink: some symlink failed
E:Error in /storage/sdcard1/cm-11-20140204-UNOFFICIAL-c1905.zip
(Status 7)
Installation aborted.
I:using /data/media for /sdcard/0/clockworkmod/.
last_install_path.
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1

Can you do anything with this?
 

dunc4n88

Senior Member
Nov 16, 2011
606
222
looking at the top lines looks like the device is locked un a read only state and also the mmcblk is the partition tables so looks like they are corrupted aswell could be wrong tho just looked through mine and the bottom address doesnt exist on my phone in them directories there somewhere else think its gonna be a case of using adb to fix this but im no good with adb we need another person here to give guidence aswell ill pm another member who might be able to help

Sent from my C1905 using XDA Premium 4 mobile app
 
  • Like
Reactions: jckelsall

jckelsall

Member
Jan 22, 2014
6
0
Hey, I am having a similar problem - I accidentally unplugged my Xperia M (Single SIM, C1905) while flashing a new boot.img. Now, the only sign of anything happening is the LED flashing red when plugged in. To fix this problem, I tried to boot into fastboot to reflash the boot.img, but my phone will not boot into fastboot at all.
I have tried to reflash the stock firmware using flashtool, and repeatedly get a similar error to yours:
23/058/2014 12:58:08 - INFO - <- This level is successfully initialized
23/058/2014 13:03:45 - INFO - Flashtool Version 0.9.15.0 built on 15-03-2014 23:00:00
23/003/2014 13:03:46 - INFO - Device disconnected
23/003/2014 13:03:54 - INFO - Selected Bundle for Sony Xperia M (C1905). FW release : 15.1.C.2.8. Customization : CE
23/003/2014 13:03:54 - INFO - Preparing files for flashing
23/004/2014 13:04:28 - INFO - Device connected in flash mode
23/004/2014 13:04:40 - INFO - Please connect your device into flashmode.
23/004/2014 13:04:41 - INFO - Device disconnected
23/004/2014 13:04:57 - INFO - Device connected in flash mode
23/004/2014 13:04:57 - INFO - Opening device for R/W
23/004/2014 13:04:57 - INFO - Reading device information
23/004/2014 13:04:57 - INFO - Phone ready for flashmode operations.
23/004/2014 13:04:57 - INFO - Start Flashing
23/004/2014 13:04:57 - INFO - Processing loader.sin
23/004/2014 13:04:57 - INFO - Checking header
23/004/2014 13:04:57 - ERROR - Processing of loader.sin finished with errors.
23/004/2014 13:04:57 - INFO - Ending flash session
23/004/2014 13:04:57 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC=" 0x80080021 ";

The boot partition on an Xperia M is located in dev/block/mmcblk0p17, so I think that the 'ERR_CODE="0017"' could be to do with the boot partition number.
 

hardwarematik

New member
Sep 21, 2014
2
0
Hello:
I'm HardwarematiK, i never post before and is a pleasure for me to contribute to this great comunity with a posible (in my case worked in a C6603 and in a L36h [C6602]) solution for this problem, after so many time finding, testing and analysing I realized that the problem is the KERNEL is corrupt, so a find KERNELONLY .tft and in the flash mode (not in the fastboot, before also try so many thing in this mode) I flash this kernel only tft and them in the first case of the C6603, after also flash the the complete tft file, in the other Sony was not necesary. Hoping that this solve the problem, I'm here to answer any question. Thanks
PD: also I have the KERNELONLY file but, googling also is so many, IS IMPORTANT KERNELONLY version the same that the tft complete file.
 

betttttto

New member
Feb 17, 2015
1
0
Hello:
I'm HardwarematiK, i never post before and is a pleasure for me to contribute to this great comunity with a posible (in my case worked in a C6603 and in a L36h [C6602]) solution for this problem, after so many time finding, testing and analysing I realized that the problem is the KERNEL is corrupt, so a find KERNELONLY .tft and in the flash mode (not in the fastboot, before also try so many thing in this mode) I flash this kernel only tft and them in the first case of the C6603, after also flash the the complete tft file, in the other Sony was not necesary. Hoping that this solve the problem, I'm here to answer any question. Thanks
PD: also I have the KERNELONLY file but, googling also is so many, IS IMPORTANT KERNELONLY version the same that the tft complete file.

Might HardwarematiK how are you telling me that I can use in kernel xperia m? kernel can not find any stock in google for xperia m. if you have the kernel tft pasarmelo Might thanks
 

BleedBlue

Member
Mar 7, 2015
36
0
Hi.
I flashed my ta partition back on my phone. Afterwards it only boots into flashmode.
When I try flashing, it gives the loader.sin error.
Is there a solution to this?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I have a Xperia M C1905 and tried to flash the stock firmware using Flashtool. I've tried this process with 4 different firmwares (since many people say the downloaded file is corrupt), but the error persists, so I think it's the phone and not the corrupted firmware.

    When I try to flash the firmware, I get the following error:
    Code:
    15/008/2014 09:08:15 - INFO  - <- This level is successfully initialized
    15/008/2014 09:08:15 - INFO  - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
    15/008/2014 09:08:20 - INFO  - Device disconnected
    15/008/2014 09:08:23 - INFO  - Device connected in flash mode
    15/008/2014 09:08:51 - INFO  - Selected C1905 / 15.1.C.1.17 / aerialus indo
    15/008/2014 09:08:51 - INFO  - Preparing files for flashing
    15/009/2014 09:09:10 - INFO  - Please connect your device into flashmode.
    15/009/2014 09:09:11 - INFO  - Opening device for R/W
    15/009/2014 09:09:11 - INFO  - Reading device information
    15/009/2014 09:09:11 - INFO  - Phone ready for flashmode operations.
    15/009/2014 09:09:11 - INFO  - Current device : Unknown: Aug 22 2013/01:15:50 - YT910KLDDY - Unknown: Aug 22 2013/01:15:50 - Unknown: Aug 22 2013/01:15:50 - Unknown: Aug 22 2013/01:15:50
    15/009/2014 09:09:11 - INFO  - Start Flashing
    15/009/2014 09:09:11 - INFO  - Processing loader.sin
    15/009/2014 09:09:11 - INFO  -     Checking header
    15/009/2014 09:09:11 - INFO  -     Flashing data
    15/009/2014 09:09:11 - INFO  - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
    15/009/2014 09:09:12 - INFO  - Processing partition-image.sin
    15/009/2014 09:09:12 - INFO  -     Checking header
    15/009/2014 09:09:12 - INFO  -     Flashing data
    15/009/2014 09:09:12 - INFO  - Processing kernel.sin
    15/009/2014 09:09:12 - INFO  -     Checking header
    15/009/2014 09:09:12 - INFO  -     Flashing data
    15/009/2014 09:09:12 - INFO  - Ending flash session
    [COLOR="Red"]15/009/2014 09:09:12 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C "; 
    15/009/2014 09:09:12 - ERROR - Error flashing. Aborted[/COLOR]
    15/009/2014 09:09:12 - INFO  - Device connected in flash mode
    15/009/2014 09:09:13 - INFO  - Device disconnected

    I've attached the full log (with DEBUG enabled) for more info.

    I've also tried this process from different computers, with different USB cables, older versions of Flastool, manaully formatted everything in CWM, but nothing helps.

    Does anyone have a clue what is happening?
    1
    if you want to return to the stock you can download Sony PC Companion ..( your phone recomend to install it when you connect it with your pc) and click Support Zone to repair your phone...

    You must have locked bootloader bcz he will tell you that your system is modified
    1
    if you want to return to the stock you can download Sony PC Companion ..( your phone recomend to install it when you connect it with your pc) and click Support Zone to repair your phone...

    You must have locked bootloader bcz he will tell you that your system is modified

    I can't do that. My phone has currently no ROM installed. Installation of a ROM gave errors, so now I'm trying to get back to stock firmware, but that also gives errors.

    PC Companion only detects your phone when it is booted in Android (not in flash, fastboot or CWM mode). So I can't fix it like that.
    1
    With the phone disconnected, open PC Companion, go to support zone and choose "Phone/Tablet software update". A small window will open saying that no phone/tablet were detected. In this window, click in "repair my phone/tablet" and follow the instructions...
    1
    Ok, now I'm trying to to lock my bootloader again and am stuck there. When I try to lock:

    Code:
    fastboot oem lock

    then it just shows a new line with "..." and nothing else. It is stuck there for 10mins now. I've also tried:

    Code:
    fastboot oem lock begin

    but it is also stuck at "...". I've tried to unlock it again (which worked perfectly), but it seems that it can't be relocked.

    Any suggestions?