[Q] How to revive a BlueAngel? - MDA III, XDA III, PDA2k, 9090 General

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

Related

Unable to boot up after upgrade ROM to WM6

I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.
Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!
yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.
Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....
Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks
Error message I recive at the 3% stage when using the German ROM and english update util.
use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112
Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?
motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.
I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.
What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.
So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!
ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks
unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help
Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted
Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0

Did I Brick My Phone?

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.

aaahh!! help please!!!

aahh something happened when i tried to flash a rom on my universa, i connected it to the pc, and started the proccess as allways, but.. it stucked at 7% and then error!!! and now i cant flash anything!! what can i do???
Isaygarcia said:
aahh something happened when i tried to flash a rom on my universa, i connected it to the pc, and started the proccess as allways, but.. it stucked at 7% and then error!!! and now i cant flash anything!! what can i do???
Click to expand...
Click to collapse
AND theres an error, 112 Update error can anyone help me??
help please!!
Quihubole paisano! Sorry, even if I speak spanish, this is an english forum so...
If you haven't had any answer yet is because that question might well have been answered several times, you have to be patient and search the forum and the wiki, even if I have never had that problem (fortunately) it is somehow "common", there are several methods, involving sometimes the need of getting the PDA in bootloader mode, attaching it to the PC and using a serial communications program (such as hyper_terminal), also if I remember well, the great MAMAICH have it's own method, so, look out, dig, read, lose your sleeping hours and good luck!
After that, if you're still having problems you will certainly propose a better question that someone might answer...
Animo
Hey thanx!! i think its bricked, now i need to unbrick it.. it can help because it can be posted on WIKI! and may be usable as well for all..
Ok slow down we need a bit more info
What rom did you have before
What exactly did you do
And witch rom did you try !!
ok step by step.
I was happy a sunday morning, and i was reading this forum lala.. Happy..
then...
i saw a rom ... that rom was WM6.1 http://forum.xda-developers.com/showthread.php?t=365335
i flashed it.. it worked fine but i had so low memory.. then i continued reading that thread, and found that someone changed the pagepool and gained memory, and i downloaded the modified version.
well, when i tried to flash it.. the phone just got unrecognized by the pc (when it tried to enter the bootloader with the RUU, as allways) and became nonresponsive... then i did a reset.. and nothing.. then i did a hard reset... and nothing... and then... i entered to Bootloader manually, and it worked... and i started the flash... but... when it reached the 7%.. it stoped and typed "ERROR 112: CE ROM UPDATE ERROR" and it happens with every single rom i try to flash...
i got some conclusions, maybe the SPL or something has corrupted the rom settings, but i dont know how to fix it.. can you help me?
HEY!! many thanx.. the problem was solved with mtty method, but with another code...
many thanx..
i will put the method here in a while (breathing DEEP)
Hey mate, as i told you in that thread, those 2 methods in wiki, they work
Congrats, mate.
Isaygarcia said:
ok step by step.
I was happy a sunday morning, and i was reading this forum lala.. Happy..
then...
Click to expand...
Click to collapse
, i liked the way, you explained it.
Ok. The way i solved the Problem was the MAMAICH method, wich is:
1. Enter Bootloader.
2. Disable Async (task manager, end task)
3. Connect Universal via USB (in bootloader mode)
4. Run mtty (found in wiki)
5. In mtty, write USB on the left corner (it says COM1)
6. Press OK button on the right upper corner.
7. A window should appear, press enter, after that, you can see a "USB>" thing.
8. Write "task 28 55aa" (without quotes).
9. A process appear on screen (nothing in the Universal)
10. Well done, now you can flash any ROM again.
Thanx for all those who helped me. n____n
@rohitsharman: haha yeah..

Dutty's ROM locked my phone?

So...I've been using an older version of Dutty's ROM, but I haven't updated in a few weeks.
Tonight, out of nowhere, my phone will now only show a screen saying:
"This concludes the beta test of this software release. Thank you very much for your time and effort in helping make this a great product for our customers.
To obtain a newer release or further information, please revisit the web site that you used to obtain your current beta release."
Strange...
I tried downloading the most recent version of Dutty's rom and loading it, but the computer says "Cannot connect to your PDA phone..."
What's going on here!?
I have tried resetting the phone via the reset button (under the stylus), and I have tried restarting the phone via soft/hard reset, but nothing works!
Everytime my phone turns on, it goes immediately to this white page saying the "This concludes the beta test of this software release..."
How can I make my Diamond work again?!?
Please help!
i am having the same problem tonight too
i did a hard rest.. didnt fix it.. plus i lost all the stuff i had on there.. but it's ok
i heard u need to reflash it or something but i donno the full detail.. hope someone here can help us... thanks
step by step instruction would be great
I think you must put your diamond in "bootloader mode". and you will reflash your phone with a new rom, or another rom...
Booloader mode (usb) = Volume down + reset
In the screen (down) = serial, and if you connect with usb you can see "usb" and now you can reflash!
how can i reflash? i'm VERY new with this smartphone stuff my first smartphone so i donno a lot of stuff..
does it need HSPL 1.24? cause if it does i cant seem to run DiamondCustomRUU after my phone went black screen
i will try the "bootloader" mode, but i hope it works! i will post results a.s.a.p.!
Same for me on Dutty 2.3, but did hard reset and let phone set up. Do NOT change the date, I left mine as September, and phone will continue to set up and start. Now what I need to know is if I flash with latest rom will that allow me to set current date?
bigbro168 said:
how can i reflash? i'm VERY new with this smartphone stuff my first smartphone so i donno a lot of stuff..
does it need HSPL 1.24? cause if it does i cant seem to run DiamondCustomRUU after my phone went black screen
Click to expand...
Click to collapse
You put "volume down" and, in same time, you put "reset" (you hold these 3 seconds) => and you enter in bootloader, then you connect your diamond to USB and launch installation...
i think you don't need a HSPL if you want flash with the same rom... but you may use another HSPL for another rom...
OK - so i just started in Bootloader mode as suggested...
after that, i plugged it in to my computer vis USB.
then, i opened the most recent rom updater (supplied by dutty...see the thread in this forum).
it is currently updating, and everythign is looking good.
so, why do you have an experation on your rom's dutty??? what's up with that?!?
thanks fabe
but let say i want to flash the SwithBL Rom.. it's not the one i used b4.. do i still need HSPL? if yes how do i install so i dont get the black screen and it actually works?
theorie said:
OK - so i just started in Bootloader mode as suggested...
after that, i plugged it in to my computer vis USB.
then, i opened the most recent rom updater (supplied by dutty...see the thread in this forum).
it is currently updating, and everythign is looking good.
so, why do you have an experation on your rom's dutty??? what's up with that?!?
Click to expand...
Click to collapse
can u send me the pw for dutty's ROM? i cant seem to unzip it.. just wondering did u use HSPL?
bigbro168 said:
can u send me the pw for dutty's ROM? i cant seem to unzip it.. just wondering did u use HSPL?
Click to expand...
Click to collapse
i just downloaded & installed: V2.9_5_2_20275_RTM_Full_MSVC
http://rapidshare.com/files/162091111/Ruu_Signed_duttys_diamond__V2.9_5_2_20275_RTM_Full_MSVC.zip
the password is: Duttys V2.9 RTM Finale
i have HSPL installed.
bigbro168 said:
can u send me the pw for dutty's ROM? i cant seem to unzip it.. just wondering did u use HSPL?
Click to expand...
Click to collapse
careful you might get banned. see dutty's thread.
We have a thread for dutty's ROM. Please discuss there!

HardSPL... 0%?!

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".

Categories

Resources