Database Users

T-Mobile HD2 with serious problems

Firstly sorry for the long post.
I'm having a few problems with my HD2, and I'm looking solutions that dont involve flashing the t-mobile ROM (which is 1.43.110.2). I have all the HTC patches installed.
The problems I'm having are ...
*Favourites are disappearing sporadically. I cant figure out whether they're going when I sync it up or just purely at random. They stay on the internet tab but disappear from the favourites menu. Folders are not affected.
*Music player: Lags. I have to wait about 2-3 minutes before a song starts playing on the first attempt, then its fine. This happens even if the little spinning circle hasn't appeared (this appears after you have updated the storage card by syncing with media player). Also when sliding album art back and forth in landscape mode, it freezes, and then jumps back to the beginning of the stack. Didn't used to do this.
*Music Sync - my biggest nightmare right now; I really need help on this one! Sync in windows 7 windows mobile device manager works fine. When I load up WM player and attempt to sync the storage card however, the device will sync for a couple of minutes, and then soft reset itself.
Hopefully when 6.5.3 comes out officially HTC will roll up all the crappy patches and T-mobile will approve it... but until then I'm stuck with these annoyances (in addition of course to crappy SMS, constant crashing, lags etc., which I certainly wasn't expecting when I got my shiny new HD2

I was in a similar boat to you. The Tmo ROM is really poor and I hate to tell you this but 1.48 or 1.61 are the answer.
If you really can't consider that option, I'd say that you should do a hard reset and see what issues you still have with a fresh ROM. The original T mo ROM is on here somewhere. download that as a backup before you do anything, just for safety.

realy sorry mate but he is right try and see if you can get hole of a free goldcard i run 1.48 insted of t-mob its not purfect but worls alot better

Thanks for your responses. I guess flashing is the only option, cos right now this phone really is virtually unusable. I'll have to try and get my head around the whole goldcards thing but if I get stuck I'll start a new thread...
Thx!

severeano said:
Thanks for your responses. I guess flashing is the only option, cos right now this phone really is virtually unusable. I'll have to try and get my head around the whole goldcards thing but if I get stuck I'll start a new thread...
Thx!
Click to expand...
Click to collapse
Hi mate, had the same issue. The gold card thing isn't too bad, theres a great idiots guide on here that I used, the hardest bit is getting the number off the MicroSD card, dont do what I did and lose all my data on it (as you edit some values which makes Windows no longer recognise it sometimes). Take a copy of whats on there just incase. Again there is a post that mentions a way of reversing the change so you have lost all your data on the memory card.
Good luck, I did without any probs to flash from 1.43 to 1.48 using the Goldcard method

