Develop Bugs

[App] QuickCab 2.0 Cab Creation Utility (Updated: 12-25-2008)

QuickCab 2.0​
Like most people around here I enjoy customizing my phone. Problem is that copying files and applying a bunch of Registry tweaks by hand is tedious. I've built CAB files in the past but creating the INF files is an ugly process...not for the feignt of heart.
So I created a utility called QuickCab that makes creating CAB files easy. It doesn't support every possible scenario, but if what you want to do is copy files or change the registry, it works quite well. This is perfect for Themes, Ringtones, Tweaks, and Mods.
***Requires the .Net Framework 3.5 which can be found 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"
}
Changelog:
2.0
* Rewrote GUI to allow for more options and fix selection errors
* Fixed many button and selection errors
* Added Shortcut support
* Added support for Vista UAC
* Added support for compressed cabs
* Added ability to prevent uninstall
* Removed support for Setup.dll (does anyone use this?)
* Move from .Net 2.0 to .Net 3.5
1.0
* Initial Release

Hello. First off great program. However i am running vista and when trying to save it comes up with a blank screen.
also in order to select individual files i need to right click the files.
Import button on reg screen doesnt work.
keep working on it and this will turn into a great app.

great work.. will try this out this weekend...

this is very helpful. thanks

shadowmike said:
Hello. First off great program. However i am running vista and when trying to save it comes up with a blank screen.
Click to expand...
Click to collapse
I'm running Vista as well...when you save it, I assume you mean when you hit the Create button. If that's the case, it's writing the INF file and spawning CABWIZ.EXE. If you selected large files, it could take awhile. Maybe I need to put up some "wait..." notification?
shadowmike said:
also in order to select individual files i need to right click the files. Import button on reg screen doesnt work.
keep working on it and this will turn into a great app.
Click to expand...
Click to collapse
Yikes! The right-click thing really confuses me...It's a standard control that I use for the file selection. I couldn't make that happen if I tried! When you hit the Import button, do you get a window where you can select the reg file?
Anyone else seeing these issues?

it would also be very nice if it can support shortcut creation

oldsap said:
it would also be very nice if it can support shortcut creation
Click to expand...
Click to collapse
Yep! That and compression are coming in the next version.

nice tool, for sure a lot of guys will appreciate

I am new to cab creation. With cabs made with this, is the cab uninstallable? If the cab makes a registry change, does uninstalling that cab, change the registry back to its old value before cab installation?

Thanks for this I am going to use this after a Hard reset to test somethings out this weekend is going to be FUN!!!!!

Very very useful program.
Ideal for vanilla ROM lovers like me
It could be even better program if we could edit cabs, changing default directories, for instance from \window to \Storage Card

superflysocal said:
I am new to cab creation. With cabs made with this, is the cab uninstallable? If the cab makes a registry change, does uninstalling that cab, change the registry back to its old value before cab installation?
Click to expand...
Click to collapse
Sorry for taking so long to respond, had a family member die and was out with that. I'm not an expert with cabs themselves, so I don't know the answer. It'd be pretty easy to test it out though...create a registry entry and create a cab to change it. then uninstall it.

teixeirabmb said:
It could be even better program if we could edit cabs, changing default directories, for instance from \window to \Storage Card
Click to expand...
Click to collapse
Interesting idea. I've tossed around the idea of being able to load a cab up and make modifications to it. I'll probably have to work on the UI a bit first. Maybe in a couple versions from now...right now there are a couple of bugs I'm working on and supporting compression, shortcuts, and a default directory.
THANK YOU for the suggestion!

Great idea. Can't wait to test it when i great my computer back

interesting... will try this out & keep an eye out. thanks

