Good Morning all,
Hope everyone is well. I realise that I am probably repeating a post somewhere and apologise profusely for that.
However my request is quite urgent. I have my phone flashed with Dutty's 4.1 using the step by step guide to update radio and ROM etc etc.
My touchscreen has now started playing silly buggars and as such tomorrow it gets picked up by UPS UK to disappear off to be looked at. Obviously I do not think they will take it to well if it still has duttys on there
So just so I make sure I get eveything right.... can someone just drop me a link to the correct files for a stock flash back to the way things should be.
Thank you thank you thank you thank you thank you thank you
Jody
To add an update, the boot loader screen shows:
BLAC100 32M
SPL-1.56.OliNex
Micro-Blackstone (LED) v6
Thought this might help in finding out how much work to stock?
I Think u need the original rom... or a htc one from the website?? ... can it not be downloaded from the htc website?? i may be wrong
I do but also need to make sure I do an original spl and radio as well
first off go to htc.com and download the romupgrade thats on that side (ive non is on the side check the wiki for youre countryrom)
then flash that one and se ive radio comes with it
ive not flash radio 13.**.**.**
then from the hard spl thread there a tut how t make youre spl stock again and youre finished
This is the last official ROM with 1.56 spl and 1.13 radio
h..p://rapidshare.com/files/231263089/-HTC_Touch_HD-MR_2009-RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship.exe
Ok, thanks for all your assistance. Just qiuck one, Once I have done all this how can I check it has all worked. Obviously the boot loader shows the SPL, and the ROM is whatever installed. Where will it display the current radio so I can check that too?
J7ody said:
Ok, thanks for all your assistance. Just qiuck one, Once I have done all this how can I check it has all worked. Obviously the boot loader shows the SPL, and the ROM is whatever installed. Where will it display the current radio so I can check that too?
Click to expand...
Click to collapse
At boot it shows, just restart your device and look at the red text in the bottom right corner, there it will show your current radio version.
Could also see it in device info when the device is on but dunno if you still can considering you need to return it.
gl.
Thanks to all help, radio is now reading stock as is the 1.56 spl all installed from latest ROM from HTC so also stock.
UPS collect tomorrow and with any luck they will return a working touchscreen and I can continue where I left off
anyone noticed lots of these requests....? where they flash then the touch screen stops working?
wtf......
I noticed these threads after the 1.17 radio but some users haven't upgraded to that radio and it happend to them.
i'm looking to stay on my rom until something more is found out about this.....
Curious????
imranmaz said:
anyone noticed lots of these requests....? where they flash then the touch screen stops working?
wtf......
I noticed these threads after the 1.17 radio but some users haven't upgraded to that radio and it happend to them.
i'm looking to stay on my rom until something more is found out about this.....
Click to expand...
Click to collapse
I also have read a couple of these help requests and the same problem, but what could it be, is it the windows mobile 6.5 builds that are doing this (not blaming the chef's in anyway), or some conflict with the spl... have to investigate this more...
imranmaz said:
anyone noticed lots of these requests....? where they flash then the touch screen stops working?
wtf......
I noticed these threads after the 1.17 radio but some users haven't upgraded to that radio and it happend to them.
i'm looking to stay on my rom until something more is found out about this.....
Click to expand...
Click to collapse
I have also noticed the very same, after changing the rom people are having screen problems! Why is that?
Returning to Stock for repair! to having screen problems after changing the rom
J7ody said:
Good Morning all,
Hope everyone is well. I realise that I am probably repeating a post somewhere and apologise profusely for that.
However my request is quite urgent. I have my phone flashed with Dutty's 4.1 using the step by step guide to update radio and ROM etc etc.
My touchscreen has now started playing silly buggars and as such tomorrow it gets picked up by UPS UK to disappear off to be looked at. Obviously I do not think they will take it to well if it still has duttys on there
So just so I make sure I get eveything right.... can someone just drop me a link to the correct files for a stock flash back to the way things should be.
Thank you thank you thank you thank you thank you thank you
Jody
Click to expand...
Click to collapse
dataSaMm said:
I have also noticed the very same, after changing the rom people are having screen problems! Why is that?
Click to expand...
Click to collapse
Hi, can someone (Admin) change the title of this thread from Returning to Stock for repair! to Having screen problems after changing the rom?
I think the first is solved and now we have this new problem in hand.
best regards
+1
i've had the problem with a cooked french rom (Pyrana V17C). My screen started to freeze for a few seconds. During that time, when I put the finger on the screen and slide, the screen follows the move but it comes back to where it first was, ant the move is finally not taken in consideration ... it looks like the screen is an elastic...
So it did it sometimes and it lasted a few seconds first, and then, a couple af days later, it was more often, and I had to soft reset everytime, and yesterday, I finally had to hard reset to take back the hand, and the bug came back more quickly. So I installed the latest release of this rom this morning and everything seems to be stable since a couple of hour. If it comes back I'll try another rom, but if someone can find a way to set this, that would be perfect ...
J7ody said:
Thanks to all help, radio is now reading stock as is the 1.56 spl all installed from latest ROM from HTC so also stock.
UPS collect tomorrow and with any luck they will return a working touchscreen and I can continue where I left off
Click to expand...
Click to collapse
You've found your solution to original query and returned device to stock rom & SPL. Thread has now run its purpose
Thread closed
Related
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
USPL and HSPL do this for you so you are able to flash a rom or radio. Read this page from wiki. It'll help you understand
Follow cRaCKwHoRe's guide on how to flash (can be found in my signature). If you intend to do a lot of flashing I'd flash HSPL as its permanent whilst USPL is temporary and you'd need to re-use it before every flash to new rom or radio
Latest HSPL can also be found in my signature
Ah excellent thank you so much.
So can I flash straight to the newest 1.56 rom from my current version which is 1.19.61.1WWE on orange?
Or is there a stage in between I would have to do.
Thanks again.
futurama said:
Ah excellent thank you so much.
So can I flash straight to the newest 1.56 rom from my current version which is 1.19.61.1WWE on orange?
Or is there a stage in between I would have to do.
Thanks again.
Click to expand...
Click to collapse
Flashing from one HTC stock rom to another you don't need to use USPL or HSPL. But going to a cooked rom you do.
Answer to your query is it depends on route you take. If you go down the USPL route you'll need to follow cRaCKwHoRe's guide. Would take to long to explain and he as already done a very good tutorial on the subject. If you go down HSPL route, all you need to do is flash latest HSPL then 1.56 rom
That clears everything up. one last thing, which rom would you reccomend? I like the look of the enwer roms with WM6.
Thanks again much appreciated.
futurama said:
That clears everything up. one last thing, which rom would you reccomend? I like the look of the enwer roms with WM6.
Thanks again much appreciated.
Click to expand...
Click to collapse
I'm currently testing Dutty's V3.4. His V3.3 is already released but I'd wait for the new release hopefully in a few days. Both are based on WM6.1. Alternatively their is so many good roms out there. I'd also recommend Davideuck, EnergyROM & L26_THDV2.2 (Laurentius26). All very good roms by very good cooks. Best thing would be to try each of them and make your own opinion
thanks again mate, you are a legend, Ill post tonight to let you know how it went.
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Does the phone really have to be unlocked before flashing a new ROM?
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Does the phone really have to be unlocked before flashing a new ROM? I didn`t know that
yeeehooo got it all sorted and working!
Thanks everyone involved with XDA developers.
davemazo said:
Does the phone really have to be unlocked before flashing a new ROM? I didn`t know that
Click to expand...
Click to collapse
There are a few forms of unlocking but the bottom line is that you need to bypass the checking which is done in the flash process.
One way is permanat as done once no issues anymore - HSPL
Another is as and when you need - USPL.
Wiki has a walk through that needs to be upated but I thought still was useable.
Flash the new 1.56 shipped rom and then move on to cooked roms. (will help you by pass the greenscreen issue)
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Can you tell me were you got lost in wiki so that I can correct it in a more user frinedly version.
futurama said:
yeeehooo got it all sorted and working!
Thanks everyone involved with XDA developers.
Click to expand...
Click to collapse
Sorry to hijack your thread futurama but I am having the same problem. Could you let me know how you did it
Thanks HDuser. Not sure if you know where I`m up to but originally I flashed my Orange 1.19.61.1 ROM with USPL and then flashed Duttys 2.7 1.56 based ROM which has given me the green screen problem. An earlier poster suggested I flash Olinex HSPL 1.54 to cure the problem. The problem I am having now is the phone refuses to sync with the PC. I have tried Vista and XP, the PC does not hibernate or sleep or anything, the phone is set to not switch off. It will usually sync on first connection but after a few seconds it will disconnect and therefore HSPL is reporting as being disconnected.
I have tried the earlier HSPL and HSPL 1.56 (as the ROM in bootloader screen is reported as being 1.56 and SPL is 1.14). I feel I`m going round in circles and its only a matter of time before I brick the phone.
I have read and re-read the wikis but I am now just getting more and more confused.
davemazo
Look the best way to approach any problem is to go back to the roots.
Flash a stock rom, find your own stock rom and refalsh it, then take it from there.
Your post is missleading and I have no idea were to sart. One issue is your PC ist does not Hibanate, not or go into sleep mode, at the saem time you are saying that you can't sync. Sounds like you have other problems and those other problems are making you have problems with your device.
Thanks HDuser. Sorry for confusing you, but I am now totally confused myself, Basically though the phone does not sync with the PC, I have tried 2 PC`s, with Vista and XP.
But back to your point about flashing stock ROM, I have tried a link in the wiki to download the one I need which is Orange 1.19.61.1 but the link seems to be broken and I don`t know where else I can get it. It doesn`t seem to be on the Orange website or HTC.
HDuser said:
Can you tell me were you got lost in wiki so that I can correct it in a more user frinedly version.
Click to expand...
Click to collapse
There is a part on the black stone wiki that mentions I need to CID unlock my phone. It says you need to do this before you can flash roms, I felt it wasn't clear that, all I needed to do was flash HSPL in order to allow me to put new roms on.
This is what I did.
1:Flashed HSPL olinex 1.14.
2:Flashed HSPL Olinex1.56
3:Flashed MIRI WM6.5 10.0WWE
only part I had trouble with, my phone wouldnt let me flash the HSPL at first, I had to use a manual thing that you launch on the device the it lets you flash the HSPL.
futurama said:
There is a part on the black stone wiki that mentions I need to CID unlock my phone. It says you need to do this before you can flash roms, I felt it wasn't clear that, all I needed to do was flash HSPL in order to allow me to put new roms on.
This is what I did.
1:Flashed HSPL olinex 1.14.
2:Flashed HSPL Olinex1.56
3:Flashed MIRI WM6.5 10.0WWE
only part I had trouble with, my phone wouldnt let me flash the HSPL at first, I had to use a manual thing that you launch on the device the it lets you flash the HSPL.
Click to expand...
Click to collapse
It sounds as if you have it sorted now and everything working. As HDUser stated previously HSPL & USPL allows you to bypass the CID lock to enable you to flash new roms
Only thing I need clearing up, I can change my SPL back to the original version cant it?
Just incase anything goes tits up and I need to send it back
futurama said:
Only thing I need clearing up, I can change my SPL back to the original version cant it?
Just incase anything goes tits up and I need to send it back
Click to expand...
Click to collapse
Of course you can. All information you need including original stock radio's, roms etc are available in wiki to download.
Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...
localcall001 said:
Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...
Click to expand...
Click to collapse
hi if you have done the hardspl then try this
to enter Bootloader
Remove the back cover from the phone.
Hold the Volume Down button.
Use the stylus to press the reset hole.
Or if the device was powered off, press the power button whilst holding down the Volume Down button.
you should see serial at the bottom of the three color screen then plug in the usb cable the serial should change to USB then just flash another rom.
i hope this helps you.
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
only to pleased to help I am glad you got your phone back working
localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
idd, this is not ROM related, its just unlucky like hell. See the phone as a PC, where blocks need be written. If a block fails or is corrupt, you get these jokes. Its like a BSOD on a Windows PC.
I gotta admit it is great knowing that once you've done a hardspl you are safe as houses as even if you flashed the most currupted ROM, the bootloader will always allow a reflash.
This is way more stable and safe than any other experience I've had of phone flashing.
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Funny that, your latest ROM was the only one I had problems with - the same problems as the original poster, in fact. I flashed a different ROM fine, re-downloaded your 2.0 and flashed it again, same problem. Hanging on the boot screen.
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Probably I think I was just unlucky. My fear (while I was panicking) was that your ROM is European based, and since mine came from T-Mobile, it didn't mesh well. I also didn't unlock my phone so that could be also be a problem...
awesome community
localcall001 said:
That's a really cool recovery feature from HardSPL...
Click to expand...
Click to collapse
well..this is a normal recovery feature for stock spl also
Same Issue
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo
wahida76 said:
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo
Click to expand...
Click to collapse
no one have told me that on my thread... only here i found this issue.. and finally how pass the problem?
I had to re-flash a different ROM.
I'm wondering if it's related to the radio version...
what is your version of radio
can't you flash the latest 23060?
i use radio 3.36
I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.
Alas, no luck with that one either.
I have no idea why it doesn't seem to work on my Rhodium :/
I'm sorry if I'm hijacking this thread but it's the only one I've found that's even close to having the same issue I have, though I'm still using the stock rom/os.
I was installing winmo msn messenger. It installed fine and reset my tp2 fine. It goes thru the tp2 splash screen, the verizon splash screen and the winmo splash screen. Then it shows owner information and this is where it gets screwed up. Owner info will stay up forever if I dont touch the screen. After touching the screen the only thing left will be the top bar and the rest of the screen stays black. The only things on the top bar are the signal icon (which always has an x), the wifi icon (which seems to be connected fine lol) and either owner info will still be in the upper left or the start menu will be there. Hitting the screen only causes my tp2 to beep.
Nothing I know how to do (which is basically just hard and soft resetting it) works. Verizon can't fix it (didnt think they would be able to) and I can find no drivers (possibly cause I'm still a noob with winmo) to resolve my issue. I'm not even sure how I'd get them on as it wont even sync up to my computer and my computer cannot find its hd. If I could get a rom for the verizon one I think I can figure it out from there with no issues...but htc website sends me to verizon website for support and vice versa. The htc wiki is the closest I've gotten to an answer...but no rom to download. The only OEM roms I can find anywhere aren't for this phone, unless one of those will work? You guys are the experts.
Does anyone know what I can try? Verizon wants me to return it but cannot tell me when I'll get my new one as they are out of stock...again. Please help lol! Thanks for any and all help.
Mr.Clark said:
I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.
Click to expand...
Click to collapse
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)
b16b said:
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)
Click to expand...
Click to collapse
Sorry, I tried that one as well yesterday. And I've downloaded your ROM a few times too...
Are you still working on the 6.1 ROM? Maybe a new version will just magically start working for me...
EDIT: Tried a fresh 3.46.25.30 and a fresh download of your ROM. Still nothing
Hi everyone,
Used cooked roms for a while now, used to use them on my tytn as well.
I have been having such a bad time with my touch HD, i thought it was time to ask what's going on with you lot.
Basically, my touch HD has been running so slow for a while now, that it can even be hit and miss if i answer a incoming call. It even takes 2/3 rings before the ringtone starts up!
I have used miri's wm6.5 v16, but recently updated to he's manilla 2.5 ROM to see if that improved things, it hasn't.
I have radio 1.14 installed along with 1.56oli.
Could i be doing something wrong or is there software out there i have installed that is restricting my touch hd?
Battery life aint too bad so i can't really see it being that.
Any help would be great, my phone is angering me! haha
many thanks for any help!
stuart
stuartturrell said:
Hi everyone,
Used cooked roms for a while now, used to use them on my tytn as well.
I have been having such a bad time with my touch HD, i thought it was time to ask what's going on with you lot.
Basically, my touch HD has been running so slow for a while now, that it can even be hit and miss if i answer a incoming call. It even takes 2/3 rings before the ringtone starts up!
I have used miri's wm6.5 v16, but recently updated to he's manilla 2.5 ROM to see if that improved things, it hasn't.
I have radio 1.14 installed along with 1.56oli.
Could i be doing something wrong or is there software out there i have installed that is restricting my touch hd?
Battery life aint too bad so i can't really see it being that.
Any help would be great, my phone is angering me! haha
many thanks for any help!
stuart
Click to expand...
Click to collapse
have you tried flashing back to stock http://forum.xda-developers.com/showthread.php?t=501583&highlight=RUU+blackstone rom?
no, ok, i will take a look at doing that then.
Will i have any issues other than the one stated about hardspl with going back to stock?
If i were to install this, would i then be able to try cooked ROM's again or would i likely see the same as what is happening now? (slow device)
Thanks for the link btw
stuartturrell said:
no, ok, i will take a look at doing that then.
Will i have any issues other than the one stated about hardspl with going back to stock?
If i were to install this, would i then be able to try cooked ROM's again or would i likely see the same as what is happening now? (slow device)
Thanks for the link btw
Click to expand...
Click to collapse
i am well experience with USPL but nil with HSPL, i have been flashing back and forth stock and any latest Manila 2.5xxxx ROMs using USPL. you can search HSPL thread and look for ways in order for you to flash stock rom and reflash cooked roms.
It sounds like you've correct SPL for rom your using, i.e. SPL 1.56.Olinex, so it shouldn't be a problem with HSPL. You've also tried a different rom which also didn't fix your issue so I'd suggest what jigners said above and restore stock SPL & rom, then re-use dummies guide before flashing cooked rom again.
Alternatively check on Miri thread incase there are issues with his latest rom(s)? If so, there are plenty of other chef's and alternative cooked roms to try before you try restoring stock
maybe you want to try kwbr's Topix rom, it's wm6.1 and fast
I would say go back to stock ROM and start all over again.
Good combo is:
SPL 1.56
EnergyROM
Latest radio is a bit disappointing for me so i am on 1.14.25.24 with its rilphone.dll
Remember to flash with no memory card inside and to do a hard reset after the flash
By the way, have you hard reseted your device after flashing a new rom?
If not then do the hard reset for 2/3 times and observe the performance.
Furthermore, remove the SD card from the device and check the same. Defective SD card simulates the same problem because system requires lot more time to access it.
OK, i have gone back to stock firmware (well most recent offical release anyway)
All seems ok at the moment, it's been up and running for a couple days smoothly now.
I will take a look at the dummies guide and get back to cooked soon.
And yes, i do a hard reset everytime i have flashed, but only, i will try that next time i put cooked ware on the phone. (hopefully later today).
thanks for all the help,
Hi,
My experience today is the motive of me writing this guide to help most of you out of this problem and eliminate the Fear that you will have of you blackstone might gone bad (hardware fault).
ok,
here is what happend to me today.
I had XannyTech Rom flashed on my phone and i really felt i found something interesting about another ROM so i decided to flash that one.
after a smooth flashing, the phone booted and i started syncing using myphone.
left the phone on the desk for a while, came back and found that the device is not responding to the power button, poked that red button and the phone get's stuck at the "smart mobility" screen!!
Hard resetted the phone and started over, again the phone hanged.
i thought that it's maybe a bad flash! so i downloaded the file again and flashed again.
still the same!!!!
decided to go to the old ROM ,
still after a while i get the same result!
notice that i hard resetted after each and every flash!
so what did i do?
[Guide]
Hard Reset the phone, check if it's a software you installed or if it happens even on a pure ROM.
If the problem still exist, Confirm it's not a bad flash! flash again the same ROM.
If you still have the same symtoms, go to HTC website and download the latest OFFICIAL ROM from there.
Run the RUU from your pc (Don't worry about HSPL, it's protected so you will NOT have to HSPL your device again, Thanks olinex)
Test your phone with the new official ROM (in my case -blackstone- it's a 6.1 rom ). Mostly everything will be back to normal.
flash the rom of your choice.
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Hope you find this usefull.
Regards,
Adel
I will remember this if it happens to me!
Thank you!
For me, with the HSPL, when I went back to original rom, I had a big problem with color. I flashed to old SPL too, and so, color where good after
Wiki
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
edit : oops, the link is accessable from the wiki
re the topic:
Looks like Viagra cant fix this issue then
anaadoul said:
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
Click to expand...
Click to collapse
Hi
You should fix your link and put wiki instead if forum
Jal84 said:
Hi
You should fix your link and put wiki instead if forum
Click to expand...
Click to collapse
it is good to see that you have followed the link
anaadoul said:
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Click to expand...
Click to collapse
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Ehol said:
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Click to expand...
Click to collapse
Good explaination!
also while i was extracting a shiped ROM i got an unknown nb file which might be responsible for this?
what you have said means that as long as you are flashing a larger sized ROM you should have no problem, but once the new ROM have a smaller size then you will face some issues?!
oh, one more thing.
after formating the phone with the stock ROM, i noticed that it runs much faster (around 15% performance increase) can anyone try flashing shipped ROM then the same one he was using and confirm this?
Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!
Sopis said:
Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!
Click to expand...
Click to collapse
Dear friend,
first let's know what ROM have you installed on your device? I'm sure the problems that you've mentioned are not hardware problems, and in fact they are related to the ROM, since I have the same problem sometimes with some ROMs and some application. I had problem with alarm clock several times, just after flashing Energy ROMs! I reported this matter, but nobody paid attention, so I downgrade my device to kwbr WM6.1+sense2.1, now I have no problem with alarm clock.
about the another problem, I still have this problem, but I think it is related to WKTask! sometimes when I turn my device off by WKTask shortcut, I encounter the problem that you pointed, but it's not the case if I turn it off by hardware key.
Same question
I have used HSPL
and have tried several roms
Few days back my touchscreen stops responding.
flashed differnet roms but no difference. so i think its a hardware problem
(kinda works sometimes so may be just a loose link)
I want to send it for repair under warranty.. so can someone tell me how to get back to factory settings of Touch HD (German)
Prajwal
Ah, now we have 2 different cases.
1. Flash with USPL
2. Flash with HSPL
I'm almost sure that "virginizing" is described on HD Wiki, but nevermind...
Case 1. is nice and easy...
Go to HTC site and try to find update for your device. Before that, write serial and IMEI (not sure which one is needed, both are under the battery).
If there is "No suitable update", then you are in big trouble... try to find what was original ROM which was on device when it was delivered.
Case 2. is bit difficult... you HAVE TO remove HSPL and restore original SPL, then proceed as described in case 1. I think for german ROM was SPL 1.54
However, I have bought my device recently (with German ROM), but maybe earlier devices had some other SPL...
Check HD Wiki anyway...
prajbio said:
I have used HSPL
Click to expand...
Click to collapse
Ah... [TUT] Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL] has at least one important thing for you: stock SPL...
Thanks Guys...
I didnt think of checking the wiki...
Ill go there, and also do what you suggest...
I guess the issue is not related..I flashed a new ROM from different cook and it happened.
Nevermind...I will virginize and then have it fixed or replaced...
THANKS!!
Bodisson said:
Ah, now we have 2 different cases.
1. Flash with USPL
2. Flash with HSPL
I'm almost sure that "virginizing" is described on HD Wiki, but nevermind...
Case 1. is nice and easy...
Go to HTC site and try to find update for your device. Before that, write serial and IMEI (not sure which one is needed, both are under the battery).
If there is "No suitable update", then you are in big trouble... try to find what was original ROM which was on device when it was delivered.
Case 2. is bit difficult... you HAVE TO remove HSPL and restore original SPL, then proceed as described in case 1. I think for german ROM was SPL 1.54
However, I have bought my device recently (with German ROM), but maybe earlier devices had some other SPL...
Check HD Wiki anyway...
Click to expand...
Click to collapse
From my experience, HTC is usually ok as long as the SPL is an official one. No matter the one came with your phone or other older/newer version.
Sopis said:
Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!
Click to expand...
Click to collapse
since you just use USPL, you just need download the official ROM from HTC page by inserting your HD serial number under ROM download. then flashed it. it think this step will solve your warranty issue.