Related
hi guys,
I've been following all the different threads and topics for a while and it has been a very nice friendly place to be in.
Anyhow.. i would like to know if someone can direct me to how to make a cab file which will input all my setting, owner name, install program a, b, c, d, e, f, g and etc then will fix up the registry key and enter all the serials i have brought in the past. This way i don't have to reinstall each program (both cab and exe) again after upgrade the ROM
I'musing Black 2.5 atm and looking forward to get balck 3 today
Thanks guys
Ditto!
I think such app would be very useful for all of us beta testers
Or taster of new flavours!
Maybe our chefs already has something like this that they use!
Some are in the works
JJ and walshieau are working on projects similar to this.
JJ has "Pimp my Black" which is HTweakC on steriods and walshieau is building an app that will restore your carrier settings.
Loading apps back on are easy, as long as you sync with a PC. They never uninstall from your PC, just simply re-check the ones you want to reload on your device and there they are again.
Backup programs like SPB and Sprite have known issues between builds, as I'm sure you know since you posted as if you've read the forums on this subject. Kudos.
It would be really cool if JJ and walshieau would combine forces and make that one killer app for all customizations to be saved to a file and restored once flashed, and if a customization were to have a format or length issue, then toss an error and let the user know. (hint, program spec??? )
I keep a backup on storage card of each of the roms I've tried...just in case.....I wonder if this is misguided somehow.
Thanks.
This is my current method:
put all the cab files (inc carrier setting -offline by walshieau) in the storage card and also along with all the serial numbers in there.
I tended to do things on the go (out of the house/ no pc) so if i happened to flash my phone before i leave my house then i will be able to install all the apps back by the time i get to work. Altho it's a lengthy instalaltion process (swapping the apps, folder, serial number, folder, app, enter rego).
i actually i was going to ask so if SPB backup and other back up will not work properly right? Say, i am using black 2.5 and backup here.... then upgrade to black 3 version then if i use restore program.. it will restore me back to 2.5 instad of 3 ... is this information correct? i read it somewhere....
I used SBP backup on Black 2.0 and then flashed 2.5 and restored from the 2.0 backup. It worked and shows the new com manager skin but it reports as 2.0 in the "about" screen so I know that this isn't the right way to go. Knowing that 3.0 was comming soon and considering that the device works great I've left it this way.
When 3.0 comes out I will load my apps and data without SBP. Then after it's up I will make a backup of the fresh 3.0 installation.
i am interested in such tools too although using the Dopod D810 aka Trinity.
RemE said:
I used SBP backup on Black 2.0 and then flashed 2.5 and restored from the 2.0 backup. It worked and shows the new com manager skin but it reports as 2.0 in the "about" screen so I know that this isn't the right way to go. Knowing that 3.0 was comming soon and considering that the device works great I've left it this way.
When 3.0 comes out I will load my apps and data without SBP. Then after it's up I will make a backup of the fresh 3.0 installation.
Click to expand...
Click to collapse
I am using Sprite 5.1 and it does the backup and migration from Black 2.0 to 2.5 very well only have to redo my Wifi and Email settings, all my apps works fine. The FAQ to do it is available at Sprite's website on doing devie upgrade or OS upgrades with Sprite and WM5, works fine with WM6
Be aware that SPB Backup and Sprite Backup cant restore backups on different ROM's. Mobile Backup 2007 says it can but I havent tried it yet..
Dunno if I can post the follwing link but its the place you can get Mobile Backup:
http://www.ipmart-forum.com/showthread.php?t=157755&highlight=mobile+backup
I have Sprite but last time I used it on WM5 after a hard reset, it would not restore my data So I dumped it and went with SPB which has worked flawlessly ever since. I just don't see how any backup would work properly when restoring onto a different rom, I got away with it but I know that it's not 100% right now.
i was thinking of making my own cab file where specific to install
A, B, C, D....... G software (cab files), then install carrier setting, patch all the serial numbers to each softwares, change the look and all the setting in WM6 to match my like... damn it sound so hard and i don't even know how to make a cab file...
is something like this possible to learn?
I am slowly reducing the number of cabs I need to keep on my storage card by combining and creating them with my set ups.
As I have limited knowledge, this involves using sktracker to see exactly what changes were made in the registry when I changed a setting, and then using cabmanager to create a cab containing the reg settings (or say for spb weather, adding the changes to the original cab).
I understand that patching in the serials is not straightforward as it is not meant to be easy by design.
Am having trouble with some settings like email account setup, but am working through others.
crazyC: Im having the same trouble with email accounts. It doesnt look like they are saved in the registry settings, must be in the database somewhere.
Also if you add your own registry settings to the original Cab files do you know what order things are done? ie. if it writes your reg file then installs the app it might overwrite yours.
senergy said:
crazyC: Im having the same trouble with email accounts. It doesnt look like they are saved in the registry settings, must be in the database somewhere.
Also if you add your own registry settings to the original Cab files do you know what order things are done? ie. if it writes your reg file then installs the app it might overwrite yours.
Click to expand...
Click to collapse
Yeah I don't know anything about creating the database entries so am going to have to leave that.
As for the second point - I am kind of winging it so to speak, so no I don't realy know.....
As I said, am most pleased with my custom SPB weather cab, as this installs the BBC template and sets up my work and home locations as the two tabs, linking off the bbc weather source.
Have also modified the Phone Alarm cab for my skin and settings, but as there is anew beta every few days at the mo, not so useful
Am about to start work on O2 plus, and setting up my shortcuts etc on install.
looking for mobile backup 2007...is this the one
trial here
CrazyC-
been messing around with the same ideas and it's driving me crazy ha.. Do you have to manually duplicate the registry entries you want when you're adding them to the original cab file (phone alarm, for instance)?
I was trying to extract the relevant registry entries, and have a program that would let me pack them into a cab, but everything i found wanted me to manually create registry keys..
any thoughts? cause it's flashing season ha
The safest way when going between ROMs is reinstalling. I use a few techniques.
1. Install CAB files from SD card. Then you just install them one by one by tapping. Installing from Activesync can be problematic memorywise as the CAB will copy down to main memory and then be deleted after installation. This can be an issue if you have too many apps to install at once.
2. Unless the new ROM has the same device ID, email settings really have to be manually entered each time. I experimented with workarounds but they simply don't work.
3. After you install all your programs, import registry keys containing your common settings. Before erasing the previous setting, do a registry dump and then search for and find those registry keys that contain the settings. Most (but not all) are in HKEY Current User. Be careful. Don't import stuff that might break the new ROM.
4. Copy files or shortcuts from old ROM to new one. Careful though - if you are going to copy directories, use Total Commander or something. SPB Backup and WM File Explorer will REMOVE the old contents of a directory and replace it with only the stuff you have in your new copy of the directory! Total Commander only updates the new items.
5. Unfortunately, the only way to REMOVE files or registry keys (short of writing a DLL file or fancy XML?) is to manually search and delete them. I think you could probably use Mortscript to automate this but not worth the time probably unless you are flashing every day.
Between copying certain files and registries, many of my programs end up 'pre registered' on the new system. (SPB time, etc.)
Actually, I make a cab file with my preferred settings and files. I just click and go. This covers pretty much everything except email. Unfortunately the program I use cost 89$... but when I consider my billable hours, it's worth the saved time over the long run.
I can get all programs + settings in place in about 40 minutes now.
Actually, I am using visual studio 2005 and making the adjustments to the emulator image, whilst watching the registry in the remote registry viewer. Once have identified the keys, I export them as reg files and then simply import them into cabmanager.
Depends on if you have access to VS2005.
I am sure there is a simpler way, (and am happy to learn it) but as I have occassional access to VS2005, this was how I decided to do it. Am using the WM6 SDK as well of course.
Because I keep updating the Phone Alarm beta, I actually modified the cab for the VisDaPhone skin to include my modified icons, and also to install the PA export file. Just running that cab after installing Phone alarm, and then importing the theme etc works for me. I did roll it all into one on an earlier version of PA, so it all started as per my settings, but then there was a new beta......
khammo01 said:
I can get all programs + settings in place in about 40 minutes now.
Click to expand...
Click to collapse
I reckon (thanks to the exchange server) I can be back up in twenty!
If I can sort out the O2plus setup then I will reduce that as well.
I keep a word document on my sd card with a step by step guide for myself with serial numbers etc and settings.
khammo01 said:
Between copying certain files and registries, many of my programs end up 'pre registered' on the new system. (SPB time, etc.)
Actually, I make a cab file with my preferred settings and files. I just click and go. This covers pretty much everything except email. Unfortunately the program I use cost 89$... but when I consider my billable hours, it's worth the saved time over the long run.
Click to expand...
Click to collapse
do yo mind telling what's the program name/url that woul dbe?
It seems a lot of you flash your ROM on a regular basis. What stops me from doing the same is knowing I have to re-tweak so much, particularly in phone settings and adv.config. Added icon sets and themes are also an issue.
I was just wandering how some of you choose to back up your files and settings pre-flash and whether you have a kind of system in place to stream-line things. I have PPCPimBackUp, which is great for contacts and messgaes etc. but not much more it seems...
Am I missing something or do most of you just not mind starting over and adding everything back each flash?
Thanks,
S.
I have managed to survive with Sprite Backup. Just run a backup before the ROM flash and then do the restore "level one" with databases.
Remember to remove the Diamond from the cradle/USB before the new ROM boots up or else it will mess up the relationship with your PC.
Hmm interesting, I take it you have the PPC version? They seems to do a discount for HTC customers...
All I care is contact info so a basic Outlook Sync is all I need However I tried some backup utilities like PPC. After restoring a backup and you Sync with Outlook, it creates duplicate entries.
I use Sashmi, it installs all programs too
yes, SASHIMI, with a bit of work on your behalf, automates everything - install apps, settings, control panel settings, registrations etc.
More info on how to use SASHIMI with our devices here.
I want to install themes and I've read just about everything out there on this subject and still don't understand how to do it safely for this phone. There are a ton of threads on this but not one of them explains how to go about installing themes safely.
Some say just dump the .tsk files into the windows folder, others say use Diamond TF3D Config, others say not to use it because there's a version coming out specifically for the HD, others say cabs aren't as good as .theme files because you may not be able to uninstall the cab...
So I'm asking...for those of you who try out almost every theme that comes out...how are you doing it? Can you explain what you use, which types of theme files you use, how you safely change from one theme to another, and why your method is the method you choose to use?
Here are some things I've read that I'm not sure are true or not (please confirm/reject if you know):
-xxx.tsk files are a type of theme file you need to put in the Application folder and are only good for the "top and bottom bars"
-you have to use Diamond TF3D Config to install xxx.theme files; there are 2 versions of this software, one for gsm and one for cdma; you may need to delete the "tweaks file" for this software to work; there is a new version (version 1.0) coming out specifically for the Touch HD
-some say you must install xxx.theme files into the windows directory...others say you can install them in any folder you want
-even after installing a theme, you may need to perform extra steps to fix the top and bottom bars and to have the correct background
So, I know these things, but still don't understand. What is the cleanest way to install and change themes without leaving behind clutter files...is it by using a cab, by using a zip, by using diamond tf3d config?
I'd greatly appreciate if someone experienced who's tried different methods of installing/changing themes would respond and help clarify some of these confusing details.
anybody know?
goldsfool said:
I want to install themes and I've read just about everything out there on this subject and still don't understand how to do it safely for this phone. There are a ton of threads on this but not one of them explains how to go about installing themes safely.
Some say just dump the .tsk files into the windows folder, others say use Diamond TF3D Config, others say not to use it because there's a version coming out specifically for the HD, others say cabs aren't as good as .theme files because you may not be able to uninstall the cab...
So I'm asking...for those of you who try out almost every theme that comes out...how are you doing it? Can you explain what you use, which types of theme files you use, how you safely change from one theme to another, and why your method is the method you choose to use?
Here are some things I've read that I'm not sure are true or not (please confirm/reject if you know):
-xxx.tsk files are a type of theme file you need to put in the Application folder and are only good for the "top and bottom bars"
-you have to use Diamond TF3D Config to install xxx.theme files; there are 2 versions of this software, one for gsm and one for cdma; you may need to delete the "tweaks file" for this software to work; there is a new version (version 1.0) coming out specifically for the Touch HD
-some say you must install xxx.theme files into the windows directory...others say you can install them in any folder you want
-even after installing a theme, you may need to perform extra steps to fix the top and bottom bars and to have the correct background
So, I know these things, but still don't understand. What is the cleanest way to install and change themes without leaving behind clutter files...is it by using a cab, by using a zip, by using diamond tf3d config?
I'd greatly appreciate if someone experienced who's tried different methods of installing/changing themes would respond and help clarify some of these confusing details.
Click to expand...
Click to collapse
Well it really depends on what you want to change. TSK files really only change the color of the top and bottom bars, highlights, etc. If you are referring to changing icons, transparency, etc of Manila/TouchFlo, that is a bit more involved. There are applications out there like Maxycy's TF3D Theme Maker that will assist with this. Also, like you said, there are lots of cabs floating around with customizations in them. Most, if not all cabs can be uninstalled. Your best bet if you want to start playing with your device is to get some backup software, like SPB Backup or Sprite Backup, and then playing with your device. Then you don't need to be worried about messing it up. You could just do a hard reset and then restore the backup and be back to where you were before playing around
cRaCKwHoRe said:
Well it really depends on what you want to change. TSK files really only change the color of the top and bottom bars, highlights, etc. If you are referring to changing icons, transparency, etc of Manila/TouchFlo, that is a bit more involved. There are applications out there like Maxycy's TF3D Theme Maker that will assist with this. Also, like you said, there are lots of cabs floating around with customizations in them. Most, if not all cabs can be uninstalled. Your best bet if you want to start playing with your device is to get some backup software, like SPB Backup or Sprite Backup, and then playing with your device. Then you don't need to be worried about messing it up. You could just do a hard reset and then restore the backup and be back to where you were before playing around
Click to expand...
Click to collapse
Thanks alot for your response. I have sprite backup and have made many backups but was hoping not to ever have to restore from one (afraid it won't work perfectly)...that's why I'm trying to understand all of the details. I guess my only concern is not being able to go back to a previous state EXACTLY as it was before installing a theme. From all of the methods available, what would you say is the best (not necessarily the easiest) and cleanest way to prevent random files from appearing or disappearing after installing or removing a theme?
goldsfool said:
Thanks alot for your response. I have sprite backup and have made many backups but was hoping not to ever have to restore from one (afraid it won't work perfectly)...that's why I'm trying to understand all of the details. I guess my only concern is not being able to go back to a previous state EXACTLY as it was before installing a theme. From all of the methods available, what would you say is the best (not necessarily the easiest) and cleanest way to prevent random files from appearing or disappearing after installing or removing a theme?
Click to expand...
Click to collapse
If you have Sprite Backup, do a full backup. Once you have that you can completely destroy the current setup on your phone. Once you hard-reset just execute the backup file Sprite created. When the restore comes up do a merge level 1 restore. It will put your phone back to the exact state it was before. I have done this many many times as I do craptons of testing
cRaCKwHoRe said:
If you have Sprite Backup, do a full backup. Once you have that you can completely destroy the current setup on your phone. Once you hard-reset just execute the backup file Sprite created. When the restore comes up do a merge level 1 restore. It will put your phone back to the exact state it was before. I have done this many many times as I do craptons of testing
Click to expand...
Click to collapse
Thanks man, I took a step forward and did my first manila mod last night. It's amazing...by simply taking three manila files I found in Maxycy's Theme Maker and replacing the originals with them, I now have background for all tabs and a new clock ha. I've also downloaded m9editor and Manila Editor and have a better understanding of how individual files influence the system. Thanks again for the support...who knows maybe I'll even be able to create a theme one day.
goldsfool said:
Thanks man, I took a step forward and did my first manila mod last night. It's amazing...by simply taking three manila files I found in Maxycy's Theme Maker and replacing the originals with them, I now have background for all tabs and a new clock ha. I've also downloaded m9editor and Manila Editor and have a better understanding of how individual files influence the system. Thanks again for the support...who knows maybe I'll even be able to create a theme one day.
Click to expand...
Click to collapse
See, it's easier than you think! Good job and good luck! Backups are your friend
cRaCKwHoRe said:
See, it's easier than you think! Good job and good luck! Backups are your friend
Click to expand...
Click to collapse
I was on a roll until now...I encountered my first serious problem and will need to hard reset and restore from backup. You mentioned to do a merge level 1 restore. Is this what I should do even if I have all original ROM, radio, etc? From what I've read on the Sprite website, level one is the most "complicated" level and is MOST likely to fail. However, you and others on here say to use level 1 bc it causes the LEAST problems.
My default settings are as follows:
-unchecked box for "delete all files"
-checked box for "check for corrupt registry"
-system settings restore set to "merge" instead of replace
-upgrade mode set to "personal data only" instead of merge
How come one option is set for merge and the other isn't? Should I change the upgrade mode option to merge level 1? I'm assuming this option wouldn't apply to me since I haven't upgraded anything, but I'm not sure...
[and just for information/advise: my problem occurred when I clicked on the cab for sdkcerts that came with the Max TTM program. The program worked perfectly and everything was ok until I clicked on that cab. I wanted to install custom taskbars and read that you needed sdkcerts first, so I clicked on the sdkcerts cab I just happened to find in the Max TTM folder (bad move). Ever since doing so, almost half of my programs no longer open bc it's either "missing a component or is not certified." So, long story short, don't click on the sdkcerts cab or install another sdkcerts cab after installing Max TTM bc Max TTM already has a sdkcerts cab which I'm assuming automatically installs when you install Max TTM]
EDIT: I went ahead and restored via sprite backup with the settings described above and it worked PERFECTLY...all of my contacts, appointments, programs, system settings, background, where I left off in a game, etc etc is now EXACTLY how it was at time of backup. The restoration went without any warnings or errors...I'm stunned at how perfect it went. Thanks again...
The only time you would want to do a merge level 1 restore is if you are restoring to a different rom than you backed up from. If you are restoring to the same rom that you created the backup from you can do a full, normal restore.
Just thought this might be useful to some of the newer users, a list of what I see as the most commonly asked questions, and some misunderstood terms.
What is the difference between Nand, Haret and SD:
Nand; refers to the devices internal memory, which is NAND Flash memory, and is used to hold what is commonly called 'a ROM'. It is this memory which holds the Operating System, and can be 'Flashed' to change the data on it, once flashed it is persistent in memory, meaning that if you remove all power sources it will not lose this data, this is also known as 'Non-volatile Memory'. Nand Flash refers to a specific type of Flash memory, and gets it's name from the way the memory cells are constructed.
SD; Refers to the MicroSD cards we use in our devices, these are also Nand Flash but typically have slower transfer rates than the Nand Flash we have inside the device. typically used to store data, they can also be used to store the Android OS when used with Haret installs.
Haret; often confused with SD. It actually refers to Haret.exe, which is a program used to launch Linux systems from within another OS, such as Windows Mobile, think of it as a Virtual machine system, which allows users to run another OS. In our case, Haret refers to running Android within WM, it does not replace WM in Nand ROM, it does replace it in RAM however, but only until powered down, after that WM will boot from Nand next time the device is powered on.
What is my Panel Type?:
Panel; This refers to the actual LCD panel hardware, there are 3 types in use on Kaiser, and although Type2 seems most common, there are also Types 1 and 3. When running WM the panel type is autodetected and the correct settings are used for the display, however Android has no autodetect, so we must tell the OS which type we are using at boot, in Haret installs this is done with a line in Default.txt, in Nand it is set in the NBH we use to flash the kernel and other boot files needed to run Android. Display issues such as odd pixel colouration, streaks or lines on the display, white screen when exiting sleep, and other noticeable display issues can usually be cured by changing the panel type.
Other useful terms:
NBH; This is the file extension of a file intended for flashing to Nand, most commonly used to flash WM or Android, it can also be used to flash radio or splash screen.
Bootloader/tricolour screen; Both are the same, it refers to the screen display you get if you hold the camera button, and press power, on this screen are a few useful pieces of information, device type, (e.g KAIS130), SPL version, (e.g SPL-3.29.Hard), in the bottom white area it will say 'serial' or if connected to a PC, 'usb'. Remember to remove the SD card before entering Bootloader mode, as the bootloader also scans the SD for a file called KASIimg.nbh, and will run the updater utility if one is found.
HardSPL; This is a specially designed SPL that allows us to flash the Nand with an NBH file that was not signed by HTC, it also prevents itself from being overwritten, so that it is usually possible to reflash as long as we can get into Bootloader mode, this means we can, ( usually ), recover from a bad/corrupt flash.
Build and ROM; In WM terms, a ROM usually refers to a complete, ready to install, single file NBH, custom version of WM. However with Android we do not use the single file approach, and therefore we do not usually use the term ROM. Build is what we usually call a custom Android install. This is roughly equivalent to the WM 'cooked ROM', since each build is designed and built in a particular way, and may be any of the different android 'flavours'.
Flavours; Mostly used to describe the versions of android, these are, in historical order
1.1 - un-named, released feb 2009
1.5 - Cupcake, released april 2009
1.6 - Donut, released sept 2009
2.0/2.1 - Eclair, released as 2.0, oct 2009, and as 2.1, Jan 2010
2.2 - Froyo, released may 2010
3.0 - Gingerbread, scheduled release date, sep-dec 2010.
Odex'ed: As stock, android builds are odex'ed. Odexing involves generating an odex file for each app, which slightly lowers the memory used by the system, and may also speed up execution of apps, the downside is that it is difficult to modify odexed builds in order to tweak or theme them.
DeOdex'ed: a deodexed build is one in which the odex files are moved into the apk's, which slightly increases the memory used by /system, but allows modifications and tweaks to be used.
Deodex Vs Odex: Odex uses less space in /system, boots quicker, especially the initial boot after installation, however themeing is impossible, and various tweaks and modifications probably won't work. Deodexed uses more space in /system, has a slower initial boot, subsequent boots are much quicker, but may be a little slower than odexed, theming is a lot easier, as are modifications and tweaking of the build. ( most custom builds are deodexed due to the ease of theming and modifying ).
Bootsplash/Bootanimation:
The bootsplash is the static picture that appears as soon as you boot the device, usually is stays for 20 seconds or so before being replaced by the scrolling text showing Linux is booting.
The Bootanimation is the animated screen you see after Linux has booted, and usually loops until Android is loaded.
Sim Pin/SIM lock:
SIM Pin is often confused with the SIM lock, the SIM pin is the code you have to enter before using the phone when you start it up, this code is stored on the SIM card itself, and until recently caused a lot of problems, since Android could not decode it properly, this has been fixed in some flavours, Eclair and Froyo, but is still an issue in older flavours, such as Donut.
Sim lock also known as provider lock is a method used my phone service providers to ensure that you only use their service by locking the phone so that it only accepts that providers SIM cards, this lock code is stored on the phone, and may be unlocked by entering a code, or by bypassing it using unlocking software, once unlocked the phone will accept any other providers SIM card.
PUK the PUK is the Personal Unlock Code, and is a code that unblocks a SIM that has been blocked by too many unsuccessful attempts to enter the Sim Pin code, ( usually 3 attempts), this code must be entered to unblock the SIM card, usually the PUK is provided with the SIM Card, however if it is lost then some providers may give you the code, if the SIM has been registered by you.
Please feel free to add to this
Back to Windows Mobile:
If you need to reflash Windows Mobile, for whatever reason, these are my preferred methods:
I recommend using a Card Reader and MicroSD adaptor for working with SD cards, it makes life so much easier than relying on the kaiser to transfer and rename files, since most of us are used to handling files in Windows.
Method 1
1. Download a Stock shipped ROM, do not go crazy getting the latest custom 6.5 ROM, in my experience these often cause problems, if you want to go to Custom ROM's then flash stock first.
2. Extract the RUU_Signed.NBH file from the .exe, ( I use 7zip for this, but other archive utilities my work, winzip, winrar etc), rename the file to KAISimg.nbh and copy to the root of a freshly formatted SD card.
3. Insert the SD card in your Kaiser, pres and hold camera button while pressing power, ( you only need to press power briefly, but keep the camera button pressed until you see the tricoloured screen).
4. Once you get the tricolour screen, ( bootloader ), it should change to a grey screen with blue instructions, basically, press the power button and let it flash.
5. Once flashed, simply pull the battery/press reset and let it go through the first boot process.
Troubleshooting
Common problems with this method are that it will just not recognise the flash file, leaving you at the bootloader screen, this is usually caused by wrongly formatted sd cards, the card must be formatted FAT32. Other reasons are file name issues, make sure you have not accidentally mistyped the filename, or renamed it as kaisimg.nbh.nbh.
Method 2:
If Method 1 fails then the alternative method is USB flashing:
1. Disable Activesync, by unchecking the 'USB' option in Connection settings.
2. Remove the SD and SIM cards from the Kaiser.
3. Press Camera+Power to enter Bootloader.
4 Connect the usb cable, ensure that is says 'USB' at the bottom of the screen.
5. Flash the Stock ROM, usually by double clicking the downloaded stock ROM exe file, allow it to flash, and wait until it is finished before removing the USB Cable.
Troubleshooting
There are a few potential issues with this method also, if this method fails try another stock rom, the last shipped ROM from HTC was Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, this is a generic stock 6.1 rom and should be compatible with most if not all kaiser variants.
Useful Links:
ThoughtlessKyle's Why my Wifi doesn't Work Invaluable Information on recent WiFi Issues, A 'Must Read'......
LCD Panel Information
Tinboot thread ( the thread that launched Nand flashing on kaiser ).
SuperJMN's Android Issues roundup thread ( common problems, as yet unsolved )
Adding language support
Miscellaneous Notes.
Radio Version
Just as in Windows Mobile, Radio Version seems to play as vital a role on Android.
There are a number of problems that may be related to radio version, and just as in WM, the effects are sometimes surprising.
Audio: yes, just like WM the wrong radio version can cause audio issues, ranging from no audio, to more subtle issues such as call audio not working, even though all other audio events work fine.
Wifi: no surprise really, the radio stack controls wifi as well as the more common phone/network activities.
Data/Network: Obvious one, but there are a number of complicating factors here too, geographical location seems to affect radio version, for instance, in the USA, 1.71 radios may offer the best signal, and data rates, while in Europe, using 1.71 may cause a lot of 'No Signal' issues, where the phone seems to drop off the network, the solution is usually an older radio version, in the UK 1.65 seems the best choice for most users, I have also had reports of 1.65 being the best for South Africa, Asis, while Australia seems to do better on 1.70 or 1.71. This may be due to the technology in use in those countries.
GPS Maybe, not sure about this one, had at least one report that a radio downgrade from 1.71 to 1.65 seemed to help with GPS, as far as I am aware the GPS and the Radio stack are not related, but who knows for sure?
Great guide! I was thinking about making similar one myself, but couldn't find free time
I'll maybe try to add something this weekend
hello maybe a stupid question
what is the differents between odex and unodex
sorry for my bad english
kisses
Rose
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
CassandraN said:
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
Click to expand...
Click to collapse
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Thanks for the FAQ, it is extremely useful to noob or semi-noob like I am.
Thanks, that's why I decided to start it, and if one person finds it useful, it was worth it
say it with me class
Click to expand...
Click to collapse
This is just hilarious
BTW, I tried some of the reboot apps in the market, non of them seemed to work (on 2.1)
the original reboot menu that you get when you hold the power button did not work at all. it just hangs on the loading circle.
In Froyo however, things are a bit different. the reboot option shuts downs the device instead, I did not try any reboot app yet
Any ideas about this zenity?
zenity said:
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Click to expand...
Click to collapse
I usually battery pull (I lost my stylus and the cheap replacement won't fit in the reset hole ), but I still seem to have problems.
I think my problems are due to a rogue app eating all the CPU. My suspicions are Twitter or Swiftkey. The phone becomes so unresponsive that sometimes a hard reset is the only way to make it useable again. I'll try to avoid it in future if I possibly can.
Tried taskiller? Useful for watching your memory, and killing tasks if needed, osmonitor is also useful for, well monitoring the os
I have noticed that the system does get very unresponsive at times, and it usually means low memory, try an eclair build if you are using a CM6 based one, I usually get about 30+Mb free in normal conditions, and if things start to get too slow, well a tap on the taskiller widget sorts that out
@Duke911:
As far as I am aware there is no real reboot option, in any build, I think it's a kernel issue, or perhaps just not implemented correctly, the safest option is a power off, which performs a proper shutdown, I do know there have been a few issues with data corruption that may be associated with using reboot, or the reset button, since these may cause the system to shutdown to rapidly to sync any data that may be cached, it's similar to pulling an SD card out of the computer, there may be data left unwritten in cache, which is why there is a nice safe removal option
This is a cool wiki for Kaiser Android users! Thank you!
By OP request, I am making this thread a sticky and making some adjustments to the forum. Please PM me if you have any requests. Thanks.
Precious work, Zenity!!!
video call anyone?
Is there any chance of getting a build to support video calling?
Video calling will need working front camera driver at least, which is not supported yet, I do not know if anyone is actively working on this, however, at some time, someone will take up this challenge, just as they have with other things which did not work previously
Sent from my HTC Dream using Tapatalk
hello..
I just want to ask about polymod and cyanogenmod.
what is the function, are they different from eclair or froyo?
thanks ^^
CyanogenMod builds are all Modifications of base android releases, these are complete rebuilds of the system, and include many improvements over the original release.
Polymod is an Eclair Mod based on OpenEclair 1.3 and is modded in a different way to Cyanogen's methods and style.
Most Eclair and Froyo builds are ports and modifications of Cyanogen bases, ( in fact I don't think there are any Froyo builds that are not CM6 based).
For Donut things are different, most builds are modifications and ports of official releases, such as Myn's Warm Donut.
I'm currently developing a program that basically receives updates and performs them on mobile devices. These are running Windows Mobile 2003.
The update simply consists in a number of files/directories deletes, creates, attributes changes and overwrites (when modified). It's not clever or optimised in any way. But there is a problem.
If the program finds some files need to be modified, the program performs the modification and then immediately makes a kernel call to hard reset the device, so as to reload the OS which is set to read the persistent directories for further booting instructions (which was just changed).
It appears a small number of devices went through such an update but the old data is still being loaded into the registry for instance. There is no trace of where this could come from and I can guarantee it is not burnt into the OS's ROM. I suspect FAT12 or FAT16 corruption of its tables or perhaps its "Root Level Directory" section... reason is probably that the program makes the hardreset too quickly for all buffers to flush in time. Being a hardreset and not a soft one, I assume the buffers are destroyed and never written on disk, thus some changes are lost and some may have been done partially. This problem leaves what I call ghost files around. These files cannot be found anywhere, but somehow are read by the program in OS ROM that is set to find them in the root level dirs of the persistent partitions.
I've been researching like crazy to find a way to make a good call to FlushFileBuffers() to flush everything (data and metadata) before doing the hardreset. But I haven't found any good documentation that works for win32 ce 3.0. I've had to implement all kinds of silly workaround that are making the whole process take much longer than needed...
I'd like your input on how I could make sure everything is flushed properly on these WM2003 devices before I issue the call to hard reset.
Thanks,
Simon