Related
Hi, first post on the forum so please be gentle with me....
I have an XDA Orbit 2 which was until last Thursday working fine with the last official upgrade from O2 (Win 6.1, no idea about all the other stuff).
Whilst using the phone last week it suddenly died in the middle of a conversation. It wouldn't power on at all. I took out the battery, waited a couple of minutes, put the battery back in and switched it on. All that happened was the phone displayed the 4 colour screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white. I repeated the battery removal exercise a few times, waiting for increasing lengths of time but nothing changed.
I had a fairly long search through the forum and have tried for a few hours now going through the various fixes suggested but I am getting nowhere.
It won't hard reset, all that happens is the message "No Image Found" appears for a very short time and I then get stuck on the 4 coloured screen with the message above.
The same thing happens if I try just putting the thing in bootloader mode.
I can't use any of the official O2 rom upgrades as the phone because all the PCs I've tried connecting to it won't recognise it over a USB link.
I've tried connecting to it using mtty, again on several PCs, but I just get a message "USB port can not open". Just in case I've uninstalled Activesync on one PC and got the same answer.
The "how to flash you polaris using the microSD card" originally looked useful but I have some problems with it.
The first is that I need HardSPL installing on the device, which I can't do because I can't get to it.
The second will be down to me not knowing where to look, but I can't find a ROM to download and copy to the microSD card as POLAIMG.nbh. I did manage to find a Win6.5 one (the HTC Polaris - PDaviet rom wm6.5 manilla 2d (core 23004) by tranminhman one) which I thought I'd try. I guess the idea was that if I could just get something working I could always reflash it again with a different ROM or maybe apply the o2 upgrade. Unfortunately the image was password protected and I couldn't find the password in the thread.
I'm kind of at a loss now so any help would be appreciated.
Cheers
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Did you do soft reset
alanazar said:
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Click to expand...
Click to collapse
Bit in bold er... cant quite understand why in iolite section as the xda orbit 2 is the rebrand htc touch cruise => htc touch find. Its in the right place.
On the side of what to do i the ony thing i can think of would be mtty and if that didnt work then try to reflash the official o2 6.1 release and see what happens when you try to do it.
You cant try to install any 3rd party roms they jsut wont flash as you dont have hard spl installed and cant do that until you have it running again.
Try the above and see what happens...
Hi Nik
I have tried just about every kind of reset, nothing has worked.
Hi Alan
If I can't get it sorted any other way I'll probably send it off somewhere but I'd like to have a go at fixing it myself. It will at least be a bit of fun!
I take then that I've posted this in the wrong forum. Oops, apologies.
Jon
You have not posted in the wrong forum look at my signature!
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
1a) Extract shipped ROM by WinRAR , take RUU Signed.nbh
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Nik Ahmad said:
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Click to expand...
Click to collapse
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
jonfsharp said:
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
Click to expand...
Click to collapse
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
have u tried this?...
turn off, pull out the battery, then put it back, charge ur phone till the battery indicators shows green (which mean it's already fully charged) then... power on ur device.
it looks like a dumb suggestion , but... i have had a same situation
(HTC KAISER, not Polaris).
if it doesn't work, then try to upgrade with a POLAIMG.nbh (take it from official HTC ROM)
in a 2G FAT32 microSD root directory.
Nik Ahmad said:
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
Click to expand...
Click to collapse
Thanks Nik
Much appreciated.
Downloaded the ROM as suggested, unzipped to the SD card, renamed the image to POLAIMG.nbh, stuck it in the phone and things got slightly more interesting.
In bootloader mode I now get a bit further. I get a grey screen which says "Loading ..." then "Checking...." then "00028002 Not allow". It then goes back to the four coloured screen as before.
However, does the fact that it is trying to read something mean that I have just got the wrong file?
I'll try a few more and see what happens.
Thanks once again, your help is greatly appreciated.
Jon
Hi oza
Yep tried all the battery pulling out stuff but got nowhere.
The ROM thing on the SD card gets further. I extracted the ROM from the official O2 upgrade, stuck it on the card and renamed it POLAIMG.nbh.
If I put the phone in Bootloader mode I now get even further than before. I get a grey screen with:-
POLAIMG.nbh -
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
OS -
Press power button to start update image
Press action button to cancel update image
If I press the power button
I get an "Update In Progress" message and a progress bar.
After about 4 minutes I get a full progress bar and :-
POLAIMG.nbh - OK
RADIO_V2 - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
Update complete
UPDATE SUCCESS
And that's as far as I've got so far.
If I take the SD card out and try a hard reset I just get stuck on the 4 coloured screen I got before, but with no No Image Found message.
I get the same thing with bootloader mode and when I just remove the battery.
If I put the SD card back in I can go through the update process but I can't do anything
else.
So, have I actually made any progress? I'm not actually sure what I have updated and what state the phone is in at the moment. Is the fact that this didn't work an indication of a hardware failure and I should send it off somewhere.
Any advice on next steps would be good.
Jon
what is ur bootloader screen says now?
IPL...
SPL...
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Try this one M-AMINES if the radio you had was a 1.59.xx radio as it has the radio included.
if it was a 1.65.xx radio then try the VLIT naked rom.
oza_crazy said:
what is ur bootloader screen says now?
IPL...
SPL...
Click to expand...
Click to collapse
Hi Oza
Exactly the same as it did when it first broke. I get the 4 coloured screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white.
No idea what the IPL is or was I'm afraid.
Jon
bally3 said:
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Click to expand...
Click to collapse
I've not been a big modifier in the past so it was just using the bog standard O2 software from the O2 website. The name of the file is "RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe" so I presume that there can be information gleaned about things like the SPL, ROM and radio versions?
Not a complete nunce, no, but so very far away from being comfortable with all this. This post was a result of a good few hours trawling through the forums looking for help. Anything I have done has been the result of a post on this site and I am very grateful that there are people willing to share their knowledge.
Anyway, as for hard spl, nope it isn't installed. I'd never needed anything like it before the phone died and now that it has died I can't get onto it to install anything.
Yes, this happened right in the middle of a conversation after a good year or so of normal day to day use. As I said, I haven't needed to make any changes to the phone so the only thing I've ever done is upgraded it with software from the O2 site.
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
jonfsharp said:
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
Click to expand...
Click to collapse
Well whatever you do dont bin it, we can always use it on the Android project if you decide to go that way.
Ok.. so lets see.. the phone is not picked up at all in windows?
If that is the case, if even a serial connection cant be made then theres issues. At this point, I would disregard all the other advice as it only applies to a hard spl device unfortunately. SD card flashing and all other radio rom flashing will only work with hard spl as far as I know - definitely safer for certain and you dont want to wreck a repairable device.
I take it, its not under warranty, for your mention of costly repair.
The important thing at this stage is a serial or usb connection from a Windows PC. I think I have heard of forcing this connection by opening the device but this would really be in the realms of profficient repairer or enthusiast.
I'll have a look but also do some searching yourself for making a connection to a Windows PC and forcing an SPL onto a phone.
I dont know whether anyone's ever managed to HardSPL a phone using a memory card? Just a thought...
Who would have known.. have a read of this and see if you can follow it up regarding the spl through sd card ..
http://forum.xda-developers.com/showpost.php?p=3273438&postcount=7
Dear all,
First of all, many congratulations for the great forum and thanks for all the support given here.
Now, I recognise that problems similar to mine have been discussed elsewhere, so I apologise for opening a new post, however with all the material that I could find, I got a little bit lost, so here is the story.
Some 5 days ago, the screen on my HTC Elf stopped responding to any sort of touch. The green, red and action buttons were working but no touch screen.
I have read several posts, and concluded that one possible problem was a corrupted ROM, so I downloaded latest Onyx ROM and installed it. Phone was upgraded successfully and screen started to work again.
However, the first time I switched it off and then turned it on again, it did not boot up. It gets to the point where it displays Smart Mobility and then switches itself off. The orange light then comes on for about 6-7 seconds, then off for 1-2 seconds, and then on again......
Now it does not seem to be able to charge, but if I switch it on with the camera button on I am able to get to the ROM screen (the 'rainbow screen'), so I have hope that it is not dead.
What can I do to attempt to revive the phone please? Is there a sort of 'format' that can be given so that one can start flashing ROM, etc. from scratch?
Many thanks.
PS: Except for the above, I consider myself as a total beginner in this area.
Hearing that the touchscreen started working again after flashing the ROM, I would conclude it's a software-issue.
In the rainbow-screen, what SPL does your phone run? If it ends with 'cmon', you've installed HardSPL. That means you can flash your phone from the rainbow-screen. Given that your phone won't boot, you should try to flash a new ROM from the rainbow-screen. But first, you have to confirm that you've installed HardSPL.
Good luck!
@mrqips - many thanks for your reply.
The screen says that:
IPL 2.20.0002
SPL 1.11.0000
xumiking said:
@mrqips - many thanks for your reply.
The screen says that:
IPL 2.20.0002
SPL 1.11.0000
Click to expand...
Click to collapse
Sorry Buddy.. It seems that you didn't use HardSPL, unfortunately you won't be able to flash any other ROMs..
Yet.. You might be able to use the Gold Card Method.. Give it a try and see what would happen..
Another point is.. I'm very interested to know how did you flash Onyx ROM.. without using HardSPL nor USPL (as obvious from your IPL), I would say that you used the "White Screen Method" which is by the way.. the least safest way..
Hope That Helped...
Thanks for your feedback.
Actually, I happened to be reading the post by @sbettencourt in this thread:
http://forum.xda-developers.com/showthread.php?t=595856&highlight=smart+mobility
Here, a step-by-step approach is given to recover the phone:
"1º [PRJ] Unbricker ROM discovered (wildcard CID and Model ID)
2º Pick any shipped ROM from this thread:
If you have one P3450 -> here
If you have one P3452 -> here
After this, with luck and good work you recover the phone...
3º Then you must do CID_Unlock... You can search how to do it on Wiki or if you want i got one steps how to do it right here and you can see one video with cid_unlock on my signature..." (pasted from the thread)
I did Step 1, and updated it with the unbricker ROM using romupdateutility, and the phone was recovered! It could load, get to Windows Mobile, etc.
Then, unfortunately, when I did Step 2 (mine is a P3450) so I downloaded a ROM from the page indicated, I tried to update the shipped ROM using romupdateutility, but as soon as it got to 2% it failed saying that the vender ID is invalid.
Now, I don't seem to be able to update it with anything - not even the unbrick ROM. What a shame I almost go there.....
xumiking said:
I tried to update the shipped ROM using romupdateutility, but as soon as it got to 2% it failed saying that the vender ID is invalid.
Click to expand...
Click to collapse
You put the shipped ROM in the same folder with RUU??? Why??? You don't need to do that...
You only need to double click on shipped ROM and the installation process begins...
@sbettencourt,
actually yes what I did was to click on the update directly.
I downloaded the file RUU_Elfin_DOPODASIA_WWE_2.20.707.1R_4.1.13.51_03.07.90_RED_Ship_Reduced.exe and executed that directly.
However, now, even this one is stopping at 2%.
Is there any hope, or have I destroyed the phone?
Thanks.
If you can't flash the Shipped ROM, you have now to try the Gold Card... Follow the steps in that Gold Card thread...
Hello everyone,
I finally managed to revive the device, by flashing it with a 'correct' shipped ROM, which did not give any errors on updating. Big thanks for all your support - you are the best!
As this starts to get addictive, and because I am now running a ROM version which dates to 12/11/2007 (2.27.468.1B WWE), what are the suggestions for upgrading the ROM please? My device is an ELF0100.
Thanks again.
Coool Now try to keep him alive
Very true
I managed to flash it with Onyx Ultimate 4.8 (10/07/2009) and it seems to be performing splendidly.
Thanks for all your help.
Good Job
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Did you try another SIM?
rpimps said:
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Click to expand...
Click to collapse
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
simplistian said:
Did you try another SIM?
Click to expand...
Click to collapse
I did that just now and it had the same problem (on the HD) no matter what sim I put in it.
Mastoid said:
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Click to expand...
Click to collapse
Here's what I did today:
1. Reflashed HSPL. Hard reset.
2. Couldn't find a working stock rom so I just reflashed Dutty 3.9XT. Hard reset.
3. Installed 1.17 radio and rilphone 1.14 like you recommended.
4. Didn't install anything else. Tested phone right after install and it's still having the problem.
barisahmet said:
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
Click to expand...
Click to collapse
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
rpimps said:
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
Click to expand...
Click to collapse
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Mastoid said:
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Click to expand...
Click to collapse
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
Unfortunately, it breaks the warranty aggreement. So e-bay is a good idea, I guess.
P.S: I heard from someone that you can go back to stock rom then you can still use your guarantee. But I'm not sure if they can see that you reflashed it or not.
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
From what I have read, if you flash back to the exact stock ROM which was installed on your phone when you had received it, then this will not affect your warranty - if you decide to return your phone (assuming it is still under warranty) just make sure you downgrade to Stock ROM and Radio version, with no trace of HSPL or USPL also, or else you will have to pay them money if they (HTC) find out
EDIT: Please follow these steps to restore back to your stock ROM version:
1. First, be sure to restore your stock OS, and then the stock radio. The Stock SPL is always to be done last!
2. Download your choice of a stock spl package from the link shown below. (currently 1.13, 1.14, 1.15, 1.54)
3. Also download the original hardspl from the link shown below.
4. Run the hardspl exe but do not click anything in RUU yet. Just let the hardspl EXE extract the files for flashing.
5. The SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
6. Continue with the RUU (or if needed, run SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen), it goes to 100%, reboots, done.
7. To verify, enter bootloader mode, see version number on tricolour screen, should now just say 1.14.0000 or any other version ending in .0000, but not ending in OliNex!
that's it.
Please refer to the following link for more information and the necessary files you will require to re-flash back to Stock (see and read the last section of post #1):
http://forum.xda-developers.com/showthread.php?t=431217
Regards.
p.s. also remember to flash back to the original Radio version of the phone, if required.
There are several stock ROMs linked in the Blackstone Wiki, flash back to one of those and see if your problem is still there. If it is, send it back for a Warranty repair - as long as there is a stock SPL and ROM image on your phone, you Warranty will be intact.
what i dont see is mention of ho u are answeing the calls.
there or at least three ways
1. the on screen prompt. i assuming this is the one that freezes
2. the answe key at the bottom left of the phone
3. the htc headphones im assuming you have
have u tried using all three of these methods to answer calls??
I will return my HD2 to Tmobile (USA). I flashed a custom splash screen rom and now need a original splash rom change it back, or anybody know how to delete it and it will work too ( I still have 1st screen and animation from tmobile when it boot, but there is a extra picture between them). I did a lot of research, but I couldn’t find it. Could anybody here help me out?
cool00 said:
I will return my HD2 to Tmobile. I flashed a custom splash screen rom and now need a original splash rom change it back, or anybody know how to delete it and it will work too ( I still have 1st screen and animation from tmobile when it boot, but there is a extra picture between them). I did a lot of research, but I couldn’t find it. Could anybody here help me out?
Click to expand...
Click to collapse
I covered this in a thread I wrote for the TP2, as these devices are the same resolution, the steps are almost the same.
Check out the "Step 6" section.
Dave
cool00 said:
I will return my HD2 to Tmobile (USA). I flashed a custom splash screen rom and now need a original splash rom change it back, or anybody know how to delete it and it will work too ( I still have 1st screen and animation from tmobile when it boot, but there is a extra picture between them). I did a lot of research, but I couldn’t find it. Could anybody here help me out?
Click to expand...
Click to collapse
There are a few questions before you proceed.
1. Did you HSPL your phone? If so you need to take that off (for turn in) and flash the original ROM from your SD card (this will remove HSPL).
Please see this thread for how to do this> http://forum.xda-developers.com/showthread.php?t=655653
The 2.10, (not 2.10.1), 2.11, 2.13 all have the required splash screens included in the ROM's for Tmo US
2. If you did not HSPL your phone then see the above post. Most of the SPL screens are generic for HTC.
Yes, I did HSPL and tried 2.10, 2.13, but it couldn't remove 2nd screen (extra one).
Thank you, Dave. I read your artical and it is helpful. It is complicate for me to do it by myself. Do you have an easy way?
cool00 said:
Yes, I did HSPL and tried 2.10, 2.13, but it couldn't remove 2nd screen (extra one).
Click to expand...
Click to collapse
Not to doubt you but the 2.13 Stock ROM overwrote all these screens... I had custom ones on my cooked ROM's and it cleared them out.
But I'll throw you a bone ;-) go here:
http://forum.xda-developers.com/showthread.php?t=625911
down near the bottom of the first post is the originals.
I installed LEOsplash_Stock.zip, it replaced stick together screen. However, the extra splash is still there. After I flashed 2.13, 1st from Tmobile came back, other thing wouldn't change. What else I can do for it? Thank you. By the way, I couldn't install HTC HD2 BIOS Boot Splash Screen DEFAULT.cab.
cool00 said:
I installed LEOsplash_Stock.zip, it replaced stick together screen. However, the extra splash is still there. After I flashed 2.13, 1st from Tmobile came back, other thing wouldn't change. What else I can do for it? Thank you. By the way, I couldn't install HTC HD2 BIOS Boot Splash Screen DEFAULT.cab.
Click to expand...
Click to collapse
The first boot screen has to be flashed... The archive should have a ruu_signed.nbh file inside. Here is what I use: - Remove the TMobile "pink" Spash screen, post #5.
In fact, I already returned my phone to tmobile and do have chance to try your method. Thank you for your input.
Hi all, i need to send my lovely hd2 for a SAV...but as many, i changed lot of things on it!
I searched every where but couldn't managed to find a stock splash image.the second one that comes up with all the writtings at the bottom.Who can help me?
thanks a lot
the stock roms generally don't have a second splash, they just show the first for twice as long and the writing appears half way through.
if you (like i did) flashed a second boot screen, or you used a cooked rom that includes a second splash, you now no doubt have found that flashing a stock rom hasn't removed it. you will need to make a duplicate of the stock first splash and flash it as a second. i had to do this with my o2 hd2.
some info on how in my sig (the watermarking link)
Okayyyy, thanks a lot! i was starting to feel lost as i reflashed so many time without making it!lol!
Now my prescious will be able to get it sensivity back....
By the way, maybe you know about this:
I used a froyo desire hd android rom and since then i'm unable to use the touch screen. Thehardware buttons works awsomly(even better than they ever did) but the ttouch screen just keep taunting me like: no no no,i won't anwser!it's kind of frustrating!
Do you know about this?
Thanks again guy, you're just incredible
sorry, i know nothing about android.
ok no prob...I'll just send it back and see how it goes.
but first, i don't understand how watermarking can help me duplacating the first splash book?can you explain please?the thing is that i don't know how to duplicate the first splash...
you need to find the splashscreen as a bitmap .bmp file (there are several threads with various stock images, or you can probably make one, i did for my o2 return) and use the method in my watermarking thread to flash that image to both the first and second splash locations. this will then look like one splash when you send it for repair, so they wont notice anything. (Theyre really only interested in the spl anyway, you can probably get away with just using a standard htc splash even on a branded phone)
blpowder said:
ok no prob...I'll just send it back and see how it goes.
but first, i don't understand how watermarking can help me duplacating the first splash book?can you explain please?the thing is that i don't know how to duplicate the first splash...
Click to expand...
Click to collapse
Depending on what boot screen you need, I might be able to help you out. If you need the plain white HTC splash (found on WWE devices) you can download the second-level splash from my sig.
sumflipnol said:
Depending on what boot screen you need, I might be able to help you out. If you need the plain white HTC splash (found on WWE devices) you can download the second-level splash from my sig.
Click to expand...
Click to collapse
Yes i'm looking for the stock splash screen...if i flash yours, will it revert the first splashscreen or the second one(the one i need)?. If it doesn't could you jus post the splash screen image?i 'll flash it by myself. Thanks a lot for all your help
By the way, do know about android on hd2?maybe you could help me with the issue i explained few posts earlier (with the unresponsive touchscreen after a using an android rom.I tried to hardreset,go back to stock rom but nothing changed....)thanks again
blpowder said:
Yes i'm looking for the stock splash screen...if i flash yours, will it revert the first splashscreen or the second one(the one i need)?. If it doesn't could you jus post the splash screen image?i 'll flash it by myself. Thanks a lot for all your help
By the way, do know about android on hd2?maybe you could help me with the issue i explained few posts earlier (with the unresponsive touchscreen after a using an android rom.I tried to hardreset,go back to stock rom but nothing changed....)thanks again
Click to expand...
Click to collapse
I have the stock white HTC splash screen (level 2) in my sig (just to clarify, it's just a white screen with a green "HTC" logo in the middle). It's the second attachment here.
What Android build do you have? List your Android build, your radio, and your ROM.
Yep, this is the one i was looking for. thanks
As i said i return to a stock rom(sd card flashing), so i don't have any android rom anymore.nor coustom windows phone.
i used
hc desire hd rom from meedjay 3.3a
windows rom: ozdroid 1.11
radio: 2.12.50.02.2(not quite sure)
it functionned flawlessly 'till i rebooted.Then the touchscreen became totally unresponsive.Now i can only use the hardware buttons...(sounds really bad.doesn't it?) i have to mentionned that i already changed the screen for aproximately the same issue(the screen used to become partly unresponsive for a while...)
blpowder said:
Yep, this is the one i was looking for. thanks
As i said i return to a stock rom(sd card flashing), so i don't have any android rom anymore.nor coustom windows phone.
i used
hc desire hd rom from meedjay 3.3a
windows rom: ozdroid 1.11
radio: 2.12.50.02.2(not quite sure)
it functionned flawlessly 'till i rebooted.Then the touchscreen became totally unresponsive.Now i can only use the hardware buttons...(sounds really bad.doesn't it?) i have to mentionned that i already changed the screen for aproximately the same issue(the screen used to become partly unresponsive for a while...)
Click to expand...
Click to collapse
No problem.
I'm a little confused. Does your screen respond only in WM? Or does your screen not respond in both WM and Android?
If your screen only responds in WM (but does not respond in Android), then it can't be a hardware problem -- it's something wrong with your Android build. If this is the case, try a different Android build; try one that is not from the Desire HD port because that port still has a lot of bugs. If you want, you can try the phireMOD ROM (based on the Sprint HTC EVO4G) that is working for me.
Nope,
unfrotunately the screen is totaly unresponsive in both roms....the only things i can use are the hardware buttons....So i guess it's an hardware issue,but i wanted an experienced opinion before sending it....
What confused me is the fact that the phone didn't fell.i only changed the android rom( i'm kind of flashaholic!lol) then i rebooted and since the screen became unresponsive, even after many hardreset.I can't enter my pin code anymore,neither can i enter windows mobile, or android.
Now i'll just have to reflash the stock spashscreen and send my prescious for a little lifting,right?lol
blpowder said:
Nope,
unfrotunately the screen is totaly unresponsive in both roms....the only things i can use are the hardware buttons....So i guess it's an hardware issue,but i wanted an experienced opinion before sending it....
What confused me is the fact that the phone didn't fell.i only changed the android rom( i'm kind of flashaholic!lol) then i rebooted and since the screen became unresponsive, even after many hardreset.I can't enter my pin code anymore,neither can i enter windows mobile, or android.
Now i'll just have to reflash the stock spashscreen and send my prescious for a little lifting,right?lol
Click to expand...
Click to collapse
Maybe your phone just wanted to fail when you did a hard reset.
Yeah, you'll have to send it back. Just flash the stock splash screen (level 2), make sure everything (splash screen, radio, etc.) is back to stock(!!!), then flash the stock SPL.
sumflipnol said:
Maybe your phone just wanted to fail when you did a hard reset.
Click to expand...
Click to collapse
LOL!
Yeah, he wanted a brake,as i tortured him so much during the past 6 months!
Thanks a lot man, it's good to know i can count on all of you experienced guys!
I'll do as u said then wait and see!lol
Last question: can i flash the latest official rom?or will it stop me if i want to reinstall HSPL when i get the phone back?
blpowder said:
LOL!
Yeah, he wanted a brake,as i tortured him so much during the past 6 months!
Thanks a lot man, it's good to know i can count on all of you experienced guys!
I'll do as u said then wait and see!lol
Last question: can i flash the latest official rom?or will it stop me if i want to reinstall HSPL when i get the phone back?
Click to expand...
Click to collapse
No, I'm not an expert. I just learned a little bit of this stuff over time after reading on XDA.
You can probably flash official ROMs because they don't need HSPL. Get it from HTC's website so in the event your phone gets bricked, you could say you got the ROM from HTC, not XDA.