Related
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
hello all,
i'm a newscommer on this forum,i've trust in upgrade my phone with aku3
i correctly followed the topic , install step 1 (forG3) and step 2
my device worked fine after the first install (qteck 2.15 fr ->2.2 from step1)
i've synchronize my phone, and run the second part, installing without problems, reboot > freeze on the boot screen htc
no way to synchronize again. my phone is reconized by mtty (1.51 and 1.50) but i don't know how to use it
ipl 2.09
spl 2.20.0000
gsm 02.47.21
os 3.0.0.0
i've tried all the night to find a solution on all forum i knew, i drive me to this one, i think it could help me best ( you'r pro dudes )
but i'm allways stick. i've call htc division hotline (i'm from france) , they said i have to send back my phone ( but he's now out of waranty, cause it's not a legal rom i've installed, so i have to paid, and i've allready too much invest on my device)
plz said me there is still a hope!
did try upload another rom from bootloader ?
did try upload another rom from bootloader ?
but first try a hard-reset
i don't know how to load a rom from bootloader (i allready have made soft and hard reset
no one could help me ?
1. dowenload this latest Qtek official rom from here: ftp://xda:[email protected]_220734_2207114_024721_QtekWWE_Ship.exe
2. enter your S200 into bootloader mode by pressing power +camera + reset, let go of the reset, but keep holding power + camera until the three colur screen will show up (that is bootloader mode).
3. connect the S200 to your pc (make sure your battery is fully charged)
4. run the Qtek official rom.
5. good luck!
i've tried those kind of upgrade several time, but without possibility of establishing an active sync connexion, it's impossible to launch the rom install...
does samebody knew if it's possible to make a rom dump with an emulator and copy it on a sd card for autoinstall backup in bootloader mode ?
while in bootloader you don't need to establish any activesync connection. just plug the usb cable, then if appears "usb" on phone you are good to go.
install the original DOPOD rom from the ftp.
this rom don't work, it give me the message
error 294 invalid vendor id
it's now working ! great !
i've juste install again the step one of jester's aku3.3 (so, i'm on a 2.20 os, i think i'll keep it for a while )
thank you verry much
pti_nourson said:
it's now working ! great !
i've juste install again the step one of jester's aku3.3 (so, i'm on a 2.20 os, i think i'll keep it for a while )
thank you verry much
Click to expand...
Click to collapse
So you can now change your signature again, right
please help! I have made a wrong ROM Update for my Artemis. The result is that it doeasn`t starts anymore. I see only the start screen no more. If i make a SW or HW reset tahn i see a 3 colored screen and USB. But i don`t get a connection via usb to my compute`! How can i wake up my Artemis ???
tell use more what did you do and how did you do it?
what artemis is it?
what rom was it
Flash went sour..
You need the original ROM which was on your device when you bought it. What version (HTC, MDA, etc..) and what language was the original ROM?
please i need help too
I guess I made the same or a similar mistake that dr.moppi did. My machine is a Dopod P800 from mainland china with the chinese operating system. I flahsed it with PDAMobiz_Dopod_P800W_AKU301_v1.1.2_PowerMap. Don't really remember what the original ROM was but now when i turn it on it freezes when it lights up. On the screen, it says
IPL 1.27.0001
SPL 1.27.0000
GSM 02.67.90
OS 1.28.0.0
DOPOD
I don't get a connection through usb to the computer either. I am not sure if I did the hard reset correctly. Didn't understand the instruction on that "press the soft key left and right and soft reset at the same time." Anyway, you guys are all experts, can you help me please?
it should be the same as my problem
if i remeber than i used the same ROM Update :-(
I hope anyone could give us a solution, please.
@dr. moppi we can only help you if we know what version you had before.
@empathyvirus you have to look for the original ROM which, in your case, should be the Chinese Dopod ROM. Install that one and your good to go.
Without the original ROM the only thing left to do is: sending your device to your provider or contact and sent it to the guys of imei-check. Either way, you'll probably have to pay to get it fixed.
how to install original rom
Thanks for your quick reply Pyth. In the case I get the original ROM from somewhere, how do I install it if I can't get a connection between the phone and my computer? Can you advice?
Put your device in bootloader by pressing the record button and reset at the same time. If you have your USB-cable connected between your PC and your phone it will indicate a connection by 'USB' in the left corner of your device. Now you should be able to run the ROM executable and update your device.
thanks anyway
i tried but it didn't seem to work. anyway, i have troubled you enough and maybe it's best i just go to the repair centre of dopod and pay for a fix. i really appreciate your help though Pyth.
Where can i find the t-mobile rom its the MDA Compact III that wont start for me
Hi Profs,
there are some problems with a Artemis Update SPL (USPL) v.01. I've found this problem is several topic but there was no solution for it.
#1:
http://forum.xda-developers.com/showpost.php?p=1739577&postcount=413
#2:
http://forum.xda-developers.com/show...44#post1745844
#3
http://forum.xda-developers.com/showpost.php?p=1713596&postcount=1
The problem:
use USPL to get rid of the CID....count goes up to 100% screen shows black with green text, then pops to white. I need to do a soft reset to get it running again.
Then i use ROM Update Utility to update my p3300....and it still keeps hanging on 3%....damn. i get mad...!! Have read almost all here online...no virusscanner, no firewall....I use win XP.
i even tried without memory card and phone card....and nothing seems to work.......
ipl 1.14.0001
spl 1.14.0000
gsm 02.07.90
os 1.14.0.0
Who has any clue...?
With other words:
I've just got back my P3300 from repair, they changed the main board. With the previous main board I was able to upgrade the device and I was using the B&B versions.
But with this new board I'm not able to upgade the SPL. When I try to upgade the device after and start the start_uspl .exe the 10...20... ....100 my device become an interresting "blue screen" status and only the reset help to get out from this status. If I start the RomUpdateUtility.exe after the upgrade I got the error message #270
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
ExtROM version: 3.12.405.102
This is not the solution for the problem. I've tried it:
Plug in USB cable. Hold voice recorder button and press reset button. Bootloader will appear (Three color stripes). Then you may flash up ROM. (This works only for RUU installation types, not for PDAmobiz modified installator) Original english HTC P3300 ROM you may download form here: http://wiki.xda-developers.com/index...temis_Upgrades ....
Please help us to solve this problem....
Probably the same problem
This should be the same:
Hello POF,
I was directed to this link by Rudegar because I want to change the french ROM to English ROM.
The relevant data of my PDA is:
The version of the ROM: 1.14.406.1 FRE
Date of ROM: 9/27/06
Radio version: 02.67.90
Protocol version: 4.1.13.28
ROM extension version: 1.14.406.101
I tried exactly the way you described in the USPL_manual and everything went well till I got to a stage where I was asked to click the update button which I did. After then there was a window which showed "updating from current version to version 9.99". I was confused at this point but clicked "continue" and after this stage I got an error message and there was no longer a connection bw my PDA and my computer.
Thanks,
Jonat
Reply With Quote
http://forum.xda-developers.com/showpost.php?p=1784337&postcount=430
Also the same
Problem "lost connection PDA-PC"
Hi,
first I would like to thank you for goooood job to many people here !
Back to my problem. I have HTC Artemis (T-Mobile MDA Compact III), OS WM6 T-Mobile Czech version.
I ran start_uspl.exe on my computer. The part in DOS based screen seems to finish everytime OK, but finally the connection with PC is lost. Therefore when the PDA Phone ROM Update Utility starts cheking version the error "lost connection with PC" appears . PDA stay in "black screen" mode and only hard reset start it again as usual.
Does anybody have the same problem? Any idea, how to solve it ?
Thanks
http://forum.xda-developers.com/showpost.php?p=1773030&postcount=426
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....
lenocs said:
then pops to white. I need to do a soft reset to get it running again.
Click to expand...
Click to collapse
What im saying is when it pops to white, dont soft reset it, just start the upgrade.
Anthony2oo5 said:
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Click to expand...
Click to collapse
that what i also do When the screen goes white, don't restart. Just start your RUU
lenocs said:
Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....
Click to expand...
Click to collapse
Same situation as above. Depending on the Artemis, the screen might go white or black. Just don't freak out and keep on flashing the USPL. It WILL work and then reboot. Then you can flash the actual ROM you want.
Hello from an absolut newbie trying his first upgrade,
And I have just experienced the same problem than lenocs.
I have run start_uspl.exe, but when the screen is suposed to become white or dark, it becomes dark and the artemis is in fact totally off and connection is lost.
Anyway I supossed that it was because the scrren got black and I tried to run the update utility, but I´ve got an error (the terminal is disconnected or similar) and nothing happens.
I have had to soft reset the terminal and fortunatelly it seems that I still have my previous ROM and it seems that it works. But, do you know if there could be some "side effect" because the first step of start_uspl script?
Anyway I would like to move to WM6, so, any suggestion would be really appreciated.
Thank's a lot
When you restart, what is the USPL number?
Ooopppssss!
I didn't pay attention.
As I've said, I'm a newbie, so I was just woried because I thought I had "bricked" my new atemis.
How can I know now the USPL number?
Anyway I tried the star_uspl again (I'm a crazy newbie) and it failed. The artemis went off almost inmediately.
Thank you very much for your help
SpiggyTopes said:
When you restart, what is the USPL number?
Click to expand...
Click to collapse
solved ... at least for me
I think the problem is in SPL version 3.13 (or maybe anyone newer than 1.11).
Try different Artemis USPL - for me worked version from this page:
http://wiki.xda-developers.com/index.php?pagename=Artemis_DumpedRoms
It's very confusional, because file sizes and also dates are the same as in unfunctional version, but this one worked.
Hope it'll help you as it helped to me.
Maybe this can help you
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.
Rocheau said:
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.
Click to expand...
Click to collapse
do u have ur card in the phone while updating
you are suppose to remove the card
Problem solved (for me)
Hi,
i had the same problem error 270, 3% and lost connection with Activesync.
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
any way to upgrade was wrong ->> error 270
My good way was:
1. Downgrade to WM5 - original shipped ROM 1.12.405.1(link found on Wiki pages)
2. Under WM5 run USPL to unlock CID (now without any errors)
3. Final STEP - Upgrade to new ROM Artemis Touch 3.01 (without any errors by upgrade)
))
Now my Artemis seems to be OK.
I ran USPL with storage card inside the device...
no problem
switch SD card back to 2GB or smaller before USPL
Hi,
for me USPL did not work with my SDHC 8GB card but then I switched back to my previous 2GB SD card and then it works.
Perhaps the SDHC driver blocks USPL in some way.
Cheers,
Markus
i have been trying for 3 months
once i have upgraded my artemis to wm 6.0 everything seemed to be OK for two days... then the screen started to go black when i restart... şi downgraded to 5.0 but nothing changed... when i remove battery for a while, my arte works... when i try to do anything with it, the screen slowly goes black as if it is broken... please DO HELP ME! i am going to go mad... i have a new iphone, ihave i kaiser as well... but i miss my artemis very much...
Hello:
I have the same problem and realized hundereds have too. I have been checking in all forums and no asolution to it
The issue that happens to me is that I used USPL for upgrading to WM6 and worked, but now for the Touchflo it does not. Tried with all USB ports, tried with different computers and no good news.
The USPL msdos screen indicates that there is no connection at all in all percentage levels, then it bocomes dark and the 260 error whne installing the rom.
please help us soon !!!
we are in trouble!!
Same Problem : Screen shut down
Anybody can help us on this point ?
The only way to solve it is to remove the batterie during 30 min., then put it back and pray...
Then, for no reason, the screen shut down, a few minutes or days after
I've upgrade from WM5 to WM6 with the original Rom of HTC, it seems a little more stable but it shut down every 2 days when i'm lucky
I have a Cingular 8525 running WM5 that is stuck in bootloader screen. I have tried to soft and hard reset ... just boots back to the same screen, I can't turn it off once in the screen and when i sync via usb to the pc i get the message that the "usb device that is connected is malfunctioning" I have not done any upgrading at all and the phone worked perfectly right up till the time i powered it down and restarted into the bootloader screen.
Please can someone out there help me with this issue?
Zulu137 said:
I have a Cingular 8525 running WM5 that is stuck in bootloader screen. I have tried to soft and hard reset ... just boots back to the same screen, I can't turn it off once in the screen and when i sync via usb to the pc i get the message that the "usb device that is connected is malfunctioning" I have not done any upgrading at all and the phone worked perfectly right up till the time i powered it down and restarted into the bootloader screen.
Please can someone out there help me with this issue?
Click to expand...
Click to collapse
same problems, run perfect before with schaps wm6 rom then flash to faria wm6.1... not feel good with faria. try to flash with other rom then the problem start ..
how to recover ....... please help
Asfarizal said:
same problems, run perfect before with schaps wm6 rom then flash to faria wm6.1... not feel good with faria. try to flash with other rom then the problem start ..
how to recover ....... please help
Click to expand...
Click to collapse
Manage to solve the problem ...thanks WIKI !!
Go to Bootloader mode: Hold side OK and POWER buttons together and reset with stylus
Then Flash to any ROM you want !!
Thanks .... But
Thanks for the reply ... but i have no idea how to do what you tell me, I am new to all this phone "stuff" as a matter of fact this is the first time that i am ever using one of these forums. I have read till i am cross eyed but dont actually understand what you are talking about ... now don't let that scare you away as i am willing to learn and i am not braindead ... you all had to start sometime in this, not so. I get that i need to try and reflash my rom...
so is there some type of rom update software that i need? ... what is a hard SPL?? ... and who is Schaps?? .. sorry guys to do this to you but i would like to get into this game and i need some ( well maybe a lot ) of pointers.
Thanks for your time.
1. Search for "mr vanxs guide" so you have an idea on what you're doing.
2. OK, as Asfarizal said "Go to Bootloader mode: Hold side OK and POWER buttons together and reset with stylus". If you cant work out what the buttons are, go to the manual. it will tell you.
3. type in "hard SPL" in search on the forum & download the .zip or .rar file. this should have 2 files inside when opened,
a). RUUWrapper.exe and
b). RUU_signed.nbh
sync Hermes and double click .exe file. follow prompts.
4. find a rom that you want (would suggest TNT SE as a fairly good rom for noobs... good and stable, no problems...) Again download, then (and this is personel preference) format an sd card fat 32 and copy RUU_signed.nbh into root directory. Rename it Hermimg.nbh. Put into Phone and put into bootloader(make sure the battery is more than 50%) follow prompts. This should get you out of trouble. You can also sync your Phone and double click on the RUUWrapper.exe HOWEVER, if you should reset your computer, pull out the usb cable or have anything else happen to the computer that interrupts the flashm, you could end up with a worse brick than you have now. try to read up on flashing (search for "mr vanxs guide") and this should help you a lot if you have other questions. Good luck and happy flashing......
Thank You
I will follow the instructions you gave and try to get it going this weekend.
Thank you so much for your time
Zulu137 said:
Thanks for the reply ... but i have no idea how to do what you tell me, I am new to all this phone "stuff" as a matter of fact this is the first time that i am ever using one of these forums. I have read till i am cross eyed but dont actually understand what you are talking about ... now don't let that scare you away as i am willing to learn and i am not braindead ... you all had to start sometime in this, not so. I get that i need to try and reflash my rom...
so is there some type of rom update software that i need? ... what is a hard SPL?? ... and who is Schaps?? .. sorry guys to do this to you but i would like to get into this game and i need some ( well maybe a lot ) of pointers.
Thanks for your time.
Click to expand...
Click to collapse
Looks like you've got a lot of reading to do, and a problem to sort out. Firstly a couple of answers...
Schaps is a Rom Cooking guru (makes custom versions of WM5, WM6 etc). When you get your phone sorted out I'd recommend trying one of his roms.
Hard SPL. The SPL is part of the bootloader which effectively dictates how a rom is flashed and what roms can be flashed. HardSPL is a custom version of this which allows you to flash any rom from any carrier. It also protects against a bad flash in many cases. It is recommended before you try flashing any new roms or radio roms. Use Hard-SPL-V7 at the bottom of the first post here.
The Rom upgrading software is contained in any of the cooked or carrier supplied roms. It is normally a .zip file which cotains 2 files: xxxxxRUU.exe and RUU_signed.nbh. You run the .exe file from your PC when connected to your phone via USB. More details of how to do this are in MrVanx's guides. Also other resources here.
Now to try to sort your phone out...
What is displayed on your screen when in bootloader mode? It should be something like this:
HERM200
IPL-1.04
HERM200
SPL-2.10.Olipro (This is HardSPL V7)
If you don't have an Olipro SPL then you need to get HardSPL onto your phone. If you haven't done any upgrading and have had the phone from new then I guess you don't have hardSPL.
Now you need to fix your USB Malfunctioning problem. I can't help too much here except to suggest trying a different cable, different USB port or different PC. Also, if you are running Vista try an XP maxhine. When you connect to the PC does your phone show Serial or USB on the screen? If you can't get a USB connection, all is not lost - you can re-flash your rom using an SD card, method here.
There is a thread about un-bricking phones which may help.
There are various diagnostic tools (which can also screw your phone if used incorrectly). The favourite of these is MTTY but you need a USB connection to use this.
If your phone is in warranty I'd recommend getting your supplier to sort it out, but if not I'd try to re-flash an ORIGINAL supplier rom (Cingular I guess). You can get links to the official supplier roms here.
I think (might be wrong) that sometimes when stuck in bootloader you need to flash an official rom, not a cooked one to recover your phone - then you can run HardSPL and then flash cooked roms again.
Cingular 8525 stuck in bootloader
Thanks for the reply ... lots of great input.
Now to answer some of your questions.
1) When I power up the phone (only pushing the power button ) it goes straight into the bootloader screen without pushing any other buttons, and it displays
HERM100
IPL-1.01
HERM100
SPL-1.06
Then at the bottom in the white bar it says "Serial"
The only way that i have found to power it down again is to remove the battery, there is no response from any single buttons after it is in bootloader
the soft reset and hard reset work but it just goes right back to the bootloader screen after.
2) The USB malfunction. This only started after the phone "crashed" and before that it worked great ... well i only used it to sync up to my work pc for the contacts and to get pictures onto my hard drive.
all the PC's that i use are running XP. I have tried my home PC and my Laptop
and the work PC and all of them have their own cables and they all say the same thing ... "the USB device is malfunctioning"
I am sure that when i get the phone going again the USB will start to function again.
3) Phone warranty ... I bought the phone off e-bay from a store in new york about 10 months ago as a "new unlocked cingular 8525" it was new and unlocked, but i have no idea how they unlocked it. I would assume that there would be no warranty now and in any case i live in Canada and would have to ship it down to the states to an AT&T repair center and that sounds like a nightmare to me with the customs and so on.
I will give you a little more background on the problem. the phone worked like a charm without any problems at all for the 10 months that i had it, then the morning of the crash the phones alarm did not go off in the morning and i was almost late for work ... i did not pay it any further attention untill at 3:26pm
that afternoon the alarm went off ??????? (it was set for 6:05am) so i checked the main clock time, it was right. I then checked the alarm time, it was right ??? So i figured that something must have just got confused, so i powered down the phone with the power button to just restart it and while it was powered down i removed the battery to take the oportunity to to clean all those fuzzies and dust that collect in the battery compartment out and put it all together and powered it up again (just by pushing the power button) and this wierd red, green, blue and white screen appeared and that is all that i have seen since ???
I hope that answers your questions and i will start going through the links that you sent and get to reading ... will there be a pop quiz ... lol
Thanks again for your time and i very much appreciate all the time that all of you have spent on me and my phone ..... I know that you all just feel bad for me because i now have to use a Motorolla V551 ... lol
Great Work
ultramag69 said:
1. Search for "mr vanxs guide" so you have an idea on what you're doing.
2. OK, as Asfarizal said "Go to Bootloader mode: Hold side OK and POWER buttons together and reset with stylus". If you cant work out what the buttons are, go to the manual. it will tell you.
3. type in "hard SPL" in search on the forum & download the .zip or .rar file. this should have 2 files inside when opened,
a). RUUWrapper.exe and
b). RUU_signed.nbh
sync Hermes and double click .exe file. follow prompts.
4. find a rom that you want (would suggest TNT SE as a fairly good rom for noobs... good and stable, no problems...) Again download, then (and this is personel preference) format an sd card fat 32 and copy RUU_signed.nbh into root directory. Rename it Hermimg.nbh. Put into Phone and put into bootloader(make sure the battery is more than 50%) follow prompts. This should get you out of trouble. You can also sync your Phone and double click on the RUUWrapper.exe HOWEVER, if you should reset your computer, pull out the usb cable or have anything else happen to the computer that interrupts the flashm, you could end up with a worse brick than you have now. try to read up on flashing (search for "mr vanxs guide") and this should help you a lot if you have other questions. Good luck and happy flashing......
Click to expand...
Click to collapse
Thanks a lot man & great work i unbricked my Herm100 with method u mention above thanks a lot & great job keep it up
I also have this problem.
I d/l Hard-SPL-V7
and when i run RUUWrapper.exe
I get an error saying the application failed to initialize properly (0xc0000135)
What's going on?
How do i fix this?
this happened when i was trying to unlock the phone.
Thanks
need help
when i switch on my orange herm100 it shows On the bootloader screen is displayed:
HERM100
I PL-1.01
HERM100
SPL-1.40.01ipro
history : i buy unlocked orange phone
fewdays back i found no imei ,
yesterday i try to flash by micro sd but in gsm stage its gets hang no progress after extrom stage
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM - (NO ACTION)
OS -
i tryed several time no action, i cant connect by mini usb.
PLEASE help me
tell me which it the right rom to chose? step by step procedure..
how to rectify imei?
thanks and regards
kirtibas
kirtibas, sorry it took so long to reply, 1st thing I'd do is upgrade to SPL 2.10 olipro. This is safer to use than others. then I'd suggest reflashing a stock rom to see if that works. After stock rom works then use a cooked rom as your heart desires... Cheers...