creating update.zip for fonts applying - Hero, G2 Touch Q&A, Help & Troubleshooting

Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks

---

The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'

---

l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?

---

I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip

---

it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file

---

btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?

---

btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder

---

after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted

---

First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip

---

I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.

---

First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?

---

Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.

---

riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted

---

You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.

---

Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?

---

Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.

---

riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$

---

You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.

---

riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?

---

i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?