Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty
Have you tried flashing a different rom or using a different pc to flash with?
i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
MontyV77 said:
Ok I've flashed close to a dozen times using various great ROMS everyone has provided and never had a problem. Today I realized that ATT/HTC released their official ROM yesterday and I thought I would give it a try. I followed their instructions but it did not work.
My phone looked as though it was updating and it got stuck at 11%. Followed the instructions to recover and it still did not work. Now my phone is stuck at the Triple Color Bar screen and I cannot do anything.
Did I brick my phone?
Can I use some of the options to try to unbrick in the xda wiki?
Thank you in advance.
- Monty
Click to expand...
Click to collapse
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.
TooSharp said:
Have you tried flashing a different rom or using a different pc to flash with?
Click to expand...
Click to collapse
Yes I've tried two different Official ATT ROMs and on different computers but same problem. Actually the only one that will attempt to start loading are the ATT ROMs and none of the cooked ROMs here are loading. Maybe that has something to do with the way they are packaged.
Jefem24 said:
i managed to revive mine from that state the key is getting the usb to let you update again dont plug in the cable until after the ruu is looking for the connection might take a couple tries but that worked for me.
Click to expand...
Click to collapse
Yeah I've done this now over a dozen times since yesterday and still no luck.
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse
This looked the most promising maybe because it felt like I was doing something and I was using the ATT ROM again to update, and it actually started updating again. But it stopped at 11% again and gave me the 262 error.
Below pulled from readme.txt file.
"ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode."
Click to expand...
Click to collapse
Tried to soft-reset and reinstall but same problem.
Scrambler001 said:
You should not update using the Oficial ROM release Update because you put in the boot loader from here (Hard-SPL-V7) and it will try over righting the entire rom if you do and is probably what messed up your update attempt. Use Dutty's NBH tool and just decompile the NBH of the official rom, then recompile the windows, splash screens and radio into a new NBH then flash using the RUUwrapper from this site to flash the phone.
Click to expand...
Click to collapse
Haven't yet tried this because I am having a hard time getting details on this. I've been searching looking for "duttythroy nbh tool", "nbh tool", "dutty nbh tool", and "dutty's nbh tool" and I can't find it.
If this helps anyone this is what I have on my tri-color screen:
HERM100
IPL - 1.04
HERM100
SPL - 2.03
Click to expand...
Click to collapse
You can also try to flash from the SD card:
- format a SD card with FAT32
- extract the .NBH file from the rom image you like (for your device of course)
- rename the .NBH to HERMIMG.NBH and copy it to your SD card
- put SD card in phone and start it in bootloader (hold OK button on left side and POWER button at same time and stick with stylus in RESET on bottom)
- confirm flashing on screen
- flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes.
This also works for normal (non preproduction) devices but keep in mind that if the CID does not match the flashing might not work. - this was taken from one old thread
- notes - you should backup everything on your SD card to your PC (because except for HERMIMG.NBH it should be blank)
- you can not get USB related error because it loads from a card
- if you flash official ROM you flash it with everything - radio ROM, Windows and bootloader
I am not really sure about bootloader you should have but for official upgrade official bootloader should be ok (it is first thing to be flashed - so I think you have bootloader from ATT ROM already.
Hope it can help somehow...
hey, what is your spl version?
it should say on your bootloader mode
and then read this http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
that really helps a lot, it has the solution and stuff. hope you unbrick your phone! all i did was download the update and it reloaded to wm5 update on my 8525 then after that, i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!
oh yea the factory update for my 8525 that unbricked my phone was this http://www.htcamerica.net/support/8525/software-downloads.html
try loading that in your phone =)
Ok that was the oddest thing but it worked. I've been trying to possibly unzip some of the packages by way of what duke_stix instructed. My last ROM was Schaps most recent 4.0. I unzipped what he had and ran the RUU file. What was funny though is that it started updating up to 3% then gave me the 260 error but this time my phone restarted and booted back up. I don't know what happen but it works now. If this is suppose to go in as a fix I don't know what happen.
Thank you everyone for all your help. I want to reflash my ROM but I will wait until I see this working for a while.
- Monty
asianr0cker said:
...i went for olipro's 2.10 so i dont unbrick it anymore =) then flash all you want!
Click to expand...
Click to collapse
How do I change my SPL to 2.10 now?
Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland
KarhU said:
Here is nice tutorial how to flash HardSPL v7 (a.k.a. bootloader 2.10 Olipro). Glad to see you are out of brickland
Click to expand...
Click to collapse
Thank you just finished flashing it. Thanks again to all that helped.
MontyV77 said:
How do I change my SPL to 2.10 now?
Click to expand...
Click to collapse
See mrvanx.org
... Edit: That's what you get for waiting 10 minutes before posting. Doh!
Thank You So Much !
I did all pricedures and it worked perfectly. You are the best dude!
duke_stix said:
Hi
Try this:
1) Turn your phone off completely
2) Hold the side OK button and the power button, at the same time push the reset button at the bottom with your stylus.
3) this should get you into the bootloader (the three colour screen)(dont be lazy and just let it load into the bootloader, actually run the key sequence ive just mentioned!)
4) on your PC run the update, i would reccomend the latest official update for your handset, BUT, do the following:
a) Make sure you have WinRAR installed
b) Right click on the update file you have just downloaded
c) 'Extract' the update file to the folder it makes
d) within that folder should be ANOTHER executable file that has the same icon as the original update
e) Extract this file again
f) open the folder it makes and within that there should be a RUUSIGNED.NBH and also the RUU utility itself
5) Run the update utility in the second folder
6) once the utility has loaded, plug your phone in (the text will change from 'SERIAL' to 'USB')
7) proceed with the update and see what happens
hope that helps
good luck.
Click to expand...
Click to collapse
if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special
blowfeld said:
if its an official rom you may need to hard sol it first as i had the same problem updating to original after a chefs special
Click to expand...
Click to collapse
what is a hard sol and how do I do it? I wanna go back to the OEM Official ROM to see if it fixes my no service phone problems.
Ok, I've tried everything that was posted in this thread and nothing worked so far.
My last setup before trying to reinstall the Radio is:
AT&T 8525 (location - Hawaii)
Black Majik's WM6
Herm Radio 1.43.00.00
Hard SPL-V7
The OS has been working great until this previous Monday. Also just in case if this is any relevant, Hawaii has just recently upgraded and turned on it's 3G network just a couple of weeks ago. They are still tweaking the whole thing to make sure all is well. Unfortunately it seems that something they did this past Monday seemed to really screw up the 8525's.
The reason I'm trying to reinstall my radio is because I happened to go to the phone settings, and saw that there was no Radio version on the screen. Thought this might also add to the problem.
Well where I'm at now is that I'm stuck at the Tri-Color loader screen. I've read the Wiki regarding fixing a bricked phone. Doesn't seem to help.
So I'm now stuck and need expertise of more knowledgeable members who might have been in the same situation as me.
Please, really need help as this is a company phone and I've got to get it working cause I don't wanna have to pay for it.
Related
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
esset said:
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
Click to expand...
Click to collapse
Here's the Tutorial and here's the Troubleshooter. They're both stickies. Please search and read before posting.
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
esset said:
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
Click to expand...
Click to collapse
Did you let your device sync with Activesync/Windows Mobile Device Center?
Try recreating the sync pairing.
Try uninstalling the device from PC's Device Manager and reinstalling it and then try recreating the sync partnership.
Try another USB port.
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
esset said:
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
Click to expand...
Click to collapse
Another USB cable?
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
esset,
May I ask what branding/model of the Diamond you own?
I own a pure AT&T model just purchased a week or two ago. And, so far I've also had almost zero luck flashing it. I'm moving from an AT&T Tilt which I've flashed so many times, the USB port is starting to wear down. I've also got a lot of experience with many small computing devices with all types of weird programming and flashing routines, so I'm not a newbie. But the AT&T Fuze just seems to be locked in a way that has yet to be covered by the good XDA folks here. Heck, I can't even dump the shipped ROM off the device to send it here for checking out by the developers. All I've been able to do is flash an odd 1.90 HardSPL that seems to have locked the phone even tighter than before. YUCK!
If you're in this same scenario, I'd suggest patience. Eventually someone with enough knowledge of these devices will be able to help out. It is frustrating though, after flashing the other phone so many times with so many different configurations to be held back on the new one.
tnyynt said:
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
Click to expand...
Click to collapse
You might find this odd. The down-volume + back arrow key combo doesn't seem to work with some of the new versions of the Diamond. I've tried on two of them, and neither respond to this key combo at startup.
Many times entering the bootloader is not a problem though. The routine does cause the phone to go there. And, I can get it there by other means. Just not via the boot up sequence. This tells me there is something very different about these models....
I tried starting and flashing directly from the bootloader (showing USB), and the phone got to show a percentage field (the one when you are flashing) but same here, is constantly at 0% until the flashing utility times out and tells me to reboot my phone and guides me through steps if it has been semi-bricked (bootloader is the volume down + softreset, right?)
I bought my phone in the first shipment to Sweden, it's not locked to any company, bought it without subscription
Else I just flashed it up to latest ROM from htc.com (still no success with HardSPL ) to 2.03.413.2 SVE (02/06/09)
Radio: 1.09.25.23
Version: 52.51.25.26H
ninjaedit: (In the four-colored bootloader thing it says DIAM100 64M SPL-2.03.0000 MicroP-Diam (LED) v11)
Tell me if you need any other info :]
Here's another indication that the new phones are different. I've copied a DIAMIMG.nbh file to both a flash card inside the phone, and to it's internal memory. (sorry, but the thread on that location is confusing on what memory. I assume like most phones of the past that it's supposed to be the flash card, but "internal memory" is not a flash card.) But, the loader screen always responds with "no image file" when it's called up. So, is there a different name expected now?
put manual hardspl into your device, and click to it from your device..
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Hi uhm, was that answer aimed for me or to scottwilkins?
If it was for me, is it possible to flash the mobile directly from the memory-card (or internal flash card)? Else if you mean the "manual make-the-screen-black-and-go-to-bootloader" my screen just goes blank, as when you do it with the RUU, and just stops there. Also seems like it looses the connection via USB doing so too. And flashing through the bootloader directly (volume down at softreset) shows the progressbar on the phone, but steadily at 0% (when trying to flash).
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
scottwilkins said:
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
Click to expand...
Click to collapse
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
okokur said:
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
Click to expand...
Click to collapse
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
zerocool81 said:
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
Click to expand...
Click to collapse
That program makes the Fuze screen just turn black and do nothing. Cool, huh
Seems that the newer stock ROMS might be blocking something... hmmmm....
Well, crap!
I just figure out where my whole problem is...
The Fuze (my phone) = The Raphael
NOT the Diamond.
I just scrolled down the forum list, saw a phone that looked like mine and went there. DOH!
I feel like a total dumb-ass.
If I'd scrolled just a bit farther down the XDA forum, then I'd seen the Raphael phone.
Holy Cow! Go ahead, say it, I deserve it...
Thanks for all the help otherwise. It was a learning experience for me....
esset said:
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
Click to expand...
Click to collapse
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
okokur said:
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
Click to expand...
Click to collapse
Thanks, but that file takes me into the bootloader, and when I start flashing the percentage is still at 0% until the software times out. Same as before, just the usual "going-into-the-bootloader".
Well I just flashed my first ROM and thought I followed everything to the letter. I ran HardSPL, it completed, and I verified that it was done in the bootloader screen. Then I downloaded Energy 23544 with MaxManila Mar 09. Sync'ed with WMDC, Ran Custom RUU, It says it flashed ok. Now it just sits at the "Toch Pro2" startup screen. Can anyone tell me what I missed and if there is anyway to fix it?
Thanks
Steve
stisinai said:
Well I just flashed my first ROM and thought I followed everything to the letter. I ran HardSPL, it completed, and I verified that it was done in the bootloader screen. Then I downloaded Energy 23544 with MaxManila Mar 09. Sync'ed with WMDC, Ran Custom RUU, It says it flashed ok. Now it just sits at the "Toch Pro2" startup screen. Can anyone tell me what I missed and if there is anyway to fix it?
Thanks
Steve
Click to expand...
Click to collapse
Need more info like who is your carrier...the problem you are describing sounds like you flashed a gsm rom (t-mobile and at&t) to a cdma phone (sprint and verizon). If that is the case you need to flash back to stock rom then grab the energy rom from here for the CDMA phone
http://forum.ppcgeeks.com/showthread.php?t=86489
hopefully you did not brick your phone...good luck
Seems like you've done everything right. Just note that first time flashes usually take a while to load on the first boot before customization procedures.
If the phone doesn't budge, try a hard reset. To Hard reset your phone, Turn it completely off (remove and reinsert battery if needed), then hold down the Send and End and the power button. It should load the SPL and then ask you if you want to Hard Reset, press the Volume Up key to accept.
If the Hard Reset doesn't work, download a stock ROM, and flash that via the bootloader. If the stock ROM works, try to flash the Energy ROM again.
To enter the bootloader, Hold down the Volume Down key while turning on your phone. or hold it down and while pressing the reset button.
Hopefully you can get this sorted.
eichenberg said:
Need more info like who is your carrier...the problem you are describing sounds like you flashed a gsm rom (t-mobile and at&t) to a cdma phone (sprint and verizon). If that is the case you need to flash back to stock rom then grab the energy rom from here for the CDMA phone
http://forum.ppcgeeks.com/showthread.php?t=86489
hopefully you did not brick your phone...good luck
Click to expand...
Click to collapse
That could be the case, but he sucessfully flashed a HardSPL, so he could just enter the bootloader and flash his stock ROM to continue operation of the phone.
When he responds about who his carrier is and which TP2 he has, we'll go from there.
I am on US Cellular and I did use the GSM ROM for some stupid reason. I can load the bootloader screen and am downloading the correct ROM now. I assume I then follow the load from microSD card procedures?
Thanks guys
You are lifesavers if I can get past this
stisinai said:
I am on US Cellular and I did use the GSM ROM for some stupid reason. I can load the bootloader screen and am downloading the correct ROM now. I assume I then follow the load from microSD card procedures?
Thanks guys
You are lifesavers if I can get past this
Click to expand...
Click to collapse
Yes, with HardSPL you can flash the nbh file from the microSD card, but I recommend you flash using your PC via USB. It would save you the hassle of trying to find and extract the NBH.
Well it wouldn't update via the PC because it wouldn't connect. I did find and rename the nbh file and put it on another sd card. It is updating now with the stock ROM. Then its back to the drawing board if this works.
Thank - I'll update and give other noob idiots my story when all is good. (still having fingers crossed)
stisinai said:
Well it wouldn't update via the PC because it wouldn't connect. I did find and rename the nbh file and put it on another sd card. It is updating now with the stock ROM. Then its back to the drawing board if this works.
Thank - I'll update and give other noob idiots my story when all is good. (still having fingers crossed)
Click to expand...
Click to collapse
Hmm... HardSPL usually enters USB mode when the bootloader is run and a USB cord is connected, but I'm glad you got your phone flashing either way. Good luck.
My problem was definitely the wrong ROM version.
For anyone else as dumb as me, this is what my problem was...
Everything seemed to flash ok originally (the program said it was successful). Then it restarted and the phone would not go past the "Touch Pro2) screen. There was nothing else on the screen.
and here is what I did to fix it...
Got another SD card and formated to fat32.
Extracted the proper original ROM.exe file using winrar.
Placed the .ngh file in the root of the card with the name rhodimg.nbh
Insert the sd card in the phone and restart into the bootloader screen
When it asked if I wanted to load the ROM, I of course did what it said
When it finished I removed the sd card and pressed the reset button
It took a while but everything loaded ok.
Then I started over with the ROM I wanted (this time using the correct CDMA version). Again everything seemed to go ok. This time when it rebooted, on the "touch pro2" boot screen there was additional text at the bottom indicating the cooked ROM I installed.
Thank you to everyone who helped me understand what I did wrong and I hope noone else is as dumb as me, but if you are there is hope.
Thanks
Steve
stisinai said:
My problem was definitely the wrong ROM version.
For anyone else as dumb as me, this is what my problem was...
Everything seemed to flash ok originally (the program said it was successful). Then it restarted and the phone would not go past the "Touch Pro2) screen. There was nothing else on the screen.
and here is what I did to fix it...
Got another SD card and formated to fat32.
Extracted the proper original ROM.exe file using winrar.
Placed the .ngh file in the root of the card with the name rhodimg.nbh
Insert the sd card in the phone and restart into the bootloader screen
When it asked if I wanted to load the ROM, I of course did what it said
When it finished I removed the sd card and pressed the reset button
It took a while but everything loaded ok.
Then I started over with the ROM I wanted (this time using the correct CDMA version). Again everything seemed to go ok. This time when it rebooted, on the "touch pro2" boot screen there was additional text at the bottom indicating the cooked ROM I installed.
Thank you to everyone who helped me understand what I did wrong and I hope noone else is as dumb as me, but if you are there is hope.
Thanks
Steve
Click to expand...
Click to collapse
No biggie, you're very welcome. We all are noobs at some point of our existance and we all make mistakes. I'm just glad you were able to learn from yours and recover, in addition to pointing out to others what went wrong. Have fun with your new ROM.
~Joseph
stisinai said:
My problem was definitely the wrong ROM version.
For anyone else as dumb as me, this is what my problem was...
Everything seemed to flash ok originally (the program said it was successful). Then it restarted and the phone would not go past the "Touch Pro2) screen. There was nothing else on the screen.
and here is what I did to fix it...
Got another SD card and formated to fat32.
Extracted the proper original ROM.exe file using winrar.
Placed the .ngh file in the root of the card with the name rhodimg.nbh
Insert the sd card in the phone and restart into the bootloader screen
When it asked if I wanted to load the ROM, I of course did what it said
When it finished I removed the sd card and pressed the reset button
It took a while but everything loaded ok.
Then I started over with the ROM I wanted (this time using the correct CDMA version). Again everything seemed to go ok. This time when it rebooted, on the "touch pro2" boot screen there was additional text at the bottom indicating the cooked ROM I installed.
Thank you to everyone who helped me understand what I did wrong and I hope noone else is as dumb as me, but if you are there is hope.
Thanks
Steve
Click to expand...
Click to collapse
Glad you got your TP2 back, it's not a nice paperweight
Badwolve1 said:
it's not a nice paperweight
Click to expand...
Click to collapse
Actually as paperweight's go, it's a damn sexy one
But I would prefer a working phone any day
I do have to say that I am drooling at the possibilities of this phone. Just have to take things a little slower.
I did the same thing basically. I tried a gsm rom on my us cellular phone. didnt know that they conflict at that point.
what rom do i need to flash to get my phone back?
Here is a good place to start...
http://forum.ppcgeeks.com/forumdisplay.php?f=98
I am very happy with the Energy Rom's, but that is a whole different discussion.
Or you can go back to the stock ROM which you can get at ppcgeeks also.
joseph881 said:
Seems like you've done everything right. Just note that first time flashes usually take a while to load on the first boot before customization procedures.
If the phone doesn't budge, try a hard reset. To Hard reset your phone, Turn it completely off (remove and reinsert battery if needed), then hold down the Send and End and the power button. It should load the SPL and then ask you if you want to Hard Reset, press the Volume Up key to accept.
If the Hard Reset doesn't work, download a stock ROM, and flash that via the bootloader. If the stock ROM works, try to flash the Energy ROM again.
To enter the bootloader, Hold down the Volume Down key while turning on your phone. or hold it down and while pressing the reset button.
Hopefully you can get this sorted.
Click to expand...
Click to collapse
O Bless you Joesph881.I had same problem.Flashed stock Rom in bootloader.My life is back to normal.Again,thanks.
stisinai said:
Well I just flashed my first ROM and thought I followed everything to the letter. I ran HardSPL, it completed, and I verified that it was done in the bootloader screen. Then I downloaded Energy 23544 with MaxManila Mar 09. Sync'ed with WMDC, Ran Custom RUU, It says it flashed ok. Now it just sits at the "Toch Pro2" startup screen. Can anyone tell me what I missed and if there is anyway to fix it?
Thanks
Steve
Click to expand...
Click to collapse
hit the red reset button on the right. mine did that also, and that is what I did, and it came back up without a problem.
STOCK ROM
FYI, the stock ROM, original ship ROM can be found here at the htc mobile phone product support page. It comes as an *.exe and you double click once in the bootloader screen and it works
I had a problem where I flashed with a new rom, and it went to the white screen. I had to flash with the original ROM and it came back to life! yay.
Hi everyone well I'm new to the flashing and dont want to jump any steps as this could possible brick my phone...
I've been having some problems with flashing as i cant find a step by step to flashing my HTC TP2. I've managed to do the RhodiumW Hard-SPL package but after trying to flash to some custom RUU's the installation seems to go fine its not until the phone first boots up, that's when the phone just hangs on the HTC splash screen
From there i cant do anything other then boot up to the tricolor bootloader screen and re-install the original 2.04.651.4 update!
can someone tell me what im missing to be able to flash my HTC correctly, or at least point me in the right direction?
Thank you in advance!!!
step 1
http://member.america.htc.com/download/RomCode/HTC Touch Pro2 (Sprint)/HTC Touch PRO2 MR1.exe
step 2
http://rhodiumw.htc-unlocks.com/hard-spl.php
step 3
http://www.mightyrom.com/mightyrom/touch-pro-2/
Hey Tommy many thanks for the post. I just upgraded my phone and peeling through the information overload, however you direct link does not work for step 1. I want to make sure that I am running the correct piece of software that you recommending. Could you please list the title for that file?
Nevermind I was able to find it via a mirror site.
Back into lurker status for now
Thanks
alright so i was able to install they mightyrom on my phone that went well my phone didnt freeze and everything started the way it should have.
but does that mean i can now flash my phone to other for example "leo cell" or Bxsteez Rhodium" if not how do i get to that point cuz when ever i flas them to they just freese on the white splash screen with the HTC logo in green letters!!
Thanks!
If you have installed Hard SPL then use the sd card method.
1. Format the sd card FAT32 ( they come FAT default) and copy the rom's .nbh file onto it. Rename to Rhodimg.nbh .
2. Insert sd card back into powered off Rhodium. Go into bootloader by pushing down volume and power.
3. If you did it properly and Hard SPL is on your phone then it should say to press power to update os...
If you aren't sure if you have Hard SPL then go to bootloader without the sd card in there, it should say SPL - 0.85.Olinex if you have Hard SPL, anything else won't register the flash file.
Cheers...
OK I was able to update to Winmo 6.5 with no issues....but here is my questions with regards to the Rhodium_W Hard-SPL
I was attempting to run it and it never gets pass 0%...In reading the details of the install instructions it reads
"the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license."
Click to expand...
Click to collapse
I have yet to activate my phone with Sprint could this be my error that I need to active my phone? I wanted to have the phone flashed and customized before activating.
signalsoldier said:
OK I was able to update to Winmo 6.5 with no issues....but here is my questions with regards to the Rhodium_W Hard-SPL
I was attempting to run it and it never gets pass 0%...In reading the details of the install instructions it reads
I have yet to activate my phone with Sprint could this be my error that I need to active my phone? I wanted to have the phone flashed and customized before activating.
Click to expand...
Click to collapse
I think you should ask this in the hard spl thread in the cmda section...That is the place for those questions Assuming that you have a cdma phone because you did not mention it. Otherwise check the hard spl thread in the gsm section.
Heading that way thanks for the directions mate!
Alright so ive been able to flash my rom to my first custom rom by energy which i like very much, although still a noob, i want to flash it to a different rom
What is the best way to flash to a different rom with out leaving any files behind that would affect the new rom?!
do i have to do a hard reset or something that would clear my phone from any old files?!
htcru7 said:
Alright so ive been able to flash my rom to my first custom rom by energy which i like very much, although still a noob, i want to flash it to a different rom
What is the best way to flash to a different rom with out leaving any files behind that would affect the new rom?!
do i have to do a hard reset or something that would clear my phone from any old files?!
Click to expand...
Click to collapse
Just flash away
LOL alright thanks i guess im just paranoid but thanks i'll "flash away"
Lock
When you start Rhodium_CDMA_HardSPL_V1_10R3_100HSPL stoppers on 0%.
I removed the firmware via mtty 1.42 entering the command: task 28 \ task 29. Ie fully formatnul system. This is often applied to remove the lock on the HTC 6800. At this time nothing worked. Under bootloger any firmware stoppers on 0%. Besides, even the official RUU_Rhodium_W_S2_Sprint_WWE_2.04.651.4_RS_2.32.00WF_NV_SPCS_2.20_0224_PRL60660_S
hip
and HTC Touch PRO2 MR1 from the official portal hangs at 1%, then is restarted Device, and as expected if there is no OSes lit logo HTC ...
What should I do?? If GSM is blocked, how do I remove it to flash?
Ps Is it possible to disable the lock on the firmware via mtty
1.42??
Thank you very much for your answer!
Scream-krg said:
When you start Rhodium_CDMA_HardSPL_V1_10R3_100HSPL stoppers on 0%.
I removed the firmware via mtty 1.42 entering the command: task 28 \ task 29. Ie fully formatnul system. This is often applied to remove the lock on the HTC 6800. At this time nothing worked. Under bootloger any firmware stoppers on 0%. Besides, even the official RUU_Rhodium_W_S2_Sprint_WWE_2.04.651.4_RS_2.32.00WF_NV_SPCS_2.20_0224_PRL60660_S
hip
and HTC Touch PRO2 MR1 from the official portal hangs at 1%, then is restarted Device, and as expected if there is no OSes lit logo HTC ...
What should I do?? If GSM is blocked, how do I remove it to flash?
Ps Is it possible to disable the lock on the firmware via mtty
1.42??
Thank you very much for your answer!
Click to expand...
Click to collapse
the Hard-SPL will only work if you booted windows mobile. you have to sync the phone in windows mobile to the PC.
is there other way to get through in hard spl because i dont have any account for example, paypal...... http://media.xda-developers.com/images/icons/icon9.gif
chrisjavier666 said:
is there other way to get through in hard spl because i dont have any account for example, paypal......
Click to expand...
Click to collapse
Hard SPL is free for non-commercial users.
my tp2 is bricked
i tried to upgrade my htc touch pro 2's rom. i received error 226 and anytime i switch it on, it gets to the tricolor boot and displays a lot of info and says try again. Can anyone please help me?
nastyrock said:
i tried to upgrade my htc touch pro 2's rom. i received error 226 and anytime i switch it on, it gets to the tricolor boot and displays a lot of info and says try again. Can anyone please help me?
Click to expand...
Click to collapse
Did you try flashing the stock ROM? It's always a good idea to try that if you think there's no hope. It flashes everything.
Also, did you try task29?
After doing soft reset to my htc trinity it gave me black screen and nothing than this...tried flashing new rom i entered boot loader and flashed correctly but after it finished flashing and reset it gave me black screen also tried different roms but same proplem
Can Anyone help?!!
Hai...! I am not expert on this stuff . may the other can give you a good solution to solve your problem. Did you try to hard reset your device or do hard SPL before flashing? if you didn't do the Hard SPL that's the problems. Some one said to fix the broken Trinity with JTAG Solution, be careful to do this.
See for the thread about JTAG to unbrick your Trinity on this forum.
Hope it will help you...
hmmm..i use olipro 1.30 hard spl,,,but i am wondering why just it cant be replaced by old spl?? and also using the JTAG solution seems dangerous alittle
EgyPharaoh said:
hmmm..i use olipro 1.30 hard spl,,,but i am wondering why just it cant be replaced by old spl?? and also using the JTAG solution seems dangerous alittle
Click to expand...
Click to collapse
Hi EgyPharaoh, Have you tried flashing back to the Stock OEM ROM yet? That will usually fix problems with a bad flash for me. You can find it HERE. I would not recommend looking into JTAG just yet.
If this does not work, let me know and we will research the next step.
SuperSport said:
Hi EgyPharaoh, Have you tried flashing back to the Stock OEM ROM yet? That will usually fix problems with a bad flash for me. You can find it HERE. I would not recommend looking into JTAG just yet.
If this does not work, let me know and we will research the next step.
Click to expand...
Click to collapse
I started flashig it but it reaches about 28% then gives me upate error [262]..but i flashed official htc rom "HTC [WWE] v1.23.405.2] with no errors and when i open it it shows the "htc image" and freezes.
and it says in the readme that if this error showed then it might be that the wince is destroyed or in upgrade mode...how to know now wether it is destroyed or in the upgrade mode??
EgyPharaoh said:
I started flashig it but it reaches about 28% then gives me upate error [262]..but i flashed official htc rom "HTC [WWE] v1.23.405.2] with no errors and when i open it it shows the "htc image" and freezes.
and it says in the readme that if this error showed then it might be that the wince is destroyed or in upgrade mode...how to know now wether it is destroyed or in the upgrade mode??
Click to expand...
Click to collapse
Sorry about the delay, and thank you for the PM reminder.
Try flashing directly from the BootLoader Screen, by holding both the Power and Camera Buttons while you press and release the Reset Button using your stylus. Continue to hold the Power and Camera Buttons until your phone enters bootloader.
If that does not work, try to flash using your SD Card.
Using either 7zip or WinRAR, extract the contents of the OEM ROM you downloaded earlier. You are looking for the RUU_signed.nbh file inside. If you prefer to just download it, you can find it HERE.
Rename the file from RUU_signed.nbh to TRINIMG.nbh and copy it to your SD Card. Don't place it in any folder, just in the Root of the Card. Place the SD Card back into your phone if it's not already.
Now, Enter Bootloader by holding both the Power and Camera Buttons while you press and release the Reset Button using your stylus. Continue to hold the Power and Camera Buttons until your phone enters bootloader. It should at this time start to flash the OEM ROM you copied earlier. Hopefully, this will be successful. If it is, it will have replaced your HardSPL ROM & Radio, so you will need to flash those again.
Let me know if this works or not.
SuperSport said:
Sorry about the delay, and thank you for the PM reminder.
Try flashing directly from the BootLoader Screen, by holding both the Power and Camera Buttons while you press and release the Reset Button using your stylus. Continue to hold the Power and Camera Buttons until your phone enters bootloader.
If that does not work, try to flash using your SD Card.
Using either 7zip or WinRAR, extract the contents of the OEM ROM you downloaded earlier. You are looking for the RUU_signed.nbh file inside. If you prefer to just download it, you can find it HERE.
Rename the file from RUU_signed.nbh to TRINIMG.nbh and copy it to your SD Card. Don't place it in any folder, just in the Root of the Card. Place the SD Card back into your phone if it's not already.
Now, Enter Bootloader by holding both the Power and Camera Buttons while you press and release the Reset Button using your stylus. Continue to hold the Power and Camera Buttons until your phone enters bootloader. It should at this time start to flash the OEM ROM you copied earlier. Hopefully, this will be successful. If it is, it will have replaced your HardSPL ROM & Radio, so you will need to flash those again.
Let me know if this works or not.
Click to expand...
Click to collapse
Thanks For your solution but it didn't work
i did all what u said and that's what happened :-
TRINIMG.nbh
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM -
GSM -
Update In Progress...
and that's all it stops at the first..i read in another thread about flashing from sd card and it said that it may stop for a while but it stops forever
Next Step
TRINITY BACK!!! xD
YEAAAAH I DID IT
well supersport, thanks alot for your help...it helped me alot
the nbh file of the dopodasia rom u gave me didnot work so i tried the same thing but with the old rom i have, the "Htc official rom v1.23.405.2" i took the file named "TRINIMG_HTC_WWE_1.23.405.2_Ship.nbh" and renamed it to "TRINIMG.nbh" then put it in my sd card ..and flashed it and update succeeded and my trinity now works good..thank you and anyone helped in this thread
EgyPharaoh said:
YEAAAAH I DID IT
well supersport, thanks alot for your help...it helped me alot
the nbh file of the dopodasia rom u gave me didnot work so i tried the same thing but with the old rom i have, the "Htc official rom v1.23.405.2" i took the file named "TRINIMG_HTC_WWE_1.23.405.2_Ship.nbh" and renamed it to "TRINIMG.nbh" then put it in my sd card ..and flashed it and update succeeded and my trinity now works good..thank you and anyone helped in this thread
Click to expand...
Click to collapse
Awesome, glad to hear it worked. Remember, you will need to Flash HardSPL again if you want to flash Custom ROMs again, and also an updated Radio if you prefer.
SuperSport said:
Awesome, glad to hear it worked. Remember, you will need to Flash HardSPL again if you want to flash Custom ROMs again, and also an updated Radio if you prefer.
Click to expand...
Click to collapse
but i found that my radio & hardspl didnt change.
EgyPharaoh said:
but i found that my radio & hardspl didnt change.
Click to expand...
Click to collapse
Then you are fine. I guess you have an OEM ROM that has the HSPL and Radio stripped out of it.
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x
d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?
d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button