Related
Hi - first major post so bear with me!
After 'cookin' my own extended ROM a few times, I realised that harvesting the various CABs was only the first step - I then had to trawl this (fabulously informative) forum (and wiki) and identify each CAB to see if I actually wanted it in this particular ROM – sometimes I’d find a picture (really helps), and sometimes not, either way I would always forget what something was and have to re-find it.
So I wrote a utility to help me - and I'm sharing with everybody else 'cos that's just the kinda guy I am. XtendROM scans a folder (I’m old-school so I still call ‘em directories, but I’m trying to speak windoze here) and treats that folder as the ‘library’ – it is from there one can select which CABs you want to include. I’ve set things up for the Himalaya (I have an XDAII) so the default extended ROM size is 64Mb, although it only warns you if you go over that.
The principal is simple - deliberately so. Information on the CAB files is stored in TXT files and the preview images are stored as GIFs, BMPs or JPGs (always the same name as the CAB file, with an extra file-extension). I’m thinking that we could post TXTs/images and maybe even CABs in this thread, thereby making cooking a ROM as easy as downloading the CAB/TXT/image, saving it to the ‘library’ and choosing it for your ROM.
Drag & drop should work (to some extent at least) and the ROM files can be moved up/down in the config.txt file easily enough – after all I made this for my own use and getting the information from the web-pages is sometimes the trickiest part. I’ve recently added an option to copy the selected CAB files into a separate folder, this way I can easily copy the new files into the new ROM without having to search manually (computers ARE here to make life easier – allegedly).
Um, I think that’s about it – consider this a first-release so I’ve undoubtedly missed stuff, and I’m pretty sure I’ve forgotten to save some settings into the registry (I’ve had to get on with some real work, but this version works okay – mostly). Of course, if this utility kills your system, turns into potted-plants or does anything else I’m not expecting then you’re on your own – if you have doubts then don’t use it, I ain’t getting sued just for sharing my stuff.
I'll be adding some TXTs/images/CABs here myself at some point - I'm just too busy with other stuff at the moment (patience, I'm told, is a virtue).
Any problems, comments, questions or thoughts then please post here – knowledge is a thing best shared.
:edit: - I forgot to mention above, but when a file is copied the file-extension is automatically checked and the approriate command inserted into the CONFIG.TXT - for example, copying a .EXE file will default to 'EXEC', whereas a .TXT file would generate a CPY1/CPY2 command (to copy into \Windows).
Toodz,
- StarFux -
Excellent, let's me try and I will post my feedback later.
Thank a lot.
cool program.... downloading now...
thanks
No further comments?
Just checkin'-in... so, no feedback? Must be just that good then ...
-sf
Thank you krab.. Let's me try..
Some TXT files to get things started
Attached are some TXT descriptions from xda-developers - the zip-files are named according to the username of the person who wrote the text (all credit to them, not me) - I've just compiled the data into a format that XtendROM will make use of.
yann.zip - from http://forum.xda-developers.com/viewtopic.php?t=6470
sin.zip - from http://forum.xda-developers.com/viewtopic.php?t=16916
Just unzip into your chosen library folder.
S'all - have fun.
-sf
besides of having one error on my first run .. just forgot wat it is .. i think you've done a greate job .. now its much easier to create config.txt and to avoid .. further error if i created it in notepad .. btw tnx for the tool m8 ..
...very nice looking tool )))
THANX
buzz
What a great application
Thanks for sharing
Now maybe we can create all huddle together and create a central library for all known extended ROMs so we can cook our own ExtROM
Thanks for all the positive feedback! - I'm working on some tweaks to cope with creating compressed ROMs at the moment (thanks to some great feedback) - I'll post here when I've sussed it
Thanks again!
-sf
Giving up
Hi all - well excessive demands on my time from work & home have meant I've been unable to tinker with my util, so I'm giving-up trying to find time and have decided to sleep more instead.
If anybody else wants to play with it (it's written in Delphi 7 & uses a few libraries but could be played with), then PM me and I'll send you the source so that you may continue development (if desired).
Hope everybody continues to enjoy the util anyway - L8rz.
-sf
Tried to make a copy of my ROM to SD Card. Dialog Box shows it copying but after completing in 6mins or so nothing shows on the card. I want to back up prior to copying XDA ROM and unlocking. Any advice would be appreciated.
well
you dont really need to save it on your sd card. You can just back it up in a file on your pc. click the browse button beside the combo box(ie the button with 3 dots) and select a name and a path. it would transfer the os to your pc and u can keep the back up there where its safer. :wink:
Thanks for your reply. Unfortunately I've already tried that and I just get an error message - Unsupported target filetype - don't know how to write destinationfile c:\Program Files\etc...
well
okay this is what you'll do :: put this line in the destination "c:\rom\os.nb1"; for the source select the combo box then select from device and it should work. if it doesnt then reply me asap. :roll:
Thanks again but unfortunately entering c:\rom\os.nb1 in the destination dialog didn't work. It returned: error opening c:\rom\os.nb1 for writing. The system cannot find the path specified. error opening target device.
Well
PS. Should also add I didn't quite understand your reference to "for the source select the combo box then select from device and it should work. if it doesnt then reply me asap
Well
PS. Should also add I didn't quite understand your reference to "for the source select the combo box then select from device and it should work. if it doesnt then reply me asap
check the image i just sent u. ull see what i asked you to click for the source.(Device Memory (current rom))
then for the destination clikc the 3 dots on its side and type in a name eg os.nb1 and lcick open. :!: :?:
Cool
Thanks, man. It looks like that's done the trick. It's currently copying. Once that's done I believe I need to load the XDA ROM to facilitate the unlock. Many thanks for your help.
David
no probs men. but i need to unlock some 2 more phones an am having a hell of a time. my bros samsung e700 and my dads hp6315. do u by any chance know how i can get that done
I wish I could reciprocate but unfortunately I don't know much about my Wallaby let alone those you've mentioned. I've just downloaded the XDA ROM and my device is not accepting it. Reading stuff on the forum to try to figure out what the problem is. Don't want to take away from your other problems with the Samsung and HP but let me know if you've heard of any problems as to why a device won't accept the XDA ROM. I'm probably doing something wrong.
Cheers for now.
okay i see you really do not know much. now all you have to do is get the special edition rom u get. then use the same program u used to backup your rom to upload the new one. i really want you to be 100% sure you have a back up. then duplicate the back up for safety reasons. Then extract the speacial edition rom. if its just the rom u got the use the program to do it. if its the whole installation u got a progamm called PROGRAMME A should open and it will guide you throught. Then i hope your phone is a wallaby/qtek 1010/ o2 xda/tmobile MDA they are all the same. else your better stop now. then why dont you lets chat i think it had be easier. yahoo ::nowoxi or msn ::[email protected]
Unfortunately, I haven't IM loaded currently. However, what you told me is a big help. I do have the MDA version of the phone so I'll try that when I get back as I have to leave right now. Thanks again and I'll keep you posted as to how it works out.
Hi nowoxi,
got a problem with OSImageTool, I did my own ROM copy but now how can I upload it to my device in case of need(mine is 2020..)? Do I need a SD card or I can do it directly from the xda image program? Many thanks
P.S. if you find a Yahoo mess request,well...it's me!
Didnt really get your compostition. I dont know where to start from or what to think. I know you have a problem and i know its with the ostool but i really dont get (understand) what your problem is. The rom u said u have. is it one you cooked up or the one on your phone before. then wher edo u wanna send stuff to. your phone or you wanna backup the one on your phone :?:
Sorry for the confusion, here's the story.
I'm the owner of an Orange SPV m1000, I received it last week and don't know much about PocketPC....my device is an English version, I'd like to convert it to an Italian one. I found an ITA ROM (it's for Qtek 2020 but it should work..) and soon I'd like to try to flash it. In case of need (maybe something wrong in the flashing...) I'd like to keep a copy of the original ROM installed in my device so I used XDAtools to get one, as you explained in this thread. Now I have this .nb1 file in my pc and the question is: can I upload it from my pc directly in case something goes wrong during the upgrade flashing? Or should I copy the .nb1 file to the SD card first and then try to flash from it ( but in what way?) ? Hope to made it clear now, thanks to your help!
P.S. Still looking the forum for a guide on using the imagetool....please be patient :wink:
Well you can restore it directly from your pc. just follow the steps in the thread. for source instead of selecting something in the combo box. click the 3 dots at the side then use your phone as destination. i hope that helps you out.
Sure thing!
Just one more question: what happen after I have finished upload the .bf1 file to my device with imagetools? It's a kind of autostart procedure or do I have to make some move? Thanks again, bye from Italy
nowoxi
I'm back and about to try to load the XDA ROM based on your instructions. However, question: do I have to removed the existing ROM from my device or will the XDA ROM simply overwrite it?
Hope you're around this Sunday evening/Monday morning!
Cheers
The rom will be overwritten.
finally i got the most turn off things i faced in 2005 to back me up to 2003 but after i installed 2005 for the 4th time & desided to stick with it untill i either solve the problem or microsoft will post solution
1. Etisalat Settings for mnet & MMS
(everytime you install them they somehow crash the original DB of messaging where you will not be able to open your mesages anymore untill you do a format
2. and most importantly Arabic reading writing
after long time spent to fix those problems i finally got them working, see screen shoots
yeah ok , great but how u fixed the issues ?
lol am sorry it was a bit hard, & even worse to explain, i writing down something that might help people around doing it once i find an easy way to make it accesseble to people
Rabia said:
lol am sorry it was a bit hard, & even worse to explain, i writing down something that might help people around doing it once i find an easy way to make it accesseble to people
Click to expand...
Click to collapse
Post a cab or tell us what you modified in the registry!!!
Waiting, thanks! :?
Oh something else I noticed the radio rom is 1.08.00, can you dump it?
PC) folder, take a copy of your registry after pasting the file & before softreseting the the device, then reset your device, if it will ask you then if you want to run few DLL files acept all of them, then take another copy of your registry & store it in a differant file, now go to your programs & you'll find arabizer file there in which one of them is english name, another one is arabic as '7ayarat & the 3rd one is arabic letters but mirrored in reverse, this will be always your indication if arabic is now working fine, click on this file, it will load couple of other DLLs but will give you some error message about an AOP????? file, don't mind it, now got to your control panel, (Setting) of your mobile & go to the settings Tab, again it will ask you to load some file.cpl say yes, soft reset your device with a software for soft reset not through the pen, then it will load, if you get an error about some file couldn't be loaded just reset few times & it should work, if you lost you signal in gsm, load the first registry file & softreset your mobile again, it will ask you to load some dll file again accept them then go to the settings to load the cpl file, then reset , if this doesn't work load the second resitry file & do the same proccess untill the file with the names reversed is corrected, now enjoy arabic on your system.
اود التنبية على انني لست مسؤلا عن اي مشكلة تطرأ على جهازك و العملية متعبة جدا
PS. if some get this way working for him i please him to put it in a simplified way because unfortunatly i have too little time to spare on rewriting it in an organized way, but once it worked i had to post it here because this is the best site in the world for PPC's & they deserve the best
Thanks mate I'll give a try later on
now that's interesting , thank u
anyone tried it guys am intrested to know
i think the secret is in the registry integrity & the file loading proccess, if you load the arabic files first after reseting the device they will affect the memory or the gsm loading, specifically the file CPROG.EXE which don't get loaded correctly, actually this is how i found i can fix arabic if i only get it loading after cprog & not before, thats why you put the files manually without the setup file so after you reset the device & when it asks you to load the dll files it will insert it in the registry after loading the cprog not before
guys i heared someone tried it withought backing up the registry & it worked perfectly fine, remaining only is the camera & record button & this should be it for me
i think the camera is the last problem , buttons are working fine 8)
Rabia said:
anyone tried it guys am intrested to know
i think the secret is in the registry integrity & the file loading proccess, if you load the arabic files first after reseting the device they will affect the memory or the gsm loading, specifically the file CPROG.EXE which don't get loaded correctly, actually this is how i found i can fix arabic if i only get it loading after cprog & not before, thats why you put the files manually without the setup file so after you reset the device & when it asks you to load the dll files it will insert it in the registry after loading the cprog not before
Click to expand...
Click to collapse
sadly it didnt work for me,the device kept hangings on the splash screen,I tried it with wireless on and off, i did hard reset 5 times (2 with clear registery option) but nothing worked,I also upgraded to Radio 1.17 but still didnt work,I couldnt find out what's going wrong (I get prompt to overwrite 3 files while copying them into windows folder) WM2005 1.50h, Radio 1.14 then 1.17
well am not sure but regarding the hard reset only do the clear registry hive option without the format,
hi guys!
we are working for the localize Himlaya WM5.0 to Chinese and Japnese.
On the previouse OS, we need Font and registry, and also need wince.nls which support to encoding to our languages.
without replacement wince.nls, the inbox and IE cant encode to ours.
Usual, we got the wince.nls which has our lamguge support from the device of Japanese or chinese, or take from SDK emulator, or make it ourseleves with MS Platform Builder.
Till the version of WM2003se, easy to replce it.
But new OS of WM5.0, replacement of wince.nls can not be effected, even it was replaced firmly. the OS seems to be ignor that!
@On the Himalaya WM5.0, Some version such like 1.6b, 1.6h, 1.6i can get encooding with new wince.nls, but other version of WM5.0, it was not be able...cant find the reason yet.
@On the Blue Angel WM5.0, also it was ignored by OS
@On the Jasjar just we got, also it was ignored..........
We need find some solution of this system which ignore the replacement of wince.nls.
i already work for that more than 5days ........
I think to localize to Alabian, you guys will have same problems.
Example some of you can replace wince.nls, some of you can not get it.
so if you got some information, please exchange it about that, of course we also let you know if we got it!
Thanks guys!
following is our thread about localize to Chinese / Japanese..
You may know what happened on new OS.
http://forum.xda-developers.com/viewtopic.php?t=24781&highlight=
here it is guys
did it
check it out
http://forum.xda-developers.com/viewtopic.php?p=160111#160111
1.6c
yes. I am using WM5 1.60C WWE, I can not replace the wince.nls in rom with new one.
this is again a simplified version of installing arabic in your WM2005, just install both attached cabs in there sequence & everthing should be working fine
PS am not resposible if it crashes your device but so far it haven't crashed min
to Replacement wince.nls
PLS install this cab,
and place your wince.nls onto \Temp folder
then soft reset. you can replace wince.nls
<exactry saying, not relace.enable to read wince.nls from \Temp frolder>
Rabia, what's so different about your arabizer version?
ramram said:
Rabia, what's so different about your arabizer version?
Click to expand...
Click to collapse
its the same as my earlier version but before people comlaint about arabic keyboard not getting installed & the need of using a 3rd party arabic keyboard for it to work, also some people had trouble over writing few files & so HOPFULLY this makes the installation far more easier untill Mr Imaginet company decides to develop a fully intergrated 2005 arabizer
Imaginet already created the arabizer for 5.0, but they didn't release it yet as you can see in the JasJar arabized version, we have a new built of arabizer
http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=0&dl_id=538
It's for the Diamond, but assuming it works on the Raph, Da_G, can you work your magic and integrate whatever's needed from here into your kitchen(s)?
OEM_Misc.dll
Extracted Diamond_audioplayback.exe contents, verified _Setup.xml, Platformxxx.reg and CM_Entries.xml:
- No registry changes
- Attached file is copied to .\Windows folder on device
Place file in .\OEM\OEMDrivers if cooking in kitchen.
Cheers,
Thanks -- trying it in my own ROM now ...
hilaireg is way ahead of me
ill check it out when i get home from the hospital! sounds good
Super-newbie question: What did you use to extract it from the EXE?
@Da_G:
Figured your queue was full enough as it is
@Wordsmith9091:
I used WinRAR 3.3 (IZArc 3.81 couldn't open the .EXE). Once it was extracted, I had a look at _setup.XML as it contains the short-to-long filename conversion details.
I renamed the pertinent files (previous post) and had a look at the content in those to ensure that there were no special requirements.
I used IZArc 3.81 to .ZIP up the file so that it could be posted here.
Thanks -- I learn a new trick every time I come to this site
Just tried building my ROM with it, all seems well so far, though I havne't played enough audio to test yet ...
... but I lost the ability to set button assignments other than Button-1-hold in the buttons panel -- it's like the stock behavior. Is that also controlled by this DLL?
Edit: Never mind, I'm a moron, this issue had nothing to do with this DLL
I don't think so ... the Stock HTC ROM only included "Button 1" which drives me crazy.
I've got a task on my list to deal with that I soon as I'm done some other kitchen related stuff.
I'll post up - unless someone beats me to it - once I figure out how to get button mapping.
Cheers,
I can't be 100 percent sure it's what interfered with button mapping, but it's the only thing I can think of that i've done different between builds.
Since this fix only requires a single DLL copied to the \Windows folder, I was able to cab it up using ChainFire's DriverWiz tool, and install it. I stream music via A2DP during every car ride, so I'll be able to test this on my ride home. I'll attach the cab if anyone else wants to try it as well.
You make me proud Captain
Following your lead, I have attached a .ZIP that can be used in a kitchen; to use:
Extract the .ZIP to the PACKAGES folder.
Verify that the <GUID>'s on the .DSM don't collide with ones you are currently using.
Remove the OEM_MISC.DLL from the .\OEM\OEMDrivers folder.
Cook away.
Note:
Tested on Da_G's (ERAS2R/Me) 21042 kitchen.
HTH,
HTC Diamond Hotfix..
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
... 25mins in..clean as a whistle!!
....3 albums in, job done.
Never mind on the button-mapping question. I realize what I did (I think). HAd nothing to do with this dll.
Any info you can pass my way?
hilaireg -- PMed you.
Well, I drove around for a bit after cooking this in and reflashing, and I still got some skips listening to music in Kinoma Play. Don't know if that's Kinoma's fault or if it's a symptom of the problem this is meant to address. I wasn't getting any skipping with the TF3D player even before applying this.
improvement?
I saw a noticeable improvement in the length of pauses in between my songs while streaming over A2DP (though it did get stuck on me after about 20 minutes). Its better than it was . . . I think. I don't know if there's really a scientific way to test this, really. Maybe the problem this is supposed to address isn't that at all. Maybe we need to find someone who actually KNOWS they have this problem, so we can see if the fix really helps.
Hotfix for Diamond..
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
looby said:
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
Click to expand...
Click to collapse
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Captain_Throwback said:
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Click to expand...
Click to collapse
And if he has a diamond, he could probably just install the hotfix directly from HTC
Wordsmith9091 said:
And if he has a diamond, he could probably just install the hotfix directly from HTC
Click to expand...
Click to collapse
He already tried that . . .
looby said:
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
Click to expand...
Click to collapse
Hello
[INTRO](a little background)
This is a guide for those who want to have their phone in their language but the operating system does not have it built in. You can flash a new ROM that has it or install an app right? Not so much. There are reasons for these methods to fail or simply not work for your situation. My problem was that the bootlegged hardware was not supported by the official ROMs or the Android community. This forum is also riddled with threds that started by people who need to mod something about their phone but have no technical knowhow. There wouldn't be annything wrong with that exept that the awnsers in these threds are something along the lines "Oh you just need to do this thingnemabob" that's it one sentence pointing to a technical slang word that means nothing to anyone but a seasoned developer despite first post DIRECTLY STATES IT WAS MADE BY A PERSON ASKING FOR A STEP BY STEP SOLUTION OR A LINK TO A TUTORIAL!
[pre-procedure]
List of necessary software:
Zipsigner (this goes on your phone)
ADB
text editor of choice( notepad++ recommended)
AIO-Flasher
smali/backsmali (depeding on wether your system files are odexed more on that later)
APKstudio
[installing above software]
Zipsigner
Why you need it?
As you modify your apk files their signature changes. Basically if you change anything about them the phone will no longer recognise these as "its" therfor you need to convince your phone that these are in fact okay with zipsigner.
how to install?
This is an app. If you ever installed anything from Google playstore before than you know how to install it. Go to your Google play store app on your phone. Search for Zipsigner and pick the top app. Agree to all the demands and tap on install
ADB
why you need it?
this is a command line piece of software. these might be very scary to use but don't worry follow the tutorial and you'll be okay. That aside what is it used for. ADB is a powerful tool but we will use it only to copy and paste files to and from Phone
how to install it?
ADB comes packed up with Android Development Kit so the easiest way to install it is to get the ADK
[STEP 1]
Okay so you want to translate your phone for one reason or another. Make backup! Backups are important. You want to have something when you fail to fall back on. Yes "When" you fail. Not "if" you fail. You will screw up but as long as you have a proper backup everything is okay.
You can back up your phone in few different ways.
Hello
[INTRO] (skip if you are not interrested in fluff)
For the past week I lived in Android Hell looking for what I thought would be a simple procedure and I wanted to share my expieriences somewhere so that no one else has to go through this flustrating expierience.
I got two phones (Galaxy S5 and Galaxy S5 mini)and I was taked with translating them. Well It should not be a problem I thought because it should be as easy as going into [settings]>>[region and langages] and choosing Polish. There is no Polish. So that was my first step towards the translating thiese.
[STEP 1]
First thing first backup. I am by no means a talented programmer or modder so I went with Samsung Kies but software didn't recognise neither phone. After fiddling with drivers and a back-and-forth with samsung costumer support we came to conclusion that phones are fake. IMEI of one identifies it as a Blackberry and other as Nokia >_< well okay they still have some sort of Android so there should be a way to translate them anyway. First thing on the agenda is still backup. So I went through a triall and error to get both roms dumped. I was successful with ANDROID AIO FLASHER which was a godsend after I failed time and again to push romdump's INSTALL into the phone. I managed to get one ROM off by now but other Phone still insists on denying me ability to dump the rom because of Segmentation error. but at least I have one rom backed up.
[STEP 2]
Okay I got myself ROM now what? I decided to make a transfusion. Why bother with getting down and dirty when you can just use the work of others. So I downloaded a ROM with same version of the Android OS and begun looking for language pack or something similar. No luck this is not how Android works. After some research I came to the conclusion that in order to make things work I need to basically decompile each and every APK file that refers to system functionality and translate Strings.xml by hand in order to ensure compatibility.
[PRESENT DAY]
this is where I am now. all I wonder if there is a way to add a new file in the APKs with polish in it or should I just translate English "strings.xml" file and set langage to english?
Feel free to point out faults in my logic as well as provide tips and tricks for those of us who bought our phones on the cheap and just want to usethem with language they are comfortable with. I will build up this topic with factual information that I come across and try to make this into a universal guide to Android translation with resources to download. I do this because no one should be subjected to this and there is no decent step by step guide on this forum just disjointed and incompleate information in posths here and there. Belive me I looked both here and Google and after two weeks of finding nothing more than a hints I want to just give back to the community all I found.