Well I'm going to unlock my phone (Sprint Touch) for the first time. I'm trying NFSFAN's wm6.5 ROM. Wish me luck. Hopefully my reading comprehension skills are up to the task so I don't skip a step and blow something up.
---
Question 1:
When I'm going to run the unlock utility, should ActiveSync actually say that it is connected to the phone? When I get to the rainbow screen ("Serial") then plug in the usb wire, the phone switches to "USB" and I hear the "something's connected" noise in XP. ActiveSync, however, still says "Not connected"
...I seem to be stuck here, at the beginning. At least my phone still works
One comment: the NFSFAN 6.5 ROM FAQ seems to want me to run the unlocker with the phone at the Rainbow screen. The PPCGeeks thread by IMCoKeMaN seems to say that you just run the unlocker with the phone normally attached to ActiveSync without unraring or Rainbow mode... Who is right? Am I just confused?
It seems like ActiveSync actually connects to the activesync program on the phone, so when you are in the rainbow screen, it connects without the OS being involved and AS won't show as being connected. If I remember, running the unlocker will put it in rainbow mode and you don't have to do that first. But it has been a long time since I unlocked mine and I forgot the details. I do remember I followed IMCoKeMaN's directions to the letter. Good Luck! It is scary to start, but these guys have got this stuff down to a science!
David
for the unlocker you go throught activesync. then to flash NFSFAN's ROM put the phone into bootloader. You can flash the rom using activesync but i've just got into the habit of using manual bootloader.
Knave,
Please let me know if the W6.5 works well on the HTC Touch (Sprint). I am a bit reluctant to try it yet, but if you can do it successfully, and report on how it does, then maybe I'll follow your lead.
Thanks
QA
So, I'm trying again. This time I plugged the phone in while it was turned on on the standard home screen. I let ActiveSync show that it was connected, and I ran RomUpdateUtility.exe. I click thru a couple screens, the phone automatically goes over to the rainbow screen, and then the status bar screen. It sits at 0% for about a minute.
...and I get another ERROR[262]: Update Error.
I turn the phone back on and it reboots fine (I guess it never actually started writing to the Phone's memory, just like in my initial post.)
One thing before you start, qanda, do you know about Dashwire? It's a way to backup all your phone contacts & info to the web before you wipe the memory. I guess there maybe different backup services out there, but I like to use one just to be safe.
Ah hah! Now it's (ALMOST) working... Here's some stream-of-consciousness directions I'm typing as I do the flash procedure.
1. Plug in phone (phone is turned on, in the normal home screen state)
2. Make sure ActiveSync says you're connected.
3. Run the unlocker (the Vogue_unlocker_MFG_2.31.exe file). Do *not* extract the downloaded file and run the RUU.exe file yourself. It doesn't work that way. You just follow the directions here in the "DOS" looking window that pops up. It does something to the phone, tells you to unplug & replug, ... Eventually a ROM loading program starts & you follow those directions. Then you go back to the "DOS" looking window.
4. Phone automatically reboots and gets to the Windows Mobile initialization screen (tap here & there, etc). Then the phone starts loading the customization stuff automatically. (I was getting a bit worried here that it was stuck on the Windows Mobile 6.1 boot screen -- seemed to take an extra minute or two, but it eventually came up.)
5. Now I guess the phone is *UNLOCKED* but still running the stock Sprint WinMo6.1 OS. I can confirm that when I do the PWR-CameraButton-Stylus reset to the rainbow screen, I see the SPL-2.31.CoKe text in the red bar.
6. Next, I'm going to try loading the NFSFAN 6.5 ROM...
7. I'm back to following the instructions in the thread by codybear *explicitly*: unplug phone, 3-button-reboot to rainbow mode (displaying SERIAL), plug in phone (now displaying USB), run the RUU.exe inside the directory where I decompressed the NSFFAN ROM. Clicked thru the RUU.exe program & phone goes to percent-loading status screen. Phone reboots itself at 100%.
8. Phone reboots *slowly*, the Sprint Splash animation is replaced by an HTC animation. Whew! after several minutes I see a WinMo6.5 setup screen. I do the setup & it autoload customizations. Phone automatically reboots.
9. Still following codybear's thread, I do the RED-GREEN-Stylus hard reset. (You have to hold down the buttons until you see the grey Hard Reset Warning Screen.) ... another SLOW reboot & I go thru the WinMo6.5 tap-screen setup again
10. Like codybear says, I install the Sprint DCD cab that I had copied onto my memory card. Phone wants to reboot again, so I OK it. (Sprint has one DCD cab and another cab for MMS, so I do both.)
----
Directions are now complete. Unfortunately when I try to do something with data service I get a "Error Code 1012 Data Provisioning Failure". It's late now, so I'll try to fix it tomorrow. This might help: http://forum.ppcgeeks.com/showthread.php?t=35433
Now I got everything working. I fixed the final error -- the "Error Code 1012 Data Provisioning Failure".
I initially tried running the IOTA thing via:
Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
...nothing happened. The I found this thread:
http://forum.xda-developers.com/showthread.php?t=410357
I did the RegEdit thing like it describes, setting the HKEY_LOCAL_MACHINE/Software/OEM/DIM/EnableCurrentUserName value to 0. Then I reran IOTA, and all is well.
Then I reinstalled Dashwire, it sync'ed my contacts up & I'm back to normal!
Woohah!
btw...RegEdit is on the NSFFAN ROM under Start Menu-> System Tools
Related
If I have overlooked the thread that covered this situation, please just point me to it as I have made several searches and read several threads but no luck.
I was happily running a custom 2003 ROM with the original AT&T stack. As I was quite happy with the way my 2003 OS was configured and operating, I decided to just try the NEW AT&T radio stack as I wanted to see if it helped with some reception issues I have expereinced. I copied the four radio stack files to the Windows directory on the PPC. I had the PPC in its cradle for power. I then executed the RSUupgrade and at 10% it locked down completely. No hard key had any effect and in fact, not even the soft boot buttom worked. I then attempted a cold reboot and that resulted in a hung machine again.
So, I decided to take the safe route and do an SD flash burn back to the original AT&T ROM (which I had copied way back when). Using XDA Tools I burned it to my SD card. Did the soft/on button routine, and proceeded to flash the memory. If indicated that the checksum matched and was finished. After the cold reboot, I got the old splash screen, but it took forever for the today screen to appear and the START button as well as ALL the indicators at the TOP are missing. I am unable to get to file manager.
I then decided to see if I could connect via ActiveSync. I uninstalled AS3.7. and reinstalled the original 3.5. When I attempt to connect, AS does see that the PPC has been docked, but it is never able to connect.
So, I am unable to reinstall a radio stack of any kind. I am unable to get the OS to function normally.
BTW, Just for grins I also tried an SD card install of the newest AT&T ROM as well as my custom ROM and the results are all the same. I suspect the now corrupted radio stack, but HOW do I purge it and start over when I can't get the OS to boot sufficiently to reinstall the stack
ANY IDEA? HELP!!!
Come on, someone has to have an idea
I will start off with an update. After reading another thread, someone mentioned that initial boot was taking about 15 minutes when there was NO radio stack. I decided to see if that might be occurring to me and sure enough, after about 15 minutes, the PPC beeped and the OS came up. If was still a bit sluggish, but operational. I was able to successfully attach to my PC via ActiveSync.
Now for the downside. Still NO success with installing the radio stack. I have tried reflashing the OS back to the original AT&T PPC2002 OS but that made no difference. I have tried both the original radio stack and the new one, no difference. I have tried to install the stack with the SIM card (SIM not SD) in and out, no difference. It always sticks at 1%, tells me the upgrade failed and to press ok to reboot. I did read the thread that gave LOTS of help regarding this issue, but nothing seems to help. I can remove the lnk in the startup folder, delete the files, reboot, recopy via ActiveSync, start the upgrade (RSUpgrade.exe) and everytime it immediately goes to 1%, sets there a minute or so, the pops up the failure message.
Surely, someone has an idea. Could a corrupt SIM cause this? Is there a alternate way of installing the radio stack?
BTW, just for grins, I thought I would try doing a "normal" exe upgrade since AT&T posted such. I know that it is full of risk, but at this point, I had little to loose. I made sure that I was running ActiveSync 3.7.1 and was connected. I then launched the upgrade. It came up with a splash screen with some warnings and the typical stuff. I then selected the "next" button and nothing happened except that cursor (when pointing in the window) went into the "working" state where it remained until I finally killed it about 30 minutes later. There was NEVER any sign that progress was being made.
HELP!!!
david
I have the same exact problem.
The Start menu is missing. No Icons on the top bar.
What's funny is that the screen seems to be inverted.
When I tap close to the bottom of the screen, the clock setting screen appears.
Anybody have a solution?
I suspect there is an alignment problem
When I first boot up after ROM upgrade, I can get to the today screen with the volume button, but I can't get to the file explorer because the start menu is missing.
When I tap on the lower part of the screen, the upper part responds.
Could this be due to the alignment steps being bypassed?
What order do you have to tap the alignment crosshairs during startup?
This sounds like a different problem
As I mentioned, on my first reflash of the OS after the radio stack upgrade failure, I got the today screen without the start bar at the top (ie it was totally blank and tapping in that area did nothing). Everything else on the today page worked. On subsequent reflashes of the OS, the today page was totally normal, start button, everything in place and working. On those subsequent reflashes, I also got the normal initial screen alignment pages on the first boot after the reflash.
I will also post, that I finally gave up on getting the radio stack to install. I have sent my unit to the guys at PPCTechs. In talking to them, they have 2 other SX-56 units in for upgrades with the same radio stack issue. They feel that they will be able to force the reflash via alternate means using a serial cable. As I mentioned on the other thread where I have been posting, I will post back once I hear if they were successful.
David
in general people should not mess with radiostacks unless they have issues and the radiostack is recommended by the phonecompany one use
My heads spinning from all the information aka post and threads, but im still stuck like my wizard on the 2nd splash screen.
I wasnt trying to upgrade the rom jst clear storage but after everything ive read i would like to upgrade to wm6 but first i want to get my wizard working.
I tried backing up the rom to the sd card but I get "You didn't get the proper security level to download a specific image" So i take it my wizard is cid locked.
My IPL:1.01 and SPL:1.06 does that mean its a g3. My activesync 4.5 doesnt pick up my wizard is it because it cant boot, i tried with it in bootloader mode still doesnt pick it up.
So plz point me in the right direction to fix my wizard
ok i think the place where im stuck at is cid unlocking my wizard with out using that imei site. any help or is there another way to do this.
This helped me when I was stuck on the first screen. For some reason, the Radio file was gone. Follow this exactly, it works. In my case (sounds like yours also), at the end of this you will at least have access to the phone again.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=bootloader
After your done. You will have a RGB screen, then follow these directions to load a base rom and unlock so you can keep going until you ca load WM6.1.
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies
I've had many, many problems over the last 3 days trying to do this. I completed it all in less than a day, but when I used the phone it had terrible reception. I completely downgraded everything back to square one. Still bad phone reception. I was about to through it out the window, when someone called my wife's cell phone and she also had bad reception. I then put my sim in another phone, same problem. Well, at&t has a tower down for the last 3 days. What timing, it seems to work when not at home, but hard to test that way Anyway, moral of the story is. Don't give up, keep plugging along.
Good luck.
I'm pretty sure imei checker is for SIM unlocking.
For G3 CID unlocking and upgrading read the stickies in http://forum.xda-developers.com/forumdisplay.php?f=289
If you can start your Wizard in bootloader, and it says "usb" in the lower-left, you can flash your original ROM. An active sync connection is not needed. Search for your carrier's ROM if you don't have it and I'd recommend the "no carrier ID" version of the RUU.
Have you tried a 'Hard Reset',hope it'll work,if it boots up into working OS and it already has IPL/SPL 1.xx,use lokiwiz02b tool to SIM/CID unlock the phone and than upgrade.
If it doesn't work still after Hard Reset,most probably,its Extended_Rom is corrupted,its required to reflash a new rom.
Activesync doesn't work in absence of a working OS and in Bootloaders mode.Its not required for flashing a rom.Just get the phone into Bootloaders and hook the phone with pc via usb cable and watch small usb appear at the bottom of the bootloader screen,if its there,it good to go and flash the rom.
ok so i downloaded the button rom finally but how do i flash it to my wizard.
Get your phone in Bootloaders,hook up the phone with pc via usb,watch small usb appear at the bottom of the Bootloader screen,if its there run the 'RUU' application,it'll start to flash,it stops at a certain percentage,don't get worried and do anything,after a couple of minutes it starts again,let it complete 100%,the phone'll restart and boot up in new OS.
which ruu application. I jst downloaded 1 which comes in the form of a rar file saying ruuwrapper. is that the right 1
So after lots and lots and lots more reading i realized i dont need a ruu. all i need to do is get into bootloader mode plug in the usb and run the wizard button rom. It worked perfectly my wizard is back to life yip pee.
Anyway i wud jst like to thank u guys for all the help and compliment u guys on a gr8 forum.
Now my next challenge is wm6 with touch flo.
Hi,
I've been reading through these forums and am getting very lost as to what to do.
I have the Orange SPV M3100 and it won't boot into windows. On switching it on, it does the orange bit: at the bottom - "m05 s04 b06 d1.23" and 'No GSM' flashes up briefly before the freeze on 'Windows Mobile' loading screen.
On pressing 'Ok' and power button together with a soft reset, I get to the tri-colour screen and it says "HERM100", "IPL-1.01", "HERM100", "SPL-1.04", and either "USB" or "Serial" depending on whether or not it's USB'd to a PC port.
I've tried the master reset - top two buttons and a soft reset, followed by 'R' to confirm a full reset. It immediately said 'done' or something to that effect, but still freezes on 'Windows Mobile'.
All the help threads here seem to indicate that I need to have this phone running with Active Sync on the PC to transfer files to it in order to refresh the ROM but Windows [XP] can't see the phone because it's not finished booting.
Please please please can someone give me a nudge in the right direction?
Many thanks
Dave
as you said ok and power together with soft reset action brings you tri colour screen. At that stage you plug in to active sync (4.5) and ensure you have .net framework installed on your PC.
with the tricolour screen, plug PC to phone and run the exe file from one of these ship ROM http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
you should then be able to get an OS back to your phone. Then get this one on to your phone
http://forum.xda-developers.com/showthread.php?t=296722
after that you can flash what ever rom you like make sure you follow the dr's suggestions here. http://forum.xda-developers.com/showpost.php?p=1990320&postcount=6
other than that, http://forum.xda-developers.com/showthread.php?t=299462 this thread is the only one I had to go on with the first time I played with my hermes.
zocster said:
as you said ok and power together with soft reset action brings you tri colour screen. At that stage you plug in to active sync (4.5) and ensure you have .net framework installed on your PC.
with the tricolour screen, plug PC to phone and run the exe file from one of these ship ROM http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
you should then be able to get an OS back to your phone. Then get this one on to your phone
http://forum.xda-developers.com/showthread.php?t=296722
after that you can flash what ever rom you like make sure you follow the dr's suggestions here. http://forum.xda-developers.com/showpost.php?p=1990320&postcount=6
other than that, http://forum.xda-developers.com/showthread.php?t=299462 this thread is the only one I had to go on with the first time I played with my hermes.
Click to expand...
Click to collapse
Will this remove all data from the phone, like contacts, settings?
If so, is there a way retrieve them before reinstalling OS?
Thank you.
[email protected] said:
Will this remove all data from the phone, like contacts, settings?
If so, is there a way retrieve them before reinstalling OS?
Thank you.
Click to expand...
Click to collapse
Well if your phone is semi dead, you can't really retrieve any data other than the ones on the SD card.
zocster said:
Well if your phone is semi dead, you can't really retrieve any data other than the ones on the SD card.
Click to expand...
Click to collapse
What is "semi dead"?
In my case it frozen at windows mobile screen, before it gets the animated "busy" square at the center...any hope?
[email protected] said:
What is "semi dead"?
In my case it frozen at windows mobile screen, before it gets the animated "busy" square at the center...any hope?
Click to expand...
Click to collapse
Well if you can't soft reset successfully then it is semi dead, you have to re flash
zocster said:
as you said ok and power together with soft reset action brings you tri colour screen. At that stage you plug in to active sync (4.5) and ensure you have .net framework installed on your PC.
with the tricolour screen, plug PC to phone and run the exe file from one of these ship ROM http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
you should then be able to get an OS back to your phone. Then get this one on to your phone
#######################################
Hi there, well, I'm back after months of forgetting about this but still hoping to get it to work. Thanks for the above reply, but that method of putting software on still relies on getting activesync to communicate with the mobile phone via the usb cable - my phone doesn't. windows sees that I've connected a usb device but active sync gives up trying to talk to it... any further ideas greatly appreciated...
Best regards
Dave
Click to expand...
Click to collapse
Hey there, just want to say before I tell you my problems that this forum is cool. I recieved a lot of useful information and tools for my phone here. Thanks.
Onto the problems!
Okay so first of all, I was given an HTC Vogue on the Telus network from a buddy because my previous phone fell in the pool. I was having a blast with this phone, 'twas the best thing that ever happend to me.
Now before I get into specifics, I'd like to mention that I've never been able to connect to activesynce because the computer would not recognize the USB cable. I've never been able to fix that problem.
Recently I've been having problems with my phone. Sometimes it would take a little spill onto the floor from my lap because I'd forget it's there or whatever. The back casing would come off and the battery would come out. No worries, I would just pop it back in and off I go. But this time it would boot up to the Telus screen with the buncha red writing.
Code:
M 03
B 01
P DCAAXOM-4350H
R 3.41.00
D 3.07
After that text disappears, the phone would freeze at the Telus screen and either: a) No LEDs would flash b) a yellow LED would come on c) THe phone would be left on that screen and just shut off after a while.
So i did some research and found that I could preform a hard reset. Voila! It worked like a charm and I was off using my phone again, but it had barely been 24 hours before the phone froze and I had to reset. And the phone would revertback to the previous problem. Hard reset would NOT work. It would reset the phone but still freeze. Sometimes it wouldn't even stay on the hard reset, the phone would shut off as soon as I release the SEND button after holding all fo the hard reset buttons. So i went back here and on Google to look for the fix.
I've done a bit of research on possible fixes to my phone like disassembley of the phone and the placement of plastic sheet over a processor of some sort and flashing the ROM.
So what I did was look up some custom roms and what not. From what I understand you need a CID Unlocker before custom roms can be used. I looked around and found that I need the USB connector to work for the phone to become unlocked. But this conflicts with my current situation and whenever I try to flash with a custom rom from the microSD, it takes me to the Loading... screen and stays there without any mention of flashing a ROM. This is also the case when I try to put the CID Unlocking .nbh on my microSD card.
So I ask what I can do for my phone to revive it. I've done extensive searches on any fix to my phone with little or no result. I need some fixes fast because I have a tonne of important calls coming in that I need to answer. I will not accept that my phone is dead.
Please guide me in the direction on how to unlock the CID with a microSD card. Or just anything that'll enable me to use my phone again. I con't afford ot buy another one.
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11[/QUOTE]
I gather that you can get to the boot loader screen by the above info. While on that screen try pluging you cable into a direct USB port on the computer and then into the phone. If your phone is recognized it will change from serial to USB at the bottom of the multi color screen. If that doesn't work let me know.
Also here is a link for the unlocker for the CDMA Touch on PPC Geeks
http://forum.ppcgeeks.com/showthread.php?t=20370
whitey10tc said:
BTW
The info on my boot loader screen reads.
VOGU100
SPL-2.01.0000
CPLD-11
Click to expand...
Click to collapse
I gather that you can get to the boot loader screen by the above info. While on that screen try pluging you cable into a direct USB port on the computer and then into the phone. If your phone is recognized it will change from serial to USB at the bottom of the multi color screen. If that doesn't work let me know.[/QUOTE]
I've tried that. The phone reads USB but the computer can't recognize the phone. Activesync won't work either.
EDIT
I've tried flashing with a stock rom. Everything runs fine in that screen. I soft resetted the phone and it went to the windows mobile 6.1 screen with an orange LED and just sat there, I wanted to wait but impatience got the best of me and I soft resetted and now it gets stuck on the telus screen again. Sometimes the green LED flashes as if the phone was running normally and the screen dims. I don't know whats going on.
I think I've tried that ppcgeeks thing but I can't be sure. It doesn't work because I can't connect my hpone with the USB cable.
My boot loader screen has changed after flashing the stock rom. It now reads:
Code:
VOGU100
SPL-2.01.0000
CPLD-3
same problem after flashing, just different writing on the boot loader screen.
patience
patience is the key.
patience is the key.
If you go to bootload screen connect cable and it changes to USB you should be connected.
Also here is a link to a tutorial
http://forum.xda-developers.com/showthread.php?p=3680838#post3680838
To be sure that your computer is not connecting to the phone plug usb in go to deivce manager and double check the USB if it is not connected correctly it will have a warning sign by that port. Try reinstalling updating your drivers for the usb.
patience is the key.
patience is the key.
beanage said:
My boot loader screen has changed after flashing the stock rom. It now reads:
Code:
VOGU100
SPL-2.01.0000
CPLD-3
same problem after flashing, just different writing on the boot loader screen.
Click to expand...
Click to collapse
You need to flash the SPL 2.31 bootloader
It appears as if it's fixed for the most part. Some minor problems but that doesn't stop the fucntionality of the phone. But I'm still pretty pissed that no matter what i do, my phone will not be recognized by the computer with the USB cable. i've tried everything and looked everywhere. Does someone want to send me the usb drivers for the Vogue? Please don't tell me that i don't need drivers because activesync won't connect. I've seriously looked all ove rthe internet for fixes and none of them work. Any pointers ro anyone want to send me official HTC drivers? I want to start using cooked ROMS.
here you go HTC windows driver will work for the vogoue
http://www.4shared.com/file/94429326/ffb09a5f/WindowsHTCdrivers.html
But unfortunately won't solve active sync problem. I would uninstall activesync and reinstall on your windows XP computer.
Quote from HTC website
Q.
Activesync is not recognizing my device, what should I do?
Be sure that you have not connected your device to your PC before you installed Activesync. If you did plug in your device before installing, uninstall Activesync and start the process over ensuring that you do not plug your device in until after Activesync has been installed.
Verify that your device is recognized by your PC in the Device Manager; if it is not, resolve that issue first.
Unplug your device from the PC for a few seconds and then plug it back in.
Perform a Soft reset on the device while it is plugged into the PC.
On the device, go to Start>Settings>Connections>USB to PC and check the "Enable advanced network functionality.
crap, my phone just ****ed off again. Same deal as before. Hate being broke.
help with vogue frozen loading screen
i unlocked my vogue and flashed NFSFAN 6.5 ROM and now phone freezes at loading screen and will go no further. i can still pull up bootloader thats all. any help or tips would be appreciated. thank you
what is your bootloader version
htc boot up screen and bootloader
m03
b01
acaaam-4070
r 2.26.00
s 3nfs
vogu100
spl-0.41.coke
cpld-3
are you using a GPS ROM if so you have the wrong bootloader and need the 2.31 from this post http://forum.ppcgeeks.com/showthread.php?t=20370.. Install the 2.31 and give it a try.
tried using 2.31 unlocker, when i run the RUU and says it will take 10 min it accually takes 10 sec and installs fast then after my phone restarts bootloader still says .41
You need that SPL 2.31 for that ROM
http://forum.xda-developers.com/showthread.php?p=3680838#post3680838
This is a quote from the facts thread for your ROM
First go here http://forum.ppcgeeks.com/showthread.php?t=20370 and
READ the hell outta it until you have it step by step.
(BTW use the 2.31 unlocker regardless about the GPS thing)
OK, now that you've read that (happy dance time)
Download the 2.31 Unlocker and NFSFANs WinMO 6.5 ROM.
Here is a good link for the boot loader. unlocker.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker_MFG_2.31.exe
yeah still can't get 2.31 to load on my phone. i tried to flash the stock alltell and sprint roms but at 29% it freezes or has recovery issues and will not go past 29%. flashed dcd 0.2.0 and got it to load! bootloader still shows .41 but now when i boot up phone it says in red at bottom of HCT boot screen.
m 03
b01
No radio
d1.17
Who is the original carrier You will need to get that OEM ROM and flash it. Then run the 2.31 unlocker follow the directions you can use the bootloader on the factory rom I have done it with sprint and alltel Vogues. The OEM ROM will reinstall your radio then you canuse the unlocker. The .41 unlocker is for non GPS radio and ROM combinations.
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)
I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"
Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?
test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?
Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.
Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse
Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium