To All and specially moderator,
I recently just lost all rom image and now my himalaya are totally dead, because I try to upgrade software from a program.
Probably you have seen many of these posting from a newbie like myself. Speaking of the truth, even after browsing many hours in this forum I still have no Idea at all how to restoring my operating system.
Well, my plea is, could one of the senior/expert on this forum to post new instruction how to restore the rom (even how to upgrade to wm2003SE, one by one, not just reverting to old post) I believe many of newbie ( lack of software knowledge) have the same problem with me.
Thank you.
Regards.
Do you get anything on screen, do you have "serial", when you connect to usb do you get "usb" on screen. If yes then you just need to download original rom for your phone and restart flashing procedure. If there is nothing on screen I cant help, sorry.
Related
Hi All,
As a newbie on the block I have been reading trhough the various posts here on upgrading or updating the PPC. There is a lot to be found on what rom's to use etc, etc, but nonetheless I am now stuck after a partial upgrade probably with a m1000 that will not go any further then the bootloader.
As i gathered from other posts it's waiting to be "fed".
But the feeding is not working, with none of the realeases I tried for this Himalaya type.
All of them either lock up or bum out with an error 119, telling me to reset the device and try again...
I can keep doing this until i'm old and grey I guess as each time the same thing happens.
Anyone here have a suggestion how to get some new data into "his brain" or should I just consider the unit trashed and throw it into a wastebin ?
I am really lost here. Any help is much appreciated.
Peter
Petey said:
Hi All,
As a newbie on the block I have been reading trhough the various posts here on upgrading or updating the PPC. There is a lot to be found on what rom's to use etc, etc, but nonetheless I am now stuck after a partial upgrade probably with a m1000 that will not go any further then the bootloader.
As i gathered from other posts it's waiting to be "fed".
But the feeding is not working, with none of the realeases I tried for this Himalaya type.
All of them either lock up or bum out with an error 119, telling me to reset the device and try again...
I can keep doing this until i'm old and grey I guess as each time the same thing happens.
Anyone here have a suggestion how to get some new data into "his brain" or should I just consider the unit trashed and throw it into a wastebin ?
I am really lost here. Any help is much appreciated.
Peter
Click to expand...
Click to collapse
additionally i cannot get to the bootmenu to format registry and storage, so please, if anyone has an original rom backed up that can help me restore it, let me know.
peter
Hi all,
I have the HTC X7500 (unbranded) version. I have upgraded to WM6 several weeks ago using the method described on the forum (unlock by "IMEI check" then upgrade using ATHE100).
(on the bootloader I have:
ATHE100
IPL-v1.00
ATHE100
SPL-v1.10.RP00)
Today I tried to hard reset my device:
- I hold the camera button and press "reset"
- I have the "press action to restore factory default"
- when I do so I get "press power key too boot"
- I press the power key and the screen goes black and nothing happens...
What is going wrong? What should I do?
Thank you for your help.
Silviu
silviu.h said:
Hi all,
I have the HTC X7500 (unbranded) version. I have upgraded to WM6 several weeks ago using the method described on the forum (unlock by "IMEI check" then upgrade using ATHE100).
(on the bootloader I have:
ATHE100
IPL-v1.00
ATHE100
SPL-v1.10.RP00)
Today I tried to hard reset my device:
- I hold the camera button and press "reset"
- I have the "press action to restore factory default"
- when I do so I get "press power key too boot"
- I press the power key and the screen goes black and nothing happens...
What is going wrong? What should I do?
Thank you for your help.
Silviu
Click to expand...
Click to collapse
I won't flame you but the answer should be in the manual and is also all over the forum. Take this moment to teach yourself how to become more resourceful and find answers and become a better forum member. Good luck.
Also, to answer your question as to what you should do....read a little more as you'll need to be more knowledgeable with the device you have.
Hello,
Thank you for your reply (and for not flaming me ). I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again. However I still do not understand what exactly went wrong, why it works again now and what will happen next time I hard reset.
I had already read a lot of posts on the forum, however the learning curve is steep, and there are a lot of things to understand which are rarely explained from the ground up (most of the time the learning process must be made by assumptions and by inferring from what problems others have and how they solved them). And quite understandably I don't want to experiment too much with my device, especially when I read solutions that worked for other devices (like the Universal), and that might or might now work for mine.
Anyway, it's a shame that one has to become a PocketPC boot process expert in order to get out of such a situation, especially if one got into it without doing anything stupid (which I think is my case).
As a UNIX administrator and hacker I do know the power of RTFM, but I don't think it applies to each and every question.
Regards,
Silviu
silviu.h said:
Hello,
Thank you for your reply (and for not flaming me ). I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again. However I still do not understand what exactly went wrong, why it works again now and what will happen next time I hard reset.
I had already read a lot of posts on the forum, however the learning curve is steep, and there are a lot of things to understand which are rarely explained from the ground up (most of the time the learning process must be made by assumptions and by inferring from what problems others have and how they solved them). And quite understandably I don't want to experiment too much with my device, especially when I read solutions that worked for other devices (like the Universal), and that might or might now work for mine.
Anyway, it's a shame that one has to become a PocketPC boot process expert in order to get out of such a situation, especially if one got into it without doing anything stupid (which I think is my case).
As a UNIX administrator and hacker I do know the power of RTFM, but I don't think it applies to each and every question.
Regards,
Silviu
Click to expand...
Click to collapse
I don't believe you have to become and expert to get out of JAMs, however I do believe you better understanding what you are doing before you start flashing your phone or device with something not released by your phone Operator.
Keep in mind you got yourself into that situation when you decide you are going to unlock your phone (play with the BIOS) and flash it with a WM6 ROM (Unsupported OS). Being a Unix Administrator, how often do you play with an Ultrasparc BIOS then decide to install an unsupported version of Solaris on it.
Nonetheless the Windows Mobile device does not cost as much and it would only affect you if you bricked it. The point I am trying to make here is that what we are doing with these phones are pretty serious and if you choose not take baby steps and read carefully, then you better be prepare to purchase new device and deal with the outcome.
I am not flaming anyone, but I think people needs to understand this is serious and the Athena is not $49.99 or free with a two year contract
Mayby my post will help a little.
First : you have to have battery charged for 100% ( my a few upgrade stopped in booting proces after upgrade because battery was on the level 70% ) So try to made HR with unit connected to power charger ( not to USB in PC)
Second: Try to go BL mode , if yes you can upgrade again, try it few times
Third : Last solution is to boot in BL mode with miniSD card with Atheimg.nbh on it , the same you have try few times
As up today it helps me.
Hello,
Thank you for your help but I said above: "I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again." So things are OK for me
Besides, since then I have flashed to HardSPL, and hard-reset seems to be working OK now.
Thank you anyway and long live the forum
Silviu
Hi,
Sorry to stat a thread on this but can't find anything similar.
I've flashed a lot of ROM's prior. Thought I was fairly comfortable with it.
Currently, I have EnergyROM 6.5 and wanted to try another.
I can establish the connection with phone/computer (1st beep), then the second beep happens (activesync). Then I run the AthenaWrapper and it starts. It restarts the phone. I hear the first beep but never the second. The progress bar stays at 0% and eventually there is a communication error.
This happens with NATF's 6.5 ROM as well as the stock ATT rom.
Any suggestions on fixing this problem?
PS - the 'contacts' button at the bottom of the home screen... are those remapable? I have a mandatory program (Good Messaging) which has its own contacts program. Once I've installed it, the contacts button goes to it instead of the built-in contacts. That's not what I want.
Chris
txemsdoc said:
Hi,
Sorry to stat a thread on this but can't find anything similar.
I've flashed a lot of ROM's prior. Thought I was fairly comfortable with it.
Currently, I have EnergyROM 6.5 and wanted to try another.
I can establish the connection with phone/computer (1st beep), then the second beep happens (activesync). Then I run the AthenaWrapper and it starts. It restarts the phone. I hear the first beep but never the second. The progress bar stays at 0% and eventually there is a communication error.
This happens with NATF's 6.5 ROM as well as the stock ATT rom.
Any suggestions on fixing this problem?
PS - the 'contacts' button at the bottom of the home screen... are those remapable? I have a mandatory program (Good Messaging) which has its own contacts program. Once I've installed it, the contacts button goes to it instead of the built-in contacts. That's not what I want.
Chris
Click to expand...
Click to collapse
I had no idea what "Athenawrapper" was until I Googled Athena. The good news is I've solved your problem. The bad news is that you have a PEBCAK
error.
"Athena" is an entirely different piece of hardware from a Raphael , so it's RUU WILL NOT WORK with a Raphael. Frankly, I think you're lucky you didn't succeed in bricking the phone completely. You need to use the RaphaelWrapper to flash a Raphael.
On the off chance that you actually have an Athena, and are trying to flash it with a Raphael ROM, then you're still begging to have your hardware bricked. Most ROMs are not compatible outside of the hardware for which they are written.
You need to:
Figure out what hardware you have.
Go to that bulletin board.
Read the sticky threads there to learn how to flash properly.
Get to work.
Hi,
Well your explanation makes sense... however, the stock ATT ROM I downloaded from the raphael ROM development section and have successfully flashed a prior Fuze with before (I had to return it for warranty). It is the same file that worked then, that is not now.
But it is not working now AFTER I tried the NATF ROM which I'm pretty darn sure I directly downloaded from a link in the Raphael section. Perhaps it was a misguided link or something, and then it damaged the phone such that previously working ROM's now won't flash?
Chris
addendum...I know for sure it was the NATF ROM from Raphael section...
it is here http://forum.xda-developers.com/showthread.php?t=539513
If you did a HardSPL to load NATF's ROM, then you cannot flash back to the OEM ROM without first removing HardSPL.
So (and this is the second time in as many days ), here's my recommendation:
Myrddin Wyllt said:
Here's my recommended procedure:
Back up your PIM data, if needed.
Remove HardSPL.
Run your service provider's ROM installation.
Install HardSPL.
Download the NATF ROM (YES...DO IT AGAIN)
Flash the ROM.
Hard reset when you get to the screen alignment.
Yes, I know I'm yelling, but that's because you don't appear to be paying attention.
It would also be helpful if you'd put your device info in your user signature.
Click to expand...
Click to collapse
Re-downloading the NATF ROM ensures that you don't have a corrupted copy.
Myrddin,
Interesting name, how do you pronounce that?
1) I learned from you today about the HardSPL having to be removed. That I did not know, so thank you.
2) Back on the computer I flash with, I confirmed the wrapper files... first line does say Raphael Wrapper, under that it says Athenawrapper, then under that it says LSD creations.
3) I'll assume since you quoted your previous advice, the yelling and not paying attention comments were not directed at me
4) I'll do what you instruct master!
That's why we like the wise sages of the forum!
chris
It's Welsh, and it's pronounced Merlin, most of the time (Merthin is more accurate, though).
No, the yelling was not exactly directed at you, just at newbies everywhere. Take no offense, I merely wanted to place a great deal of emphasis on certain aspects of the process. It helps us help you.
M
Hi,
Well, somehow I managed to get back to the stock ATT Rom. I'm not sure how to remove HardSPL specifically as searching that topic doesn't bring up any specific threads (at least in the Raphael forum).
I thought since I had got the ATT rom to work, I coul ddo a 6.5 ROM, but I'm running into the same communication error I had before.
Very specifically, everything starts up fine. It causes my phone to restart.
The USB connection noise happens, but then I never get the activesync alert noise, so the download indicator stays at 0% and I get a communication error.
If I just plug my phone into the computer, it starts up activesync just fine.
Any suggestions? And if it is HardSPL, where's the instructions to remove that?
Thanks again,
Chris
Well shoot,
It must be my lucky day.. I did find some instructions for hardspl, did that.. and I think things are about to be working...
Nevermind on the last post for now!
chris
Hey everybody,
My phone is stuck in an infinite restart loop when i tried to revert back to the original rom without replacing the hardspl. Is there anything that can be done for that?
glz88 said:
Hey everybody,
My phone is stuck in an infinite restart loop when i tried to revert back to the original rom without replacing the hardspl. Is there anything that can be done for that?
Click to expand...
Click to collapse
Most often this is the result of a bad flash or a corrupt ROM. Try putting the phone in Bootloader mode (see the wiki for instruction), and download the ROM again (delete your old copy to avoid confusion). Try the flash once more, and don't forget to do a hard reset when you get to the screen calibration the first time.
Hello everyone,
That's my problem:
almost a year since I turned in different custom rom, which had never caused any problems. Then my screen started to lose its sensitivity, or even move all alone. So I recommend it as everywhere trying to return to the origin.
I am currently in the 2.1 HTC last updated.
The screen is much better. But I want to return to 1.5, to really be sure I completely reset.
And that's where the trouble begins. Unable to install the HTC RUU, always the same error (Error 170: bad version of bootloader), whereas it normally means a problem with drivers. I checked several times these drivers, be it XP or Win 7 64. Always the same message.
And then I fell in that you (really sorry) I had completely forgotten. So I tried to follow the tutorial "How to restore the firmware of the HTC hero.
There can not run the commands, I put: "Into rebooting bootloader ... FAILED <remote: allow> not verbatim or 'downloading' boot.img '... FAILED <remote: not allow>
And I do not see what I could do differ between the two responses.
I'm starting to believe I'm even more noob than I thought.
I guess the question has to be asked of you, but then it starts making long as I want and I can not find.
I see no reason why it does not work because he sees in fastboot My phone devices.
Does anyone have an idea for the method I should follow or tell me why this command does not work. (Although for lines order Now began with the first root of my phone, then virtually unknown).
If there is already a topic or a wiki, thank you for giving me the links if possible.
Counting on a pretty fast response from you all.
In advance thank you for the help you can give me.
PS: sorry for the novel, but I think I managed to summarize all the parameters of my worries.
PS: I think I have tried all methods so far found only one positive is that I'm sure my drivers, still appears in them because MyHTC, it is in bootloader or in sync.
Sorry for my bad english but it's a traduction for google.
Replied in thread above pal.
Sent from my HTC Hero using XDA App
Hello there!
My first post here so at first: thank you, community. I am using your knowledge since a years. Mostly with Galaxy S3 phones.
This time i got very special i9300. I was resurrecting it few times, all of them with (partly or fully) with XDA help.
Issue: I flashed LineageOS without a backup. Phone lost connection (bad wire) and gets bricked. That's not a first time, but now i really don't know what to do.
So the question is: could i repair basic files without JTAG, like trough Linux or something? Or could anybody link me a image of files, that i could put on SD and try to repair software?
Now while flashing i got "There is no PIT partition". Therefore i am not able to flash anything, includin' PIT. Phone gets into Download Mode, but without - white screen with lines, like broken TV. Before wiping it has boot-loop.
I am expecting an instruction of things, step by step, what should i try. I will answer in one post with results of each of them. I think that it could be helpful for persons with similar issue (instead of looking in hundreds of topic, like i did).
This phone i bought in Nederlands, but it works in Poland. Since this day it has 3 times loosing IMEI, 5 times bricked, two times loosing PIT partition. Each time i found a way to resurrect it, but this time i am totally confused. I was trying a lot of ways and i just lost a bit within which i tried, in which combination. I was using different version of Odin, ect. I remember that once, when i lost IMEI, flashing was failed with v3.09 and worked with 3.07 (same files).
I hope that we will try last time with these Frankenstein (trust me, it is). If it fail - maybe someone needs original display or some parts, i have 3 motherboards (2x i9305).
Best regards,
Bartłomiej
Skitt01 said:
Hello there! My first post here so at first: thank you, community. I am using your knowledge since a years. Mostly with Galaxy S3 phones....
Click to expand...
Click to collapse
I don't have this variant but, I believe that one or more of the following, device specific, threads should be helpful for what you need and don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=1916796
https://forum.xda-developers.com/showthread.php?t=2535367
https://forum.xda-developers.com/showthread.php?t=2798642
https://forum.xda-developers.com/showthread.php?t=2218825
If all else fails, try posting your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2690307
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.