Database Develop

Modify init.rc to add a2sd partition

Hello,
I'm looking for explanation of how to auto-mount the a2sd (ext3) partition.
My rom is a simple rooted stock rom and so the init.rc is not already modified, so anyone could help ?
Best regards,
rXp>!<

As it happens, I've done just that recently:
http://forum.xda-developers.com/showthread.php?t=934777

I should have tried different words in my search ^^
Thank you for the link. Little follow-up question... can I extract the init.rc and put it in my phone without installing all over again ?

Short answer: no
Besides, you don't have to re-install your setup to use it, just flash the boot image, followed by DTA2SD and you're away.
Edit: Assuming your ROM is FRG83G anyway, I don't know if it'll work with other versions.

Rusty! said:
Short answer: no
Besides, you don't have to re-install your setup to use it, just flash the boot image, followed by DTA2SD and you're away.
Edit: Assuming your ROM is FRG83G anyway, I don't know if it'll work with other versions.
Click to expand...
Click to collapse
I have the FRG83(D) Stock.

Hmmm.
Well, given it's only stock rooted, I would use the OTA file to get on FRG83G then re-root with SoC... least then I know it will work, since that's what I based it on.

I use the http://forum.xda-developers.com/showthread.php?t=714184 rom.
So I tried to search but I didn't find how to update my rom already rooted ^^ because he hasn't upload the update.

Yeah you wont be able to update that one with the OTA file.
However, there is a changelog at the bottom that says it's already got the A2SD stuff there. Just install DT-A2SD and you're away.

Didn't see the changelog... but A2SD is on my phone already ! But I can't see the partition from the phone (root explorer).

A2SD doesn't create the partition, that's down to you. You can do it from recovery (after backing up your SD card), or you can do it on the fly using GParted Live CD.

I wanted to say that A2SD is up and ready. Partition is good and all the applications are on it and it works. But the partition is not auto-mount.

If it's not auto-mounting it kinda wont work?
It's mount point is /system/sd

But I still can't see it :/
Sent from my Nexus One using Tapatalk

If you run a2sd check it should say what it thinks the mount point is and if all is well