I have the same problem with favourites and i'm on the 2.02 ROM. I never touch IE on my computer though so i've not put much thought into what happens with the sync. I'm just throwing together a wee app to sync it with Firefox though so that will solve my issues.
As for synching it with media player (and i'm old school - I drag and drop files), could there be any corrupt/unrecognisable data in your playlist? You could try a drag/drop dump of music onto your device and see if that works.

severeano said:
Thanks for your responses. I guess flashing is the only option, cos right now this phone really is virtually unusable. I'll have to try and get my head around the whole goldcards thing but if I get stuck I'll start a new thread...
Thx!
Click to expand...
Click to collapse
There is now HSPL and SSPL available so goldcard is no longer required, using SSPL or HSPL is much easier too

Hi, I converted my T-Mobile HD2 to 1.48 using SSPL. After a couple of teething troubles with Firewalls and a hanging Activsync - fixed with a PC restart it worked just great. It scared me twice when it hung in the boot loader but taking the battery out and restarting fixed it. I made a goldcard aswell just in case but do not really know if it would have worked.
Now its loaded The HD2 seems faster, has more programs and the battery seems to last longer particularly with WLAN.
I still have 1 open question though that I have, touch wood, not had to find the answer for yet. If I do a hard reset which ROM reboots, T-Mobile or the 1.48? Perhaps somebody here knows? I would be grateful to find out before I have to try it out.
Good luck and hopefully it works as well for you.
Bedwar22

i believe if you hard reboot it will revert to the Tmobile rom.. as you used SSPL... only if you do a HSPL will it stay... correct me if i'm wrong guys

nutmegy said:
i believe if you hard reboot it will revert to the Tmobile rom.. as you used SSPL... only if you do a HSPL will it stay... correct me if i'm wrong guys
Click to expand...
Click to collapse
Incorrect...your Rom does not change regardless of flashing method SSPL or HDSPL. If using the SSPL method a hard reset will remove the SSPL only, and your SPL ONLY will revert back to original, Your latest Rom does not change....

Thanks for the quick responses guys but I am still a bit confused - sorry.
Perhaps in laymans terms -
If I have to hard reset, when the phone reboots will I get all of the T-mobile c**p again and have to go through the SSPL process again- which is not easy when on a business trip, or will I keep the HTC version.
If as I think I understood from band27 I get the HTC version back but lose the SSPL what effect will that have?
thanks again

No, When you hard reset you will get exactly the same ROM as you have before you hard reset. IT will be just like the first time the phone booted after you initially re-flashed it.
The only way to return it to T-Mobile's ROM is to find the download that 'football' posted a few weeks ago and flash it.

Plz let a noob continue this question
If i use SSPL to flash a cooked ROM and for some reason want to go back to a original ROM, how?
Is it correct that i only take my original ROM and flash it as usual, or do i need to do annything els?
Do i need a goldcard?
Plz help a noob

Hard Reset Necessary?

So I use the Kumar roms and I was wondering, if I flash from version 1.5 to 1.6 of the same rom is it still necessary for me to do a hard reset? Or is it any time you update the rom, you must do a hard reset? What happens if you don't do a hard reset?
Thanks!

You don't have to do a hard reset but it always ensures that are no old sys files left that may have been updated in the version. It will help prevent any bugs or glitches from occuring but hard resets are not required with a new flash.

Or just run task29 first and u wouldnt have to hardreset...

lol, doesn't Task29 delete EVERYTHING? I mean, technically you're right, I wouldn't need to hard reset if I do a Task29.
Basically, I don't want to have to re-setup my phone every time I want to load the latest ROM.
Since it's the same ROM just updated it should be fine right.... right?

joe_coolish said:
lol, doesn't Task29 delete EVERYTHING? I mean, technically you're right, I wouldn't need to hard reset if I do a Task29.
Basically, I don't want to have to re-setup my phone every time I want to load the latest ROM.
Since it's the same ROM just updated it should be fine right.... right?
Click to expand...
Click to collapse
Well every time you flash a new ROM even if its just a newer build of what you already have it still wipes you phone and is basically the same as a hard reset. The reason why it is recommended run task 29 is because there are files that a hard reset DOES NOT remove that you dont want to have interfering with the new build. So I guess Im confused why are you worried about a hard reset if you just flashed and theres nothing on your phone to reconfigure anyway. But look into a UC program that will install everything that you want as the phone sets up for the first time so you dont have to do. Makes it much easier.

joe_coolish said:
Basically, I don't want to have to re-setup my phone every time I want to load the latest ROM.
Click to expand...
Click to collapse
You have to reset everything if you want to flash a ROM. There is no getting away from it.

I need to learn to use UC better or even Sashimi.
I HATE having to set everything back up after a new rom flash.
But yes, I would agree you should be running Task 29 before each flash...although I was puckered up the entire first time I tried it.

Maybe I'm a strange guy but I never do a hardreset after flash and I never experienced a problem for not doing that.
I just don't believe in it and I jump from build to build to base to base while I'm cooking.
Does HTC or T-Mob recommends you to do that after a flash?
joe_coolish said:
So I use the Kumar roms and I was wondering, if I flash from version 1.5 to 1.6 of the same rom is it still necessary for me to do a hard reset? Or is it any time you update the rom, you must do a hard reset? What happens if you don't do a hard reset?
Thanks!
Click to expand...
Click to collapse

Laurentius26 said:
Maybe I'm a strange guy but I never do a hardreset after flash and I never experienced a problem for not doing that.
I just don't believe in it and I jump from build to build to base to base while I'm cooking.
Click to expand...
Click to collapse
hah, you probably dont stay on one rom long enough to notice whether it works or NOT!
Does HTC or T-Mob recommends you to do that after a flash?
Click to expand...
Click to collapse
hmm, and what do THEY know about it????

Laurentius26 said:
Maybe I'm a strange guy but I never do a hardreset after flash and I never experienced a problem for not doing that.
I just don't believe in it and I jump from build to build to base to base while I'm cooking.
Does HTC or T-Mob recommends you to do that after a flash?
Click to expand...
Click to collapse
I don't either. hard reset after flash doesn't do anything different, I don't know why people say it matters.

DatDereX1 said:
I don't either. hard reset after flash doesn't do anything different, I don't know why people say it matters.
Click to expand...
Click to collapse
The reasoning is that when you flash, and allow the rom to instal, it doesn't do a task 29, so you flash, and then do a hard reset which forces a task 29, followed by the rom setting itself up for first use.
( Personally i sometimes do, sometimes dont. In my experience I seem as likely to get a good rom without doing it as getting a bad rom after doing it. Seems pretty hit and miss)

A flash is actualy doing the same as Task29, but when you use only Task29 it wipes out the phone internal memory and you have nothing.
During flash the rom gets formatted and the new data will be written.
samsamuel said:
The reasoning is that when you flash, and allow the rom to instal, it doesn't do a task 29, so you flash, and then do a hard reset which forces a task 29, followed by the rom setting itself up for first use.
( Personally i sometimes do, sometimes dont. In my experience I seem as likely to get a good rom without doing it as getting a bad rom after doing it. Seems pretty hit and miss)
Click to expand...
Click to collapse

Laurentius26 said:
A flash is actualy doing the same as Task29, but when you use only Task29 it wipes out the phone internal memory and you have nothing.
During flash the rom gets formatted and the new data will be written.
Click to expand...
Click to collapse
so task29 is not really something necessary, if you flash and hard reset right after?
Sorry for the newb question, but coming from excalibur to kaiser to raphael and now hd2, it's the first time I heard of task29, so just wanted to check if it's a big deal or not!

Yeah, I've heard mixed talk about Task29. I actually would really like to know what it is exactly. Why is it called Task29? Is it the same for all phones? I know you have to run a program from your computer to do it (Well, atleast that's what I think) I've never been brave enough to search for it and really understand it. Just saying "Task29" is kinda scary sounding!

