ROM UPGRADE PROCESS STUCK on 95% - JAMin, XDA Neo, S200 Software Upgrading

The story: Received an new O2 XDA NEO from Germany. Being portuguese I don't know nothing of german idiom. I dowloded the JAMIN Eng. rom from the FTP and tryed to unstall this rom. With the ROMUpadte utility that comes with the ROM I get an error. With the ROM Update Utility_NOID the process stars and go normally until 95%. Here, after some minutes give me an error saying I can't upagrade with the NBF file.
I was a little passed out thinking that instead a phone I had a brick. Pul out the batery for moments. After I turned on the phone and it shows the tri color scren of bootloader. Ok conect the usb cable again and start the upgrade to the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID. and voila... the process completed without problems.
The weird thing is why my phone doesn't accept the JAMIN rom?
Anyone has an expplanation for that? Thank you

can you tell me wehere i can download a jamin rom ? then i can test it with my o2 xda neo

I upgraded my Neo to jamin rom without a problem. I was using the RomUpdateUtility by machinagod, which you can find in this forum. But now I have switched to RUU_2151327..._DOP_ASIA_WWE too. To me, the new version DOP_ASIA_WWE rom works much better than that jamin. More fast, more effective. The JAMIN always runs out memories and makes the CE-Star chinese input inactive, especially when WiFi used. The DOP_ASIA rom rarely meets such problem.

Upgrade rom
You can only upgrade rom but can not downgrade. So now you are at 2.15
but Jamin is at 2.13.

Hi,
upgraded qtek s200 with RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship.exe, using ROMUpdateUtility-NoVendorID.zip, which does not check Vendor ID.
No major issues so far. During boot dispays Dopod instead of QTEK .
Besides, few differences I found in voice diler and new program called AutoConfig. Appears, to configure automatic settings for your GSM carrier, but only for ASIAN operators, which is useless to me. No worries, interface still English.
It was mentioned few times in this forum, that you may experience some "delays" during flashing your device - don't panic, don't touch it, just wait for some time, it will finish on its own.
Good luck with upgrades.
de yl1wc

Related

GetDeviceData output from a S100 wanted

Dear fellows,
I am still at a dead point (my S100 is screwed and the OS is gone!)
I have seen several methods listed here to reflash the OS but most of them require the GetDeviceData output file to modify the original ROMs. Unfortunately I can't run anything on my PDA... It would be a great help if a kind S100 owner would run the GetDeviceData on his handset and post the output file for me. Do not worry, it doesn't hold any sensitive data. Just device model details. Any S100 device, any language... would suffice.
Thanks in advance for your help.
Silver.
...at least the Operator for QTEK...
C'mon guys... help me.
Here ya go...
Operator ID: DANGA001
Qtek S100 bought at Dangaard Norway.
Thanks...
...but it doesn't seem to work. Maybe an Italian PDA would be required.
I am afraid I have to send the PDA back to the service...
Maybe you can try the following:
- Set your Qtek in Bootloader mode
- Connect it to your pc
- Start the update program of the Qtek ROM 1.06
- The installer will not find any version of your current ROM because it is in bootloader mode, but it will allow to update it
- flashing...
- done
Hopefully it'll work for you.
And I will test it further, but this looks like the way to update the ROM without editing the ROM files...
The other alternative that worked for me:
I have a Dopod 818 ROM which I screwed up. I can't therefore read its country code with GetDeviceData.
I used the following to flash the i-mate ROM:
http://www.clubimate.com/Support/ma_cdlsku1_wwe_10300_143_10100_ship.exe
Then I upgraded with qtek 1.06 successfully.

fragged my mda_c with official update

Hi all,
yesterday, i thought it's a nice day to do the official german t-mobile 1.12 upgrade on my official german t-mobile mdac. It wasn't.
After the upgrade (no errors) the bootscreen shows:
no gsm, and only one Version number: 1.12.01 Ger
on the bottom line.
After it bootet, i get no gsm and no bluetooth working. When i connect by usb, active sync hangs for about 3-5 minutes. If i try to repeat the upgrade, i get something like wrong device, and it shows empty fields on the version screen. I tried to do the update by extracting the official update rar and start the update by MaUpgradeUT_noID.exe, but it says something like wrong device.
I tried this to the same with the 1.13 upgrade from the xda ftp, same thing. I tried a rombackup from sd-card that i found somewhere on the net, but the bootloader says wrong section=1 not allowed.
Is there anybody wo could help me to resurrect my poor little mdac?
Thanks alot,
J
Hi J.
Don't know how to solve all your problems with upgrading, but did you copy the first bytes of your own romdump to the downloaded rom? Otherwise your device won't accept it, you can find a lott about this in other threads. try searching for BigStorage and you will everything about rom upgrades.
Good luck, M
Upgrade your device with the imate rom 1.12 wwe using MaUpgradeUt_noID.exe ,it should work ,then try to upgrade to the german rom upgrade.
Good luck
ongoing revival
Ok, i tried that big storage thing, i replaced the id in the new image from my backup (broken) rom, and when trying to upgrade from sd-card, i get Section = 1 not allowed update.
I'm trying to upgrade the radio stack from the bootloader screen with MaUpgradeUT.exe, but it seems that the usb port doesn't work: for 10 minutes, the update screen stands at 0%, then an error appears:
Radio Rom Update Error.. i should reset, reconnect and retry.
Any more ideas? Is there a possiblity to do the normal "online" update (not via bootlaoder/backup-image) just from sdcard?
Please Help
J,
Last night I did a BigStorage in a very easy way. I followed the description in the thread about upgrading to radio 1.13. You'll have to unzip the shipped rom, decode nk.nbf it with dnbf. Then you replace the usual bit pattern and encode nk.nb1 again. After that you can use maupgrade with or without the noid function like a regular apgrade.
Hope it helps you, M

PLS HELP! Vodafone V1240 Dead!

Hello! i have a vodafone v1240 (qtek 8310) and i tried to update its rom and got stuck at 73% for hours. finally i unplugged it from pc and when i reset the phone it shows me just a white screen and i can't shut it down i must take the battery off. it doesnt want to connect with the pc again, in activesync wont recognise it. can u help me pls to get my phone back to life?
i suppose you have new a paper weight now .
cant guarantee but some people have recoverd the phone from this state.
what rom did u try to flash?
Ill suggest you try getting in to the bootloader (Plug the usb ,press and hold volume down and the press the camera button). If you see a 3 color band. Then way to go. Just flash the latest vodaphone V1240 rom
it doesnt want to work that way, it's not responding to this key combination. i tried to update with the latest update rom from vodafone vf-uk_v1240_aku2_v254832_ship.exe and got stuck. someone told me because it was slipped off and can be some hardware failure(i just got it repaired, the display was broken and had to be replaced) but it was working just fine after that, the win mobile 2003 second edition was good just that I want to update to the latest version from vodafone.do you have some other method of ressurection ??
I just read somewhere that from this state cannot be recovered (white screen of death) and my bootloader is crashed.
do you have knowledge if I can repair it by replacing the rom memory phone with a new one ?? (of course, at an authorised qtek service)
is your phone still under warranty??
may i know where do you stay/which country???
allow me sometime to check what part of the rom is flashed first.
That's because as you said your flash was stuck @ 73%.
if the bootloader is flashed first then it might be recoverable(can't guarantee though!), if its flashed at the end then you might want to get it repaired from a authorised repair center , trust me it will be costly as buying a new phone!
my phone has no warranty. i'm from romania but the phone was bought in italy. so can u tell me if the bootloader is still good? and how can i get in?
it was working just fine after that, the win mobile 2003 second edition was good just that I want to update to the latest version from vodafone.do you have some other method of ressurection ??
Click to expand...
Click to collapse
Are you sure its a Tornado, i did not know that any Tornado shipped with WM2003SE.
yeah maybe he had loaded the inappropriate rom.
it's a vodafone v1240 (qtek 8310) ...the update was an official rom from vodafone exactly for this model. yes it had win mobile smartphone 2003 se
I sent the phone to a very good service and it cannot be re-softed. I think the rom memory on the phone's board must be replaced.
so... I'm looking for somebody who has a damaged QTEK 8310 (VODAFONE V1240) or a rom memory chip for this model
I will pay for it because I want to repair my phone!
Hi guy, it's nothing to do with the rom memory. The phone you got is not a real Tornado, but you tried to update it by loading a Tornado ROM, it's a dangerous action, it may damage the IPL and SPL!
yeah i insist. maybe he's just confused or what. his device is not a Tornado. it runs on wm2003se os.
ok let's get all clear here. it's a vodafone v1240 (search on google to find out more) and it is similar to qtek 8310. I tried to update with an official rom for V1240 its not an innapropiate rom or a modified one. Still looking for someone who has a broken VODAFONE V1240
It's very clear, you loaded an inappropriate rom, because your phone is not a real Vodafone v1240. A real Vodafone v1240 shipped with Windows Mobile 5.0, TI OMAP 850 CPU and Wi-Fi block, but your phone shipped with Windows Mobile 2003 SE, TI OMAP 750 CPU and without Wi-Fi. I give you some more information about Vodafone v1240, it's made by HTC, which is a mobile device ODM. The same device sold in defferent areas got defferent names.
Vodafone v1240 = Qtek 8310 = imate sp5 = Dopod 577W
As I know, Dopod 577W got a brother Dopod 577, which have the same specifications as your phone got. Dopod 577 or your phone can not load official rom for Dopod 577W or Vodafone v1240, because they got defferent board and CPU.
i think it falls in cases like in t-mobile sda(wm5 usa version). they also have t-mobile sda II(wm5 europe version) and t-mobile sda II(wm2003se usa version). they almost have the same appearance and form factor but different os. so if your unsure of what kind of device you have, check its system info carefully. but in your case i think you got the inappropriate ROM. unless you show us bits of system info of your device.
cheers
u know u got me all confused. so bluehanson u're trying to tell me that i have a Dopod 577 with Vodafone label on it, who looks just like V1240?
the model is this:
http://pdadb.net/index.php?m=specs&id=471
but it had on it Win Mobile 2003 SE cause I checked before the crash occured.
the rom i was trying to update is vf-uk_v1240_aku2_v254832_ship.exe
based on your link, it is indeed a wm5 tornado smartphone. the rom you loaded is not intended for your device.
Maybe when the screen was "repaired" (as described in an earlier post), the shop just put in the guts for a 2003se edition phone? Perhaps worth checking with them?
ericjm said:
based on your link, it is indeed a wm5 tornado smartphone. the rom you loaded is not intended for your device.
Click to expand...
Click to collapse
ericjm so what's the real V1240 model designed for this rom? cause now i'm totally confused
i dont know what led you to believe it had 2003se,but all tornados are loaded with wm5... and i believe that its not the issue... i think sometime while flashing your rom your phone lost connection with your pc hence your phones curent state... cause you said it stopped at 72% or sumthing... when flashing even with the wrong rom it will go to 100% then not restart... stopping before it got all the way to 100% accidentally or intentionally could lead to a bricked phone... just my 2 cents...

My Prophet is dead!!! What can i do? PLZ Help!!!

Hi. Congratulations for your good work!!!
Last week i bought an O2 XDA Neo (used) from Germany. Everything was working ok. The only problem was with the language (German) so i wanted to change the language to English and after that if it was possible to Greek. I thought that the only way to do that was to change its firmware. My phone had the official firmware WM5. I downloaded and installed ActiveSync on computer. Then i synchonised the PC with the phone succesfully. And at last i runned a rom that downloaded from wiki from the prophet forum. It installed succefully but after a restart the phone stucked on a three colour screen. I reinstalled the same rom and another rom but the problem is the same. Nothing works. The phone is dead?
What did wrong? Is it possible to repair this problem? Plz if enyone knows something, i would appreciate it if he replies to this thread.
the good thing is..
your prophet is NOT dead..
simply flash it again..
tri-colour screen is a bootloader mode and in that state you still can flash your neo with RUU ROMs
a prophet is called DEAD ,only if it cannot enter bootloader state
flash it with ORIGINAL ROM..and that should works..
read the instructions before going to WM6 as it needs some steps before simply flashing it
check this link :
http://forum.xda-developers.com/showthread.php?t=389558
Hi m friends. After hard work i finally made my phone works again. I instaled the oficial rom for prophet (O2 Germany) that founded in another thread. Then it worked fine. Then i hadrspled my devive and finally i installed a WM6 rom caslled evolution.... and it worked fine. But does enyone knows if it is possible to have greek language and greek keypad on my prophet? Thank you for your help in advance.
There is a greek ROM here: http://forum.xda-developers.com/showthread.php?t=323868
It uses the old upgrading method, so you will need to flash the "Part One" ROM first, then don't do anything to the device and then flash the "Part 2".

Problem after upgrade wm6.1 on polaris

Hello all,
I am in crisis situation.
I purchased the touch cruise (polaris) from authorised dealer in the middle east (my polaris is middle east version) came with wm6 SPL 1.28.000. ROM 0.0.415.2 (sorry I had saved the details in one of the files but I guess it got deleted. so I dont remember which ROM version I had)
I wanted to test the diamond TF3d style, so I upgraded. below is the steps I took
1. Hard spl - v2
2. downloaded _HTC Touch Cruise_RUU_Polaris_HTC_WWE_3.13.405.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe
3. installed the same.
4. Installed HTC-CA-Polaris drivers and TF3d.
5. I read somewhere that it works slow and need to upgrade Radio to 1.59.42.23. I did that.
but now my GPS is not working with Garmin also tried TOm TOM which is installed by the WM6.1 upgrade, no luck even the phone is too slow
I want to revert to the original version. please help me find the ROM download and steps to downgrade to original. I can downgrade the SPL to original but need to have the ROM first bcos I dont want my phone to be total dead.
need urgent attention from the experts.
thanks in advance
Niranjan
In my experience downgrading radio is bad thing to do.
When I did it, my signal has weakened radically, and I lost WiFi stability and almost lost BT.
However, hardware was not damaged, so I have normal reception after turning back to the official WM 6.1. So I guess you will need to hack your device again, or wait for newer ROM...
Oh, yeah... I never did hard-SPL...

Categories

Resources