There is the check:
sh-3.2$ su
sh-3.2# a2sd check
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[ ] Creating /cache/dc
[ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
[ ] Starting Apps2SD Check Program.
[ ] Checking for ext partition
Darktremor 2.7.5.2 Apps2SD Status Report
===================================================================================
Legend: [*]=Setting is correct
[!]=Setting is correct, but not optimal.
[X]=Setting is incorrect and needs to be fixed or option is not available.
===================================================================================
Block Device - [*] Found
- [*] /dev/block/mmcblk0p2
EXT Partition - [*] Mounted
Mount Point - [ ] /system/sd
Partition Type - [*] EXT3
Support EXT2? - [*] Yes
Support EXT3? - [*] Yes
Support EXT4? - [X] No
Apps - [ ] Linked to SD Card.
[ ] No Apps2SD Flag File not found.
[*] Programs run from SD card
To run from internal storage, type a2sd remove
Private Apps - [ ] Linked to SD Card.
[ ] No Apps2SD Flag File not found.
[*] Private Programs run from SD card
To run from internal storage, type a2sd remove
Dalvik Cache - [ ] Symbolically Linked.
[ ] Dalvik to SD flag file found.
[*] Dalvik runs from SD card
To run from internal storage, type a2sd nocache
To run from /cache partition, type a2sd cachepart
Swap - [ ] Partition not present or no swap support.
[*] Swap does not start.
ZipAlign - [*] Not running at boot.
To activate it, type a2sd zipalign
Dalvik Heap(MB) - [*] 32m
Low Memory
Killer Settings - [*] 1536,2048,4096,4096,5120,15360
Note: Values are in pages.
1 page = 4KB memory.
Values represent the following:
1st number = Foreground App
2nd number = Visible App
3rd number = Secondary Server
4th number = Hidden App
5th number = Content Provider
6th number = Empty App
[] For a list of commands that you can use with Apps2SD
Type: a2sd help
sh-3.2#
Click to expand...
Click to collapse

[ADDON][ARC/ARC S] BootSounds for CyanogenMod/MiUI ROMS [v01]

[ info ]
so guys here is a small update.zip to flash on ur CM or MIUI ROM to enable bootsounds!
the sounds will be played during bootanimation!
i have tested this to work on latest CM7 [ARC] and it should work on other devices as well...
Users of my kernel (DooMKernel for CM7/MIUI [ARC/PLAY]) need not bother with this as my kernel already has this inbuilt
[ how to install bootsounds ]
just flash the provided update.zip via CWM5 recovery and reboot device to hear "DROIDDD"!!!
[ how to change bootsounds ]
u can surely have ur own music/file played during boot
for this just replace the file /data/local/android_audio.mp3 with ur own file
[ how to disable bootsounds ]
remount /system as RW
open RootExplorer and modify /system/build.prop
at the end of the file will be
Code:
ro.config.play.bootsound=1
just replace the 1 with 0 to disable the bootsounds!
save file and reboot
[ download link ]
DooMLoRD-BootSounds-CM7-v01-ENABLER.zip
[ additional info ]
this should work on any Andorid device which has CM/MIUI
just replace the update-binary and correct the updater-script syntax for ur device
[ references/sources ]
This is based on the files/info posted at:
How to add a bootsound to CyanogenMod

nice one! thanks man.

Always good stuff from Mr Doom... Thanks so much

Thanks for this.

drm keys help

[ ------------------------------------------------------------ ]
[ Backup TA v9.7 for Sony Xperia ]
[ ------------------------------------------------------------ ]
[ 1. Backup ]
[ 2. Restore ]
[ 3. Restore dry-run ]
[ 4. Convert v4 backup ]
[ 5. Quit ]
[ ------------------------------------------------------------ ]
Please make your decision:[1,2,3,4,5]?2
=======================================
RESTORE
=======================================
When you continue Backup TA will perform a restore of a TA partition
backup. There will be many integrity checks along the way to make sure
a restore will either complete successfully, revert when something goe
wrong while restoring or fail before the restore begins because of an
invalid backup. There is always a risk when writing to an important
partition like TA, but with these safeguards that risk is kept to an
absolute minimum.
Are you sure you want to continue?[Y,N]?Y
Waiting for device...OK
=======================================
CHOOSE BACKUP TO RESTORE
=======================================
[1] TA-backup-20151108.084721.zip
[Q] Quit
Please make your decision:1
Are you sure you want to restore 'TA-backup-20151108.084721.zip '?[Y,N
=======================================
EXTRACT BACKUP
=======================================
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: backup\TA-backup-20151108.084721.zip
Extracting TA.blk
Extracting TA.img
Extracting TA.md5
Extracting TA.serial
Extracting TA.timestamp
Extracting TA.version
Everything is Ok
Files: 6
Size: 2097244
Compressed: 123825
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
COMPARE TA PARTITION WITH BACKUP
=======================================
OK
=======================================
BACKUP CURRENT TA PARTITION
=======================================
dd: can't open '/sdcard/revertTA.img': No such file or directory
=======================================
PUSH BACKUP TO SDCARD
=======================================
5036 KB/s (2097152 bytes in 0.406s)
=======================================
INTEGRITY CHECK
=======================================
FAILED
*** Restore unsuccessful. ***
Press any key to continue . . .

Your Windows version?
Have you correctly set up drivers?

Fail to backup TA - fail to install recovery

Hi,
I need help for backup TA and install TWRP recovery.
I have a Xperia SP Jelly 4.3 firmware 205 rooted, locked bootloader (unlock allowed), and want to use flashtool to save TA partiton and install TWRP (no recovery installed yet).
I have installed all drivers, Pc companion off, antivirus off, Sony USB cable, windows 10 x64.
Impossible to save TA with Backup-TA (I read the entire thread in developpement section and download/tried all the solutions there. As I am not allowed to post there, I post here). Here is the error :
Code:
=======================================
FIND TA PARTITION
=======================================
[COLOR="Lime"] Partition found![/COLOR]
=======================================
BACKUP TA PARTITION
=======================================
[COLOR="Red"]dd: can't open '/sdcard/backupTA.img': No such file or directory[/COLOR]
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup does not match TA Partition. Please try again.
*** Backup unsuccessful. ***
Even in flashtool, can't save TA nor install TWRP
Code:
27/059/2016 21:59:30 - INFO - <- This level is successfully initialized
27/059/2016 21:59:31 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
27/059/2016 21:59:31 - INFO - Executing search strategies to find proxy selector
27/059/2016 21:59:31 - INFO - No proxy found for IE. Trying next one
27/059/2016 21:59:31 - INFO - No proxy found for firefox. Trying next one
27/059/2016 21:59:31 - INFO - No proxy found for java. Trying next one
27/059/2016 21:59:31 - INFO - Syncing devices from github
27/059/2016 21:59:32 - INFO - Opening devices repository.
27/059/2016 21:59:32 - INFO - Scanning devices folder for changes.
27/059/2016 21:59:39 - INFO - Pulling changes from github.
27/059/2016 21:59:40 - INFO - Quietly closing devices repository.
27/059/2016 21:59:40 - INFO - Devices sync finished.
27/059/2016 21:59:40 - INFO - Loading devices database
27/059/2016 21:59:40 - INFO - Loaded 91 devices
27/059/2016 21:59:40 - INFO - Starting phone detection
27/059/2016 21:59:46 - INFO - [COLOR="Lime"]Device connected with USB debugging on[/COLOR]
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Connected device : Sony Xperia SP[/COLOR]
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Installed version of busybox : BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary[/COLOR].
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Android version : 4.3 / kernel version : 3.4.0-perf-g4c8352f-00775-g89dacae / Build number : 12.1.A.1.205[/COLOR]
27/059/2016 21:59:46 - INFO - Checking root access
27/059/2016 21:59:46 - INFO - [COLOR="Lime"]Root Access Allowed[/COLOR]
27/059/2016 21:59:52 - INFO - Begin backup of /dev/block/platform/msm_sdcc.1/by-name/TA
27/059/2016 21:59:52 - ERROR - [COLOR="Red"]Erreur when doing raw backup[/COLOR]
27/000/2016 22:00:36 - INFO - Now plug your device in Fastboot Mode
27/000/2016 22:00:40 - INFO - Device disconnected
27/001/2016 22:01:21 - INFO - [COLOR="Lime"]Device connected in fastboot mode[/COLOR]
27/001/2016 22:01:33 - INFO - [COLOR="Lime"]Selected kernel (boot.img or kernel.sin): C:\Users\Someone\Downloads\twrp-3.0.2-r12-boot-huashan.img[/COLOR]
27/001/2016 22:01:33 - INFO - Flashing selected kernel
27/001/2016 22:01:33 - INFO - sending 'boot' (12253 KB)...
27/001/2016 22:01:33 - INFO - [COLOR="Red"]FAILED (remote: The Device must be rooted first)[/COLOR]
27/001/2016 22:01:33 - INFO - finished. total time: 0.007s
27/001/2016 22:01:33 - INFO - FASTBOOT Output:
sending 'boot' (12253 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
27/001/2016 22:01:33 - INFO - Please check the log before rebooting into system
I don't understand what is missing, can't find any solution that worked...
Thanks for any clue.

In this thread (where I am not allowed to post yet), I tried every solutions people thought about, but none worked for me. By using Backup-TA-9.11 method and tips, I have even though be able to pass one more step by doing this :
unplug SD card
replace 'sdcard/backupTA.img' by '/storage/emulated/0/backupTA.img' in backup.bat script
Click to expand...
Click to collapse
Then, where I was stuck in first step because of that :
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
dd: can't open '/sdcard/backupTA.img': No such file or directory
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup does not match TA Partition. Please try again.
*** Backup unsuccessful. ***
Click to expand...
Click to collapse
I eventually reached that (in green) until a new error (in red):
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
PULL BACKUP FROM SDCARD
=======================================
remote object '/storage/emulated/0/backupTA.img' does not exist
*** Backup unsuccessful. ***
Click to expand...
Click to collapse
backupTA.img file DOES exist on my phone, and it's not empty (about 2 Mo), script created it well !
I assume there an issue with adb 'pull' command in line :
tools\adb.exe pull /storage/emulated/0/backupTA.img tmpbak\TA.img
Click to expand...
Click to collapse
Here is where I am now, looking for a solution to make 'pull' command work...
Thanks for help !

Problem solved for Backup-TA-9.11 method.
unplug SD card
then replace these lines in backup.bat script :
tools\adb.exe pull /sdcard/backupTA.img tmpbak\TA.img
tools\adb.exe shell su -c "%BB% dd if=!partition! of=/sdcard/backupTA.img
tools\adb.exe shell su -c "%BB% md5sum /sdcard/backupTA.img
Click to expand...
Click to collapse
By
tools\adb.exe pull /storage/emulated/0/backupTA.img tmpbak\TA.img
tools\adb.exe shell su -c "%BB% dd if=!partition! of=/storage/emulated/0/backupTA.img
tools\adb.exe shell su -c "%BB% md5sum /sdcard/backupTA.img <-- this one unchanged !!!!
Click to expand...
Click to collapse
Don't ask me why, I really don't know, I assume it is because of the way each command uses path...
Problem with Backup-TA-9.11 method solved, still remains flashtool ones !
Just to check, please tell me if the backup zip file contains the right files :
TA.blk (1Ko)
TA.img (2048 Ko)
TA.md5 (1Ko)
TA.serial (1Ko)
TA.timestamp (1Ko)
TA.version (1Ko)

Glad to hear that you've solved the TA partition backup problem.
For flashing twrp recovery you need to root your phone first as stated in your flashtool log. And the easiest way to root the stock firmware is by using "towel root" app (just Google it and download the apk then install and root your phone by touching the lamda icon).
Sent from my Xperia SP using Tapatalk

Phone IS rooted from the beginning, like I said.
Installing flashtool 0.9.18.6 instead of 0.9.22.3 solved problem. Flashtool 0.9.22.3 have never worked well in my case.

I still have the problem as during integrity check it said "backup does not match ta partition" . i am using xperia SP(rooted) with locked bootloader and unlocking allowed.

[ROM] MM M1D63X ext 4 Rooted + Frankenlenok Kernel

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, thermonuclear war,
* or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point
* the finger at me for messing up your device, I will laugh at you.
*/
I've made a very fast rom, without a lot of stupid apk and with ext4 system for modifing /system.
You must say thanks to other people, I'm only a stupid "aggregator"....
But thanks also to @Cameo164, after his experience i've made a more little system.img, changing the partions size.
- Download my rom, unzip
http://www.mediafire.com/file/ke5h46vy86o23tl/DF0.1.zip
- Reboot into fastboot
- Install this Recovery (you'll find also here: http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 )
fastboot flash recovery path/to/twrp-3.0.0.img
- Reboot into recovery and Make a backup of your Rom/data/system with this recovery!!!! It's very important!
- Wipe cache and data via recovery, reboot into bootloader
- Install my boot.img
fastboot flash boot boot.img
- Go to this thred ( http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 ) and follow the steps 4-15 and then come back here
- Then:
fastboot flash system systemimageresized.img
- Reboot recovery and install supersu: Wear-SuperSU-v2.67.zip (you'll find in my zip)
- Restart system and wait..........
- Don't care for the google play error on your smartwatch, if you have
- Enable adb debug under dev options on your watch, you can also enable before paring, pushing the hardware button for about 2 seconds
- Pair with your phone
- Install busybox (you'll find in my zip)
adb install busybox.apk
- Install advanced settings for wear http://forum.xda-developers.com/android/apps-games/advanced-settings-t3341722
adb install com.sssemil.advancedsettings.apk
It's very usefull for change the screensaver brightness and other things
- Install Kernel Auditor http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
adb install KernelAudiutor4Wear.apk
For enable/disable cores and other things
- on your smartwatch if you have issue, reboot and clear data to google.play. framework (with advanced settings), reboot again
This rom is without a lot of things (like lg wathfaces, tutorial.apk and other things that i don't remeber, i'm sorry).
I use other watchfaces (with facer, this is mine: https://www.facer.io/watchface/hLzCJbTR3Z?draft=true )
Don't ask for add apks, or other things, thank you!
I suggest disable with advanced settings under apps also Bug report sender com.google...wearable.bugreportsender
Remember:
Don't change kernel or rom because you'll corrupt the new ext4 partition and you'll lose your data.
In any case before make a backup,
So, when you'll change rom/kernel you must install again the right kernel and the right rom.
If you have adb error ($ADB_VENDOR_KEYS is not set; try 'adb kill-server'), from recovery:
On your pc search adbkey.pub
cd user/.android
adb push adbkey.pub /data/misc/adb/adb_keys
You must say thanks to:
For stock Image thanks to @intersectRaven and also @vt0r http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
For This great Kernel thanks to @dirtyhank http://forum.xda-developers.com/g-watch-r/development/kernel-frankenlenok-t3342054 (look at the last page)
windroid toolkit http://forum.xda-developers.com/showthread.php?t=2499926
@Chainfire
@suleymanovemil8
@Xmaster24
@Grarak
@dirtyhank
@Cameo164

Changelog
I've uploaded my things.

Hi, thanks for your work, but for me restoring your system in twrp fails. It show's me an "ERROR: 255" close to the end. I re-downloaded the backup files, so that I can be sure that the files aren't damaged, but still no luck. I'm using the twrp.img you provided and did it like you described.
And btw. When I'm right, it should be called "adb push" not "adb pull".

http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Did you mount system in recovery?
Or try installing before leedroid rom.
Yes... is push! I'm sorry!

dettofatto said:
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Or try installing before leedroid rom.
Click to expand...
Click to collapse
Yes I did. But it's not important if I did it, because TWRP does it before restoring anyways.
What difference would it make if install leedroid rom before restoring, when TWRP formats /system before restoring your backup ?

If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.

dettofatto said:
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
Click to expand...
Click to collapse
To have ext4 I don't need to install a non-mm rom like leedroid's. I can just format /system to ext4 in TWRP.
Yes I have read it. The file that causes problems is "/system/usr/icu/icudt55l.dat". I removed it from the backup file and pushed the new file to the watch. And now the restoring works. But I ended up with a bootloop (tried with SuperSu flashed & without SuperSu). I don't know if it's because I removed the file or if it has any other reason.
Thanks for trying to help me.

Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...

dettofatto said:
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
Click to expand...
Click to collapse
Yeah I waited 30 minutes, rebooted, waited another 30 minutes and again, again...
The bootanimation I see on watch is in the attachments but because the watch screen is too small there's only "ndroi" instead of "android" visible. And there's that darker font shadow, like a fade-out animation which is going through continuously.
I know that I can't just delete one file, but with that file I can't even restore the backup.
Then I get this error :
Code:
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/")
item name: '/usr/icu/'
dir
==> extracting: /system//usr/icu/ (mode 40755, directory)
==> setting perms: /system//usr/icu/ (mode 40755, uid 0, gid 0)
Restoring SELinux context u:object_r:system_file:s0 to file /system//usr/icu/
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/icudt55l.dat")
item name: '/usr/icu/icudt55l.dat'
reg
==> tar_extract_regfile(t=0xb56a9300, realname="/system//usr/icu/icudt55l.dat")
==> extracting: /system//usr/icu/icudt55l.dat (file size 23068784 bytes)
FAILED RESTORE OF FILE i: /system//usr/icu/icudt55l.dat
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/411KPFX0122123/DF/system.ext4.win'
Fehler während der Wiederherstellung. *should be "Error during restore process" in english
Prozess extractTarFork() endete mit FEHLER: 255 *should be "Prozess extractTarFork() ends with ERROR:255" in english
I:Failed to reset capabilities of /system/bin/run-as binary.
Can you send me the file icudt55l.dat from your running watch and then I can try replacing the file in the backup?

I'll send you icudt55l.da after, when I come back at home. But is very strange...
Anyone has this issue?

icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat

dettofatto said:
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
Click to expand...
Click to collapse
I tried everything I'm able to do : First pasting your new icudt55l.dat file into the backup, just gives me the same error as before. Then I tried restoring the backup without the icudt55l.dat file and push the file with adb push to /system/usr/icu, just gives me a "no space left on device error" and at last I tried to extract the system.ext4.win file on the watch with adb shell instead of twrp, this gives me a "no space left on device" error too, but it seams that I does it anyways. But still stuck on bootanimation. I just can't get this rom to work on my watch :|

After I'll try tu upload another backup...

Ok i've created a system.img_sparsechunk1 flashable via fastboot
Backup everything.
Then download: http://www.mediafire.com/file/d3yo1opb4i7j7at/system.img_sparsechunk1
Reboot into bootloader and:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash system system.img_sparsechunk1
Flash also (I don't know if is necessary for you, but you must use mine boot.img) boot.img http://www.mediafire.com/file/w11byay60nwy5xb/boot.img
fastboot flash boot boot.img
Reboot into recovery and
Wipe data, davlink and cache
Reboot
How I've obtained this system.img_sparsechunk1?
I've extracted my system.img with: dd if=/dev/block/mmcblk0p19 of=/sdcard/system.img
but when i reflashed via fastboot I had an error because was bigger than system partition.
So i've compressed with SparseConverter v1.0.1 http://forum.xda-developers.com/showthread.php?t=2749797
to correct size: sparseconverter /compress system.img .\ 2684354560
and I've obtained the righht system.img
I hope...
In any case i've reflashed on mine and is ok

Thanks a lot for your hard work but my watch still refuses to flash the system -.-
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.288s]
sending sparse 'system' 1/2 (252175 KB)...
OKAY [ 8.280s]
writing 'system' 1/2...
FAILED (remote: size too large)
finished. total time: 8.651s
I have tried it with the latest fastboot version for windows and linux too, but both fail on "size too large". I have even downloaded SparseConverter myself, decompressed the "system.img_sparsechunk1" to "system.img" and then compressed it back into two 100MB and one 61MB sparsechunk files. Still fastboot gives me the "size too large" error.
I can flash the stock "M1D63X_system.img" successfully and it boots too.

I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe

dettofatto said:
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
Click to expand...
Click to collapse
I tried your fastboot version, but it happens the same :
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.332s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.711s

Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)

dettofatto said:
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
Click to expand...
Click to collapse
I don't have any ideas too, I would be very good if anyone else could try your rom and tell if installing and booting works. Then we would know if it's my watch's or my' fault or the rom's fault.

System uncompressed extracted: http://www.mediafire.com/file/g481ae7m3ayrjmb/systemuncompressed.zip
New Backup from System:
http://www.mediafire.com/file/4jc5a31xe2insc6/TWRP.7z
May be is my rom