[Q] custom rom for t-mobile htc touch pro2? - Touch Pro2, Tilt 2 Windows Mobile General

hi everybody!
first of all, i'd like to ask for your leniency since i'm a total noob here at xdadev.
I just got a T-Mobile HTC Touch Pro 2, and I have no complaints in terms of reception and connectivity. However, from the very beginning I have noticed that memory usage is high even with no apps running. I have stripped touchflo from all nonessential components, like weather, stocks, etc, but it makes little difference.
Also, the rom is loaded with apps that I don't need and apparently can't be uninstalled. As an experiment, I tried to install Gmail (tho you don't really need to) and I got the following error message:
installation failed, errno=910 Application authorization failure
what's up with that??
My previous device was a generic windows phone running windows mobile 6.5.2.23090 Pro, and I really liked the finger-friendly menus. i also had flexibility to configure the device that I seem to have lost completely with the touch pro 2.
I have considered installing a custom rom, but I really like touchflo, with the black/Grey/White interface, the smart looking flipping retro clock on the front, the dialer, the menus, the multimedia handlers, etc,.
Would I be able to install touchflo on top of a custom rom? your eyes must be rolling by now, but... i have looked and i've only found versions that are different from the one I have and love.
What do you guys think? do you have a specific rom or touchflo version to suggest? lemme know!

TouchFLO is old (Manila 2.0) and replaced with Sense (Manila 2.5). Basically the same thing, but better looking, and more functionality. TouchFLO/Sense cannot be installed onto a phone after the fact. It needs to be cooked in as part of the original ROM. If you like the HTC Manila UI, look for custom ROMs which have Sense. Most of the things you mention are the same/similar in Sense as TouchFLO (although I'm not familiar with what carrier customizations to TouchFLO the T-Mob version has).
Custom ROMs will solve your issue with the carrier bloatware, and many of them manage memory better than stock. Although, you will see there is huge variety in terms of looks and what apps are cooked-in. If you want a clean, lightweight ROM try simplicity or Jackos (Jackos is really good for memory management). Many people also like Valkyrie. Energy is very popular, with great looks and lots of cooked-in apps, but not the most lightweight.

Esmertec Jbed 20090506.2.1 by Aqrab works very well with Gmail.

thanks you guys! im soooooo on it!!

Custom ROM
Hi,
I just recently (like a week and a half ago) got a T-Mobile Touch Pro 2. I had been using an older HTC Touch Viva. It just like the TP2 I bought came with Windows Mobile 6.1. I used my Viva for quite a while with WM 6.1 before I found my way here to XDA.
I went very slowly at first flashing my first custom ROM onto my Viva but after a while got to a point that I was trying out a different ROM almost weekly. The problem is that a lot of these custom ROMs have bugs in them to some degree. So I went back and forth to find the ROM that I liked that seemed to run the smoothest.
As someone previously stated, the TouchFlo 2 interface is an older interface. But as I understand it it wasn't that it was replaced by Sense 2.5 but was created for phones that weren't as powerful. It didn't need quite as much graphical power to operate it and gave phones like the Touch Viva a nicer interface that looked a lot like the nicer Sense interface.
I spend quite a lot of time trying out different custom ROMs on my Viva so when I decided to upgrade my phone to the TP2 I had already scouted out the ROMs to some degree and had download a few to try out.
I too liked the finger friendly menus of Windows Mobile 6.5.x of the ROMs that I had been using on my Viva and knew that I wouldn't keep the OEM WM 6.1 on my TP2 any longer than I had to.
I went through a couple of custom ROMs for the TP2 before trying out the Simplicity ROM. It seems to still have the look and feel of an OEM style ROM without all of the bloat that comes with them, but this is only my opinion. You'll need to try out a few of them to see which one you like.
Good luck.

Dear All,
After I started this thread, a couple of noobs actually pm’d me to ask about my progress. They said they were too embarrassed to post their noob questions directly on my thread. Since I know the feeling, I will post a quick recap of what I did and where they can find the relevant information on xdadev.
First of all, before I began, I made sure I:
1) had my rhodium connected to my PC via Windows Mobile Device Manager (for XP users it would be Microsoft ActiveSync);
2) knew how to enter bootloader mode on my rhodium;
3) knew how to hard reset my rhodium;
4) had a backup copy of the latest official rom release from T-Mobile, just in case.
At this point I chose a custom rom from one of the many talented chefs on xdadev. My choice is the simple and gorgeous “Reference”, that NRGZ28 has created for htc rhodium. The full file name is:
Energy.RHODIUM.28244.Sense2.5.Reference.Nov.13.7z
And it can be found on the chef’s original thread:
http://forum.xda-developers.com/showthread.php?t=562773
STEP 1:
I downloaded and installed the ‘Hard-SPL’ package from the following thread (after I read the instructions):
http://forum.xda-developers.com/showthread.php?t=550131
This tweak allowed my rhodium to 'accept' custom roms.
STEP 2 (NOT NECESSARY, BUT I DID IT BECAUSE MY ROM HAD BEEN FLASHED A FEW TIMES BEFORE):
I downloaded and ran Task 29 from the following thread (after I read the instructions):
http://forum.xda-developers.com/showthread.php?t=649191
This tool formatted the internal memory of my rhodium to remove any trace of previous roms.
At the end of the process, I was quick to put my rhodium in bootloader mode and proceed with STEP 3 below. However, if you allow the device to reboot, it will be stuck on the splash screen because task 29 has wiped the rom partition clean. It’s totally normal, so don’t freak out. All you have to do is yank the battery, restart the device in bootloader mode, and proceed with STEP 3.
STEP 3:
I ran the installer from my custom rom of choice. At the end of the process, I yanked the battery and hard reset the device. Then I repeated the operation one more time. It’s recommended to hard reset a couple of times after flashing a new rom. So what’s the point of waiting through the first run and customization screens twice just to hard reset?
If your chef doesn't provide specific installation instructions, you can read mskip's flashing guide for noobs:
http://forum.xda-developers.com/showthread.php?t=550540
The whole process ran smoothly and I’ve been enjoying my new rom for a few days now.
Next mission: get rid of that awful T-mobile splash screen at startup…
Peace-out

