FORUMS

IonVR Coming Soon, HTC M9 Dev Edition Gets Android 5.1 – XDA TV

The HTC M9 Developer Edition has received Android 5.1. That and … more

Android 5.1.1 Omni ROM For Motorola Xoom

Back in Feb 2011, the Motorola Xoom became the first device to be sold with Android 3.0 … more

CleanSlate Brings Fingerprint Scanner Mod to HTC One M9+

Work of XDA Recognized Developer tbalden, CleanSlate custom kernel for the HTC … more

Sunday Debate: Which Factors Caused HTC’s Woes?

Join us in a fun Sunday Debate on HTC’s situation. Come with your … more

[Q] Error 0017 flashing stock firmware

19 posts
Thanks Meter: 4
 
By goocreations, Junior Member on 15th March 2014, 08:12 AM
Post Reply Subscribe to Thread Email Thread
16th March 2014, 10:19 PM |#21  
dunc4n88's Avatar
Senior Member
Thanks Meter: 221
 
More
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
 
 
17th March 2014, 03:40 PM |#22  
OP Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by dunc4n88

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?
17th March 2014, 05:07 PM |#23  
dunc4n88's Avatar
Senior Member
Thanks Meter: 221
 
More
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
The Following User Says Thank You to dunc4n88 For This Useful Post: [ View ]
17th March 2014, 06:34 PM |#24  
OP Junior Member
Thanks Meter: 4
 
More
Thanks, I appriciate it.
24th March 2014, 05:49 PM |#25  
Junior Member
Thanks Meter: 0
 
More
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.
21st September 2014, 11:26 PM |#26  
Junior Member
Thanks Meter: 0
 
More
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.
17th February 2015, 12:33 AM |#27  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by hardwarematik

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
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes