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
The problem appeared today morning, while listening music using tcmp. the sound stopped suddenly, and standard animated cursor appeared over tcmp screen. i closed tcmp, and the rest of the system seemed fine, i was able to mute the phone and entered my work place. After a while i noticed the screen is off and i can not turn it on using pwr button, although green led kept blinking so the phone was operating. after a soft reset it would not go over splash screen showing IPL, SPL (which are: IPL: 1.06, SPL 1.06, GSM: 01.12.10, OS 1.6.2.4).
I've tried multiple times and still the same, only difference is that sometimes I can see the cursor and sometimes not. I can get to rgb screen and "press send to restore" as well, but that's it. I can't remember whether previously pressing a key illuminated a screen and keys, but now it doesn't. I used to have problems with screen not going black on idle since few days, but that's it. What could have happened? And if the only solution is hard reset, please tell me, could I somehow backup my contacts now? I don't have activesync here so I have to wait till I finish my work to find out..
please help anyone...
rom version : 1.6.2.4 WWE,
date : 11/15/05
radio : 01.12.10
protocol : 4.0.13.23
extrom : 1.6.2.105
That's spooky. My MDA has the same versions of IPL, SPL, GSM and OS, and this morning started misbehaving.
What's this rgb screen you can get to with the "press send to restore" option?
How do I do a hard reset (I have a backup on SD) without being able to get to the Start>Settings>System>Clear storage control panel option?
Rgb screen is a bootloader which i enter by holding cam+voicedial+commmanager butons while softreseting wizard. the other screen i mentioned i enter holding cam and voice buttons, and then pres reset. that screen says 'pres send to restore factory defaults any other key to quit' and it does hard reset if you press green button here...
my problem seems to be over for now, i managed to turn the phone on while i plugged it into a wall charger (believe me, the battery was not a problem - i don't know for how long it's ok now, but at least i made contacts backup now so that i'm ok with a hard reste if i have to...
You both have old roms and could do with upgrading them to aku2 roms. (your device will be more stable) i.e. the first number of the rom will be 2. Please dont ask me to go through how to flash a rom because there are hundreds of posts on the same topic and read the wiki - shortcut top left of the screen. You need to identify whether your device is g3 or g4 but i suspect you both have g3 chips.
Now read & read esp the wizard upgrading forum and wiki and then when you feel confident - flash your device.
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
banannq said:
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
Click to expand...
Click to collapse
Looking at your rom numbers i gather you have a t-mobile vario - is it uk or usa rom or polish - i see you live in poland.
there latest uk rom is here ftp://[email protected]/Wi...Prodigy_2210206_109_21911_TMO_UK_WWE_Ship.exe
us rom ftp://[email protected]/Wizard/Roms/Tmobile/RUU_Prodigy_2170702_217_20710_TMO_US.exe
user name xda password xda
Its prob best you sim unlock and cid unlock before you flash in case you change to a non-tmobile rom inc one of the cooked roms.
see here http://forum.xda-developers.com/showthread.php?t=249474
and read dr puttingham's tutorial http://forum.xda-developers.com/showthread.php?t=285435
and now i have given you more than enough hints
p.s. by the way remember to write down your gprs settings and mms settings to use with your new rom.
thats right, its tmobile vario, uk one. it is sim unlocked, i'm not sure about cid but it should not be a problem. thanks for the hints, it really seems more then enough;] i'll probably have to use theese, as soon i have a spare evening...
you don't have to explain me the importance of gprs settings - forcing my wiz to work in uk's o2, then in polish plusgsm, then loosing settings and doing it again finally got me into a habbit of backing every settings up ;]
and last but not least, guys, yesterday i did my first HR ;] ...
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
Hey guys,
I have two WINgs and I Hard SPLed one already and I Flash it regularly
the other one was at the T-mobile Rom and stable till it starting restarting at every call.
So i treid to Unlock it also like the other one
So I backed up all my contacts and Messeges with PimBackup
and after i Installed the three files
security removal, Aserg and cannonyang
when I try to Hard SPL through RUU with USB so it tells me no connection although its connected in Activsync
I searched the forums and Bypassed the Connection issue by entering the Boot loader through the phone and it got to 2 percent and told me i need a newer RUU although it is the Same as the other Wing for the versions and I have done the other one Fine
when I tried to do it again and still bypassed into the boot loader through the phone it now tells me that There is no Connection to the device. Although the USB sign is available in the bottom.
Now I have Also searched the forums and found Aserg suggesting that we install the Native T-mobile Rom
It connected fine and went into
1% of updating Image and then it gave me a communication Error
Now I noticed two things:
1. it Goes into Bootloader and CHills there
2. It Changed the IPL number from 4.26.0000 to 4.10.0000
but SPL remained 4.26.0002
Does any one have a Solution for this Problem Guys?
Is it bricked now and I just can't see it?
Please help because all my contacts are are on it and i am working with crappy nokia instead of it that has none of them.
Hello,
I work for a mobile phone distributor. As such, we often get from manufacturers "pre-series" handsets that we use to showcase to our customers.
Usually, these handsets are mostly if not fully identical to what will be on the market but the S200 I got hold off yesterday shows a weird OS version : S200_0.019a.00_EN
And it seems the flashing functionnalities have not been implemented on it or even restricted : when trying to flash an official Acer ROM, when pressing "Yes" the following message is displayed on the screen : "KernelIoControl fail ! Your device not support this function. Please check your OS version"
I also tried flashing custom ROMs but they all fail after reboot in FTM mode
I really think the bootloader is special on this unit but can't find any HardSpl or alternative bootloader that I could flash over =(
Thanks for your support
rahan95 said:
Hello,
I work for a mobile phone distributor. As such, we often get from manufacturers "pre-series" handsets that we use to showcase to our customers.
Usually, these handsets are mostly if not fully identical to what will be on the market but the S200 I got hold off yesterday shows a weird OS version : S200_0.019a.00_EN
And it seems the flashing functionnalities have not been implemented on it or even restricted : when trying to flash an official Acer ROM, when pressing "Yes" the following message is displayed on the screen : "KernelIoControl fail ! Your device not support this function. Please check your OS version"
I also tried flashing custom ROMs but they all fail after reboot in FTM mode
I really think the bootloader is special on this unit but can't find any HardSpl or alternative bootloader that I could flash over =(
Thanks for your support
Click to expand...
Click to collapse
Seems like you have a pre-production unit, acer does not apply any kind of flashing encription to there phones, so you dont need any hard-spl,soft-spl etc, you should be able to flash your device, since hdubli first rom cooker for the acer s200 also had a pre-production unit, send me screenshot of the back of your device without the battery, il see what i can desiver off of it.
Hello,
Thanks your interest in my issue !
Here are a few pictures of the back of my device + bootscreen :
[img=http://img141.imageshack.us/img141/3921/20100214092350.th.jpg]
[img=http://img188.imageshack.us/img188/2736/20100214092252.th.jpg]
[img=http://img191.imageshack.us/img191/9638/20100214092232.th.jpg]
[img=http://img188.imageshack.us/img188/8813/20100214092308.th.jpg]
Thank you
rahan95 said:
Hello,
Thanks your interest in my issue !
Here are a few pictures of the back of my device + bootscreen :
[img=http://img141.imageshack.us/img141/3921/20100214092350.th.jpg]
[img=http://img188.imageshack.us/img188/2736/20100214092252.th.jpg]
[img=http://img191.imageshack.us/img191/9638/20100214092232.th.jpg]
[img=http://img188.imageshack.us/img188/8813/20100214092308.th.jpg]
Thank you
Click to expand...
Click to collapse
Hmmm this is intresting indeed....have you tryed flashing any of my roms?? what you have there is test bootloader, if do have a flashing security/or no flashing support is withing the bootloader, try flashing my rom as i have the oldest bootloader, let me know how it goes, im very interested in your device.
edit: turn off your device, and press and hold camera, and wile still pressing camera press the reset button, and tell me what it does
Hello,
Actually, I think my test bootloader had nothing to do with my issue but it was rather the flashing tools disliking my Windows 7 on bootcamp =(
Just borrowed a laptop with XP and could flash your latest ROM
Well, actually my phone won't reboot at all (all I get when pressing the power button is the blinking red light) but I guess I will find the solution in your main topic, won't I ?
Removed battery, put it back in, pressed camera and power button then pressed reset but nothing happens
EDIT : looks like I bricked it =( Can't reboot, no matter what I do all I get is that red blinking light
Reflashed, program says procedure is complete but still the same in the end
rahan95 said:
Hello,
Actually, I think my test bootloader had nothing to do with my issue but it was rather the flashing tools disliking my Windows 7 on bootcamp =(
Just borrowed a laptop with XP and could flash your latest ROM
Well, actually my phone won't reboot at all (all I get when pressing the power button is the blinking red light) but I guess I will find the solution in your main topic, won't I ?
Removed battery, put it back in, pressed camera and power button then pressed reset but nothing happens
EDIT : looks like I bricked it =( Can't reboot, no matter what I do all I get is that red blinking light
Reflashed, program says procedure is complete but still the same in the end
Click to expand...
Click to collapse
Well its not bricked just yet =], if you press camera and reset and the red light start blinking thats good, it means your device is in download mode(bootloader) so you can save it, but my guess is that your device doesn't have the flashing partition in its nand flash, you would need to flash a proper production CSV this will partition your device nand to production standarts, hence giving you the flashing partition, as this said you would need qualcomm's qpst something qualcomm engineers only have, so for now your device can only boot into bootloader.
Doesn't sound too good =(
I guess I'll never be able to add the flashing partition myself, will I ?
Edit : finding the QPST seems easy on RS, how about the proper production CSV ?
Thanks a lot for your time
rahan95 said:
Doesn't sound too good =(
I guess I'll never be able to add the flashing partition myself, will I ?
Edit : finding the QPST seems easy on RS, how about the proper production CSV ?
Thanks a lot for your time
Click to expand...
Click to collapse
This one should work, be aware the QPST is not flashing utility its an engineering tool, meaning you require certain knowledge to use it, if you fail to do so you will render your device completely and utterly useless, good luck.
Before trying QPST, just tried and flashed UFE Nuts rom : it works like a charm !!!
rahan95 said:
Before trying QPST, just tried and flashed UFE Nuts rom : it works like a charm !!!
Click to expand...
Click to collapse
Strange hes using my rom as based so mine should have work as well.
Strange indeed ! And then i could flash your rom on.
Only thing is that it aparently lost the radio !
Oh... It's a pity you flashed it so quick We could have used the pre-production rom for various experiments (as I remember, none of the reviewers complained about 2d landscape issues or low headset volume ).
Sorry, no one told me it could be of any interest to you guys =(
By the way, would you know what I should do to flash Radio the radio only ?
If you use the old flasher (i.e. there're plenty of files in rom package - flash.bin/extrom.bin/amss/...), you can try to delete flash,extrom,dsp1 and to leave only amss file.
Will try that when I'm back home, thanks a lot !
I think I've flashed all the ROMs I could find on the forum but without much success : everything works perfectly except the phone =(
All I get is "Phone off" on the desktop and all that is related to phone doesn't work (placing calls, SIM toolkit, connections setting, etc...) just as if there were no SIM card in the handset. I get the "Phone is off, would you like to turn it on ?" message but it never gets to the PIN input screen.
I tried with several SIM cards that work perfectly well in my other phones with the same result
Any idea would be greatly appreciated =)
Thanks
rahan95 said:
I think I've flashed all the ROMs I could find on the forum but without much success : everything works perfectly except the phone =(
All I get is "Phone off" on the desktop and all that is related to phone doesn't work (placing calls, SIM toolkit, connections setting, etc...) just as if there were no SIM card in the handset. I get the "Phone is off, would you like to turn it on ?" message but it never gets to the PIN input screen.
I tried with several SIM cards that work perfectly well in my other phones with the same result
Any idea would be greatly appreciated =)
Thanks
Click to expand...
Click to collapse
You need to try different AMSS.MBN these are the Radio part for the acer s200, try flashing the one found in my flashing tools, if dosnt work download difrent Acer OEM roms, and try all the amss.mbn, one of these should work lol, good luck.
rafyvitto
Tried to flash all the AMSS.MBN I found, including the one in your flashing tools but I'm still stuck =(
I'm about to throw the phone through the window =)
rahan95 said:
Tried to flash all the AMSS.MBN I found, including the one in your flashing tools but I'm still stuck =(
I'm about to throw the phone through the window =)
Click to expand...
Click to collapse
Hmm it seems that your pre-production device flashing partition is not as big as the normal acer s200 devices, my only guess is that your flashing partition is full thus not been able to flash the amss.mbn, my question is in the flashing process do you see amss.mbn been flashed?? or is it skipped?
Hello
No, the whole procedure goes fine, no error message of any kind and apparently nothing is skipped