Related
Dears,
I faced the white screen the first time last Thu. I migrated my device (Jasjam) to Black Pro 2.0 on Wed. and started to get the white screen on Thu.
I was going arround it by few turn-of turn-on untill today morning when I noticed that the screen shifted down by 1mm. In fact more precisly, rotated down 1mm. Starting with the splash screens, the Windows booting screen and the Windows later. Everything is rotated down by the 1mm meaning what is disapearing from bottom is showing on top!
I got to the device through the mtty and ran task 2a, everything was okay. Then I ran task 28 and task 8. The deveice booted with the sae shifting problem. I installed the latest LVSW 05Apr07, the same problem still although the Windows is working fine. Switching the device off will not switch the screen off immediatly, the screen goes in fade-away type of action for about 2 minutes until it totally powers off.
Any idea? Does that mean I am loosing the mobile? Please help.
Appreciating all help.
Regards.
attot1239 said:
Dears,
I faced the white screen the first time last Thu. I migrated my device (Jasjam) to Black Pro 2.0 on Wed. and started to get the white screen on Thu.
I was going arround it by few turn-of turn-on untill today morning when I noticed that the screen shifted down by 1mm. In fact more precisly, rotated down 1mm. Starting with the splash screens, the Windows booting screen and the Windows later. Everything is rotated down by the 1mm meaning what is disapearing from bottom is showing on top!
I got to the device through the mtty and ran task 2a, everything was okay. Then I ran task 28 and task 8. The deveice booted with the sae shifting problem. I installed the latest LVSW 05Apr07, the same problem still although the Windows is working fine. Switching the device off will not switch the screen off immediatly, the screen goes in fade-away type of action for about 2 minutes until it totally powers off.
Any idea? Does that mean I am loosing the mobile? Please help.
Appreciating all help.
Regards.
Click to expand...
Click to collapse
Remove the battery for 5 minutes and re-insert it back..see if it will fix it or not.
attot1239 said:
Dears,
I faced the white screen the first time last Thu. I migrated my device (Jasjam) to Black Pro 2.0 on Wed. and started to get the white screen on Thu.
I was going arround it by few turn-of turn-on untill today morning when I noticed that the screen shifted down by 1mm. In fact more precisly, rotated down 1mm. Starting with the splash screens, the Windows booting screen and the Windows later. Everything is rotated down by the 1mm meaning what is disapearing from bottom is showing on top!
I got to the device through the mtty and ran task 2a, everything was okay. Then I ran task 28 and task 8. The deveice booted with the sae shifting problem. I installed the latest LVSW 05Apr07, the same problem still although the Windows is working fine. Switching the device off will not switch the screen off immediatly, the screen goes in fade-away type of action for about 2 minutes until it totally powers off.
Any idea? Does that mean I am loosing the mobile? Please help.
Appreciating all help.
Regards.
Click to expand...
Click to collapse
what bootloader version are you running?
Many thanks trashcan for your quick response. I have removed the battery for 5 minutes, the screen was still showing that last image. I keept the battery out for 15 minutes untill the screen was totally off. Reruting the battery resolved the ****ing issue, thanks again.
Also thanks to walshieau, the device has IPL-1.01 and SPL-1.40.Olipro.
Regards.
Regards.
The bad part of the news is that the white screen is still comming!!!
Any clue?
Regards.
I thought of sharing this with you
I have just done the follwoing:
> Updated (again) the device with SSPL-1.40
> Re-flashed the device Force through SSPL the new OS (LVSW)
The phone looks better, however I got the white screen two times in about five minutes.
Wat else I should do? Please share your experience.
Regards.
attot1239 said:
I have just done the follwoing:
> Updated (again) the device with SSPL-1.40
> Re-flashed the device Force through SSPL the new OS (LVSW)
The phone looks better, however I got the white screen two times in about five minutes.
Wat else I should do? Please share your experience.
Regards.
Click to expand...
Click to collapse
Read?
1) Ensure that you have 1.40.Oli by checking the bootloader screen.
2) Run the upgrade, but, select AUTO DETECT! DO NOT CLICK FORCE SSPL!
3) White screen gone
LegolasTheElf said:
Read?
1) Ensure that you have 1.40.Oli by checking the bootloader screen.
2) Run the upgrade, but, select AUTO DETECT! DO NOT CLICK FORCE SSPL!
3) White screen gone
Click to expand...
Click to collapse
not quite, the ROM image affects some devices, I'll redo Black 2.0 like I redid LVSW if this keeps happening.
It is getting worse now ... I do not know what is happening
Good morning,
Thanks LegoLasTheElf and Olipro for you input, I started to patch the device again and although everything was normal, the update program sayed the connecting was lost and took me to a recovery screens which just went into a loop (repeating the same steps with no hope).
The device is on the bootloader (tri-color) screen. I tried getting into it using the mtty and set 14 0 (as I found it on on of the posts) however it did not help.
Could someone tell me please to to get the device to boot normal again.
Regards.
attot1239 said:
Good morning,
Thanks LegoLasTheElf and Olipro for you input, I started to patch the device again and although everything was normal, the update program sayed the connecting was lost and took me to a recovery screens which just went into a loop (repeating the same steps with no hope).
The device is on the bootloader (tri-color) screen. I tried getting into it using the mtty and set 14 0 (as I found it on on of the posts) however it did not help.
Could someone tell me please to to get the device to boot normal again.
Regards.
Click to expand...
Click to collapse
yeah... flash my patched LVSW with CustomRUU
Olipro said:
yeah... flash my patched LVSW with CustomRUU
Click to expand...
Click to collapse
Yeah, that works!! That is how I solved my whitescreen.
thx Olipro!!
Many thanks Olipro for your continued help.
I have gove through your topic on the white screen and I posted you a reply there. The megaupload site is blocked in my area, if possible please mirror it on another site, i.e. 4shared.com
Regards.
I have exactly the same White Screen symptoms and more recently, the 1 mm screen shift problem too. I removed my battery for 15 mins and the screen shift temporarily went away but on the next reset, it is back :-(
I have SPL-1.40 Olipro but am unable to download the LVSW to resolve White Screen as Megaupload never works in my area. Can someone post that ROM to Rapidshare please.
Thanks a ton!
Olipro said:
yeah... flash my patched LVSW with CustomRUU
Click to expand...
Click to collapse
Where can I get the CustomRUU? The device is now on the BL screen and the tools are being able to communicate with it.
Regards.
Alright, I have the same problem here. Now before anybody comes on here and tell me to read this and that, I've tried everything.
From going back to 1.01MFG, mtty the OS, use 1.40, use customRUU, leaving the battery out for 5mins, 15mins, hours, over night. Even tried going back to the original ROM and still nothing, the same damn white screen. As far as I am concerned, the intervals are actually getting worse and it comes on more often.
Anybody has any other ideas beside the ones that are posted everywhere. Trust me I've been trying to fix this for over a week now and I have read everything on here.
Any help is appreciated. Thanks guys
YES This was my first solution
http://forum.xda-developers.com/showthread.php?t=298520
bcrx7 said:
Alright, I have the same problem here. Now before anybody comes on here and tell me to read this and that, I've tried everything.
From going back to 1.01MFG, mtty the OS, use 1.40, use customRUU, leaving the battery out for 5mins, 15mins, hours, over night. Even tried going back to the original ROM and still nothing, the same damn white screen. As far as I am concerned, the intervals are actually getting worse and it comes on more often.
Anybody has any other ideas beside the ones that are posted everywhere. Trust me I've been trying to fix this for over a week now and I have read everything on here.
Any help is appreciated. Thanks guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=298520
@BCRX7- After the WHITNESS from LVSW and then black1.2 I used this QTEK rom. It got rid of the white screen. Then I used Olipro's modified ROM. I am now running BLACK2.0 with no problems. Props OLIPRO and JasJammin!!!
i solved my white screen in a different and strange way, but easy
you may not believe it, but i did it, i solved the problem of my white screen in a very simple way.
i put my hermes in the fridge for 20 mins at 2C and i keep it on and put it over night.
(no charging, no sync, .... nothing)
this is the way how i solve it.
try it at your home, and tell me what happened to it.
thanks for all.
Hardware or software issue?
Hi,
Did anyone figured if white screen is hardware or software related issue? I wonder if there is anybody that doesn't got any whitescreen since they upgraded to WM6. I observed that the number and the severity of the white screens was different depending of the cooked ROM used (I have Olipro 2.10 SPL, Radio 1.50). Unfortunately I didn't count the white screen number for each version in order to choose the right one
I want to be sure I have tried all software methods before I will send my Hermes to the mobile operator for a replacement (if it is a hardware issue). Thanks in advance for any suggestion!
Hi all.. I had the same prob and it developed into this: http://forum.xda-developers.com/showthread.php?t=303872
So its a HW problem... You can get it back to normal by hitting(yeah not the nicest thing to do with a toy that has high price tag) the phone when its turned off completely -if its hibernating it doesnt work. If you have warranty time left -get it fixed. If not -you can try opening the hermie and doing whats told on 8th page in thread I mentioned. I got mine fixed by changing the front keyboard circuit board..
Hello,
I hope someone could help me with this because I have been reading this thread:
http://forum.xda-developers.com/showthread.php?t=329079
for more than 3 hours.
(I started reading at 10pm and now it is 1:42am)
and read through every single post (and even every single word).
However, I am still having a problem with upgrading my IPAQ hx2495b
Basically, when I tried to get into the white screen boot loader mode, the screen faded to white and then nothing happens. I do not see any icon (or any graphical shape appear whatsoever) to indicate I am in the boot loader mode, it was just white.
I pressed the contact+iTask+reset button, which I believe is the correct combination.
And the screen shows no reposnse when I pressed and held the calender button.
I was be able to format PS though.
And when I tried to run the update program, it simply said the program failed to connect to ActiveSync.
My current bootloader version is 1.02.00H and I am running on Windows Vista Service Pack 1 using the Windows Mobile Center.
Could someone please let me know what I should do? Many thanks!
Regards
Anyi
OK, problem solved, I just have to work with the white screen! Welcome WM6!!!!!
Really
How id you fix it
you pretty much have to just do everything blindly and hope things will work, which turned out to be the case for me. Good luck!
Try Tommy's ROM http://forum.xda-developers.com/showthread.php?t=383173 , it's 6.1 and it's faster (as far as i can tell) than 6.0.
zhuanyi said:
Hello,
I hope someone could help me with this because I have been reading this thread:
http://forum.xda-developers.com/showthread.php?t=329079
for more than 3 hours.
(I started reading at 10pm and now it is 1:42am)
and read through every single post (and even every single word).
However, I am still having a problem with upgrading my IPAQ hx2495b
Basically, when I tried to get into the white screen boot loader mode, the screen faded to white and then nothing happens. I do not see any icon (or any graphical shape appear whatsoever) to indicate I am in the boot loader mode, it was just white.
I pressed the contact+iTask+reset button, which I believe is the correct combination.
And the screen shows no reposnse when I pressed and held the calender button.
I was be able to format PS though.
And when I tried to run the update program, it simply said the program failed to connect to ActiveSync.
My current bootloader version is 1.02.00H and I am running on Windows Vista Service Pack 1 using the Windows Mobile Center.
Could someone please let me know what I should do? Many thanks!
Regards
Anyi
Click to expand...
Click to collapse
i posted the begining of my problem somewhere on monday but cant remember where. so.....
on monday, the screen on my tmobile dash messed up, now the top half of the screen has white horizontal lines covering it.
well, i called tmobile and the phone was still under warrenty, so got a like new phone sent and it arived today. I went about unlocking it and upgrading to wm6.1 like i had on my last phone. started out with all sorts of problems sycning and i had to reinstall active sync and that seemed to fix it. continued installing the upgrade, the dos program runs i press the center button and i get the red blue green screen and i know from before that that normally means it isn't working, so i reboot the phone, re sync, and re do it and get the red green blue screen again and the update program says it can recover and it leads me through a four step process, upplug, pull bat, reboot and do it again, only it reboots into the red green blue screen, wouldnt sync and when i turned it off, i couldnt get it to power back up. no response from the phone at all. pulled battery many times and all.
What are my options? I know that i agreed to the statment and i have no one to blame but my self. is there anything i can do? i have 7 days to return the half working phone, and i have a feeling that because its unlocked and has wm6.1 on it that tmobile is going to charge me what ever it will be. I have 200.00 in credit with um, and i feel that those fees will take away from that, leave me with an un usable phone, and no money to do anything about it !
a brainstorm, could i just tell tmobile that i got the phone that way? or would they see through my lies?
please please please please help!!!
and thanks a ton in advance.
Nick
NJDubois said:
i posted the begining of my problem somewhere on monday but cant remember where. so.....
on monday, the screen on my tmobile dash messed up, now the top half of the screen has white horizontal lines covering it.
well, i called tmobile and the phone was still under warrenty, so got a like new phone sent and it arived today. I went about unlocking it and upgrading to wm6.1 like i had on my last phone. started out with all sorts of problems sycning and i had to reinstall active sync and that seemed to fix it. continued installing the upgrade, the dos program runs i press the center button and i get the red blue green screen and i know from before that that normally means it isn't working, so i reboot the phone, re sync, and re do it and get the red green blue screen again and the update program says it can recover and it leads me through a four step process, upplug, pull bat, reboot and do it again, only it reboots into the red green blue screen, wouldnt sync and when i turned it off, i couldnt get it to power back up. no response from the phone at all. pulled battery many times and all.
What are my options? I know that i agreed to the statment and i have no one to blame but my self. is there anything i can do? i have 7 days to return the half working phone, and i have a feeling that because its unlocked and has wm6.1 on it that tmobile is going to charge me what ever it will be. I have 200.00 in credit with um, and i feel that those fees will take away from that, leave me with an un usable phone, and no money to do anything about it !
a brainstorm, could i just tell tmobile that i got the phone that way? or would they see through my lies?
please please please please help!!!
and thanks a ton in advance.
Nick
Click to expand...
Click to collapse
Okay do this, make sure the phone is off and hold the camera button down for about 5 seconds... this button is located to the right of the keyboard. While still holding it down plug in the phone to the usb and now you should see a tri-colored screen come up. Now you can load the original rom the phone came with... The official roms could be found in the link below... called "official roms" and just download the t-mobile rom... and now you can flash your phone with the original rom...
stonersayswhat?
gixxum said:
stonersayswhat?
Click to expand...
Click to collapse
quis-ego....
anyone seen the other half of my thought from the other night? anyone?
Ok, I had found a forum post saying to hold down the SYM button, but couldn't get it working untill I read your reply. Much thanks, the phone is on, and giving me the red green blue screen. I hear the windows alert saying a USB device is plugged in, but active sync wont pick it up. So I'll post about it here, and while I dig through the internet trying to find my cure, I will hope that someone will know what my next step is.
Much much thanks jdoggraz! At least now I know my phone isn't completely dead!
Nick
jdoggraz already told you what to do. YUou do not have to wait for active sync to pick the phone. Just run the exe for the orginal rom.
I have tried to do a hard reset.
Hold the 2 softkeys down(the "-" on each end) for a few seconds, hot the power button down for 2 seconds and then hold the 2 softkeys down and wiat, but nothing happens. Donno why, but may be not being able to hard reset is a clue to whats wrong.
[EDIT]
I have found something about a program called Mtty.exe, and also a UNI_ExitBootLoader But I get a "un able to connect to usb" error with both programs when I try to connect. But, once again, every time I plug the phone into the computer I hear the alert saying a usb device has been attached??
[Another Edit]
I just noticed in Device Manager, under Window CE USB Devices, that my Smartphone USB Sycn Has that nasty Yellow explanation mark next to it.
This device cannot start. (Code 10)
Click Troubleshoot to start the troubleshooter for this device.
?
NJDubois said:
I have tried to do a hard reset.
Hold the 2 softkeys down(the "-" on each end) for a few seconds, hot the power button down for 2 seconds and then hold the 2 softkeys down and wiat, but nothing happens. Donno why, but may be not being able to hard reset is a clue to whats wrong.
Click to expand...
Click to collapse
why are you resetting it? you were at the bootloader screen in your last post...right where you needed to be. now you are 2 steps back?
Sorry guys, I guess I wasn't getting a refreshed look at the forum post, and I didn't see any other posts. I went back to what I was told to do in the first place.
I first tried
1.33.422.1 (Worldwide English, WM6)
1.27.405.1 (Worldwide English, WM6)
With both I get:
ERROR [224] : INVALID MODEL ID
This update utility cannot be used for your smartphone. Please check your Update Utility.
And in the lower right there is a string of characters that is different every time.
What am I doing wrong? I'm so frustrated. I followed your instructions =(
[EDIT] OMG I am an idiot, ignore this post. If I wasn't so beat I might have scrolled down and noticed the tmobile DASH!!!!!!!!!!!!!!
NJDubois said:
Sorry guys, I guess I wasn't getting a refreshed look at the forum post, and I didn't see any other posts. I went back to what I was told to do in the first place.
I first tried
1.33.422.1 (Worldwide English, WM6)
1.27.405.1 (Worldwide English, WM6)
With both I get:
ERROR [224] : INVALID MODEL ID
This update utility cannot be used for your smartphone. Please check your Update Utility.
And in the lower right there is a string of characters that is different every time.
What am I doing wrong? I'm so frustrated. I followed your instructions =(
[EDIT] OMG I am an idiot, ignore this post. If I wasn't so beat I might have scrolled down and noticed the tmobile DASH!!!!!!!!!!!!!!
Click to expand...
Click to collapse
pass the hookah brother..i wanna hang out in your world
puff, puff, give... man!....you're [email protected]#ing up the rotation!
An update.
I have gotten wm5 installed and working on my phone. I can't for the life of me get the 6.1 update to work. I get the agreement, press the center button and it goes back to the OS, the phone then locks up, and I have to restart it to re sycn.
This is very time consuming! The phone takes for ever to start. I also want to note that I upgraded my last dash with little problems, but this dash has been nothing but a head ache. WHY?!?!? I am not looking forward to being stuck with this phone.
Thanks everyone, for all the help. I went a little off course last night, I was falling asleep trying to get this thing working.
puff puff pass
nick
[EDIT] Why wont the screen go almost white after i click the middle button?!?!?!?!?
It works, YAY!!
Thank you soooo freaking much, everyone!
NJDubois said:
It works, YAY!!
Thank you soooo freaking much, everyone!
Click to expand...
Click to collapse
No problem, so what exactly did you end up doing?
damn! it's "cashed"!
pudgedaddy said:
damn! it's "cashed"!
Click to expand...
Click to collapse
hahaha
My Dash started acting up the other day and I am hoping someone here can help.
It is responding very slowly to most key presses, sometimes taking 5-10 minutes to, say, open a folder or bring up a settings screen. Sometimes they don't come up at all and it appears frozen, requiring a "yank the battery" reset procedure.
ActiveSync on both home and work PC's detects the device but cannot connect to it.
On bootup, the Windows Mobile splash will be displayed much longer than it used to (3 - 4 minutes) before I finally get a desktop.
The time on the main (top) sliding panel is often the last to (slowly) appear on the display when "waking up".
Email has stopped working in and out. I can receive calls, and Bluetooth is working, but often the ringer will continue for 5 -10 seconds after I answer, and transferring calls to my headset takes about 5 - 10 seconds after that.
Sometimes, settings changes won't "take" and will reset themselves back to their previous values.
Hard resets haven't helped, and nothing seems changed after them, which is odd.
The only thing I have changed recently is I installed the ODSHOW weather thing a few weeks ago (which seriously fubar'd my phone and it was all I could do to get the "normal" top panel back) as far as I know it's uninstalled now.
And all of this started happening after the battery had run completely down and the phone shut itself off. I have already tried another battery and the behavior hasn't changed.
I would love to flash it as I think the problem is the O/S is hosed, but is that possible without being able to connect to a PC through ActiveSync? Say, by copying the ROM package to the SD card and running it from there?
I am running RickyWatts/Kavana's WM 6.1 ROM, btw.
Many thanks if you have any suggestions.
-GoJ
Ghost of Jaco said:
My Dash started acting up the other day and I am hoping someone here can help.
It is responding very slowly to most key presses, sometimes taking 5-10 minutes to, say, open a folder or bring up a settings screen. Sometimes they don't come up at all and it appears frozen, requiring a "yank the battery" reset procedure.
ActiveSync on both home and work PC's detects the device but cannot connect to it.
On bootup, the Windows Mobile splash will be displayed much longer than it used to (3 - 4 minutes) before I finally get a desktop.
The time on the main (top) sliding panel is often the last to (slowly) appear on the display when "waking up".
Email has stopped working in and out. I can receive calls, and Bluetooth is working, but often the ringer will continue for 5 -10 seconds after I answer, and transferring calls to my headset takes about 5 - 10 seconds after that.
Sometimes, settings changes won't "take" and will reset themselves back to their previous values.
Hard resets haven't helped, and nothing seems changed after them, which is odd.
The only thing I have changed recently is I installed the ODSHOW weather thing a few weeks ago (which seriously fubar'd my phone and it was all I could do to get the "normal" top panel back) as far as I know it's uninstalled now.
And all of this started happening after the battery had run completely down and the phone shut itself off. I have already tried another battery and the behavior hasn't changed.
I would love to flash it as I think the problem is the O/S is hosed, but is that possible without being able to connect to a PC through ActiveSync? Say, by copying the ROM package to the SD card and running it from there?
I am running RickyWatts/Kavana's WM 6.1 ROM, btw.
Many thanks if you have any suggestions.
-GoJ
Click to expand...
Click to collapse
Here's what you do.Turn the phone off, holding the camera button down for about 10 seconds , plug the usb cable that should give you the bootloader screen,you can get the official tmo 6.0 on there, it has to be an official rom. Once you got the phone with the 6.0 running, set up active sync and then flash which ever 6.1 rom you want. Good luck.
Here's the link for the official 6.0 rom http://forum.xda-developers.com/showthread.php?t=381726&highlight=official+roms
Her's the 6.1 rom link. I recomend V24 w/opera http://forum.xda-developers.com/showpost.php?p=3315417&postcount=1
Thanks rolo. Let me make sure I have this:
1) Turn off the phone while holding down the camera button for about ten seconds.
2)Release the camera button and plug in the USB cable. Bootloader screen will appear.
3) From the bootloader screen I can put the TMO ROM on.
Is that correct?
Thanks again!
Ghost of Jaco said:
Thanks rolo. Let me make sure I have this:
1) Turn off the phone while holding down the camera button for about ten seconds.
2)Release the camera button and plug in the USB cable. Bootloader screen will appear.
3) From the bootloader screen I can put the TMO ROM on.
Is that correct?
Thanks again!
Click to expand...
Click to collapse
No!
1. Turn off phone
2. after phone's off, press and hold the camera button.
3. after holding it for about 10 seconds, plug the usb like you're gonna use active sync.
4.That will give you the bootloader screen, and you can now install official 6.0.
5. after you got 6.0 set. set up active sync.
6. I would wait about 10 or 15 minutes, then flash 6.1
roloracer said:
No!
1. Turn off phone
2. after phone's off, press and hold the camera button.
3. after holding it for about 10 seconds, plug the usb like you're gonna use active sync.
4.That will give you the bootloader screen, and you can now install official 6.0.
5. after you got 6.0 set. set up active sync.
6. I would wait about 10 or 15 minutes, then flash 6.1
Click to expand...
Click to collapse
Ah! Ok, now I have it in bootloader mode. Thanks.
I d/l'd the Official TMO_1.22.531.6 file and unpacked it, but the 40 MB RAR file contains only a 60 KB(?) file named RUU_signed.nbh
What do I do with that?
Ghost of Jaco said:
Ah! Ok, now I have it in bootloader mode. Thanks.
I d/l'd the Official TMO_1.22.531.6 file and unpacked it, but the 40 MB RAR file contains only a 60 KB(?) file named RUU_signed.nbh
What do I do with that?
Click to expand...
Click to collapse
the phone should recognize the 6.0 rom update. If it doesn't, unpack it again, wait until the screen ask you if you did everything to establish connection, click next and attempt the bootloader sequence again.
ah-HA!! I did it! Officially un-bricked! I downloaded the latest ROM for the T-Mobile site.
ActiveSync now works, I can receive Outlook email, and have even paired up my Aliph Jawbone via Bluetooth! Thanks so much Rolo!! You rock, dude!
I think I might wait a bit before flashing a custom ROM. I'd like to have sliding panels and such, but I'm not in a hurry.
-GoJ
Tweaked removed post as you obviously found the other .zip needed
Ghost of Jaco said:
ah-HA!! I did it! Officially un-bricked! I downloaded the latest ROM for the T-Mobile site.
ActiveSync now works, I can receive Outlook email, and have even paired up my Aliph Jawbone via Bluetooth! Thanks so much Rolo!! You rock, dude!
I think I might wait a bit before flashing a custom ROM. I'd like to have sliding panels and such, but I'm not in a hurry.
-GoJ
Click to expand...
Click to collapse
I'm glad everything worked out well
Same problem with an O2 XDA COSMO.
To put it back to live I need an original O2 XDA COSMO Rom.
Please help or I have to put my loved Cosmo to the bay.
chubbichubbi said:
Same problem with an O2 XDA COSMO.
To put it back to live I need an original O2 XDA COSMO Rom.
Please help or I have to put my loved Cosmo to the bay.
Click to expand...
Click to collapse
Yep, you need the official rom that the phone used from factory. Check for your rom on the official rom thread on the sticky. You might want to pm profezza and ask him if the O2 XDA Cosmo, Orange SPV E600 and the Rogers HTC S621 use the same rom. If they do, he has your official rom there.
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.