• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

while flashing the boot.IMG from harmonia after installing harmonia might be applicable along the lines of how let's say my HTC one v does,I'm not thinking it will work the same way guurak. however there could be something to the idea if its not something else.
 
Curtis1973 said:
while flashing the boot.IMG from harmonia after installing harmonia might be applicable along the lines of how let's say my HTC one v does,I'm not thinking it will work the same way guurak. however there could be something to the idea if its not something else.
Click to expand...
I meant flashing the boot.img from the Harmonia zip to the boot partition with adb or Terminal Emulator.
 
Okay installed part_13_cwm_9_21_02_09.bin and got a little further with harmonia, but still didn't finish because of the previously mentioned boot issue.

2012-09-21%2021.57.09.jpg


I just performed a nandroid restore on with the newer CWM and did not get a factory restore this time.
 
MacFett said:
Okay installed part_13_cwm_9_21_02_09.bin and got a little further with harmonia, but still didn't finish because of the previously mentioned boot issue.

2012-09-21%2021.57.09.jpg


I just performed a nandroid restore on with the newer CWM and did not get a factory restore this time.
Click to expand...
same happened to me
 
landonh12 said:
So dont restore from the nandroid backup i made?
Click to expand...

I think you will be ak restoring the nandroid backup. I did some more testing, and it looks like a copy/paste error that made me think the partition wasn't restored. After doing my test again, but paying better attention, I think we're good.
 
giantpune said:
I think you will be ak restoring the nandroid backup. I did some more testing, and it looks like a copy/paste error that made me think the partition wasn't restored. After doing my test again, but paying better attention, I think we're good.
Click to expand...


Im not running the newer recovery that was included in the installer. Im running the one in the faq.
 
As soon as I get done with what i am doing I will be messing with it more, GP thinks he figured out the issue, in the meantime I am trying to wipe and pull a fresh boot image with the update.
 
I typed that error message into google and it shows a bunch of places where that error has reared its ugly head on other devices. There are 2 different fixes that get mentioned over and over again, but neither of them dealing with the recovery app. If we try both of those fixes and neither one works, then we can start blaming the recovery.

The first fix was to replace "write_raw_image("/tmp/boot.img", "boot")," with the path to the block device. So ours would be /dev/block/mmcblk0p9. The second fix said to use a different update-binary program inside the zip. If it turns out that neither of those fix it, I have an idea where to start looking in our recovery.



EDIT:
I'm reading the source for the recovery program now. The nandroid backup code uses a different method than the install.c file to find the partitions belong to which block devices. install.c is using mtd_find_partition_by_name(), which gets its list of partitions from the kernel via /proc/mtd. Our kernel doesn't list any partitions through that interface, so it won't work. I think you'll have to specify the block device in the rom install file to write to the boot and recovery partitions.
 
Does anyone have Drew's email address? I know someone said they were going to PM him, but he might not check this board at all.

Giantpune's been making great progress, but it would be nice to have two minds working on it.
 
giantpune said:
I typed that error message into google and it shows a bunch of places where that error has reared its ugly head on other devices. There are 2 different fixes that get mentioned over and over again, but neither of them dealing with the recovery app. If we try both of those fixes and neither one works, then we can start blaming the recovery.

The first fix was to replace "write_raw_image("/tmp/boot.img", "boot")," with the path to the block device. So ours would be /dev/block/mmcblk0p9. The second fix said to use a different update-binary program inside the zip. If it turns out that neither of those fix it, I have an idea where to start looking in our recovery.



EDIT:
I'm reading the source for the recovery program now. The nandroid backup code uses a different method than the install.c file to find the partitions belong to which block devices. install.c is using mtd_find_partition_by_name(), which gets its list of partitions from the kernel via /proc/mtd. Our kernel doesn't list any partitions through that interface, so it won't work. I think you'll have to specify the block device in the rom install file to write to the boot and recovery partitions.
Click to expand...


Leslie ann, try setting that in the rom and see what happens
 
MacFett said:
Does anyone have Drew's email address? I know someone said they were going to PM him, but he might not check this board at all.

Giantpune's been making great progress, but it would be nice to have two minds working on it.
Click to expand...

I messaged him yesterday on Android Central where he is active but he has not responded.
 
The one is the FAQ is the most current one that I've seen giantpune post in this board with the exception of the version he wrote the installer for. I have not included the installer version - I'm still not even sure how to use it, and until we've the aforementioned bugs ironed out I don't plan to just yet. But we'll be there soon. However, if there is a more recent version, I will gladly link to it (but be sure to note whether or not it is the installer one).
 
giantpune said:
I typed that error message into google and it shows a bunch of places where that error has reared its ugly head on other devices. There are 2 different fixes that get mentioned over and over again, but neither of them dealing with the recovery app. If we try both of those fixes and neither one works, then we can start blaming the recovery.

The first fix was to replace "write_raw_image("/tmp/boot.img", "boot")," with the path to the block device. So ours would be /dev/block/mmcblk0p9. The second fix said to use a different update-binary program inside the zip. If it turns out that neither of those fix it, I have an idea where to start looking in our recovery.



EDIT:
I'm reading the source for the recovery program now. The nandroid backup code uses a different method than the install.c file to find the partitions belong to which block devices. install.c is using mtd_find_partition_by_name(), which gets its list of partitions from the kernel via /proc/mtd. Our kernel doesn't list any partitions through that interface, so it won't work. I think you'll have to specify the block device in the rom install file to write to the boot and recovery partitions.
Click to expand...

Checking a CyanogenMod CWM-flashable ZIP from my Galaxy Tab, the boot.img is written like this as nearly the last step in the updater-script:

assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
delete("/tmp/boot.img"));
show_progress(0.100000, 0);
unmount("/system");

Some of the other CyanogenMod CWM-flashable ZIPs I have around just simply do this:

package_extract_file("boot.img", "/dev/block/mmcblk0p5");
show_progress(0.100000, 0);
unmount("/system");
 
ktb83 said:
Checking a CyanogenMod CWM-flashable ZIP from my Galaxy Tab, the boot.img is written like this as nearly the last step in the updater-script:

assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
delete("/tmp/boot.img"));
show_progress(0.100000, 0);
unmount("/system");

Some of the other CyanogenMod CWM-flashable ZIPs I have around just simply do this:

package_extract_file("boot.img", "/dev/block/mmcblk0p5");
show_progress(0.100000, 0);
unmount("/system");
Click to expand...

Hmm, that may be the solution we end up using. Good find!
 
Im getting a permissions denied whenever I try and run the installer, But I am using su on my terminal emulator. I already have the recovery from the .bin, just thought Id say that because I kinda wanted my MSL xD

OHH! And Id also like to know where I can acquire a copy of Harmonia. I cant find one anywhere O.O

Thanks Guys(:
 
You must log in or register to reply here.
Back
Top Bottom