Related
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
I came to this phone solely because there are so many roms to choose from and a lot of development. In the past I have worked flashed dif galaxy s phones, and mytouch 4g so I am not a complete noob.
When i power the phone on these are displayed:
R: 2.10.50 26
G: 15.39..50.07U
D: 2.13.90963 8G
In settings my flash size is 1024mb
I read the guide through and I just want to be 100 percent clear that my phone is capable of something before I flash it. So in short, do I just flash hardspl to phone, then magdlr, then the rom? I have a macbook pro and my windows desktop is old and sucks so I try to avoid using it whenever possible. Once i flash hardspl and magdlr can I use clockwork recovery to flash my rom? I am going for the cm7 nightlies. All help is greatly appreciated!
Yeah that's correct. I don't think there are any osx installers though, so you'd probably have to do all this through bootcamp. I don't have a mac so I don't know about the stability of bootcamp, but you really gotta make sure your computer doesn't crash during the flashing process, especially HSPL.
After having Magldr installed you can either use that to flash, or indeed use clockwork (which I recommend). MDJ's Gingerbread is a great CM7 nightly build.
Thanks for your quick reply! How long does it take to flash hardspl? And do I need to have that activesync thing going with windows mobile? This phone is 100% stock I dont want to back it up so can I just avoid windows mobile active sync and run that program in the noob tut
And one more thing, do I need to check to see if my stock spl is supported? What is everything I need to verify to ensure I will not brick the phone due to flashing the wrong thing? Thanks
Go to the guide, it tells you what you need in there. HSPL takes seconds to install. Once that is installed, it's pretty hard to brick your device. Just be wary when installing a stock rom. Best advice is to read lots.
Good luck.
:edit:
I'm not sure if you need active sync. I'm 99% sure you do, but I may be wrong.
Sent from my HD2 NANDroid using XDA App
Flashing HardSPL takes about 20s.
A rom takes about 10m. You can also check this link.
http://forum.xda-developers.com/showthread.php?t=925509
and
http://forum.xda-developers.com/showthread.php?t=893948
They explain how it works. Even with video.
good luck!
I'm guessing you have a T-Mobile so watch out! Don't flash an EU-radio.
If you want android your radio is good. No need to change it.
Flashing a rom takes only 3-4 minutes, but it will stop at 96% or 99% for a few secs, so don't freak out
also be sure to flash the newest version of HSPL. and check the youtube vidz, there many around. you don't even have to read, just google youtube+HD2+hspl
The support for this phone is much better than other devices, quick responses thanks! Just to be safe I am trying to find the windows sync thing for the phone. When I am finished flashing hardspl and magdlr do I need to format my sd card to a special way or can I just delete all the stuff on it and put the rom?
I strongly recommend that you first install the official 3.14 firmware, It has the newest radio so you don't have to worry about bricking your phone. After that flash hdspl and you are safe and ready to install magldr and Android.
Depends on the rom, zip, app2sd+, cwm, anything which mentions ext2/3/4, data.img data on sd, all require certain partitions. I would recommend starting with projections rom. It's quick and easy to get started with, and is a good base to get some confidence.
Sent from my HD2 NANDroid using XDA App
I just installed the hspl and now i am going to do the magdlr. Really I only want cyanogen mod 7 nightlies on here. I am pretty confident its just whenever it is my first time with any phone I like to be 100% clear because they all vary. I didnt get to looking at the installation of cm7 yet but I am sure I will be going to ext4 with it too. What format do sd cards come stock? I just wiped everything on it but im guessing thats not enough lol.
Um confused... I just got around to flashing magldr 1.12 and it said on screen and in guide post it will take ten min, it took no more than 30 sec. It did boot me into the black magldr screen though so i guess its good. Now can flash cm7 or is there other stuff. I am sure I will find out with more reading which i am about to do but I would like to use cwm to do it.
rrodxbox360repair said:
Um confused... I just got around to flashing magldr 1.12 and it said on screen and in guide post it will take ten min, it took no more than 30 sec. It did boot me into the black magldr screen though so i guess its good. Now can flash cm7 or is there other stuff. I am sure I will find out with more reading which i am about to do but I would like to use cwm to do it.
Click to expand...
Click to collapse
It's just a very wide margin to prevent people from flooding the forums if the flashing takes a little longer than expected, 30 seconds is normal.
Go to the clockwork thread and follow the 7 steps posted, you can then use CWM to flash CM7.
I have been trying to flash with usb flasher and I keep getting an error.
Error Description: USB init failed.
Can I flash cwm from magdlr? Every time I reboot it goes to that.
I see two possible problems here:
- In Magldr, have you picked menu item #4? (Something like USB Flasher). If you can still see all the options on the menu, you have not correctly selected it.
- Your USB drivers are not correctly installed. Reboot computer, power off and unplug phone, replug and restart Magldr. Wait for drivers to correctly install.
I just did what was suggested and same thing. Can I install it a different way? Option number 5 is usb flasher, 4 is mass storage.
My bad, I'm still using an older version of Magldr where it's #4.
What are you flashing by the way, CWM or CM7?
By the way, are you running the flasher as admin? Not sure which OS it is you're bootcamping, but right click on the installer and choose Install as administrator should be an option. Might be the problem!
I am on my desktop pc which is xp so I do not believe i need to run as admin. I was just checking out another post in this forum that has a fix for nand usb init failed, I am lost as to what daf.exe is. It sounds when I figure that out I should be good to go.
And I am trying to install cyanogen mod 7 mdj's version. If I can not get usb thing to work could I install clockwork mod without having to use computer and jsut put a .zip file on sd card?
I just hit run and typed DAF.exe and there isnt one. I am not completely lost lol
DAF.exe is the clockworkmod flasher.
I'm not sure what's going wrong, but just try everything again and make sure you follow the instructions very closely, you're probably just overlooking something somewhere.
Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install. So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03. So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins. Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick? Or might one of you have The Ultimate Revival Secret for me?
myrtthin said:
Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install.
Click to expand...
Click to collapse
do you mean magldr wouldnt START? see note at the end**
So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03.
Click to expand...
Click to collapse
no need, you could have just flashed teh radio, thus avoiding changing teh whole rom, removing magldr and hspl, and taking about ten minutes less.
So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
Click to expand...
Click to collapse
ummm, what OS? you havent flashed one yet
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
Click to expand...
Click to collapse
spl is prevented from being changed by usb flashing once hspl is installed
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins.
Click to expand...
Click to collapse
again, there is nothing to boot, , flashing magldr removes winmo, and you havent yet flashed an android rom.
Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick?
Click to expand...
Click to collapse
not even close. So far everything sounds like a simple missmatch between magldr spl and radio, made more confusing because you arent really 100% sure of what exactly is being added / removed at each step. (Sorry, not having a go, just being blunt )
the connection errors might be an issue, but probably not, give your PC a reboot, use a different usb port.
in bootloader, what do the top line, and the spl line say? does it say USB at the bottom?
With your phone in bootloader and connected to PC, on the PC, click start - right click 'computer' (or 'my computer', depending on win version) choose properties, find device manager, and see what entry is listed for the phone.
**NOTE when you flash magldr, if the radio or spl is wrong, magldr will be there, it just wont show up, it will go straight to the boot screen and hang there. You dont have to re flash magldr, just change the spl/radio to the correct ones, and magldr is still there and should start, no need to re flash it. Magldr is only removed by flashing a stock winmo rom (or a cooked winmo rom that includes splash screens)
Be still, my beating heart...
Thanks for your answer, Sam. No harm done in the bluntness, you quite rightly marked me as a noob. Indeed not all is clear on the boards, but we all do our best.
As you said, I had no clue all the OS on my phone were gone. So i saved me another ten minutes (thank you, again) and flashed a new radio. And behold! Magldr is back!
You, sir, should be kissed!
Now to find out how to install a Zimage, that still seems to elude me (seeing there is no daf.exe or install.exe)... I'm aiming for this one to install: http://forum.xda-developers.com/showthread.php?t=1250703. hd2toolkit will only help out on nb or nbh, though.
If you could point me in the right direction?
And muchos thankyous are coming your way!
well first up you should add cwm on top of magldr, most roms are clockwork(cwm, cwr its called slightly different things, all mean the same, , 'clockwork mod recovery') roms.
You can do this with the toolkit, but instead of the hd2 being in bootloader, enter magldr and choose 5 usb flashing, then in the toolkit, choose a partition size, (160 by the looks of it, for an eu model) and when thats done,
restart,
enter magldr
option 8 ad recovery - will start cwm,
then choose 'install zip from sdcard' - 'choose zip from sdcard'
but remember BEFORE you do all the above, you should
1 - set up your ext partition (you can do that in cwm, , 'advanced' - 'Partition sd card', but be warned it will wipe the whole card)
and
2 - copy the romname.zip onto teh sd cards fat32 partition.
EDIT - oh and most roms have two versions, a magldr version and a cLK version, dont confuse cLK with CWM, theyre different things. For now stick to teh magldr versions, you can find out about cLK later.
Now we're getting places!
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
However, the android I pointed out is, if I read you correctly, not NAND? It was posted in the NANDcategory, so that confuses me. Bummer, I need my SDcard for data.
yea its a nand rom. most nand roms use an EXT partition, and for most sense 2 roms, its advisable, and for sense 3 roms it simply wont work without it. Look at the partition size for the tmous version(which is the same but doesnt use an EXT),,,435meg, that's just for the system partition, it would leave you about 50meg for apps and data.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
myrtthin said:
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
Click to expand...
Click to collapse
not a rom, as such. Go into the toolkit, with teh phone in magldr, option 5 'usb flashing',,at the top of toolkit 'magldr repartition', below that click the 'custom' size, below that cache size 5 (from the 5/160/5, personally i use 45 regardless of what teh rom says, but thats just me, its not absolutely critical), then below that 'repartition', , a popup will ask you teh custom size, 160, OK,and off it goes installing cwm.
Hm, interesting.
Thanks to your feedback, i get magldr 1.13 up and running, just fine.
Next to that, flashing ROMs seems to be working smoothly.
However, none of the android ROMs are taking! I downloaded (from several sources to exclude download errors) three ROMS:
1) rom Based RUU Desire HD 3.06.405.1 - With sense 3.0 - Android 2.3.5 http://forum.xda-developers.com/showthread.php?t=1264828
2) Desire_S_sense3.5_Android.2.3.4_v1.2_EU.zip http://forum.xda-developers.com/showthread.php?t=1250703
3) GBLeor3 http://forum.xda-developers.com/showthread.php?t=1256581
nrs. 1 and 3 are installing, but on startup hang on HTC's splashscreen. Nr 2 is not installing (aborting during install, status 0), tried both on 5/160 and 5/200.
Seems like android install through magldr is not working at all! Any thoughts?
To be complete, I installed:
hSPL 2.08
magldr 1.13
radio 2.15.50.14
repartitioning through hd2toolkit
It all started with stock winmo, wich i updated to 3.14.404.2. It's an EU phone.
Don't forget it takes a while on first boot, especially the large ones,I can well believe a sense 3 rom that is writing 300+ Meg to the ext partition would take well in excess of ten/fifteen minutes and more first boot.
Also, if you flash a rom and then go to flash another, you will be leaving parts of the old rom on the SD card. In cwm before the flash choose wipe data/factory reset. That's in cwm, not magldr. Also, did you set up the ext through cwm?
My advice would be go for a simpler rom, one of the cm7 roms, typhoon for example, purely to show its working.
The desire S (sense 3.5) did not even install after 6 hrs, so I'm guessing something's wrong there ;-)
I'll wipe data between flashes, and per your suggestion, try something light as an appetizer first. Not before next weekend though! I lost enough sleep )
Thanks again!
When I started flashing nand, very often(six times in ten maybe?) the first boot never completed, and I soon learned that if after a few minutes nothing happened,I'd pull the battery and it would Start the next boot. Also, keeping the hard keys lit (touch every min or so) seemed to help.
I know I'm straying into "lucky socks" and good luck charm territory,but can't help to try, and I DO know I've seen one rom in the past where the instructions mention keeping the screen on as being important, so who knows?? Not this stoned and overtired techaddict!
I've had a stable rom that I've been just flashing updates for some months now, so I've not had that situation for a while. The wipe data command in cwm is deff important tho.
The only other thing that consistently causes non starting is too small a partition size.
cyanogen is stable
Yub yub, commander, time for an update. Cyanogen has been installed and working for close to 3 months now. So it actually does all work!
On the boards, I can now see updates on the ROM I crave (sense 3.5 from htc desire), and those updates are suggesting 260 Mb partitions (no ext). So it would seem my first partition was indeed too small.
So tempted to try those again...
Too bad cyanogens rom backup is acting weird. Otherwise it'd be no problem just to try, eh?
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.
hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with ,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks
moose579 said:
hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
Click to expand...
Click to collapse
I assume (since about ten people per day ask exactly this) that you flashed magldr but magldr didn't start as expected? This is caused by (as I type half a dozen times a day) by not having 2.08.hspl AND a compatible radio.
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
Click to expand...
Click to collapse
bootloader
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with
Click to expand...
Click to collapse
not sure what that means, sorry.
,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks
Click to expand...
Click to collapse
You haven't given any real details as to what you have done so far.
Details details details.
So, tell us what you did so far, please. Please be detailed, with names, filenames, versions, etc. not just 'i flashed that thing and now nothing works'
hope this helps more
ill start from the start
i first ran this file HSPL3_PKG.exe this run fine without any problems
then i ran this file rom updateutility from this rar folder ive downloaded called DFT_LEO_MAGLDR113_DAF
now this is where it all went wrong ,i ticked all the boxes and went thought the set up by following this video
got to 6;08 into the video and followed the steps
then got to 7;04 in the video and this is where the phone stayed on the htc screen for 30 mins ,,,and its done nothing
so i unplugged it
now i read that its possible to get the phone back to booting up with another offical rom from htc but carnt find the rom that ill need ,,plus the windows mobile wont reconise my phone in usb mode
hope this helps you a little more to solving my problem
and sorry i carnt post the link to the video yet as ive not done my 8 posts
ok, so its all fine so far, you just haven't yet done the next step, which is flash a compatible radio. (had you changed the radio after flashing hspl and before flashing magldr, magldr would have started straight away)
(I shall assume that you have a regular hd2, not a t mobile US model, since you haven't said, if it IS a tmous, then its a different problem)
download radio 2.15.50
enter bootloader
plug in usb
count to 5
run customruu to flash that radio
reboot
magldr should now start
thanks for your reply
ill go and find this radio now and keep you posted
thankyou
you rock dude
thank you so much for your time posting ,,
100% working andriod now
anything eles i should know please post
Lovely.
Only thing to know is that you shouldn't need to flash radio or magldr again now, if you want a different sized rom you may have to reflash cwm to change partition size, but if you ever have probs booting or whatever, nine times in ten someone will tell you to task29 and reflash stock and start over,,,, nine times in ten that's massive overkill.
Read read read is the best advice I can offer, see what issues others have and read the answer,, one day that issue might be yours, and you'll have a head start solving it. Never panic and start random flashing, that always ends badly, and means any help request posts are harder to work with.
thank for your reply
just a quick question for you
ive got a 16gb sd card in with about 300 app/games ,,and ive installed about 20 so far but now phone says memory full ,,should they be installing on sdcard instead of the phone memory
or is this normal for the phone memory to run out so fast
Depends on the rom, some leave 200+ free, some far far less. That's why most roms support an ext partition, which the phone treats as internal.
Backup your SD card (it will be wiped) start phone into cwm, then (I think its) advanced - format SD card, or something like that. Create a 1 or 2 gb ext partition, swap 0, and reflash the rom. C
The rest of the SD will be formatted to fat32 just like it is now.
It will detect the ext partition and use it as internal memory automatically. You should not choose the option to "move app to SD card", that will take the app off the ext partition and put it in the fat32 partition,, and some apps wont work from fat32.(angry birds for example)