[DRIVERS]Latest HTC Drivers [4.2.0.001] - EVO 4G General

Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001
BMP Drivers are the same for both sets of drivers.
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
Instructions:
Determine if your system is 32-bit or 64-bit
Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
Disable any antivirus program(s) present
Run both files downloaded above (the BMP.msi and the HTCDriver file)
Re-enable your antivirus program(s)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x86 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
Updated on 11.28.12
HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
HTCDriver_3.0.0.023.msi
Click to expand...
Click to collapse
------------
MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.
After you download each file, make sure to check that the md5sum matches what is given.
Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]
Click to expand...
Click to collapse
How to check the md5sum of a file:
Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.
After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"
Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"
{
"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"
}
Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.
Open a terminal and type the following ("fileNameHere" must include the extension):
Code:
$ cd path/to/download/folder
$ md5sum fileNameHere
Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.

Awesome, man! Thanks!

Bump

Updated Drivers to version 4.1.0.001.
Two important note, from here on out I will also be including fast links for the Sync setup files (HTC Sync and Sync Manager), as well as a SyncManager_XXXXX_STRIPPED.exe which will literally be ONLY the Sync Manager program, all drivers stripped out from it (as in, it won't install any drivers, hence a much smaller file size).
You will now be able to find the FULL setup files for HTC Sync and Sync Manager inside the Original HTC Sync Folder of the linked mediafire folder in the OP. This will provide a much faster download if you do want to install either one, rather than a capped speed download from the HTC site itself.
Well here's the changelog
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe

Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe

Download link not working

Related

[APP][22-01-09]OEM Version Checker (Display version numbers of OEM Packages)[UPDATED]

Hi,
This is a little app I made to display the version numbers of the OEM Packages either of a dumped ROM rather than searching for them in the rgu (Desktop Edition) or what are the versions of the OEM Packages are installed on their phone (PPC Edition). Hope this app is useful.
{
"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"
}
​
Desktop Edition
Description:
OEM Version Checker Desktop Edition is useful for cooks who wants to see the version numbers of the OEM Packages of a dumped ROM so that they can compare the versions for different OEM packages before selecting the package to include into the Kitchen before cooking
How to install and use:
Download and Unzip the OEM_Version_Checker.zip onto you desktop
Run the app and click on the Select OEM Folder button to specify where all the OEM Packages can be found
Click on Get Version to display the version numbers. Then you can click on Output Report to export the results into a text file
​
Pocket PC Edition
Description:
OEM Version Checker PPC Edition is useful for anyone who wants to know what are the version numbers of the OEM packages that are installed in your phone
How to install and use:
Download and unzip the OEM_Version_Checker_PPC.zip and copy the exe file into your phone OR you can just download the Cab installation file created by Garymeg attached and install it your your phone
Run the app from the file explorer and all the version numbers will be displayed. If you have installed the cab file by Garymeg, a shortcut link will be automatically created in the Programs folder
Click on Menu for more options
​​
Nice!
I'm using it already
Vic5870 said:
Hi,
This is a little app I made to display the version numbers of the OEM Packages of a dumped ROM rather than searching for them in the rgu. Hope this app is useful.
Click to expand...
Click to collapse
Nice vic !
I will make it into my custom kitchen.
Thanks for this tool, looks interesting!
Pocket PC editiion added
Added Pocket PC Edition. Read first post for information.
Awesome work! This will come in super handy.
How to have OEM Packages from ROM,
for example: RUU_Diamond_HTC_WWE-ME_2.03.456.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
mobiAnd said:
How to have OEM Packages from ROM,
for example: RUU_Diamond_HTC_WWE-ME_2.03.456.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
Click to expand...
Click to collapse
You gotta dump the ROM with a kitchen first then use the tool to open the OEM folder.
Cab Installer for PPC
Hi I have put together a cab file for the PPC Version
garymeg said:
Hi I have put together a cab file for the PPC Version
Click to expand...
Click to collapse
Thanks! I will add it into first post
Thanks! Nice work!
It goes perfect!
Thanks a looooott!
Create this tool for WM Standard

[APP] findutils 4.2.33 (updatedb / locate) for Android

Introduction
As I like to stay connected via Putty to my Android phone, from time to time I missed the functionality of updatedb / locate that I so got used to within Linux environment.
I've decided to cross compile the findutils package (I couldn't get the latest version 4.4.2, but an older before, 4.2.33).
Screenshot
You can see the updatedb command followed by some locate commands.
{
"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"
}
Installation
Busybox is required.
1. Copy the archive onto your /sdcard/ folder.
2. mount your /system folder as read-write
3. cd /system/
4. tar xf /sdcard/findutils-4.2.33.tar.gz
It is mandatory that you are inside /system/ folder when you extract the archive.
Then you have to create the database (using updatedb script). It will take a bit of time - but not too much.
Then you can use the locate command giving any part of a file name that you can remember, you can also use wildcards!
Observations
1. No integration with cron / etc. If you know your updatedb database is out of date, rebuild it using "updatedb"
2. Busybox comes with a /system/xbin/find command. The trouble with it is that it doesn't support the fstype argument, and thus, updatedb cannot prune some standard file system type paths. However, the bundled package here comes with its own find utility which unpacks into /system/bin/find.
3. Busybox is required for sort / sed, but updatedb script is patched to use the /system/bin/find (its own find executable) instead of the default busybox one.
4. My phone did not have an /etc/mtab file (list of mounts which mount is supposed to update whenever something happens). Thus, there is a line in the updatedb script which recreates that file on each updatedb invocation (mount > /etc/mtab). If you phone / tablet has it, please modify updatedb script and remove the mount command.
Download
Use it at your own risk!
findutils-4.2.33.tar.gz
This is great! Thanks for your work!
I hope that there will be a file manager for android which uses updatedb/locate to index/search files in the future, that would be sooooo awesome!
Don't know about other software that searches - but it would be nice too.
Maybe I can create something, but I'm sure there are others more integrated - such as looking in SMSes or in mails too, etc.
nice! find takes for ever lol now i have locate!
Any chance of getting the code. Did you create your own Android.mk? Did you use the FindUtils make?
When I run updatedb, I get these errors:
/system/bin/find: /preload: Value too large for defined data type
/system/bin/find: /storage/sdcard0: Value too large for defined data type
/system/bin/find: /system: Value too large for defined data type
/system/bin/find: /data: Value too large for defined data type
yelkarama said:
When I run updatedb, I get these errors:
... <snip>
/system/bin/find: /data: Value too large for defined data type
Click to expand...
Click to collapse
I also get this error
This doesn't work. Might have worked a couple years ago before 4.x Android...
Use something like es file Explorer
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
viulian said:
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
Click to expand...
Click to collapse
Thanks for your efforts, I guessed it needed a rebuild from a google, but given how long ago you posted this I didn't think it would happen. Looking forward to the update!
Sent from my GT-N7100 using Tapatalk
Please upload the new build
viulian said:
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
Click to expand...
Click to collapse
Hi
Please upload the new built binaries.
Thanks
Don't work with Oreo. Please make a update.

