Database Users

Renaming HtcContacts.apk

I installed the MoDaCo Custom Rom r3.1 and it's perfect except for 1 tiny little thing: the default HTC contacts app has been renamed from 'People' to 'HTC People' (actually, from 'Contacten' to 'HTC Contacten' in my localized version of MCR).
I decided to unpack the HtcContacts.apk using apktool and replace all occurrences of 'HTC People' with just 'People'. Then, I repacked everything into an .apk and signed it with a key. Then, I pushed the new HtcContacts.apk to /system/app/ while in recovery mode. However, the new contacts app does not show up after booting ... might this be caused by using a random key for signing? If so, how should I sign this apk to make it work?

The whole thing should have been signed with test keys when it was de-odexed. The only other thing is that it could have been re-packed wrong, or you need to update the packages.xml.

I'm quite new to this odex stuff, so I don't know much about it. I'm usually 'just' a developer.
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?

No, I mean don't sign it again after you edit it.
-------------------------------------
Alias::NeO on HTC Desire

Well, that's what I tried first. To be more concise:
1. I flashed MCR r3.1 to my device and kept it in recovery
2. I took the HtcContacts.apk from the update zip that I used in step 1
3. I used apktool to unpack it, since all resources were in binary format in the apk itself
4. I edited the appropriate resources
5. I repacked everything into a fresh HtcContacts.zip
6. I pushed the new HtcContacts.zip to /system/app/
7. After the very first boot of MCR r3.1, the Contacts app was invisible in the app drawer
Since that obviously didn't work, I decided to sign the apk before pushing it to /system/app/ but that yielded the exact same result.

Do I need to sign the APK with the same key that is used for the other apks in /system/app?

alias_neo said:
No, I mean don't sign it again after you edit it.
Click to expand...
Click to collapse
You must resign files after any change made to them. If we wouldn't have to do it, then whole signing idea would have no sense.
franklinvv said:
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?
Click to expand...
Click to collapse
franklinvv said:
Do I need to sign the APK with the same key that is used for the other apks in /system/app?
Click to expand...
Click to collapse
Yes, and they were probably signed using testsigner tool. Did you used testsigner last time? If not, then try it.
Also looking into logcat would be helpful - to be sure, that problem is related to signing.

I'm not sure where to find the testsigner that you mention ... but I used some testsign.jar that I found somewhere. Using that jar, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse

Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?

franklinvv said:
Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?
Click to expand...
Click to collapse
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.

Brut.all said:
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.
Click to expand...
Click to collapse
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?

Are you flashing or pushing the file?

franklinvv said:
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?
Click to expand...
Click to collapse
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.

eViL D: said:
Are you flashing or pushing the file?
Click to expand...
Click to collapse
I'm pushing it ... I will try flashing it now. (Never knew that there really was a difference between those 2 methods.)
Brut.all said:
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.
Click to expand...
Click to collapse
I'm trying that right now.

Argh ... whatever I do, my update-script keeps yielding syntax errors!
This is all that I have in the update-script:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Click to expand...
Click to collapse
I put the HtcContacts.apk in a /system/app subdir.
When I try to flash the zip, it fails with 'E:Syntax error in update script', and /tmp/recovery.log tells me:
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-signed.zip
Opening update package...
I:Update file path: /sdcard/update-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
I:Verified META-INF/com/google/android/update-script
I:Verified system/app/HtcContacts.apk
Installing update...
line 1: syntax error at '0.1'
E:Syntax error in update script
Installation aborted.
I:Set boot command ""
Click to expand...
Click to collapse
I have NO idea what I'm doing wrong.

Try: "show_progress 0.100000 0". But I don't know much about update.zip creating.

If I try that, it tells me:
line 1: syntax error at 'show_progress'
Click to expand...
Click to collapse
Edit: I'm all out of ideas ... I think I'll have to give up.
Edit2: After playing around with the update-script and trying stuff with the show_progress lines, I finally removed the lines and that worked after the 2nd try.

