Develop Bugs

Digital Signing WM5

I have been reading XDA-Developers for sometime and have marvelled at the ingenuity that many of you demonstrate in solving problems - I have now registered and here is my first post and hope someone can help - Digital Signing for applications we develop for WM5 is a real pain especially if you need privileged access to run as it is up to the carrier or device OEM if they want to grant you use of the certificate. I guess if you were selling software this could mean they could withold permission because they had a competitive application, all smacks of anti-trust...unprivileged access is more straight forward but is no good if you need to access the kernel or other specialist processes. I note from the XDA WM5 part of this forum that someone had changed a rom so that it would not moan at unsigned apps. Does anyone know if this change would allow any unsigned "privileged" application to be used on a JASJAR - if so does any kind person have the ability to create a CAB file that could or program that could enable this condition and another to revert to normal operation. This would make a huge difference for those wanting to develop and test apps on a device instead of just the PC emulator however it would still require signing to get the end result available for others to use on their devices - I guess we would also have to consider if this "modifying" app also needed to be signed to run in the first place - nice one MS :evil: , the user is no longer allowed to decide what he wants to install :roll: .

According to MSDN there is a tool in the WM2005 SDK called createcert.exe that allows you to create certificates for test purposes.
I didn't have much luck with it my self, but I haven't read all the documentation, so I probably screwed up when creating the certificate.
Have you tried it?
If you make it work, could you please give me some advice on it. Thanks!

Update file

for all releaser...
i wanna learn something that is Why dont you release an update file instead of a new rom file ?, do you have to release as a new rom file ? i am bored about new rom install issue...tell me why..
thanks in advance...

The reason chefs don't release update files is because the programs designed to create ImageUpdate files are still in development. There is currently no way for us to use the ImageUpdate system at this time, and that's the only true update mechanism that would work with ROMs.
I suggest that until the XDA ImageUpdate project is online and running (could be awhile), you should learn to automate the installation of all your .cabs, personal info, email accounts, etc. with XDA User Customization (provided your ROM supports this). I have almost nothing to install or configure after a ROM flash because I've automated everything on my device with XDA User Customization.

i mean that the publishers would make a cab to update our rom. i didnt mean a nbh file. is it logical ?
thanks in advance...

DaveTheTytnIIGuy said:
The reason chefs don't release update files is because the programs designed to create ImageUpdate files are still in development. There is currently no way for us to use the ImageUpdate system at this time, and that's the only true update mechanism that would work with ROMs.
I suggest that until the XDA ImageUpdate project is online and running (could be awhile), you should learn to automate the installation of all your .cabs, personal info, email accounts, etc. with XDA User Customization (provided your ROM supports this). I have almost nothing to install or configure after a ROM flash because I've automated everything on my device with XDA User Customization.
Click to expand...
Click to collapse
They've been developed...the problem is that no current roms support image update and that the program has evolved into a something a bit bigger and has slowed in development.

CABs won't work, because some files are "cooked" into the ROM (read only memory) and cannot be changed.
The "Image Update" been discussed is the solution to this - if you want to know how / why, see here.
Until it's developed, theres not much you can do.
Hope this helps.
Dave

thanks for all your answers..

[Q] Problem on installing apps to an unpublished Bada phone (GT-S7250)

Hello guys, I'm a greenhand on XDA, English and Mobile-dev, so please forgive any of my stupid words if I do have said in the bellowing description.
Yesterday, I joined the Samsung Bada Developers' Day, and got an unpublished Bada phone, it's GT-S7250 (Wave M). The problem is , I found I don't know how to install apps on it .
At first, I tried the built-in app market client, but strangely, I can only found some test apps on it, I guess that 's because the app market server still can't recognize this phone type yet.
Then, I use Samsung Kies on my PC, wish I could send apps to my phone after downloading them with Kies, but unfortunately, still doesn't work, cause it always prompts that the device is not supported.
So, could anyone provides my any idea to bypass all these limitations ? Thanks.
PS: I have do some monitoring work on Kies, and seems that there no validation requests to the server, and thus I think there might be a configuration file on the local disk, containing the supported devices's info, and if we can find and hack it, perhaps we could bypass the limitation.

what display resolution does your device have?
maybe you could ask larioteo for a copy of his app, he has found a method to install one app without kies, but he's only developing in 800*480 resolution

Can you show us the FW code read by kies???
i want to see if i can get the FW you have right now
About hacking kies...i think your phone is HVGA device so you can't install apps that are in kies right now
Wait until larioteo is back from his work to see what we can do about it
maybe we take you as a tester because you know chinese and we don't have chinese localization
Best Regards

Lithophyses said:
what display resolution does your device have?
maybe you could ask larioteo for a copy of his app, he has found a method to install one app without kies, but he's only developing in 800*480 resolution
Click to expand...
Click to collapse
Thanks for your reply, as @mylove90 said, the screen is HVGA, 480x320.
I will dig into larioteo 's posts while waiting for his reply.
Acutally, I have found the downloaded app files on my PC, the path is
C:\Documents and Settings\Administrator\My Documents\Samsung\Kies\Download\Applications, under this folder, I have found the *.app files, together with the corresponding *.app.img file each. I guess these are the app files I need, but to my disappoint ,when I copy these files onto my phone, I can't install them, it prompts unknown file type.

mylove90 said:
Can you show us the FW code read by kies???
i want to see if i can get the FW you have right now
About hacking kies...i think your phone is HVGA device so you can't install apps that are in kies right now
Wait until larioteo is back from his work to see what we can do about it
maybe we take you as a tester because you know chinese and we don't have chinese localization
Best Regards
Click to expand...
Click to collapse
Hi, mylove90, thanks for your reply.
To be honest , I don't quite understand what do you mean by "FW code", this is the first time I met this abbreviation, I guess you mean the "FirmWare code", right ? If so , Kies shows the firmware version is : S7250XXKI8/S7250XAKI8(XXX) , Hope this is what we need to find.
As to become a tester, I have to say that I'm REALLY REALLY glad to do that, it's an great honor for me that I can do something for possibly all Bada users as my feedback to the community.
And I also had a look at larioteo's post about the voluntas browser, hope I can do somthing for it.
Thank you again,
Best Regards.

S7250XXKI8/S7250XAKI8(XXX)
Click to expand...
Click to collapse
Thank you for info.
Firmware seems from September... XXX seems Product Code...
About install Apps... as handset is "new" (different Resolution)...
But you could play with bada 2.0 SDK to install few examples...
Maybe be carefully, as it is an prototype and as I know no Firmware is leaked, to fix problems...
Best Regards

I found something, if i wanted to search "S7250XXKI8". There is http://www.badaforums.net/forums/bada2/bada-dev-day-2011-t4913.html discussion on badaforums about Wave M.

Oh Samsung is so evil
XXX is invalid product code for kies updates
you get XXX product code is you damaged your original one
they know that we already got kies firmwares for sure
Best Regards

Hello there i am see left
XXX is not invalid it is the "Default Code", the main product code for all devices, only test devices gets this code, it is the ultimative update everything code.
As i know it from slyfer my tool to watch their server XXX was always the first code that got an open europe firmware, than the others get an upadte like DBT, OXA OXB OXC OXD OXE OXG after that the providers pick another of that and make something liket his VIA DRE and so on.
For more infos you need only to ask.
Picture in 5 minuetes: (also with other codes that you believe me )
note: yes the server changed but not the codes

larioteo know the best, but probably you can't install any apps that already launched. I mean, you can't install the apps that downloaded with Kies. but you can install an app that under development via Bada SDK 2.0 or larioteo's method. I hope I didn't make things worse for you.

Root Cert method via BADA SDK
If you just want to install your own apps on your wave M, ask Laoriteo about the root cert method via BADA SDK.

Really appreciate all you guys very very much, thank you for you kindly replies to my first thread on XDA.
According to your opinions, seems that there isn't much I can do with this problem. Perhaps I can only wait for the publication of this phone type, maybe till that time I will be able to use the built-in Samsung app market client. Or perhaps some hackers may jailbreak Bada, so that we can directly install any apps.
Then, I will be aiming at Bada app development, because I really feel the lack of apps on Bada, especially under the condition that I can't install any apps on this phone now.
Thank you,everyone!

http://forum.xda-developers.com/showpost.php?p=17900523&postcount=166
Maybe you could try this...
Maybe you see then Firmware for your handset...
Maybe Apps...
Best Regards

[PROG] Did you know Slyfer

larioteo developer make's verry great program but we know the samsug server changing, there's the source.
http://forum.xda-developers.com/attachment.php?attachmentid=601440&d=1305838631
Why im intersting about this program because difference with CheckFus you can see all about information, binary, can download just what file you want on firmware not all, can check number...etc
Thread for binary version :
http://forum.xda-developers.com/showthread.php?t=1087530

