How to debug the "data" restore procedure (from a backup) in CWM-based recovery?
I'm using the ClockworkMod-based recovery.img for Galaxy S (GT-I9000) from http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages (the last one, from 2013-04-06), on two such devices.
I've created a backup on one of them, copied the clockworkmod/ directory to the other one, and want to restore it there.
But an error happens when restoring data. (The log and the backup files were attached to a bug report there.) There is no information in the error message or the log what the cause of the error is.
(My main system is CyanogenMod 10.)
I could try to figure out what is wrong and debug the restore process myself, but for this, a prerequisite is for me to be able to study the source code of the restore program and to run it under tracing/debugging tool (the first simplest thing would be for me to run it under strace, in an emulator of Android perhaps). Since the Replicant project is known to pay special attention to being free software, I'm expecting to have the freedom to study the source code and to debug. But unfortunately, this is not very clear how to do: the page where I've got the recovery.img from (http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages) doesn't point me to the source code of the image, and doesn't explain how I can peek inside the image on another system for studying it.
So, my question is:
How to study and how to trace/debug the restore procedure in a CWM-based recovery? (How to peek inside the recovery.img? How trace the restore procedure with strace? How to run the restore procedure on another system--like a GNU/Linux one--to test it?)
I'm using the ClockworkMod-based recovery.img for Galaxy S (GT-I9000) from http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages (the last one, from 2013-04-06), on two such devices.
I've created a backup on one of them, copied the clockworkmod/ directory to the other one, and want to restore it there.
But an error happens when restoring data. (The log and the backup files were attached to a bug report there.) There is no information in the error message or the log what the cause of the error is.
(My main system is CyanogenMod 10.)
I could try to figure out what is wrong and debug the restore process myself, but for this, a prerequisite is for me to be able to study the source code of the restore program and to run it under tracing/debugging tool (the first simplest thing would be for me to run it under strace, in an emulator of Android perhaps). Since the Replicant project is known to pay special attention to being free software, I'm expecting to have the freedom to study the source code and to debug. But unfortunately, this is not very clear how to do: the page where I've got the recovery.img from (http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages) doesn't point me to the source code of the image, and doesn't explain how I can peek inside the image on another system for studying it.
So, my question is:
How to study and how to trace/debug the restore procedure in a CWM-based recovery? (How to peek inside the recovery.img? How trace the restore procedure with strace? How to run the restore procedure on another system--like a GNU/Linux one--to test it?)
No comments:
Post a Comment