After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan
http://www.xda-developers.com/forum/viewtopic.php?t=2489&sid=8c1aea80a41318c77a50013b562fe4df
Jan said:
After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan
Click to expand...
Click to collapse
Hello Jan
please find these two links i guess they are usefull to resolve your problem and the posts are by chosl and wwb95
First link click here
Second link click here
good luck and best regards
Othman :roll:
Fixed!
Here is how I did it.
First how I made the mistake:
From the Dutch O2 site (now Telfort site) I downloaded 2 zip files. They contained 2 .exe files
·Radio_unit_upgrade_v31703.exe (xda_ruu.zip, containing program A)
·RSUv1.15(gprs_421_eng_o2).exe (xda_rsu-zip, containing program B)
I followed the instructions and the first file (Radio_unit….) was installed without problems, but the second one hung up the XDA. It was asking for the code for the SIM card at the time of error but more windows were overlaid and when I tried to remove these I must have done something that I was supposed NOT to do. The end result was that the XDA was dead as doornail. (see further description in the above link)
I searched the Internet for resources on XDA and came to this nice place. I searched using different criteria, but did not find something very useful, then I decided to create an issue and within 2 hours I had a response (Thanks FROG). It was the link you have above and here I found the solution. I did try to follow the exact path described but as usual the case is, my situation was not exact the same, but I still recommend reading THE FULL THREAD and my description before doing anything. Be sure you understand what you are doing, I think it is quite easy to make things worse, but if you are careful you should come out with a working XDA. I did!.
BEFORE YOU START DOING ANY THING, TAKE A BACKUP OF THE NON FUNCTIONING XDA. (look at this site for description of the wallaby-bootloader)
If everything fails you can at least restore the XDA to the initial error state, either if you need to perform another try or if you are “throwing the towel into the ring” and send the XDA to official repair.
Here is what I have learned.
To me it looks like the “Radio_unit….” File is the upgrade of the operating system, that’s why it is so big (15MB) and the “RSU….” Is an upgrade of the phone (which I have read somewhere here is using a separate CPU/thingy). To me it also looks like the “RSU….” File and thereby the phone part is somehow connected to the control of battery and recharging of the same, because one of the things I noticed was that the little yellow/green light that shows battery charging stopped working after the failed installation of the “RSU…” file, and during the whole recovery I had to struggle with having enough power on the XDA to perform the tasks at hand.
So a piece of advice, get the thing fixed while you still have some power on the XDA and if that fails use your AC charging cable connected directly to the XDA during the fixing of the problem. The fixing involves using the SD card as a boot mechanism and inserting and removing while having the power cable in is a bit tricky but manageable.
Power level on the XDA is obviously very important, one thing I have noticed is that it is impossible to switch the phone back on again if there is too little power on the XDA, to get it to switch on I will always have to connect the XDA to external AC power. As soon as it is on, I can disconnect and use the phone quite happily. So there is something fishy with the phone and battery power level.
I have later seen on another site that you are supposed to close the phone BEFORE installing the phone update. I did not do that, maybe that was the reason for the failure.
Here is what I did.
First step is to get the PC and XDA to synchronise again.
In my situation the XDA was so dead that no connection using the cradle was possible and then the only other way to get information into it was through the SD card.
First I downloaded the recovery.zip file from http://www.xda-developers.com/repair.zip.
It comes with a small explanation. Basically you place a file and a subdirectory containing another file on the SD card, and then by inserting the SD card in the XDA you can boot the XDA.
To get the XDA to a point where he will accept the SD card, you need to have a To-day screen showing, it will not be a working screen but at that stage the XDA should be able to locate the SD card and boot.
To get the To-day screen try soft-reset (the small pinhole on the left-hand bottom side of the XDA) and be patient, my XDA was very slow under the whole recovery operation and remember to give him power using the power cable not through the cradle.
You might try pressing the volume button, it did nor help in my situation, but I do not think it makes anything worse.
When you have the non functioning To-day screen insert your SD card (with the recovery files).
The XDA starts doing something, you see a progress bar, but it stops after 1% is done with a flash error. The trick here is NOT TO PRESS THE OK OR CLOSE THE ERROR MESSAGE WINDOW, just let it be as it is, showing the message.
Put the XDA in the cradle (and put the power cable back on the cradle too). What we are trying now is to get a working connection going with the PC. Here you have to be a bit creative, like taking the XDA out of the cradle and put it back in, maybe click somewhere outside the messagebox while it is in the cradle or when it is out of the cradle, but again DO NOT CLOSE THE ERROR MESSAGE WINDOW.
If you cannot get this to work, you can try to change the RSUpgrade.sa.cab on the SD card with the other one from the recovery.zip file (as suggested in the documentation coming with the recovery.zip) or by copying the file you were trying to install with the “RSU…” file. In my case it was placed under c:\program files\PROGRAMME B, or just search your whole PC for a file named “RSUpgrade.sa.ca”.
At this stage you should have had a successful syncronisation with your PC.
Every time you start your XDA it will try to finish the failed update and we do not want that to happened. As described elsewhere (see link above) there are several ways of doing this. What I did was renaming 2 files in the windows directory on the XDA.
You should now be able to view the content of the XDA from your PC (no magic in this, this is what you always have been able to do. You have a mobile device icon when opening “My Computer”) , open the windows directory and look for 2 files named RSUpgrade.exe and RSUpgrade.cp64.
Either delete or rename these 2. This will prevent the XDA from trying the upgrade again when you soft reset it.
A bit of ordinary info:
As in windows on your PC, you have a “startup” directory under the “windows” directory. In the startup dir. There is a link file to the RSUpgrade.exe file. This is how the XDA starts the upgrade every time you “boot” the XDA
Remove the SD card from the XDA and softreset it.
Put the XDA back in the cradle and hopefully you get a connection to your pc again.
Now run the installation of the “RSU…” file again, YES the one that failed the first time, we need that to be finished to get back to a working XDA. During the installation, a check on the power capacity of the XDA is done and if less than 70% loaded, the installation will stop.
If this happens, have patience while you recharge the XDA, at this point in time the yellow light should have come back on so now at least you can follow the power loading progress.
After this my PDA part worked but the phone would not switch on, I tried different things including a good whack with a big hammer…. After I had bought a new one (just kidding!), anyhow after a while I decided to try something totally different namely installing the much acclaimed XDA developers special edition ROM and after installing that I was asked if I wanted to open up my phone for access from other parties (or something like that) Boldly I answered YES and LOO AND BEHOLD, my phone was suddenly working (It is something with the SIM lock I think. But anyhow I can recommend the Special edition, if not for anything else that it makes the phone works, but it actually comes with a lot of nifty software. Recommended!
Now is the time to read the whole tread attached (if you have not already done that) and then, good luck.
Related
First of all, I'd like to say this is the most positive and progressive forum I've ever joined on the internet so far. You guys not only rock, but also inspire, for which I would like to add to the THANK YOU chorus!
I have spent days and sleepless nights browsing this forum, trying to unlock my T-mobile MDA.
The details are:
-T-Mobile (USA)
-ROM Version: 3.14.40 ENG
-ROM Date: 11/26/02
-Radio Version: 6.18
-Protocol version: 324e4
-Model No.: PW10B1
-IMEI: 35031400086966009
I'm using the USB via the cradle. The XDA unlock gives me an error reading, which is not uncommon elsewhere in this forum. I had to download the SER v 1.2.
Upon download and installation, I copied (via OSImage Tool)as per instuctions and ran programme A, only to get the "error message 007 ....No ROM image file".
At this point I'm pretty exhausted, especially when I see other posts of people who successfully unlocked theirs. I give up on foguring it out myself, so I please need help. Apparently, I'm a total rookie in this field . It would be highly appreciated if someone can be kind enough to please give me a step-by-step guide on the entire process either by replying to this post in this forum or by anyother means to contact me (e-mail, IM, etc) through my profile. I'll have a great sense of achievement and happiness gaining my freedom by eventually unlocking my device this weekend before my trip next week.
Thank You and I appologise to anyone that might be offended by the length of this post :wink:
You can run the file from your desktop, make sure you are synced with the xda, it will update the rom through the usb port. Before you do this it would be a good idea to back up your current rom using the sd bootloader method. Once the special edition rom has completed, just poke the unscrewed top half of the stylus in the hole on the bottom right of your xda, just poke once, wait one minute then poke again. You should tehn have an unlocked xda, you can then restore your original rom by inserting the sd card with your original rom, entering bootloader and pushing the action key when prompted.
Thanks for the response. OK, first, what ecxactly is the bootloader and the "bootloader method'?
Secondly, I tried running the S E ROM and keep getting the error message relating to its inability to find the ROM image.
Where did you download from, what size is the file? The bootloader method is accesssed by pushing the reset with the stylus while holding down the power button, then press the top left key on front of xda, you will see options there, you will not see these options when you restore a ron from sd, all you need do is enter bootloader, the xda will ask if you wish to program the rom, you press the centre of the 4 way jog button and away it go's.
I downloaded from:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
It seems to be a 15.4MB file
The file size is correct, you should be able to sync your xda, click on the special edition rom .exe file and it should install to your xda using program a, there is need to use any other tools, as\long as you have a backup of\current rom you have a way back to your original configuration.
I have just downloaded and executed that same file, the first thing that comes up is winzip self extractor, once it has unzipped itself a dos box pops up, it then jumps to program a and commences the install, make sure you are running the file direct from the directory and not from a shortcut, it definitely works.
I did that and I keep getting that bewildering error code 7. Again, I tried unzipping the file first and then run prog A. It went fine until after step #3 then error code 12 pops up: "ROM image is not compatible with my device.............. download utility nd try again...."
This thing seems simple and works for everybody else but me :evil:
at this point, you should use winzip or winrar to extract a file named nk.nbf frim the exe you downloade. then to either use the XDAtools to copy it directly to your XDA ROM, or move the file to SD card using your xda then use the SD flashing method from the bootloader.
good luck ...
Good news & Bad news ...... I was able to run the SER prog. First, I ran the adaptrom file and then programme A. Everything was proceeding fine until it was about 50% and then my system (desktop) froze/crashed. I had no choice but to restart the system. Now the XDA screen has a display with a progress bar and the message: "Upgrading........ It will take about 5 mins.........."
It seems its a curse :twisted: but since I've made some progress, I cant give up now. So I'm determined to succeed by fixing this stuff. My question is Can someone please tell me where to go from here??????? As usual, your patient and kind response is highly appreciated.
Oh, I forgot to add that in addition, now ActiveSinc cannot establish communication with my device, even after restarting it several times and trying to get connected via its program
hey ... no big problem ... relax!
you have to get SD reader/writer and connect it to your PC. move the extracted nk.nbf file to the SD card then insert it into the XDA. goto the bootloader mode (power + soft reset) it should recognize the card content ... just press the middle of the rocker key (action) and you will see hex counter increasing from 000 to 200 ,.. at the end, press hard reset and after 60 sec press hard reset again.
note: make sure your XDA is > 80% charged before start!!
good luck.
Didnt Work
Did exactly as you suggested, but ending up with the same screen "uploading..... It will take about 5 minutes..." :?
Finally made it!!! Thanks guys for all your input. Device works fine, so far, I dont seem to have lost anything! I feel FREE, excited and victorious!!!! YEAHHH!!!!!
ok...I'm really new to all this so please show a little patience towards me!
I was trying to load the XDA-developers-SER-v12 on my phone and just when it started with the progress bar moving at the top of the PPC screen, when it said "Do not Remove Device..." I accidently lifted the phone out of the cradle as dumb as I am...! After that I tried to hard start it by shoving a pin on the hole in the right side under the battery icon with the cross (hard-reset) and got the Bootloader 5.17 screen with the three colors and GSM (OK) there when I pressed the soft-reset and power buttons simultaneously.
But since I was the idiot and could not understand what was going on, as I was not in this forum nor even behind a computer, I reset it again and again a couple of more times. Now present situation; I have the same "Do not Remove..." screen everytime I do a hard or soft reset even if I keep the power on/off button pressed alongwith pressing the hot or cold boot buttons on the left and right corners respectively. In fact the screen has gotten badly distorted but the same "Do not Remove..." comes up in the totally distorted state on the screen and the Bootloader or the colors, nothing comes up anymore.
When I try to put the phone on the charger, the light goes orange just as if it is charging, in fact, after an hour or so, just as it normally would in the correct phone state, it turns green.
Is my phone toast or can I still do something about it?
Munz.
I'm no expert, but it seems to me that if there is a complication with the software when loading, one should try using the sd method of rom flashign. Cook or dl a rom, use XDA tools to load it to an SD, put the SD into the device, and then use the bootloader to load off of SD. Other than that, I know little to nothing.
Good luck!
Search in the forum after SD Card flashing for the Wallaby.
This would fix your device...
HTH
Stefan
Re: Dead SX-56
You guys are good and quick....but!!! As I mentioned, I can't even see the Bootloader even after a reset and power button combo...nothing comes up or happens...the screen just blinks and then goes blank...should I open it up and disconnect the battery or something...? Right now I am just seeing the screen saying "Do not Remove...." and that even in a totally distorted form....
Try pushing a pin in the hard reset, push once only, leave it overnight, I think that is good as removing battery as it disconnects the connection between battery and mainboard as fas as I know. Next morning push once with oin again, you never know your luck. Its weird that the bootloader should be affected however the good thing is that your gsm seems ok and the xda is charging.
XDA Dead!
Thanks for the reply...I have just pushed the pin and am leaving the XDA in that state for the whole day...hope it revives back...its presently just giving me a garbled screen and nothing else...even when I press the power and hard reset together, it comes back to the garbled screen and nothing else...I'll take your advice and not touch it after the above for the day and let you know what happens, if there is any other advice I would highly appreciate it...
Bootloader Malfunction
You mentioned that your bootloader seems to be screwed up. Download the full version of XDA tools WITH the bootloader and Programme A. Grab yourself a new ROM of your choosing, lumpistefan's kitchen, etc. Then use the XDA tools to write the bootloader and the rom to your SD card. After that hard booting the device with the SD card installed should ask you if you want to flash the device.
I noticed that if you have XDA tools without the bootloader file it will write the rom to your SD and you will NOT be able to get to the flash your device screen.
This is the only way to do it since your device will not boot to a rom. Upgrades from manufactures and roms prepared with Programme A all require MS Active Synch AND a good working connection.
If you have a SD card prepared with the ROM and the bootloader the right way, it should almost be foolproof from what I understand.
Hope this helps, I was in much the same situation
XDA Dead!
Yups! I tried to boot it from an SD Card, its not exactly an SD Card but an MMC Card (128MB). It still comes up to the same garbled screen which is more garbled than ever before! Does not ask me for anything; or even confirms anything...It does not do anything else besides the screen even after a soft reset/hard reset or a combo hard/soft power button reset.
I'm really totally stuck...Any ideas will be much appreciated!
Thanks.
Your XDA is completely dead; you screwed OS ROM and bootloader.
Forget SD or Details method, it won't work for you!
Re: Dead SX-56
Can you help me fix it please? What do I need to do?
Bootloader
The more experienced members of this forum can correct me on this, but I have been under the impression that the SD method of flashing does not require an intact OS ROM or bootloader on the device.
If you created the SD correctly, it should contain its own bootloader. Just putting it in the unit and then reseting it should come up with the screen to flash the device.
Did you create the SD card with XDAtools? Did you also have the bootloader file in the /bin directory when you did it?
If a properly created SD "flash" card cannot fix your problem, then you really might have no choice to but to get it professionally repaired where the remove the chips themselves and replace them.
I think you may even be in luck. www.pocketpctechs.com probably can do this and they are located in Fountain Valley, CA about 4 hours away from you. They can also put in bigger memory and batteries at the same time at a discount if you are getting it repaired
Re:
Thank you so much for the reply...I will try it once more; although, yes I have tried the same thing before and made the MMC Card through the XDATools, but never hurts to try again...I'll double check on the bootloader again too this time...
If you can, please send me the contact information for the people who fix the XDA's professionally as you mentioned in the USA somewhere near me preferably, I am in San Jose, CA...I'll try to contact them also...
Best Regards.
Contact Information
Their website is www.pocketpctechs.com.
You can find all the contact information right there. As far as I know fountain valley is about 4-5 hours away from San Jose.
Similar problem:
I have a XDA I here, which has a similar problem:
It boots with the welcome to T-Mobile screen, and
it shows at the bottom of the screen 4.01.16 after a while R4.06 and after a while G32S54. The machine locks-up and does not respond to anything except the touch screen. If i tap the screen, the backlight turns on, and a
rotating 'wait' icon appears. That's it. I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD.
I guess the former user has tried to reflash the unit, and had put the OS overwriting the bootloader, OTOH, the unit seems to run *some* code, since it responds to taps on the screen, by turning on the backlight.
Any guru have any clue on this one? I could not find anything in the forums, while the forums are VERY helpful in the past.
GreetingZ,
Richard
Bootloader
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Re: Bootloader
ed207_us said:
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
Click to expand...
Click to collapse
I also have a good working unit, and testing my SD card, created with XDARIT in this unit tells me i need to press power -> reset to be able to
flash the unit. if i do'nt hold the power button, the unit boots normally.
ed207_us said:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card.
Click to expand...
Click to collapse
It is there. 'press action to download ROM, or press record to exit'
ed207_us said:
<<
Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Click to expand...
Click to collapse
I cannot connect the unit to activesync.
ed207_us said:
<<
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
Click to expand...
Click to collapse
I don' know the contents of the SD, since i created it a long time ago, but i really would appreciate is if you can email me a image of yours. Hope you are right and i can use the bootloader on your card to start this unit.
email size is no problem upto 100Mb
ed207_us said:
<<
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Click to expand...
Click to collapse
<<ed207_us wrote:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. >>
<<<RichardRosenberger wrote:
It is there. 'press action to download ROM, or press record to exit' >>>
It is only there when you have the SD card in the device, otherwise you cannot find it by moving around through the different menus.
XDAArit is completely outdated. You need to get their new tool.
XDATools can be downloaded from the website here. The best thread that talks about the tool is:
http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools
The exact link to get the tool and all the supporting files, including the bootloader is:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
When you install this version of XDAtools you will find a directory called binaries. Under it there should be a file called "bootloader_v5_15.nb0"
Use the tool to create your SD card with a .nb1 file of your choice. After that it should only be a matter of powering on the device with the SD card inside the unit.
I have 2 XDAs. 1 good en 1 have problem with bootloader and rom.
I can't access Wallaby bootloader en the OS don't start.
I backup it from good XDA in the bootloader (ce+Boot) and i pushed my SD in the XDA where problems are..
He don't work. How can I fix my problem..
Please Help...
I am not aware of what the (ce+boot) actually creates on the SD card. If that is the exact ROM that you want, I would suggest downloading the full version of XDA tools, and I think you can use it to copy the ROM from the SD card to a .nb1 file on your computer. Then follow the instructions I have already posted to make the working SD card that will flash the XDA.
When it comes to the SD card, the only time I have ever been successfull is when creating it with XDAtools with a .nb1 file and the bootloader .nb0 file inside the binaries directory.
That's it. I have never been able to do it any other way. Programme A does not count since it requires an active and working OS and connection to the PC and most people that are in trouble don't have that.
Alpine R.I.P.
Hello First of all to excuse the translation for the reason that my level of English is null and I must myself serve as tools like google to translate.
I have a problem and salary if some of you happens some solution to you since I no longer have but ideas. I have tried to change to the one language alpine (xdalli) and the result has been death.
The steps:
1: Copy original ROM (in English) with romupdate.
2: To pass copied ROM to the PC with ntrw.
3: Once copied to separate the ROM in three parts (header.nb1, ext.img and trailer.nb1) with split.
4: With the publisher hex workshop 4,2 to copy the head of the file header.nb1 removed from xdalli and to copy it in the file header.nb1 of 2020i_XDII_cambio_idioma_esp_by_ferdy (ROM in Spanish). Thus we would obtain that xdalli when loading the new ROM by SD in Spanish thought that this about English when really this in Spanish.
5: Once kept the file header.nb1 modified I have mounted rom.nb1 uniting the 3 parts with merge (before divided with split header.nb1, ext.img and trailer.nb1.) So it would be left header.nb1 modified, ext.img and trailer.nb1 are the original ones of xdalli.
6: To copy with ntrw in the SD.
7: To put xdalli bootloader with the SD inside and leaves message SD download press to power to flash.
8: Once fact this and finished updating reset.
9: And here it is where one dies.
These are the followed steps, now pda does not start neither in normal way nor in bootloader nor reset nor hard reset. KO
Some idea please, although is absurd since xda does not respond to anything.
Thanks and I wait for your ideas.
PS: of brave this the full cemetery. Who would command to touch xdalli to me. jejjejeje
Does it write anything on the screen? Or nothing at all? Try to remove and insert battery again.
get into bootloader, put in cradle n upgrade your ROM. g00d luck!
p/s:Enter to Bootloader Mode by press Power + Record Button and Soft Reset.
hi clustered,
The problem is that it does not enter nor bootloader. If it entered already she would be alive.
greetings
hi server
I cannot write nothing in the screen and believe that the reason went that when doing upload before described to him loaded bootloader to me.
I have tried to leave the battery that exhausted days and when I put it in the base ignites the red light of load nothing else but.
Also I have tried to put it in load without battery and to tighten the button of ignition and nothing.
I have put myself in contact with pof to comment the problem to him and it has commented to me that a serious solution jtag and to load to him to bootloader new but not it encounter for alpine.
If some solution is happened to you but it would be arranged to make it since this dead now.
Thanks and greetings
Hi folks, i'm looking for 2 days a way to solve my DHD problem:
It can't boot anymore. It pop up the "htc quietly brilliant" screen, play the boot sound and, start this step again, and again, and again...
So I'm googling a LOT about how to solve this, if exist a way to restore the original rom. Because i'm thinking that was the problem, my original rom is gone.
That happens when i try to install 3 softwares from appbrain, my device got freeze and i hit the power button to reset. So, after that, my device is gone.
So i came here, to ask you folks: There is a way to recover the original rom ? Without send to warranty (because it spend something like 1 month here).
I'm not a mobile hacker or something, i'm just trying to be happy with my device.
Thanks a lot and sorry for my poor english!!
Perhaps try booting to the bootloader, by holding Power + Volume down button. From there, you should be able to do a factory reset, which may or may not fix your problem. Worth a shot at least, imo
And if it does not work when you do a factory reset, you can use a rom.zip from HTC RUU to restore your phone.
Now the important thing is to know which HTC rom you are running. If it is unbranded, 1.72.405.3 is a sure shot. Download the RUU.exe from Stock roms thread in android development subforum, and run it. When the window pops up, open run prompt, and type: "%TEMP%". Then search for rom.zip, copy it to your desktop, rename it to PD98IMG.zip and put it to your SD card (I hope that you have a card reader). Then just reboot to bootloader as tmh described, and watch the magic happen
Then if your phone is branded, you can still use the same technique to make PD98IMG.zip, but you have to get the RUU that matches your branding. There are lots of RUUs in android development subforum, just search.
Hi guys,
thanks a lot for quik reply!
I perform the procedure indicated by tmh, but without lucky ;\
I think it is unbranded. I buy it at Portugal and i'm using at Brazil right now.
I'll perform your tip jkoljo.
I'll post a repply to let people know if it works or not.
Thanks a lot!!
Hope the advice the last guy gave helps , a factory re set may work fine and fix the issue. Iv had 3 dhd since the day of release , the second one I had wouldn't switch on, had it replaced by Vodafone . Not sure weather or not they will give you a new one . Hope u get it fixed
Sent from my Desire HD using XDA App
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
dogasantos said:
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
Click to expand...
Click to collapse
the different is just the radio version. just try flash one of them and see if that work.
WWE means World Wide English, which is an international release
Any one of those RUUs you linked is ok, as hedayat7 already said.
WWE is World wide English...so both are english Roms...try the RUU flash, it should work like a dream....
jkoljo said:
Download the RUU.exe from Stock roms thread in android development subforum, and run it.
Click to expand...
Click to collapse
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: http://xdafil.es/index.php?path=DesireHD/RUU/
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
jkoljo said:
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: ...
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
Click to expand...
Click to collapse
But i did that.
The "1.72.405.3" files at this URL are broken (Or need password to access it, because "You don't have permission to access" message pop up).
When i run the RRU i got two screens, first i must accept a advice, the second one ask if I have a USB connection to my device. Even when i proceed to next step, i got no .zip file on my %TEMP%.
Im lost because of that lol
UPDATE: OK I FOUND IT! haha ty
Thanks a lot my friends,
but it doesn't work.
I perform the process for 2 different roms, and it doesn't work.
Still can't boot.
I'll sent for warranty and wait a loooong time..
But thanks a lot for help me with this!!
Ok, then there is something wrong in the device itself. You have to send it to a service center.
Sent from my Desire HD using Tapatalk
Hi again,
i keep a little hope that i can restore my phone, so i found a possible solution:
OTA update.
At "showthread.php?t=667728&page=2", i found a guy with the same problem i think, here is the quote:
Kinma said:
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
Click to expand...
Click to collapse
(thanks Kinma for the feedback)
So, i start a search for OTA update file here, and found at "showthread.php?t=885996".
But when i choose "Apply sdcard:update.zip", i got INVALID OPERATION.
Someone have a tip for me about this?
Thanks (its very sad, but i must keep hope).
dogasantos said:
(thanks Kinma for the feedback)
Click to expand...
Click to collapse
You are welcome.
What happened was that after a reboot of the phone the phone started rebooting in the boot sequence, i.e. a boot loop.
I tried a lot of things and nothing worked.
Finally I suspected that the problem might be with the SD card. I had a backup, so I had no problem doing a factory reset.
Then I booted the phone without the SD card.
The phone booted fine.
That way I was certain that the problem was with the SD card.
I had 2 partitions on the SD card, an EXT3 part and the rest was a normal Fat part.
I could still read the card, so I made a backup of all the data on the card.
Then I reformatted the card using windows.
The phone booted fine with an empty, reformatted, SD card.
Since I use Apps 2 SD, I had to recreate the EXT3 partition.
If your rom does not use this, you do not have to do this.
After recreating the EXT partition, put back all files that I want on my SD card.
My advice would be to do a factory reset and after that boot the phone without the SD card.
If the phone boots, you know the problem is with the card.
Hope that helps; good luck!
dogasantos said:
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
Click to expand...
Click to collapse
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Hi folks,
boot without the SD card, doesn't work =(
I'm really without luck with this.
I do:
- Factory reset
- Clear cache and userdata
- Boot without SD or/and SIM cards
- Reflash RUU WWE 1.72.405.3 Radio 26.04.02.17_M2
- Reflash RRU WWE 1.72.405.3 Radio 26.04.02.17_M2 SF
- erase all SD
One show was use OTA update.zip, but at this step i got "invalid operation"
SO, nothing works!
Well, it appears a lost battle =\
thanks folks for all help.
Yeah, there must be something wrong in your device itself, for example a motherboard fault. Send it back to HTC.
yukinok25 said:
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Click to expand...
Click to collapse
Hi,
I found the information extremely useful. Big Thanks
GRuti
So I have browsed the forum religiously to figure out how to fix this problem, and cannot even understand what to do, as I am just a phone reseller and never messed with these.
Anyways, bought the phone with a custom android rom, sold it on ebay, and the person said it was working and he somehow messed it up to the point where its stuck on the colored screen.
The phone connect to the computer fine. I followed this link to try and fix it
"the unlockr .com/2010/04/22/how-to-get-the-htc-hd2-back-to-stock/"
and no go.
There has to be a way I just know it.
My problems are I have no idea how to add files to the SD card, or where to even get half of these files people are talking about.
If someone would not mind helping me out I am willing to paypal them money if they succesfully help me. We can do it over the forum or I could give you my phone number to quickly assist.
I am serious in the money. like I said I dont use HTCs. I am an iPhone person, and just dont know how to function it. I am very tech literate so I promise it will be easy to walk me through this! Thanks in advance
bwyand92 said:
So I have browsed the forum religiously to figure out how to fix this problem, and cannot even understand what to do, as I am just a phone reseller and never messed with these.
Anyways, bought the phone with a custom android rom, sold it on ebay, and the person said it was working and he somehow messed it up to the point where its stuck on the colored screen.
The phone connect to the computer fine. I followed this link to try and fix it
"the unlockr .com/2010/04/22/how-to-get-the-htc-hd2-back-to-stock/"
and no go.
There has to be a way I just know it.
My problems are I have no idea how to add files to the SD card, or where to even get half of these files people are talking about.
If someone would not mind helping me out I am willing to paypal them money if they succesfully help me. We can do it over the forum or I could give you my phone number to quickly assist.
I am serious in the money. like I said I dont use HTCs. I am an iPhone person, and just dont know how to function it. I am very tech literate so I promise it will be easy to walk me through this! Thanks in advance
Click to expand...
Click to collapse
Mate,
ok Step 1. Get the serial number off the back of the phone and write it down.
Step 2. Identify if its a T-Mobile version or if its not.
Step 3. If it is your outta luck i have no experience with those Roms currently.
Step 4. If it isn't a T-Mobile and is a normal HD2 you need to download a new Rom
Step 5. Go to http://www.htc.com/uk/SupportDownload.aspx?p_id=297&cat=2&dl_id=1088
Step 5. Enter the serial number at the bottom of the page.
Step 6. Download the utility to your desktop.
Step 5. Turn the HD2 on to the 3 coloured screen your recieving
Step 6. Connect the USB Cable to your Phone and Computer.
Step 7. Select & Run the utility you just download.
Step 8. Press next until you recieve an do not touch your phone screen.
Step 9. Follow the final instructions on the page and you should have a fully functioning phone after it restarts.
If you don't mind paying service $35AUS + shipping i can do this process for you.
it is tmobile...
Couldnt I just get a tmobile rom.
Or even just flash another custom rom onto it?
bwyand92 said:
So I have browsed the forum religiously to figure out how to fix this problem, and cannot even understand what to do, as I am just a phone reseller and never messed with these.
Anyways, bought the phone with a custom android rom, sold it on ebay, and the person said it was working and he somehow messed it up to the point where its stuck on the colored screen.
The phone connect to the computer fine. I followed this link to try and fix it
"the unlockr .com/2010/04/22/how-to-get-the-htc-hd2-back-to-stock/"
and no go.
There has to be a way I just know it.
My problems are I have no idea how to add files to the SD card, or where to even get half of these files people are talking about.
If someone would not mind helping me out I am willing to paypal them money if they succesfully help me. We can do it over the forum or I could give you my phone number to quickly assist.
I am serious in the money. like I said I dont use HTCs. I am an iPhone person, and just dont know how to function it. I am very tech literate so I promise it will be easy to walk me through this! Thanks in advance
Click to expand...
Click to collapse
If you have a T-Mobile HD2, it will say T-Mobile on the top of the screen and have a red end button and a green send button. Anyway if you have a T-Mobile HD2 then go to here and download the LEOIMG,nbh file. When you download it extract it from the zip format and then copy the file to the root of a 4 gig or smaller SD card freshly formated with Fat 32, preferably the only thing on the SD card.
To format the SD card use a SD card reader and then click on start>computer>right click on the SD card and select format.
Put the SD card into the HD2 and hold the volume down button down while powering on the HD2 and wjhen you see searching let the voloume button go and follow the on screen instructions.
Send me a PM with your number and I will walk you through the process of flashing via SD card or by using the Custom RUU I have attached below.
You will have to create a folder and extract the custom RUU to that folder then place the LEOIMG.nbh file in the folder but rename it to RUU_signed.nbh. Then put your HD2 into bootloader (hold volume down button down while powering on the HD2) and connect it to your computer via USB cable. Wait for the Serial in the white bar of bootloader to change to USB and then open the folder you created and right click on the custom RUU and select run as administrator. Then follow the instructions of the ROM Update Utility.
You also need to have ActiveSync (Windows XP) or WMDC (Vista and Windows 7) installed on your computer as they have the USB drivers you need. Go to here to get the one you need aqn install it.
I formatted a card using fat 32. Put the leoimg.nbh on the card, and put it in the phone. It got past the bootloader screen asked if I wanted to update image I did, it said update complete and did nothing else from there.
Took the battery out, and same thing happend again. How do I get the phone to work now?
bwyand92 said:
I formatted a card using fat 32. Put the leoimg.nbh on the card, and put it in the phone. It got past the bootloader screen asked if I wanted to update image I did, it said update complete and did nothing else from there.
Took the battery out, and same thing happend again. How do I get the phone to work now?
Click to expand...
Click to collapse
So it booted right back to bootloader?
If this is so like I said in my PM I just sent to you, the volume down button is probably stuck in the down position.
Also if it said update complete then the ROM did flash.