Task 29 is a commando you give with MTTY to wipe out your phones internal memory.
MTTY has many commands and some can realy kill your phone as it can touch the bootloader if you give the wrong commands.
A device without a bootloader is dead.
Maybe other people think different about this but I recommend to use it only incase of a emergengy, to fix a corrupted flash.
joe_coolish said:
Yeah, I've heard mixed talk about Task29. I actually would really like to know what it is exactly. Why is it called Task29? Is it the same for all phones? I know you have to run a program from your computer to do it (Well, atleast that's what I think) I've never been brave enough to search for it and really understand it. Just saying "Task29" is kinda scary sounding!
Click to expand...
Click to collapse

THANK YOU!!! First time I started flashing (Kaiser) i did as advised. Ie. hard reset... then I quit doing this IMO absolutely unnecessary step and never noticed any difference.
The device memory will hard-reset and format everytime I flash it anyway.
Why should be two formats better than one?
Once you format hard drive, it's formatted. No need to format it again.
When people say "some files don't get formated" I'd like to see a proof. What files? What program did you use to view these files? If there is no such, HOW THE HELL DO YOU KNOW then????
Laurentius26 said:
Task 29 is a commando you give with MTTY to wipe out your phones internal memory.
MTTY has many commands and some can realy kill your phone as it can touch the bootloader if you give the wrong commands.
A device without a bootloader is dead.
Maybe other people think different about this but I recommend to use it only incase of a emergengy, to fix a corrupted flash.
Click to expand...
Click to collapse

WARNING: Task29 format may do harm to your device? Tell me this is not true

It’s bad day for me.
When I flashed Jackos Oldschool ROM(WM6.1_21048_M2.1) last week I used the Task29 tool to format the device, Jackos Oldschool ROM ran fine.
Then yesterday I flashed WM6.5_21903_M2.5 by Ark666 [Rhodium_AF],there was problem, the ok button on the up-right corner of the screen is not working,when you click it,the notifications window comes up,it's like you click on the midddle of the top screen. what's wrong? And it freezes whenever you click on Contacts(People) and HTC Calendar.Cannot use this rom.
Then I flashed WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5],Settings are not working,for example,you click on today setting,it doesn’t response.
These two roms are recent releases,I don’t see anybody post complaint about similar problem,therefore I suspect Task29 is the CAUSE because I formatted device before flashing these two roms.
I even tried flashing a official stock rom,then flashed WM6.5_21901 Valkyrie FireStorm tr2.5 again,the problem still exists.
Do you think Task29 might have damaged my device memory? I have not seen anyone gave a warning about Task29’s potential harm.
I just flashed old rom WM6.5_21889_M2.5 by dotcompt [DeepShining v12 RC] which I used before, thank god,have not seen problem.
I am worried my device memory has been damaged,gurus and everyone, pls have an assessment on my situation, I don’t hope it’s Task29 that bring this.
Thanks