IABovine said:
QuickCab 1.0
Like most people around here I enjoy customizing my phone. Problem is that copying files and applying a bunch of Registry tweaks by hand is tedious. I've built CAB files in the past but creating the INF files is an ugly process...not for the feignt of heart.
So I created a utility called QuickCab that makes creating CAB files easy. It doesn't support every possible scenario, but if what you want to do is copy files or change the registry, it works quite well. This is perfect for Themes, Ringtones, Tweaks, and Mods.
I plan to add support for Shortcuts in the near future. If you use this program, I'd appreciate feedback. I can't improve it without your ideas.
Requires the .Net Framework 2.0
Click to expand...
Click to collapse
It is a great application.
Just there is a problem with the registry import function: if a string value contains comma (,) then only the first item is imported, everyhting after the comma is just simply cut.
Or am I doing something wrong?
Thanks.

Thanks man, great app and works like a charm, really appreciate your work

Thanks for your effort!
I will try it on my X01HT.

Thanks. This will be very helpful to streamline setting up the phone after flashing.

I am trying to use this to cab some of the standard regedits I make, but I need a little guidance. Could someone please post an example of 1) how to change an existing registry key and 2) how to add a new one? Thanks.

[KITCHEN][ROM] >-=+ [mu] kitchen +=-<

Placeholder for the [mu] kitchen.
DOs and DON'Ts:
DON'T:
1: DON'T ask about vista support. I'm seriously allergic to that expression. Use WinXP SP2/3 and be happy.
2: If it doesn't suit your needs, don't b**** about it and just use another one.
DOs: if you like it, say thanks.
CONSTRUCTIVE criticism/suggestions: more than welcome via PM.
^.^
### Here's the link (lzma)##############
# http://www.mediafire.com/?oufm4oq9t2v #
##############################
### Here's the link (tar+bzip2)#########
# http://www.mediafire.com/?u4tj1jsnuzt #
#############################
1: .net framework 2.0 at least needed.
2: ms vb runtimes recommended.
3: BEST uncompress with 7zip (or any app supporting lzma) / WinRAR/WinZIP to c:\
4; there is no "readme", so place your RUU_signed.nbh (and Part*.raw) into the "source" folder in the kitchen,.
5: although I tried coding it as noob-proof as possible, the kitchen DOES require some minimal knowledge about the cooking/rebuilding process.
I DON'T intend to spoon-feed you, so if you want additional features, you need to seriously catch up on some reading.
This kitchen DOES need further/extended testing, but I decided to release it after several successful tests on 2 different systems.
Nethertheless, I CAN'T possibly account for the heterogeny of every system in the wild...
I could TRY coding the "perfect" kitchen, but that would be utterly pointless, since experienced chefs use their own kitchen/or don't use frontends.
6: last but not least: even though a cooking process might've been completed, give a few seconds till you move to the next step. HDD/IO bottlenecks tend to do strange things.
^.^
The mirror/kitchen link MAY be inaccessible at times. If you REALLY need access to anything hosted, leave me a PM.
I'll provide you with another (temporary) link.
# # #
20090110 edit
Will be uploading an updated version of the kitchen maybe next week.
# # #

Pre-applaud and Pre-thanking
Thank you...................................

Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^

adwinp said:
Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^
Click to expand...
Click to collapse
(pre)Thanks for sharing a probably great and useful tool !

I think it will be a great kitchen because adwinp is a very hardworking man and he reads and searches a lot.

Thanks Cyphol.
I'm honoured. Though I learned a lot from you guys.
I'm nearly done with the batch file. I'll finish and test it tomorrow.
I tried giving the end user as much control as possible, even though using just one batch.
We'll see if it works.
DOS batch coding sux.
Bash rulez.
^.^

.. [reserved] .. for private use.