Thanks for posting your experience here for others.
But a couple comments:
Task29 is supposed to stop on the splash screen. Once it does, you hold the volume down button, while pressing and releasing the soft reset button with the stylus (under the battery cover). It says this in the Task29 instructions.
I usually do a hard reset after flashing the new ROM. Personally I only hard reset once. I think (not sure) its just to make sure that any previous data has been cleared. Pressing the soft reset button with the stylus does the same as pulling the battery, but to me a bit easier. And I've seen it cautioned here that the soft reset button is safer than pulling the battery.

Soft reset is less volatile on the flash memory. Always soft reset when possible. There is no need to hard reset if you perform a task29. Hard reset pretty much does the same thing. You only need to do EITHER a task29 OR a hard reset for best performance. Also, you only need to do a single hard reset if that's the route you choose. Doing two of them is a bit extreme.

Everybody thanks for your feedback!
I will correct the procedure accordingly should I need to flash the rom again in the future.
My experience is that the process itself is very simple; what makes it confusing is that the info is scattered all over the place, and sometimes there's too much unnecessary detail to sort through.
One way experienced xdadev contributors could make life easier for us mere mortals would be to state in more simple terms which devices their tool/rom is compatible with and how to check that you have the latest version. It took me a while to figure out, for example, which HSPL package was compatible with my rhodium and whether I had the latest release.
Anyway, thanks as usual for your gr8 work

There is only one Hard SPL tool. It's the only one in the Rhodium sub-forum. It's also the second thread in the ROM development area. Even if you were still confused in getting to that thread, the instructions in the first post are laid out clearly, and step-by-step. I don't get what was so confusing. It took me all of 3 hours to get my device set up the first time I began flashing ROMs.

bettasbetta said:
Next mission: get rid of that awful T-mobile splash screen at startup
Peace-out
Click to expand...
Click to collapse
use this task29. it changes the boot screen to say Touch Pro 2. I use it on my sprint tp2 and my gf's tmobile tp2. it gets rid of the white htc screen on mine and the tmobile screen on hers.
mission complete
Peace

puff601 said:
use this task29. it changes the boot screen to say Touch Pro 2. I use it on my sprint tp2 and my gf's tmobile tp2. it gets rid of the white htc screen on mine and the tmobile screen on hers.
mission complete
Peace
Click to expand...
Click to collapse
Do you even know what task29 does? It formats your internal memory, meaning it erases the ROM image. Don't use that RUU file. Just drop the NBH file into a folder with any other RUU and it will work exactly the same without destroying all of your data.

cajunflavoredbob said:
There is only one Hard SPL tool. It's the only one in the Rhodium sub-forum. It's also the second thread in the ROM development area. Even if you were still confused in getting to that thread, the instructions in the first post are laid out clearly, and step-by-step. I don't get what was so confusing. It took me all of 3 hours to get my device set up the first time I began flashing ROMs.
Click to expand...
Click to collapse
The confusion arose from the fact that i wasnt sure whether the posts were up-to-date. When you're dealing with a phone that's been around for over two years, you gotta at least acknowledge the issue. I was concerned that an earlier version of hspl would not accept more recent custom roms.
Again, I only started the process once I was positive I had the latest compatible tools/rom, and I was done in less than one hour.
Thank you for all your input.

Related

Can I create a Reinstall disc from my Sprint TP2