Before flashed WM6.5, have u done task29 again? Every changing ROM u should do task29. Mine is just fine.

Personally I never had any issues with Task29. The forum is full of people who have used it with success. Try flashing Task29 again and then flash a Stock ROM to see if that will get you back on track. Good luck.

Sergio76 took Task29 apart and determined that it can cause NO DAMAGE to your phone. All the application does is write a 'dummy' ROM to memory setting all memory addresses to 0 (zero). It is not a true format as it doesn't set memory maps or similar, it just sets everything to Zero.
Russ

TASK 29 Does NOT harm the device its jusk like flashing a black. some of the issues you descrived could of been due to a bad download/ downloads maybe on the task29 or ROMs or maybe something else.. but if you feel Task29 is no working for you just flash the stock ROM before flashing a custom ROM

Russ741 said:
Sergio76 took Task29 apart and determined that it can cause NO DAMAGE to your phone. All the application does is write a 'dummy' ROM to memory setting all memory addresses to 0 (zero). It is not a true format as it doesn't set memory maps or similar, it just sets everything to Zero.
Russ
Click to expand...
Click to collapse
Hi Segio,Russ,thank you taking time to investigate this. if Task29 is not the cause,then there must be something wrong with these two roms,I am wondering anyone tried the following two roms:
WM6.5_21903_M2.5 by Ark666 [Rhodium_AF]
http://htcpedia.com/Rhodium-AF-manila-2-5-VX3/soft/htc-rhodium-rom.html?page=1
WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5]
http://forum.xda-developers.com/showthread.php?t=569507

I have posted the problem in rom makers' threads,hope they can give some thought.
WM6.5_21903_M2.5 by Ark666 [Rhodium_AF]:
http://htcpedia.com/Rhodium-AF-manila-2-5-VX3/soft/htc-rhodium-rom.html?c_page=11#comments
WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5]:
http://forum.xda-developers.com/showthread.php?p=6439578&posted=1#post6439578

bmw2320 said:
Before flashed WM6.5, have u done task29 again? Every changing ROM u should do task29. Mine is just fine.
Click to expand...
Click to collapse
what do you mean? do you mean we cannot do Task29 twice before flashing a rom?
No No I didnt format twice.
I formatted the device once then flashed Jackos Oldschool ROM(WM6.1_21048_M2.1),it's fine.
I formatted the device once then flashed WM6.5_21903_M2.5 by Ark666 [Rhodium_AF],it's NOT fine.
I formatted the device once then flashed WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5],it's NOT fine.
Now i think my experience is clear to you.

Dunno it did for me...
I don't know if it is true that it will do harm or if my issue is repeatable...
I have been flashing ROMs for years on my Titan and Rhodium and never had any reason to do something like Task29...
One of my regular ROMs is MightyROM. I do not understand the reasoning but in January Mike recommended flashing back to stock then to his newest ROM. So I did it because he said to. Mine is not to question Chef.
So again flashing through ROMs and last month Mike said to run Task29 and completely empty the ROM before installing his new one. So I did...
All I could get was the black screen that says "TouchPro 2" in white.
I tried everything. Posted in forums. Research. Finally I called Verizon Support. Nothing could get me into the bootloader... So fortunately Verizon sent me out a "like new" handset.
Since getting the new handset I have flashed MightyROM, Energy, BharS, Mr.X, and others looking for the best ROM for me for this time. I have had no issues ever in flashing ROMs on multiple devices that I don't know why Task29 would ever be necessary.

nokiadashi, i would assume since your using recent roms that your falling in to the trap of early adopters, buggy roms.
MHatter469, thats what its supposed to do, you use the cdma version for verizon. after you task29 connect your phone to your computer hold the volume down button while pressing the reset button at the same time. after you press the reset button keep holding the volume down until a red,blue green, white screen shows up. thats the boot loader. From there flash your rom like you always have

ive used task29 once to flash a rom to my device and thats when i flashed it from the stock rom
after that i have never used it before flashing. Am i taking a risk by not doing it?
i usually flash straight from my device because i download the rom through my phone and extract and flash making use of my computer unecessary instead of fighting with windows7

[Q] Task 29 problem

I'm sorry i know it's against the rules to be starting a new thread but it's been a week i've been asking for help and no one noticed. This is just a try to come noticed.
I installed task 29 on my blackstone. I had olinex 1.56 installed and later did the task29 with radio 1.13, 1.14 and 1.17 After successfully doing it i went on step 2 that is installing a clean rom. I tried these roms
blackSTONEhengeHyPerSlim_4_1
RUU_TOUCH_HD_MARYONE_23148_WWE_191110
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship(3)
They get installed but after i store the contacts and everything it gets stuck if kept for like half an hr. The screen doesn't respond but power button and the volume button works.
I took my phone to a repair center and they couldn't fix it. So please help me i've just got only one phone.
I don't mean to offend any moderators by this but i'm just asking for your help. Thank You

Try reinstalling stock ROM after Task 29.
Restore ONLY contacts, and then try using device for several days.
DO NOT install any other software!!!
If it works, then problem is in some data or software you're restoring.
If not, restore original SPL and original ROM and try again.
If it does not work... and service can not help you... then sorry...

Hello i did reinstall the stock rom after task 29 and i was using pimbackup for restoring but that freezed my phone so i installed the stock rom again and thought of not using it. Did that but nothing much helped.
I hope believe these are the correct shipped roms
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship(3)
Everything on xda has worked like wonders for me. Be it android on any other rom but right after task29 nothing seems to be working on my phone.
One thing i've noticed after installing any rom after task29 is if i get to the bootloader it gets me to a 1 sec white screen saying no image found. I hope what's causing a problem.

Do you understand WHAT Task 29 is?
It formats the partition drive of your device where the ROM resides. Meaning, it wipes any data regarding ROM.
So of course it would say "No image found".
I don't know which ROM is stock for your device. Try to update ROM via HTC site.
If lucky, it will suggest / let you find adequate ROM.
For my device it's 1.56.407.2 (German)!
If unlucky, it will say "Not supported" or something like that - then go for Orange 1.59.61.2 ROM.
And you might try one 1.5x ROM flash WITHOUT Task 29...

Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.

Thanks will do it and keep yu updated with it..

simplistian said:
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Click to expand...
Click to collapse
Thanks i tried installing the stock rom like you told me but then got stuck on the screen alignment screen. I later installed blackSTONEhengeHyPerSlim_4_1 and now it's responding to every touch. Thanks alot. I hope this stays like this and yes instead of restoring i forwarded all the contacts through bluetooth. Owe you a BiiiiiiiiiiiiG thanks..

Too soon to be happy as same again..I don't think there should be a problem with touch as it works fine for first 1hr but right after something gets stored by something i mean contacts it stops reponding after sometime. The volume and power button work all fine. I can't make out the problem. Any ideas or suggestions. Shall i make a video and post ??

FIRST you have to make it work with factory settings - stock SPL and stock ROM.
After that flash what you like...

I think you have to follow Bodisson's suggestion, do everything as stock and retest without restoring anything. If it still failed...... you should have it repaired
Good luck!!

I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...

Bodisson said:
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Click to expand...
Click to collapse
Glad to see somebody researching things out and settling on a radio he prefers due to performance rather than those just going for latest

I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.

kulwant said:
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
Click to expand...
Click to collapse
All rom's should work with each radio to be honest. Glad your device is working better, though still a little baffled why you're still having difficulties
EDIT - You are on a wm6.1 rom. Is the rom based on 1.56+, if not you may need to revert to HSPL 1.14

I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers

kulwant said:
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
Click to expand...
Click to collapse
I'm baffled but still want to get to the bottom of your issue and would appreciate any help from other members who may have idea's on how to solve your issue. From what I've read everything you have done is correct, but I don't like being stumped!!
If we start from the start, we may get to the bottom of this........

Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.

