Related
I have been toying with the idea of making a theme. Sounds like fun and the How To's here are really thorough (by the way, I appreciate that, those things must have been quite the labors of love).
As you can tell from the thread title, my OS of choice is obviously Ubuntu. The autosign tool sounds pretty convenient, but I notice it is for Windows. I've searched a bit, but honestly I am getting tired of thumbing through thread after thread looking for the answer and was hoping for a friendly nudge in the right direction.
Anyway, long way around to these questions:
1, when I re-sign an apk, do I use test-keys, do I create my own key, or do is that something JDK will create for me to use?
2, I don't want to create a theme that makes people need to wipe before switching, the template is up to date on the How To thread? Are there templates for JF ADP1.1, and maybe even RC8 as well? Or was there a thread I could read about taking the necessary parts of JF's update and building a template of mine own from that?
3, To actually resign an apk, you have to edit some hex code right? If there truly is NO tool for Linux, I could use some directions on where to find how to manually sign a file. Then hopefully I can find / convert / create a tool in Linux to handle the dirty work for me.
I guess this is what I get for coming in so late into the game.
Also, I am curious if anyone else creates themes in anything other than Windows... any *nix creators out there?
ok, first off to resign an apk or a zip you dont have to do any hex editing at all, in fact, to make a theme you dont have to do any hex editng.
2nd, use my default themes as in the stickies as a template to build your theme, it will not wipe.
3rd to resign in linux, which I haven't done, you will probably need the original signing tool which can be found in jf's recovery.img .zip[ he provided a while ago. I believe it is stickied on android development.
This is the command to resign them
java -jar testsign.jar >inputfile> <outputfile>
Hope this helps
Stericson
Thanks for the super quick reply
Ok, I'll give a search for "testsign.jar", that should get me in the right direction. Once I have that I guess it is time for some experimenting. It shouldn't be hard to develop a shell script that takes every file of xxx type, from a directory and then pass them as values to the testsign.jar app one by one. I had a shell script do something like this to rename all of my photos.
I resign the apk and zip files then.
Thanks Stericson, now I am off to find that testsign.jar, make sure I have the up-to-date default themes, and play around a bit.
EDIT:
SignApk.jar is a tool included with the Android platform source bundle.
testkey.pk8 is the private key that is compatible with the recovery image included in this zip file
testkey.x509.pem is the corresponding certificate/public key
Usage:
java -jar signapk.jar testkey.x509.pem testkey.pk8 <update.zip> <update_signed.zip>
Click to expand...
Click to collapse
This is what I need isn't it? I thought that sounded familiar, I had this downloaded from the whole "let's explore how to root my phone" process.
oh yea, ooops, that is right...sorry I have a custom version of the tool I use. Sowwy.
But that is right.
that cmd line will sign both apks and zips
Stericson
Enlighten me please... I want to edit the keymappings and define my own symbols and whatnot. I already found the init.etc/keymaps but how would i go about rebuilding the rootfs.img?
Thx.
How are you accessing rootfs.img? If you simply mount it as a loopback device in Linux, I don't think you have to rebuild it. Thor_Asgard listed the necessary commands needed to mount rootfs.img, if you don't know how to mount it.
How did I get into it? WinImg, or something like that. Looks like I gotta boot up some linux. HMM I could just use Rhobuntu to do it couldnt i?
Thanks for the link
andershizzle said:
How did I get into it? WinImg, or something like that. Looks like I gotta boot up some linux. HMM I could just use Rhobuntu to do it couldnt i?
Thanks for the link
Click to expand...
Click to collapse
Is it an "official" keymap update? Is it more complete or better than what is currently being used? Or even maybe a keyboard that has not been mapped at all yet? Would you like to put it in the main build, so that everyone else can use it? Contact babijoee or phhusson, they have access to update the main rootfs git!
Oh no I'd be doing this because my T Mobile TP2's ALT key doesn't work so I'd be swapping shift + letters for symbols instead of capital letters as well as including my own custom symbols like a < and > so i can text <3's to my girlfriend HAHA.
But yeah. It wouldn't be like an official thing, just tinker with which extra symbols i want on the keyboard such as < > { } [ ] | \
Hi!
I would like to make keymap for Finnish layout (only difference are FN-key combinations really). I already found the mentioned files from rootfs.img, but have a few questions:
What's the difference between rhod100* and rhod210* files?
Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?
Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!
EDIT:
andershizzle said:
Oh no I'd be doing this because my T Mobile TP2's ALT key doesn't work so I'd be swapping shift + letters for symbols instead of capital letters as well as including my own custom symbols like a < and > so i can text <3's to my girlfriend HAHA.
But yeah. It wouldn't be like an official thing, just tinker with which extra symbols i want on the keyboard such as < > { } [ ] | \
Click to expand...
Click to collapse
Did you manage to create or modify files in the img file? If so, could you advise me how to do it?
"What's the difference between rhod100* and rhod210* files?"
They're just different layouts for different models. Rhod210 is based on one of the North American models, I forget which; Sprint or T-Mobile I think. The rhod100 layouts are the European ones.
"Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?"
You have to compile it to produce rhod210_microp-keypad.kcm.bin and put that into the rootfs. The tool to do this is only available inside the Android source. I have a compiled version of it here for Linux 32-bit, I can send you the tool or you can send me the .kcm and I can compile it for you, up to you.
"Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!"
If you want to submit it for general use, yes, you have to name it something else. You should also submit it with a patch for the file 'init' in the rootfs.img image; look down the bottom and you can see how the keymap stuff actually works. The files are not actually used under their 'rhod*' names, if you specify in the kernel command line that you want a particular Rhodium keymap, it is copied to the filenames which are actually used. So add a little bit for your layout that corresponds to the others in there.
"Did you manage to create or modify files in the img file? If so, could you advise me how to do it?"
On Linux, you can just mount the rootfs.img file:
mount -o loop rootfs.img /mnt/some_mount_point
then edit stuff, then umount it. Dunno how to do it on Windows.
AdamWill said:
"What's the difference between rhod100* and rhod210* files?"
They're just different layouts for different models. Rhod210 is based on one of the North American models, I forget which; Sprint or T-Mobile I think. The rhod100 layouts are the European ones.
"Only place I found relevant things to change, is rhod210_microp-keypad.kcm file; what do I have to do to get the changes in use when I put the modified file back in place and into my Touch Pro 2?"
You have to compile it to produce rhod210_microp-keypad.kcm.bin and put that into the rootfs. The tool to do this is only available inside the Android source. I have a compiled version of it here for Linux 32-bit, I can send you the tool or you can send me the .kcm and I can compile it for you, up to you.
"Do I need to name it something different after modifications?
I'd like to submit it to general use when I'm done, so if you could just help me with these, I'd really appreciate it!"
If you want to submit it for general use, yes, you have to name it something else. You should also submit it with a patch for the file 'init' in the rootfs.img image; look down the bottom and you can see how the keymap stuff actually works. The files are not actually used under their 'rhod*' names, if you specify in the kernel command line that you want a particular Rhodium keymap, it is copied to the filenames which are actually used. So add a little bit for your layout that corresponds to the others in there.
Click to expand...
Click to collapse
Ok, I made some changes and renamed my new files. If you could do the compiling, I'd be very happy. I renamed them after rhod100, if that's the european model then. The attached zip contains the kcm and kl files.
Here are the rows to put in init:
Code:
elif /bin/grep -c 'physkeyboard=rhod100_fi' /proc/cmdline >/dev/null ; then
echo "USING EXPERIMENTAL RHOD100 FI LAYOUT"
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kl /etc/keymaps/microp-keypad.kl
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kcm.bin /etc/keymaps/microp-keypad.kcm.bin
cp -f /init.etc/keymaps/rhod100_uk_navi_pad.kl /etc/keymaps/raph_navi_pad.kl
If you could add these changes to the rootfs.img, I'd be very grateful!
hey good work guys! us CDMA guys have been desperatley seeking a verizon tp2 keyboard port. The symbols are way unmapped.... i only have windows. If someone could give me some instrucitons i'd happily try and help
Matt
Jekku said:
Ok, I made some changes and renamed my new files. If you could do the compiling, I'd be very happy. I renamed them after rhod100, if that's the european model then. The attached zip contains the kcm and kl files.
Here are the rows to put in init:
Code:
elif /bin/grep -c 'physkeyboard=rhod100_fi' /proc/cmdline >/dev/null ; then
echo "USING EXPERIMENTAL RHOD100 FI LAYOUT"
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kl /etc/keymaps/microp-keypad.kl
cp -f /init.etc/keymaps/rhod100_fi_microp-keypad.kcm.bin /etc/keymaps/microp-keypad.kcm.bin
cp -f /init.etc/keymaps/rhod100_uk_navi_pad.kl /etc/keymaps/raph_navi_pad.kl
If you could add these changes to the rootfs.img, I'd be very grateful!
Click to expand...
Click to collapse
How did it go? Did you get a cool rootfs.img? I need a swedish keyboard layout..
Tools needed: smali, baksmali (google them), a JDK, and an extracted factoryfs.rfs from an éclair ROM.
(If you don't have a linux machine to mount an .rfs file to a directory never forget that your device has linux on it, so it can actually mount the .rfs file to a directory)
First collect the files you need from factoryfs.rfs:
/app/AxT9IME.apk
/app/AxT9IME.odex
/lib/libXt9core.so (this is actually the same file that's inside the apk)
/lib/libDHWR.so
/framework/android.policy.odex
/framework/core.odex
/framework/ext.odex
/framework/framework.odex
/framework/services.odex
Copy all the odex files into the same directory as baksmali is. Disassemble it with:
java -jar baksmali.jar -x AxT9IME.odex
This should create an out directory, with the disassembled, and deoptimized files. Now reassemble them, with smali:
java -jar out
This should create an out.dex file. Rename it to classes.dex, and put it into the AxT9IME.apk (don't be fooled by the extension, it's a simple zip file)
Now copy the following files to your phone:
AxT9IME.apk --> /system/app
libXt9core.so --> /system/lib
libDHWR.so --> /system/lib
Remove the following files:
/system/app/AxT9IME.odex
/system/lib/libdhwr.so (this is lowercase. The above was uppercase. Case does matter!)
Now try to enable the samsung keyboard. If everything goes well then you can now use the old keyboard.
-----
Alternatively if you needed the keyboard from the XWJM8 version, you can download the result files from here: http://android.sztupy.hu/dl/SamsungKeyboardFroyo.zip
Thank you
can I use this method in order to replace framework.jar/framework.odex from another build?
JHJP4 support proper BIDI (for Hebrew/Arabic and other RTL languages)
And how do we do the opposite? Want 2.44 on eclair =)
Should work the same
omrij said:
Thank you
can I use this method in order to replace framework.jar/framework.odex from another build?
JHJP4 support proper BIDI (for Hebrew/Arabic and other RTL languages)
Click to expand...
Click to collapse
No, framework.jar is too much different between eclair and froyo. You can only port simple applications (in /system/app) this way.
dupel said:
And how do we do the opposite? Want 2.44 on eclair =)
Click to expand...
Click to collapse
It would only work if the new keyboard doesn't use anything FroYo specific (like gesture support, or enhanced multitouch support). If it does use froyo specific api functions it will break under eclair.
sztupy said:
No, framework.jar is too much different between eclair and froyo. You can only port simple applications (in /system/app) this way.
Click to expand...
Click to collapse
Both frameworks are from Froyo
just different version
JP4 framework has proper BIDI support
omrij said:
Both frameworks are from Froyo
just different version
JP4 framework has proper BIDI support
Click to expand...
Click to collapse
If framework.jar changes then all pre-optimized files (odex) have to be reoptimized (the same way as the tutorial above shows), and even after that it might not work...
hi can I ask a few questions. I don't know much about these complicated things, but I will try my best.
can we collect files you asked us from factoryfs, through root explorer.
you asked to copy file with capital letters to phone and then asked to remove same file name with small letters. can one directory have two files with same name?
and finally how would we copy files to the phone?
thanks.
Sent from my Nexus One using Tapatalk
pitsyapa said:
hi can I ask a few questions. I don't know much about these complicated things, but I will try my best.
can we collect files you asked us from factoryfs, through root explorer.
you asked to copy file with capital letters to phone and then asked to remove same file name with small letters. can one directory have two files with same name?
and finally how would we copy files to the phone?
thanks.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
You can use rootexplorer to transfer the files to /sdcard modify them on the PC, tran transfer them back from /sdcard to their location.
thanks I really appreciate your help can I ask you another simple question. I have downloaded jdk.
and installed it. how do I use these commands to disessemble, java jar. is there any special java prograame. thanks.
thanks v much. problem solved. ported urdu keyboard from eclair to jpk. thanks again.
How do I know which files from /lib do I need to replace?
I'm trying to use contacts apk from other froyo rom
So, I tried the above instructions, and all I get is errors with bksmali, but i get the out directory, then when I run smali, it get another bunch of errors, but no out.dex. Any help would be amazing.
I haven't tried any of this other than trying to just install the AxT9IME.apk which obviously didn't work. I can enable it but trying to switch to it or access its settings instantly resorts in a force closure.
What I don't think I've seen mentioned is whether or not the end result of this allows you to have both the 2.2 and the 2.1 keyboards. Could anyone clarify for me if you get both or just the 2.1 keyboard in the end?
Lastly, would it be possible for someone to write an app (downloadable via market) for this keyboard for any android version? Because that'd be pretty awesome.
It'd be nice if it didnt create an app-drawer icon, but I wouldn't mind as Go Launcher allows me to hide unwanted apps.
I honestly like the 2.2 keyboard, but the 2.1 one (with its 4 pages) has symbols in on it that I have seen no where else, which is pretty cool and why I'm wanting it.
http://bbs.gfan.com/android-575451-1-1.html
ignore the link at the top that one is mostly chinese the english version is provided hear thanks to da900
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.[/QUOTE]
please aware that this rom is only contain about 20% english , most of words are chinese
u should be able to change it to english in the language and input settings
Is this newer than the QnD 1.2.4 rom?
Look at the number lol. 1.2.11 > 1.2.4
no that one has chinese this one does to thou dnt flash nevermind
dictionary said:
Look at the number lol. 1.2.11 > 1.2.4
Click to expand...
Click to collapse
XD I was thinking 4 > 1.
here's the changelog:
MIUI 1.2.11 version update:
Phone:
Add in the phone settings to add "call from the sensors used in the process" of setting
Fix the call log to the Canadian people through IP numbers to send SMS / MMS will bring IP prefix, resulting in the issue could not be sent
Theme:
Add support for setting alarm
Ringing in the new system comes with the option "mute"
Optimize the system comes with the choice of ring tones
Repair some of the theme of the correct format does not show the problem package
System Update:
Add WIFI connection can support the Ad-Hoc (peer to peer) network
Press the Backspace key fixed the problem miscarriage of justice
Local Backup:
Installed on the sd card repair program can not be the problem with the backup and recovery
Click to expand...
Click to collapse
terrelltp said:
no that one has chinese this one does to thou dnt flash nevermind
Click to expand...
Click to collapse
What? Slow down and make sense lol. Are you saying that you screwed up, and there is next to no English in the build?
terrelltp said:
u should be able to change it to english in the language and input settings
Click to expand...
Click to collapse
i repeat :
this rom does contain 20% of english translation only !
Even you change to english language :
your 80% of menu still display "Chinese".
So, this is useless unless you understand simplified Chinese. I'll wait on g4rb4g3 to release a port.
Sent from my htc.desireZED
Weren't there language packs you could install
Sent from my HTC Vision
Device Specific Language Packs
I think that language packs are device specific.. I haven't been able to find a language pack on the net for the G2.. though I did manage to a how to guide but I'm green to this stuff..
If somebody out here is familiar with how to do this guide and create a language pack for the G2 for us.. that would be helpful.
djmcnz said:
Okay guys, there's a lot of demand for this rom and for language packs but not yet a lot of people who know how to make the packs. Whilst I set up the crowdin translation project I can not create or maintain language packs.
So, here's a summary of the instructions required to create a language pack for MIUI (indeed for any app/rom). You need a collection of tools and a little patience but the process isn't too difficult so do give it a go.
Also note that this summary includes generalisations for brevity. These instructions assume you have a deodexed rom.
Introduction
For the purposes of this post language information is stored in XML strings in files on the Android system. In the case of MIUI and these instructions we will be dealing with .apk files (applications).
Within the apk files is a resources directory (/res) and within this are various values directories, there is a default values directory (/res/values) and alternative language values directories (e.g. /res/values-DE and /res/values-IT).
If the rom is set to use it's default language it will read values from /res/values although these may NOT be in English. In MIUI, all of the common Android ASOP values in /res/values are English but the (additional) custom MIUI strings are in Simplified Chinese.
If you select a different language in the ROM than the default then the appropriate values directory will be searched. If a suitable string that matches your language selection is found in the alternative /res/values-xx directory then that string will be used instead. If an alternative does not exist then the default will be used.
Example:
Code:
/res/[COLOR="red"]values[/COLOR]/strings.xml
<stop_button_text>[COLOR="Red"]Stop[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-DE[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Halt[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-IT[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Basta[/COLOR]</stop_button_text>
In this example, if the language is set to the default the word "Stop" will be used, if it is set to German the word "Halt" will be substituted in, likewise "Basta" for Italian.
So, to add languages to a rom (or app) or to make an app multi-lingual you need to either change the default strings in /res/values/strings.xml to the ones you want to use or, and this is the preferable approach, add a /res/values-xx/strings.xml with the translations you want. The first approach will work (changing the default strings) but is not recommended because the Android Open Source Project and Android development in general, defaults to English. It's best to use the built in language substitution capabilities of Android rather than to work around them. Indeed, if the MIUI devs actually added their strings in English to /res/values/strings.xml and the Chinese equivalents in the appropriate directory this rom would already be in English!
Adding Languages
To add a translation file (strings.xml) to an apk you need to:
decode the apk
create a language directory
add the translation files
recompile the strings
add the new strings to the apk
Which all sounds a little daunting but it's really quite straight-forward, rewarding when you see the result and a good way to understand how parts of Android work. Here's how you can do it.
1. decode the apk
You will need the excellent apktool from brut.all which you can get from the link below. apktool is relatively easy to use but includes some little tricks so you will need to read the wiki and thread about it.
Do NOT just post problems about apktool if you can't get it to work. The tool DOES work so if it's not decoding (or encoding) your apps correctly then you're probably doing something wrong. If you start with this understand BEFORE you ask for support you'll get a lot more help...
apktool: http://code.google.com/p/android-apktool/
wiki: http://code.google.com/p/android-apktool/w/list
thread: http://forum.xda-developers.com/showthread.php?t=640592
Please make sure you run the following command to include the MIUI framework in apktool. You only need to do this once for each framework. If apktool works with one rom and not the next then (re)install the framework for that rom.
Code:
apktool if framework-res.apk
Where framework-res.apk is the one from the rom you are working with. Make sure apktool can find (the correct) framework-res.apk before you run this command.
This thread is not for apktool support.
Now, before you proceed, decode a simple app from MIUI (such as updater.apk) using apktool, do not make ANY changes, then re-encode it using apktool. For example:
Code:
apktool d Updater.apk ./decoded/
apktool b ./decoded/ new_updater.apk
Use the -v (verbose) flag in apktool if you have problems and need to diagnose further.
Remember, Android uses a case-sensitive file system, make sure your capitalisation is correct.
Typically you will not be able to install this apk because it is not signed so if you want to test the process further you can now just try step 5 below using the two apks you have.
2. create a language directory
Assuming you can decode/encode now, this is the easy bit. For your decoded app, navigate to the directory it was decoded in, then to the /res/ directory and simply create an empty directory for your language (e.g. /values-FR/) - use international naming conventions.
3. add the translation files
Again, not too difficult this. Download the appropriate language file for your apk from the crowdin project linked below and, using the same structure as exists in /res/values/strings.xml create a new file called strings.xml in your alternative language directory (e.g. /res/values-ES/strings.xml).
The news strings.xml may contain as many or as few translations as you like. Remember, if a translation does not exist the default value from /res/values/strings.xml will be used.
Crowdin: http://crowdin.net/project/miui-rom-translation/invite
The xml formatting and tag names need to match exactly with the default strings.xml in /res/values although the translated file does NOT need to be complete.
It is worth remembering here that unless your source apk is already translated to English then some of the default values in /res/values/strings.xml will still be in Chinese, it would pay to check these.
4. recompile the strings
Now, if you've done everything carefully and correctly this step is really easy, all you need to do is recompile the apk with apktool using the b (for Build) switch.
Code:
apktool b ./<decoded_apk_dir>/ <output_apk_name>.apk
If this throws errors or does not work then use the -v switch to turn on verbose mode and diagnose your problem. If you did the test in step #1 and it worked then any problem at this step is likely related to your news strings.xml. Back out the changes one by one until you have found the problem and try again.
If you simply can't get it to compile with your changes then try just making a single change to the default strings.xml file in /res/values and see if that works for you.
Do NOT sign the apk!
5. add the new strings to the apk
Easy. Open your new apk with a zip program (like 7Zip for Windows) and copy out the resources.arsc file in the root directory of the apk. Now take that file and copy it into the source apk from the rom overwriting the existing one. This process replaces the strings but keeps the integrity of the signatures on the files.
You can now push the modified file to your phone, replacing the stock one, reboot and you're translated. Push the file using "adb push" or copy it into place using a root file manager, do not "install" the new apk. Make sure you put it in the correct place (replace the original) and reboot.
Conclusion
This process will help you add languages to any app including those in the MIUI rom. Because it's a rom the strings are contained in many different apps as well as framework-res.apk. To completely translate the rom you will need to edit every apk that has strings in it.
You will need to do this every time an apk in the rom changes. If a new version is released and say launcher2.apk is changed but updater.apk is not, then you can retain your updater.apk but you'll need to re-edit your launcher2.apk.
When an app changes the default strings.xml may also change. In this case you will need to make corresponding changes to your translations.
Good luck and if you get really stuck there's lots of people in this that have achieved success and may be willing to help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=789566
MIUI 1.2.11 for Vision ENG
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.
ok cool so basically u made a english version for that latest update cool cool
terrelltp said:
ok cool so basically u made a english version for that latest update cool cool
Click to expand...
Click to collapse
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?
da900 said:
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?
Click to expand...
Click to collapse
i thought thats what u did isint that link u posted the english version
terrelltp said:
i thought thats what u did isint that link u posted the english version
Click to expand...
Click to collapse
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.
dictionary said:
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.
Click to expand...
Click to collapse
That's what i mean. Thanx.
lol yes i did that now
da900 said:
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.
Click to expand...
Click to collapse
WOOOO..good job . it's perfect !!!!!!!! work very well ~!! thanks a lot
Hello.
WP7DZExtract extracts every partition from DZ file and converts flash.bin to nb (opens by htcRIE).
My second tool WP7DZBuild builds DZ from partitions and their table (mb it will be not required, please pm me LG device owners).
By the way, files from that topic were extract using this tool.
Usage:
WP7DZExtract.exe input.dz output_dir, there input.dz is DZ ROM file, output_dir is directory.
In output directory will be created many files, one of them, flash.bin, is nb file, just rename it to flash.nb and open it using htcRIE or any tool.
WP7DZBuild.exe input_dir output.dz, there input_dir is directory constains flash.bin, output.dz is out file.
Note: This tools requires .Net Framework 4.0 (at least Client Profile). You can download it form Microsoft web site.
I hope it works (althrough my device is LG, but there is no way to dump or flash it's ROM). Any bugreports here.
Thanks!
I've used standart GZIPStream (works well for unpacking), but it's output doesn't equals original, i've tried to use SharpZip, DotNetZip and even gzip, but uselessly... LG Flasher doesn't work on my computer (why?), so i can't check my work, i fully hope on you, LG owners! Sorry for my english, i dislike online translators and write as i know, though my english skill is pour (too).
Very nice. Hope to get using this very soon.
Yes support for lg devices i am loving it :3 Thanks.
I will tested out.
thx for sharing
Build tool is ready!
Great work!
I'm getting a "#46 Cannot load. Invalid file format" when opening flash.nb with HTCRIE
Please post the link to your ROM, mb i broked down something while developed build tool.
Telus_LG_E900
airwa1kin7 said:
Telus_LG_E900
Click to expand...
Click to collapse
Everything works well. Mb you are using old version of htcRIE? Try to donwload most fresh. At least WP7DZExtract checks hash after unpacking and compares it with dz included, so if hash matchs file is successfully unpacked.
Screenshot
Your correct. I was using "0.5.0.12" Upgraded to "0.7.0.19" and it works.
I was able to get the LG Quantum dz and use these tools to have a look inside the rom and the registry. It makes me wish we could rebuild these roms to unbrand them.
fb401 said:
I was able to get the LG Quantum dz and use these tools to have a look inside the rom and the registry. It makes me wish we could rebuild these roms to unbrand them.
Click to expand...
Click to collapse
That's right, i wanted to build my own rom, but as i wrote above there is no rom for my device. Please test it LG owners, i want to check my gz.
WP7DZBuild
I have been working on my own encrypt/decrypt program. The decrypting is fine, however the trick is encrypting the extracted files back into a flashable image. Using GZip or Zip on linux produces a ROM that is 200 KB smaller than the original LG C900AT ROM. The LG flasher program gives the error "ErrNum 501 Load Image."
So I tried using your WP7DZBuild tool to create a ROM and it's size is 214 MB, the original ROM is ~191.8 MB. The LG flasher program does not give an error when using the ROM built with your tool, but the ROM will not flash to the phone (LG Quantum C900). The LG flasher program just sits waiting. It seems as if the recompression of the files is the key to making the build process work. The original ROM from LG contains files that are decompressable with GZip, but using GZip to recompress results in an invalid file.
I have looked at the binary file produced when using both GZip and Zip, both contain the filename which is not included in the Original ROM . Also, looking at the GZIP file format, some of the Data headers are empty in the original ROM, but both GZip and ZIP fill these fields in.
Do you guys have any ideas as to a ZIP program/library that can output a valid Zip file for inclusion in a flashable ROM that does not include the name of the file that was compressed to make the file? Maybe the original LG encryption program deletes/zeros certain fields in the Zip file header?
Also, just taking the decrypted original ROM's files while still compressed by whatever method LG used, I can create a flashable ROM (it's actually what my phone is running right now!). I'm thinking of GZipping the files and then going back and zeroing out the fields so that the data headers match the original. Maybe that will work.
Has anybody else tried to rebuild a ROM and flash it to the phone?
Everyone test on kdz g5 ?