OK, I searched and could find quite what I was looking for.
I have a new, factory fresh TP2 from Sprint. I'd like to create a reinstall disc so if I screw something up, I could reinstall back to factory and start over again.
Is there a program that does this for me or is it something I have to hack alot to do?
I'm new to the TP but I've been using an Axim for years. Now that I have this new Smartphone, I'd like to play around a bit with the cooked ROMs out there for the PDA and maybe eventually do it to the phone too. But, right now I just want to have a backup of my phone and my PDA just in case.
Thanks
JohnMcD348 said:
OK, I searched and could find quite what I was looking for.
I have a new, factory fresh TP2 from Sprint. I'd like to create a reinstall disc so if I screw something up, I could reinstall back to factory and start over again.
Is there a program that does this for me or is it something I have to hack alot to do?
I'm new to the TP but I've been using an Axim for years. Now that I have this new Smartphone, I'd like to play around a bit with the cooked ROMs out there for the PDA and maybe eventually do it to the phone too. But, right now I just want to have a backup of my phone and my PDA just in case.
Thanks
Click to expand...
Click to collapse
Well the good news is that just resetting your windows mobile install back to it's complete factory-new condition, all you have to do is what's known as "hard reset" (power+send+end), a simple procedure that's built in to the phone just for this type of scenario. The one drawback is that it takes you ALL the way back, so ANYTHING you've added to the phone since you first took it out of the box won't be retained.
Now, if you want to first install your most important programs, contacts, etc before creating the backup, use a 3rd-party program like SPB Backup to create a restorable backup copy of all that right to your storage card.
No, I just wanted to create a disc that would allow me to reset/reinstall everything back to factory just in case I should ever need it. I figure I'll eventually start playing with installing cooked ROMs and such and just wanted a safety balnket in case I don't like what happens.
Well, either of those methods will achieve the same thing, just depends on whether you want that "security blanket" to include anything other than the aboslute stock setup...
-If you do, the SPB backup works just like a backup disk, includes a self-reinstaller in the backups it makes.
-If you don't, then the hard reset is the same thing as a backup disk, just automated and built into the firmware.
Once you start playing with cooked ROM's, a hard reset will not restore the device to factory defaults; it will restore the device to the state it was in right after flashing the cooked ROM.
There is section specifically about flashing ROM's, and there's information there on how to restore to the original factory defaults. Start with reading these two topics: flahing cooked ROM; undo your cooking.
Oh right, I wasn't thinking about that, but yes, hard reset will only take you back to the stock of whatever ROM you have loaded. You obviously have already figured out how to undo it and get back to the Sprint stock if you want
I don't mean to sound rude, but you sound very "green". I would very strongly urge you to read every wiki and sticky on this forum before you ever consider playing around with your device.
If you play around without first educating yourself completely, your device can become a very pretty, very expensive paperweight...aka...a brick.
I have been with xda for a few years and have had a couple of devices, I recently got the TP2, and have spent the past almost 2 months reading and re-reading various tutorials and stickies and wiki's. My rom is still stock. This is not because I am a noob, it is because I am a noob with this device.
SPB backup or Sprite backup are about as close as you will come to a recovery disc for a ppc. As far as I know, there is no true recovery disc as you would have for a laptop recovery.
Also, before you consider trying out cooked roms, you will need to learn the unlocking process. Also using cooked roms, while 99.9% of the time are far superior to stock roms, may void any warranty you have.
So again, I strongly urge you to read, read, read...read until your eyes bleed, then read some more. Once you understand how the device works, then consider f**king around with it.
It would suck if you ended up bricking your device because you went from point A to point D without first stopping at B and C.
akashastrega said:
I don't mean to sound rude, but you sound very "green". I would very strongly urge you to read every wiki and sticky on this forum before you ever consider playing around with your device.
If you play around without first educating yourself completely, your device can become a very pretty, very expensive paperweight...aka...a brick.
I have been with xda for a few years and have had a couple of devices, I recently got the TP2, and have spent the past almost 2 months reading and re-reading various tutorials and stickies and wiki's. My rom is still stock. This is not because I am a noob, it is because I am a noob with this device.
SPB backup or Sprite backup are about as close as you will come to a recovery disc for a ppc. As far as I know, there is no true recovery disc as you would have for a laptop recovery.
Also, before you consider trying out cooked roms, you will need to learn the unlocking process. Also using cooked roms, while 99.9% of the time are far superior to stock roms, may void any warranty you have.
So again, I strongly urge you to read, read, read...read until your eyes bleed, then read some more. Once you understand how the device works, then consider f**king around with it.
It would suck if you ended up bricking your device because you went from point A to point D without first stopping at B and C.
Click to expand...
Click to collapse
That I Am! and I make no bones about it. AS far as the idea of modding my PDA's go, I've never done it since I really kinda relied on them for the programs I carried at work(medical), I was afraid of bricking it. I'm new to modding but not to PDAs in general.
Now that I have my TP2 and have finally converged into a phone and PDA in 1, I now find myself with 2 Axims begging to be cooked. BUT! before I do that I want to have a backup.
Any and all advice you have is welcome. Please keep it coming.

[Solved] New questions about Android

