Hi searched the threads and cant find the answer. HD2 512.Radio_2_14_50_04
Put HSPL on it no bother
Ran Magldr 1.3 it flashed, the phone said reboot but didn't. Took the battery out and the phone restarted but came up with the hit 1 error.
Put it in bootloader tried to flash a standard rom, froze at 0% then failed.
Renamed the Nbh file and put it on the memory card, back into bootloader, phone said loading but nothing happened.
Tried to run task 29 sticks at 0%
The bootloader is stating usb, so I have now ran out of ideas, so any help would be appreciated.
husky_motox said:
Hi searched the threads and cant find the answer. HD2 512.Radio_2_14_50_04
Put HSPL on it no bother
Ran Magldr 1.3 it flashed, the phone said reboot but didn't. Took the battery out and the phone restarted but came up with the hit 1 error.
Put it in bootloader tried to flash a standard rom, froze at 0% then failed.
Renamed the Nbh file and put it on the memory card, back into bootloader, phone said loading but nothing happened.
Tried to run task 29 sticks at 0%
The bootloader is stating usb, so I have now ran out of ideas, so any help would be appreciated.
Click to expand...
Click to collapse
Here is my run down. try using a different USB port just in case it is a driver issue. Did you you use a 500MB to a 4GB Sd card formated Fat 32? Maybe you got a bad download try redoanloading or copying it to the SD card, maybe bad file transfer. Make sure you try running the update as administator. Heck just keep trying period, it seems like several people or having this kind of problem as you with not being able to get the phone to boot and then not being able to flash a ROM to fix it. But through perserverience they did get it to flash just had to keep trying and trying. By chance does it even show the screen on .oot up that has the R, G, and B in red letters if so what does the R and the D have beside them?
The minute you tried to flash a stock rom from SD,, you removed hspl, even if the flash stopped at 0%. In fact it stopped at 0 because hspl is no longer there to allow the flash and I suspect you used just any stock rom, not the correct stock rom.,,,, ditto with task29.
T-Macgnolia said:
Here is my run down. try using a different USB port just in case it is a driver issue. Did you you use a 500MB to a 4GB Sd card formated Fat 32? Maybe you got a bad download try redoanloading or copying it to the SD card, maybe bad file transfer. Make sure you try running the update as administator. Heck just keep trying period, it seems like several people or having this kind of problem as you with not being able to get the phone to boot and then not being able to flash a ROM to fix it. But through perserverience they did get it to flash just had to keep trying and trying. By chance does it even show the screen on .oot up that has the R, G, and B in red letters if so what does the R and the D have beside them?
Click to expand...
Click to collapse
Hi The phone does go into the red/geen/blue boot screen. (will post later what the writing in red states)
Using a 2gig memory card which was formatted using panosonic and is fat32.
Tried different usb then a different laptop (both running windows 7) Tried a fresh download of the rom from HTC using the seriel no on the phone so should be the right one. Tried to run the RUU from both the laptop and renamed on the card. Not sure if its worth trying to put CWM on it?
samsamuel said:
The minute you tried to flash a stock rom from SD,, you removed hspl, even if the flash stopped at 0%. In fact it stopped at 0 because hspl is no longer there to allow the flash and I suspect you used just any stock rom, not the correct stock rom.,,,, ditto with task29.
Click to expand...
Click to collapse
Hi
The rom was the official one downloaded from HTC based on the phones seriel No.
Will try installing HSPL again and Magldr, but was trying to put a standard rom on, as all the comments advise flashing back to standard if your having problems. Cannot understand why it is freezing at 0% on the laptop, or just saying loading when i try to do via memory card.
Cheers
husky_motox said:
Hi The phone does go into the red/geen/blue boot screen. (will post later what the writing in red states)
Using a 2gig memory card which was formatted using panosonic and is fat32.
Tried different usb then a different laptop (both running windows 7) Tried a fresh download of the rom from HTC using the seriel no on the phone so should be the right one. Tried to run the RUU from both the laptop and renamed on the card. Not sure if its worth trying to put CWM on it?
Click to expand...
Click to collapse
If you are using a computer with Windows 7 on it when you go to run the update utity right click it first then click run as administrator. Sometimes when using Windows 7 this helps.
Edit: Ifyou are trying to flash a Windows Mobile ROM then no CWM would not .ebifit you as it is for Andriod ROMs on the HD2.
T-Macgnolia said:
If you are using a computer with Windows 7 on it when you go to run the update utity right click it first then click run as administrator. Sometimes when using Windows 7 this helps.
Edit: Ifyou are trying to flash a Windows Mobile ROM then no CWM would not .ebifit you as it is for Andriod ROMs on the HD2.
Click to expand...
Click to collapse
Same with MAGLDR.
MAGLDR and CWM are ONLY for WP7 and Android.
Reflash HSPL , install the radio you named in the OP, then try a custom win6.5 rom such as Energyrom.....
Yea I understand, but when the standard rom would not run, tried a few android roms as well.
Now have managed to install the HTC rom from the sd card, but on reboot sticks at the white htc screen. Not sure if its maybe a battery issue. So am waiting for a wall charger to be delivered.
husky_motox said:
Yea I understand, but when the standard rom would not run, tried a few android roms as well.
Now have managed to install the HTC rom from the sd card, but on reboot sticks at the white htc screen. Not sure if its maybe a battery issue. So am waiting for a wall charger to be delivered.
Click to expand...
Click to collapse
Make sure you have a current radio version and not a older version. The most current radio version is 2.15.50.14, and you can download it here. It flashes just like a ROM either via computer and USB cable or SD card, exactly the same as flashing a ROM.
you may have a nand memory corruption. The phone should have been capable of reflashing itself if you can get to the bootloader and use a proper stock rom. If your phone either fails to flash or flash completely but gets stuck on next reboot, you can have some corrupted memory sectors. The phone will be able to write on them but the information can't be read, therefore the phone will lock up. Think of them like bad sectors on a hard disk drive. I had these sort of problems with some older HTC's and Eten's, in some case you could eventually flash them but however you will still experience some problems or errors. In other cases it will simply fail on every flash attempt or at the boot screen. I only managed to fix these by connecting the board to a JTAG interface and marking those sectors as "bad" then reflashing the phone after i run a special version of bootloader directly from ram memory, line by line.
I also saw these problems on boards with problems in the cpu area (bad soldering, mechanical shocks etc).
I hope that's not the case with you, maybe you simply have some logical problems with the internal memory or the spl area.
Cheers, thinking of sending it for repair, now ran out of ideas. Installed the latest rom from HTC, it said everything from radio to wallpaper had installed correctly, but still will not get past the white screen with the HTC logo.
you can try another last thing. place a stock rom onto the memory card, place the card in the phone then place the phone in a transparent bag and put it in the refrigerator. Wait for about 1 hour, then... with the phone still in the refrigerator area, start it (don't remove it from the bag) in bootloader mode to flash it from the microsd card. Wait untill the process completes, then at the first restart when the phone is displaying the logo, quickly open the bag, remove the battery, then leave the phone & battery separate, in the bag for another hour in the refrigerator. After all this, remove them from the refrigerator and try to normally start the phone while it's still cold. If this doesn't work, then i'm afraid you have 80% chances of hardware NAND memory corruption/damage.
If this works, then you have a problem with the qualcomm chipset, it's pretty known, the BGA soldering between the chip and motherboard got damaged by excesive heat produced by the CPU and now some connections are not making proper electrical contact, thus producing errors in the cpu's normal operation. If the phone is very cold, the cpu and soldering will contract, thus giving the BGA matrix a chance to remake those electric contacts, for the moment - untill it heats up again.
The 2 problems can be related to each other. First, a CPU that works improperly (due to BGA failure) can disrupt I/O operation on the nand memory chip. Overtime this could lead to a situation where some memory blocks are destroyed due to improper handling by the qualcomm chipset and although the memory chip reports a number of blocks available for writing when you flash the device, some of these blocks are unaccesable when reading back. Somehow, if this is the case here, these blocks must be marked as damaged, so the memory chip's controller doesn't report them back as available and prevent them from being used anymore. I don't know how this can be done in HD2 as i don't have the hardware datasheet for either the qualcomm chipset or the memory chip itself. Like i've said, it was possible on some older devices by disassembling and directly connecting the cpu to a jtag bridge, as i could figure out how the cpu works from the original aplication notes and datasheets from samsung.
Thanks for that, my wife stuck it into a shop when I was out. (she is sick of me messing on with it)
They have told her it is only a software issue, not sure they know what they are doing.
If they do not fix it I will try this method.
Cheers
Related
Hi all,
This is my first post in this forum. Just got my HD2 yesterday & immediately set about installing a new ROM. I installed HSPL without any issues, but I'm having problems installing a new ROM. I've downloaded a couple in .exe format, synced up the phone to WMDC in Win 7, then when I start the exe file everythings fine until it starts to install, then the 4 colurs come on to the phone, and then the USB connection drops so WMDC isn't connected, then I get the error 266 (or 226). I used to have a touch diamond that did this, but I can't remember how you get the connection to remain whilst uploading the new ROM. I've had a look through the forum, but can't find the answer. Can anyone give me some ideas?? Does the phone need to have certain settings applied to it before flashing?? I'm not exactly a noob to flashing ROM's, but can't work this one out!! Thanks all.
just extract the exe, rename *.nbh to LEOIMG.nbh, put in ur microSD root, enter bootloader, press power button when u asked to do so. soft-reset when complete. feel free to pm me n i will guide u.
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
EddyOS said:
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
Click to expand...
Click to collapse
Hi, I'm using the same OS. I've tried running as admin but it still drops connection. The SPL is 1.42.HSPL. It just starts the update, then I see the phone disappear from the connected devices, then WMDC shuts down & a few seconds later the error message comes up??
you started flashing this fast only after one day of use
You don't need WMDC open - just close it once it says you're connected
The run the file and it should work.
As mentioned, why are you flashing it out the box? It's always best to get to know the device as it might just work as it is...perhaps try a stock ROM if you're not already using the newest one and go from there
EddyOS said:
SD card method is the quickest way to brick your phone...
Click to expand...
Click to collapse
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
samsamuel said:
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
Click to expand...
Click to collapse
Didn't know that, glad I have HSPL on my phone now!! lol
lots don't and that's what makes sd flashing dodgy. in the case of 1.6 it can be downgraded with a 1.4 spl stock rom.its just a pain. but 2.0 spl can't. check out the horror stories in my sig.
Yeah read about them, I nearly bricked my phone using the SD card method the first time I flashed but luckily the WMDC flash with my stock ROM got me back to normal!
I was trying to flash the stock 1.66 ROM, but it still disconnected. I have 1.43.206.4 WWE at the moment. The reason for flashing straight away, is usually the stock ROM updates are to improve / fix previous issues. This is why I wanted to start with a stock ROM & maybe move onto a cooked ROM at a later date. Does it make any difference when starting from an .exe file instead of RUU? Do you have to change something on the phone itself to allow it to stay connected?? cheers everyone for your comments.
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
samsamuel said:
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
Click to expand...
Click to collapse
Just tried it again & still no joy. It starts, the phones switches off, thats when it loses connection, then the bootloader appears, then about 10 secounds later it says error 266 connection lost. Still stumped???
Sounds like the device isn't reconnecting with the PC once in the bootloader - try another one...
with the phone in boot loader unplug the usb and plug back into a different port. preferably a port directly on the motherboard (round the back) not through a usb hub or slot in the case.
Sussed it now. I'm a mac user using Win7 using VMware fusion. I think it was this that was causing it to not detect the phone once it had started flashing the ROM. I tried it on my work laptop running XP & voila, it flashed immediately. Thanks everyone for your comments - no doubt I'll be posting a few more questions soon!!!
ah good stuff.
todays lesson ? put all the system info in the first post!
clemo71 said:
Sussed it now. I'm a mac user using Win7 using VMware fusion.
Click to expand...
Click to collapse
Ahhh... yes, that's the kind of non-standard setup that would make sense mentioning right away indeed. Everything that touches hardware level is rarely friendly to emulation, virtual machines, resource sharing and so on...
1st lesson - use a PC!!! POW!! lol
Ok.....next question. I've tried to flash a rom using the customruu file, but all it does is open up the contents of that file. I'm using XP Pro. Any ideas why anyone???
Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Edit: i can now connect my phone to the pc i'm trying to update to 2.13.531.1 but i got to 8% but the update froze there and the phone currently has no image version. I'm using windows 7 ultimate and ive tried to run as administrator and with xp service pack 3 compatibility.
thatg said:
Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Click to expand...
Click to collapse
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
can someone also help me figure out how to get the ruu.nbh file off this rom and how big it should be so i can try to flash it from the sd card. thanks
http://forum.xda-developers.com/showthread.php?t=681030
zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone
thatg said:
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone
Click to expand...
Click to collapse
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom
zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
+1 or flash the phone then task 29 it.
Sent from my HTC Desire using XDA App
zelendel said:
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom
Click to expand...
Click to collapse
no i have not run hard spl so i can only install a stock rom a suppose. the exe gets stuck at 8%, i have no idea where the right nbh file is. i read somewhere when you run the exe it installs the nbh in a temp folder but im not sure i found the right one. ive also downloaded task29 and tried to run as admin but it doesnt do anything just goes to the htc install screen and stays at 0% Getting frustrating it was working fine actually before i tried to install the new tmobile software update. ive read that task29 gets rid of extra leftovers of other roms and might help the exe finish up on the phone and get past that 8% wall but it doesnt seem to be working for me
right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.
samsamuel said:
right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.
Click to expand...
Click to collapse
lol thank you for the words of encouragement, so i've extracted the .nbh file its 268mb, renamed it to leoimg.nbh tried the update from the sd card and it fails at the radio says, update terminated, update FAIL. any idea where to go from here?
Edit: i've run hspl3 on the phone is boot loader mode and have also run task29 from doloop but still get the same error with the tmobile file. 8% using the exe and FAIL trying to flash from the sd card
heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?
samsamuel said:
heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?
Click to expand...
Click to collapse
The first exe file, which got to 8 percent then went red and failed was
T-Mobile_HD2_MR_Software_2.13.531.1
After hspl3 and using task29 i tried flashing this exe which gets to 99% and fails
RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15.29.50.07U_2.06.50.04_TeleNav-5.5.42
that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl
samsamuel said:
that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl
Click to expand...
Click to collapse
i tried flashing using the .exe method in bootloader mode. next to spl it reads -2.08.hspl 8g XE
it now says
Upgrade ROM code error
ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.
samsamuel said:
ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.
Click to expand...
Click to collapse
Which do you suggest, i bought the phone so that i could ultimately install android on it. but it seems i'd be lucky to even have wm running on the thing
Edit. just tried kumars classic rom, renamed to leoimg tried running off the sd card, The update finishes successfully but after i hit the reset button on the back of the phone i just see the tmobile stick together logo and the phone doesnt boot. Do a lot of people struggle with the hd2s or do i just have a bad example here?
well unfortunately i think you may have a dud. its the radio that is preventing it from booting.
it could be the radio from that test rom, it could be something else (but still the radio)
options...
its still under warranty, speak to t mobile and/or htc, but don't mention flashing and be sure to remove hspl if you do send it back. (run hspl3, choose 2.08.0000, that's stock)
or
look on here for a user called xmoo, he knows a lot about this sort of problem, (im just good with regular flashing issues)
im having the same issue so if you believe its the radio will installing different radio maybe fix the problem?
i;ve tried installing a new radio from the sd card. it goes red and fails
It sounds like a hardware issue at this point. I'm willing to bet you fried something when you pulled the battery in the middle of the master reset.
Hope thats something htc will cover. Phones on its way over
I'm trying to reflash the stock WM ROM on my Vogue, but I keep getting Error 260 in the RUU. My phone is currently on an Android ROM (the latest Incubus26Jc's Super FroYo, which I installed yesterday) but I should note that the sdcard wasn't being read by Android, and my phone can't mount to be viewed on my computer.
How can I revert back to the stock ROM now?
Thanks for any help.
biomech91 said:
I'm trying to reflash the stock WM ROM on my Vogue, but I keep getting Error 260 in the RUU. My phone is currently on an Android ROM (the latest Incubus26Jc's Super FroYo, which I installed yesterday) but I should note that the sdcard wasn't being read by Android, and my phone can't mount to be viewed on my computer.
How can I revert back to the stock ROM now?
Thanks for any help.
Click to expand...
Click to collapse
Error 260 is a connection error (sorry for being so obvious). Can you post the exact steps that you are following to flash?
Haha yeah, I know it's a connection error. I've done many flashes so it's weird that it doesn't work anymore.
I press the power+camera+reset buttons to go into the tri-colour screen, plug in the phone to my computer, run the stock Bell RUU and then get the error.
Tried this at least 5 times now, restarted my computer a few times, tried different USB ports. No luck. =/
biomech91 said:
Haha yeah, I know it's a connection error. I've done many flashes so it's weird that it doesn't work anymore.
I press the power+camera+reset buttons to go into the tri-colour screen, plug in the phone to my computer, run the stock Bell RUU and then get the error.
Tried this at least 5 times now, restarted my computer a few times, tried different USB ports. No luck. =/
Click to expand...
Click to collapse
I had to ask since I needed to make sure that you were doing the right thing . You mentioned also that Android is not picking up your SD card. Try to put a nbh rom file in the root of your card (hopefully 2 GB or less), stick it in the phone and reboot into bootloader. The device should pick it up and try to flash from SD. If this doesn't work, then I am afraid that you may have a bad board in your phone.
egzthunder1 said:
I had to ask since I needed to make sure that you were doing the right thing . You mentioned also that Android is not picking up your SD card. Try to put a nbh rom file in the root of your card (hopefully 2 GB or less), stick it in the phone and reboot into bootloader. The device should pick it up and try to flash from SD. If this doesn't work, then I am afraid that you may have a bad board in your phone.
Click to expand...
Click to collapse
Ah, the thing is that the 512mb card that came with my phone stopped working the other day, so I've been using an 8gb one instead, and I'm too far from any computer store to go and buy a smaller one.
I did try the .nbh trick but I'm guessing the phone wasn't reading the card.
biomech91 said:
Ah, the thing is that the 512mb card that came with my phone stopped working the other day, so I've been using an 8gb one instead, and I'm too far from any computer store to go and buy a smaller one.
I did try the .nbh trick but I'm guessing the phone wasn't reading the card.
Click to expand...
Click to collapse
Try to get a 1 or 2 GB and see if that works. If it doesn't.... I think your phone may be toast...
Okay, I'll try that as soon as I can. Really appreciate the help! Thanks.
biomech91 said:
Okay, I'll try that as soon as I can. Really appreciate the help! Thanks.
Click to expand...
Click to collapse
No problem and good luck!
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.
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)