Related
I've read a few posts regarding the device ID changing from OS to OS flashes. I've been using Black from the beginning and it didn't seem to change the Device ID. Slingmedia and other programs installed OK.
I recently flashed LVSW ROM and it changed the ID. I had to get new registration codes from my programs because of this. I am afraid to flash new ROMS often now because of changing the device ID. These companies probably won't continue to change the codes for us forever.
I thought that the device ID is static based on the hardware itself. How can this change with a new OS? Can it be changed back without flashing another ROM? Can it be prevented from changing with a new flash?
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Very interesting, but I wonder if other apps are using ( and used in WM5 ) the "same" ID ... In any case, there's gotta be a way to see and change it one way or another. "The doors are everywhere, you just have to know how to open them"
doedoe said:
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Click to expand...
Click to collapse
I don't believe this at all. I think it's more likely the device is taking a one-way hash to the manually input device ID (see below) and SIM ID, plus some randomizer to create a unique identifier for the storage card encryption. My guess is this process runs when you check the box to encrypt the card. If anyone knows this to be different, please share how to locate the unique device ID.
Some ROMs has the Device ID (Settings -> System -> About -> Device ID) pre-populated with things like TyTn, or other text. I think the differences in some of the earlier ROMs was screwing everybody up because close attention wasn't paid to this. The first thing I've done each time I re-flash is change this to WM_[my-windows-logon], because when the device syncs with Activesync the first time, it goes with some combination of what's there plus your logon. Anyway, I've manually set this to WM_[myname] (yes, this is an example, 'myname' is not my logon) before syncing with Activesync. I've done this on Black 2.5, 3.0.1, one of LVSW's ROMs, and Custel's 2.5. I have yet to need a new sling code or tomtom code.
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
If anyone can confirm this, we should place it in the wiki.
Device ID
The device ID does not change after every hard reset, however with certain roms it can change the ID, at this time there is no fix for the changing ID problem. I also have a few programs that are teathered to the device ID instead of the IMEI.
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
100Tbps said:
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
Click to expand...
Click to collapse
It may work for those apps, but it isn't that easy for Infogation Odyssey (TomTom competitor), to name one. Has to be some deeper hashing algorithim in the ROM or whatnot. It changed around the time the 17xxx builds started appearing and I've always wondered if it could have a "dogfood" link.
Here are some MSDN articles on the issue:
http://blogs.msdn.com/jehance/archive/2004/07/12/181116.aspx
http://blogs.msdn.com/jehance/archive/2004/07/12/181067.aspx
http://blogs.msdn.com/windowsmobile/archive/2006/01/09/510997.aspx
We need a good programmer to figure this out
My Experiences
I have suffered from this very problem. My device ID stayed the dame from WM5, to XDA 0.1 > XDA 0.2 > Black 2.0 > Black 2.5
I then went to Black 3.0.1 and my device id changed. Infact, after getting a new licence string, the program that needed it (PocketHeroes) would bomb out whenever it tried to verify the new licence. This problem persisted in LVSW 3.3.
Now I am on Black 3.5 and my device id has reverted. My origional licence works fine and the app is 100% stable. My only guess is that a certain build of the kernal had a flaw with the deviceid and this has been naturally replaced by a newer version.
Device ID
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
lewnetoons said:
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
Click to expand...
Click to collapse
How can I see this 12 digit code?
Anybody going to write a program to change this? if legal!
lewnetoons said:
...clip...
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
Click to expand...
Click to collapse
I say, that is a great suggestion. :thumbsup
What's happening here is the platform ID portion of the Device ID is changing. This is because many roms here (including mine) use IMGFS components from the Universal. When this occurs, the platform ID portion of the Device ID changes from Hermes to Universal as well.
It appears that even the Official WM6 released today does indeed change the Device ID for instance with Tomtom Traffic.
I am having to take this original wm6 off now and stick with a development version of wm6 until i can convince tomtom to change my device id which they wont do. They are so useless....
just so other users are aware.
Problem:
a. CID Locked phone from Latin carrier but attempted upgrade anyway.
b. Did not backup original ROM before attempting upgrade (original ROM impossible to get on internet).
c. CID Bypassed and attempted upgrade from WM5 to WM6, USB cable disconnected at 16%!!!
d. As consequence, phone stuck on splash screen when turned on (must pull battery to turn off), I'm only able to force it into bootloader mode (connects to PC but no activesync connection). No cooked or official ROMs work (invalid vendor id message because phone stayed CID Locked) and as I said, original ROM impossible to get on internet: B-R-I-C-K-E-D!!!
What I attempt to do:
a. Get a hold of my friend's new, untouched, same carrier, same original ROM, same brand, same model WM5 phone.
b. Backup my friends phone with Sprite 6 (with Device Upgrade Mode) creating a self restoring backup file (backup.exe)
c. Use said backup file on my bricked phone to restore original factory/carrier ROM.
Aproach:
Connect the bricked phone in bootloader mode to the PC and run the backup.exe file that Sprite Backup 6 made of my friends phone.
Main question:
Does said backup.exe file need an activesync connection to connect to the device (somethin bootloader mode can't do)? or is it able to run with device on bootloader mode? Like many RUUs outhere.
Why I ask:
I don't want to cash out 30 bucks for Sprite Backup 6 only to find out it wont help me.
Other questions:
Has anyone else done these?
Does is sound plausible?
Other backup software that may do what's needed?
Sprite backup wont help :-(
sorry for bad news
BTW. it might be usefull for everyone to write what device U have, and/or post it to that particural thread.
why?
phsnake said:
Sprite backup wont help :-(
sorry for bad news
BTW. it might be usefull for everyone to write what device U have, and/or post it to that particural thread.
Click to expand...
Click to collapse
Does it need active sync?
It's an HTC Excalibur
I posted on my device's forum about the bricking and someone told me I should have backed up first with Sprite. Why would a Senior member say that if it doesn't work?
I appreciate your fast answer, but would you kindly care to elaborate?
DOnt know, but Sprite is for backing up installed SW & date. Anyway how do U expect to run EXE, if phone is bricked? It needs OS to be run on device (or thru sprite srvr on PC & async connection). RUU is different thing. RUU directly overwrites DOC and that for doesnt need async.
OK.. got it... then...
I've read many many times these golden rules:
"Backup your original software before you upgrade." And, "If you brick your phone you can only flash your original ROM."
In fact I've been scolded (politely) in all the posts I've made about bricking my phone for not backing up the original software before the upgrade.
What software does this if not Sprite? How do people back up their original ROM before the upgrade in case of bricking?
As I understand, if I backup the original ROM of my friend's Excalibur (which I said in this thread, is a clone of mine: same carrier, same OS, etc.) with the right software, I'll be able to flash it onto mine and unbrick, right?
I suppose I have to make an *.nbh file of my friend's ROM, replace it in an extrated RUU, and run the *.exe
One last question, are you sure the *.exe made by Sprite 6 works different from the RUU's one? I've read in the support section of Sprite's website when refering to self executable backups: "they can restore your device after a Hard Reset without having to reinstall sprite backup first" and "if your device doesn't boot after a ROM Upgrade"
As mentioned Sprite only backs up data: system setting, your files, databases, registry, and so on. It doesn't back up the ROM. This is generally only recommended in case the flash of the new ROM erases your data.
No idea how to make a backup of the original ROM... although I'd like to know.
If you will pm me or find me on MSN/Live IM @ ([email protected]) I will help you to determine if your device is truly a brick. I have a good reputation in the Kaiser forum & have successfully "unbricked" over 50 devices.
My main concern is that you don't do too much more damage in your state of panic. Please try to refrain from trying to many things.
Again, email or PM me to remind me, & I will have you pr walk you thru a few diagnostic tests. Because I don't know what device you have, you didn't mention it, it may take a little time ( a day or so to locate & disassemble your device SPL & OEMSBL) but I am confident I can resurect your device.
There are also tools available that WILL allow you to dump another device ROM & then reconstruct the raw data & repackage it into a flashable version. Slight modifications may be necesary, but again, I think we can get through this issue. It sounds to me like a bad Memory Block, but I'd like to confirm that before jumping into the "let's fix it" phase.
If reflash is required, we will have to dump to raw data, pack that into a .nbh or .nb0 & then we can modify a RUU to call on that nb file for reflashing. It is a bit of work, but there is a 60 to 70% chance that it won't even be required & a simple memory block flush will be sufficient.
Great!! Gsleon U Rock!!
OK... I'm adding you to MSN right now, I'm new to this and besides unbricking my phone (HTC Excalibur) I'm eager to learn everything about modding, upgrading, etc. mobile phones.
My activesync just stopped to work since some day, it is just keeping connecting, but never succeed. I've tried to reinstall activesync several times but no luck. Now the version is 4.5, and my rom is a custom made one from the forum (xplode_7.00 6.10.00.WWE). I don't have a clue as it just suddenly stopped to work. Some thing that may be useful for troubleshooting:
1. when connected to pc (winxp), no device showed under " USB controller" in device manager, instead a "windows mobile based device #16" showed up under "Network adapter"
2. When just hooked, a connecting icon will show up at connectivity status(top of the screen) for about one second, then replaced to "two arrows with a cross ".
3. I have Rogers blocked my data service... could that be a reason? (seems not quite likely)
That's all what I could think about so far. I've looked through posts regarding similar issues but still could find a solution. I appreciate any input/insight.
----
Another question, does any one know how to have the youtube app working with wifi. It just showed " Error, Connection problem. Failed to initialize...."
Thanks a lot
your data service theoretically could be the issue, but since you said it worked before, and your device manager says #16, i guess, this will help you:
i don't know if you use the cradle with a pc or maybe a usb cable that is not permanently connected, but it seems, the driver is just installed many times now, so try the following to clean that up:
1. disconnect the cable/cradle
2. on the pc, right click "my computer" or "computer" (depending on whether you use xp or vista/7), and click 'properties'
3. go to the advanced system settings
4. click "environment variables"
5. make a new variable by clicking the upper "New" button
5.1 the name must be "DEVMGR_SHOW_NONPRESENT_DEVICES" without ""
5.2 the value must be "1" without ""
5.3 close all open windows with OK
6. restart the pc
7. start the device manager again, e.g. by right clicking "my computer" or computer and clicking "manage"
8. click "View" and then "Show hidden devices"
9. now you see a lot of new greyed out devices, all devices that were ever connected to the pc.
10. now you can start cleaning up:
10.1 go to "Universal Serial Bus controllers"
10.2 all the greyed out entries named "Unknown device", "USB Mass Storage device", "USB root hub" can be right-clicked and uninstalled, but just the greyed out ones!
10.3 go to the tree "Portable devices" and uninstall anything like BlueAngel, PocketPc and stuff like that.
10.4 go to the tree "mobile devices" and uninstall them all.
10.5 close the device manager
11. connect the cable and the device again.
12. since all the old drivers are uninstalled, it will start searching for new hardware and then connect the device again. if you are in fact using xp and the driver is not found disconnect the device again, uninstall active sync, restart the pc and re-install it. it brings the driver and on the next connect, the "new" hardware will be found.
ok, it seems like a lot of work, but it will seriously speed up all your usb connections, because all the dead links and drivers are cleaned up. if, for any reason, this was not the solution to your problem, at least enjoy the faster usb, you're welome
in that very case, you should use pimbackup from my thread in my signature (the "read first" one) and make a backup of all your pim data and perform a hard reset, that could also help.
btw. when you are in my thread already, there is also a youtube app there, that works extremely well with wi-fi and is a lot faster than the official one.
Thank you very much for this detailed procedure. I've tried it through, but still no luck. I'll see if I could find solution before "a necessary hard reset". One odd thing is I didn't see any "blueangel related item" under Portable devices, and I even don't have "mobile devices" tree..
I also downloaded youtubeplay. I will give it a try later. Also, isn't myphone usable through wifi either?
Thanks a lot for the help.
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Chef_Tony said:
myphone should also work fine via wi-fi, maybe you should check your connection status there as well, i could imagine one situation, where no change at all could also screw that up. if you have an incredibly bad connection or your dhcp encountered a conflict, you might get stuck with an APIPA ip address, something like 169.254.x.x, your wi-fi shows up as connected but there will be no data transfer. in that case, assign a manual ip address or check on your access point or router.
if all other programs work, except for those two, you should think about a hard reset. by the way, if you are a person, that does not like hard resets because of all the programs you need to install and set up again afterwards, you should think about trying spb backup, which can create full backups of your system state before a hard reset. it's pretty neat and due to the fact, that you make a hard reset afterwards, you can use the free trial version.
little warning though:
- never plan on restoring a backup on another rom! this app backs up your complete system, including registry and stuff, and that can vary from rom to rom, after you restored a backup from another rom or device, your device will behave odd, if it will even start, and you probably have to re-flash the rom.
- if you are hard resetting because you screwed up something software or registry related, don't hard reset and restore the backup, the screw-up will be restored as well only make backups of running systems and for last minute backups of pim data, use pim backup.
oh, and with the "portable devices" tree, my bluangel probably shows up there, alongside with card readers and usb flash drives, because i am using windows 7. the mobile devices tree might also have a different name, something like windows ce devices or something like that, basicly you were to delete everything with a pda icon at least, especially that "windows mobile based device #16" and its 15 possible predecessors, so that windows could search the device again.
in a very last attempt to determine whether it is the device to blame or the pc/active sync, you could also try connecting it to another pc. if it is actually just your pc, maybe you don't have to make a hard reset after all. you know, if you get that wi-fi issue out of the way...
Click to expand...
Click to collapse
This is why history is important... you learn from it
Here is an extract from xplode's thread (first post)
R7 Release (this does not mean that this is windows mobile 7)
-------------------------------------------------------------------------------
Rapidshare: R7 ROM
Ziddu: R7 ROM
[highlight]Known bug with it , does not want to sync ... (or maybe it is my pc error i will look into this, but now it is 4 AM and i am going to bed[/highlight]
Click to expand...
Click to collapse
I have a simpler solution.... get PIM backup to save any important things out of your phone, flash a newer rom . Remember, xplode's latest version was 7.1 and not 7... and that is for a very special reason... bugs (activesync being one of them). More than likely, you will have to either HR or change roms. I would personally go with the latter since I am gonna have to reinstall everything anyways.
BTW, Chef.... awesome guide!
yeah, i remembered that xplode had some sync issues with some past roms, but i always thought that it if it hit you, sync wouldn't work at all but it seems to have worked before, which is why i didn't blame the rom first. that usb driver issue is trouble though, it could have been the solution this time, since it isn't i will use this to link on, the next time it might be
but i agree, in this case, changing the rom should clear all issues.
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
java218 said:
I finally fixed the problem in a way like what egzthunder1 suggested... And now I am trying out wm6.5. Here is what I've been through
1. Spb backuped my PIMs. Restored to my previous backups ( which I am sure worked well with Activesync )... Sync still not working.
2. Hard reset, sync works. Restored to any previous backups... sync not working
So I decided to flash a rom, now that I have to hard reset it anyway. So, I HRed the phone, restored PIM, and synced with my PC and MS' myphone account, downloaded a new WM6.5 rom, and flashed the phone...
bling..everything works now
I don't think it's old ROM's fault for not ActiveSync, it must be something I did to the system which is weirdly not restore-able. Anyway, starting over is always an effective solution, just takes a lot of time to get everything back to work again.
Thank you guys for great guides and insights.
Click to expand...
Click to collapse
There are things that get backed up with 3rd party software (such as Sprite Backup), which will mess things up in the device. It is usually recommended not to use these softwares to back your things up. Instead, you should always try to either use AS, or try PIM Backup, which for some reason doesn't mess things up.
Glad it worked out
same issue with ELF0 100 i can't figure out :-(
Dear all,
After resolve my flashing issues, now I am bump into another problem.
I tried flash my phones via at least 4 roms.
Regardless of the version of rom, after I successfully flash them, I can proceed to install applications of my preference.
When I restart or hard rest them, my phone will automatically return to the after flash screen whereby it prompt me to tap the screen to setup the phone.
All previous software installed will be missing from the system, including the contact, mail that I successfully sync from my computer.
Is this hardware problem?
If it is, how can I check what likely is faulty
Thanks in avance.
decent_devil said:
Dear all,
After resolve my flashing issues, now I am bump into another problem.
I tried flash my phones via at least 4 roms.
Regardless of the version of rom, after I successfully flash them, I can proceed to install applications of my preference.
When I restart or hard rest them, my phone will automatically return to the after flash screen whereby it prompt me to tap the screen to setup the phone.
All previous software installed will be missing from the system, including the contact, mail that I successfully sync from my computer.
Is this hardware problem?
If it is, how can I check what likely is faulty
Thanks in avance.
Click to expand...
Click to collapse
This seems to be caused by multiple bits of pieces from other flashes, especially from windows mobile 6.5.1 onwards, to fix this you can either:
a)Get the ROM, and rename it to DIAMIMG.nbh and get it into the root of your internal storage, then use MTTY (Directions here:http://forum.xdadevelopers.com/showthread.php?t=540290), then holding vol down+back button and reset, perform an internal storage upgrade (note: Certain ROMS may not work like this). Then, perform a hard reset (vol down+Center button+Reset)
or B:
b)Get a stock ROM, flash that one and then flash the ROM you want
btw, for the "a", you can always flash using active sync if you get into bootloader (vol down+reset) and connecting it to USB, im not sure if this works on vista/windows 7
and also, would encourage you to use the "Search" feature before posting this, I had the same problem and I just searched the forums. And ROM upgrades/flashes will make a hard reset to your phone, but ALWAYS do the manual hard reset to format your internal storage
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time
There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.
The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.
Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!
Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)