Hello everyone,
Xperia is my first Windows mobile and therefore kinda novice to some terms used in this area. My colleague helped me in installing new ROM HTC touch it. It now looks like an HTC phone with cool graphics.
I know mine is tf3d but how can i verify. Also I keep listening to terms like manila, jailbreak, brick etc can someone explain me what these terms relate to. Need little overview of all these terms used.
I tried to install new themes and therefore installed tf3d config tool but it doesnt work on my X1 gives me an error.Is there any other way of installing these themes. Mine is the default black theme.
Hey sandy,
you can check your version under the Settings tab in your TouchFlo at the point "Info".
Also, if you can switch your home clock back and forth i can assure you its TF3D .
By Manila is meant the same as with TF3D(TouchFlo 3D). Jailbreak is usually used to be a name for an iPhone hack, but in our case you can categorize it as something connected with HardSPL. It's a tool that patches your phones rom manager and allows you to flash it with custom roms(like the one you got from your friend - means that your phone is already equipped with it).
I'm not sure about compatibility with the config tool since i've never used it, but i can tell you that the easiest way of applying themes is the usage of cabs.
You can find different theme-cabs in this section (themes and applications).
If you have any other questions I'd suggest you just to ask in here.
Thanks mate for clarifying, do you have a simple procedure on how to flash rom and install new custom roms. As for theme cab file is it possible for you to provide me with one theme cab file i just wanna test it out before downloading others. I assume i can revert back to my original black theme incase i dont like the new one.
hello m8 in this thread there is very usefull tutorial on how to flash custom roms and if u bored there is also tutorial on how to get back to official sotck rom. read it carefully and in 20 mins u will become profesional flasher http://forum.xda-developers.com/showthread.php?t=431218
i hope i helped you
The link you provided is about hardspl whats the next thing to do after hardspl? How to install custom roms available in this forums? Is there a procedure for doing this.
Actually there's always an .exe file with the rom package.
you simply start the .exe and follow the steps described.
The only thing to care about is a stable activesync/dev centre connection and a battery life of above 50%
06/16/2011
The screenshots are not important. This is not a theme!
You can install a theme from here, for example if you like.
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com
This is the actual Android Froyo operating system for the HTC Kaiser
So, stop asking me for screenshots and software installed, it's not relevant.
And the how to install guide is been posted here
Bug reports are welcome, other then that, I don't wont to hear from you.
Don't post a thank you either, there is a bottom for that, and you can also vote on the poll up there, but install and test it first!
Again Bug reports only, please!
I been working on this for 3 days straight, and figure I'll share what I got.
Everything seems to be working, except the camera is blurry, but that seams to be the norm.
Included is the rom, radio and kernel
ROM: 2.2.1
Kernel: 2.6.25
Radio: KAISER 1.70.19.09
Panel: 2
Key Map: US Normal
Resolution: 240x320
Storage: Nand & Nand
Most everything is installed in userspace and can be uninstalled or upgraded.
Oh got GO Launcher EX installed (Also in user space)
Credits:
I stole ideas from, and used following tools:
Makers of atools
Makers of NBH creator
HTC Flasher
kallt_kaffe
Krazy-Killa
dzo (dzo's posts wore a big help. just wish he would answer his own questions after he found the solution)
n2rjt
and many more.
@todo
Resize NAND partitions to the smaller system size
Original post and download Links are posted on my blog:
http://press.pzzazz.net
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
Yeah witch apps are include. Some yours tweaks or etc... ???
MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
That sounds like a trick question.
Yes, at first I compiled everything my self but then to resolve bugs, I looked at other systems and basically stole stuff from them to fix my bugs. In other words, I can't take all the credit, it was a community effort.
Neo2SHYAlien said:
Yeah witch apps are include. Some yours tweaks or etc... ???
Click to expand...
Click to collapse
I removed most everything from the system and installed it in user space. So the system is very lean. You can uninstall what you don't like.
how is the rom？just waiting to see
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
tundelogic said:
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
Click to expand...
Click to collapse
here is the howto
http://forum.xda-developers.com/showthread.php?t=680518
kkp said:
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Click to expand...
Click to collapse
The screenshots are not important.
This is not a theme.
You can install a theme from here, for example if you like:
http://golauncher.goforandroid.com/category/themes/
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com/
This is the actual android froyo operating system.
Anyone else having trouble getting the kernel to install?
I get to 33% and the phone reboots...
Radio installed fine even though I was already using 1.70.19.09, just to be sure I installed everything in the package.
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
I also tried to install this kernel but I can't. Flashing in hardspl after few second give folowing error:
00018003
Os Fail
Update Terminate
UPDATE Fail.
Changing parameters in atools not helping. Every another kernel is flashing without problems so it's not phone fault
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
BTW, I call shenannegans on one of the 5-star votes... just sayin'.
Your kernel have fake ;/ . rom works great ;D
sorry for bad english;p
PoXFreak said:
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
Click to expand...
Click to collapse
1) The kernel doesn't care where you place the files. Right now I use a debian system with Ferora and Gentoo in a chroot. Both work fine with the Debian kernel.
In other words, if you have a kernel that works for you then use that it should work with the rest of the installation.
2) I don't get what you mean with files are "split up into many files", I am just guessing but you must be extracting it wrong. Maybe it's a windows thing, I haven't used windows in 15 years so I wouldn't be able to help you with that.
3) I have included everything you need to duplicate what I got, which works for me, and it appears to work for others too. Now i don't use that phone much, and there might be bugs I am unaware of, but don't tell me it doesn't work at all, just because you can't get it to work.
barmalini said:
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Click to expand...
Click to collapse
barmalini, it appears that a few people have trouble installing the Kernel, but the ROM seams to work for everybody as far as I can tell.
According to my server records the files have been downloaded over 200 times and I have yet to hear a complain about the ROM.
So I would say try to install the Kernel, but if you can't still use the ROM with a Kernel that works for you.
If you have trouble installing from windows you can also try a live CD from debian or knoppix. I installed everything from a Debian system. (Knoppix is based on Debian)
If you don't know what a live CD is then go here for info:
http://wiki.debian.org/LiveCD
PoXFreak said:
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
Click to expand...
Click to collapse
PoXFreak,
you are not the only one having trouble, installing the ROM it appears.
I am wondering, are you also using Microsoft Windows to install the ROM?
If so can you try again with Linux, because it worked fine for me.
If you don't have Linux you can use a Live CD
Also if you can't get it to work, try the ROM with a Kernel that works for you.
Please report, I will check back.
Hi
First of all I'll apologise if the flavour of this post is similar in nature to a few others but I haven't quite found an exact match for what I need when searching through the other posts and I really need a definitive answer.
The background.....
My company use a third party forms application for passing data between our field service technicians and our office. This application had been specifically designed to be run on Windows Mobile devices. Up until very recently has been perfect for the task.
With the arrival of WP7 and Android in the phone market I have been finding it increasingly difficult to source devices running windows mobile. Those which I am still able to get hold of have varying versions of WM running which presents me with a variety of continuity issues. Providing support over the phone can also be quite challenging due to slight version descrepancies.
Recently one of my suppliers has been able to source me a large number of HTC Touch Pro 2 devices, however they are again running slightly different versions of the OS.
I would like to be able to use a standard WM6.5 ROM accross all the TP2's regardless of the original version or region of the device. I have been in touch with HTC without a great deal of joy. They simply refer me to there download page where invariably I am only able to download and install the ROM which corresponds to the individual device serial number.
Finally the Question.....
If I download a custom WM6.5 ROM can I run it accross all my GSM TP2's and if so then can you point me in the right direction?
Thanks for any help you can give
if these are all unbranded phones i suggest hard spl on all of them, and download a stock rom for one of them extract the .nbh file and flash them all to the same build...easiest way....
WC
Wild Child said:
if these are all unbranded phones i suggest hard spl on all of them, and download a stock rom for one of them extract the .nbh file and flash them all to the same build...easiest way....
WC
Click to expand...
Click to collapse
Are you really suggesting a stock ROM to this guy over your ROMs?
@Si_UK If you want the stock look without the bloat and with more speed, go with Wild Child's Illuminati ROMs. They retain the functionality of the the stock ROMs, but are tweaked for better performance and stability across the board. These ROMs are a very nice business choice. Like he said, though, you will need to Hard SPL the devices to be able to flash anything other than stock ROMs.
Thanks guys
I managed to download a standard rom from HTC using one of my UK device serial numbers and gave it a try to see if the RUU would work on one of the non UK devices. It did and works fine. I was planning on replicating this now with all the devices to ensure they're all the same.
I am now going to try and Hard SPL a device and use custom ROM as recommended. I like the idea of being able to improve the speed and lose some of the crap.
Fingers crossed as I've not done this before
cajunflavoredbob said:
Are you really suggesting a stock ROM to this guy over your ROMs?
Click to expand...
Click to collapse
Hmm, Sense 2.1 roms where... ehmm... usable... Not THAT bad after all.
However those S2 Sense 2.5 aren't capable of being used more then one day.
Hello XDA,
I've been following you for years. I started following you with my first Android phone, an HTC Hero. I've been very happy to be able to use a community ROM that made a far better experience than the stock ROM.
I recently got a brand new HTC One V PrimoU, and I'd like to make it my new polyvalent tool.
I'm not a noob in computers, kernel/linux related stuff, electronics, networking. I already tried some ROMs. In fact, I started with KangBang 3.0 (the same version as now I think), but both WiFi and BlueTooth were not working. Android could not even detected the WiFi MAC address, so I guess it was a driver or wireless chip firmware related problem. I think I was the only one affected, so it was maybe a bad flash or I used the wrong kernel. I did'nt investigate more at the time, but if it happens again to me, I'll send some system/kernel logs.
I then tried AOKP, had a great (really) experience with it, except that the Jack plug sound quality was awful. No bass, only mid/high tones. I even thought my speakers were dead at first, but then tried with headphones. Now, I want to try KangBang again, because that ROM was good, and fast, just missing WiFi.
TL;DR
I'd like to ask some precise questions about KangBang and the HTC One V.
I initially wanted to ask in the ROM dev thread, but can't since I'm a new user, so I ask here. Sorry if the questions are stupid/simple/answered, but let's make a clear base, with precise interrogations and answers, so that they will never be asked again
The kernel is included in the .zip file. Still, do we need to flash manually ? Or will the Aroma installer handle that ?
What about ROM Manager ? Is it recommended to use or is it a good way to brick a phone as I heard ?
Does this ROM change the base Android system and file structure ? Would it be compatible with a side-by-side installation of a Linux system such as Debian ? (To see what I mean by side by side installation of Linux, search Debian Kit for Android on Google, as I can't post links)
Also, I'd like to tell ROM makers these advices (don't take them bad, I you think I'm wrong about them there's no problem, just tell me why) :
It would not be a bad idea to give a simple statistic about the ROM : the load average with the ROM installed on an idle and clean phone. That would give a good indication of idle power consumption and ressource wasting.
I see that users reporting problems with their devices NEVER include any kind of debug information. Maybe you should ask for them, just because by searching for this debug information they might solve the problem themselves. Most Android systems and kernels report a LOT of information, that we can access with simple commands such as dmesg.
Last but not least, I would like to thank you, ROM developers and XDA users for allowing me to play this way with my phone, and to make it work exactly the way I want.
Hugo G.,
ummm this device has kangbang?? (btw questions go into q&a )
so i'll move onto the TL;DR which i was grateful for
1) The rom thread should say what kernel but yes, we don't have s-off so flashed manually
2) Ignore rom manager don't touch it
3) think of it as the differences say with debian vs ubuntu vs mint all basically debian but all with they're own differences (pros and cons)
also about the "suggestions" to the devs, that will NEVER go down well, why should YOU suggest to use what to put in the threads also i know in my threads i ASK for logcats time and time again...
hope this helps
if you need more info i'll be welcome to add more, but 1st i need sleep BADLY