make a copy of the blackberry.alx file, paste it to the desktop, edit that file, save it, drag the edited one back into the folder where it came from, drag out the original blackberry.alx file. that should work.
Well then you are going to have to elaborate on your issue. What OS are you using? Is your user account an admin account? Any other info you can provide about the issue? Any error messages? Have you checked the error log viewer in control panel for more info?
Ok, this is really simple. I've done this through and through. If you follow directions from the unlock vendor themes thread, you should be fine. On that note. Have you done any memory optimization (i.e. removed .cod's for any of the vendors?) If so, put them back. I read your above posts, but make the .alx file looks just like this http://forums.crackberry.com/f16/how...595/#post13048. Also you should open the file as a notepad or wordpad file. The best thing to do is right-click on the blackberry.alx file, open with, and search for either pad program. YOU SHOULD NOT HAVE TO DRAG/EDIT AND RE-DRAG! If it's not saving, it's your computer. So I would reboot the comp and try again. I previewed all the themes and chose have the TIM theme and it's working perfect. Obviously you're missing something.
...
If you are just changing the vendor id number instead of removing the vendor id string, then it isn't going to work.
And Reckoner has already given you a solution to saving the file.
and no Sunkast, you do not have to remove the string. I don't have the screen shot program, but I will gladly show you a copy of my blackberry.alx file proving it.
and no Sunkast, you do not have to remove the string. I don't have the screen shot program, but I will gladly show you a copy of my blackberry.alx file proving it.
That's nice, but partly accurate. Like I said, as it is posted in the unlock vendor themes you can just change the vendor code to your carrier in the string, but it has been acknowledged that it can be removed also in the same thread and by me. It's up to the user, and i guess we'll see what happens with natanz