Android for Sprint HTC TP2 links for an old newbie!

[Oldladyonbrady]

I really should know my limits but nothing beats trying even if I fail. I Thank you all for your time and patience and I'm GOING FOR IT!! lol

For me, knowing that the phone can do so much more than what windows offers makes me want to get the most out of it!

Thanks again everyone for your kindness

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Once you try Android, you will want to run it all the time, but the battery life is pretty poor at this point.

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

are you booting using thed statrtup utility or haret? if using the utility, in advanced settings, is overclock enabled? if so, disable it and try to boot android again.

[DaveTN]

Start here: http://forum.ppcgeeks.com/tp2-androi...ct-2010-a.html

Its a "Stickie thread" with the tutorial for getting android on your TP2. Worked great for me with easy to follow step by step and links.

Please don't forget to thank teradog.

David

[martian63]

Tried all that. wifi works on WM but not on Android. Please help!

[natemcnutty]

Originally Posted by martian63

Tried all that. wifi works on WM but not on Android. Please help!

When wifi doesn't work, it almost always means you updated the zImage but didn't update the modules that came with that zImage. They are a matched pair. If you did update both at the same time, then try renaming your data.img and let it create a new one and see if that fixes wifi. Sometimes the data.img stops installing new drivers when you've updated it too many times. Seems to be kind of random.

[martian63]

Originally Posted by natemcnutty

When wifi doesn't work, it almost always means you updated the zImage but didn't update the modules that came with that zImage. They are a matched pair. If you did update both at the same time, then try renaming your data.img and let it create a new one and see if that fixes wifi. Sometimes the data.img stops installing new drivers when you've updated it too many times. Seems to be kind of random.

1. I ran ProjectAndroid2.2Froyo.112210.cab from the SD card.
2. An Android icon was created on WM, I started android from there.
3. During startup, it asked the phone type, I selected
RHOD400
Cdma
HW3D
N AM DIAL

4. The startup also gives you an opportunity to run Update. It automatically downloads all updates and installs.

I do not know if this update is for zImage as well as for Module and data.img. Should I not run this update?

If I'm to manually update,

1. Do I need to run all updates sequentially from FRX01 to FRX03?
2. In order to update, do I just unzip/extract the files and replace the old zImage,Modules and data.img with the new ones?

Thank you once again for your help!

[arrrghhh]

Originally Posted by martian63

4. The startup also gives you an opportunity to run Update. It automatically downloads all updates and installs.

I do not know if this update is for zImage as well as for Module and data.img. Should I not run this update?

If I'm to manually update,

1. Do I need to run all updates sequentially from FRX01 to FRX03?
2. In order to update, do I just unzip/extract the files and replace the old zImage,Modules and data.img with the new ones?

So that tool updates zImage/modules (kernel) and rootfs. It does initrd too, but that probably isn't going to get anymore updates.

It does not update the system.ext2 (system image) which is basically the build you're running. You can download it from xdandroid.com, and no - you can go straight to FRX03 - just one thing to be wary of, is when you go between system images you sometimes need a new data.img - if you've run Android before, you'll have a data.img file that has all the apps and customizations you've done. You may need to delete this file if you're moving between system images (ie FRX01->03), initial boot will create a new one for you.

Originally Posted by dcurry

I used the startup utility that opened when I clicked on the Android shortcut on the start menu. Overclock was not enabled. And now the program that loaded when I clicked on the .cab file won't uninstall. I would caution anyone looking for a simple, pre-packaged program to run Android on a Sprint CDMA TP2: this doesn't appear to be it!

I kinda wish the CAB file was never created - this project is for testing, it's not meant to replace WinMo. The compressed RAR/ZIP builds are really simple to use (extract to your SD...grab correct startup...run haret...) and you actually get to see how the file structure looks so you can manually update and at least partially understand how it should look

With that said, again... This project is for testing. It's not meant to be easy, it's not meant to replace WinMo. Have fun with it, enjoy it... but don't dog on it because it's not "easy" enough for you. If it were up to me, it would probably be much harder to install Android - some have taken pity and tried to make it easier for noobs, just to have this kind of reaction from them.

[Oldladyonbrady]

Oh my, I had no intention of starting a war guys. I'm sorry that I asked but I really had no idea that it was cause hard feelings or words.
I thank you all for taking the time for even answering me. Thanks again and I think that I'll go back to lurking.

[natemcnutty]

Originally Posted by dcurry

I wasn't dogging the program, I was saying that it is not the simple, click-and-go installation indicated by the second post. I thought people should know that, and it looks like you agree that it should not be represented as "easy." Remember, this thread was started by a "newbie" who was, ". . .trying to Android my Sprint HTC TP2 by the simplest way possible." No offense intended.

If the link had worked on her phone, it would have been that easy. I'm usually pretty good at explaining things well to non-technical people, but I obviously failed on my response.

I still believe the click-and-go install really is that easy. Using the browser on the phone, download the CAB, click it, select SD card as the install location, it installs everything for you, then use the launcher to set your phone model and click Boot. Only way to make it easier would be to make an actual EXE for WM that downloads and does all the setup for you. But you still have the issue of getting that EXE onto their phone...

Originally Posted by Oldladyonbrady

Oh my, I had no intention of starting a war guys. I'm sorry that I asked but I really had no idea that it was cause hard feelings or words.
I thank you all for taking the time for even answering me. Thanks again and I think that I'll go back to lurking.

Didn't start a war, just some constructive criticism and helpful ideas