Related
after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!
......
noone?????
The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)
Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...
Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .
i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck
There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL
It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?
another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL
When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.
I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.
The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!
Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.
It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.
Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."
The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!
Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.
hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
trexxcrap2 said:
hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
What are you trying to update it to?
secano said:
What are you trying to update it to?
Click to expand...
Click to collapse
the new update that came out a few days ago....
trexxcrap2 said:
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
Click to expand...
Click to collapse
Here is a link to the error codes. Your error means you need to go back to SSPL before you can flash that ROM.
trexxcrap2 said:
i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
Here is a link to my tutorial on how to flash via SD card.
i am having the same issue each time i attempt to update my rom. error 260.
jenelson said:
i am having the same issue each time i attempt to update my rom. error 260.
Click to expand...
Click to collapse
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
I don't know if you are totally new to flashing ROMs or not, since you didn't say and your post indicator said that was your first post here, but I would advise you to be very, very careful. In the early days (last month, actually) a TON of people were bricking their phones because they accidentally downloaded the European ROMs for the 512Leo. Ours is the 1024Leo and only ROMs designed for our phones will work.
The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.
same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.
nyaznteen said:
same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.
Click to expand...
Click to collapse
I encountered the same problem and it appeared that my computer was slow in "re-recognizing" the phone. For some reason, it had to reinstall drivers before continuing with the update. After the device was again recognized, I restartde the update (without disconnecting the phone) and it continued without issue.
I had been worried that the phone had become a paperweight when I saw the tricolor screen, but everything has been fine and the upgrade appears to have worked correctly.
jenelson said:
The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.
Click to expand...
Click to collapse
Think of HSPL as your BIOS (it isn't, but it may help you to think of it as such). You don't have any control over the options, but you need it to load or install your OS. Installing HSPL is simply a matter of following the directions in the link that I posted last time: http://forum.xda-developers.com/showthread.php?t=653614
Once you have HSPL installed, you should be able to "flash" any ROM. Of course, this also allows you to flash ROMs that are not meant for your phone, so that's the danger behind it.
When you visit a thread that offers a ROM, it should either have instructions or a link to instructions on how to install. If it does not, a google search for "xda how to install a custom rom" should give you a million helpful links. (This is actually beyond the scope of this post so I won't go into details)
Hope this helped some...
Same problem but i have hspl?
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!
mumbles85 said:
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!
Click to expand...
Click to collapse
just for kicks did you try a different ROM, find another ROM that is Compatible and try it, not saying there is anything wrong with Dutty's , but could just be the download , but not sure since you tried stock too ...
You may need to reinstall HSPL3, if you tried to flash a stock rom, and even if it failed it could have removed HSPL ...
Also try plugging the USB cable into the back of the machine
error 260 1024hd2
Hey guys,
I am having the same issue although I may know the answer but not sure how to fix it. Prior to flashing chuckyRom, I installed HSPL but I don't think I installed the correct version (still worked). So does anyone think this entire problem is attributed to initially installing the wrong hard SPL. If so, how can this be fixed? android is running great on chuckyRom but it would be nice to use a rom that is used for more than running android.
Please help, I have been in misery trying to solve this for over two weeks now.
Error 260, T-mobile HD2
Error 260 during ROM update
I had the same problem and tried everything (?)
Finally I got it work.
After I started the update the first time, I got the message, driver was not installed successfuly ...blabla
I ignored the message, tried and the connection disconnected every time again.
At the end I used another usb port and it asked me to download the CDMA driver. After download and installation, the update was in 5 min. done
Snarksneeze said:
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
Click to expand...
Click to collapse
He was trying to install the OEM rom. I'm doing the same and have the same issues.
Error 260 on Htc Hd2 running windows mobile 7
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?
Dizzle88 said:
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?
Click to expand...
Click to collapse
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.
Error 260 connection in HTC HD2
Dear all;
i have this problem in windows 7 each time i connect my phone with pc it gave me error 260 , so when i connect the usb cable i choose the first choice sync not the default one storage and it worked for me .
Ahmed Hosni
thanks for the note
fred_up said:
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.
Click to expand...
Click to collapse
First time flashing the radio and kept getting error 260 from CustomRUU.
Read so many threads and all say sync the phone with your PC and run CustomRUU. Nobody said to run it under BootLoader Mode.
This simple note helped a lot for a newbie like me.... thanks
Error [260]
Hello
I want to try to update my HD2 from 2.2 to 2.3.x but I always geht thr Connection error.
I´ve flashed my HD2 from Windows Mobile 6 to Android.
I thank you for your help.
Hello, I just decided to finally root my Legend and install a rom.
My phone is currently running 2.1 and i'm on the Virgin Mobile Canada network here in Canada. We don't have an official 2.2 release yet.
I have made a gold card and i'm all ready to root and load a rom. I just don't know what one to do.
I think i'd like to start off fairly basic. just to play with 2.2 then try some of the more advanced custom roms. So, All i really need is help finding the 2.2 stock rom that would be best suited for me?
Sorry if this is sort of a newb thing. but i'm a newb. I tried looking this up, but couldn't get a solid answer via google results. Too many options out there and i didn't know if they applied to my situation.
So, yeah. Just want the basic 2.2 Then maybe i'll try some custom roms later.
Also, if anybody has any advice of what to expect or any other advice, i'd appreciate it. Any features I will loose if i root/rom? I hear FM radio won't work, but i'm not too worried about that. Anything else?
Thank you.
You say "basic ROM", but it's a bit more complicated.
You can simply update your phone to HTC stock ROM 2.2 or the Vodafone ROM 2.2, this would be basic but crappy (slow, branded, buggy roms).
I recommend you to skip these roms and try BlaY0's rom (with sense) or CyanongenMod 6.1 stable. These two are really good work !
So you can play with serious froyo and the time you'll take to root and change the rom would be useful !
Cyanogen will be a bit more "exotic" since HTC sense is not included in the ROM.
For the features, you will not loose any of them, except maybe the FM radio (depends of the rom), but you will get many you have not right now (root of course, overclock,..., plus every changes of 2.2)
Your Legend is about to become a greeaaaaat phone, congratz !
I hope my answer will help you ;-)
PS : Few months and we'll get stable gingerbread roms ! Time to get to Froyo ! ^^
Thanks for the reply. It was very informative and just the type of information i need.
I hate these situations where i know i'm missing a lot of knowlege, but due to not knowing it, i don't know how to aquire it. I hate that.
That's why i'm glad i have this place. Thanks. I think i'll install that CyanongenMod 6.1 stable. I've been using launchers most of the time since i got my phone as i didn't really enjoy sense that much.
Could somebody please link me to the exact file i'd want? I keep finding different versions/builds and they say for different phones, and i just get confused A download link would be great.
Search for rom manager in the market, install and choose Flash Clockwordmod Recovery
After that:
In Paid version just select Download Rom / CyogenMod.
Select Backup current rom & wipe data and cache when installing
In free version 1st d/l CM6.1 from http: // forum.cyanogenmod.com /files/category/29-htc-legend/ and put it on your sdcard, then Select Install Rom from SDcard in Rom manager.
For both also install the google apps (same source locations & method)
gl
So, Upon trying to root my phone i find out i first need to downgrade my phone.
I go through all the steps needed and eventually get to the part where i need to install the new "RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed" file.
I set up my phone. Goldcard, the correct version of HTC sync, USB Debugging, i'm fairly certain i did everything correct. I try to run the RUU and i get errors. Either USB not Connected errors, or and more frequently "Device ID Incorrect" errors.
So, I seem to be unable to downgrade to 1.31. Any advice on how to get by these errors? It's really frustrating.
Thanks.
Try recreating the goldcard and reinstall the latest HTC sync.
I tried re-making the gold card. I have the same problems. Although, I did realize i made a mistake when i made the gold card. But remedying that didn't seem to fix the problem.
When the Serial was reversed it already had the first two digits as zero's so i didn't really have to do that.
As for HTC Sync, I installed the correct version. I could try doing it again.
I'm on Win7 64 bit. I also tried it on a WinXP machine. Same error(s).
I'll try making the gold card again. I'm using a Kingston 2GB microSD card.
I had issues with Win7 x64 too. Your best bet is to find a 32-bit machine for this one-time step, or use VMWare Player to make a temporary virtual machine.
Sent from my Legend using XDA App
I've also tried it on a 32bit winxp machine.
Here is basically how it goes.
Enable Debugging mode.
Hook up via "Charge only"
Run RUU as Administrator
It runs and says "waiting for bootloader" but errors out with the Error 171 USB Connection error.
The phone stays on the black screen that says HTC. Have to take out the battery to reset it.
OR. run the RUU again.
If i do that.
it "clears user data"
then does "sending..."
then "Updating Signature". It gets about 20% done, then errors out.
Error 130 Model ID Error.
Then when i select exit. The phone reboots back to the homescreen.
Which, if i try again, starts the cycle again.
so, it goes. First try, USB error, black htc screen. second try. Model ID error, Re-boot. Repeat.
My sync is the correct version. i've re-installed my HTC drivers. I've tried on a winxp box. and my win7 box. I've re-created my gold card. I even temporarily disabled my firewall and anti-virus in case that was the conflict.
I've done everything. This is really pissing me off at this point.
rooting
FourForty said:
I've also tried it on a 32bit winxp machine.
so, it goes. First try, USB error, black htc screen. second try. Model ID error, Re-boot. Repeat.
My sync is the correct version. i've re-installed my HTC drivers. I've tried on a winxp box. and my win7 box. I've re-created my gold card. I even temporarily disabled my firewall and anti-virus in case that was the conflict.
I've done everything. This is really pissing me off at this point.
Click to expand...
Click to collapse
i had same problem but i solved it by doing this look at my guide
http://forum.xda-developers.com/showthread.php?t=954450
report if it works in that thread if it dosnt post back here and well help, (remember some one will read this thread when they are stuck one day)
Thanks. I posted on that guide with an update to my situation. Sort of stuck at the moment as the custom boot loader after step 2 failed to load and aborted the installation. so now i'm sort of screwed until i figure that out.
I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?
Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.
flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.
Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.
Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.
hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.
Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.
gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.
samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.
@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!
gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.
Hello to all of you guys, i have searched the forum but have not found a similar problem that I currently have in hands, so let me start to explain.
I have an HTC T-Mobile HD2
Model No: PB81120
SPL: 2.10.0000 8G XE
Stock Rom: Never tried to install anything or upgrade
The phone worked fine until some days ago it stopped working and hangs on boot, screen all white with the logo all messed up and stretched.
I did a softreset, an hardreset, i can boot it on Bootloader (the tri-color screen) and it detects usb.
So thinking this behavior was caused by its software I tried to reset it (soft and hard) but with no luck, if i try to install via USB the phone dont pass the 0% (and it shows no logo above the bar, only a white rectangle with some black lines), then I tried boot from the SD (8gb class 4) but it hangs on Loading... screen (searching the other threads i found that maybe I need a higher class card and if possible with only 4 or 2gb).
Running Task29 from toolkit or trying to install something from the USB does the same thing as trying to install the Stock ROM (freezes at 0%).
So my question is, am I doing somthing wrong, or do you guys have a solution for my problem? And sorry for my english.
P.S: If needed i will buy another microSD card.
P.S2: If you have any questions, I will try to answer them the best as I can.
Album
imgur.com/a/kzRMo#0
I continue with the same problem, as I am unable to post direct links in this forum, I put at the end of previous post a link to one album with pictures and screenshots I took from my phone while attempting a recovery, I hope its enough for you guys to understand whats going on.
Primordium said:
I continue with the same problem, as I am unable to post direct links in this forum, I put at the end of previous post a link to one album with pictures and screenshots I took from my phone while attempting a recovery, I hope its enough for you guys to understand whats going on.
Click to expand...
Click to collapse
Based on the second image, it looks like you're trying to re-flash WM6.5 on it, correct? FYI, v3.14.405.2 is not the latest version. I think that v3.14.531.0 is (and the filename is RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship.exe). I suggest looking for that (it's likely in a stickied thread in the WM6.5 sub-forum) and trying it. If that doesn't work, you might try downloading the latest radio and installing that first.
Another idea: could your USB cable be flakey, perhaps? If you have another that you can grab, try that.
If you can't manage to re-install WM6.5, try installing Android or Windows Phone 7 (see the respective sub-forums), instead. This guide can help you do it for Android, if you're interested.
Osprey00 said:
Based on the second screenshot, it looks like you're trying to re-flash WM6.5 on it, correct? FYI, v3.14.405.2 is not the latest version. I think that v3.14.531.0 is (and the filename is RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship.exe). I suggesting looking for that (it's likely in a stickied thread in the WM6.5 sub-forum) and trying it. If that doesn't work, you might try downloading the latest radio and installing that first.
Another idea: could your USB cable be flakey, perhaps? If you have another that you can grab, try that.
If you can't manage to re-install WM6.5, try installing Android or Windows Phone 7 (see the respective sub-forums), instead. This guide can help you do it for Android, if you're interested.
Click to expand...
Click to collapse
Ty for the fast answer, I'm donwloading the ROM right now and later i will update with the results. I cannot install Radio only version because I do not have HSPL installed, and about the USB cable, I'm using it with other devices and it's working fine. (I will try to find another USB meanwhile cable just to be sure).
Update, after downloading the ROM I tried to install it via USB but the strange behavior continues, it does not pass the 0% and after some minutes the setup fails as shown in the album I posted in the first post
I'm not sure what more you can try if you want to keep WM6.5. I suppose that you could try to install HSPL, a new radio and even MagLdr, then try to install the WM6.5 ROM again. If it fails, then just install Android or WP7, I guess. I would just do that, anyways, since WM is dead. I would go with the Android 4.3 (latest version from Google) ROM that's in my signature, but it's up to you.
Osprey00 said:
I'm not sure what more you can try if you want to keep WM6.5. I suppose that you could try to install HSPL, a new radio and even MagLdr, then try to install the WM6.5 ROM again. If it fails, then just install Android or WP7, I guess. I would just do that, anyways, since WM is dead. I would go with the Android 4.3 (latest version from Google) ROM that's in my signature, but it's up to you.
Click to expand...
Click to collapse
The problem is install anything, i cannot install HSPL or anything else by USB (phone freezes at 0%), trying to install from the microSD the behavior is hanging at Searching . . .
Primordium said:
The problem is install anything, i cannot install HSPL or anything else by USB (phone freezes at 0%), trying to install from the microSD the behavior is hanging at Searching . . .
Click to expand...
Click to collapse
Are you trying to install HSPL through HD2 Toolkit, perchance? Have you tried the standalone version? A link to it is here. I would suggest right-clicking and running it as an administrator, just in case. After that, try using the HD2 Toolkit to repartition as MagLdr or CLK. If it's still a no-go, then I don't know.
OK, I just did a search and it came up with a slew of threads that possibly describe your problem. Have you looked at any/all of these and tried the suggestions in them?
[Q] HD2 freezes at 0% during update or flash
[Q] is this HD2 bricked or... need your opinion
Hd2 white screen of death
HD2 Bricked?HELP?
[Q] How to "unbrick" HD2?
HD2 stuck on custom boot screen and won't flash anything in bootloader
my htc hd2 is STUCK.. HELP ME PLS
[Q] Htc hd2 stuck on white screen
[Q] Unable to flash any ROM!
I realize that not all of them describe your situation perfectly, but the replies may still be helpful. There are a lot of things to try. I would read each of them carefully and try them all (as well as check that, the ones that you've already tried, you did the right way).