kulwant said:
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
Click to expand...
Click to collapse
Well as you know a T29 formats device so you need to flash a rom or you'll be stuck at boot screen. Before you do a T29 it states you must have HSPL on your device first. Now from what I've read you did have HSPL on first and your T29 worked as you where stuck at boot screen afterwards.
I'm assuming you turned device off, booted into bootloader then flashed youir rom (blackSTONEhengeHyPerSlim_4_1) which is based on 1.56+ as was your HSPL.
This all seems correct so I'm not sure what went wrong.
Is above all correct?
Did you try a T29 again and flash different rom or did you just flash different rom over existing?

I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.

kulwant said:
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
Click to expand...
Click to collapse
Right, I never put any files in same folder as it only confuses flashing process and can cause issues. I.e. put T29 in its own folder, radio 1.14 in its own folder and then rom in another folder.
Do a T29 and when its complete, I.e. stuck in smart mobility screen. Then you take out battery to turn phone off. After this put phone into bootloader and flash rom. Then flash radio after it as a lot of roms have a radio file included
...........................
Sent from the improved version of Tapatalk, better known as Forum Runner

Need Help. PLEASE!!!!!!

I can no longer get android to run on my HD2. Here are the details to my problem. Please I really need help, will make it well worth the while of anyone that can sort this problem out for me.
First off, I had been running android on my device for about a month. Then it started just going off and freezing at the android boot logo. Nothing I did would work unless I reinstall the rom.
Then that just stopped working and even after reinstalling a rom (nand) it would never get past the android boot logo after the go go go screen. It would just stay there then restart and the restart loop continues.
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Nothing works. And I have lost count of how many times I have gone through all this.
Please take note that I did have android running on my EU HD2 with the HSPL, radio and rom in my sig on this very phone so I at least know what I am doing.
I just dont get this issue, cause windows mobile runs just fine on my device every single time. My cards read fine too. And even when trying to run an SD rom build, after haret starts up it cuts to the HTC logo and just hangs there too. And I am assuming that if it was my battery or my battery pins it would at least affect the phone generally and not only when trying to boot android.
Please, I really need help as this phone is practically useless to me now.
Any help would be greatly appreciated.

Lorddeff07 said:
I can no longer get android to run on my HD2. Here are the details to my problem. Please I really need help, will make it well worth the while of anyone that can sort this problem out for me.
First off, I had been running android on my device for about a month. Then it started just going off and freezing at the android boot logo. Nothing I did would work unless I reinstall the rom.
Then that just stopped working and even after reinstalling a rom (nand) it would never get past the android boot logo after the go go go screen. It would just stay there then restart and the restart loop continues.
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Nothing works. And I have lost count of how many times I have gone through all this.
Please take note that I did have android running on my EU HD2 with the HSPL, radio and rom in my sig on this very phone so I at least know what I am doing.
I just dont get this issue, cause windows mobile runs just fine on my device every single time. My cards read fine too. And even when trying to run an SD rom build, after haret starts up it cuts to the HTC logo and just hangs there too. And I am assuming that if it was my battery or my battery pins it would at least affect the phone generally and not only when trying to boot android.
Please, I really need help as this phone is practically useless to me now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried running a CLK build or just MAGLDR or SD builds?
As far as i know (sorry if this is nonsense ) the HD2 runs natively on ppp not on rmnet, magldr (and sd?) pushes something in the radio so that rmnet can be used, maybe something in that direction went wrong with your phone?

Cheech1976 said:
Have you tried running a CLK build or just MAGLDR or SD builds?
As far as i know (sorry if this is nonsense ) the HD2 runs natively on ppp not on rmnet, magldr (and sd?) pushes something in the radio so that rmnet can be used, maybe something in that direction went wrong with your phone?
Click to expand...
Click to collapse
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.

Lorddeff07 said:
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.
Click to expand...
Click to collapse
Well before i get flamed by those who know better, i would ask you to look for threads covering this topic, i.e. the difference between ppp and rmnet and which one is used with which one etc.
I have read in another forum that the hd2 runs natively with ppp, but magldr pushes something "in" the radio rom while booting, so the radio looks like a desire, so the android builds can run on rmnet...
Or something like that, what i have gathered from this is, that there is a difference and since it sounded like you were running out of options, i thought i´d propose installing a clk build

Lorddeff07 said:
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Click to expand...
Click to collapse
Can you elaborate "formatting my SD cards" a little?
As in how, which tools, were was the partitioning done if any?