Unfortunately, my own HtcContacts.apk STILL doesn't work ...
I/PackageManager( 328): /system/app/HtcContacts.apk changed; collecting certs
E/PackageParser( 328): Package com.android.htccontacts has no certificates at entry AndroidManifest.xml; ignoring!
I/PackageManager( 328): Failed verifying certificates for package:com.android.htccontacts
Click to expand...
Click to collapse
So the APK does need to be signed before putting it in the update.zip?

you don't need:
set_perm_recursive 0 0 0755 0644 SYSTEM:app

Thanks, I changed the update-script accordingly.
However, I ended up with this:
I/PackageManager( 190): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 190): Package com.android.htccontacts signatures do not match the previously installed version; ignoring!
Click to expand...
Click to collapse
And after the second boot, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
So, I'm stuck now ... I have the feeling that Paul signed everything in the MoDaCo ROM with an unknown key?

How to make a update.zip help!!!!!!!!!!!!!

i want to know the easiest way to make a update.zip

asad510 said:
i want to know the easiest way to make a update.zip
Click to expand...
Click to collapse
I am not sure how "easy" it is, but here goes:
Well basically an update.zip is a zip! use your favorite zip program to open/edit/compress it.
When flashing through the recovery the META-INF\com\google\android\update-script from the zip file is run.
Try to look at update scripts of existing updates to learn how to use it. You can also look here: http://forum.xda-developers.com/showthread.php?t=641223
Finally, recovery won't flash zips which have not been signed. You need to sign it with the testkey.
I don't remember where I got the procedure from (probably somewhere here on the forums) - but using the files from here:
http://www.multiupload.com/0GB7Y94BGD
You need to run something like this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 x.zip x_signed.zip
which will sign x.zip and create x_signed.zip.
Note that the zipalign in the above package is not relevant in this case.

.rc files

can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk

alex1301 said:
can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk
Click to expand...
Click to collapse
Hi, here are the contents of the folder:
http://i.imgur.com/bxbK3.png
And attached is latest boot.img (kernel 3.0.8 from dzo's Aurora ICS) and the decompressed files if you need that...

i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel

alex1301 said:
i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel
Click to expand...
Click to collapse
Can you post the un packed files? I could try to repack them

I think I know what the problem is, you need to have mkbootimg... Here it is, put it in /bin and then rerun the repack script
EDIT: for some reason, attachments are always corrupt... but here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=475249&d=1293574570

http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back

alex1301 said:
http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back
Click to expand...
Click to collapse
Here it is.
But your error was because you probably didn't have mkbootimg on your system

are you ready?

alex1301 said:
are you ready?
Click to expand...
Click to collapse
I've posted the boot.img right now
I hope there's nothing wrong with it... to repacked the files, I put all the files from your both zip files in one folder, then run repack-bootimg.pl script over boot.img-kernel as argument, is this correct?

yes man thanks. i will give you credits in the rom section.

do you know if i can use the updater script form aurora?

alex1301 said:
do you know if i can use the updater script form aurora?
Click to expand...
Click to collapse
I guess yes, the script, if I'm not wrong, only formats partitions and copies the ROM files to the appropriate locations and sets permissions... try using it, or post the ROM here and I'm sure someone can work it out if it doesn't work...
Cheers
Sent from my U8800

i will release it in a couple of minutes. so when the script is not working, someone other can fix it

have i also to replace the updater-binary?

I don't think that's needed, the binary I assume is the same for different ROMs, only the script changes... but I would to be sure good luck!
Sent from my U8800

i can't sign this bull**** apk

alex1301 said:
i can't sign this bull**** apk
Click to expand...
Click to collapse
What do you mean? I was hoping for a release today :-( good luck man...
Tomorrow I'll try posting from desire z... can you post a link for a guide? Thank you...
Sent from my U8800

[Utility] Android boot Manager APK

Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.

I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.

atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?

lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.

New version won't install on Kit Kat

PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.

atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt

Are extracted files accessible in file system? I can't find them

levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM

PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.

atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?

levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...

It seems that the image you want to unpack it is not an android image.

atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk

Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Possible way to self-sign Recovery and Rom's on S7, Just need some help.

Hey, I noticed while looking through the Stock Firmware AP file, that in meta-data/fota.zip there are .jar files that have to do with package signing. Only issue is that the zip is password protected. If someone has the Compute power and skills to decrypt a zip and look at the jar files and ****, maybe we could find a way to sign our own TWRP recoveries and roms. Just a thought, i'll post a link to the fota.zip file i was talking about in a bit if anyone wants to take a crack at it. (Google drive is taking forever to upload cause of AT&T's ****ty DSL speeds, sorry)
Download Link: htt*ps:/*/drive.*google*.com/file/*d/0B9tb-svjqaVD*b3Y0V0tXR3drSzA/vie*w?usp=sharing (Remove all *'s from link, stupid 10 post until you can post links limitation)
Thanks,
Lavavex

Did you saw this Thread?
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
About fota.zip...
Did you heard about plain text attack?
In few Seconds... minutes done... no password required but you can unpack.
Best Regards

Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards

adfree said:
Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards
Click to expand...
Click to collapse
Which will allow unpacking of the above zip? I thought it needed a zip password.

osm0sis said:
Which will allow unpacking of the above zip? I thought it needed a zip password.
Click to expand...
Click to collapse
We never found the Password... but for Decryption you need only these 3 Keys...
They can be easily found in few Minutes... with the right Tool...
Code:
2b4d493c
6142b289
1b7024aa
Here Key0 Key1 Key2 for Samsungs fota.zip...
This is really no rocket science...
Simple read about plain-text attack...
You can see all filenames...
You can see all filesizes etc...
Many files are floating around the Internet... to create ZIP for attack...
Then result is in few Minutes possible... :angel:
Use these 3 Keys in Tool:
Code:
Advanced Archive Password Recovery
And try self to unpack...
Best Regards
Edit 1.
Screenshot added...
Then maybe more clear...
Trial Version have mabye limtations... but to see it work... it is enough to play with trial.

@adfree or to anyone who can answer.
Quick question, what are the legal limitations to what is going on here? I may or not have a file from inside the fota.zip, but will sharing it put me in the legal wrong? If it is within the legal boundaries, I'd be happy to upload it for anyone to take a look at, but I don't want to land on the wrong side of the law by doing so. Please do let me know, as this is the most exciting development we've had when it comes to bootloader unlocking in a while. Also, it seems as though we can't view the entirety of the contents of the fota.zip with the trial version of the zip extraction tool mentioned in this thread, so if someone with more knowledge about this can confirm we could unlock our bootloaders with the contents of the zip (based on what is currently known about this), I'd be happy to bite the bullet of paying for the premium version given we can do this within the boundaries of the law.
Thanks.

1.
Maybe you can answer your question self...
Samsung PROTECTED this ZIP with password.
2.
IMHO it is Kernel related...
Yeah I know... Boot is every irritating...
But it is not sboot.bin related...
3.
About decrypting all files...
There are floating around Command Line Tool...
Code:
pkcrack
Try to Google it...
I have not tried...
I am 1 click Button user...
Best Regards

zipdecrypt from the pkcrack package plus those 3 keys worked flawlessly. :good:
Edit: Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.

the password for that zip is fotatest1234

Correct. All fota zips passwords are fotatest1234

Drdra3 said:
Correct. All fota zips passwords are fotatest1234
Click to expand...
Click to collapse
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?

Delgoth said:
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?
Click to expand...
Click to collapse
Presumably what I previously said still stands:
osm0sis said:
Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.
Click to expand...
Click to collapse