The [mu] ROM is coming next.
(It might take some time for me to release a ROM worth sharing with the community. I may want to wait for the next official ROM update since I'm not really satisfied with the 1.93 base).
PLEASE DON'T ask when it might be available.
^.^
Although I respect bepe's and dutty's (DP) great work, I stick with Wally regarding protecting the ROM against disasm/copying.
Meaning: No copying protections. Feel free to do with it as you please.

I won't say thanks for this kind of Kitchen. WHAT HAVE YOU DONE???
I only want to say MARVELOUS! NICE AND CLEAN! CONGRATULATIONS.

Thanks Cyphol!
The real thanks goes to the authors of the various tools this kitchen serves as a frontend to.
I doubt this is bug-free, but I hope it will be a contribution of some sort to the community I have learned so much from.
Maybe somebody will do a much better job than I did.

Sorry,
but WinRAR says the archive is destroyed.

scorpio16v said:
[...]WinRAR says the archive is destroyed.
Click to expand...
Click to collapse
Re-download and make sure your browser doesn't screw with the file extension, it's .tbz2 (tar+bzip2) otherwise your unpacker might have issues reading it.
The Archive is fine, and adwinp: the kitchen looks extremely sexy. I'm completely new to cooking and just trying it because I want a proper JVM, but I've looked at the other kitchens, and this one is the nicest so far.
If your ROM is as hot as the kitchen, I might have found myself a new base rom

cptsunshine said:
.... otherwise your unpacker might have issues reading it.
The Archive is fine...
Click to expand...
Click to collapse
You're right.
Was my WinRAR version.
Sorry for the rumour.

scorpio16v said:
You're right.
Was my WinRAR version.
Sorry for the rumour.
Click to expand...
Click to collapse
Use 7zip for any of the archive versions.
It's a fast and free archive manager, supporting lzma.
You can still uncompress the .tbz2 archive with 7zip/winrar/winzip.

Hi adwinp,
Great tool !
Thank you very much for sharing this tool !!!
I've tried it to rebuild a .nbh with some dump files associated with a RUU_signed.nbh from a stock HTC ROM.
After the first steps, all is OK (my casserole seems to smell good ) until the Build step...
I got an abort 'BuildOS.exe ....'
any idea ?

Could you post a screenshot?
Gimme a link to the stock ROM (or tell me what version it is) and I'll check it out.

OS conflict ?
Hi adwinp,
And thanks for your reply.
So, here is what I've done :
1. Copy my 4 Part0*.raw files in y=the \source folder
2. Copy the stock RUU_signed.nbh in the same folder
Notes :
> Dump files are the parts of a french ROM from Bouygues provider avalaible here : http://dl.free.fr/rkxdkK3bp
> RUU_signed.nbh file becomes from an official HTC ROM 1.37.406.1 avalaible here : http://www.4shared.com/file/5430812...io_Signed_Diamond_5226a2509_1002503_Ship.html
3. Launch mu.bat
4. select "a" to Accept
5. select "r" to Rebuilt
6. select "d" to leave it Dirty
7. select "z" to extract OS from base (OK, new folder 'casserole' with the OS.nb file)
8. select "g" to extract system files (OK, new folder 'imgfs_e' in the casserole)
9. select "y" to extract core files (OK, new folder 'xip_e' in the casserole)
10. select "p" to concatenate system (it seems good)
11. select "o" to rebuild the base...
And then, the error message :
{
"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"
}
After that, I've tried to use the other method with Diamond Kitchen, and I got exactly the same error when building the OS...
plus another message :
Even if I don't really know how the BuildOS step proceeded, it seems there is an OS incompatibility or conflict, right ?

I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?

adwinp said:
I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?
Click to expand...
Click to collapse
A quick answer though: .NET framework 3.5
Cheer,

Hello,
@ MonteCristoffOn, you've installed Microsoft Visual C + + 2008 Redistributable Package Download

[TOOL] XIPKitchen from PPCKitchen.org (Beta 6) Updated: 06/07/09

{
"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"
}
File is attached below. It's still in beta form. Will update more as needed. I do have some major improvement's coming soon I hope. So stay tuned!
Beta1 had 346 views!! Thanks for all the testing!
Beta2 had 1388 views!! Thanks for all the testing!
Major thanks to evalu8t0r for helping out with some "Auto Click" source code!!! Please make sure you donate to him here if you can!
Process:
1. Open XIPKitchen.exe
2. Pick your device xip, wait for XIPPort to do it's thing, and then disappear.
3. Pick your new xip, wait for XIPPort to do it's thing, and then disappear.
4. Go thru the checkboxs for files you want to remove or not. If the files are not in the XIPs, then the checkboxs will not even show. So if it shows, it's there.
5. Press build xip, wait for several apps, including XIPPort, to do their thing, and then all disappear.
5a. If you see this message,
then just press the OK button until it goes away.
6. New XIP will be moved to a folder.
7. Temp folder will be the new XIP OUT folder. If you need to do any more tweaking to it.

What this app does: (At the moment)
At the moment, it only works with BIN files. It does not work with OS.NB.PAYLOADS. Yet. Therefore you will manually need to extract the XIP from the payload for use with this program.
Uses XIPPORT to dump two BIN files you choose, and combines them into a third BIN.
At the moment, this app is only a frontend for other apps. This process has already been noted in another thread by sp3dev located here. This app does that process, and more is to come. I give the credit to sp3dev for inspiring me to finish this app. (It was started with the buildxip method, but since that source was lost, and that file isn't compatible with every device, it was converted over to this method.) Even though this app uses other apps, it is planned to slowly start removing the need for these other apps, and do it all by itself with no help at all. But even though these apps are needed, there is basically no work at all on the end-user side except pushing a few buttons.
Gives you the option to remove some of the un-needed files if they are found in the XIP.BINS.
Allow's you to preview the finished MAP.TXT when it's done just for verification purposes that everything went smooth.
How to use: (At the moment)
You can either Drag/Drop a BIN file onto the "Pick Device XIP" button, or click it to bring up a box that defaults to the "DEVICE_BINs" folder in the root folder of the application EXE to allow you to choose one in there or anywhere else on your PC.
You do the same thing with the Donor XIP that has the Microsoft build files you want to be included in the finished XIP.
If certain files are found in either the Device OEM section, or the Donor Microsoft section, and they are in the list of files that are known to be able to be removed from the XIP, then checkbox's will be available to be checked to not include those files in the resulting finished XIP.
A checkbox will also be there to open the MAP.TXT file when its done to show you if the process worked or not.
After checking the wanted/needed checkboxes, then you can press "Build XIP"
This will start the conversion process of the two XIP folders into one new folder.
Once you've done that, the new XIP will be moved to a folder in the application root called "NEW_XIPs". The filename will be a conversion of the Device XIP filename, and the Donor XIP filename. (Ex. Device XIP = Raphael.BIN Donor XIP = 20757.BIN New XIP filename will be Raphael_20757.BIN) With my current setup, I have all my Device XIPs named properly in the DEVICE_BINs folder. And the Donor filenames named with the build version they are (20757.BIN) in the DONOR_BINs folder. Thus making the new Filenames always resulting in a less confusing name.

<--- Reserved --->

looks easy to use.
thanks.

looks awesome, which devices are supported ?

its all waiting game now eh

Another great tool for the kitchen! Christmas is early!

xplode said:
looks awesome, which devices are supported ?
Click to expand...
Click to collapse
So far, all of them?

It is excellent idea.
When it will be possible to test the program?

cool tool to have .... hopefully no more !!!!! hunting after using ur tool

When can we try this beautiful tool ?

cruzzmz said:
cool tool to have .... hopefully no more !!!!! hunting after using ur tool
Click to expand...
Click to collapse
I don't even look at the map.txt anymore. lol...
Trying to eliminate some of the steps, but should have a test release soon enough. I want this thing to do a new XIP faster than 30 seconds. Sheesh... 30 seconds is just too long.

lennysh said:
I don't even look at the map.txt anymore. lol...
Trying to eliminate some of the steps, but should have a test release soon enough. I want this thing to do a new XIP faster than 30 seconds. Sheesh... 30 seconds is just too long.
Click to expand...
Click to collapse
you have always been out for performance but jesus lenny i think your pushing the limits a lil dont ya think. well i cant wait to see what you got in the making.

I've been waiting for someone to make this....PPCHaven.com was really close to finishing their Kitchen which would include this, but they never finished it :'(

Great work Lenny. Eagerly waiting for your kitchen Did you check the suggestions I made? Possible to include those too in your kitchen?

ahhh so thats what Noonski was talking about
Nice tool indeed, cant wait for it to be finished

Lennysh, great idea.
Hi Lennysh,
You are very bussy becasue I've read several posts from you in different web sites and for different PDA ;-)
Well, this tool is a great idea and I'd like to test it in Diamond. We are still waiting for your new HX4700 ROM.
Thanks in advance!!!
Regards,
El Parra

lennysh said:
... 30 seconds is just too long.
Click to expand...
Click to collapse
Too long? I'll wait 15 minutes if you release that "Too long release" ...
And i'll say that it is very fast... Like a rocket or something...
Thanks for your hard work.
Cheers

very very nice cant wait.

30 sec too long eh
try doing the porting manually .....

[XAP] New way of getting files into file explorer!

When wanting to put content on my phone I wanted to add it into the phones file explorer, much to my delight I found there was TouchXplorer allowing you to access the phones file system.
Sadly there was no way to copy content into this explorer and use it apart from the registry hack zune method but it renames files and causes more problems than is worth.
Recently ultrashot came out with a ported version of Opera. I looked into this further and found this was a good way to put files on the phone.
Step 1.
Download the XAPDeployer.xap file attached in post also install WinRAR, google it.
Step 2.
You'll see there is a folder called Opera, open the folder.
{
"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"
}
Step 3.
You'll see the same as the image below. This is where you can add the content you want to put into your phones file explorer. Simply just click and drag into the WinRAR window and click okay to the message.
Step 4.
Once done you can now install the XAP to your phone using Toms XAP installer. Once thats done run Opera Mini on your phone, it won't work but it will install the files you want into program files.
Step 5.
Install TouchXplorer attached at the bottom of the post and open it on the phone, navigate to Program Files / Opera Mini / and there you will find your files!
Notes:
There is also a windows folder inside the XAP which will copy files into the windows folder if needed.
Don't know if this has helped but I thought i'd get this out there

This has been around for a while. Heathcliff made the deployment XAP. Personally i just use WPDM as it allows easy drag & drop from PC Windows Explorer into WPDM window. No editing/deploying XAP's needed.

This has been known for... a few months, at least? First discovered by Heathcliff74.
Your method will still put the files in the application install directory (I mean, you're only going down one level and then back up again, why?) If you want to put files in the root of the phone, or any directory other than the \Applications directory off the root of the phone, you need to go up four levels (..\..\..\..) since the app install directory is \Applications\Install\<GUID>\Install.
I prefer 7-Zip; it's free, open-source, integrates pretty well with Windows without sticking a bunch of entries in the context menu directly, and is generally good software. It'll read anything, although due to the RAR format being proprietary I believe it's not allowed to write it (not that it couldn't, the RAR developers just refuse to open up their format - screw 'em).
Also, you really shold give credit where credit is due; TouchXplorer is the work of Julian Schapman, "schaps" on this forum, and is posted on his site http://touchxperience.com. Additionally, be aware that it only works on HTC devices, and even then only on ones with unlocked HTCFileUtility drivers, which means either they don't have the HTC Mango update (typically bundled with the Microsoft 7720.68 update) or are using a custom ROM or something like that. For Samsung devices, there is WP7 Root Tools by Heathcliff74, which also includes a file browser.

drkfngthdragnlrd said:
This has been around for a while. Heathcliff made the deployment XAP. Personally i just use WPDM as it allows easy drag & drop from PC Windows Explorer into WPDM window. No editing/deploying XAP's needed.
Click to expand...
Click to collapse
Thanks a lot man, didn't know this existed.

GoodDayToDie said:
Also, you really shold give credit where credit is due; TouchXplorer is the work of Julian Schapman, "schaps" on this forum, and is posted on his site http://touchxperience.com. Additionally, be aware that it only works on HTC devices, and even then only on ones with unlocked HTCFileUtility drivers, which means either they don't have the HTC Mango update (typically bundled with the Microsoft 7720.68 update) or are using a custom ROM or something like that. For Samsung devices, there is WP7 Root Tools by Heathcliff74, which also includes a file browser.
Click to expand...
Click to collapse
Agreed, also WPDM now works on Mango v2 Drivers for HTC. I'm using the DFT 7740 ROM & used it to copy in my custom icons & than his Advanced Config to change the icons.

is there any way I can deploy files directly to Windows\fonts folder on Samsung Focus?
Also I cant transfer files with WPDM to windows folder or windows\fonts folder
any ideas?

Build a provxml file. The specification for provxml is publicly available from Microsoft (http://msdn.microsoft.com/en-us/embedded/gg155017). An easy way to move the files is to include them in a XAP and install it. Then, either deploy your provxml to the \Provxml\ folder (like the interop-unlock XAP does) or use an app like DiagProvXML (which will also assist you in building the file, if you want).

probably this is only a stupid idea, so i'm writing here instead of creating a new topic for it.
Idea for universal Interop-unlock, tell me if it sounds right:
i read that we can deploy registry editor if you remove the interop privileges string from the xml config files. With this you can only read the registry.
Well, if we can read the registry can't we make another application for a total registry dump?
After the dump was made we can edit the app-limit and copy that file on the computer.
Using the already know exploit that this thread is recalling.. we can overwrite the old registry with the new modded one.
overwriting the registry sounds sooooooooooooooo wrong, but maybe it could be a way to do the interop unlock, what do you all think about that?

HypeZ85 said:
probably this is only a stupid idea, so i'm writing here instead of creating a new topic for it.
Idea for universal Interop-unlock, tell me if it sounds right:
i read that we can deploy registry editor if you remove the interop privileges string from the xml config files. With this you can only read the registry.
Well, if we can read the registry can't we make another application for a total registry dump?
After the dump was made we can edit the app-limit and copy that file on the computer.
Using the already know exploit that this thread is recalling.. we can overwrite the old registry with the new modded one.
overwriting the registry sounds sooooooooooooooo wrong, but maybe it could be a way to do the interop unlock, what do you all think about that?
Click to expand...
Click to collapse
I don't think this will be possible, but please correct me if i;m wrong:
* Without interop unlock we don't even have read access to the whole registery, dumping the phone's registry without interop unlock will therefor lead to an incomplete backup
* Restoring the registery by copying over on filesystem level almost certainly is not possible because of for example open file handlers to the current registery (which will prevent it from being overwritten). I don't know if special permissions (policies) are required (e.g. interop unlock) to overwrite this kind of system files [can we overwrite any file on WP as long as it is nog being used?]. The registry might be tagged as a ROM file (it ships with the ROM anyway) so even with interop unlock we will not be able to overwrite it.

Briefcase has it mostly right. Leaving aside the issue of being able to make a full registry backup (typically requires high permissions i.e. intoper-unlock already), you can't overwrite the registry hives with this. For one thing, the files that store them are located in the Windows folder, which this hack can't write to (the App manager not having write permission there). For another, they are almost certainly held with exclusive file handles.

[PC-APP] GalaxyS3 Mod Tool

I made this tool originally for SonyEricsson Xperia X10, but have now modified it to work for our Samsung Galaxy S3. I hope it will make life a little easier when modifying files on the device. It uses ADB to pull and push files, change file permissions and much more - so users don't need to remember long command prompt/terminal emulator commands! It also has a nifty little application manager, which allows for quick installation, backup, and removal of both pre and self -installed software. It has a LogCat function to read and save logs on the go when investigating errors, as well as functionality to decompile/recompile APK, JAR and ODEX files, sign and zipalign APKs, and decompile System images. ADB Shell will be released in v0.6.2.
{
"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"
}
Instructions:
1. Extract archive.
2. Install LinuxReader to GalaxyS3ModTool\tools\LinuxReader.*
3. Run GalaxyS3ModTool.jar
*This step is only needed for the Decompile System function in the ROM Manager.
Note: Make sure your phone is connected in debug mode, you have root privileges, and unsecured your device's shell. The application will try to unsecure your shell if you haven't already, but worst case scenario you might have to do this manually.
Also, the manage ROMs functionality is still experimental, and the Recompile System function is disabled. If you know how these processes can be automated, let me know and I will incorporate the functionality.
If you have problems, let me know and I will try to sort them out with you. Keep in mind that often when a modification goes wrong, you can simply push back the original files and reboot. So keep backups handy!

Reserved in case of future expansions.

Reserved in case of future expansions.

Thank you!
I'll finally be able to modify the ODEX files :victory:
Is it possible to recompile an ODEX file to .odex (not .jar)?

Great tool
Thanks!!!

Great tool. Looks very promising
Sent from my GT-I9300 using Tapatalk 2

Saleen NS said:
Thank you!
I'll finally be able to modify the ODEX files :victory:
Is it possible to recompile an ODEX file to .odex (not .jar)?
Click to expand...
Click to collapse
Yes modifying ODEX:ed filesystems has become a breeze Just remember to remove the original *.ODEX file from your system if you incorporate it into its associated APK or JAR.
As ODEX is a device-specific format, compiled to be most effective on specific hardware, recompiling with baksmali to *.DEX and renaming to *.ODEX is not enough. I don't know of any way to recompile to proper *.ODEX, but I mean it has to be possible, and if anyone knows how - please drop a line here or PM me. However the rule of thumb is to not decompile and incorporate the *.ODEX unless smali-code is being edited. This will allow you to keep the efficiency of the original *.ODEX file, and just replace the APK or JAR - i.e. having no negative effect on performance.
EDIT: Realized there is a way to recompile to *.ODEX on the device via the dexopt binary. Working on implementing the functionality.

Thanks for your work!

Warren87 said:
Thanks for your work!
Click to expand...
Click to collapse
shahed26 said:
Great tool. Looks very promising
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
SETdown said:
Great tool
Thanks!!!
Click to expand...
Click to collapse
Great to hear you guys like it!
I've got version 0.6.1 in testing now, with proper ODEX recompilation functionality incorporated. Will upload it soon.

Unable to run d App!
I downloaded d files & followed above instructions...but clicking on GalaxyS3ModTool.jar opens the archive! What am i doing wrong?

Very promising tool! I will test in weekend and give a feedback!:good:

Mr.Mefisto said:
Very promising tool! I will test in weekend and give a feedback!:good:
Click to expand...
Click to collapse
Good stuff! Looking forward to that.
harryS2 said:
I downloaded d files & followed above instructions...but clicking on GalaxyS3ModTool.jar opens the archive! What am i doing wrong?
Click to expand...
Click to collapse
Do you have Java installed?

harryS2 said:
I downloaded d files & followed above instructions...but clicking on GalaxyS3ModTool.jar opens the archive! What am i doing wrong?
Click to expand...
Click to collapse
Java must be installed on your PC and .jar files associated with java.
Sent from my GT-I9300 using xda premium

Thnx this is what i need.
Works great.

Version 0.6.1 is now uploaded in first post!
Updates:
I have implemented proper ODEX recompilation functionality. However, it requires the device to be connected as the operation has to be performed from within the system and then pulled back out. The tool will let you know when to connect your phone. For the process to be possible, a wrapper for the binary dexopt needs to be pushed to /system/bin - so this is also done programatically.
Some user prompts have been added to make human mistakes less likely. For example if you say you want to decompile an associated ODEX file, you must also specify the framework directory - or nothing will happen.
A fancy automagic script has been added for JAR-decompilation. It turns out since the dex-optimizing of ROMs, some JAR-files don't include a classes.dex file anymore, which makes baksmali.jar cough up errors. But recompiling the ODEX file as classes.dex and inserting it into the JAR makes it decompile properly - so this is what the script has automated when it recognizes the situation.
I have actually rewritten most of the decompilation/recompilation code to execute more efficiently. When time flies and inspiration runs amok, this sadly results in djungle-code. So I had to clear everything up into reusable functions so that nothing is repeated or unnecessary slow.
Happy modding folks!

ADB Shell has been implemented in the coming version. Screenshots updated in first post.

Wow, what a quite bunch
Version 0.6.2 is uploaded in first post.
Changelog:
ADB Shell functionality implemented
Some bug fixes

Fantastic work!

If anyone notices this tool working on another device - please post the device name here with any related problems. I'm looking into extending the device support for this tool.

This tool is very convenient .. I used it for the nexus 7 with firmware 4.1.2
too bad that does not work with 4.2, we look forward to updates
still great