Lorddeff07 said:
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.
Click to expand...
Click to collapse
Hi,
Sometimes boot loops occur when the battery pins are out of shape.
Make sure all your battery pins are aligned and see if that helps.

Cheech1976 said:
Well before i get flamed by those who know better, i would ask you to look for threads covering this topic, i.e. the difference between ppp and rmnet and which one is used with which one etc.
I have read in another forum that the hd2 runs natively with ppp, but magldr pushes something "in" the radio rom while booting, so the radio looks like a desire, so the android builds can run on rmnet...
Or something like that, what i have gathered from this is, that there is a difference and since it sounded like you were running out of options, i thought i´d propose installing a clk build
Click to expand...
Click to collapse
Looking into trying a CLK build now. Actually just finished downloading one.
Cheech1976 said:
Can you elaborate "formatting my SD cards" a little?
Click to expand...
Click to collapse
Ok, i have a total of 3 SD cards. One 16GB, one 4GB and the last one 2GB. I have used both gParted and partition wizard. Did full 30 mins (approx) wipes on the cards and had them formatted to fat32. For the 16GB card I try that with the ext3/4 partions. Tried using both 4kB and 32KB cluster sizes.
And again, I had actually got android running on my phone before. And even tried different roms at that time so I have some idea what I am doing. I don't have any issues reading my cards either from a card reader or through the phone.
malybru said:
Hi,
Sometimes boot loops occur when the battery pins are out of shape.
Make sure all your battery pins are aligned and see if that helps.
Click to expand...
Click to collapse
Yeah read about that, I have tried straightening my pins and all that but nothing changes. And I would think that if the pins are the issue then I would at least hav some issues running windows mobile 6.5 too. I have never had such issues running WM ever. Android on the other hand just refuses to run.

Lorddeff07 said:
Yeah read about that, I have tried straightening my pins and all that but nothing changes. And I would think that if the pins are the issue then I would at least hav some issues running windows mobile 6.5 too. I have never had such issues running WM ever. Android on the other hand just refuses to run.
Click to expand...
Click to collapse
Hi,
The only thing I can think of is maybe some corrupt software along the way.
May I suggest using KSUBEDI's TOOLKIT (Don't forget to thank him).
Run through the whole process using his toolkit.
It worked for me.
Start from
HSPL 2.08 HSPL
Task 29
Radio HERE
Magldr
CWM partition for the ROM you intend to use
ROM

malybru said:
Hi,
The only thing I can think of is maybe some corrupt software along the way.
May I suggest using KSUBEDI's TOOLKIT (Don't forget to thank him).
Run through the whole process using his toolkit.
It worked for me.
Start from
HSPL 2.08 HSPL
Task 29
Radio HERE
Magldr
CWM partition for the ROM you intend to use
ROM
Click to expand...
Click to collapse
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.

Lorddeff07 said:
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.
Click to expand...
Click to collapse
Hi,
What ROM are you installing, and what CWM partition are you using?

Lorddeff07 said:
Ok, i have a total of 3 SD cards. One 16GB, one 4GB and the last one 2GB. I have used both gParted and partition wizard. Did full 30 mins (approx) wipes on the cards and had them formatted to fat32. For the 16GB card I try that with the ext3/4 partions. Tried using both 4kB and 32KB cluster sizes.
And again, I had actually got android running on my phone before. And even tried different roms at that time so I have some idea what I am doing. I don't have any issues reading my cards either from a card reader or through the phone.
Click to expand...
Click to collapse
Didn´t mean to let it sound like you don´t know what you´re doing, just trying to narrow it down and the sd cards can be the culprit for so many bugs, so it was worth a shot
Lorddeff07 said:
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.
Click to expand...
Click to collapse
malybru said:
Hi,
What ROM are you installing, and what CWM partition are you using?
Click to expand...
Click to collapse
Especially the NAND partition used in flash.cfg would be interesting, maybe there´s something wrong with that, that would be consistent with the failure to boot, wouldn´t it?
Other than that, i have to admit, slowly but surely this leaves my area "of expertise"
I sure hope you get your phone running again! I´ll keep my fingers crossed!