Everything is working nice for me now, except for missing ÆØÅ, but I guess Ill get used to it.
The os is a bit slow, but meh.
So my I have found answers to my questions, but below are the original ones.
New questions:
Hello again!
Thanks for the information. Big thanks to this wonderful forum, because I can run Android on my phone!
But as I have tested it I have some questions:
1. The wifi is really slow. It feels like I am using Internet through the SIM card, but I am indeed not. (I took out the SIM card to test). And there isn't any problem with our Internet, because it is fast and good on everything else.
Downloaded some older files and the WiFi is working much better now!
2. I got some problems with vertical lines, but after readings some FAQs I found out about a setting. It has worked overnight, but is it permanent?
This problem is solved, haven't experienced any vertical lines after boot fix.
3. I'm not sure if GPS is working, because it take ages to start. Just says loading... loading... etc.
GPS is working, but slow.
4. Since I am from Norway it seems like I have custom physical keyboard. (with ÆØÅ) And because of that all the FN keys are messed up, well except for numbers.But as I read somewhere the default mapping for Tytn II should be FN + Q = @
And that is how my keyboard look now. But it should be FN + Q = ? according to the text on the keyboard and how it worked in WM.
And is there any way to do the same for the Android keyboard?
Anything I can edit without too much hazzle to fix this? Cause its a pain to write texts without the Norwegian letters.
I found a custom kernel and it is working nice (I have asked for a custom build of it so I can have ÆØÅ too, but mapping is good)
Besides that I am SO happy with it! I just love the menus and how its so easy to touch compared to WM.
Original questions:
Code:
Okey, first of all.. this is probably a newbie question and I might have found my answer if I searched for a while.
But as both you and me know, it would've taken me much more time to search and read a bunch of threads than it would be to just simply ask the question.
I am a newbie at the whole ROM and radio business on phones. To be honest I just found out yesterday that it was even possible.
As you might have guessed I want to run Android on my phone. Im going to run it from the microSD card etc.
Well there werent really any problems to download the Android files together with Haret and then put them on the sd card. (If I wasnt able to do that I wouldnt bother.)
The problem is that when trying to run Android from within WM (6.1) it just freezes at full bar with the text "Go Go Go". The whole phone is just frozen and I have to restart it.
Well as I read on the troublehooting guide on "androidonhtc.com" I have to update my radio which then leads me to this website.
Fine so far. The problem is that I do not really want to mess with the phone itself. First I want to know how I can "backup" the radio so if I mess up something while flashing I can easily go back.
Second of all Im not really sure which radio which works with which rom.
I am running the original rom which came with the phone and I do not really want to mess up anything.
Here are the infos I got from the phone:
Rom version: 3.29.409.0 NOR (Yeah, Im from Norway)
Rom date: 05/05/08
Radio version: 1.65.16.25
Protocol version: 25.83.40.02H
The phone is HTC Tytn II running Windows Mobile 6.1
The guide on androidonhtc said that I needed "1.65.24.xx or 1.71.xx.xx"
Can I then use a 1.71.xx even though I have a 1.65.16.25 now?
tl;dr:
I want to know which radio I can use for the phone with the specs above.
The recommended radio for most android builds is 1.71.xx, however it will still run on older radios, but may experience some audio, wifi, bt, gps, and possibly other issues.
If you intend to run from SD card, then this may not be much more than an annoyance, since you can reboot to Winmo at any time, and as a newcomer to android this would have been my advice anyway.
To upgrade the radio is a simple step usually, provided your device is prepared properly.
A prepared device means that is ready and able to be flashed, and this requires HardSPL, ( basically an unlocked bootloader that allows you to flash roms/radios/ splash screens etc).
I recommend reading through the guides and tutorials sticky in the 'main' rom forum: http://forum.xda-developers.com/showthread.php?t=533976
This should give you an understanding of what might be involved in starting to flash your device, and should answer many of your questions about radios, flashing, unlocking, roms and other things you may need to know about before proceeding.
Good luck, and remember, I was once as new as you, and that thread was where I learned all I know about my devices
So if I update to 1.71.09.01 while still using the original ROM, I wont get any big problems?
Or do I have to upgrade the ROM too?
You see.. this stuff is confusing to me. I consider myself a PC geek, but I suck at phones.
The instructions are pretty easy to follow, but its not so easy to know if I'm able to revert the stuff I'm doing.
I want to do as little "damage" to the phone as possible.
Is it necessary to backup the radio which is on the phone now, or do I have to find another radio from here and flash it on?
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
cXhristian said:
So if I update to 1.71.09.01 while still using the original ROM, I wont get any big problems?
Or do I have to upgrade the ROM too?
You see.. this stuff is confusing to me. I consider myself a PC geek, but I suck at phones.
The instructions are pretty easy to follow, but its not so easy to know if I'm able to revert the stuff I'm doing.
I want to do as little "damage" to the phone as possible.
Is it necessary to backup the radio which is on the phone now, or do I have to find another radio from here and flash it on?
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
Click to expand...
Click to collapse
You don't need to upgrade the ROM. All you need to do is install hardSPL, then install the radio. If you install hardSPL properly, your phone will be almost impossible to brick. It's really the first thing any person should do to their phone when beginning to do modifications. You can't "back up" your radio, but all available radio versions, including the one you currently have, are available HERE. So if you ever want to go back to your original radio, it will always be there. I honestly don't know the difference between the radios, I just know that certain versions are recommended depending on what ROM you are using, for the best signal and least bugs with wifi and bluetooth, as zenity previously mentioned. Hope this helps you some, good luck!
Thanks, thats what I wanted to hear.
The reason why I want to try out other mobile OS and ROMs is that I hate how the menus are so frigging tiny on the WM 6.1
If I'm trying to do stuff fast I always click the wrong button.. And yeah I have lost my stylus.
Anyway, thanks for all the help. After getting some answers and reading some threads I feel ready to update the radio.
cXhristian said:
And one last question. Is there any difference between the original radio on the phone and the radios I'm downloading from here?
Click to expand...
Click to collapse
Basically the higher the radio version number, the newer the radio software, as our devices aged, HTC brought out a number of software updates.
Our network carriers usually have custom ROM's which have a 'matched' radio for best operation, however even these 'matched' radios had small bugs, which were patched by releasing newer radio versions, of which 1.71.xx was the lastest and last official HTC radio for the Kaiser series.
There are also radios from other devices which work with our kaisers, but these are not recommended unless you have a particular need for one of those.
As far as the ability to 'undo' any modifications you make is concerned, it can all be reversed and your device put back the way it was relatively easily, instructions for this are best found on the wiki pages for the kaiser, along with a load of other information about radios, roms, flashing etc.
But unless the reason for not messing with your kaiser is in case you have warranty concerns, then pretty much everything is 'safe' to do, ( there is ALWAYS a risk of a bad flash, or unforseen power cut, but even these are recoverable in all but the most extreme circumstances).
Finally, take everything one step at a time, don't be tempted to rush in and try everything at once, you will make mistakes, you will also learn how to fix them.
As with everything else, remember to backup anything you really cannot afford to lose, get a 128Mb SD card with an HTC ROM on it, and don't panic
Hello again!
Thanks for the information. Big thanks to this wonderful forum, because I can run Android on my phone!
But as I have tested it I have some questions:
1. The wifi is really slow. It feels like I am using Internet through the SIM card, but I am indeed not. (I took out the SIM card to test). And there isn't any problem with our Internet, because it is fast and good on everything else.
2. I got some problems with vertical lines, but after readings some FAQs I found out about a setting. It has worked overnight, but is it permanent?
3. I'm not sure if GPS is working, because it take ages to start. Just says loading... loading... etc.
4. Since I am from Norway it seems like I have custom physical keyboard. (with ÆØÅ) And because of that all the FN keys are messed up, well except for numbers.But as I read somewhere the default mapping for Tytn II should be FN + Q = @
And that is how my keyboard look now. But it should be FN + Q = ? according to the text on the keyboard and how it worked in WM.
And is there any way to do the same for the Android keyboard?
Anything I can edit without too much hazzle to fix this? Cause its a pain to write texts without the Norwegian letters.
Besides that I am SO happy with it! I just love the menus and how its so easy to touch compared to WM.
I'm having the exact reverse, m FN + Q is ?.
If i remember, fn+q='?' means you are using a tilt keymap on a non tilt keyboard, if you are running from nand, try a non-tilt nbh, if you are running from SD theres a setting in default.txt. ( board-kaiser-keypad.atttilt=1 ) if it's set to 1 change it to 0
No, on the nbh i'm using, the tilt keypad layout is set to 0. But I'm back on ext2 now so it isnt a problem anymore.

Android Troubleshooting, A Posting Guide.

I'd like to ask those wishing help with troubleshooting to please help us to help you.
When reporting a problem it is useful to get as much information as possible, the more information we have, the easier it is to help.
Is it running from SD or Nand.
What radio version.
What build are you having the problem with.
What kernel/nbh are you using.
If you can, try to post any error messages.
Please try to post your questions in the thread for the build you are having issues with, it's more likely to get noticed there, and other users of that build may have the solution you need.
All this information saves a lot of time, and helps cut down on confusion, especially the SD/Nand part.
I have trouble with signal, it's weak than WM, when I used WM my radio is 1.65, I'm up to 1.71.09.01 and flash Android (NAND menthod) and the signal so weak
So Android support radio 1.65??? I want to back 1.65
I'm using TYTN 2 Kaiser _ WarmDonut version
Another Qs:
Q.How can I use my fone like a modem? I see in Menu have Modem but I don't know how to connect with my PC as a modem
Q.How can I connect to my PC via Wifi ad-hoc? (if available, please guide step by step- because I'm... chicken )
Q.GPS so slow and weak (in Vietnam)
Q.It so hard to power off (It's hang)
Best regard
I had issues with 1.71.xx radios too, and went back to 1.65.21.14 and my signal was good once more.
To change radio, download the radio you wish to use from this thread http://forum.xda-developers.com/showthread.php?t=393182, post 3 has the download links you need.
Once you have it downloaded, rename the ruu_signed.nbh to kaisimg.nbh and copy to SD card, flash using the power+camera method you used to flash the nand nbh, you will not have to reinstall Android when you do this.
The modem in question refers to the gprs modem used for data, it should be possible to use the phone as a modem, but as far as I know this is not working properly yet.
Not sure if you can do this either, I know wifi works for data transmission, but accessing the computer this way with android may not be possible, yet.
Gps problems may depend on which nbh you have installed, some of the more recent nbh's perform better than older ones. I'd recommend Kallt_Kaffes NBH's as I know these are quite good for gps, for me at least. http://forum.xda-developers.com/showthread.php?t=660158, you will need to load the nbh into the editor and set the correct panel type, keyboard, and 3d type, ( donut in your case), then save as kaisimg.nbh and copy to SD and flash using power+camera, again this will not affect your android install.
Power off issues may be nbh related also, however this can still happen anyway, usually pulling out the battery will sort out the reboot issues.
many thank for quick reply, I love Android on my phone
thank you again
I was wondering what steps to take when the android loader gets stuck in a loop, when I install andriod right after install it boots fine but when I try to boot second time, after andriod appears on the bottom of the screen it will go into some kind of loop. I have tried different radios and a different version of hardspl, and a few nbh panels as well as reinstalling the system, any help would greatly appreciated.
Phone: AT&T Branded TILT
OS: Nand w/Incubus Super Froyo Installed
Radio: 1.70.18.02
NBH: kaisimg-panel2-320-tilt-froyo-07-07-10
HardSPL: v3.34.hard
Everything looks fine, although I haven't used that particular build, however bootloops are commonly build or kernel related.
Have you tried other builds? Or is it just this build that does this?
Generally panel type only affects the display on the screen itself, or sometimes problems with sleep mode.
Since you have a froyo kernel installed, maybe you could install this build to see if it helps? http://forum.xda-developers.com/showthread.php?t=724821
Yeah I have tried other Froyo builds and they worked, but I just like the way Super Froyo build is put together. But if it is the build then its is the build. Oh well maybe next release. Ok thank you for your time, guess I will give the GZO build or the one you suggested a try.
Installed the kernel you suggested, it works. It boot looped once, then I cleared the dalvik cache and it booted again after install. I don't know if that is what it is used for, but it worked after that.
It is a awesome build, battery life works correctly, signal is good with radio, and wi-fi works good. But I had one more questions.
1. What is up with live wallpapers, on some builds I have used some work on one build but not the other, I have looked through the forums, but can find no solution for this. Is it because of the amount of RAM in the TILT as I saw somewhere or is there a fix. Even in this build when I try to load a live wallpaper on a couple of them is just stays on wallpaper loading and stay black screen.
I would like to take a minute to thank the people that make this awesome stuff, now my TILT has more current software than my BACKFLIP, so my older phone is now newer than my new phone, and I would also like to thank the people who help others out on this forum, I don't think a lot of people like myself would get anywhere without your help.
Forgot to mention dalvik cache. oops, ah well, you found it anyway
It's another of those occasionally useful things, like fix permissions, I have used it before to fix unusual behaviour, but not tried it on a bootloop.
Live wallpapers are usually pretty buggy at best, it's complicated, memory is one problem, cpu speed another, and 3d handling yet another, some wallpapers work ok, but slow, others just won't, ever. I just delete them before install, along with a few other minor customisations such as deleting a few ringtones and notification sounds, changing boot animations, nothing that affects the core of the build, just personalising a bit
I'm using:
1)incubus's Super Eclair 6.1, with the downgraded settings.apk which enables wifi (another member offered the settings.apk from a previous version (3, I think) as an androidupdate.tar)
2) Currently radio 1.71.09.01 (thinking of switching to 1.65.21.18 to improve reception)
3.) Currently using the latest Dzo kernel for eclair (07-02-2010, I think)
My problem is that my data connection doesn't work (and this has been an issue on just about every release, save for one Froyo install where the data autostarted once, and then I never saw a 2g/3g notification and mobile internet didn't work).
I'm currently in India, and I've used the correct APN settings (they have worked on other phones including Nokias, iPhone, and a USB modem). I've tried asking the question in the SuperEclair vogue thread, but alas, no love. I'd really appreciate if you could help me on this, or at least guide me in the right direction, because android (especially eclair) is too awesome to abandon for this single issue.
By the way, everything else works, Wifi (with the mentioned update), GPS, Voice, and SuperEclair is the fastest that I've found so far.
I have seen a number of issues with data such as this, and i'm afraid none have had a truly satisfying resolution.
However I would try:
Downgrade the radio as planned, this may help, and certainly won't hurt.
Boot to installer, and run fix permissions and clear dalvik cache, this has been known to fix various issues, not certain why yet.
Double check the apn settings, especially the MCC and MCN settings, a lot of online guides seem to miss these two, but they are important.
Not sure where to point you after this, apart from a long trawl through the thread here, however if you do get it resolved please post back, and if not, try another post on it in the build thread, along with the steps you have taken to resolve it, it may convince someone to have a closer look at this issue.
data connection
I too have had this problem after installing a recent froyo build to nand....I had checked no.start data when flashing dzo's latest kernel using nbh editor and had to reset my apn settings. Remember to open your modem utility and press connect twice....this actually starts the connection......Radio type could also be an issue..Ive had good luck with the 165's with 2 different froyo builds....Hope this helps.....
Thanks for the replies! I'm going to try this out (need to recharge the data service on my prepaid) but one thing I did notice was that the MNC/MMC were different that those listed on my providers website. Hopefully this will help.
I have tried to switch on the data using the modem utility, and the utility itself says that data is connected, but it never really worked. In settings, there is an on/off switch for mobile internet, and a mobile internet settings. When I click the on/off switch, then mobile internet just goes gray and does nothing. I'll try to post back to the Super Eclair vogue board, but I think that Incubus might have moved on...
I'll update once I get my gprs service paid up. Again, thanks for the help!
The process com.android.phone has stopped
Those are my first Android experiences, so I`ve got problems .
Phone : Kaiser (TyTN II)
OS : Win Mo 6 Profess (original-not flashed)
Radio : 1.27.15.32
I`m trying to install Android on the SD card, without additional partitioning. I`m currently trying this Android version : Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 gamma [Based on OpenEclair 1.2.2 (XDA thread)]
and using this too : How to run Polymod’s AWESOME 2.1 Eclare Build and Updates (the forum didn`t allow me to post links for the Android versions). I`ve tryed this too : VaniljEclair RLS7c - A fast and stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-07-02] - the same result
I`ve done everything according the instructions... Starting Haret.. Hit D-Pad, Install, clear data... etc. etc... It actually starts to install... and everything seems fine... At some point it brings me again the install menu, I`m hitting exit, and then come some errors ?!? I forgot to type them down... Something like that some files cannot be found... And after rolling errors for a while the Android actually boots ! But then come errors too... At the first time it brings me the dial pad to enter my pin-code... I entered it , but it says it is wrong...I wasn`t wrong ofc . For the next time I simply disabled my pin in Win Mobile and try again... After the Android booted it says : The process com.android.phone has stopped unexpectedly. Please try again. , and some button like "cancel" or something like that. I'm hitting it , the Android guy appears and a message " Hit the android to begin" with a hand pointing it. I`m hitting the android - nothing happened !
I`ll be greatfull if someone can help me , or at least give me some clues !
Thank you .
p.s. sorry for my english... not my native language ;-)
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Thanks
zenity said:
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Click to expand...
Click to collapse
Thank you for your fast response . But I`ve tryed (I`ve tryed again today) before to download an official WinMo 6.1 ROM from HTC_com , but according to my TyTN II`s serial number , they said : "Sorry, this software download is not suitable for your device". And I want an original ROM... I`m not sure that I can manage to flash a cooked one on my HTC . So I guess I`ll stay with the original WinMo 6.0 withut Android .
Thanks anyway
To flash a cooked rom you would need HardSPL, it is possible to do this for WM 6.0.
Regarding an upgrade to WM6.1, this too should be possible, I'd tend to disregard the warnings about upgrades being 'unsuitable'. The unavailability of certain upgrades is more to do with them being designed for certain providers or areas, rather than their actual unsuitability for the device itself.
If you have a need for a language specific rom this too is probably available from another source, if the wiki was available then there is a table of rom upgrades that would almost certainly contain just what you would need.
Note that the wiki links are all official HTC roms, and would not need HardSPL.
@Zenity - You had given me some advice on getting the gprs working on my eclair install (Eclair problems/Android problems thread). Well, I ended up ditching Super Eclair for polymod 2.1d, and mobile data started working out of the box (which is odd, because it wasn't really working before, but who am I to question?!). Now my only issue is that if I activate wifi without first deactivating mobile data, then wifi gets caught in a loop and won't connect (i.e "Connecting, obtaining address, unsuccessful, connecting, obtaining address, unsuccessful" and on on on...). Then if I try to deactivate data or wifi, both get grayed out and say turning off, but never do. I'm fairly positive this is some conflict between data and wifi, because I've connected to the same AP without any issues while the data connection is off. Regardless, this is the most fully functional implementation that I've found. Still playing around, now that I have the time I'm diving a little further into tweaking and hacking through these releases.
Thanks for the help man. I've been on xda-devs since I first got this Att Tilt, mainly reading and learning, but I've noticed that a fair number of people don't take the time to further explicate and help people through problems and troubleshooting. You and kallt_kafee are both awesome when it comes to responding to less knowledgable users, and I for one really appreciate it. So Cheers, bro!
Thanks matcha, the main reason I still find polymod 2.1D my build of choice is that of them all, it just works, all the other builds do to, but I have found less issues from users on Polymod than the other builds, perhaps it's age has something to do with it, it has less 'new' features than the others, so less to go wrong, and perhaps also that it has grown with the whole android on kaiser project.
Anyway, appreciate the vote of confidence, really I'm just trying to give back a small measure of what Xda-Developers has given me

New to WMO 6.5, Android device broke

Ive used an android device for about 2 years now, and it just recently crapped out on me. I have a unlocked touchpro2/tilt2, and i want to flash a custom rom to it, any suggestions of which rom i should flash, and what is the easiest way to go about doing so? Ive read the flashing for noobs post, and it made no sence to me, it was all sooooo simple with android. So basically i am asking if anyone would be willing to help me with the process?? PLEASE I NEED HELP WITH THIS!!!!
It looks daunting, but it's actually quite easy. Just reread a few times, and after the terror racks you jump in. It's either that, stock ROM, or run XDAndroid, and be patient about the sporadic updates.
Honestly, though, HardSPL is very easy. Just do your research, and welcome to your new Rhodium!
thanks, ive been looking it over for a few days now. Does xdandroid require me to do all that syncing crap too?? Isnt there like a flash recovery tool like for the android devices, where i can just punch in a few commands?? Or at least a tuturial video that i can see it done?? you know how Android has Cyanogen, does WINMO have a compareable dev??
I do want to become more familiar with winmo, what are the best roms avaliable?? Im only using a tilt2/touchpro2, so please take the system specs into consideration. Also i love how easy it is to navigate with android, is there a winmo rom that is as user friendly??
looking over the instructions now about to sync and flash, but when do i flash the radio??? i need help with this!!!
alroco20 said:
looking over the instructions now about to sync and flash, but when do i flash the radio??? i need help with this!!!
Click to expand...
Click to collapse
I'm sure this pictorial tutorial will help you. Let it open your mind as it opened mine. Then, you shall be awakened into custom ROMs land.
P.S. You don't have to flash a radio -- it's just recommended if you have horrible signal and/or battery life.
P.S.S. Remember to back up everything on your phone before you flash! Use MyPhone or PIM Backup (for e-mails, SMS, phone numbers).
P.S.S.S (How many "s's" can you have?) You need to flash HardSPL before flashing anything else. HardSPL is covered in the pictorial I linked.
This is the best flashing process: Task 29 (basically, it flashes a blank ROM) > [flash radio] > flash ROM > [let the ROM finish loading up -- so you are on the Today Screen] > Hard Reset (Press/hold Power + Talk/Send + End at the same time).
P.S.S.S.S Have fun!
THank you, did my first flashing last nite, and all went well. You guys at this site rock. Keep up all the good work and help!!!

[Q] Moving from WM6.5 to Epic 4G, suggestion?

Let me first tell you about myself.
1. I'm a geek.
2. I don't like programming that much, so I avoid it. I learn stuff to get by, but yes I avoid it. I have access to both XP & Linux, running it as a PDC server at home along w/ VPN server (ClearOS w/ modified bridge OpenVPN ).
Some background about myself that may help you answered my question, or pointing in the right correct direction. (no middle finger to the right.) And here is past experience on mobile device.
I have used Nokia 770 and N800, fun to hack back then but it's pretty useless now. I had SERO 500 , which I just recently upgraded to SERO Premium 500. I have been using HTC TP2 w/ Energy ROM. It has been good, granted TP2 is an older phone w/ older Qualcomm CPU. Energy ROM did help a lot, along w/ a few tweak, I manage to keep the battery to last pretty long and upon boot up I got about 70% memory left to use. So, I'm not exactly new to the custom ROM myself. That said, I'm new to the Android phone and custom ROM. I have been reading in the past 2 weeks deciding between Epic 4G and EVO Shift 4G. Well, I end up w/ Epic 4G as a final choice. Already ordered the phone, but still waiting for it. So, I don't have Epic 4G as off right now. But I would like to start playing w/ it once I get a hold of it. That's why I end up here asking for some wisdom in this forum.
After doing some research, I think I think get the basic concept of flashing custom ROM on a new Epic phone. If I got it wrong, let me know.
prep step 0. get USB drivers.
1. root it, 2 steps root?
2. install CWM3 for recovery.
3. flash new ROM, appearance each chef have difference instruction for the install. That's where it start confusing me.
Few things that are unclear to me, should I update PRL prior to rooting it and flash new ROM or after? Or should I even put DK28 on it prior to start rooting it? I'm guessing a no on 2nd one, as it's not necessary.
Now, rough question, what ROM is close in term of the way it package that most closed to the Energy ROM. I'm leaning toward either Nebula or Bonsai. Since Epic is only on Sprint only, I'm sure some of you have use TP2 or might have even used Energy ROM in the past. If you haven't, I'm sure you know where to look for reference. Again, what I very looking for is a Froyo ROM(if not Gingerbread) that's clean, lean, snappy and stable. In fact I don't even care if the Samsung TouchWiz is totally removed. I even think I might like Touch Flo interface better, but I suppose I won't have it. I think I have read enough to know where to find the TouchWiz apk(s) and remove it, so that's not a big problem.
Welcome to android your steps are 1.get drivers 2 dl one click root plus cwm. Once you have it rooted with cwm you can start flashing. If you want to go to the froyo leak then flash the upgrade first then start the root process. If you go with froyo,which I love it and I have bonsai rom and it works perfect, you have some choices when rooting. If you want to stay with the stock Rfs filing system use the one click with cwm v2.5. If you want to run ext4filing system then run the one click root with cwm3. This new clockwork will convert your filing system to ext4 for you. My setup is in my sig and is my favorite. It's up to you to pick the rom you like the best. Make sure before you root turn your USB debugging on. Good luck and welcome to android.
In addition to what was posted, Nrgz is a great chef. I used his stuff for quite some time when I had my TP2.
That being said.. WinMo and Android are 2 different animals.
I think you'll find that you're going to flash each ROM and play with it for a few days to determine which one you prefer.
They are all very nice in their own right. Some of us have favs. The neat thing about android vs WinMo is that after you flash a ROM in Winmo, it's a big pain in the ass to set your device back up (if you weren't using custom scripts).. with android, it's much much easier and can be completed within a couple minutes.
I think you'll enjoy that aspect of it.
Welcome to Android
I'm making the same transition as you, long live the TP2. I followed the how-to recommended by the wiki, but a lot of that is actually a waste of time at this point, except as a learning experience. The steps that actually got me ROMed (I'm assuming you'll pick an Ext4/DK28 ROM:
1. install 32-bit drivers on Windows
2. put phone into debug, connect
3. flash DK28 to phone using ODIN
4. copy zip for ROM of choice to root of sdcard
5. run cwm3 to change file system, root device
6. flash with custom ROM while in recovery
From what I understand, only steps 4 and 6 will have to be repeated when trying other ROMs. Wifi tethering isn't working for me on ViperROM, so I think I'll try something else.

Categories

Resources