Related
Ok, I have spent the past few hours both ruining my phone, and then trying to fix it
So here is my situation. I have a newly purchased SX56 Phone that I decided to try to upgrade using the exe off the Siemens site. I made sure my battery was fully charged, plugged into the cradle, and started the process. At about 10% during the Radio Stack upgrade, the phone failed. My desktop told me to unplug the USB cable, and then reset, at which time the Radio Stack would finish updating. This of course didn't work, and I got the 1% error. It kept rebooting with the 1% error. I proceeded to try to soft resent, and go the now infamous white screen.
I don't currently possess an SD Reader, and its one in the morning, so I don't imagine getting one until tomorrow. In the meantime, after reading MANY posts, I'm not sure what to do.
I suspect that my Radio Stack is gone or fried, and I'm not sure I understand if I can somehow reload it or not?
I'm assuming my current ROM is still intact, only because for one brief second at one moment, I got my PPC up again but it was barely functional, didn't have a start menu, just a white bar at the top of the screen where the start menu bar was before. Since then I've only gotten white screens.
I have tried doing the boot-loader just to see what I got on my phone, I apparently have Wallaby 5.22, but I don't understand if this is a bad thing or not, as I saw many people talking about getting down to 5.17 or 5.15??? Furthermore, I didn't have an SD card in the phone when I pulled up the bootloader, and the phone just got a GSM ERROR. I have yet to find informative info on if this is ok considering I have nothing in there, or if this is a problem for me.
I have also tried the volume + soft reset to get back to the 1% error, but I haven't seen that yet.
My end goal is to have a functioning phone, I would like to have WM2003, but its not necessary. I'm just not sure anymore what methods to try from my current situation.
Keeping in mind I am frozen on the white screen page, Should I:
1. Try to reinstall the Radio Stack first? (and if so how? Does it involve copying files to a SD card? I assume so because I cannot connect to my phone anymore through active sync)
2. Try to get my PC2002 or WM2003 up and running and not worry about the Radio Stack just yet? (also how if this is the case?)
3. Try to return my phone? (This is a last option, because I'm not sure I can even find this phone anymore in my area, and I really like it, and would love to continue to use it)
and finally, am I pretty much screwed on charging my phone until I fix everything else?
Thanks Again
Thanks for all the great information
unless you are in US
then installing the us radiostack which is shipped with the s56 update is a big nono!
imho then installing any radiostack unless you have gsm signal issues or if your phonecompany tell you to is somewhat a risky buiness
Rudegar said:
unless you are in US
then installing the us radiostack which is shipped with the s56 update is a big nono!
imho then installing any radiostack unless you have gsm signal issues or if your phonecompany tell you to is somewhat a risky buiness
Click to expand...
Click to collapse
I am in the U.S., and ATT Wireless sent us all text messages telling us about the upgrade,...
If the radio is knackered the only option is to return it or get somebody on the forum to help that has jtag kit for direct chip flashing. Personally I would send it in for replacement.
cruisin-thru said:
If the radio is knackered the only option is to return it or get somebody on the forum to help that has jtag kit for direct chip flashing. Personally I would send it in for replacement.
Click to expand...
Click to collapse
I seem to see others talking about reinstalling the Radio Stack using RSUpdate, etc...would this not work for me? How would I know if my RS is completely gone, or just malfunctioning because of a bad install?
Not quite sure what the issue is with this one. Back in the beginning of the year my XDA II fell from waist height when the carry case snap popped open (notebook bag brush across the front catching on the flap). The only noticeable problem after that was that the power button no longer works, so I have to power it on by pressing the phone or address book buttons etc.
About a month and a half after that incident the phone suddenly just stopped getting signal. I was using the standard shipping firmware with a few apps. Soft reset, hard reset both failed to fix the issue, the phone simply will not pick up the network. Interestingly enough if I play with the phone settings and go through the process of manually selecting a network the phone WILL pick up available networks in the area (this kills my idea that the GSM radio failed altogether). For now I've had to switch back to a junk phone as I've been unable to figure this one out. Anyone have any ideas on this one? I'm using T-Mobile for a service provider and I'm based out of California.
Also, does anyone know of a place that can do diagnostic/repairs here in the U.S.? So far my searches have come up empty.
Thanks in advance.
Give this a try:
Reflash the phone with any version of ROM and it should start working fine again. I think the problem is that you're radio firmware somehow got corrupt.
Ok, guess I'll have to give it a try. I've been avoiding trying the slightly riskier stuff as I got this thing via an independant third party, so warranty/support are iffy.
Is there a general release ROM that I should be looking for (using T-Mo in U.S.)? Or should I look to cooking my own (which I'd rather not)?
You can try upgrading the ROM with the same branded one. That shouldn't void the warranty.
I.e. If you've got an O2 device, get the new O2 ROM
Reflashing
I have had a simular problem with hard locking. Finally my phone quit working all together. I went into boot loader mode and flashed it. It's like having a new phone again. So yeah.. I think the ROM's can get corrupt.
Brandon
NeoCole: Looks like you are using T-Mo in the U.S. Mind if I asked what you flashed yours with? Did you use a specific ROM, Radio Stack version etc.?
I'm running an unlocked i-mate (contradictory to my subj title, I know).
Flash it with the T-mobile 1.72 ROM
ROM Version
Well.. I flashed it with the IMATE 1.72 ROM and used most of it's extended ROM. I used the battery Meeter from the Qtek extended rom. I built most of my extended ROM Myself.
I look at T-Mobile's Beta 1.72 ROM like I look at Windows ME. Both should have never happend. I can't count how many times I had a hard reset with the T-Mobile ROM. I'm not sure if it was a combination of the programs I was useing or not. I saw a post that said SBP was possibly causing the problem. So I quit using SBP products. Later I still had to HARD RESET from time to time. Now that I'm running differently, My device has never been so smooth.
Let me know if this helps,
Brandon
Looks like I'm pretty much screwed. Without a working power button I can't do a hard reset into bootloader mode. When I try using a utility app that allows me to do a hard reset I can't hold down the jog dial at the same time. Good times.
*edit: yeah, that would be 'can't' hold down the jog dial.
You don't need to boot into the bootload to perform an upgrade... the upgrade software takes care of everything for you (except the hard reset at the end)
All you need to do is sync through Activesync and then run the upgrade program.
I would (and have!) flash the imate 1.72 ROM. It is very stable for me and HAS improved the battery life of my imate.
As stated above, just start the flash process and it will put the device into bootloader mode and perform the flash. It will need a HR at the end, but since your power button is not working, maybe you could remove the battery, slide the red slide/switch back into place for a few seconds as if the battery were there, then slide it back, put in the battery, slide it back into place and press one of the puttons to turn it on.
Hey . . . it might just work!
imate 1.72 ROM did the trick. After I actually READ all the posts regarding the ROM I realized it came with an installer and got that done. So far so good. Now if I could only find my missing tomtom 3 cd key that went MIA during my last move
Hey, that's fabulous! Welcome back to the world of convergence.
i got my mda compact last week and updated the rom to an imate jam rom the first day i got it.
now since then i have had to do several hard resets because after so long whenever i press the power button to turn the screen on, the screen is completely white and i cant see anything else except this.
Is this a known problem or does anyone know what to do to sort this problem as its getting a tad annoying having to hard reset almost every day!
Any help will be greatly appreciated
jamzi said:
i got my mda compact last week and updated the rom to an imate jam rom the first day i got it.
now since then i have had to do several hard resets because after so long whenever i press the power button to turn the screen on, the screen is completely white and i cant see anything else except this.
Is this a known problem or does anyone know what to do to sort this problem as its getting a tad annoying having to hard reset almost every day!
Any help will be greatly appreciated
Click to expand...
Click to collapse
May i ask why you upgraded it the day you got it? I also have the MDA Compact and i still run version 1.01 P) because i don't have any problems with it.
Did you just blindly update or did you have problems before updating?
the reason i upgraded the rom was that i wanted rid of all the t mobile stuff as i use o2 mate.
the only other stuff i installed on it a game called s tris, pocket painter and tcpmp player, not sure if either of those could have anything to do with this.
Any ideas mate?
jamzi said:
the reason i upgraded the rom was that i wanted rid of all the t mobile stuff as i use o2 mate
Click to expand...
Click to collapse
Did you unlock the sim?
And are you aware that you can actually remove all Tmobile junk pretty easily without having to upgrade?
it was already unlocked by the person i got it from.
yeah i was but i just thought it would be quicker and better if i just changed the rom.
i just downloaded the newest mda compact rom. do you recommend i go back to that one and get rid of the t mobile stuff manually?
oh and have you ever heard of this white screen problem that im having?
jamzi said:
it was already unlocked by the person i got it from.
yeah i was but i just thought it would be quicker and better if i just changed the rom.
i just downloaded the newest mda compact rom. do you recommend i go back to that one and get rid of the t mobile stuff manually?
oh and have you ever heard of this white screen problem that im having?
Click to expand...
Click to collapse
I think it is a better idea to go back to the original 1.1 ROM. I removed all T-mobile crap with the push of a button.
You have to hardreset the device, when you get to the today screen immediatly softreset the device and voila. No more T-Mobile crap.
When you get to the today screen for the first time after a hardreset the device is programmed to install all Extended ROM files (which include the TMobile crap).
Simple as that .
cheers mate.
what should i install from the extended rom folder without the risk of installing any t mobile nonsense?!
i thinkive just about figured out what to install but i cant seem to get the smart dialler function without installing the t mobile skin over the phone function :?
If you go to the XDA devs ftp in the magician extended rom folder, grab the smart dialler from the Jam extended rom. I don't necessarily agree with reverting back the rom but if it fixes it, great.
If you want a completely unbranded rom, go for the I-mate WWE versions of the rom. I haven't had a single problem with any up til 1.11 (I haven't tried 1.12 as I have no need to go any higher)
im looking in the shipped roms folder now, is there any WWE 1.11 one that you would recommend? its just there is so many and ive had this white screen problem with every rom ive tried i want to make sure i choose the correct one!
Well if it happens with every rom you've tried then I'd say the problem must be hardware related. If a rom upgrade, downgrade, or anything doesn't fix the issue then it has to be the one thing that hasn't changed, your hardware. My recommendation is put the original rom back on and get it looked at under warranty, unless someone else can offer another explanation.
The latest rom I've installed and still on my phone is the Anansky BigStorage rom. I haven't needed to change that for months, although I've played with all the I-mate roms up to 1.11. The only change I've made since then is the 1.13 radio upgrade.
ok ive went back to the mda compact rom (one i downloaded from a link on this site, not the ftp)
got rid of the t mobile stuff as explained earlier and changed the splash screens too with a cab file.
fingers crossed so far so good!
im terrified to turn the display back on after it goes off now though! and a bit apprehensive of installing anything after the last few days ive had!
Spoke to someone technical about the problem with screen alignment going wacky 3-5 times a day. He said the system files are probably corrupt and to do a Hard Reset. Told him I had upgraded ROM and wondered if that could have affected my 8125. Nope. His solution was to ship back to HTC or go to Cingular where they would reinstall Cingular ROM, as this is a low level problem and flashing ROM wouldn't fix the problem since the files are Cingulars. Sort of like reflashing BIOS on a PC, really low level.
Is this info correct? Phone is SIM/CID unlocked. Can the basic ROM be changed? I have already applied a ROM update to IPL/SPL and radio. I am using Suncom (not Cingular) and would love to get rid of Cingular splash screen and stuff.
Anyways, Hard Reset and reinstalled everything. 5 days now and 8125 has not gone out of alignment.
Thanks all.
I'm having a wierd problem with my Hermes. I have the Scnaps 4.01 WM6 rom on my phone right now, but the same thing happened with Blacks rom when i was running that.
Sometimes when i turn it on, it says it has signal so i try to make a call i get operation failed, and then you see the signal drop back to searching, it finds the network and then logs back on. Same thing happens even if i dont make a call, turn on the hermes, and look at it, has signal, then 10 seconds or so later it drops to searching (it never really had signal) then logs back on, and then sms's get delivered. I've also had people try to call me during this time and it's like the phone is off.
I've tried a few different radio versions recently but same behavior with all of them. 1.54.30, 1.54.07 and currently on 1.43.
Something else weird is the fact that it seems like (I could be wrong) this only happens after having the rom on for a week or so, ie after flashing a rom, the first week or so i don't get the issue, then it slowly starts to happen - this could just be my imagination.
Has anyone else had this issue? Any ideas/suggestions welcome, thanks
Hi Ferni...
This is something that is becoming quite an issue recently
Firstly, have you made sure the SIM contacts are nice and clean and everything is fitted OK - and have you tried a different rom image? If not - try these first.
Secondly, where abouts in the world are you and what network are you on?
Thirdly - when did you install 1.54.30 and 1.54.07 - did your problems start before or after you flashed a 1.54x radio - and what radio were you running before trying these.
Finally - What other information do you have about your device - is it a herm100,200 or 300, what IPL/SPL is it.
Sorry for the 100 questions, but I'm investigating these issues at the moment as a lot of users have had similar problems especially after using radio 1.54.x as this thread discusses.
Thanks for the reply. Just read the other thread you linked to (and the threads it linked to). Interesting to know i'm not the only one.
I just pulled the sim out and gave it a rub and the contacts and put it back in. I also had a bigger battery in it, so i removed that and put the standard one back in. See if that makes a difference.
I used to run the black rom, now I run the schaps one, trying to avoid flashing it again just a pain to resetup everything you know....
I'm in Australia, on the Optus network. The JasJam is actually only sold by Telstra here, but i got one 2nd hand and use it on the optus network fine (Optus sell the Dopod). The latest radio rom 1.54.30.10 i belive is actually from Telstra - in the offical WM6 rom from them for the JasJam.
As for when i flashed which rom and when the problems started happening - i can't really say sorry, i didn't keep track. I've had the phone around 6 months, flashed it with a cooked WM6 rom (black i think) when i first got it, i probably updated the radio as well.
How do i tell if it's a 100, 200 or 300? Also not sure what SPL it is, HardSPL or something?
Tempted to flash it to the official telstra rom released recently with the latest radio, so if it does die completely i can send it back for warrenty. What do you think?
Thanks for the info - every little helps at the moment!
Firstly, yes - the radio you're running is native to the area and network and so if you're running 1.54.30.10 and it goes duff you should be covered by your warranty so don't worry. Also, it's not certain yet that there is definitely a problem with this radio so don't loose too much sleep. (Most of the problems linked with this radio that I've researched so far seem to be coming from Europe and after rolling back).
As for flashing with the official ROM, that's a decision for you - however in the cases of sudden GSM death, the phone will still boot to Windows and it is still possible to flash the OS and bootloader roms (just not the radio) so if it did go bad with an unofficial ROM on it you should still be able to roll it back - again sleep easy ;-).
As for the problem - the steps you've taken are a good start, see how it goes and keep us informed here.
It may be worth also trying to manually set your band (if applicable on your network). Sometimes problems like this can be caused by issues on the network itself and trying an alternative (maybe a friends) SIM card for a different network or even manually switching the phone to GSM (if available) can "cure" a problem (although it's a pain if you specifically need to use 3G and it's data speeds!).
Finally - to see your full device information you need to enter the "bootloader" (tricolour) screen. Hang on to this information on the bootloader screen as it can be useful if you ever encounter a bad flash.
To do this, hold the OK button on the left of your phone and the power button on the right then press the little reset button with your stylus. You will then see the model at the top with the IPL version below it and then the SPL version below that. To get out of the tricolour screen, press the reset button again. Needless to say this won't erase anything or damage your device but make sure you close your apps and save your data first
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
ferni said:
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Click to expand...
Click to collapse
What radio are you currently running? Thought it was 1.54.30.10 or did you change that the other day when trying a new ROM?
ferni said:
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
Click to expand...
Click to collapse
*IF* this is the sudden GSM death syndrome then it will progressively get worse unfortunately - but it might not be that (think positive!)
[edit : removed - brainfart you answered my question] Incidentally, just updated this thread here - Look at post #60, it's a long post but there is a couple of possible things for you to try there (multiple flashing on a "chilled" phone) for users who STILL have some GSM connectivity... Might be worth a go and certainly could do no more harm... The post itself is very technical but just follow the instructions about 3/4 way through the post and ask any questions back here in this thread so things don't get too confused!
In terms of flashing your ROM - when you _really_ feel the phone may die _very very soon_ then it's worth considering flashing it with the latest OFFICIAL rom from your provider while you are able to do a full flash but don't leave it until DHL are at your door to collect it just in case you need some help!
Oh yeah... and finally for tonights post - Rolling back from Olipros Hard SPL... back to the normal, official SPL - Mr Vanx has written a fantastic guide to this here complete with illustrations - That should save you some searching
The SPL rollback, of course, should be the very last thing to do before shipping it back under warranty of course tho - just incase you need it in the mean time!
Good luck - and keep us updated - particularly if all works again (or not)forum.xda-developers.com/showthread.php?t=299070&page=32
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
ferni said:
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
Click to expand...
Click to collapse
Yes. Crazy as it sounds, if the previous radio caused "logical" bad blocks - a combination of a couple of flashes in quick succession with the PLA at a cooler temperature might recover them! (temperature issue came from the data sheet for the chip itself - Apparently more efficient writing at temperatures a minimum of 10C below ambient).
Good luck - let us know how it goes... I've got my fingers crossed you'll have a Hermes with it's wings back shortly
Last night the phone got worse, i had a missed call, tried to turn the unit on to see who it was and it wouldn't turn on, so i soft reset it, it booted up ok, but wouldn't pick up a signal.. eventually after about 5mins it did, but then it locked up. So i pulled my sim card out put it into an old phone which i'm using for now.
This morning came into work and put it in the fridge for 15mins, and flashed the latest radio firmware on it. Then flashed the latest official telstra rom onto it (getting ready for warrenty). That's just finished, only step left is to put the original boot loader back on. May test it again for a couple of days to see if i can get it to do the same thing on the offical rom/radio before i send it back. Will let you know.
Thanks for your help so far.
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
ferni said:
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
Click to expand...
Click to collapse
We did indeed - Ah well, at least you're covered by warranty
Mr Vanx has written a fantastic guide to rolling your bootloader back - complete with illustrations. (repeated for others who've just started reading this thread)
Yeah hopefully it gets covered under warrenty. That bootloader guide worked perfect
For anyone who cares, they replaced my radio board under warranty - I now have a new IMEI number. Haven't got the phone back yet to test to see if it's fixed.
Did you ever upgraded the Radio ROM ?
Or was it always 1.43.
My first ROM only upgrade.
http://forum.xda-developers.com/showpost.php?p=1462158&postcount=292
Yeah i had tried a few different radio roms before this. I suspect it didn't like being flashed so many times.
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
gondalguru said:
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
Click to expand...
Click to collapse
I flashed one of the wm6.1 roms and ended up with 1.54.07 radio and was getting the "modem disconnected" error message everytime I tried to log on to the internet.
I reflashed the original WM6.0 ROM from AT&T and then reflashed my radio to 1.48 (can't go back to 1.16 because of the radio bootloader I think) and then tried to log on to the internet.
That didn't work
But then I made a phone call to my home phone
tried logging on and it worked.
Been working fine since
crossing my fingers and hoping I dodged the bullet, not gonna flash again til ATT comes out with 6.1 then if it acts up even a little I am gonna send it in for warranty repair.
I hope this procedure works for you mate.
pedro2k said:
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
Click to expand...
Click to collapse
Not exactly sure where this setting is, the closest thing I could find was to install HTweakC. And now I have auto attach off. I also live in WI rural area, and 3G has been growing. Coming closer my home, and when I go to work it switches to 3G from Edge and I believe this is the biggest cause of this problem. I will let everyone know if this has helped me or not.
Thanks pedro for your suggestion. I will try that and will report back.