malybru said:
Hi,
What ROM are you installing, and what CWM partition are you using?
Click to expand...
Click to collapse
I am installing HyperDroidGBX-v12[GRI54-2.3.3][a2sd+][TytR8.3] and using the required 150mb partition size. I had got this very rom and RAFDROID rom (though with a 400mb partition) to work on my phone previously.
I also got the a couple of SD based roms to work on my device before nand roms became available now even those dont work too.
Just tried CLK for the first time and flashed the CLK version of the aforementioned rom. Been on the white HTC screen for about 10mins now.

Cheech1976 said:
Didn´t mean to let it sound like you don´t know what you´re doing, just trying to narrow it down and the sd cards can be the culprit for so many bugs, so it was worth a shot
Especially the NAND partition used in flash.cfg would be interesting, maybe there´s something wrong with that, that would be consistent with the failure to boot, wouldn´t it?
Other than that, i have to admit, slowly but surely this leaves my area "of expertise"
I sure hope you get your phone running again! I´ll keep my fingers crossed!
Click to expand...
Click to collapse
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.

Lorddeff07 said:
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.
Click to expand...
Click to collapse
Hi,
That would mean making a DAF.exe file and install it the old fashioned way.
Sadly,beyond my level of expertise.
Good luck.

Lorddeff07 said:
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.
Click to expand...
Click to collapse
Sorry but i am at a loss for any further possible advice for you. I would propose the build i am using for you to install.
It installs with the according daf.exe and after that you can install the zip file via cwm. I never flashed another android build myself, what with all this nand partitioning (i have heard of it, but never had to set it up myself), so i don´t really know how the nand partitioning is done without daf.exe and the according flash.cfg file.

Cheech1976 said:
Sorry but i am at a loss for any further possible advice for you. I would propose the build i am using for you to install.
It installs with the according daf.exe and after that you can install the zip file via cwm. I never flashed another android build myself, what with all this nand partitioning (i have heard of it, but never had to set it up myself), so i don´t really know how the nand partitioning is done without daf.exe and the according flash.cfg file.
Click to expand...
Click to collapse
Thanks, will try. I have given up though. been working on this thing for too long. Guess its time to buy the galaxy s2. I really loved this phone. And windows mobile just doesn't cut it.

Lorddeff07 said:
Thanks, will try. I have given up though. been working on this thing for too long. Guess its time to buy the galaxy s2. I really loved this phone. And windows mobile just doesn't cut it.
Click to expand...
Click to collapse
Hi,
Just before you bin it,how have you been formatting the sd card?
Have a look at this:
"You should also properly format your sdcard with Panasonic SDFormatter (Full+Overwrite+size adjust). Then in recovery>advanced>sd partition (1GB+0MB swap) If you have a EU HD2 and need the extra data storage/rom requires it. "
Worth a shot.

Dont give up!
Might be a long shot, But have you tried turning off your antivirus software during the installation? Ive seen a few of your posts about and i hope you get it to work again. Bet your sick of the sight of task29 lol

malybru said:
Hi,
Just before you bin it,how have you been formatting the sd card?
Have a look at this:
"You should also properly format your sdcard with Panasonic SDFormatter (Full+Overwrite+size adjust). Then in recovery>advanced>sd partition (1GB+0MB swap) If you have a EU HD2 and need the extra data storage/rom requires it. "
Worth a shot.
Click to expand...
Click to collapse
yeah I have tried that too. Still leaves me hanging at the android logo right after the go go go screen. Truth is that I have come to the conclusion that nothing i am doing will actually work. Cause all these things mentioned now I have already done and didn't even need to do half of them at one point when i was actually running android on my phone.
The fact that I cant even run the SD card builds of android just goes to show that something must be very wrong with my phone now. It could be battery related or something but that doesn't make sense either cause WinMO 6.5 roms work fine every singel time.
I just dont get it really.

fuuunkdat said:
Might be a long shot, But have you tried turning off your antivirus software during the installation? Ive seen a few of your posts about and i hope you get it to work again. Bet your sick of the sight of task29 lol
Click to expand...
Click to collapse
Lol.... you have no idea lol
Its sad no doubt, but I am actually happy for the amount of help offered by a lot of ppl here in the xda community.
So at least I am taking it all in good spirits. Oh, I have probably tried that at one point too....
The only thing I can think of now is to flash my HSPL back to spl 1.66 and revert back to factory setting, then try and reflsah the 2.08 HSPL. Though I dont know what difference taht will make considering how many times i have reflsahed the very same 2.08 HSPL so at least i know I have a clean fresh one on my phone now lol.