[DRIVERS] Latest HTC Drivers [4.2.0.001]

Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001
BMP Drivers are the same for both sets of drivers.
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
Instructions:
Determine if your system is 32-bit or 64-bit
Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
Disable any antivirus program(s) present
Run both files downloaded above (the BMP.msi and the HTCDriver file)
Re-enable your antivirus program(s)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x86 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
Updated on 11.28.12
HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
HTCDriver_3.0.0.023.msi
Click to expand...
Click to collapse
------------
MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.
After you download each file, make sure to check that the md5sum matches what is given.
Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]
Click to expand...
Click to collapse
How to check the md5sum of a file:
Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.
After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"
Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"
{
"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"
}
Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.
Open a terminal and type the following ("fileNameHere" must include the extension):
Code:
$ cd path/to/download/folder
$ md5sum fileNameHere
Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.
Updated 3.6.13
Changelog:
Added HTC BMP USB Driver for Windows 64 bit
Added HTC Driver 4.0.1.001.exe AND extracted HTCDriver_4.0.1.001.msi
there are available new drivers, 4.0.1.002
Re: [DRIVERS] Latest HTC Drivers [v4.0.1.001]
orymd said:
there are available new drivers, 4.0.1.002
Click to expand...
Click to collapse
Check the link in my sig
But thanks for the heads-up, OP updated
Updated OP with md5 checksum's and how-to
Bump
Thank you for posting this, been looking for it a while.
No problem
Updated Drivers to version 4.1.0.001.
Two important note, from here on out I will also be including fast links for the Sync setup files (HTC Sync and Sync Manager), as well as a SyncManager_XXXXX_STRIPPED.exe which will literally be ONLY the Sync Manager program, all drivers stripped out from it (as in, it won't install any drivers, hence a much smaller file size).
You will now be able to find the FULL setup files for HTC Sync and Sync Manager inside the Original HTC Sync Folder of the linked mediafire folder in the OP. This will provide a much faster download if you do want to install either one, rather than a capped speed download from the HTC site itself.
Well here's the changelog
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Thank you
prboy1969 said:
Thank you
Click to expand...
Click to collapse
Yup :thumbup:
Thx for all
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
about drivers for shift
nice postings, grettings.

[TOOL] Zipster Tool - Extract, Compress and sign.

{
"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"
}
Hi guys, I've made a batch command program to Archive and Extract files to zips. Why would you use this? Well, back at the time where I was porting backwards and forwards, I worked in a certain folder, then I just have to click on my batch command and it automatically get's zipped.
How does it work:
Extracting: Place your zip in /EXTRACT/INPUT and your file will be extracted to /EXTRACT/OUT
Compressing: Place your zip in /COMPRESS/INPUT and your file will be compressed in the folder /COMPRESS/OUT
Signing: After you Compressed your files, you just select sign and it will be named " updated-signed "
Note:- At the moment the tool and it's folders need to be ran from the desktop!
Ui:
It's a very basic command prompt.
What I'm working on:
I am going to add the following features:
The ability to Root and Unroot Ace
The ability to Odex and Deodex Ace
The ability to Add scripts to Ace.
The ability to be ran from anywhere not just the Desktop.
Installer and windows Ui.
ADB Tools
Sign Apk's
This shall later on be renamed to something like : The Ace All-In-One tool.
------------------------------------------------------------------------------------------------
Translations:
Porteguese:
Translated and modded by Danilo_Pascal
Download Zipster Porteguese
------------------------------------------------------------------------------------------------
Have fun!
Thanks to my dad for helping me with Windows Scripting and Programming, lolz.
Changelog:
27/03/13
Initial release.
28/03/13:
Added capability to sign zip files.
Changed name to: Zipster Tool
Can i use this with wine in linux ?
Mm7 said:
Can i use this with wine in linux ?
Click to expand...
Click to collapse
Yes.
useful for porting roms..nice idea..thanks and subscribed
The Alchemist said:
useful for porting roms..nice idea..thanks and subscribed
Click to expand...
Click to collapse
Thanks!
Updated the thread, renamed and added the ability to sign. I am thinking of making a Galaxy Ace only tool that can Root and everything in one, and perhaps a universal one like this one is at the moment.
PulseDroid said:
Thanks!
Updated the thread, renamed and added the ability to sign. I am thinking of making a Galaxy Ace only tool that can Root and everything in one, and perhaps a universal one like this one is at the moment.
Click to expand...
Click to collapse
Something like nexus phones have?
root toolkit
Sent from Ace on JB (4.2.2)
n0p3zz said:
Something like nexus phones have?
root toolkit
Sent from Ace on JB (4.2.2)
Click to expand...
Click to collapse
Yep.
Hey PD.. I cant sign my update.zip
when I try to sign the update.zip it show the line like this >> 'java' is not recognized as an internal or external command, operable program or batch file.
look at the attachment. can you help me with this, please :angel:
isafarady said:
Hey PD.. I cant sign my update.zip
when I try to sign the update.zip it show the line like this >> 'java' is not recognized as an internal or external command, operable program or batch file.
look at the attachment. can you help me with this, please :angel:
Click to expand...
Click to collapse
Need to download the Java Development package (JRE)
Translation added.
delete, Problem solved

APK Tool For Windows

{
"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"
}
APKTOOL FOR WINDOWS
First and foremost thanks to @iBotPeaches for his dedication to Apktool!
Because I can double-click more accurately than I can type, I made this up to avoid having to use command line and speed up modding the couple of apks that I try to keep up on. Maybe it'll help a few others speed up their process too.
Now, this is a Windows based GUI for Apktool. No command line needed. That said, you should be very familiar with already using Apktool via command line so you know the process that it follows and the corrective measures needed should errors pop up. You need to have the exact same setup as Apktool (Java in your environment path and current Java version AND relevant frameworks installed via apktool!! ). All that this does is provide a simple Windows style menu for the process. You can very easily update apktool.jar as @iBotPeaches updates it. Also, if you would like to add any switch to the decompile or compile command other than the typical (which is what I used) you can just modify the corresponding .bat file located in SupportFiles that APKTool For WIN calls on.
See the attached screenshots in the following post for the easy to follow layout and it's capabilities. It will install frameworks/etc, decompile, compile (with or without original manifest and meta-inf), sign (with testkey or your personal one), and display an apktool log.
As this directly uses apktool.jar, it will have the same quirks/issues such as this current one:
10/18/2016 - for apktool v2.2.1 regarding v2 signed apps - LINK​
V4 - As I was posting this, I noticed there was an update to apktool.jar (v2.2.1) which I updated the file to reflect. I modded several apps with the earlier version but only attempted two apps with the updated one (didn't see any issue with either app but I'm still on MM). I haven't looked more in depth at this V2 signed apps issue yet to see if I can modify the signing.bat to account for it (it's 230am). I will update it if there is.
V5 - (1) Updated apktool.jar to 2.2.2 if you haven't already yourself and (2) added java version info in your log file on Decompile routine to help identify a beginners issue on determining whether or not you have java installed in your path
Copy apks to the "APKs_To Decompile" folder.
Copy your framework-res, twframework-res, systemUI as needed to the folder "Frameworks".
Install frameworks.
Running the APKTool For WIN.exe select Install Frameworks
Decompile.
Select Decompile .apk
Choose your apk.
Decompiled app will be in the Decompiled folder.
Compile.
Select Compile
Choose your app to compile.
(One backup will be automatically created if there is an existing one to be safe in the decompiled app's folder)
Choose to copy the original manifest and meta-inf if desired
Compiled apk will be in the Compiled folder
Sign.
Select Sign APK
Choose the apk to sign.
Choose to sign with the testkey or with your personal key (help file is included in the zip for initial setup for using your own key)
Signed apk will be in the Signed folder
APKTool Log
If an Error message is displayed after decompiling or compiling you can check the log.
It's also beneficial to clear the log sometimes.
reserved for future use, faqs, issues
hmmm......after being away for a while i'm checking back to see if anyone had issues with trying to use this....and.......
not a single issue/question/comment with nearly 100 downloads. you guys are GOOD!!! (unless y'all think it's pointless and are being too kind to comment )
in the next few days, i'll use it a bit more in depth with the updated source and see if anything needs tweaking
Great tool !! I like it , this is solve my problems.
thank you so much , please keep it up.
Small update - V5
1. Updated to apktool 2.2.2 in case you haven't already done so yourself.
2. Added your java version info to the log generated when you run a Decompile routine to help beginners identify whether or not java is in the required path

Categories

Resources