Related
is it possible to make an already full patched(button fix,camera,bluetooth,etc) rom with all basic programs (such as mms client,stk,backlight,etc)?
i think yes but i'm not able to make it..it will be very usefull for newbies such me..
with this full rom you do not need to post lots of duplicated threads and all will works since the beginning..
yeah i would like that to,
so we only have to install it without patching and so
very good idea!!!!
but now, apart the Wiki, there is a list of all patchs that must be installed?!
'cause I don't have enough time to read alle the pages in WM5 problem resolutions thread
well,
so far, i created a project for a extended rom under wm2005.
http://wiki.xda-developers.com/index.php?pagename=BA_WM5_Extended_ROM
Butt im stuck, it will not install off the rom after a hard reset.
If this would be working we do not have to worry anymore if we forgot or lost our sd card for the neccesary patches.
i think yes
i can make a list but someone has to do that
i think tha the 'default' are:
camera fix
wm5_v3 fix
button fix
midi with album fix
missing system programs (mycpl.rar)
traylauncher
wifi programs
sim manager
and a set of default programs:
pdf reader
xscaler
pocketplus
pocketrar
etc..
I would say no, i'd rather have the choice to install what patches i want. For instance if i dont use MMS or prefer the soft keys of WM5. The way it is now you can configure the device just as you want. Getting a working extended rom you can customise would be my choice. I definitely wouldnt want Pocketplus installed by default on my device.
It has to work first.
So anybody already found a working autorun.exe and config.txt files?
I Tried alot of those two, but still not able to get it working under te extended rom after a hard reset.
efjay said:
I would say no, i'd rather have the choice to install what patches i want. For instance if i dont use MMS or prefer the soft keys of WM5. The way it is now you can configure the device just as you want. Getting a working extended rom you can customise would be my choice. I definitely wouldnt want Pocketplus installed by default on my device.
Click to expand...
Click to collapse
you don't have to use the all in one pack..
it's only the noob choise..and very easy to use..
flagg said:
efjay said:
I would say no, i'd rather have the choice to install what patches i want. For instance if i dont use MMS or prefer the soft keys of WM5. The way it is now you can configure the device just as you want. Getting a working extended rom you can customise would be my choice. I definitely wouldnt want Pocketplus installed by default on my device.
Click to expand...
Click to collapse
you don't have to use the all in one pack..
it's only the noob choise..and very easy to use..
Click to expand...
Click to collapse
Yes i dont have to use it; but if the patches are no longer released separately then i have no choice. If there is a choice of all-in-one rom and non-patched that will be ok. But you have to think of who creates the rom, it may be easier just to maintain one rom version. I guess we have to wait and see..
@pimbo have you tried the autorun from the K-Jam extended rom? May be different from the Universal files. Its here ftp://ftp.xda-developers.com/Uploads/
efjay said:
@pimbo have you tried the autorun from the K-Jam extended rom? May be different from the Universal files. Its here ftp://ftp.xda-developers.com/Uploads/
Click to expand...
Click to collapse
Not yet, preparing my device now, autorun is 17kb from this one
setup is 104kb, looks common, exept the dates are a bit older.
Manually launching the autorun of files on the extended rom will work, so i guess that i have to do a hardreset again, thats what i going to do later the evening. lol 8)
:evil: :evil:
No luck. wil not automaticly run.
Still need to make the rom visible and run the autorun.exe for the installs.
But this is the nearest solution for now i guess.
So you still need a single cabfile on a sd card to unhide your rom and install all files on there.
If anybody knows the bytes to change in the nbk or nbf files or maybe in the bootstrap, the adaption could be completed and the patches would automaticly install after a hardreset. .
please don't OT
...so
dev can make all in one rom and single patch
flagg said:
i think yes
i can make a list but someone has to do that
i think tha the 'default' are:
camera fix
wm5_v3 fix
button fix
midi with album fix
missing system programs (mycpl.rar)
traylauncher
wifi programs
sim manager
Click to expand...
Click to collapse
ok!!!!
From the Wiki...
camera fix [Camera2K5_v1.rar]
wm5_v3 fix [ba_wm5_fix_v3.rar]
button fix [Buttons_Fix_v2.rar]
midi with album fix [Album with midi.rar]
-------------------------------------------------
traylauncher [http://www.phm.lu/Products/PocketPC/PowerToys/]
sim manager [ftp://xda-developers.com/Uploads/Blueangel/wm5_test/AsukalSIMManger.cab]
missing system programs [mycpl.rar --> ftp://xda-developers.com/BlueAngel/BA_WM5/Patches/Old Patches/mycpl.rar]
wifi programs [ftp://xda-developers.com/BlueAngel/Programs/WIFI/Retina digital security/RetinaWiFiPoc.exe]
right?!
i for one would love an all encompassing rom patch. reading through all the duplicate posts and other resolutions is a real hassle for noobs. we see the same questions being asked every 3 days or so and it just creates more clutter for the other noobs to sift through. i figure a lot of those fixes should be included in the next patch of the current wm5 rom anyhow if people rather wait for that to come around.
Closer said:
flagg said:
i think yes
i can make a list but someone has to do that
i think tha the 'default' are:
camera fix
wm5_v3 fix
button fix
midi with album fix
missing system programs (mycpl.rar)
traylauncher
wifi programs
sim manager
Click to expand...
Click to collapse
ok!!!!
From the Wiki...
camera fix [Camera2K5_v1.rar]
wm5_v3 fix [ba_wm5_fix_v3.rar]
button fix [Buttons_Fix_v2.rar]
midi with album fix [Album with midi.rar]
-------------------------------------------------
traylauncher [http://www.phm.lu/Products/PocketPC/PowerToys/]
sim manager [ftp://xda-developers.com/Uploads/Blueangel/wm5_test/AsukalSIMManger.cab]
missing system programs [mycpl.rar --> ftp://xda-developers.com/BlueAngel/BA_WM5/Patches/Old Patches/mycpl.rar]
wifi programs [ftp://xda-developers.com/BlueAngel/Programs/WIFI/Retina digital security/RetinaWiFiPoc.exe]
right?!
Click to expand...
Click to collapse
nice job..so we have only to wait maimac or someone else..
we are all noob..we are all waiting for you :lol:
if ppl want to install single patch one by one they can do that
but i think that for noobs this is such as an "official" rom
tested and approved from xda devs
please try to create folder named 2577 in your extrom and place autorun in that folder.
it should be executed automatically...
buzz
buzz_lightyear said:
please try to create folder named 2577 in your extrom and place autorun in that folder.
it should be executed automatically...
buzz
Click to expand...
Click to collapse
did not work, did the autorun in a folder called 2577. cab files on the root.
did a hard reset, but would still not install.
The screen of the 3sec before install wont pop up
But after i made my extended rom visible, it automaticly runs after a soft reset.(the 3sec screen pops up )
(last problem?)
But i'm going to get some sleep now, maybe that will help a bit :shock:
flagg said:
nice job..so we have only to wait maimac or someone else..
Click to expand...
Click to collapse
OK! now I'm ready to flash with Mamaich Patch 3 ..
buzz_lightyear said:
please try to create folder named 2577 in your extrom and place autorun in that folder.
it should be executed automatically...
Click to expand...
Click to collapse
This would not work. WM5 on BA lacks registry settings and driver for the extended_rom folder.
mamaich said:
buzz_lightyear said:
please try to create folder named 2577 in your extrom and place autorun in that folder.
it should be executed automatically...
Click to expand...
Click to collapse
This would not work. WM5 on BA lacks registry settings and driver for the extended_rom folder.
Click to expand...
Click to collapse
ok, then put that folder on your SD card.
buzz
I have uploaded a greek rom file for the htc wizard.
This ROM has a second level of protection that can not be bypassed only by CIDunlocking a phone.
After installing the ROM, uppon second boot (first boot installs ext rom then restarts) it displays a message
"This rom is intended only for devices sold by ace hellas" and freezes.
I think it searches for a valid IMEI range but I am not sure.
I am trying to find the exe file responsible for locking up the phone (using WM5 editing tools my maimach) but I have no luck yet. If someone could lend a hand I would be gratefull. Even giving me a hint (like how to edit the registry from a dumped ROM etc.)
Anyway, the file is located here.
http://dcom.teipir.gr/RUU_Prodigy_10107105_Qtek_WWE_ship_GR1.04.exe
Thanks in advance
Below, you can find instructions to customize smartdialing for recognizing characters for any language
My best man has the EXACT same problem with his Universal.
We haven't uploaded the firmware yet but can easily be downloaded through qtek.gr.
Can someone help?
It's a pitty not to be able to use the device just because he bought it outside Greece.
It's an interesting challenge after all.
Andrew, maybe you can send me a PM with what you have tried yet.
Re: I have a challenge for the xda-gurus
andrew_sh said:
After installing the ROM, uppon second boot (first boot installs ext rom then restarts) it displays a message
"This rom is intended only for devices sold by ace hellas" and freezes.
Click to expand...
Click to collapse
Check your Extended_ROM files. They might be what you are looking for. Probable workaround might be soft-resetting your device before extended_rom files are being installed, i.e. hard-reset your device now and immediately soft-reset it when you will see message "Customizing will start in 3 sec..." or something like that...
I think it searches for a valid IMEI range but I am not sure.
Click to expand...
Click to collapse
The IMEI is stored in registry within "RIL" branch, but your IMEI is not touched within traditional flashing/reflashing
A Russian fellow had done this job last year, for the S100 Greek Rom (Anansky i think was his name). The lock is not on the extended rom, but on the main OS. And if i remember well, it has an IMEI checking ytility, and another one which checks Language settings for the Language selection utility to work, but this can be changed with registry hack. Well, we are all waiting...
Re: I have a challenge for the xda-gurus
IMate->WM2k5 said:
andrew_sh said:
After installing the ROM, uppon second boot (first boot installs ext rom then restarts) it displays a message
"This rom is intended only for devices sold by ace hellas" and freezes.
Click to expand...
Click to collapse
Check your Extended_ROM files. They might be what you are looking for. Probable workaround might be soft-resetting your device before extended_rom files are being installed, i.e. hard-reset your device now and immediately soft-reset it when you will see message "Customizing will start in 3 sec..." or something like that...
I think it searches for a valid IMEI range but I am not sure.
Click to expand...
Click to collapse
The IMEI is stored in registry within "RIL" branch, but your IMEI is not touched within traditional flashing/reflashing
Click to expand...
Click to collapse
no it's not in extended ROM at least for the Universal (and sorry for posting in Wizard forum) - we tried your method from the first moment
1. No, extended rom has nothing to do with it , for sure.
2. Yes, anansky has done it before for the htc magician (my previous phone) but never revealed a howto.
@NLS
I have found a suspicious file called langbootcheck.exe which I tried deleting (with WM5 edit tools) prior to flashing my device. But then the device won't boot at all. Maybe this file is needed, or maybe I did something wrong?
If someone could at least tell me, how to edit the registry hives with the wm5 editing tools. This way I could see wich applications are executed on startup.
Re: I have a challenge for the xda-gurus
NLS said:
no it's not in extended ROM at least for the Universal (and sorry for posting in Wizard forum) - we tried your method from the first moment
Click to expand...
Click to collapse
Did you try to play with HKLM\Comm\BootCount value? To put it as 0 so it is always thinking of a just hard-resetted device?
no I didn't try that, nor the device is mine (to try)
andrew try having a 0 byte file in place of the exe - maybe it needs the file to be there but nothing to happen when it is called
maybe Ace (since I am 99.5% sure that they read xda-developers), could give us a hint on why they have done this (when nobody else did on the whole planet)...
Re: I have a challenge for the xda-gurus
IMate->WM2k5 said:
Did you try to play with HKLM\Comm\BootCount value? To put it as 0 so it is always thinking of a just hard-resetted device?
Click to expand...
Click to collapse
No, but it sounds like a good idea. That would explain why it doesn't lock up during the first boot process. But then again there is no way to change it because the os automatically reboots itself. Unless it installs a cab file from ext rom that does the trick. Do you think this might work?
NLS said:
maybe Ace (since I am 99.5% sure that they read xda-developers), could give us a hint on why they have done this (when nobody else did on the whole planet)...
Click to expand...
Click to collapse
i realy doubt it! I mean giving us a hint
I will try to replace the file with a zero-sized one. But then again I'm not even sure if it is the file responsible. I mean, that I just guessed (because the name sounded suspicious). It could be any other file. The file name could be desguized. Thats why I need to know 2 things:
1) How to edit the registry with maimach's WM5 editing tools.
2) Where is the startup configuration located i the registry
I didn't say tell us "how", I said for the to tell us "why"...
anyway...
Yeah ACE sux, well it's been really disgusting to lock the roms so we anyone who want Greek language to buy only from em. ACE think theirselves smart enough and all the other like Russian, italian, norwegian, dutch and many more who have their Qtek rom unlocked are the "stupid"...
Anyway this is a different story..
I am available to help in any way but i'm not such an expert user as you to play with the editing tools.
P.S:I see the rom is uploaded on a TEI of Piraieus server, you have any connection with teipir? I'm in the Automation.
bill_viper said:
P.S:I see the rom is uploaded on a TEI of Piraieus server, you have any connection with teipir? I'm in the Automation.
Click to expand...
Click to collapse
I'm in automation dept too! PM me!
NOone? :!: Buzz? Come on, you will make many people happy!!!!
I don't want to sound nagging but it must be very easy for you!!
I found another approach to our problem.
Instead of trying to hack the rom, I extracted some dll files needed for the greek smartdialing.
I dumped the Greek rom and followed the instructions here.
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&id=10204&catid=45
but used the Greek smartdialing.dll instead of the one posted above.
It worked very well. I even edited the smartdialing cab found on the ext rom and included the dll. So each time I hard reset the device, the smartdialing feature works for greek characters. I think the smartdialing can be customized just as easily for any other language, just as long as you find the .dll in your language. (For this, download a rom containing the language, and user WM5 editing tools found on xda-devs).
If someone needs it, I can upload the greek smartdialing cab to overwrite the one in your ext rom (for wizard only).
I also use AEKMAP for the internal qwerty and I find it very stable, simple and small.
So I guess there is no much point in hacking the greek rom (unless someone wants the menus customized - I don't).
how did you dumped the greek rom ?
andrew_sh said:
I found another approach to our problem.
Instead of trying to hack the rom, I extracted some dll files needed for the greek smartdialing.
I dumped the Greek rom and followed the instructions here.
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&id=10204&catid=45
but used the Greek smartdialing.dll instead of the one posted above.
I also use AEKMAP for the internal qwerty and I find it very stable, simple and small.
So I guess there is no much point in hacking the greek rom (unless someone wants the menus customized - I don't).
Click to expand...
Click to collapse
Awesome idea.... is there any way i can get my hands on that .cab file? And maybe on your .aek greek layout? because mine kinda sucks
Anywho, i see we are off to a good start here fellas, don't worry answers will come soon enough.
I'm trying to customize a few Extended ROMs here and I'm running into some stubborn CABs. When installed manually, everything works fine. No warnings, no errors. Just click the CAB, let it do its thing, then click OK.
Put these same ROMs into an Extended ROM and hilarity ensues. Some will work, others will not and I don't know why. Any suggestions on what I might be missing will be greatly appreciated.
Quick question?
Are the CAB's signed, if not are you installing the 'signed' unsign CAB 1st .
Edit: Thinking more about this (and realising that the 1st thing you do is disable signing in your ROM's ) can you provide a little more info about the CAB's (maybe an offending CAB if the content is not private?).
I managed to replicate this issue with a CAB that had a warm reset as part of it's install process (seems to bork the autoexec batch process) and I have had a similar issue with a CAB that just contained some simple OMA in the _setup.xml.
John
yes, that's the point. But how to make any Unsigned CABs become Signed?
huangyz said:
yes, that's the point. But how to make any Unsigned CABs become Signed?
Click to expand...
Click to collapse
Without wanting to sounds facetious you sign them ;-)
You would use a private key to generate an Authenticode signature for the CAB (and maybe the apps inside if you need to) however you would still need to install the ROOT certificate into the code stores on your device. Or get your app signed by a 3rd party with a certificate that has it's ROOT already on the device (MS's MobileToMarket and things like that take care of this for ISV's that need it).
Once you have the ROOT cert on the device in the correct store signing is trivial, you either use SignTool.exe from many of the MS SDK’s or just use the GUI options if Visual Studio is your poison. All you need is an export of the PKF (Private key) and the password to the certificate.
In enterprises one of the 1st things people often do before giving Windows Mobile devices out to users is to install a ROOT certificate for the enterprise onto the device in both the code and transmission stores. This means from then on you can sign in-house apps and CAB’s and they behave as signed commercial apps and you can use features like internal signed SSL for ActiveSync etc. etc.
Don’t forget you can also do away with a lot of this by installing the HTC signed “Disable Certificates” CAB 1st and then the signatures are not checked on subsequent CAB’s, EXE’s or anything code related for that matter.
djwillis said:
huangyz said:
yes, that's the point. But how to make any Unsigned CABs become Signed?
Click to expand...
Click to collapse
Without wanting to sounds facetious you sign them ;-)
You would use a private key to generate an Authenticode signature for the CAB (and maybe the apps inside if you need to) however you would still need to install the ROOT certificate into the code stores on your device. Or get your app signed by a 3rd party with a certificate that has it's ROOT already on the device (MS's MobileToMarket and things like that take care of this for ISV's that need it).
Once you have the ROOT cert on the device in the correct store signing is trivial, you either use SignTool.exe from many of the MS SDK’s or just use the GUI options if Visual Studio is your poison. All you need is an export of the PKF (Private key) and the password to the certificate.
In enterprises one of the 1st things people often do before giving Windows Mobile devices out to users is to install a ROOT certificate for the enterprise onto the device in both the code and transmission stores. This means from then on you can sign in-house apps and CAB’s and they behave as signed commercial apps and you can use features like internal signed SSL for ActiveSync etc. etc.
Don’t forget you can also do away with a lot of this by installing the HTC signed “Disable Certificates” CAB 1st and then the signatures are not checked on subsequent CAB’s, EXE’s or anything code related for that matter.
Click to expand...
Click to collapse
I am NOT a software developer so, most of your opinions sound enigmatic to me except that the last one: put the HTC signed "Disable Cert" in the 1st place of the ext-rom config.txt.
Thanks very much! I'll try later on.
gamescan said:
I'm trying to customize a few Extended ROMs here and I'm running into some stubborn CABs. When installed manually, everything works fine. No warnings, no errors. Just click the CAB, let it do its thing, then click OK.
Put these same ROMs into an Extended ROM and hilarity ensues. Some will work, others will not and I don't know why. Any suggestions on what I might be missing will be greatly appreciated.
Click to expand...
Click to collapse
most problably you forgot to set some cab file to read-only before saving the extende-rom.check the cabs atrebutes and the config.text file while inside de program that you are using to edit the extended-rom.its not because they are not signed as long you got the cert .cab set to be the first to be installed.also cab files that require user input will not work.this is from experience, as posted above.
huangyz said:
I am NOT a software developer so, most of your opinions sound enigmatic to me except that the last one: put the HTC signed "Disable Cert" in the 1st place of the ext-rom config.txt.
Thanks very much! I'll try later on.
Click to expand...
Click to collapse
So, where did you found the signed Disable_Cert.cab?
faria said:
most problably you forgot to set some cab file to read-only before saving the extende-rom.check the cabs atrebutes and the config.text file while inside de program that you are using to edit the extended-rom.its not because they are not signed as long you got the cert .cab set to be the first to be installed.also cab files that require user input will not work.this is from experience, as posted above.
Click to expand...
Click to collapse
Sorry to ping an old thread - flogging to proceed immedietly after...
Being that this is a windows device, isn't there a flag that can be passed when executing the cab - like you can on a windows installer application? Similar to setup.exe -q or whatever you're trying to do. Some flags set the answers to yes, admin mode... you get the picture. Does the cab installer engine allow similar flags to get passed with the cab execution command?
In PPC, it calls wceload.exe to install and uninstall a cab.
As shown in http://msdn2.microsoft.com/en-us/library/ms926281.aspx , the only possible argument is to ask or not ask for destination, but no quiet mode.
How can you call wceload.exe manually at ExtROM installation may be a question.
Guys,
I have a requirement to provide a level of security on some corporate 8100/8125 devices.
I've proved that by implementing a couple of registry changes I can disable the SD and Camera devices which is exactly what I want to do.
The problem is that if a user Hard Resets the device and applies the customizations those registry changes are lost.
I've been told that I could put the registry changes into CAB files and install them in the Extended ROM, this way each time the user performs a hard reset the reg changes will be re-applied.
If someone has detailed instructions on how I could do that I'd be grateful.
Thanks
acowx said:
Guys,
I have a requirement to provide a level of security on some corporate 8100/8125 devices.
I've proved that by implementing a couple of registry changes I can disable the SD and Camera devices which is exactly what I want to do.
The problem is that if a user Hard Resets the device and applies the customizations those registry changes are lost.
I've been told that I could put the registry changes into CAB files and install them in the Extended ROM, this way each time the user performs a hard reset the reg changes will be re-applied.
If someone has detailed instructions on how I could do that I'd be grateful.
Thanks
Click to expand...
Click to collapse
How "secure" do you want this to be? A determined user could install a registry editor and re-enable the reg options you disable. If your users are sales and marketing folks, then they probably don't have the technical aptitude required to do such things (jk!), but if there's a desire, there's a way.
A slightly more secure way would be to not only disable the reg keys, but also remove the camera app and drivers and SD drivers from the OS. This requires building a custom ROM, which I could probably throw together for you relatively quickly.
If removing the reg entris is enough to satisfy you, you can create a cab file using wince cab manager or the cabwiz from Visual Studio. This could be placed into an extended ROM image which you can flash to the devices. I can do that for you as well, or you can look through the posts here regarding custom ext roms.
to do this you need to build a custom extended rom there is a whole post for this it is called home cooked roms how to http://forum.xda-developers.com/viewtopic.php?t=52564&highlight= you will need the tools on there as well as wince cab manager which costs a little bit to buy or you can use the trial version but it expires quick so make sure you have the time to figure out what you are doing before you go through starting to do it and here are the tools http://forum.xda-developers.com/viewtopic.php?t=54563&highlight=extended+rom
this should pretty much get you started all you need to do is take the files already in the extended rom and add your cab file to it and update the auto execute file the lists all the items to be automatically executed and then repack it and flash the extended rom to the phone and then hard reset then they should be applied
summiter said:
acowx said:
Guys,
I have a requirement to provide a level of security on some corporate 8100/8125 devices.
I've proved that by implementing a couple of registry changes I can disable the SD and Camera devices which is exactly what I want to do.
The problem is that if a user Hard Resets the device and applies the customizations those registry changes are lost.
I've been told that I could put the registry changes into CAB files and install them in the Extended ROM, this way each time the user performs a hard reset the reg changes will be re-applied.
If someone has detailed instructions on how I could do that I'd be grateful.
Thanks
Click to expand...
Click to collapse
How "secure" do you want this to be? A determined user could install a registry editor and re-enable the reg options you disable. If your users are sales and marketing folks, then they probably don't have the technical aptitude required to do such things (jk!), but if there's a desire, there's a way.
A slightly more secure way would be to not only disable the reg keys, but also remove the camera app and drivers and SD drivers from the OS. This requires building a custom ROM, which I could probably throw together for you relatively quickly.
If removing the reg entris is enough to satisfy you, you can create a cab file using wince cab manager or the cabwiz from Visual Studio. This could be placed into an extended ROM image which you can flash to the devices. I can do that for you as well, or you can look through the posts here regarding custom ext roms.
Click to expand...
Click to collapse
Hey, thanks for the speedy response.. from the top man in the forum too !
Given your comment about users being able to re-enable the reg settings I think you're right and I'd be grateful if you could produce a custom ROM based on the 2.25 ROM that Cingular provided for the 8100/8125 with all Camera and SD functions removed (and no other customizations)
In the meantime I'll trawl the documentation on here to work out how I can do this myself given.
Thanks man !
acowx said:
summiter said:
acowx said:
Guys,
I have a requirement to provide a level of security on some corporate 8100/8125 devices.
I've proved that by implementing a couple of registry changes I can disable the SD and Camera devices which is exactly what I want to do.
The problem is that if a user Hard Resets the device and applies the customizations those registry changes are lost.
I've been told that I could put the registry changes into CAB files and install them in the Extended ROM, this way each time the user performs a hard reset the reg changes will be re-applied.
If someone has detailed instructions on how I could do that I'd be grateful.
Thanks
Click to expand...
Click to collapse
How "secure" do you want this to be? A determined user could install a registry editor and re-enable the reg options you disable. If your users are sales and marketing folks, then they probably don't have the technical aptitude required to do such things (jk!), but if there's a desire, there's a way.
A slightly more secure way would be to not only disable the reg keys, but also remove the camera app and drivers and SD drivers from the OS. This requires building a custom ROM, which I could probably throw together for you relatively quickly.
If removing the reg entris is enough to satisfy you, you can create a cab file using wince cab manager or the cabwiz from Visual Studio. This could be placed into an extended ROM image which you can flash to the devices. I can do that for you as well, or you can look through the posts here regarding custom ext roms.
Click to expand...
Click to collapse
Hey, thanks for the speedy response.. from the top man in the forum too !
Given your comment about users being able to re-enable the reg settings I think you're right and I'd be grateful if you could produce a custom ROM based on the 2.25 ROM that Cingular provided for the 8100/8125 with all Camera and SD functions removed (and no other customizations)
In the meantime I'll trawl the documentation on here to work out how I can do this myself given.
Thanks man !
Click to expand...
Click to collapse
No worries - can you PM me a little reminder? I'll look into this tomorrow.
I'd like to start building my own ROMs.
I have now read two massive articles on how to do this. Two hours later I do not have a clue what either of them was on about.
Here is how I would expect the process to work. Roughly.
1. Get OS base files
2. Get device-specific kernel
3. Get device drivers
4. Get important apps and files to cook with ROM
5. Get less important apps and files to add in customisation
6. Set reg keys and provision XMLs
Then I'd expect at least one tutorial or page of notes which goes something like:
"First get a kitchen. Popular visual kitchens include Ervius Visual Kitchen and OSKitchen. This example talks about Ervius Visual Kitchen. There is a predefined hierarchy which you must use to build your ROM. The Tools folder is for [...], so you [...] to change the files there. To build a ROM for your device you need to first [...], the OS base files for a given OS can typically be found be searching for something like [...], and the kernel by searching for [...]. Don't forget to [...]. There is a comprehensive list of apps available as packages here on XDA at [...]. To add an app to your kitchen you'll need to either find or make a packaged version. More about packages here [...]. Packages [...] be made from CAB files. Here is a list of bullet points that you need to work through [...]. If you flash your ROM and the device fails to boot [...]."
As it is all the tutorials are assume you already know everything and skew off on more tangents than a kid with an electric spyrograph.
I get that some people have tried to write tutorials. I haven't found one yet though that's was worth the hour or more it took to read. All I've learned is that you can flash the radio separately to the OS and I'm not even sure about that. Does anyone know of some decent reading material?
at45 said:
I'd like to start building my own ROMs.
I have now read two massive articles on how to do this. Two hours later I do not have a clue what either of them was on about.
Here is how I would expect the process to work. Roughly.
1. Get OS base files
2. Get device-specific kernel
3. Get device drivers
4. Get important apps and files to cook with ROM
5. Get less important apps and files to add in customisation
6. Set reg keys and provision XMLs
Then I'd expect at least one tutorial or page of notes which goes something like:
"First get a kitchen. Popular visual kitchens include Ervius Visual Kitchen and OSKitchen. This example talks about Ervius Visual Kitchen. There is a predefined hierarchy which you must use to build your ROM. The Tools folder is for [...], so you [...] to change the files there. To build a ROM for your device you need to first [...], the OS base files for a given OS can typically be found be searching for something like [...], and the kernel by searching for [...]. Don't forget to [...]. There is a comprehensive list of apps available as packages here on XDA at [...]. To add an app to your kitchen you'll need to either find or make a packaged version. More about packages here [...]. Packages [...] be made from CAB files. Here is a list of bullet points that you need to work through [...]. If you flash your ROM and the device fails to boot [...]."
As it is all the tutorials are assume you already know everything and skew off on more tangents than a kid with an electric spyrograph.
I get that some people have tried to write tutorials. I haven't found one yet though that's was worth the hour or more it took to read. All I've learned is that you can flash the radio separately to the OS and I'm not even sure about that. Does anyone know of some decent reading material?
Click to expand...
Click to collapse
Brother,I agree with you 100%. I tried to follow their tutorials and I'm as lost as ever
did you read this thread?
http://forum.xda-developers.com/showthread.php?t=548130
Why not post your queries/concerns in the tutorial threads. No need to create a new thread for this
Thread closed