I have been troubleshooting this issue for some time now and have narrowed down to 'my HD2 unit' which has an issue only on 2.10+ base roms. Apparently this does not affect most users and appreciate any ideas for resolution.
When using 2.10+ base roms:
Receiving calls, the screen blanks off which is ok for calls but when I try to access the phone during the call, no buttons can light the phone except the end call which of course ends the call.
When any other buttons pressed, the button light just turns on for a split second and turns off, nothing else. Volume buttons seemed to work as volume can be changed but screen just remains blank. After the call is complete, the screen turns back on automatically.
Strangely out going calls are fine and do not exhibit this symptom.
What I have tried and does not help:
Different radios (both 576mb & non 576mb versions)
Different HSPL (1.42, 1.66, 2.08)
MTTY, fresh rom install, hard reset everytime and test immediately before any application install
One more note is that my unit was one of the early batches which I ordered from expansys.co.uk but should be from HK.
Thanks in advance...
Are you enabling Tap Time or Screen Sensitivity using BsB Tweaks? If so switch them off and see if that resolves the problem.
ClydeB1 said:
Are you enabling Tap Time or Screen Sensitivity using BsB Tweaks? If so switch them off and see if that resolves the problem.
Click to expand...
Click to collapse
Nope. I have been using Topix all the while and tested each rom from a fresh install, no additional apps.
Currently I have downgraded to Topix 1.6 (1.72 base rom) and the issue was resolved
coatercup said:
Nope. I have been using Topix all the while and tested each rom from a fresh install, no additional apps.
Currently I have downgraded to Topix 1.6 (1.72 base rom) and the issue was resolved
Click to expand...
Click to collapse
so you've not tried other 2.10 based roms, just the topix?
maybe try another rom based on 210 to see if you get the same effect?
fards said:
so you've not tried other 2.10 based roms, just the topix?
maybe try another rom based on 210 to see if you get the same effect?
Click to expand...
Click to collapse
Yes, I did try. in fact originally I thought the 2.10 rom by zenkinz had problems so I switched back to Topix then 1.6+ roms. now I know it is due to 2.10 rom compatibility...
coatercup said:
Yes, I did try. in fact originally I thought the 2.10 rom by zenkinz had problems so I switched back to Topix then 1.6+ roms. now I know it is due to 2.10 rom compatibility...
Click to expand...
Click to collapse
Strange thing is I never heard that before. You say more users experience these problems but at least it was never mentioned in the topix thread nor did I read about it in other threads. Did you ever flash back to stock and perform a task29?
You can check 2 things.
1- Older radios caused problems when 3g mode was set to auto. 2.10 radios don't have this problem.
2- Could be a problem with the proximity sensor hardware or settings. Try to test the proximity sensor by some other means.
kwbr said:
Strange thing is I never heard that before. You say more users experience these problems but at least it was never mentioned in the topix thread nor did I read about it in other threads. Did you ever flash back to stock and perform a task29?
Click to expand...
Click to collapse
Probably a good idea to try. I will try and feedback once I download the stock...
Well the stock flash did not work.
Tried to flash back to stock, hard reset
Re-HSPL, mtty, Topix 1.6.4, hard reset
Problem still exists, running out of ideas now...
I had the same problem...-My- solution was...
...turning off the -Face mobile down to stop ringing- feature...
FW-ROM v1.66 -hTC-
I Had exactly the same problems with miris 2.10 based roms. After some requests he built a 1.72 based rom. After flashing radio 2.10.50.19_2 a task 29, Installing HSPL 1.66 and flashing miris 1.72 rom the problem was gone. i also noticed a big improvement in in call audio quality and data connection stability. I am using his new v15.1 rom with the 1.77 base and it is great His roms are available at htcpedia.
Hope it helps
Related
I upgrade the ROM fairly frequently on my Blackstone, usually with the latest Dutty release. This was fine up til yesterday. I installed Dutty's Holy Grail R0 ROM, and after installation, after about an hour, the device completely locked up. I pressed the reset button, and the device Hard-resetted, removing everything and going back through the setup screens. This happened a couple of times, so last night I put on a different ROM, Dutty's WM6.5 R15. The device locked up after about an hour, and wouldn't get past the "smart mobility" screen when restarted. This morning I loaded the stock (Orange UK) ROM back onto the device. I haven't had the chance to check if this problem will re-occur, but when I turn on the phone the colours are flipped (putting it to sleep and turning it on again fix this problem, but on a soft-reset it happens again). Seems I can't get anything right at the moment, can anyone suggest what might be up? Tech specs below:
UK Touch HD on Orange
USPL - used exactly as per the Dummies Guide.
Using Win7 x64 (yes, I've got the drivers installed correctly for USPL)
ROMs mentioned in post:
Dutty's Holy Grail R0
Dutty's W6.5 R15
I suppose you didn't install the stock ROM prior to installing the Dutty ROM. You MUST flash a stock ROM before you flash a home cooked ROM, since they work a bit differently when it comes to erasing data. USPL doesn't seem to be the best way either. I had similar problems like you when I used USPL.
So try the following:
Flash your SPL to OliNex
Flash your device with a stock ROM
Use HSPL to flash the Dutty ROM of choice
Ogredani said:
I suppose you didn't install the stock ROM prior to installing the Dutty ROM. You MUST flash a stock ROM before you flash a home cooked ROM, since they work a bit differently when it comes to erasing data. USPL doesn't seem to be the best way either. I had similar problems like you when I used USPL.
So try the following:
Flash your SPL to OliNex
Flash your device with a stock ROM
Use HSPL to flash the Dutty ROM of choice
Click to expand...
Click to collapse
not sure where you got your info, but, you DO NOT have to flash a stock ROM before flashing a cooked ROM. if you're having issues, they could be solved by flashing a STOCK rom. i'm sure i've flashed my HD over 60+ times and never flashed a stock ROM before doing so. i have not had any issues at all. in the original poster's case, it could be that the STOCK ROM he flashed requires an older SPL.
not sure where you got your info, but, you DO NOT have to flash a stock ROM before flashing a cooked ROM. if you're having issues, they could be solved by flashing a STOCK rom. i'm sure i've flashed my HD over 60+ times and never flashed a stock ROM before doing so. i have not had any issues at all. in the original poster's case, it could be that the STOCK ROM he flashed requires an older SPL.
Click to expand...
Click to collapse
Could it be the SPL? Does USPL work with every ROM? The confusing thing is having flashed a stock ROM (the Orange UK ROM), while the device seems fine (apart from having to use 6.1!) it does suffer from the bizarre colour problem while starting up. If I were to flash the SPL to HardSPL, would I be able to undo this? I don't really want to get the phone to a state where I can't return it to the stock ROM/SPL if I need to return it.
cortez.i said:
not sure where you got your info, but, you DO NOT have to flash a stock ROM before flashing a cooked ROM. if you're having issues, they could be solved by flashing a STOCK rom. i'm sure i've flashed my HD over 60+ times and never flashed a stock ROM before doing so. i have not had any issues at all. in the original poster's case, it could be that the STOCK ROM he flashed requires an older SPL.
Click to expand...
Click to collapse
lol i was gunna say exactly the same thing
fredley said:
Could it be the SPL? Does USPL work with every ROM? The confusing thing is having flashed a stock ROM (the Orange UK ROM), while the device seems fine (apart from having to use 6.1!) it does suffer from the bizarre colour problem while starting up. If I were to flash the SPL to HardSPL, would I be able to undo this? I don't really want to get the phone to a state where I can't return it to the stock ROM/SPL if I need to return it.
Click to expand...
Click to collapse
maybe you should try hspl rather than uspl, its a lot easer and more convient, and its eaaasy to go bk to your original spl if you need to
cortez.i said:
not sure where you got your info, but, you DO NOT have to flash a stock ROM before flashing a cooked ROM. if you're having issues, they could be solved by flashing a STOCK rom. i'm sure i've flashed my HD over 60+ times and never flashed a stock ROM before doing so. i have not had any issues at all. in the original poster's case, it could be that the STOCK ROM he flashed requires an older SPL.
Click to expand...
Click to collapse
Just sharing the experience from myself and several users at HTCpedia where flashing a stock ROM first is the general recommendation. You might have made it just fine with your HD without a "stock flash", but you may have different set-up of your phone (SPL, ROMs) than others. That's why I say play it safe and install the (latest) stock ROM and HSPL-OliNex. Seems to work for more or less everyone.
However, I agree that there is no definitive explanation to why you should flash the stock ROM, but it seems as if the flashing procedure of a stock ROM resets the memory completely, where a cooked ROM flash does not. Note that this well may be an issue with the wrapper and not the ROM, but that's another story.
Ogredani said:
Just sharing the experience from myself and several users at HTCpedia where flashing a stock ROM first is the general recommendation. You might have made it just fine with your HD without a "stock flash", but you may have different set-up of your phone (SPL, ROMs) than others. That's why I say play it safe and install the (latest) stock ROM and HSPL-OliNex. Seems to work for more or less everyone.
However, I agree that there is no definitive explanation to why you should flash the stock ROM, but it seems as if the flashing procedure of a stock ROM resets the memory completely, where a cooked ROM flash does not. Note that this well may be an issue with the wrapper and not the ROM, but that's another story.
Click to expand...
Click to collapse
The best thing to do is use mtty to completely format your device and totaly remove the current os and any defragmented parts of older roms left in the memory blocks before flashing a new rom
Ogredani said:
Just sharing the experience from myself and several users at HTCpedia where flashing a stock ROM first is the general recommendation. You might have made it just fine with your HD without a "stock flash", but you may have different set-up of your phone (SPL, ROMs) than others. That's why I say play it safe and install the (latest) stock ROM and HSPL-OliNex. Seems to work for more or less everyone.
However, I agree that there is no definitive explanation to why you should flash the stock ROM, but it seems as if the flashing procedure of a stock ROM resets the memory completely, where a cooked ROM flash does not. Note that this well may be an issue with the wrapper and not the ROM, but that's another story.
Click to expand...
Click to collapse
Think someone in HTCPedia was playing if safe by suggesting users flash stock rom before flashing cooked rom. Like cortez.i said above you DO NOT need to flash a stock ROM before flashing a cooked ROM. Some poeple occasionally experience issues with cooked roms and a solution can be to flash a stock rom. But like cortez.i I've flashed well over 200+ times and never flashed a stock ROM before doing so and I've never had an issue. It may be inexperienced users are doing something different which causes these issues or haven't followed the flashing process properly.
Yesterday I've HSPL'd my leo.
Then I flashed the Dutty0.3v and thought everything was fine. Until this morning the device was unlocked with S2U2 and hung afterwards (not able to show manila page). After a softreset, device hung at white bootscreen (three red version lines bottom). Several softreset later, it actually lost all its settings, windows welcome center was welcoming me. So it did a hardreset.
Then I flashed another rom, the freyberryROM.V5.3. After flashing, I always hardreset the phone of course.
After two hours configuring and installing, all of a sudden some application weren't starting anymore, so I thought let's do a softreset, to see, if it fixes things. The same happened, device hung a bootscreen. After softreset, a hardreset occured again....
First I wanted to put the blame on the HSPL, but I think it was coincidence. But thinking over and over about my procedure and reading the dutty rom's thread, I think this has to do with S2U2. Maybe some of you experienced this as well, and we can put together what might be the culprit.
Details:
Using S2U2 v2.24 (video rawbuffer mode) - imported settings from reg-file.
Using T2Pro-Theme on SD-Card
Manila and every other HTC/WM setting concerning language set to German.
Hooked on Exchange2010 - Pushmail activated.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
ROM
I have had the same too with my former Blackstone, as I flashed it with T2M PDViet, I thought it is a virus, however I solved it by downloading a new version and installed it all over again, good luck
Donald24 said:
Yesterday I've HSPL'd my leo.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
We had to do this on all the WM6.5 cooked roms for Kaiser, not heard of it being required for HD2 yet, why not post this in the thread for the ROM you are using?
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
tomasz said:
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
Click to expand...
Click to collapse
I've had this on my TytnII as well, but I never heard it for the HD2. So Custom to Custom ROM flashing is a NO GO?
?? Is there any other SPL? SSPL and HSPL are both 1.42 based....
In the diamond and other devices like tynt you could fix this with MTTY but dont know if it will work with the hd2
I thought MTTY was for recovering a device after a bad/interrupted flash??
Can you really use it to fix the non-boot situation and recover your installation?
So, when talking about stock-rom flashing is SoftSPL-flashing enough, or is a full HSPL- or even CID-ID-corresponding flash (incl. radio-rom) necessary?
Can somebody shed some technical background around this issue? I don't understand that there are mysterious areas, which don't get flashed and updated when flashing from custom to custom rom. There is no logic that this works for ONE flash ONLY.
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
xvx45 said:
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
Click to expand...
Click to collapse
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Donald24 said:
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Click to expand...
Click to collapse
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
crazyman1 said:
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Click to expand...
Click to collapse
It's not the flashing, me thinks. I experienced the issues only after flashing from custom TO custom rom. So I just think, it's like to old KAISER's times:
Always flash stock rom before!
Has anyone else noticed this?
I've never flashed a stock rom between custom roms and never had any lock up problems. I always use sspl or customRUU. Just thinking it might be the way you're flashing as I'm sure I read somewhere on the forum that there were problems with flashing from the MicroSD card.
xvx45 said:
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
Click to expand...
Click to collapse
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Donald24 said:
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Click to expand...
Click to collapse
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
makeveral said:
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
Click to expand...
Click to collapse
hey - we're getting closer. thinking about a sub-forum about flashing techniques, they will surely get device-dependant at some point.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that fear...
nobody on xda normally shows this respect for trying out undocumented functions
Donald24 said:
hey - we're getting closer.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that respect
nobody on xda normally shows this respect for trying out undocumented functions
Click to expand...
Click to collapse
ya some people have bricked his device because of this... but well it can usually get fixed! problem was that they used mtty without having a hardspl and then they couldnt flash any rom... but if you have hardspl then no problem because you can flash from bootloader!
And if you dont have hardspl then you should also be able to flash HTc official rom(or the official rom that came with your device)
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
makeveral said:
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
Click to expand...
Click to collapse
Why hesitating? I'd love to see a "call task 29" as a menu item in your BSB tool I woke up this morning, and I felt for yelling "Task 29" to my girlfriend. No, to be honest, I didn't, I said "69" and enjoyed the morning.
I am going to try this method out and report back, but as it seems, it will be seen as a hack, that doesn't fit for everybody. But I would prefer this against always preloading a stock rom, if it would do the job.
Thanks for putting light on this!
Donald24 said:
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
Hi,
this is correct, you can stop this happening by flashing a OFFICIAL rom before your cooked rom.
Although i have just posted a thread on MTTY, which is the EXACT answer to all problems in this thread.
THREAD HERE - (It is Under Construction so please dont use until the big red warning has gone, you cant miss it!!)
MG
I was having the same exact problems with softspl and hardspl and with any custom rom. My cousin has the same issues too. I flashed back to stock 1.61 and dont have hardresets anymore.
I'm so tired of this phone right now but since my company only offers HTC phones with WinMo this is the only one that's "interesting".
It has actually worked kinda well the last month but after I changed ROM last Friday it has been totally unusable. After the ROM-change I couldn't hear anything when I made a call so I changed radio, problem solved... I thought.. The phone freezed after one hour so I had to take the battery out and when I tried to boot it again it took the phone 6-7 minutes to get past the screen with Rom and Radio information. When it got past it I got the first booting screen with the "Windows is setting up your phone" blahblah so it was like I have made a hard reset.
Ever since I have tried different ROMs and different radios but nothing helps, it keeps giving me these crazy problems. On some ROMs I'm unable to save and access my contacts etc. One thing that is persistent is the time to get pass the screen with ROM and radio information, it's really slow no matter which ROM or radio I'm on. Of course I haven't tried all ROMs and radios but around 4 ROMs and 3 radios.
Is there anything else then ROM and radio that can be updated or replaced because I'm on the edge here and I'm about to throw it in front of a car just to get rid of it.
I appreciate all the help I can get.
Hi, try out OzROM and Radio 2.08_2. This combination is very fast, stable and usefull. I have testet a very lot other Roms but OzROM is the best off all !
Never hang since 1.30, good phonequality and no big Problems.
And remember to make a hardreset after flashing !!!
HQ_seppel said:
Hi, try out OzROM and Radio 2.08_2. This combination is very fast, stable and usefull. I have testet a very lot other Roms but OzROM is the best off all !
Never hang since 1.30, good phonequality and no big Problems.
And remember to make a hardreset after flashing !!!
Click to expand...
Click to collapse
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Click to expand...
Click to collapse
How many ROM's have you flashed since you got your HD2? were they from the same Cook?
I always Flash a Stock ROM (via USB of course so I don't lose HSPL) before flashing to a new ROM by a different Cook... (so If I was on LIA, before flashing Dutty's I flash the Stock ROM, before flashing Artemis, Flash the stock ROM, before flashing Miri... and so on...)
If I want to get a truly clean device, I do a task 29 via mtty, which is akin to formatting your PC before you install a new OS.
Try mtty, its fast, easy and the results are proven (head over to the stickied mtty thread on HD2 ROM Development)
mtty
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
Click to expand...
Click to collapse
might be time to mtty mate while you still can becarefull downgrading the 2.0.8 roms some people are having problems read the site about those
DJGurth said:
might be time to mtty mate while you still can becarefull downgrading the 2.0.8 roms some people are having problems read the site about those
Click to expand...
Click to collapse
one of the reasons I have never flashed a custom ROM...the stock rom may have bugs but I have found that custom ROMS have so many more!!
I've yet to find a stable one, so now I don't bother with them...pity as they do have some nice features, but I can't live with the drawbacks
If its a company phone and, I assume, you use it for business purposes in the main and it was working ok, why did you upgrade the rom with the risk that you might break something?
How much reading have you done on here? Have you looked at the Hints & Tips thread fpr fixes or the "HD2 died- or did it" thread that deals specifically with the lockup issue?
If you are a secret rom junkie, flashing roms every 5 minutes, are you aware of the issues with doing so and the need for MTTY?
I tend to be very helpful to people in trouble; however I am struggling to understand why you fiddled around with a business phone that appears to be critical to you and was, as I understand it, working perfectly beforehand?
WB
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
Click to expand...
Click to collapse
Jes thats it, you can download it on the OzRom Site
If you get Duttys HG ROM from my sig radio 2.08 is included so no extra flashing needed
In addition to the other recommendations in this thread (mtty/stock rom, etc.), I would recommend you stick to the 6.5 series (21xxx) rather than 6.5.x (23xxx) for added stability and speed.
wacky.banana said:
If its a company phone and, I assume, you use it for business purposes in the main and it was working ok, why did you upgrade the rom with the risk that you might break something?
How much reading have you done on here? Have you looked at the Hints & Tips thread fpr fixes or the "HD2 died- or did it" thread that deals specifically with the lockup issue?
If you are a secret rom junkie, flashing roms every 5 minutes, are you aware of the issues with doing so and the need for MTTY?
I tend to be very helpful to people in trouble; however I am struggling to understand why you fiddled around with a business phone that appears to be critical to you and was, as I understand it, working perfectly beforehand?
WB
Click to expand...
Click to collapse
Yes its a company phone and yes it worked "ok" after trying different custom ROMs. But I think that a phone in this price class should be working perfectly and not just ok. That's why I tend to flash a new ROM once in a while, because I want perfection. And we all know that HTC won't give us that.
Even though the last working ROM was ok, there still were some issues that didn't affect my daily use but that bugged me a bit, that's why I wanted to try a newer ROM.
I don't know that much about MTTY but I will look into it now. Thanks for the heads up.
no device will give you perfection - it's impossible as everyone has different perceptions of perfection
EddyOS said:
no device will give you perfection - it's impossible as everyone has different perceptions of perfection
Click to expand...
Click to collapse
True, but all programs and features that's implemented in the phone should work as designed. If they don't, the device isn't perfect imo.
Do you know how many issues Apple fix with the iPhone each week? All phones have issues, all PCs have issues, anything to do with tech has issues!!
End of the day you either try and fix it, send it back or wait for HTC to fix it (although some issues may be down to M$ themselves)...
LeoLite 2.3 with radio 2.08.50.08_2 is sweet!
The ROMeOS ROM is great as well - head to romeos.monx.biz for that one...
MTTY
I'd reiterate the advice about the MTTY, my device was utterly corrupted and flashing didn't help. After a MTTY format its back to 100%. Choose your ROM's carefully though, i still had some stability issues with some of the more exotic ROM's (even after a MTTY), I ended up choosing something closer to stock (Dutty) which was rock solid.
Ok, I did use the search feature and I did find information but I just want to verify that it is correct. From what I seen to update from a Custom ROM with HSPL to the Official 2.13 Update you have to do the following:
1. Flash the 2.13 Update
2. Run HSPL again but this time select (in my case) 2.08.00 instead of 2.08.00 HSPL which should flash the stock SPL onto the phone.
Is this correct? Just want to verify as I dont want to brick my HD2.
Thanks,
Mike
correct
.......
Thanks for verifying that.
if thatsvthe update from tmobile i advise against it. it messed with my sensitivity and took me a few days of work to go back to the 2.10 ROM version
Let me ask you this though, did you do a hard reset before flashing the update, as well as after flashing the update? If you did this it shouldn't have any bad effects on it. Ive heard no others say they have had this issue. Ill let you know if I have this kind of issue though. What exactly was it doing?
ssconceptz said:
Let me ask you this though, did you do a hard reset before flashing the update, as well as after flashing the update? If you did this it shouldn't have any bad effects on it. Ive heard no others say they have had this issue. Ill let you know if I have this kind of issue though. What exactly was it doing?
Click to expand...
Click to collapse
That is most definitely a wise practice when flashing ROM's...however, there are indeed quite a few users reporting sensitivity issues after flashing to the new 2.13...there's changes in the new ROM intended to improve sensitivity, but the effects aren't always desirable it seems.
Some serious efforts are underway here to get around that, you can keep up with them at the following thread (which is also a sticky at the top of this forum section):
http://forum.xda-developers.com/showthread.php?t=683192
Or......
1. Use an extrator program on the .exe file and then you will find that the 2.13 update has 11 files. (rename the .exe to .rar)
2. Run a Task29
3. After the 11 files are extracted you can just use the romupdate utility, and presto stock 2.13 without messing with HSPL
These steps will not overwrite the HSPL to 2.10 and if you decide to go to another custom ROM then you are good to go.
It also works the same with the 2.10 stock ROM
I had a custom went to the new tmous official and went back to a custom without having to redo Hspl.
well I just heard that the HSPL gives problems with 2.13 and you need to use the factory SPL
uhmm.... i'm using smaberg's touch extreme rom.... which is better? the tmo 2.13 update or the custom rom?
May I ask why would you consider returning to 2.13 after running a perfectly fine Custom ROM? Well, besides selling or trying to return the phone to T-Mobile... 2.13 gave me nothing but problems and freezing left and right. The music app in 2.13 took 1 minute and 25 seconds to load the songs !!!!
2.13 is the latest right? even the new custom roms are 2.13 based right? or that's old?
matyoka said:
May I ask why would you consider returning to 2.13 after running a perfectly fine Custom ROM? Well, besides selling or trying to return the phone to T-Mobile... 2.13 gave me nothing but problems and freezing left and right. The music app in 2.13 took 1 minute and 25 seconds to load the songs !!!!
Click to expand...
Click to collapse
Something is definitely wrong with your HD2. I have the latest rom and it's just as stable as the previous versions. Using Garmin Mobile XT GPS and SportyPal along with G-Alarm very frequently with no hiccups.
You sir suck at HD2.
Appreciate your response, even though it had nothing to do with you. On a second note, I'd rather suck at HD2 than suck something else... something you are very familiar with.
Hi everyone,
I need help with android on my HD2. I put on my HD2 the Android 2.2 OS but there is no sounds and calls have robot like sounds (can't even make out words that are spoken). I have been having the same problem no matter what I do and how many times I redo the installation process. I even installed HSPL3 and went from a 2.10 radio to a 2.08 radio still the problem persist. And yes i did tap on CLRCAD before taping on HaRET. Someone please help...
The Robot Voice is a known issue. However, some cooks have fixed the issue in their custom ROM's. Why don't you check them out.
http://forum.xda-developers.com/forumdisplay.php?f=624
gaarry said:
The Robot Voice is a known issue. However, some cooks have fixed the issue in their custom ROM's. Why don't you check them out.
http://forum.xda-developers.com/forumdisplay.php?f=624
Click to expand...
Click to collapse
x2.
certain rom+radio combinations are better than others in terms voice call quality. e.g., chucky rom+latest radio works good with mattc's froyo sense, miri's rom seems to work well with darkstone's builds, etc..
I went through most of the threads of there but in vain
ryan562 said:
x2.
certain rom+radio combinations are better than others in terms voice call quality. e.g., chucky rom+latest radio works good with mattc's froyo sense, miri's rom seems to work well with darkstone's builds, etc..
Click to expand...
Click to collapse
well that's what i though therefore tried to use darkstone's builds with miri's rom but to no vails
Daftdog2002 said:
well that's what i though therefore tried to use darkstone's builds with miri's rom but to no vails
Click to expand...
Click to collapse
You just have to experiment, or look around in user's signatures, and see what build combo's they are using.
i've tried this so many times to no avail, the sound is very low plus i get tke robot voice and after the second call it does not sound anymore. Also there are no ring tones, everything works but the audio. This is what I'm running:
Froyo Stone with sense, my radio is 2.10.50.26 everything is in the SD card, also how can I access the sd card? Thank you so much for any help you cab give me.
well ill give you my tip on how to resolve your problems. i did this to my phone and now i can run android FLAWLESSLY on my HD2.
1.go to tmobiles site and download the latest STOCK rom for your HD2.
2. run the program to install it so that you have the newest stock rom on your phone.
3. install HSPL 2.08 and MAKE SURE its HSPL and not SPL.
4.after installing that, install a custom WM rom of your choice(im using the WM bare bones by NRGZ28)
5.then install a new RADIO rom( i am using the Leo_RADIO_2.12.50.02_2)
6.download and install the ANDROID ROM of your choice(i am using MATTC's NeXus one 2.2 OTA operating system)
7. reboot after you finish installing the android and it should work great! i havent had any robot voices/SoD or screen freezes and i have been using it for 4 days now and i usually get about 12-14 hours of use out of a full charge.
let me know how that works!
This has been talked about MANY times already. Android on the HD 2 is kinda like a learning a new recipe, you have to try different things till you find something that works for you. Did you know there is a whole forum dedicated to android on the HD 2? Really there is It is HERE
It does not work with all ROMS. You have to find a ROM that is compatible with Android. Omega's latest ROM is compatible.
Hey man you are a life saver. Tried what you did and my HD2 is working. The only thing I have found is when I hook up my bluetooth headset it somehow corrupts everything and i have to reinstall the rom to get everthing else working. Thanks again
kyleshaffer21 said:
well ill give you my tip on how to resolve your problems. i did this to my phone and now i can run android FLAWLESSLY on my HD2.
1.go to tmobiles site and download the latest STOCK rom for your HD2.
2. run the program to install it so that you have the newest stock rom on your phone.
3. install HSPL 2.08 and MAKE SURE its HSPL and not SPL.
4.after installing that, install a custom WM rom of your choice(im using the WM bare bones by NRGZ28)
5.then install a new RADIO rom( i am using the Leo_RADIO_2.12.50.02_2)
6.download and install the ANDROID ROM of your choice(i am using MATTC's NeXus one 2.2 OTA operating system)
7. reboot after you finish installing the android and it should work great! i havent had any robot voices/SoD or screen freezes and i have been using it for 4 days now and i usually get about 12-14 hours of use out of a full charge.
let me know how that works!
Click to expand...
Click to collapse
+1
Few differences.
I have chuckyrom light and froyostone (8/7/2010) build.
Its a t-mobile phone.
When I had the 2.10 radio, the build froze constantly. I couldn't use it. As soon as I changed to the 2.12 radio mentioned above, I haven't had a problem since.
I'm going on nearly 2 weeks and it has performed flawlessly.
Sent from my HTC Desire using XDA App
same here
I have same issue with robot woice, just like from videoclip Black Eyed Peas
I think the combination one month old Duttys ROM and Foryostone2.2 Android image is the reason. Radio ROM is the latest. Therefore I think every chefs WM ROMs has to be modified to be compatible with currend Android port developement.
Also I have very fast music player, everything sounds like Smurfs and battery drain is very extrem.
But battery drain is common for every Android ports, as I can see at forum, so until this issue will be resloved it is just for fun not for the real usage I hope developers who spend a lot of time with porting will have luck with that soon