Related
Hello people,
I gave this short title to this topic because... I'm simply having troubles. Troubles upgrading, syncing, translating.
I have a Qtek2020. It had WM2003 installed. Had, because I finally managed to install WM6.
But let's go by order.
Some days ago I found this awesome fantastic forum full with binaries.
I have some experience with ROM flashing with various devices. I also did upgrade my OS several times on my 2020. And I decided now it's time for WM6. Many people here said it works, and I wanted to upgrade too.
I'm Italian, so you would understand that I prefer using an Italian OS. But I first wanted to install English WM6 to try it out.
I downloaded TofClock AKU 0.7 and tried to install. But then, the first troubles.
I could no way upgrade my device on my home PC, which runs Vista x64. When I put the device in bootloader mode, the upgrade software returned error 101.
So I tried to do the upgrade at office, under XP SP2 (x86 platform), and everything gone fine.
OK, you would say, you got your new fresh OS. I actually don't have musch to complain about TofClock: I really say BIG BIG HUGE THANKS to the genius that did it!
But here's another problem. Still at office, I could no way sync my PDA on ActiveSync 4.5. Windows didn't install the driver properly.
I came back home: as I said, I run Vista x64. Fortunately, Vista downloaded a driver from Windows Update and the whole thing worked.
OK, you would say. You even got your sync relationship at home.
But now that I saw it worked, I wanted to install an Italian version, maybe even cooked a bit, so I downloaded both the Kitchen and the Microwave for m0dding and translation. The firts thing I tried was the Microwave I found at http://forum.xda-developers.com/showthread.php?t=334421&highlight=italian+microwave
I followed the full tutorial literally but I had the following problems:
There was no dump directory. Only dump.src. And dump, filled with tons of files, was required
There was no nk.nb file
There was no 800401-OS.bin file, required by other parts of the batch script
I tried on my Vista x64 and I also tried on a XP SP2 Virtual Machine on my desktop PC. Same result. I found another tutorial. I will probabily try it, but I'm so confused now. Why am I the only one who can't translate his ROM by following literally a tutorial?
Can somebody help me? Maybe with an already-working ROM for Himalaya that I can flash by myself?
At this time, I'm trying to connect my USB cradle to my Virtual Machine using USB over Network, because if I want to do this at home I have no other choice than using XP x86.
Meanwhile, I ask you help with translation. Please! I just need to run it in Italian. I will take care of Kitchen and all the mess that comes with customization later. I only need Italian now, and I need to be able to upgrade. I still have 15 days (by now) of trial license for USB over Network. I could even share my cradle with somebody that is able to do the upgrade remotely, because, as far as I know, if connection breaks during upgrade and the process fails, the Bootloader mode prevents the PDA to become another brick in the wall and the operation can be still tried again.
I will leave my MSN Messenger contact on my profile. You can find me everytime but business days/hours.
Thanks in advance.
I'm sorry, but the Microwave is for HTC Wizard only, you can not use it for Himalaya.
Download the Himalaya kitchen, find Italian *.dll.04xx files or extract them from the free Microsoft Italian WM6 emulator. Use the quick and dirty way to create Italian ROM as described in
http://forum.xda-developers.com/showthread.php?t=311078
success
I tried that tutorial (still in Virtual Machine). I had error "file temp\dump\imageinfo.bin already exists" when clicking the green arrow in Kitchen. I tried both Anichilius and TofClock's Kitchens
[Add]: I'm trying with HyperCore. I'll let you know
Anichilius kitchen is for Hermes, not for Himalaya
Tofclock worked on several devices
Hypercore is Hermes as well
Get your facts straight before trying to cook a ROM or you'll brick your device
Unfortunately I'm no expert in ROM cooking. It's my first time here. I don't know about the differences between the devices.
As far as I know, most of the Kitchens carry the same program: BuildOS. I found the problem running it. I'm trying to learn everything now by reading the forum.
I dumped TofClock's ROM (OS ver. 6.0) using ImgfsToDump and got all the files. I dumped WM6 Emu too. I found that TofClock ROM doesn't carry the *409.mui files that are inside emulator's ROM, like explained in the tutorial. So when I renamed the files from 410 to 409 and copied them I didn't actually overwrite anything.
Running BuidOS, which is a script that comes with every kitchen with no modifications (I didn't binary compare the files but I think it's the same script), so it doesn't seem to be device-specific, I always got the error "File temp\dump\imageinfo.bin already exists". I tried to find out the reason by reading Hypercore documentation. And it seems, as I thought, that the files I want to build are in conflict with the original files. I tried to understand why. I'm not sure about it, but by the hex address I saw around in the dump files it seems that the ROM is not organized as a file system, where every file is dynamically allocated and indexed in a file table, but they are allocated to raw memory address somehow.
I don't know why. For example, if I want to cook a Windows XP setup CD with my own bootloader I have to simply burn a CD with a modified ntoskrnl.exe file and here we go every XP installation from now on shows my ugly/sweet face (choose the best that suits)
As far as I know, apart from obvious size limits that vary with the device, there's a new limit in ROM cooking: I can't copy&paste files. I thought that the BuildOS script "simply" packed all the files into the ROM rebuilding the file table, adding checksums and other info according to the ROM format (which I don't know), and maybe I'm wrong.
[Add]: I have been trying to get in contact with slumpolo, which is very expert in Italian ROMs. Meanwhile, I read on that tutorial one of his replies: he said that not all ROMs have MUI files. So TofClock doesn't use MUI (btw Windows Vista does, but that's other things), but WM6 emu does, and that may be the reason why they are not compatible.
I know Himalaya devices are a bit "ancient", but I wonder if there's another ROM than TofClock to work on. I may try with it.
I wouldn't like to ask "can somebody [with big big experience] do the translation for me?". I would like to do it myself, but I need tools and knowledge. I think I already got the tools...
There is already a great Tofclock WM6 AKU 0.7.0 especially for Himalaya. Download it from http://forum.xda-developers.com/showthread.php?t=331637
and the Xplode Kitchen Tutorial. This kitchen has all files and registry hives extracted and nicely organized. So you don't need to dump them yourself.
Of course you will need the emulator dump. Keep folders well separated and organized.
It does have all the 0409.mui files. If you use the quick and dirty method of simply renaming your mui files/folders to *.0409.mui and overwriting the original ones, you should get a fairly acceptable result. Not perfect, the emulator runs an older version of WM6 than the one in the kitchen. If you want perfect, you'll have to spend a lot of time...
Your big "WHY" question: Intel X86 architecture is very much different than the ARM/Xscale architecture. The ARM is a child from the Acorn RISC processor. So operating systems for X86 and ARM are very different in structure as well. But if you want your pretty face on the Hima bootloader screen, it can be done, search the forum for "splash screen"
Hima is by no means "ancient", it is still one of the best HTC designs ever. All right, the newer models are lighter, have beter cameras and some even 640x480 and a "modern" price tag...
Don't worry, I won't offer to do the translation for you. I'm still trying to create the perfect Dutch ROM.
We talked about the same Kitchen. I tried it too in the beginning. But now I found something more. Many of the 409.mui files in this Kitchen are in subdirectories. So I could simply paste them there and find no error in BuildOS... Maybe... I'll let you know.
BTW the face thing was a joke: I already know how to change a bootscreen and I will do that as last thing once the ROM is stable and Italian.
About the "perfect" ROM, I can accept the challenge and spend some more time on it once created the BASIC Italian Rom, at least...
And I said Hima may be "ancient" because my Qtek 2020 is more than 3 yrs old
Cya 2moro
In desktop PC's I consider 2 years old the equivalent of stone age, I'm really surprised that this hardware has such an enormous life span. I even believe we've yet to discover the full potential of this little beasty.
Lol.
By the way, here's the thing I wanted to show you.
The files in Microwave directory are the dump of emulator, while the files in Work directory are from TofClock.
So I "simply" have to match directories while pasting emu files into TofClock after renaming
djechelon said:
So I "simply" have to match directories while pasting emu files into TofClock after renaming
Click to expand...
Click to collapse
Simple, as long as you're concentrated. Because in the Quick and dirty method both directories have identical names, I once started dragging and dropping in the wrong direction, overwriting Dutch with English...
Next pitfall, some files point to one another
a.04xx refers to b.04xx
I use Ultra€dit to search inside all these files for the string 0413 (dutch) both in plain ASCII and in Unicode. Do not automatically replace, watch in the hex editor if it's actually a string, not a piece of code.
Now edit initflash.dat using a good unicode editor (like ultraedit) and take care to save as unicode. Do not allow the editor to convert it into anything else. Take care that there's only one initflas.dat in your kitchen, the edied one, and not for example an autogenerated backup (Ultraedit can do that...)
Read cooking tutorials on how to edit initflash.dat
Add OEMs (see cooking tutorials)
Cook, burn, test
I think you're going to tell me that the ROM I managed to cook now won't work until I manually edit each single MUI file against 410 pointers... Actually I forgot to paste initflashes.dat, because when i pasted the whole directory I always found out that the names were correctly translated! Yea, just because I pasted it.
I'm gonna use TortoiseMerge to compare initflashes.dat from emu to TofClock.
Fortunately, I can make as many mistakes as I like because if I brick the device I can reflash it using Bootloader mode with a working ROM (which I'll jealously keep on my hard drive in more copies ).
However, I was unable to flash under my XP SP2 Virtual Machine. I'm trying again under Vista, else I'll have to do it at office where it worked last time...
It's really harassing, but it's a fascinating world I'm exploring.
Brick
Oh finally I bricked my device!!!
Hahahaha. OK I managed to build my first Italian ROM but, as expected, the device got stuck on the Windows Mobile logo.
Not bad. I tried a little modification and re-flashed it. Same error. So I gotta restore TofClock original for now... It makes me little sad because I ran in lots, lots, lots and lots of troubles, putting all of my efforts, to build the f***** ROM.
Till my device still lives, I can test as much as I want. By the way, Maggy, I need your help now.
You talked about cross-links in MUI files. I tried to find them. I used UltraEdit and tried to search for "410" (Italian) in the MUI files I renamed into 409, but I can't find anything. I tried with a lot of files, not all files, but no one has cross-links.
Just to see if everything's fine, I'm trying to re-cook the TofClock ROM that came with the Kitchen, with no modifications, not even the bootscreen. It's just a check. It's 3 AM now: should I take a nap? I think so...
Anyway, let's get back to my problems. I noticed that both on Vista and XP (btw I managed to cook&flash with Vista so I can now throw the VM in the bin together with the shareware version of USB Over Network that installed me a harassing driver blocking all USB devices including mouse & key if I don't manually disable driver signature...) the BuildImgfs program... explodes!
Well, actually it consumes too much memory. The heap goes up to 1GB before crashing. I think here is a bug in the script: destructors should be called to free memory from unused object ASAP. .NET and Java have Garbage Collectors, which take care of destroying unused object, but it's not the same with unmanaged code like C++ or whatever used to make the program.
I tried to search, but I found nothing (did I say something about a nap...?). I need, if available, a newer version of BuildImgfs that manages memory correctly and doesn't crash. I saw many people having the same problem. I don't add too many packages: I'm even forced to remove Windows Media Player to let it build!!!
[Add]: as expected, the re-cooked TofClock works. OK I'll go sleep now. Promise!
Here is basic program for your windows computer that just does basic stuff.
It can reboot your phone to wherever you want like recovery, bootloader.
It will wipe your ext2/3 from recovery if you choose and it will repair your ext2/3.
This is still beta, so far everything that is on the app works. But when I say beta I mean I still to implement alot more features so just use it and then tell me what you guys want. I am working on implementing switchrom into it.
This is just about 3 hours of work so you will see alot more in the future.
Screenshots Below!
*(For those of you wondering it is writen in a mix of C++,vb.net,python,and MS-DOS)*
Twitter: http://twitter.com/kickfliprock13
** Oh I forgot to mention you need to have adb set up for this to work if you don't have it set up than it wont work. So if you want to set up just go here: http://punk-in.com/driver_vista.html
Continued
Changelog:
9/8/09: Added a link to tell you how to install usb drivers for your phone
Added links to our twitter's and plurk's
Fixed a few small bugs
Continued Again
This is for problems and things I am changing!
Problems:
Can't get it to put arguments into adb commands, for example adb shell sh /system/sd/switchrom -s (then the name they want to name it)
I suck with ShellExecute commands so I need to get better at those
Need to learn how to add .exe's and other files into a C++ file and then run it.
Changing:
I will probably be changing the layout in the next update
I will be learning ShellExecute commands hopefully. So then it can set up adb for you and do a switchrom.sh for you
looks good dling now btw how many programming languages do you know lol
Languages
I know a couple. This program is written in C++. I have only done C++ for about a week so I am still kind of a noob. But other than that I know: html, MS-DOS,Python, I am learning java, I know some C and C#.
I am taking some visual stuff right now, like blender and game development.
After that I want to learn CSS, and learn the reset of java and C++
do you think you can make it that the program can flash the new spl and radio so the phone won't brick. Anyway awesome program
It looks like it's just issuing the non-response ADB commands. Do you have anything there to capture the commandline output from ADB? I'm trying to get the push and pull confirmations for mine. It seems the stream is immedately written as blank and then changed to the confirmation but the change is not rewritten to the stream.
Also ADB does not have to be in a specific directory in order to work. Just change the working direcory of your process to the folder where you have them stored. I bundled the files with mine so I didn't have to worry about if someone didn't have them in the right place.
M..N said:
do you think you can make it that the program can flash the new spl and radio so the phone won't brick. Anyway awesome program
Click to expand...
Click to collapse
Yes, we are working on making that happen very soon. It is difficult but yeah, we already figured out a way to apply new radio,spl and get to hero in about a minute now we just need to implement that into the app but I just can't figure out exactly how to include multiple files in my C++ project but once I figure that out I will tell you.
Excellent thanks very much
Hi so how is this program coming along
Very well I almost have rooting figured out
Cool would this work on uk phones and when is the estimated release time
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
someone needs to close this thread before this flame war gets any bigger
tekgek said:
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you tried just pushing with adb? By development do you mean cooking or compiling your own?
Please be respectful of others ...
I taken the time to cleanup this thread and move to Q&A where it should have been. If someone has an answer post a reply; plans to respond using trolling tactics are ill-advised.
If the thread goes OT again, a moderator will be forced to close it and likely remove it ... would be nice if it didn't have to come to that.
Regards,
I am building this directly from AOSP, from scratch. Thanks to the mod for cleaning up the flame war, by the way
Oh, from AOSP. How are you adding them in? AOSP does NOT include the Google Apps by default, I'm not expert in ROM building but I am sure there are some .libs needed (I know GTalk requires some) and possibly need the other Google Apps as well.
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
./adb install alpha-1-signed/system/app/Vending.apk
898 KB/s (1274068 bytes in 1.384s)
pkg: /data/local/tmp/Vending.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Click to expand...
Click to collapse
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
EDIT: For all of you who are currently viewing this thread, how many of you would like a very fast (possibly faster than OpenEclair), stable, no-frills Android 2.1 ROM? I would like your opinions, because this will give me a good idea of how many people would be interested in this kind of thing.
Tekgek
tekgek said:
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
Tekgek
Click to expand...
Click to collapse
It's good to know that you are missing libraries
Your best bet is to compile your rom, and then compare it to a rom that already has the google apps included (WesGarner build, CSDI, etc...) and see what libs are missing from yours, add them in and then try again
I was having the same problem too. I am gonna try this too.
And ya besides the libraries, the aosp build doesn't include some of the framework files and permission files too, like the framework files relating to gtalk and google maps should be added as well to the system/framework folder and the permission files in system/etc/permissions relating to gtalk and maps should be added as well.
I tried with all the missing libraries but with no luck...there must be some other files tooo. Gonna continue on Thursday.
Did you try resigning the apk file?
Not really. I am gonna try that too. Got coll tomorrow so may be later tomorrow. By the way did you got the video working?? I tried pushing some libraries from supereclair. But not workin till date. it works in his build though.
College is more important than android, imho. whenever you get the chance .
I hope to get video working in the future, but not right now. My primary computer (the core i7 rig I use for all my computer work) needed an OS reinstall, so I have made no progress since my post on ADB. My fist priority is to get the basics working, then I'll work on the other issues, like video playback and the camera. However, as of right now, I am re-downloading the source, and hopefully building it in the very near future, expect an update tomorrow, and maybe even a finished product (keep in mind that this is ALPHA, so don't expect anything wonderful).
Alright, I got it... mostly. The market appears installed, now all I need to do is make it not crash. Whenever I select the market app, I get a white screen, and then the home screen. I'm also getting a force close on the gapps process. What am I doing wrong
How did you got market show up???
The gapps framework file is also missin in the /system/framework folder in AOSP build.
Did you tried pushing the missing file?
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
tekgek said:
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
Click to expand...
Click to collapse
ya its com.google.android.gtalkservice.jar
okay, added it in, still getting a force close on the gapps. Where to go now???
As i mentioned earlier there are some files missing in system/etc/permissions. Did u tried pushing those files.
All permission files are in place, all gapps are resigned. The framework is in place. The setup wizard i also resigned, which now crashes. If anyone has any suggestions please post them. I am at my wit's end here.
Perhaps these might help some of the devs here.
The installer helper app didn't seem to do anything (as expected since this is for an Archos) but maybe ripping it apart to see what it's doing may help.
I downloaded the apps from within apps.zip as well but the only ones that would install was media uploader and maps. The rest gave parse errors.
http://code.google.com/p/archos-apps-installer/
This would be great if it work for our device. I shall look into it but I have close to no experience with android programming
Droidish said:
Perhaps these might help some of the devs here.
The installer helper app didn't seem to do anything (as expected since this is for an Archos) but maybe ripping it apart to see what it's doing may help.
I downloaded the apps from within apps.zip as well but the only ones that would install was media uploader and maps. The rest gave parse errors.
http://code.google.com/p/archos-apps-installer/
Click to expand...
Click to collapse
I have a (speculative) feeling that the version of Android included with the Archos tablets may be more complete than what ships on the Nooks. Still, this may be helpful. I'm 'bouts to tear into it.
Interesting to see this thread started today. Last night I found the gapps for Archos and tried a few things but to no avail. The error that I was getting was that it only ran on xxx. I can't remember the exact wording. But someone that actually knows how to read/write software code might be able to make something out of this Archos package.
This works for Archos because the '/system/app' directory has aliases to the '/data/test/froyo/system' folder. Basically, Archos sorta knew we'd manually install the Market.
If the Nook has something similar, it could work, but you'd have to see what writable directory the Nook has if they even do this like Archos.
If they don't have the files like this prefixed with a 0 then you'd probably need full root to get the market going. However, I'm not root expert to guide Nook users nor do I have a Nook... (=
0GenieWidget.apk
0Gmail.apk
0GoogleBackupTransport.apk
0GoogleCalendarSyncAdapter.apk
0GoogleContactsSyncAdapter.apk
0GoogleFeedback.apk
0GoogleServicesFramework.apk
0Maps.apk
0MarketUpdater.apk
0MediaUploader.apk
0NetworkLocation.apk
0SetupWizard.apk
0Talk.apk
0Vending.apk
0VoiceSearch.apk
0YouTube.apk
0googlevoice.apk
I have LUMIA 620 dev unlocked via dream spark.
I downloaded XAP file from marketplace and it seams to be encrypted so they are not installing via DEV tools to my device.
But i searched around some apps which can be installed via DEV tool because the are modified and i want to know what are the changes that are need to be made in XAP files:good:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
prashantvrm said:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
Click to expand...
Click to collapse
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
TheGoldrocker said:
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
Click to expand...
Click to collapse
You are correct sir. It sucks that you can't even sideload Xaps that were downloaded manually due to the app being removed from the WP store on a non-SD device. I'm trying to see if I can make a workaround for this though. It would be nice if it worked. In terms of modifying the encrypted XAP, it'll be a while before one of us figures out how to decrypt, but at the same time that opens a whole new can of worms regarding to piracy.
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
GoodDayToDie said:
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
Click to expand...
Click to collapse
It would be nice to be able to put one on the emulator itself and see what was going on..
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
tonbonz said:
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
Click to expand...
Click to collapse
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
snickler said:
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
Click to expand...
Click to collapse
I don't like the sound of that The app is part of the settings on my device but when opened says there is a problem with my account and contact Verizon.
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
GoodDayToDie said:
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
Click to expand...
Click to collapse
I've enjoyed the benefits of all the devs and their hard work here at XDA since my HTC Trophy. Glad to give back in any way I can. If any other files or folders are needed I would be happy to oblige...and... I thank you sir!!!
Oh what the h*** Rest of the dump files currently uploading. Dump 1, three 7z files altogether, is the Programs folder from earlier post. Left out maps data from Data/shared data folder as it was huge and of no consequence as to what we are trying to accomplish. Also, to be clear, this is a dump from the Lumia 928 variant package not my actual device. Have fun!!!
http://sdrv.ms/13tlc0F
@djtonka Thank you for your tutorial on Nokia Care Suite on wimdowsmania.pl.
@AnDim Extra thanks for ImgMount Tool which was used to dump these files!!!
I'll let you know. Just for curiosity's sake, how are you extracting those files? Is it from a working device, or a ROM image?
EDIT: Just saw your message, thanks for the info!
Initial results are a mix of cautious hope, disappointment, and speculation.
1) The OEM apps use a ton of restricted capabilities (among the most tame, for example, is "ID_CAP_MEDIALIB_PHOTO_FULL", which gives direct access to the image folders and has visibility "public" according to the policy XML files from the Windows directory).
2) The OEM apps can be sideloaded, but you have to remove the PlayReady header and all the restricted capabilities. They aren't very exciting at that point; they may not even start up.
3) Speculation: The so-called "public" restricted capabilities require a (Store-?)signed app when used on a standard phone. It *may* be possible to sign the apps ourselves, install that cert on the phone, and then sideload them, but I doubt it.
4) More speculation: These new, high-privilege capabilities seem to have largely replaced ID_CAP_INTEROPSERVICES. Although the error when trying to sideload them on an interop-locked phone is different than it is for INTEROPSERVICES, it may be that an interop-unlock would allow sideloading apps that use those capabilities anyhow.
5) The OEM apps include WPInteropManifest.xml. It's exactly the same near-empty file as on WP7. However, they don't use COM but instead use the same native-CLR interop as the official SDK advocates (.winmd files that bridge managed code to C++ DLLs). Its presence does not impede sideloading.
6) Speculation: The WPInteropManifest may be needed for apps which intend to use the "raw" win32 API (as opposed to WinRT) in C++. This theory is supported by the presence of things like DLLs that read and write to the registry directly (not through a driver, which would need INTEROPSERVICES), using APIs such as RegCreateKeyW.
7) More speculation: Since we can extract the system libraries from our phones, it should be possible to use the DLL-to-LIB tools to create .LIB files (the official WP8 SDK is extremely short on these) that we can then use to link to the native Win32 API. Although we would still be (cripplingly) limited by the sandbox's low permissions, we could probably do things like write a basic registry browser.
8) The provxml commands to install apps are very simple, but I don't understand all the parameters. Nonetheless, whenever we have an app, its license, and a tool which can process AppInstall provxmls, we should be able to install those apps on any reasonably compatible phone.
9) Speculation: Due to the use of OS-based capabilities rather than OEM drivers, an app that is installed on any given phone *should* work on other OEMs' phones even if it accesses the registry or does similarly privileged operations.
10) There may yet be a vulnerable app which we could exploit (possibly by using a provxml-injection attack?) to write to the registry / move files / do similar stuff. However, it would probably have very limited permissions even so; unlike on WP7, most things which can write to *some* of the registry can't write to *most* of it.