Hi,
I have the dutty rom 2.9 on my touch hd. Everytime I recieve a call the phone will only ring once and then switch to a voice announcement of the caller's ID or number. Does anyone know how to turn this off and stick with normal standard continous ring alert? I have searched everywhere in settings, there is nothing obvious that stands out.
Also what is the difference between Dutty's MSVC and CVSD? Which should i be updating with?
Thanks
Have you got Microsoft voice command? The setting for it is in settings\personal.
HAHA, Yes. Sorted now. Thanks.
Can anyone help with the Dutty Rom question?
Is it really worth me upgrading from 2.9 to 3.2? It seems to freeze everytime I try through Active Synch, any ideas why?
tahirh said:
HAHA, Yes. Sorted now. Thanks.
Can anyone help with the Dutty Rom question?
Is it really worth me upgrading from 2.9 to 3.2? It seems to freeze everytime I try through Active Synch, any ideas why?
Click to expand...
Click to collapse
You should really be asking these questions in Duttys threads. The reason why your phone freezes during upgrade to V3.2 is most likely because you haven't used USPL again before you flash. All Duttys latest roms based on 1.56+ roms you'll need to use USPL before every flash as USPL is only temporary. Alternatively use HSPL so you don't need to continually have to use USPL, though HSPL is permanent
Links to latest HSPL and also guide on flashing to 1.56 based roms can be found in my signature
Hello
Sorry for that Asking Stupid Questions again. (my English isn't very good too)
I have Read many Posts for some Hours so i could Help myself Solving the Problem
How to Hard SPL
Flashing Roms via HardSPL
Flashing Roms via MicroSD Card
other Threads with possibly same Problems
...
Now i think that i have Forgot or Missed Something quit Important.
Either i Forgot something or probably didn't Understand the Guides and HowTo's....
About My Problem:
Ok i have an German O2 XDA Orbit 2 (HTC Touch Cruise or HTC Polaris)
December last Year i easily Flashed my Device with the "M-Amine 2.0 Final GER" Rom.
My Device worked after Flashing via HardSPL Perfectly.
Now i wanted to Flash the "Kostas244-Rom-WWE-WM6.5 Because i wanted to try the new WM6.5 on my Device.
But i simply cant Flash my Device, no matter waht Rom i try.
The Officially O2 Germay, the Flashed M-AMine 2.0 Final or any other Rom.
I can verify that i have the Required HardSPL, done all this by Flashing "M-Amine 2.0 Final".
But every Time i try to Flash via HardSPL i get these dammit "Error 260 Message".
Now Matter what Rom Upgrading or Downgrading...
Even the Flashing via MicroSD Card wont Work.
Please is there Somebody willing to take the Time and Help an Newbie Like me?
Thanks for Helping
Starsheriff
Starsheriff said:
Hello
Sorry for that Asking Stupid Questions again. (my English isn't very good too)
I have Read many Posts for some Hours so i could Help myself Solving the Problem
How to Hard SPL
Flashing Roms via HardSPL
Flashing Roms via MicroSD Card
other Threads with possibly same Problems
...
Now i think that i have Forgot or Missed Something quit Important.
Either i Forgot something or probably didn't Understand the Guides and HowTo's....
About My Problem:
Ok i have an German O2 XDA Orbit 2 (HTC Touch Cruise or HTC Polaris)
December last Year i easily Flashed my Device with the "M-Amine 2.0 Final GER" Rom.
My Device worked after Flashing via HardSPL Perfectly.
Now i wanted to Flash the "3LIT3_VIII_Full_GER" Because i wanted to try the new WM6.5 on my Device.
But i simply cant Flash my Device, no matter waht Rom i try.
The Officially O2 Germay, the Flashed M-AMine 2.0 Final or any other Rom.
I can verify that i have the Required HardSPL, done all this by Flashing "M-Amine 2.0 Final".
But every Time i try to Flash via HardSPL i get these dammit "Error 260 Message".
Now Matter what Rom Upgrading or Downgrading...
Even the Flashing via MicroSD Card wont Work.
Please is there Somebody willing to take the Time and Help an Newbie Like me?
Thanks for Helping
Starsheriff
Click to expand...
Click to collapse
The only thing I can suggest is to check your radio version... if it's 1.65.XX.XX then that could possibly explain the issue. You'll need to downgrade the radio before doing anything else. Here is the link (from Pcar's ROM thread) which contains a radio that can be flashed over 1.65.XX.XX.
http://rapidshare.com/files/285239274/Polaris_Radio_ROM_1.59.46.12.rar
3LIT3_VIII_Full_GER....is wm6.1...
@Alexander
Ah yes sorry that was right. I meant "pcarvalho eXtreme ROM 3.19 WM6.5" Rom.
Also gave "Kostas244-Rom-WWE-WM6.5" Rom a try, same Problem.
@dlotters
Thx for the Tip...
Sorry it didn't Work, same Problem like all the other Roms, Radios,...
I simply can't Flash my Device, even after an Hardreset!
Everytime it goes in Bootloadermode it got Stuck and then the HardSPL aborts with same Error Message. (Error 260)
And i absolutly dont know what i'am Missing or forgot to do. There is only one Thing im sure about.
That the Problem is on my side, the Flashtools are fine.
Starsheriff
Hallo
So i took some Time But i Solved my Problem. "HAPPY"
Looks Like my SD-Micro Card did the Trick and a dozen of Hardresets...
Starsheriff
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.
Dear All,
i face the following issues.
1) if i use froyo stone clean build (Release date: 07.AUG.2010 GMT)
after i following all the instructions, i hang on the line "jumping to kernel"
>> a search on the forum, ask me to change ram addresses and cmd="ips****", but it doesnt help.
2) if i use the latest Parad0XUA_Experimental, it hangs on "init panel" then the screen fades to black.
I would be glad if someone could help me on this
Thank you
whizz
Sorry i cant help, but i have the exact same jumping to kernal problem and thats with any version of android ive tried. Ive got a box full of HD2's and no version of android will work on any of them. Do you need custom ROMS to run them?
Really hope someone can answer this, we cant be the only people to have this issue.
You certainly need to change the Radio to a .50, and it would appear that a custom ROM helps too.
http://forum.xda-developers.com/showthread.php?t=732380 - Already details all you need to know.
Thanks man! Installed HSPL3 and a different radio. Got it to boot now!
Awesome!!!!! Fantastic!!! thank U thank U
kerman19 said:
You certainly need to change the Radio to a .50, and it would appear that a custom ROM helps too.
http://forum.xda-developers.com/showthread.php?t=732380 - Already details all you need to know.
Click to expand...
Click to collapse
I have tried all radio version (2.08 ~ 2.12) none of them work for all fullram version ...
Changing the ROM did it for me. I was using a .51 ROM...replaced it with 2.15.50 ROM..Now, its fine and I must say Darkstone ROM is quite stable and performance is good too..I am using it on a 2GB card..( my 8GB went bad..Waiting for a replacement.. ) and it still gives me amazing speed.
I have resolved the problem using only the latest version of official rom by HTC without HSPL or anything else
Hi Guys,
Please help, i am having problem with the robot voice like most people here.
I don't know where i'm going wrong... i've read the forum and have tried what ppl have said, but i still can't fix my problem.
I have HardSPL'd my phone.
Have installed the custom ROM. (Tried Chucky ROM & currently on the Energy ROM)
Have tried all the radio's i believe.
Can someone plz tell me where im going wrong.
And also another Q. After loading the Radio, do i have to install the Custome ROM again? or installing the custome ROM is a one off thing??
Hope someone can help me.
Thanks in advance
Radio change
Have you tried radio 2.12 or 2.14? I stopped having the robot voice even with a 2.08 radio.
I can't post the link, but just do a search for HD2 2.14 and it should come up!
As for your second question: No, you do not need to flash the ROM again!
Hope this helps! Let me know how it goes.