Related
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.
Hi,
I have a HTC Desire and just after I got it I managed to muddle through unbranding it to get rid of the Vodafone addons. At the same time I managed to root it.
I recently decided to take the jump and try some of the non stock ROMs as that's one of the reasons I went for Android.
I have to say there are some great tools out there and my sincere thanks to the developers, namely:
o AlphaRev
o ClockworkMod
o ROM Manager
o unrevoked
Wow nandroid is a real bare metal restore that works ))
When I decided to take the plunge I went through the recommended approach detailed elsewhere in this forum.
I've so far tried LeeDroid, Oxygen & Defrost.
I now have a slight problem that seems (perception) to be getting worse.
In summary, if I reboot into recovery (either power/back or ROM Manager) it sometimes works and more often now doesn't work. When it fails it just hangs at the AlphaRev screen, just a boot screen I guess. When it hangs it never recovers, battery out and try again, again, again .... then it'll work.
Does anyone have any thoughts on this boot into recovery issue ?
Colin
~~~~~~~~~~~~~~~~~~~
HTC Desire
AlphaRev S-OFF
Radio 32.49.00.32U_5.11.05.27
ROM currently Defrost (still trying the various flavours)
This is the issue, people get a brand new shiny phone and the first thing they do - as opposed to actually USING the thing - is find as many ways to bodge it as possible...
People need to actually read everything, take some time to absorb it and then read it again. Then use the phone as chances are unless they're a real app whore they'll never need to worry about internal space...
I've no idea why you're having issues but I assume you don't have a copy of the RUU your Desire originally came with so should you need to return to stock you can?? this is the first thing anyone should do before undertaking any type of customising and would save a lot of headaches
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
how bout reflashing recovery?
gol_n_dal said:
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
Click to expand...
Click to collapse
I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
>> I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
NP,
I get it all the time having to "help" people who tried things on their Home PCs or TVs, BluRay, HDMI inerconnect, ..... Shops offer bloody useless help to them. ;-)))
>> how bout reflashing recovery?
Yes, I've tried reflashing ClockworkMod through ROM Manager, it's currently 2.5.0.7 confirm by ROM manager and when it finally gets into recovery.
It just seems an intemittent issue that only arises when I want to do a Nandroid backup or "play" with the ROMs / Radio etc. The only solution I have is to remove the battery, count to 3 and re-insert it. Then try again.
It's not a show stopper just a real pain, especially when installing a new ROM/Radio when it's supposed to reboot. It's a case of how long do I leave it and hope it recovers to sod it, battery out and pray it's not bricked as a result.
Regards
Colin
I've run into a very strange issue where ADB isn't functioning properly in two of the sense Roms I've tried recently, both Fresh 3.5.0.1 and the newest Evio Rom by Caulkin, 1.8 I believe.
I can't get the phone to go into USB debugging mode, although it works just fine in CM7 and another gingerbread rom I tried yesterday.
Here's some of the things I've tried, give me something I haven't tried, I dare ya!
Wiping properly in recovery (with Amon Ra 2.3, 1.8.0, and clockwork recoveries 3.x and 2.5.x)
Using Caulkin's Format All in recovery
my golden nandroid backup of Fresh didn't work, neither did a fresh fresh install
ADB works in fastboot or recovery, but not in the ROM
ADB works just fine in CM7 and non-sense ROMS (tried 2)
I tried going back to the roots by flashing my post nand-unlocking PC36img.zip and it worked fine, new fresh 3.5 install, borked.
Different USB ports
Different USB cables
Different Android SDKs
Different Android USB Drivers
My wife's HTC Hero works fine on those same ports on the same machines
two machines, one XP 32 bit and one win7 64 bit, wifes works on both, my evo works on neither.
doesn't work on stock fresh kernel, doesn't work on netarchy custom kernel.
Used to work, because I use my Evo for a test device on my apps, but I can't remember if it has ever worked on Fresh 3.5
Tried formatting my SD just to be sure there wasn't a remnant on it.
And oh yes, I made sure USB Debugging was checked.
As you can see I tried a lot. I'm very familiar with ADB and its nuances. This is genuinely stumping me, as I feel I've eliminated nearly all variables and tried nearly all configurations.
Any ideas, or anyone have something similar happen?
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
trimeijer said:
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
Click to expand...
Click to collapse
I'll flash back to Fresh tonight and check the build.prop to see if you're right.
I did notice that Flipz said he took the debug message out so it shouldn't pop up, but maybe that meant he disabled those lines in the build.prop. I would think he would know better than to do that, though, as that would disable ADB altogether, something he surely would see. It's totally possible though.
is there any way that mine could have gotten modified or something I wonder? I'd think no, because that would have to come from his install, especially on my new installs I did. Weird.
Unfortunately, my default.prop is the same as in the correct version in the link you posted. I'm literally at a loss of what else to try. Hoping some more pop in to share as I doubt we're the only two with this or have experienced this before.
I think I've figured out what's going on, now I just need to figure out how to fix it.
Like this post below, I think that the ADBD process isn't running because I couldn't find it in my process list. They used one from another build image and replaced their current one.
http://code.google.com/p/android/issues/detail?id=9437
Anyone done this before or could provide some guidance in addition to that thread?
I'd really appreciate the help.
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
trimeijer said:
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
Click to expand...
Click to collapse
Have you tried the "adb remount" command prior to trying to write to system? That will get you sometimes.
I pulled the boot.img from CM6 and replaced the /sbin/abdb process with the one from CM6 inside the Fresh boot.img. When I repacked, everything looked good, I installed Fresh Rom, and then it won't boot. Not at all. Wish I knew more about how to do that. I think I'm going to try again, but was following the perl scripts he posts on this page:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I had to suppress a message in one of them because there was a fourth file, and it says it was not created to be able to handle those. Read on another forum to comment it out. Anyway, it didn't work but I'm going to keep trying.
Installed CM7 again, and there it is as a process, /sbin/adbd. That's got to be the key.
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
trimeijer said:
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
Click to expand...
Click to collapse
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
kmartburrito said:
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
Click to expand...
Click to collapse
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
JusticeAA said:
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
Click to expand...
Click to collapse
Hey, trying this now, will let you know what I find. Thanks for the idea!
gpz1100 said:
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
Click to expand...
Click to collapse
Unfortunately, this is already set as such in my properties. I tried it anyway though on Mikz rom, and ADBD still isn't starting or working afterwards.
You know what it seems like? It seems that this is an issue with the HTC Kernel after one of the first versions that they released after FroYo. I say that because it works on Fresh's 3.1.0.2 rom which was one of the first FroYo builds, and it doesn't really work after that, which was a newer base build and newer Kernel. Doesn't work on really any other sense-based ROM for me either.
It DOES, however, work on any AOSP rom (which also uses a diff kernel) Which is one thought as to why it might not be working for me. The strange thing is though that this is somewhat isolated to my Evo. Maybe I have a lot of bad blocks or something, but something's fishy in that it works with early FroYo roms and any AOSP roms consistently, but not new Sense roms. So, either the majority of Sense devs are using Fresh's stuff as a base, or the problem is a bigger one related to the base build or Kernel itself.
I tried using the old HTC Kernel on a new build of Fresh, and found that the ADBD process did in fact appear when using a ps command, but it still did not function properly.
And furthermore, there is absolutely jack **** on documentation out there on what makes ADB work, or what could make it not work.
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
gpz1100 said:
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
Click to expand...
Click to collapse
Yep, several versions of Netarchy's kernel, several HTC, no dice. I suppose that should rule out the Kernel and point to the base build. What is really weird though is that it's happening mostly just to me, although there are a couple others for the Evo I'm sure (many might not even know it) and there are definitely others affected like I am on different devices.
Hardware 002 and rooted using part 1 and part 2 of toast's method.
Hi all!
I have spent over half an hour searching but to no avail so thought I'd ask here, how are the kernels hacked or modified?
When it comes to the real tech stuff I'm a bit lost, and to be honest before I stumbled across this site I knew nothing about making custom ROMS, but thanks to all of you out there, you have taught me loads without me asking much, so its here I need to ask!
Thanks in advance for your time & replies,
Arty.
just search the web for "linux kernel" the android kernel is a linux one.
when you know a bit about linux kernel you can add kernel mods to it, as in android.
you just need to download the source of the kernel modify it and compile it than.
hope this helped a bit
ps.: and if you dont have the source you have to be a tech/kernel genius like -snq
Thanks for your reply there crendot!
I was afraid I'd have to know about Linux stuff, which to be quite honest I dont!
I have messed about with a Ubuntu Virtual Machine in the past (when I first read how to root the Desire) but I find it too difficult to understand, I'm much more at home with the old DOS commands personally!
Only reason I ask is that my fone is playing up and has overheating / reboot loop issues with anything greater than Android 2.2 (since it came back from repair when I dropped it & cracked the screen completely) and so far I am stuck with my own slightly customed Rooted 2.2 with standard features (no 4-in-1 menu, no wake & unlock on trackpad and the DSP manager wont work) also, I have not yet tested it, but I know only a few kernels will let me send & recieve MMS, the previous build was a lightly customed LeeDrOiD_V3.0.8.2_GB_A2SD ROM, but alas kept bootlooping after it became warm and I found I couldnt do much with it :-(
I am hoping to get a shiney new Sensation soon, but until then I wanted to know how to modify the kernel to add / remove stuff!
Is there an easy way to take a kernel file & be able to 'read' it so I could copy the stuff I need into the stock kernel at all, or is that my wishfull thinking again?
Thanks again & sorry about the long reply!
Arty.
to understand what a kernel for the desire is, u can download the stock one on the htcdev.com site http://htcdev.com/devcenter/downloads
for example u can download the latest for our desire: "HTC Bravo – GB MR – 2.6.35 kernel source code"
that is the source code..u will see there are thousands of .c files...is not easy at all modify the kernel..it requires strong skills on linux and C language
about the send sms and mms, that is related to the rom and ur apn settings i think..not to the kernel..the kernel handle very low level actions..
maybe u would like to make custom roms..this is a bit much easy if u just cook it for example with the android kitchen (search for it)..the rom contain the kernel and the operating system and some apps
so lets check the facts!
did the phone overheat when it came back from repair (with stock rom)?
or have you flashed the new rom instant?
i would say you save all your stuff and do a nandroid backup.
than you follow this instructions to flash the rooted stock 2.2 rom and the radio
if the problem is still there i would say its a hardware problem, if not you can try other roms as long as no problems occure
dont play around with kernels, you dont have to, the stable kernels are in the roms
if they arent stable for you its not the kernels fault
i guess something messed up while you flashed something...
ps.: if you have absolutly no linux skills and so on, i would say you read into that before playing around with your mobile ^^
andQlimax:
Thanks for your reply also!
I know the APN settings for the mobile data & the MMS as I have written them down, the strange thing is I rooted my fiancee's Desire with the same ROM I was using at the time & she couldnt send or recieve MMS either (I'm O2 and she on Orange, both contract) and I have only found a few custom ROMs that allow the sending & recieving of MMS messages.
Also, I can make custom ROM's, I use Android Kitchen for most of the stuff (such as de-odexing, adding root, bash, busy box etc) but I find mostly when I bake the ROM using the kitchen I have errors on install, so I just prefer to use the kitchen for adding the needed stuff, then I'll just use windows to add / remove apps, boot animations & the audio files I want and just zip it myself & flash which has a higher success rate if I'm honest!
crendot:
so lets check the facts!
Q: did the phone overheat when it came back from repair (with stock rom)?
A: No, I didnt have stock ROM on, I still had either LeeDroid HD or a HD InsertCoin ROM, which when I got the phone back I did a nandroid restore (I make them quite regular & copy them to my PC for extra piece of mind!)
Q: or have you flashed the new rom instant?
A: I also have installed an untouched ROM(untouched by me) a day or so after as the nandroid backup wasnt the version I wanted, I was due to be on holiday to Blackpool for a week, so I flashed the LeeDrOiD_V3.0.8.2_GB_A2SD ROM on both my desire & my fiancee's desire, hers was stable, mine I couldnt have the screen on for long before it got too hot (managed about 5 picture captures before I had to turn screen off for a while or it got too hot) then thing is, my fiancees gets got too, mine is the metal holders for the memory & sim cards, i either have to place something cold on them like a glass or even hold a fan to it for a few minutes until it cools down again!
Q:i would say you save all your stuff and do a nandroid backup.
than you follow this instructions to flash the rooted stock 2.2 rom and the radio
A:My current ROM is the standard one after downgrading HBOOT & using Unrevoked, but I used the phone's update feature to update everything to 2.2, then I rooted it and all works fine, BUT, if I add any modifications, like circle battery it is too much for the phone & gets too hot & power cycles, it gets to the boot anim then automatically reboots again, it can do this for about half hour before it works again, but I mostly just pull the battery & put something cold on the affected area! Yesterday I put my fone in the freezer for 10 mins, but using even the most basic customisation was getting hot again so I reverted back.
Q:if the problem is still there i would say its a hardware problem, if not you can try other roms as long as no problems occure
I have tried a number of other ROM's, but I think I will just stick with what I know works for now!
Q:dont play around with kernels, you dont have to, the stable kernels are in the roms if they arent stable for you its not the kernels fault
A: thanks for that, think I'll leave them alone for now lol!
Q: i guess something messed up while you flashed something...
A: Nothing went wrong with the flashing, as Ive done it so much in the past year or so I know what its sucessfull or not!
Q: ps.: if you have absolutly no linux skills and so on, i would say you read into that before playing around with your mobile ^^
A:Thanks!
I really dont know what the cowboys done with my fone, but they have totally screwed it up, the microphone dont work and I have to almost eat the damn thing n shout, even then sometimes nobody can hear me! The WiFi signal is horrendous since it came back, can only get a full signal if I sit on top of the router, so using the WiFI out of the room is now out of the question! I also noticed they had cut off or pulled off something that I am convinced is the WiFi aerial, it sits just under the flash, a black tab it looks like, they insist they didnt do it, I KNOW otherwise!
When I first saw the phone, the back cover wouldnt fit on & it looked like they hadnt installed everything right, so they had it back as also the in-call speaker didnt work either, there are still outstanding problems, but as I have left it so long (main shop in Glasgow, me in Paisley with no way of getting there myself) I doubt they will do anything about it, i am SOO angry there isnt a swear word I dont shout every time the bloody fone hets hot & power cycles!
Again thanks for all your replies & sorry for the essay lol!
Arty.
hi, ok it really sounds like they have messed up your little desire!
first of all i want to apologize i thought you dont have a clue about anything ^^
so i would suggest you try to flash a new radio maybe the 32.56.00.32U_5.17.05.23 helps, if you have it on your mobile reflash it just to be sure(if you have a different hboot, you have to do it with fastboot)
if this didnt help, i would say you try to flash the RUU
and when that fails i would start yelling at the customer support
wish you the best
ps.: i just started thinking if it is maybe the battery, change it with a/the other one
Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )