Hey, I just tried to install DCD's newest ROM and it looks as if i may of bricked my phone. When i connect it to my PC, Active Sync will not even pick it up. this happened right after i ran Hard-SPL-MFG to unlock the phone... I did try and run the titan_exitbl but no luck. I also attempted to run the relocker but i would not even run.. any ideas?
thanks!
recover from flash
Are you at the 3 color screen? If so you need to unplug the USB and replug it again as per the instructions. You MUST follow the instructions EXACTLY or your flashing will be very scary experience.
If you are not at the 3 color screen, you need to get back to the bootloader by pressing power+camera and soft reset. This will get you to the 3 color screen. Then have a look at the version of bootloader you have. If it doesnt say Olipro 1.20 or 2.40 you still have the locked bootloader and you can flash a stock carrier rom. If you have 2.40 you can flash to the 3.16+ rom and then flash the new radio this way or via sd card install which will be more painless and less scary.
If you dont know what an sd card flash is, I would search the forums here. Over at ppcgeeks you can look up imcokeman's posts and see instructions how to do a sd flash.
If you are are real noob, I would suggest staying with non gps roms at this stage because the change of radio rom needed to enable you to flash a gps rom will almost certainly lead to sleepless nights wondering if you have bricked your machine.
Most important thing to realise is that the machine is almost certainly not bricked. But you might have a few more scary moments before you get your machine back working again. You might also need to call your carriers service desk a number of times to get your provisioning data back working.
Check all the way through these two posts and dont sweat too much. With effort you will get your machine back. The answer to your problems is listed in one of these threads, but you need to dig a fair bit to find it. The posts contain lots of problems that people had flashing this rom, and I am sure your exact problem was there and solved. Its I believe somewhere in the second link I have listed here.
Good luck. i feel for you.
http://forum.xda-developers.com/showthread.php?t=371314
http://forum.xda-developers.com/showthread.php?t=362566 particularly this bit http://forum.xda-developers.com/showpost.php?p=1856032&postcount=216
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
optyhtp said:
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
Click to expand...
Click to collapse
It doesn't need to active sync. Once it switches to USB you are ready to flash.
Stuck at Verizon Screen/HTC Mobilty Screen
If you are stuck at the VZW screen then you have only flashed one of the two essential parts. You need both (ROM and RADIO) to make it work. 3.16+ ROM will not work with the old radio. You need 3.27 radio.
Use the camera+power+soft reset and you can flash the one (new radio or new ROM) that you are missing.
See dcd's thread about the 2.3.2 rom. He has added a HUGE new disclaimer.
http://forum.xda-developers.com/showpost.php?p=1952956&postcount=1
Well nothing really worked so i used a sd card to flash back to the stock verizon ROM, i then attempted it again and got it all working!!!
Related
So after having my Mogul for quite sometime, I figured it was time to upgrade the ROM which includes the GPS, etc etc. I followed all the instructions to the "t" and when I go to update it, the phone goes to the tri-color and says "USB" at the bottom...but on my computer, it stays stuck at 0%.
I've left it go for almost 30 minutes. I end up having to shut down the update and reboot my phone. Luckily my phone wasn't affected at all. (whew!) I've tried this three times and all end up being stuck.
I'm new to all this, so ANY help would be greatly appreciated. I've searched for this same occurrence but have not read about any resolutions to the problem.
Thanks for any help!
Anyone have any suggestions?
Right now I have ROM version: 2.09651.3
I have downloaded a ROM for the Quest 'version' of the Mogul which is 3.35.656.2....will this work?
I dont get why it wont update and install the ROM.
Any help is greatly appreciated!
what version of bootloader are you using?
if its not giving you an error try letting it go overnight. Maybe its just going REAL slow.
Other than that, try one of the intermediate ROMs first, or try re-downloading the ROM and going from that.
The process is pretty simple, sync, backup anything important, establish activesync/MWDC connection, run the RUU, press yes several times, restore backup/resync.
Did you ever unlock the phone? The sprint ROMs wont load with an unlocked phone, AFAIK.
not sure what you mean by version of bootloader....
As far as running reall slow, not sure, I might try that if nothing else works.
I'm going to try the 3.35 ROM and see if that works. So stupid that it is such an easy task, yet it doesnt work....and I never "unlocked" the phone...its basically factory straight from Sprint. Again, it was bought back in December 2007 so the ROM on it is pretty 'dated'
I'll let ya know what happens...
2.09... lol.
that rom was slooow. screen flickered.
lockups.
your problem is that you cannot use a rom from a different carrier unless you unlock first. Just get the latest sprint rom and flash it.
edit: perhaps i read your post wrong. do you have the sprint or qwest rom? the qwest rom will not work. the sprint rom should work fine providing the phone has not been unlocked with olipro 1.2. Check the bootloader version when in the tri color screen. if it says olipro 1.2 then you need to update to 2.4.
If it's stock then you should be good. you could try putting the phone into bootloader before running the ruu. sometimes this helps the connection since it doesn't mess with activsync. to get to bootloader hold power + camera and hit the reset button.
First off, I've been flashing my phone for almost a year now. So I don't consider myself too big of a noob. I loaded scrosler's round 4 rom. Worked great! Until I did a soft reset. It put the phone in bootloader mode and I can't boot up at all.
Here's what I have:
Olipro SPL 2.40
Radio 3.42.50
Here's what I've tried to get it out of bootloader:
mtty1.42.exe
titan_exitbl.exe
No success. I'm able to install a ROM, but as soon as it reboots after 100%, it goes right back into bootloader.
Someone please tell me it's not bricked
Try reflashing your radio.
BTC
kill the active sync processes via the task manager, then put the phone back into the usb cradle, run the titan exit bootloader and it should work.
josh77b said:
First off, I've been flashing my phone for almost a year now. So I don't consider myself too big of a noob. I loaded scrosler's round 4 rom. Worked great! Until I did a soft reset. It put the phone in bootloader mode and I can't boot up at all.
Here's what I have:
Olipro SPL 2.40
Radio 3.42.50
Here's what I've tried to get it out of bootloader:
mtty1.42.exe
titan_exitbl.exe
No success. I'm able to install a ROM, but as soon as it reboots after 100%, it goes right back into bootloader.
Someone please tell me it's not bricked
Click to expand...
Click to collapse
If no other suggestion works this will... But it sucks.... Flash a stock rom. I garuntee that will fix the problem. then just flash back. You don't have to flash a VZW ROM and I recommend against it. My new recommended ROM for unlocking and flashing is the Alltel ROM. Its got the latest radio in it (which you already have). Good luck and let us know how it turns out.
thanks for all the suggestions. i'm not sure what exactly went wrong, but i spent about a day and a half just to get it working again. it's somewhat stable now.
after flashing an older dcd rom, i was somehow able to get the OS to boot up, even after the auto soft reset. immediately i wanted to upgrade the bootloader to 2.47 since i've only found it in an exe(only can run from windows mobile) version. I then was able to flash the OEM MR1. Which automatically downgraded my radio. it was definitely the most stable thing i've flashed since the phone got all screwed up. i could soft reset as much as i wanted and didn't get the blue screen of death aka bootloader.
but of course, i couldn't be satisfied with no gps and no internet sharing. i use internet sharing more since i use it when i commute to work on BART (bay area's version of the subway) 50 min each way.
so now i'm on DCD's 3.2.6 ROM with 3.42.50 radio. so far it's somewhat stable. if i soft reset, i get the bootloader sometimes. but a couple solutions to the get the OS to boot back up is
1.) take the battery out for 20-30 seconds and power up
or
2.) take the battery out, plug in the computer usb or power usb with the battery still out. somehow resets the phone? i have no idea.
but i read somewhere that ROM's were causing people to have to take their battery out for 30 seconds to boot up. I doubt it was DCD's ROM's. But who knows, maybe i ran a bad radio file, ROM, or bootloader upgrade, that really caused the initial issues.
My only issue now other than getting the bootloader once in a while is that GPS isn't working. Not that big of a deal for now since I have the Pioneer AVIC F90BT in my car now. but would be nice to have it on my phone (tomtom & google maps) for that one time that might come up when i really need it and i'm not in my car.
again thanks for your help in trying to help a brotha out.
Verizon xv6800 bootloader and startup issues
My issues are, I cant get into the bootloader screen no matter what I try(power, camera and reset). Most times my phone will only go to the verizon screen and then just go white, other times, it may show the WM 6.5 startup screen and the freeze there. This all came from me trying to install WM 6,5 Beta 5 21159 rom from WM 6.1. On another not, my pc will not see my phone. So am I completely screwed? Is there any hope? Thanks in advance for any help.
So, overall, am I screwed?
Anybody have any suggestions?
Thanks
Can anyone help? my phone will not let me into bootloader mode or even startup past the verizon splash screen. I am desperately hoping that its not bricked. Also, the pc to phone usb connection will not see eachother.
My phone will charge via the usb cable to pc. When the wifi switch is turned on, the led on opposite side of the power led will do it green blinking.
Is there anyone that has time and is willing to work with me?
Thanks in advanced.
I have taken the phone apart so that I could push the internal buttons (power, camera and reset) to see if the outer shell buttons were the problem. They werent. I also still can't get past the verizon splash screen. Anyone have any ideas?
Thanks
I you cant get into bootloader you dont have any options.
I recently flashed to the new AT&T Test ROM 5.08. Basically I want to flash an energy rom over the AT&T and am having issues. Any rom I try to flash will go the gray loading screen on the phone and then hang up and gives the error 260 connection lost. I tried running the Raphael custom RUU before flashing the energy rom and I get an error 240 trying to run the custom ruu. I tried running the raphael unsigned hardspl and that only takes me to the black screen. From the black screen I've tried running the custom ruu and energy rom and nothing happens. Can anyone help me because I'm tired of this rom and I can't get anywhere!
Power off your device, hold the Volume Down button (keep hodling it), turn the device back on.
You should see the TriColor BootLoader screen; it should halt with USB or SERIAL displayed on the bottom white portion of the screen. Note the information that appears on the screen and post the details. To return to normal device operation, remove the battery for 30 seconds and put it back in.
That should assist us in determining the next steps.
HTH,
Screen appears:
RAPH110
SPL-5.08.0000
PSOC-Raph STAGE-CVT V0x36
PCBID 0x00
RID 0x0
Serial
It would appear that the HardSPL did not "take" or hasn't been applied yet. Here's the link to the HardSPL thread and Wiki page:
http://forum.xda-developers.com/showthread.php?t=410150
http://wiki.xda-developers.com/index.php?pagename=Raphael_HardSPL
Once the HardSPL is applied, you should be able to flash custom ROM's to your device. If you need a "refresher" on flashing, have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=448008
Lastly, although optional, you may want to consider performing a SIM unlock.
HTH,
It freezes the phone on the gray loading screen when trying to hardspl and then gives the 260 error code connection lost. I followed all the guides and nothing works (hence the point of starting the thread in the first place). I am a noob, but not a complete idiot that can't read guides. I understand if I can't hardspl, then I can't flash a rom. Well the hardspl does not work for me! I have tried the unsigned version which freezes the phone loses connection. I've tried the raphael wrapper which only takes me to the black screen and gives the error 240. From the black screen I cannot run spl or roms. I tried running stock spl's. I don't understand how the Test ROM flashed fine and now I can't flash anything.
The test rom worked fine because you don't need hard spl to flash it; it matched the carried id of your phone (CID). Hard spl CID-unlocks your phone, so you can flash non-ATT roms.
You should never try to flash a custom rom without hard spl. In the best case scenario, you'll be stonewalled. You need to use the wrapper that comes with the hard spl package to flash hard spl. Using any other wrapper is a waste of time. It says this clearly in the hard spl thread, where you should have posted your question. If you read the last 50 or so posts of that thread, you'll come across a post by Captain Throwback. He had some problems flashing H-spl, and he found some tricks to get it going. I suggest that you search the thread for his how-to. My guess is that you're forgetting something obvious, like turning off your anti-virus software or installing net framework 3.5 on your pc (if it isn't already there). You have to flash hard spl off of your pc, so don't even bother trying to flash it off your sd card. It's probably easier to do it off of XP than Vista.
I already tried the raphael wrapper as I stated twice. Raphael wrapper takes me to the black screen (where I read about the post by captain throwback). I followed everyones instructions that got it to work and still the same thing happens. The Wrapper only takes me to the black screen where I cannot do anything because the computer isn't synced with my Fuze and will not. Then the error 260 message comes up saying that there is no connection. Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
I already tried the raphael wrapper as I stated twice. Raphael wrapper takes me to the black screen (where I read about the post by captain throwback). I followed everyones instructions that got it to work and still the same thing happens. The Wrapper only takes me to the black screen where I cannot do anything because the computer isn't synced with my Fuze and will not. Then the error 260 message comes up saying that there is no connection. Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
Few questions:
1) Under usual conditions, does the device establish a connection via ActiveSync?
2) Does the problem occur in a new user profile /w Admin priviledges on your XP workstation where you establish a Guest connection via ActiveSync to the device?
3) Have you tried a Hard Reset on your device prior to flashing HardSPL?
4) Have you removed the SIM and any SD Card for the time being?
5) Are you able to successfully flash a non-test version of an official AT&T ROM to your device?
1. Yes alot. Only use it for transferring files and battery charging.
2. No, registered device in activesync with full administrative rights to my workstation. I don't have any problems with losing connection during file transfer, etc.
3. Yes, did a hard reset a couple weeks ago and same thing. Possibly going to try it today again because I installed a couple programs before attempting hardspl the last time.
4. I take them out when trying to flash
5. No, I'm stuck with the AT&T Test ROM. Have tried ones on here that are supposed to be stock AT&T ROMs and the same thing happens.
Your response to #5 concerns me; just to make sure I understand ... you are unable to flash an official ROM to your device?
Here's the link to the latest official AT&T FUZE ROM:
http://www.htc.com/us/SupportDownload.aspx?p_id=198&cat=2&dl_id=553
Springboard URL: http://www.wireless.att.com/answer-center/main.jsp?t=solutionTab&solutionId=KB95876
Download the ROM and try flashing it to your device; if it fails ... time to call AT&T, you have a problem with your device.
HTH,
bratch15 said:
Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
Click to expand...
Click to collapse
Is there a net framework 3.7 for pc's? Or are you talking about your phone? You need net framework 3.5 on your pc to run the flash. It won't work with 2.0. It doesn't matter which compact framework you have on the phone.
Did you already try putting your phone in Bootloader mode, and then connecting it to your PC? Does it load the Qualcomm CDMA Technologies/HTC/Pocket PC USB Sync driver? Did you make sure the SIM and SD cards were removed from your device? FYI - You HAVE to use the RUU that comes with HardSPL in order for it to flash successfully. If you've verified that your computer has installed the drivers, and then been unable to successfully complete HardSPL, I'm not sure what to tell you. Do you press "yes" on the Device when running the HardSPL RUU & you're prompted to run the program?
Those are all the suggestions I have.
Last night as I was driving home my phone kept disconnecting as it was charging. I finally found the answer! First time it ever did that. So its back to AT&T for a new one. Probably should have mentioned that the phone was submerged in the toilet (thank god before the #2) a couple months ago. The phone went crazy and started saying error messages with email and then lines going thru it. But after a couple days of drying it worked fine again.
THREAD CLOSED!!!!!
Always wanted to say that
bratch15 said:
THREAD CLOSED!!!!!
Click to expand...
Click to collapse
If you say so...
I've been searching on how to completely restore my (T-Mobile) HD2 on this forum for a while and haven't came to it, so sorry if I'm repeating any threads.
Basically I'm fairly novice in flashing and things in that nature. I've been flashing updating Energy ROMs on my HD2 for about six months since I got the phone. Which was fairly simple to do. Since WP7 ROMs, I've switched over to flashing those. The problem is that 99%, it'll flash fine, then won't get past the boot screen. And on the rare occasion it does get past it, I can't turn it off, or else I'll have to trying getting past the screen 1000 more times to be successful. I think I have all the requirements to run WP7, but not exactly sure.
So I would like to know what to download and flash/ install for it to be as if I bought this from T-Mobile today.
Thanks!
I need help with this too..I craked my screen and am going to send it to t-Mobile so they can send me a new one, but I want to put it to factory reset. Ive looked all over cant find them...the post a couple up...links are dead
you do realize that if you cracked your screen your warranty is already void. it doesn't matter what software you are running at this point.
diazjohn said:
you do realize that if you cracked your screen your warranty is already void. it doesn't matter what software you are running at this point.
Click to expand...
Click to collapse
Maybe they have the insurance feature?
Late answer, but go herehttp://www.t-mobile.com/wmupgrade/ to get stock ROM.
follow steps here http://forum.xda-developers.com/showthread.php?t=623402
your done.
how_weird said:
Late answer, but go herehttp://www.t-mobile.com/wmupgrade/ to get stock ROM.
follow steps here http://forum.xda-developers.com/showthread.php?t=623402
your done.
Click to expand...
Click to collapse
Sorry for MY late reply, but I put this phone away for a while and now my dad wants to use it. I've gone though the steps, but I can't get past "6. Hold the volume down key and power on your phone. As soon as the coloured screen changes to grey, RELEASE volume down." It never turns grey. I'm one step from taking this phone and throwing it out my window to see it shatter.
art0605 said:
I've been searching on how to completely restore my (T-Mobile) HD2 on this forum for a while and haven't came to it, so sorry if I'm repeating any threads.
Basically I'm fairly novice in flashing and things in that nature. I've been flashing updating Energy ROMs on my HD2 for about six months since I got the phone. Which was fairly simple to do. Since WP7 ROMs, I've switched over to flashing those. The problem is that 99%, it'll flash fine, then won't get past the boot screen. And on the rare occasion it does get past it, I can't turn it off, or else I'll have to trying getting past the screen 1000 more times to be successful. I think I have all the requirements to run WP7, but not exactly sure.
So I would like to know what to download and flash/ install for it to be as if I bought this from T-Mobile today.
Thanks!
Click to expand...
Click to collapse
I have done a dozen of flashings on my Tmobile HD2 and works fine so far. Thanks to XDA forum all the tools I need are available right here on XDA !!! You just to search them out yourself (sorry I don't have the links ....... ).
I suppose you know how to flash your phone so I will not explain details how to do it.
In brief, to install WP7 this is what I suggest you should do -
1. Update flash radio to the latest available update from Tmobile US website, regardless of what ROM you have at present (version 2.15.50.14 is the latest, I think).
2. Flash HSPL 2.08 to your phone to maximize 576 RAM usage, if you have it (do not use SPL 2.08.000 as this will recognize only 448 RAM size).
2. Use Task29 to clean out the existing the existing ROM on your phone (this will erase your OS and you will only be booting on the white HTC logo screen). This will clear out those ROM leftovers on your phone.
3. Flash magdlr 1.12 or 1.13 on your phone (press power button on boot to show magdlr menu).
4. On magdlr menu scroll down to no.5 USB flasher, connect your phone to pc and run dwi.exe on your WP7 installer and wait till installation has completed.
I have done these procedures a dozen times already I have not encountered problems so far. I have been flashing and flashing to choose the best ROM (WP7 or WM6.5.x) I want. On personal note, I think I would settle for WM6.5.x cooked ROMs because of usability and handiness (I find WP7 too complicated to deal in terms of tweaks and handling of personal videos/photos file security).
Some notes:
a. You need to flash radio and HSPL only once.
b. Use Task29 every time you need to install a new ROM (your choice, but recommended).
c. After Task29 you can start out clean and flash to stock ROM or any other rom you choose.
d. There are dozens of videos on YouTube to help you flash but I have not seen one using Task29 to start the process of flashing.
This works for me, hope it does to you as well. Good luck !!!
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App