3 stages should be continued to change a current .apk record:
- Firstly, do the genuinely wanted adjustments inside the .apk file
- Sign the .apk
- Next, introduce the .apk on the gadget
- Change the asset in the .apk
- Open apk file with WinRAR (if that doesn’t work, rename the document expansion .apk to a .zip file)
- Next, change the asset in the file as wanted (packager apparatuses permit to change documents without the need to separate the file)
- Whenever you’re finished with your changes, you need to take care of the mark documents that are essential for the .apk:
- Inside the chronicle, go to organizer META-INF
- Erase the current *.RSA and *.SF records
- Thereafter, the accompanying screen capture shows the substance of the META-INF envelope in a .apk document:
- Presently the chronicle can be shut.
Sign the .apk
When fostering an application in Eclipse, the ADT (“Android Developer Tools”, the augmentation to Eclipse that upholds advancement for Android) deals with marking the application with a default testament, before introducing it on the gadget.
Android doesn’t permit the introduction of an application (app) that isn’t agreed upon.
That is agreeable, however, with the accompanying depiction, everyone can sign an application.
Marking the .apk is done in 2 stages:
a) make the declaration
b) sign the .apk with the made testament
- The two stages are finished with orders on the order line
a) Generate a testament
In case you’re working in a Java climate, you have the JDK on your document framework.
- The JDK accompanies an instrument to oversee endorsements: the key tool.
- You can think that it is in the …/container envelope of your JDK establishment.
- Presently you can produce a declaration utilizing underneath order. \
- Notwithstanding, before executing it, kindly take a look at the notes underneath, to adjust the boundaries
keytool.exe – genkey – v – keystore – assumed name – sigalg MD5withRSA – keyalg RSA – keysize 2048 – legitimacy 1000
- Kindly note that you need to adjust a portion of the boundaries of the above order to your necessities:
Here, you can give a discretionary name to your Keystore.
The name that you give here will be the name of the Keystore-record that will be made.
The record will be made in the current catalog.
Here also, you can give a discretionary name to the assumed name.
- Firstly, it is intended for you to remember it.
- The nom de plume is the comprehensible name of the authentication which will be made and put away in the Key store.
- This is the number of wanted days.
- You can enter any number you wish.
- I figure it ought to be sufficiently high to remain generally safe with lapse.
keytool.exe – agency – v – Keystore mykeystore – false name myalgias – signaling MD5withRSA – keyalg RSA – key size 2048 – legitimacy 10000
- While executing the order, you’ll get a few prompts on the order line, requesting secret phrase, username, association, city, and so forth
- You can enter any discretionary information here, you just need to make a memorable point the secret phrase.
- thereafter, you’ll see the produced Keystore document on your record framework in the current registry (from where you’ve executed the order)
- Presently you can continue with marking the .apk utilizing the recently made authentication.
b) Sign the apk
- Before marking the .apk document, you need to ensure that there are no endorsements accessible in the .apk.
- This is portrayed in sync 1 above.
- For marking a document, we utilize the jarsigner device, which is given JDK, and which can be found in a similar area to the key tool.
- The accompanying order is utilized for marking an apk.
jarsigner – verbose – sigalg MD5withRSA – digestalg SHA1 – Keystore
- If it’s not too much trouble, note that you need to adjust a portion of the boundaries of the above order to accommodate your necessities:
- Here you need to enter the name that you have given in the past stage a)
- To keep the order line short, I prescribe briefly duplicating the Keystore document to a similar area where you’re executing the order.
- Here you need to enter the name of the apk record which you need to sign
- Furthermore, to keep the order line short, I prescribe briefly duplicating the .apk document to a similar area where you’re executing the order.
- Here you need to enter the name of the assumed name that you’ve given while producing the authentication
jarsigner – verbose – sigalg MD5withRSA – digestalg SHA1 – Keystore mykeystoremyApp.apkmyalg
- Once you have executed the order, you can look at the outcome inside the .apk record:
- Open the document, go to the envelope …/META-INF and check if the records CERT.RSA and CERT.SF has been made.
3. Introduce the apk on the gadget
- Presently that the .apk document is marked, and you can introduce it on your gadget.
- For Android applications the establishment is done on the order line, utilizing the ADB order.
ADB represents Android Debug Bridge
- adb.exe is a piece of programming that associates the PC with the Android gadget.
- It permits admittance to the gadget, permits trigger tasks, moves records, and so forth
- To introduce the .apk on the gadget, you need to associate the gadget to your PC by employing a USB link,
- Then, at that point, execute the following order
- To keep the order line short, you can briefly duplicate the obj file to a similar area where you’re executing the order.
- The outcome ought to be an “achievement” message on the order brief.
- If not, any of the past advances might have fizzled.
- You can discover the application in the applications organizer of your cell phone.
You can also read- The Best Channel to Watch Movies