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.
Related
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 have upgraded my orginal rom to offical roms such as 1.48 and the latest 1.61. I really want to try a cooked rom (which I did many a time on my Blackstone which I have sold), but other than wanting the Documents tab which I would find very useful for me.... well I just am not sure if flashing cooked roms are a good idea.
I say this because I flashed so many cooked roms on my Blackstone and even after hard resets, I had noticed a decrease in speed in overall performance. I think it was because I flashed it too many times. I wrote in the Blackstone forum if flashing too many times could do more harm than good.
I just read in the Leo Rom forums that when you flash roms of different sizes it can leave residule files behind in the rom which can make the phone unstable or sluggish.
I so want to try a new rom and every time I see an updated cooked rom in the rom thread I aways go to the last posts and still read of some problems some users have which puts me off.
I am not degrading the wonderful lengthy work these rom cookers do but I think I am happy enough with my phone with official roms. I just wish I could add in a documents tab without having to flash the entire rom.
Also why is it that the phone is super fast after a hard reset and as soon as you start installing stuff it becomes less so? Shame really. I am thinking one day to try the phone with no third party apps just to see if the speed stays the same. However, that is defeating the whole purpose of the phone about not installing apps.
Rant over
Well, I have a T-mobile-branded phone, and I have no intention of flashing a cooked ROM at least until after T-mobile releases a T-Mobile-compatible ROM upgrade. Until they do, I have no way of flashing back to a T-Mobile ROM and SPL, which means that flashing would irreversibly void my warranty; and with hardware as flaky as the HD2's clearly is, that's an unacceptable risk.
I'm not going to flash a new rom until I'm looking around for a new phone. Then I might try to dash in some new roms, but untill then I'm rolling stock all the way
Shasarak said:
Well, I have a T-mobile-branded phone, and I have no intention of flashing a cooked ROM at least until after T-mobile releases a T-Mobile-compatible ROM upgrade. Until they do, I have no way of flashing back to a T-Mobile ROM and SPL, which means that flashing would irreversibly void my warranty; and with hardware as flaky as the HD2's clearly is, that's an unacceptable risk.
Click to expand...
Click to collapse
do the T-mobile ROMs that are available to download from many locations here not flash back the SPL?
I downloaded my version of the t-mobile ROM so that I could go back if I encounter any hardware problems...
josep54 said:
do the T-mobile ROMs that are available to download from many locations here not flash back the SPL?
I downloaded my version of the t-mobile ROM so that I could go back if I encounter any hardware problems...
Click to expand...
Click to collapse
My phone is on vodafone but I got the phone from Phones4u does this mean it's branded to vodafone? Also if this is the case that it will void my warranty I have insurance. I f*ck the phone up then I loose it "unintentionally" . Then get a new one
Jammie_1989 said:
I have insurance. I f*ck the phone up then I loose it "unintentionally" . Then get a new one
Click to expand...
Click to collapse
Lol thas is so illegal, if they find out you do it you get in alot of **** xD , still I do think its a good idea
I looooove flashing new custom roms, Im addicted @[email protected] although lately Ive been sticking with dutty's latest, very fast and rather stable
[★] said:
Lol thas is so illegal, if they find out you do it you get in alot of **** xD , still I do think its a good idea
I looooove flashing new custom roms, Im addicted @[email protected] although lately Ive been sticking with dutty's latest, very fast and rather stable
Click to expand...
Click to collapse
lol I know but think is how are they ever going to find out as long as your not posting on forums saying 'I've done this' lol they will be none the wiser. Serves them right for offering insurance to people who are on the sh*test network going lol. Wish I could have got mine on a different network but apparently as it's from phones4u I already have the 1.48 rom and can upgrade straight from HTC woohooo
josep54 said:
do the T-mobile ROMs that are available to download from many locations here not flash back the SPL?
I downloaded my version of the t-mobile ROM so that I could go back if I encounter any hardware problems...
Click to expand...
Click to collapse
Flashing an official ROM through the PC won't overwrite the hspl, flashing an official ROM via sd card WILL overwrite the HSPL.
You should read the HSPL thread, it talks about uninstalling hspl half way down the first post.
tboy2000 said:
I say this because I flashed so many cooked roms on my Blackstone and even after hard resets, I had noticed a decrease in speed in overall performance. I think it was because I flashed it too many times. I wrote in the Blackstone forum if flashing too many times could do more harm than good.
Click to expand...
Click to collapse
This decrease in speed has to do with you installing apps and the registry gets filled up and through the installing and uninstalling of things, things slow down as the rom gets fragmented just look your computer. This is why overall performance decreases and not primarily because of flashing.
Another reason that the device can all of a sudden perform worse is also due to the different builds out there. They all have difference strengths and weakness. Some are more fast and some of them are more stable. The device itself does not mutate however I'm sure over 1000 flashes, there is a natural wear and tear. Most of us are no where near that.
Wait for your providers to provide stock upgrades so that reverting to stock is possible. I know quite a few members don't have any stock roms to fail back on. That would be the only reason not to flash a cooked rom.
Happy flashing people...!!
Lessons Learned in HD2 ROM Testing (Confessions of a Cooked ROM hopper) =)
Here's what happened:
I'd been through at least 20 "Flashes" of about 3-5 Cooked ROMs from the best chefs. I decided I wanted to reflash back to my stock ROM just to "refresh" (in lieu of mtty, of course which I still plan to do sometime). So off I went to download what I thought, at the time, was my stock ROM.
I thought I had a WWE Europe device (wrong for me to assume, I know) because I only had the UK Plug accessory included...
So I download the WWE Europe ROM and put it in my newly formatted 8gb microsd, renamed it to LEOIMG.nbh and started the upgrade process...
HOLY &*%$#@ it stops and tells me I have the wrong freaking device....
Then I thought that maybe, just maybe (since there was pinyin support from what I vaguely recalled) that it was in fact a WWE Asia ROM...
To cut the long story short, I flashed via microsd using the Asia WWE 1.48 (the CORRECT Stock ROM) and have started from scratch... (install HSPL, download Cooked ROMs, Flash, Test AND repeat from step 2... download, etc... you know the drill)
I'm only posting this in a new thread so that others who may run into what happened to me can find it and not panic that they can only get to a bootloader, etc...
I'm off to flashing some more Cooked ROMs... (BTW, I was a XDA2mini user way back, then shifted to an iPhone 2G and 3G for the past 2 years... and you know what, I missed the thrill of Windows Mobile Customization, I must say!)
Happy Flashing Everyone!
Well .... is that a "Confession of a Flasher-holic"?
LOL!!
This feeling is just like the feeling of those people that mod their PC .... mod their cars .... etc.
In life ... the kick or fun of it is the process ....
you were describing normal things which happen once you start modding or in this case flashing
htc12345 said:
you were describing normal things which happen once you start modding or in this case flashing
Click to expand...
Click to collapse
Exactly =) Now I need another HD2 for Flashing and Testing... back to work I go...
Hi,
i don't know wht happen. After I have flash cook rom, my screen look strange after i reboot it.
But it becomes normal after i press the power button and on it again.....
No peoblem in flashing stock rom......
IT's so strange........
(Flash ROM using USPL 2.5)
Are you sure your phone is an original HTC Touch HD device? There are lots of good copies of this phone in Asia which I have seen with similar problems when flashed with non stock roms.
stuntdouble said:
Are you sure your phone is an original HTC Touch HD device? There are lots of good copies of this phone in Asia which I have seen with similar problems when flashed with non stock roms.
Click to expand...
Click to collapse
Ha Ha Ha Ha Ha.......
I bought it from HTC and it is normal when i flash the stock rom
is it because i am using USPL???
FWIW mine did the same after flasing EnergyRom the other day. It's a T8285 that's Telstra branded. No problem once I turn the screen on and off but it was a bit unsettling.
You need to have your SPL (bootloader) to 1.56. Something in the initialization of the palette changed about a year ago in the various MS ROM updates.
I seem to recall the way to upgrade (for stock SPL, you can also go with custom HSPL) is by simply applying the most recent factory ROM update.
So, if you went from (old) stock ROM to a custom ROM, you would see this. If next you go from custom ROM to a new stock ROM and then back to the custom ROM, the problem is gone.
Or thats how I recall this, it has been a year since I had this problem.
If you already have newer SPL, then I do not know what the problem is.
You need to have your SPL (bootloader) to 1.56. Something in the initialization of the palette changed about a year ago in the various MS ROM updates.
I seem to recall the way to upgrade (for stock SPL, you can also go with custom HSPL) is by simply applying the most recent factory ROM update.
So, if you went from (old) stock ROM to a custom ROM, you would see this. If next you go from custom ROM to a new stock ROM and then back to the custom ROM, the problem is gone.
Or thats how I recall this, it has been a year since I had this problem.
If you already have newer SPL, then I do not know what the problem is.
Click to expand...
Click to collapse
thaank you!! You are right! it is normal now. thanks maybe this issue should post it in wiki.
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.