Related
I've got a Cingular 8125 (HTC Wizard) that is stuck on the first splash screen - the one with the Cingular image on the background displaying the IPL/SPL/GSM/OS information (image here)
I've flashed with the "button rom", the "wizard love rom", and tried the method to flash with a different rom to a CID locked device. The "button rom" and "wizard love rom" flashed fine, but it still hangs on that splash screen after the flash. I've reverted back to the "official" HTC rom, and it still does this.
The device is NOT CID/SIM unlocked.
This device is NOT under warranty. (A few months out actually, but it was purchased at full retail price without renewing a contract and Cingular seems unwilling to move on any sort of warranty replacement/repair -- big shock huh?)
Is there any hope?
Take out any sdcard/ mini sdcard in the phone and do a Hard Reset.
Button's and wizard are patched Roms,they can be safely flashed to a CID locked phone just like official rom,but no other custom Rom like wm6 will work or flash to a CID locked phone.
Secondly,when you flash,take out the sdcard,it sometimes creates problem in flashing if it needs formatting,and also close/disable any anti virus or firewall and don't surf the net or run any other program,rather try to close down any programs running at the background.
There is no SD Card in the phone, and the SIM card was out when it was flashed.
There have been so many hard resets done to it that it's not even funny.
All unneeded tasks were killed before performing the flash.
I'll try it again tonight (I left the phone at work to give me something to piddle with) just to make sure there wasn't some sort of fluke.
Does anyone think it would be a good idea to just buy an 8125 that has a broken screen or something and replace the innards of my frozen one with the innards of the one with the broken screen?
It isn't crucial that this phone be fixed - it's more of just something for me to fool around with to see if I can get it working. It was actually given to me for that purpose, but if I can get a cheap PDA phone on the cheap, then I'm all for it (even though I'd have to switch carriers - cause I'm pretty sure it won't work with Verizon.)
[EDIT]
I'm gonna try replacing the motherboard battery (I've successfully taken it apart and put it all back together without breaking more than it already is) and I'll report back once I get that replaced. Perhaps this is the problem?
Hi,
Phone info :
ipl : 3.08
SPL: 3.08
GSM: 01.12.10
OS : 4.0.0.0
Using a rom i upgraded a year ago.
So yesterday i decided to update my music on the phone, so not a big deal, but when i tryed to play 1 my telephone said it was out of memory and just went really slow, so i decided a reset, bad move.
After the reset it goes to the 2nd loading screen and just hangs there, i cant do anything.
When booting i can go into the screen with all the colors. (gotta press the cam button).
I already googled 2 days but cant find anything to fix this.
Any idea's ?? or is my phone dead ?
didnt remember this forum to be this dead.... any word ?
All my snarky comments about your misplaced impatience can be set aside for later abuse.
For now, here's how you fix it:
Charge on a wall charger with phone turned off. Verify green light before going any further (flashes don't work on less than 50% charge, and a full charge is the only way to be sure when you can't boot the OS).
Let it boot until it's stuck in bootloader mode (the three-color screen).
Hook it to a computer that you have previously synced to the phone with. Verify that "USB" appears in the bottom of the screen. If not, you're probably hosed.
Flash the ROM you loaded again (or get another ROM, doesn't matter...the one in my Sig is pretty nice, if you re-skin Manila after loading it). If you unlocked this phone before adding the ROM you last had, do NOT flash back to OEM ROM unless you can flash a ROM that removes the unlock (for G4, it's the Remove HardSPL procedure).
After that, you can stave off a lot of these kind of memory problems in the future by loading some kind of RAM indicator (QuickMenu has a built-in one, can manage running programs, and gives you a Windows desktop-style start menu for programs instead of the dumb endless folder parade) to let you know you have too many programs running, and you need to do a soft reset every once in a while, just to jog it clean. It also would be wise for you to load a cleaner to clear out your temp files...you'd be shocked how much crap piles up under the OS when you're not looking.
One last thing, do us a favor and put all your phone's info in your Sig...it helps others have a strong footing for making suggestions...not everyone would know off-hand that you have a G3 or a G4 without that info, and your problems can be made a LOT worse by someone offering the wrong answer based on not clearly identifying your hardware.
Hi,
First, Sorry for my impatient, it kinda sucked to have to go back to my old phone and recharge every 30 mins
In this impatiency (dont know if its a word but it sounds cool ) i found out my t-mobile contract was up for renewal, so i did that and ordered a new HTC Touch HD (will update my sig assoon as it ships )
So i guess ill fix this phone, and find a dutch ROM and give it to my dad, he's always working with excel etc and i think this is perfect
Thanks for your response and fix, sorry again for my impatience.
Sorry, double post, pretty slow forum lately
I have a UK supplied Touch HD from Orange and it`s going crazy!
Problem 1:
Backlight switches off without warning, touchscreen still responds but obviously you can`t see anything! Multiple hard resets will eventually coax the backlight to wake up, but the delay between power button pressed and the "first buzz" of life is around 20-30 seconds. Started happening when it was about 2 months old. Initially it was infrequent and I put it down to an installed software problem, but now every few hours. Other symptoms include the charging light failing when the backlight fails and there is usually an increase in heat around the case. Strangely however when I use it as a sat-nav and it is permanently charging the backlight never fails. I have tried a new battery, desktop charger, turned off fast-sleep, autolock, light sensor, full reset and removal of all my software and it still does it. Sometimes its OK for 5 days, other times it goes "dark" after 10 minutes.
All ROMs updated to latest versions. NB This started happening with the original Orange installed ROMS
My original solution to the problem was to run bootloader which forced the backlight on, but the long delay between on/off and start means this doesn`t work anymore.
Problem 2:
Screen display appears inverted and mirrored after pressing power button during operation. This is an infrequent problem but may be connected.
I live in Thailand now. HTC Thailand will no doubt take it and charge me $250 for a new motherboard whether it needs one or not. I can`t easily return it to the UK and I just hope somebody somewhere has some ideas?!?
I was just talking to another user with completely bizarre issues. What you are experiencing is totally abnormal. Just to make sure it's not a software issue- what SPL version shows up in your bootloader? Also, what rom are you currently running?
Please read next post
Please read next post
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
jamesmclean said:
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
Click to expand...
Click to collapse
So is the phone working properly again with the factory Orange rom? All I can tell you is that if you want to run the 2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship rom you must have a base SPL of 1.54.0000. Even if you use USPL to flash the rom to bypass CID-locking you still need to upgrade your SPL because the new 1.56+ roms are not compatible with an SPL version less than 1.54.0000. Read the guide in my signature for more information.
I see cRaCKwHoRe is on your case, so your in safe hands. I'll leave it to him.
One suggestion though. Instead of creating new posts and saying 'Read Next Post', why not just edit your first post and state 'EDIT' or 'Update' with new information below. This way thread remains short and easy to follow
Just an idea mate!!
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
jamesmclean said:
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
Click to expand...
Click to collapse
Most virus scanners show a false positive that USPL and HSPL are trojans or viruses. This is based on heuristics and how these utilities work. They are tried and tested and are most definitely safe.
And again I stress that you cannot run a 1.56+ rom on an SPL version below 1.54.0000. Since you are running SPL 1.14.0000 this is why you are having such issues. You need to flash a newer SPL version!
After the hardspl back to original Orange ROMS:
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
I had 2 dark events. I wondered if there could be a problem with the memory card, so I took it out. My reasoning being, after it goes dark and is reset, something was causing it to wait 30 seconds before "smart mobility" and/or buzz (if the screens still alive). When my PC does that its usually because there`s a memory card or external hard drive confusing it. Took out the card and it was OK all night. Formatted the card this morning and had no problems all day.This is a guess, I am an idiot! But the memory card is the only ongoing part of my phone; internal storage and ROMs has been cleared or upgraded every month.I dont doubt my feeble attempts to upgrade to 1.56 and bypass HTC`s no upgrades for Orange handsets policy may have been a significant contributory factor. Interestingly, Orange are actively discouraging purchase of the HD, they have had too many problems with their handsets.
Going to keep the phone empty for a few days, no software, no sat-nav and see if I have any more events. Then I think will read your HARDSPL instructions far more carefully and retry the ROM upgrade. Excellent work by the way!
The odd thing about this telephone (apart from the inversion and mirrored display problem, which still occurs) is that following the nuclear option of total clearance and ROM upgrade/downgrade it will behave for an number of days and then the backlight dies again. It could still be hardware!
Going to keep my eye on things for a few days.
But if anyone else has had these problems with their HD or Orange handset, please tell! Maybe you aren`t crazy! To help this is a list of symptoms:
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Thanks!
Looks like a SPL problem only. It is responsible for the boot events and mismatched display drivers between SPL and the ROM most likely did it. Anyway interested in knowing updates once U flash a new SPL 1.54. and ROM..
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
jamesmclean said:
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
Click to expand...
Click to collapse
That's really unfortunate. Seems you have bad luck, consistently
Most people really like HTC devices. They do actually make some pretty decent stuff. Seems you've just gotten rotten luck.
Taken it back up to 1.56 with Hardspl as suggested. Installed Dutty 3.4. And it worked... For one night! Dead again today. I think now it is a hardware fault. So I suppose she`s off back to HTC and I will have to pay some money.
I have been very unlucky with HTC products. I said before I had to have 4 HTC Hermes, thought it would be interesting to tell what was wrong with them:
1. Orange SPV3100 WM5. First generation Hermes 100, hopeless wifi, buggy, returned to store and refund.
2. MDA Vario 2. WM5 Upgraded radio version, better wifi. Decided it didn`t like being a telephone anymore and the radio died after 3 months. Returned to store.
3. MDA Vario 2. WM5 Factory replacement. Dead memory card reader, didn`t make it out of the store when I went to collect.
4. MDA Vario 2 WM6 (Hermes 300). Working wifi, a much better operating system. A real telephone. Lasted 18 months! 2 weeks ago, complete power failure for no specific reason. Won`t charge or do anything now.
But before Nokia and iPhone customers get too smug. I also had an iphone when they were first released in 2007 (1.02) and that was a bug infested piece of junk as well. Got stolen in Bangkok. I really do miss having to reinstall the OS every 2 weeks! And my brother`s Nokia N95 has spent more time with Nokia than with him. 8 visits to Nokia care.
And now I have a broken Touch HD, probably with a power supply issue!
All these phones have one thing in common. They were (with the exception of the Hermes 300) first generation examples. And just before you rush out and pay big bucks for the latest telephone from HTC or whoever... Think, was this phone ready for release? Or was it just rushed out to keep the shareholders happy?
Think about it...
Hell! finally I found someone with the same problems. But I have bought it just some days ago!! The only thing I have done since then: installing tomtom on my sd-card and setting this gps-signal thing to the value 3000.
when I bought it i tried to run it in the store: after turning on, black screen but still vibration when i pressed some button, so it must have been on. Then it suddenly worked, installed the system, everything perfect. yesterday i installed tomtom, today it probably "died" around 20 times. everything the same like already described, screen messed up, after turning on vibration after 30 seconds, god!
is there anything i can do? i just bought that thing
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Click to expand...
Click to collapse
Sounds like you have the exact same problem as my HD: inverted screen, screen blank but still functioning etc...
http://forum.xda-developers.com/showthread.php?t=520781
I am waiting for mine to happen more frequently before sending it away for service. Otherwise they will just return it if they can't reproduce the problem.
Pretty sure it is a hardware problem. I am in Australia and have the original stock ROM.
We may be onto a new fault here. Just noticed 2 more threads with the same screen issues. My phone has been OK for a few days, but today screen won`t wake up at all. Hooked it up to Pocket Controller Pro and it`s reporting a "microp version mismatch 0" in its dark state. Been checking on other websites and this seems to have been a problem with Touch Diamond previously. There doesn`t seem to be an update for microp firmware. One user tracked it down to a loose connection between screen and motherboard. I don`t know! I just wish it would work!
Any suggestions for MICROP issue?
Currently running Dutty 3.4 with 1.56 Olinex. But this has been a problem long before this ROM version.
Fallen Spartan told me this:
"Have you tried going to Start > Settings > All Settings > System > Power > Advanced and making sure device isn't set to turn off after a period of time?"
Until now my phone works without problems, I will report again after some days
Yup, tried that one. Doesn`t work. You will notice after you end a call, the screen will be dim. This is the warning of imminent backlight failure. It is not power management dependent. My problems with the phone started in Feb. Initially intermittent. Now constantly.
Sometimes the thing will work for a few days for no reason. Only way to guarantee no failure is permanent USB power. Pull out the USB and watch it die, instantly! That`s with the original or the new battery.
New motherboard may be the only solution. But it is worth noting that when I had problems with my Hermes and it had to go back to HTC 3 times, each time a new phone was sent. On the service report "New motherboard" was reported. The guy in the T-mobile shop told me they`re too expensive to repair so it`s easier giving you a new one. They still hold onto the old one for 3 weeks though!
Might try to repair the Touch HD, I still have my Samsung SGH. (It`s very slow!) but I think I will wait for ASUS or Toshiba phones with snapdragon processors. Had enough of HTC and don`t want another iphone.
This is a hardware issue. No if's, and's or but's. It is caused by a disconnection between the screen and the motherboard. A faulty motherboard or a loose / broken connector is the usual culprit. I would say 7 out of 10 times it is due to a loose connector. It is a poor design to begin with and after being dropped or roughed up enough it tends to break or get loose. HTC typically just replaces the motherboard in a warranty repair situation.
If you are lucky and just have a loose connector and are comfortable with opening up the device yourself, you can disassemble the device and re-connect or re-solder the 2 port connector that connects the motherboard with the screen. Of course this will "void" your warranty so I wouldn't recommend doing this unless you are comfortable working on micro-electronics. If your case is the type where it is intermittent and it works sometimes and then sometimes not, then you have a loose connection and it just needs to be reconnected or re-soldered.
I have seen and fixed a couple of these now.
I have a Hermes (Orange SPV 3100 but unlocked). The phone has stopped working but everything else is fine.
I've tried putting other sim cards into it, cleaned all the sim contacts etc with no success at all. As far as it's concerned, there is no valid connection. Phone and data connections don't work. All the Windows settings and programs run fine, it's just the phone that doesn't so I have a pda without a phone! I wasn't trying to flash a rom - the op system is all as original except for the unlock.
I don't think it's worth enough to pay for a professional repair so any suggestions for tracing and curing the problem and hints as to whether its likely to be a faulty connection, faulty parts or software problem?
Thanks.
I have the exact same phone, and similar problem. The difference is my phone is not completely unusable, it sometimes works for a while and sometimes doesnt.
I have just - 10 mins ago - flashed a new radio rom to see if it helps and so far (10 minutes!), so good. But I will need to leave it for a couple of days to see if it works properly.
Is there an "X" beside the signal icon? Also have you checked the Comm Manager and disable the phone and enable it again?
Ah well I didnt need to leave it for a couple of days, its not working again even with new radio rom.
Ive tried new o/s, new bootloader and new radio but still the same problem, nothing else to try really ?
(btw: Mine usually has an exclaimation mark next to signal strength.)
Carthief When did the problem first start occurring? Did you flash a radio/OS ROM and it started to happen, or did it just happen out of the blue?
Sorry I did not see this post...http://forum.xda-developers.com/showthread.php?t=562486
I don't know dude. Maybe one of the senior members can help out.
Shawn80 said:
Is there an "X" beside the signal icon? Also have you checked the Comm Manager and disable the phone and enable it again?
Click to expand...
Click to collapse
I will check tomorrow. I am using a different phone at the moment and have left the Hermes at the office.
Hi Shawn, yeah that post covers when my phones problem started - I hadnt flashed anything recently when it started messing up.
I've tried tonight;
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Problem 5:
METHOD 1
But I didn't flash the patched radio.
Phone is working at the moment... I'll update if it is still working or not tomorrow, if its still working maybe Batxda could try it out as well
--------------
Update:
--------------
Phone worked all night, and this morning, but froze up this afternoon and needed rebooting. It's currently working ... but probably not for long! My battery is running out very fast as well.
Shawn80 said:
Is there an "X" beside the signal icon? Also have you checked the Comm Manager and disable the phone and enable it again?
Click to expand...
Click to collapse
Hi again. Yes, there is an "x" beside the signal icon (normally meaning that phone is turned off) and also beside the connectivity icon (two horiz arrows and a "x" meaning no active connection). Also, I've just noticed that both of those icons no longer respond to stylus taps. All the other icons do.
I've tried turning the phone on via Setup > Connections > Comms and Setup > Personal > phone. Neither work, in fact, they do not respond at all.
I haven't tried the cure that Carthief tried but then, I've never flashed any roms on this phone either. I am apprehensive about that because I haven't done it before so, if that's the solution, I would need to find a free evening and do lots of reading.
BTW, the unlocking was done ages ago professionally, not by me.
Any ideas?
Thanks.
Batxda said:
Hi again. Yes, there is an "x" beside the signal icon (normally meaning that phone is turned off) and also beside the connectivity icon (two horiz arrows and a "x" meaning no active connection). Also, I've just noticed that both of those icons no longer respond to stylus taps. All the other icons do.
I've tried turning the phone on via Setup > Connections > Comms and Setup > Personal > phone. Neither work, in fact, they do not respond at all.
I haven't tried the cure that Carthief tried but then, I've never flashed any roms on this phone either. I am apprehensive about that because I haven't done it before so, if that's the solution, I would need to find a free evening and do lots of reading.
BTW, the unlocking was done ages ago professionally, not by me.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Maybe I missed it but I did not see any mention of your doing a Hard Reset. (I assume you have tried soft resets) In general if the problem persists after this it rules out most software issues. I also think it's worth a try because of your comment about the icon being unresponsive.
Mike
Mike
I had done a hard reset but, just to be sure, I've just done it again. After the first it locked up at the password screen so I did a few more. Next, I let the Orange config run through. With the third, I removed the battery before Orange it did its thing. Both the same - no active phone but no lock-up either.
Icons on top bar still not active and x's against them.
When I go to settings > Personal > Comms, the phone icon is highlighted and appears to be "on" (no "x") but the top bar icons still show that it isn't. When the comms phone icon is clicked, the cross appears and the phone is, presumably, turned off and can't be turned on again.
When I go to settings > Personal > Phone, it says that the phone is off, would I like to turn it on. Click yes but it doesn't work.
BTW, I'm using an O2 sim card which works perfectly in a NIKI (touch dual).
I hope this is a software not hardware problem. Is there any point in flashing a new radio or complete windows rom? If so, which one would you recommend (it's a minefield for one of little brain)
Many thanks.
B
I did think you might already have tried a hard reset. In general that tends to point towards hardware, BUT corruption of the ROMs can occur. Unfortunately that is not my area of expertise. Hopefully someone will recommend something here. You could always look on http://www.mrvanx.org/thg/ making sure you have Hardspl installed.
Mike
Hi all, my phone is still not working completely but it does seem to be staying alive for longer periods now.
I have just downloaded the latest (from Oct. 2007) software upgrade from Orange for the Hermes - I think it is windows mobile 5, not sure yet. I cant install it tonight but Im going to try that tommorow.
I downloaded the Orange update but it wouldn't load on my phone. all I got was an error message which said it was the wrong rom for the phone. I don't know whether that's because I've had it unlocked or maybe my rom is newer than the update. anyway, I'm no further forward.
I've just noticed that, in Settings > Device Information, it is blank against the radio version and the Protocol version and that there is no IMEI listed either. I guess that means the radio is corrupted so I will try installing a new one. It is op version 14.123.1.614 and ROM version 1.23.61.4. Which radio is recommended.
What does the missing IMEI number mean or is that also connected with the missing radio?
B
Hi Batxda, I dont know which radio to recommend, mine is Radio version: 1.47.30.10 and ROM version: 3.54.255.3
My phone has now been working for over 24hrs, battery has stayed charged as well... so I haven't installed the Orange rom yet.
I bought a new phone having pretty much given up on this one... and now it seems to be working again!
Nope. Not working. Ran for over 48hrs but locked/froze up today with calls going straight to answerphone, battery drained from 70% to 20% in about two hours as well!
My last attempt is going to be running the phone with no memory card in, and no sim card with phone disabled. Will report back.
Have you had any luck Batxda ?
Radio flashes all lock up - help please
carthief said:
Nope. Not working. ...............
Have you had any luck Batxda ?
Click to expand...
Click to collapse
Sorry to hear that. I've had different but similarly unsuccessful times. I hope your experiment goes well.
I flashed with HardSPL (SPL-2.10.Olipro) then tried to flash a Radio.
1st I tried v 1.11.00.00 running from the PC. It froze so I had to unplug it. That messed everything up and I ended up with it stuck on the bootloader screen (Type 2a) so I used mtty and found that command "set 16 0" worked so I could return to WM5.
2nd I tried to flash radio v 1.47.00.10 from the SD card. It started OK, got to about 20% and stopped. That was at 11:15. Its now 13:30, 2.25 hours later and it hasn't moved in that time. I am going to have to stop it but I'm sure it will end up corrupted again.
H E L P anybody, how can I flash a radio to this damned thing?
BTW, it is a Hermes 100.
B
Batxda when I reflashed a new radio I just followed the guide here:
http://www.mrvanx.org/thg/index.php?option=com_content&task=view&id=18&Itemid=26
It sounds like you've gone through the same procedure as me so you've probably already followed that guide...
I don't know what to suggest, but if it was me, and the radio wouldn't flash, I would (being a bit dim ) try it a few more times until I was exhausted...
I've just rebooted mine to see if I could provoke it to do anything with no sim/memory cards in. It gets to the password entry screen and tells me I've entered the wrong password but I know its the right password !! Does anyone know where/how these phones store the password ?
carthief said:
Batxda when I reflashed a new radio I just followed the guide here:
http://www.mrvanx.org/thg/index.php?option=com_content&task=view&id=18&Itemid=26
It sounds like you've gone through the same procedure as me so you've probably already followed that guide...
I don't know what to suggest, but if it was me, and the radio wouldn't flash, I would (being a bit dim ) try it a few more times until I was exhausted...
I've just rebooted mine to see if I could provoke it to do anything with no sim/memory cards in. It gets to the password entry screen and tells me I've entered the wrong password but I know its the right password !! Does anyone know where/how these phones store the password ?
Click to expand...
Click to collapse
I have a AT&T 8525 Hermes that was having No GSM issues.
I'm not sure if both of you seen the No GSM message when booting the phone (when it was bootable) & if you did, here's what I did to get the phone working again.
I removed the battery & pressed hard against the back stainless steel plate especially around the area near the battery contacts. It worked for mine & the No GSM issue would go away. If it happened again, then I repeat the same procedure & it works again.
My conclusion is that the GSM chip has broken or loose contacts with the motherboard so as long as the contacts is good, that keeps the radio working. BTW, this phone was dropped before & after that, this issue started happening.
Lastly, I'm not sure if your issue is really with the password...that's just a symptom of something else that is wrong with the system...not sure if it's entirely software or perhaps hardware or combination of both.
konker said:
I have a AT&T 8525 Hermes that was having No GSM issues.
I'm not sure if both of you seen the No GSM message when booting the phone (when it was bootable) ...
Click to expand...
Click to collapse
No, I haven't seen that message.
Since the last post, I've tried to flash various radio roms, two WM6 roms and what XDA says is the original WM5 Orange SVP M3100 rom for my phone (v slightly different version number though). All of them hang at around 11% or give an error message. I've ended up with a Dopod start screen (from one of the WM6 attempts) and a funny mixture of colours but I can still start Windows so I've got a pda with no phone access.
Taking your message on board, I'm starting to think that there is a hardware fault preventing the radio from being recognised. That is unless there is something fundamental that, being a n00b at this, I'm not doing. I've put Hard SPL on the phone, flashed roms and failed, reset it with MTTY (set 16 0) and used a variety of radio and main roms. Is there anything else I should have done?
I'm about to give up and see what it's value is and then see if I can get a hardware repair (if it's worth it). Otherwise, I've heard that some fetes have a throw the mobile competition ......... !!!!!!
B
My still under warranty 6900 has a totally black screen. I can see that the backlight is on- it is the actual lcd that is black and the phone will receive calls. (I can't see if it goes to bootloader since the screen is black) Presumably, this has nothing to do with the nsfan6.5 ROM on it.
Verizon CS told me on the phone that if they sent me a warranty replacement then found it to be water (or physically) damaged, they would "have to" bill me for the RETAIL value of the phone. She gave me the option to take it into a verizon store to have a tech first OK the replacement to avoid this possibility. He OK'd it and is should be here shortly.
Is there a way to get it back to stock rom while not being able to read what is on the screen? For that matter, is this even worth doing or will VZW not notice?
PS- I'm trying to decide what ROM to put on the replacement phone- Android is tempting but I think I'm going to wait for the smart people to finish getting stereo bluetooth and standalone GPS all sorted out. I'm sure I'll play with it on the SD card in the meanwhile. Thoughts?
I realized I should add:
On the phone I need to send back, I have the bell (complete with ugly blue start up screen) 3.42.50 radio and whatever nsfan 6.5 build was most recent back then.
To accomplish the flash, I also have a 2gb microsd card (with reader) and have downloaded the stock verizon rom.
Also, the touch screen appears to work (vibrates on touch) however, no amount of guesses with random screen touches could get the phone to connect with activesync or tether (sadly, the last type of connection I made was as a removable drive). In other words, things might not be where they are supposed to be on the screen so telling me to tap at pixel 120x200 (or wherever the "next" or "ok" button might invisibly be) may or may not work.
thanks again!
Enter bootloader - Hold Camera and Power and soft reset.
Connect to usb
Run RUU from stock rom.
dvirus1023 said:
Enter bootloader - Hold Camera and Power and soft reset.
Connect to usb
Run RUU from stock rom.
Click to expand...
Click to collapse
LOL, thanks. I just logged on to say I'd figured it out. It finally dawned on me that 10 months ago i'd noticed (or heard or something) that you didn't need the active sync connection going if you entered bootloader first.
Fantastic. Many thanks.
Just in case someone reads this trying to do the same thing: I saw elsewhere that you need to run imcoke.41 before reflashing with stock ROM so that's what I did.
Correct?
I think you need to run the .40 unlocker, not the .41
.40 is supposed to be overwritable, .41 is not
I've been using .40 before I send back my phones. When I flash the VZW ROM it usually errors out the first time, then you follow the instructions on the screen(pc) and it takes the second time.
scotttr said:
I think you need to run the .40 unlocker, not the .41
.40 is supposed to be overwritable, .41 is not
I've been using .40 before I send back my phones. When I flash the VZW ROM it usually errors out the first time, then you follow the instructions on the screen(pc) and it takes the second time.
Click to expand...
Click to collapse
You're right. I'm hoping it was .40 that I used and just wrote .41 here. Regardless, I already sent it off.