larioteo was so sad where the server was changed
It is really good application and when i saw its source go public i hope that someone will take it to the next level but i think no one have the skills to do it
larioteo is really good developer and i am happy for working with him in Team VEA....he is currently so busy just like me-maybe i am a little bit more free-he is not planning to revive slyfer soon
Please Developers/Hackers if you think you got enough skills to rebuild slyfer just dig in it...i'll ask larioteo to watch his thread so he can answer anyone got a question about his code
Best Regards

hi folks,
you all know how to find latest version of android stock-roms on samsung server,
but only problem is that all software for decrypt them is for .NET (pseudo jvm) for windows...
so if you like to decrypt the files on linux you can get the commandline from:
http ://android.zsolttech.com/index.php?file=GT-I5700_I5700XXJH6_I5700ONEJI1_I5700XXJD1_I5700XXJH6_XX_ONE.zip.enc2
REPLACE the FILE parameter from the URL
pls remove space after http!!!
it just works for enc2 files....
hth
arris

Good idea lets hope someone cones up with a new app for this matwrpiece!
Sent from my GT-N7000 using xda premium

[XAP + SDK] WP7 Root Tools 0.9

Download: www.wp7roottools.com
Today I am proud to announce the immediate availability of WP7 Root Tools 0.9 alpha and WP7 Root Tools SDK 0.1!
WP7 Root Tools 0.9 brings true Root Access to devices with stock ROM's, but it also works on devices with custom ROM's and Full Unlock. Your device needs to be Interop Unlocked to use WP7 Root Tools!
This is still an alpha-release, because there are a lot of new hacks and the tools are still not feature complete! I have rewritten about 75% of all code from the previous release. So before you install WP7 Root Tools you should make a backup of your device. WP7 Root Tools will make changes to system settings and, although this has been tested, it is still possible that a problem occurs. In that case you want to have a recent backup of your device. Installing WP7 Root Tools will be your own responsibility. The author of WP7 Root Tools and the SDK cannot be held responsible for any damages caused directly or indirectly by installing and using WP7 Root Tools or the SDK!
Windows Phone is a closed system to protect the user and his/her personal data from malware and to protect the intellectual property of the developers. The downside of this closed system is that homebrew developers are very limited in their ability to control and tweak a Windows Phone device. With WP7 Root Tools I attempt to open up the system in a gentle way, so that users stay in control of their device, while homebrew apps can get more control to get the maximum power out of your Windows Phone device!
WP7 Root Tools 0.9 now has a File Explorer, Registry Editor, Certificate Installer and a Policy Editor! Thanks to true Root Access on Windows Phone, this new version of WP7 Root Tools will work a lot faster than previous releases and it supports a lot more devices!
WP7 Root Tools should work on these devices:
- Samsung first and second generation devices
- LG devices
- HTC first generation devices with Mango v1 drivers (SPL 4.x or lower)
- Samsung first generation devices with custom ROM and Full Unlock
- HTC first generation devices with custom ROM and Full Unlock
On devices with stock ROM's WP7 Root Tools need to install Root Access. The first time it runs, a 2-phase-installation will start. The app will inform you to start the first install-phase. Then the device will reboot after a few seconds. After the reboot you need to start WP7 Root Tools again immediately! Then the second phase of the installation will start and your device will be rebooted again. After the second reboot you are ready to use WP7 Root Tools. You can use the Policy Editor to give other homebrew app a "trusted" status. With this you will give the app Root Access privileges. So be very careful to which app you give Root Access!! You are responsible for giving access to an app! If you are not sure, read the forums to decide if an app is trust-worthy.
I also created an SDK, which developers can use to profit from Root Access. It provides a way to gain access to the filesystem and the registry (and more) from their managed Silverlight application. No need to worry about COM interop and C++ anymore! The package contains a read-me with short instructions. More details and examples will follow soon! Over the last days Rafael Rivera from the Chevron WP7 team has tested the SDK and he is finishing up the first homebrew app that will use my SDK. He is planning to release his Backup-app soon.
I also need to thank some people for making this possible:
- My wife! (for having to put up with me while doing all this hacking!)
- YukiXDA (for helping me with research on policies)
- Justin Angel (for sending me a NOKIA)
- Cees Heim (for supplying an HTC device for testing)
- Rafael Rivera and Chevron WP7 team (for pioneering WP7 Unlocking)
- HD2Owner (for helping me make custom ROM's for testing)
- fiinix (for helping me with research on policies)
- Ultrashot
- xb0xm0d
- AndrewSh
- Ondraster
- Barin
- Football
- Cmonex
- GoodDayToDie
- Jaxbot
- Dennis Wilson
I will update the guides and manuals on www.wp7roottools.com and here on XDA in the next coming days. I need some time to update all of it.
Have fun with Homebrew now!
Heathcliff74

reserved*****

reserved***** (2)

reserved***** (3)

reserved***** (4)

thank you for your hard work

SO AWESOME!!! Thank You SOOOO Much!!!

big thx 4 all your work man!thxthxthx...
Sent from my OMNIA7 using Board Express

Previous Versions
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?

Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?

Fantastic work, Heathcliff74. Oh man, this is going to be awesome.
Suggestion: use one of your reserved posts to compile a list of trusted apps that benefit from policy elevation.
Two that I've found so far (one of mine):
Root Webserver (in my sig) - runs better with Root Tools than ever before.
TouchXperience - gives way more access through WPDM.
Two others that are in development:
LockWidgets - the preview build has some bugs, but it can be run with Root Tools.
XapHandler - the test build has some known issues (can't install or update if the app is already installed) but fresh install works at least some of the time.

Awesome work! I can confirm that the install works perfectly on an LG Quantum.

Big day!
I need some free space in C:/ to make backup.

sensboston said:
Great news, thanks a lot! Successfully installed on Focus and Surround, no problems at all.
But I've tried "BT file transfer" and "Opera mini" (after install I've enabled "trusted" status for the apps): both apps not working properly. Should we expect updated versions of these apps (built with your SDK) or it's some another issue?
Click to expand...
Click to collapse
WP7 Root Tools will give Root Access to Silverlight apps. DFT BT and Opera Mini both use native executables. You can't give the executables root access with WP7 Root Tools (in fact, you only give the launchers Root Access). These apps could possibly be recompiled to run under TaskHost.exe (as all Silverlight apps do), but I'm not sure about the inner workings of the apps. You'd have to ask the developers.
I will investigate this matter. With all the hacks I have now, I should be able to give Root Access to executables too, but that needs more research.
Ciao,
Heathcliff74

@sensboston: Those tools both require additional native binaries. WP7 Root Tools elevates apps, including all the DLLs they load (which is how the SDK works - it's a homebrew DLL, similar to the old Native.dll and company). However, it doesn't work with out-of-process binaries. Opera requires an EXE (which is obviously its own process) and BT File Transfer requires a driver.
In theory, supporting these would be possible. They'd need to be signed, and the certificates added to the Code Integrity store, but that's already possible. However, they'd also need new policies added. The current version of Root Tool only supports modifying the policies for installed TaskHost (Silverlight/XNA, possibly including some native code) apps, not adding policies for other apps.
BTW, although it's very limited, it turns out that Application.GetResourceStream can be used on files outside the app (with sufficient permissions). That means, if you want to write an app that only needs to access existing files at known locations, you don't even need to mess with native code... although the Root Tools SDK will make it quite easy to do such apps anyhow.

Thanks HeatCliff
Thanks man for this wonderfull pice off work

Heathcliff74 Installed on My Omnia 7 Thanks a lot for your Hard Work

JamesAllen said:
Thanks for your great work. Do we need to uninstall previous versions before installing the latest version? I have .8, how do I install .9?
Click to expand...
Click to collapse
You can just reinstall. No need to uninstall. From this new version on (version after 0.9) you better do an "UPDATE". Not all xap-installers support updating. A lot of them will do a full-install-cycle. If you do a full-install-cycle, you'll loose the permissions and you will have to do the 2-phase-install sequence again. If you do an in-place-update, you will keep the permissions and everything keeps working as expected.
Heathcliff74

Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.

dreamcaster012 said:
Damn, doesn't work for me.
Verizon HTC Trophy
OS 7.10.8107.89
Firmware: 2305.13.20110.605
Hardware: 003
Thanks for the work! Hopefully I'll see support later. I probably updated to the HTC v2 drivers at some point.
Click to expand...
Click to collapse
Hmm. are you interop unlocked? I'm no expert with HTC's but that versionnumber looks like your drivers are not that new and could possibly be supported. If you are not Interop Unlocked, then read the opening post of my Interop Unlock thread. At the end of that post is a section specifically for Verizon Trophy's
Heathcliff74