I have a TSM 500 and tried to install the WM 2003 SE Upgrade as listed in http://forum.xda-developers.com/viewtopic.php?t=12101, However it immediatelly gave an error and all i get now is the boorloader screen with the serial no. displayed. I know in the post it states that if you do get this, just reset it and start again. I have tried to do a hard reset, but it just fails to respond. Please help as this was the first time i have tried to do anything like this.
Related
I have no idea what's going on with my XDA II. I have not done anything to modify or upgrade it recently. But suddenly the phone froze one day. I tried doing a soft reset but the phone just shut off. Kept pushing power button but nothing worked.
I then tried a hard reset which didn't work either. I finally just removed the battery and the sim card and then replaced them. My phone finally booted up and went through the standard hard reset sequence. I restored my backup information into the phone. Later on it froze again...with the same problem.
I finally got my phone working, but it freezes almost everytime I try to do something. When i do a reset, whether hard or soft, I get stuck at the boot screen with nothing happening. I reset it about 8 or 9 times before i get back into the phone and go through the intro to WM2003 again.
When i do get in, i can maybe make a call or two before the phone freezes up again. Don't know what to do, but really confused. I was going to contact o2 because the phone is still under warranty. However, I have upgraded to the TMobile 1.6 rom.
If anyone has any suggestions on how to fix this please let me know. If not, does anyone have the original o2 rom that I could get a hold of? Thanks for all the help in advanced.
Does the phone freeze after you restore backup or does it do it even when you use it from scratch after hard reset?
It freezes no matter what. Most of the time, it'll refuse a hard reset. I would reset it, hard reset it and the phone will just load up on the Tmobile screen and stay there. Sometimes i'll get that circle thing that shows the phone is doing a process...but it'll go in circles forever.
Sometime down the line it'll actually let me through. Then i'd do the whole WM2003 intro again.
So to answer that question, it's not only on my restore, the phone consistently freezes up.
Looks like it's time to avail of the warranty and have your phone replaced.
I know, but in order to do that I have to get the original rom because i'm on tmobile 1.6 rom.
Mate, did you try to reinstall the 1.6 rom? Maybe download the latest ROM version and try to install it from your dead device...
My phone is just freezing on the boot screen and sometimes i can actually get in and use the phone for a while. Does this still constitute it as dead?
Since I can't get past the boot screen most of the time, I can't connect the phone to the computer to install the 1.6 rom again.
However, I did get past the boot screen once and did manage to sync it with my computer and reinstall the 1.6 rom. No help...same problem...
Ok, i finally got in and managed to update the rom to the new O2 rom. Everything was working fine for a long time. I used the phone and no problems. I left the phone on the sync cradele over night and by morning the phone was frozen. Reset and getting stuck at boot again...
ANyone have any ideas?
i also get this problem.
I have found many ppl got this problem, but no one has solution.
so what is everyone doing about it?
Tried to upgrade the ROM on an M1000 to 2003 SE from a 1.600 version and wound up with the following symptoms.
Only able to see the bootloader (v1.06, but computer recognises the device when in the USB cradle)
HimaUpgradeUT will run as far as the screen saying what ROM it's replacing (though it says that there is nothing on the device itself). Then when I press "next" it just hangs on the erasing ROM 0% screen until I get an Error 112.
Tried using two different computers and still get the same error.
Tried different HimaUpgradeUTs and still get the same error.
Tried hard resets, soft resets, reinstalling ActiveSync, disabling ActiveSync etc.
Going insane and need suggestions. Help!
I think your best bet is to revert to the original ROM. I thought it was on this forum, but I just looked and can't find it, but...
http://www2.orange.co.uk/servlet/Sa...096364420640&product=Feature&t=Product#answer
Should get you to the ROM download page on ORANGE UK, where you have a choice of with and without MMS ROM images.
If you can get your 'phone back - that might be a start.
Richard
Edit - just tried the link and it isn't that good. Go to 'Your phones features'.
Sadly I've already tried that. But it won't accept anything. Thanks for the suggestion though.
I at a loss as to what exactly the problem is. I've checked the log file from the HimaUpdateUT file and it keeps trying to erase the original ROM but can't. Which is weird because there doesn't seem to be anything on the device. I wish there was better logging by the program.
I'm starting to consider exploring Bootloader commands to see what I can find.
did you put your device in BOOTLOADER MODE?
PROCEDURE: PRESS ON/OFF POWER BUTTON-SOFTRESET BUTTON-NAV PAD
Yep. In fact I can't get it out of bootloader mode. Have hard reset it several times.
Hi,
do you have SD card???
buzz
Ironically I just ordered one before I fried the device. I guess using it to transfer the ROM image is a possibility. It looks difficult though.
http://forum.xda-developers.com/showthread.php?t=298967
I have tried *everything* to get this working man and I'm no firmware hacker but I can follow directions and have had plenty of experience flashing G3 devices.
Basically when I do the flash (starting from the latest T-Mobile or aku rom) I get trapped on the boot screen with the T-Mobile or aku background and the following:
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
To get back I of course put the phone into "rainbow" mode by pressing camera while I boot up the device and reload either the T-Mobile rom or the akus rom. They go right in and I try again without success doing something a little different.
Things I've tried that were mentioned in other forum posts:
I've tried a number of times from more than one PC running Windows XP.
I've tried redownloading the rom and replacing the one that came with it.
I've tried waiting extra long between installed the EnableRAPI and other cab file.
tried with radio on and off (I assume this meant just disabling the phone in the connection manager?)
Things I've tried on my own account:
Doing it with and without the sim card installed
Trying multiple hard resets
Tried installing EnableRAPI but not the other one (some instructions left that peice out).
So basically i've spent a good 8 total hours on this (of course in the background of other activities) and tried load, fixed an reloading at least 15-20 times without success. The rest of the time has been spent searching the forums because I do not want to be the guy who swears at the creator or complains about it when they are doing something wrong. I see my problem (freezing at the boot screen) a number of places in the forum but never seems to be an educated person explaining what they tried.
So I've come to the conclusion that maybe it doesn't work on all phones or I'm doing something really stupid but apparently common and not easily figured out by myself (thinking too hard about it?)
im assuming you are using Shell Tool made by MuN
here is my advice:
-flash the wizard rom (i was unable to flash any other Rom until i got the wizard love in it)
-make sure you enable both cabs (rapi and the other one)
-turn on figth mode (i know you did this step and i can see that you are following all the instruction but hey we are almost out of options )
-close any antivirus or firewall (probably you did this too)
-do not have any other application running in the background
just so you know i was unabe to flash the xplore core 2.0n, i had to flash it at least 3 times going back to the wizard love (i guess this is something like hit-or -miss thing)
-try the wizard love and then flash the Rom that you want you should be able to flash it.
hope i helped in any way.
THANKS -
I've always flipped back to the TMobile a bit faster than maybe I should have. I guess the question is, if I keep trying it should work? Has anyone just determined that on certain new G4's that this option isn't valid?
I think I'm going to try the following:
Rainbow Mode USB Connection
T-Mobile original rom
Hard Reset
Wizard Love Rom
Hard Reset
Guest Sync
Copy Files
unplug USB
Enable Rapi and Other file (don't know why I can't remember the damn name)
Wait 2 minutes
Soft Reset
ShellTool Load all options except "OK"
Guest Sync
Hard Reset
Pray......
It if doesn't work I'm going to revert back to wizard love and redo the above 3 times.
At that point I'm calling it quits....
happyware said:
I've always flipped back to the TMobile a bit faster than maybe I should have. I guess the question is, if I keep trying it should work? Has anyone just determined that on certain new G4's that this option isn't valid?
I think I'm going to try the following:
Rainbow Mode USB Connection
T-Mobile original rom
Hard Reset
Wizard Love Rom
Hard Reset
Guest Sync
Copy Files
unplug USB
Enable Rapi and Other file (don't know why I can't remember the damn name)
Wait 2 minutes
Soft Reset
ShellTool Load all options except "OK"
Guest Sync
Hard Reset
Pray......
It if doesn't work I'm going to revert back to wizard love and redo the above 3 times.
At that point I'm calling it quits....
Click to expand...
Click to collapse
i would guest sync first and then shell tool load all options (dont know if this would make a difference but it a possiblity) then flash, then hard reset and before all this PRAY LOL....
dont quit i know you probably are frustated but there is gotta be a way to do it.
ill search around to see if i find something.
I thought the problem was for G3 devices
Though the shelltool was made for G4 devices, I use it on my G3. I have ended with the same problem. I couldn't upgrade to PDAVIET 4, Underground, Faria's The Real Thing.
But I do know that you can get PDAVIET 3, mUn aRTM, and Xplore 1.1 to work. There might be more but I don't know. I also use the same methods that all of you have.
Also, the ones that worked only worked when i used EnableRAPI.cab not the certspcs.cab file. Maybe the same will work for you.
I also requested mUn for his code and will try to edit it to be able to add other parts of the ROM (extended and splash).
Sick of ROMs
I been trying so many variants of CrossBOW WM6 for my G4 Wizard but sick of it, they never work out. Only successful was the WM5 Wizard love ROM, wut could be the issue?
Happyware, when you are running the shell tool, how long does it run? On most of the roms I've tried, the shell tool runs at least 8 minutes. I had a problem with an email application on my PC that was checking for email every 5 minutes and was causing the shell tool to end prematurely. After I temporarily killed the email app, the shell tool was able to finish and I had a good flash.
BTW, here's the scenario I always follow when flashing a new rom:
Temporarily kill my email application
Make USB connection to Activesync
Revert to Cingular stock rom or wizard love rom
Copy cert_spcs.cab and enablerapi.cab to the my documents folder on wizard
Install both cabs to main memory, wait 2 minutes, soft reset
Turn on flight mode
Start shell tool
Shell tool runs for approx. 8 minutes
Hard Reset
I don't know what it's doing after the hard reset, but it takes approx. 2-3 minutes to load the first time.
^^Exactly.....thats why I messed up my 1st 4 flashes because I wasnt patient.....after u do a hard reset for some reason that 1st time it takes forever for the rom to load up but it does. Also I agree w/ using wizard love, I couldnt flash anything until I that rom loaded up now I flash 1st time every time.
G4 No Luck either
Same as Happyware here.. No luck flashing my rig. with the Wizard_Love_2.26.10.2_WWE_Novii_CF2 ROM. The shell prog. cant even tell if its CID lucked or Unlucked.
blversion 2.26.10.2
device WIZARD
entrycount 5
flags 17
flags2 12
hdrcrc 0x0ab4e5ff
language WWE
magic HTC
operator
rest2
version 2.26.10.2
9b000000 00a00000 9cabd734 Extension Rom
80040000 03900000 f46dd463 OS
96000000 00280000 6b60114a GSM
92000000 00030000 19375118 Splash Screen
9d000000 00010000 093cf0a5 HTC Logo
Followed all instructions and did the steps twice. No luck Any ideas?
mdhensley5 said:
Happyware, when you are running the shell tool, how long does it run? On most of the roms I've tried, the shell tool runs at least 8 minutes. I had a problem with an email application on my PC that was checking for email every 5 minutes and was causing the shell tool to end prematurely. After I temporarily killed the email app, the shell tool was able to finish and I had a good flash.
BTW, here's the scenario I always follow when flashing a new rom:
Temporarily kill my email application
Make USB connection to Activesync
Revert to Cingular stock rom or wizard love rom
Copy cert_spcs.cab and enablerapi.cab to the my documents folder on wizard
Install both cabs to main memory, wait 2 minutes, soft reset
Turn on flight mode
Start shell tool
Shell tool runs for approx. 8 minutes
Hard Reset
I don't know what it's doing after the hard reset, but it takes approx. 2-3 minutes to load the first time.
Click to expand...
Click to collapse
Flight mode "ON" ????? Thought the instructions said OFF
I think it might relate to specific phone models
I tried many times and got into the exact same situation as Happyware. The phone just freezes at the bootloader stage with the following info:
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
I am pretty sure I followed every steps in the instruction as I spent the last 6 hrs playing with it to no avail. Is there anyone could help? Appreciate it.
I spent some time with it last night and this morning and this is what I've come up with.
I have the T-mobile MDA G4 Wizard. The Faria ROM included in the all-in-one kit simply would not flash to my device. After 2 minutes the flash would stop abruptly as if it had finished, when it simply couldn't have gone that quickly.
I tried several times, following each step exactly as I should have. It simply wouldn't work. When I hard reset the device after flashing, I was stuck on the same screen as the rest of you.
I then went back to the original T-Mobile ROM and then tried flashing with Orwell (wi6ard) and it flashed in 8 minutes and my phone APPEARS to be working normally. I haven't tried making any calls since I don't get reception in my home on any of my 4 phones (Wizard, Herald, and 2 RAZRs).
So I would recommend if you are having the same problem, you might try a different ROM.
bluebari said:
I spent some time with it last night and this morning and this is what I've come up with.
I have the T-mobile MDA G4 Wizard. The Faria ROM included in the all-in-one kit simply would not flash to my device. After 2 minutes the flash would stop abruptly as if it had finished, when it simply couldn't have gone that quickly.
I tried several times, following each step exactly as I should have. It simply wouldn't work. When I hard reset the device after flashing, I was stuck on the same screen as the rest of you.
I then went back to the original T-Mobile ROM and then tried flashing with Orwell (wi6ard) and it flashed in 8 minutes and my phone APPEARS to be working normally. I haven't tried making any calls since I don't get reception in my home on any of my 4 phones (Wizard, Herald, and 2 RAZRs).
So I would recommend if you are having the same problem, you might try a different ROM.
Click to expand...
Click to collapse
I have to agree with you... After several tries with the same ROM (Orwell´s) I decided to use WM6 Reloaded 1.5 and it worked just fine with my G4.
Now... Im having some issues (lol) with a strange behavior thingy. My phone turns itself on and dials random numbers (specially letters U Y T D A). Made a soft reset already, no-go. Hard reset, no-go. Flashed back to 2.26 and to WM6, no go
I wonder if its a virus stored in my 2GB Ultra II miniSD card Ive read a lot about AV SW been a scam in WM OS. I gotta try an antivirus b4 getting into wrong conclusion. I dont think its a HW issue.
If anyone has any ideas on this, please let me know... Or if theres a separate thread on this...
I've tried to search to see if anybody has ever encountered a problem like this, but my search was in vain.
I was trying to upgrade ROM, I successfully load SPL 3.5, before it I was running AP dual 3.0. However after the installation the device rebooted and the started auto customisation. It installed SDAautorun and then SDConfig.txt but before this one completes, the device reset itself. It restarted and do the same process again and again, just restart and restart.
I tried all types of resets and I even tried to reinstall other roms that worked with the device before but nothing is any good. This is because when the device boots it load the SPL 3.5 (Windows mobile 6.1) instead of installing the ROM I'm trying to install.
I get a chance to do so as the device can still connect to the computer and it stops when it prompts to callibrate the screen (tap four corners and center of the screen)
Please help me if there is anything I could do to start using my device again. I appriciate any support in advance. It is very possible that I've messed up something somewhere but please once again do help me, even if the by telling me that my Ameo is a brick that would help me to know what I've got to do.
NB: My device is T Mobile Ameo (Athena, Advantage X7500)
Please Can someone help me, I had a friend help me flash my HD2 because I had a dutch version ROM and I really didn't know how to do it myself and it seem working fine not until I got a call but couldn't answer it and the phone got stuck. Each time I reset it wouldn't help, it will gets stuck at htc and won't load up. I did a hard reset and it loaded up but when I tried calling it got stuck again. This morning I tried to flash a new ROM from CleanEX DsE Core ROM Series (6.5.X ManiMore) every thing seems going on well during synchronization from computer. it showed the last ROM being (Miri_HD2_WM65_21914_Sense25_V18.0). But now the phone wont get to a complete start up. I cant hard reset it any more since it keep continuing from the same htc screen spot before battery removal, not giving me the chance to hard reset from power down mode. when I soft reset it once, it got to the point when it ask for my pin code but it went back to the htc screen mode again before completion. now I cant do any thing just staring at the htc screen.
He first flashed the ROM with HSPL. I saw something like SPL 1.42 SPL 1.42.HSPL on the reset screen. Is this suppose to be the correct HSPL number? and how can I go about this, I need all the help please.
Hold the Volume-Down button and switch on. This should get you to the Bootloader Mode.
Run Task29 to clear any latent info on your phone.
Flash the Radio ROM (the Custom ROM will specify which ones to select).
Flash the Custom ROM.
Please read the ROM's page to make sure that your phone will work with that ROM and Radio and all the instructions.