Hi, I hope someone out there can shed some light onto this problem. This is what I have: Orange SVP M3100; Operator: 14.123.1.614; ROM Ver.: 1.23.61.4; ROM Date: 07/13/06; Radio Ver.: 1.06.00.00; Protocol Ver.: 32.37.7010.01H.
I've downloaded and successfully (I think) flashed Hard-SPL-V7.
Bootloader used to read: HERM100; IPL-1.01; SPL-1.04.
Bootloader now reads: HERM100; IPL-1.04; HERM100; SPL-210.Olipro.
The phone still works and syncs. properly, but when I try running SPV_M3100ROMUpdate_0407, it eventually returns Error 260 (Update utility cannot connect to your PDA Phone.) This happens in Vista Ultimate and in XP Pro.
The program will go as fare as identifying the current image as Ver.: 1.23.61.4 and suggests to replace it with image Ver.: 2.11.61.1 however, when I click on OK, it puts the phone into Bootloader mode, disconnects the USB connection and unable to reconnect again. After this I have to do a soft reset and everything goes back to normal.
I'd very much appreciate any ideas to help me get around this conundrum. Many thanks.
put device into bootloader and try flashing from there, otherwise try sd card
OK, I could not flash from Bootloader either; same error message.
Extracted the SVP_M3100ROMUpdate_0407.exe onto the SD card.
Ended up with the following files: EnterBL.exe; GetDeviceData.exe; README.doc; ROMUpdateUt.exe; RUU.dll; RUUUI.dll; RUU_signed.nbh.
None of the above files will run on the PDA. What do I do next? Sorry for being such a novice and thanks again.
commnet said:
None of the above files will run on the PDA. What do I do next? Sorry for being such a novice and thanks again.
Click to expand...
Click to collapse
Correct, the files are not run from the device.
The hermes wiki has the directions for flashing from an SD card, go check it out.
Thanks for that jdc. I found the information you have suggested and here is what I did so fare:
-Formatted the SD card.
-Renamed the ROM image file to HERMING.nbh
-Inserted the SD card with the renamed image file into the phone.
-Restarted the phone and confirmed that it was reading from the card.
-Put the phone into Bootloader mode by pressing PWR+OK+Reset.
The multi-colour Bootloader screen comes up and nothing else happens. I'd tried pressing the PWR button just in case, but it had no effect.
Any more ideas? THANKS!
SPV m3100 upgrade - error 260 - connection drops when allowing enterBL.exe to run on
Hi - am going through the same process to upgrade my SPV m3100.
I've followed Mr Vanx's guides to the letter - ROM update from 1.23.61.4 to Hard-SPL-2.1 - as soon as i click 'yes' on the phone to allow enter.BL.exe to run - the connection between phone and laptop immediately drops.
I've tried using different USB ports as suggested in different threads = but to no avail
Am running Vista Home Premium.
I'm a novice so sorry for sounding stupid - any help would be really appreciated.
I had the same error until I disabled the phone lock. Worked ok after that
I had this problem for awhile, and I'm using Vista. I can't remember the problem to explain it, but I did one of 3 things to fix it.
1. Follow Mr Vanx's Vista Guide. The most important part is downloading his attached drivers and getting Vista to detect your phone as an "HTC USB Device" or "HTC USB Sync" or something like that.
2. Then I would recommend installing the official ATT Rom, you can download it off of HTC's website.
3. Install Schaps Advanced Config cab, and disable "security warnings"
After this done, you should be able to install a cooked rom from here.
Related
Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?
Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]
This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.
Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…
Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...
Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.
I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.
Okay I'll give that a go now... Will let you know how I go...
Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?
Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?
I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??
Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...
Hi,
I was upgrading the software upgarde on my device. I successfully upgraded the Pocket PC software on the O2 XDA, but when I tried to upgrade the GSM radio/GPRS software of the O2 XDa, it gave some error and after this my device is not starting at all. The only mistake I did was that "I did not remove the SIM card before upgrading the GSM radio/GPRS software" The device does not start even after cold booting the same. When I start the device, the O2 screen comes and after a quite long time the main window does come but I cannot do anything. I tried to tap on contacts, time, tasks but nothing happens. I can see the windows logo wall paper but cannot do anything. Please help on how I can restore back my O2 as a cold reset also does not work. :?
Thanks and Regards
Jinesh
There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip
There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip
Hi,
I have tried all the available options but it still does not work. To restore the ROM how do I get access to the O2 cause niether serial nor USB is detecting it.
Please help.
regards
Jinesh
SD card install guide
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
Thanks Chief, I will try out and let you know.
regards
Jinesh
Hi Rudegar,
I tried the procedure given by you. I was able to write to the flash successfully. After writing to the flash it gave a message "Checksum OK, Please cold reboot to reset".
I did a cold reboot. After starting the O2, it showed the O2 logo screen and after quite a long time, it asked me wether I want to format the SD card or not. After that it took me to the default screen of XDA wher eit showed options like "Add today's date, Contacts, Schedule etc etc. but upon tapping any of the options the O2 behaves erratically. If I tap on today's date it takes me somewhere else. Inshort it does not work.
I again did a cold reboot and now the device is in its original position i.e not going after the O2 logo where it gets stuck up.
One thing I would like to mention is that all these activities have been done putting the O2 on the cardle only as the battery is totally discharged and the device turns on only after putting it on cradle. Even after the cold reboot it does not start unless I put it on the cradle whichis connected to the mains. Is it Ok with this or am I doing something wrong? The battery does not charge and hence I have to do it in this way.
Please suggest what wrong am I doing? Any suggestions from anyone will be welcome.
regards
Jinesh
Hi,
Someone posted the original O2 ROM on this site and I downloaded the same after which I was partially succesful in flashing the ROM and reviving my dead O2 back to half life. :roll:
I burned the ROM on
to my SD Card and flashed the ROM on to my O2. After
successfully flashing the ROM I rebooted the device.
The device now starts Windows but it takes atleast 15
minutes to start. I get the today screen. WHen I cick
on start the start menu appears after a delay of 10
seconds and all applications run normal, however all
this happens only on the Cradle only.
When I go into the Battery Settings it shows "Battery
Status Unknown".
Also none of the phone functions work. The SIM card is
not recognized and in device information it does
dispaly the "IMEI number" and the "Protocl Version"
I am only able to use inbuilt phone applications.
Is there some problem with my battery cause it is not
charging even on the cradle.
Device Information does not show Radio Version, Protocl Version & IMEI number at all.
Can anyone please help me?
hello all,
it means that your radio stack are dead. Currently, We don't have any real method to fix this problem. When the radio stack is error, you can not upgrade it or do anything to make it work. We can only upgrade or downgrade the radio stack if it works. Also if you try to upgrade the radio stack, we realy need to flash the chip using a speceial tool or need the sd card which build in radio stack with we can only flash in bootloaading mode. Howerver, in some case, we can fix it but .... I think it is just lucky or the xda error when battery problem.... in this case, just disconnect the battery few minutes and connect it again by pressing the battery hole.
Regards,
Hoanghon
p.s. I have dead xda. I killed it when I upgraded the RADIO STACK. Therefore, if you are really need to upgrade the radio stack, I recommend use the official upgrade for secuirity. or just upgrade the rom only.
Note:
To eliminating the error, you need to upgrade the rom or the radio stack, you need to check if the rom fix the radio stack or the stack you are trying to upgrade it fix the rom or not.(ie, Tmobile Rom have to use it radio stack built for Tmobile pocket pc...... I know that in some case when we mix between the radio stack and OS it works but I don't think it work propertly. Anyhow the mixing bettween radio stack and OS is very dangerous if it doesn't suppport then you have to reflash the radio stack or rom(the OS is Okay but the keep upgrading the radio stack may cause the radio stack killed)
WE NEED SERIAL CABLE FOR PDA ANY HELP PLS!!!
Hi Jineshd we
have the same problem and we are sure that the only way is to do SD uptade
and U said U have a serial cable to Yours device. With that we can be able to download flash gsm rom from working device and put it back via SD card to ours. Pls tell me where can I get a serial cable or some schema how to prepare it and I will try to repair ours dead pdas. Its our only chance
rgds
Lukasz
Hi,
Thanks all for the replies.
Can anyone tell me how doI repair the radio stack?
Regards
Jinesh
no way without having special RSU rom update on SD card and run it from bootloader or dissembling the device and reprograming GSM rom on special rom/bios programing socket. (Here on forum is user Cgigate from Toronto CA who can do it but I cant contact him)
Hi
I am new here and i have problem
When i turn on my qtek9000, i recieve message Serial V.100.
If i connect USB cable it displays USB instead of Serial.
This happened when i tried to do radio upgrade (through usb hub, sim and sd were also in phone...).
I have 1gb SD card and also card reader mounted in laptop, so transfering files should not be problem.
Can someone help me with step-by-step procedure how to make my qtek work back. I used a lot of search but i am even more confused....
I just remember that when qtek worked Radio was something like 1.0.3.1 and also WWE was writen somewhere....
Probably i should put rom to sd with ntrw (which wersion of both),.......
please help....
might be a dumb question on my part - but have you tried a reset (initially a soft one but then a hard one of course, if nothing else works...) ???
I mean you will at least be able to revert back to the condition 'out of the package'...
Hope everything works out!
jup.both things NOT HELPED
looks like you're stuck in the bootloader mode....
try flashing the rom & the radio rom once again by connecting it to your laptop's usb...
i guess something screwed up while you were upgraging your radio rom...and you'd need to redo it!
Best,
San
can you please write me a procedure?
You might want to check the following thread. Everything is well described.
Cheers
hrb
http://forum.xda-developers.com/viewtopic.php?t=32725
i am trying to download files but i get permission denied all the time
You mean you get an error when clicking this link ?
ftp://xdaupload:[email protected]/Universal
I don't understand that, it works perfectly well for me
Cheers
hrb
I have solved problem with Radio upgrade. I am in much better mood now. 8)
Anyway i have 4 more questions.
1.) I am using bluetooth car-instalation Parrot CK3100. I am wondering if is possible to transfer any other sound except telephone conversations to that device. When i had Nokia 9500 i was able to hear every single click,tone,...i made on phone also on car-instalation. I also heard nokia ringtone in car instalation.With qtek i am getting generic car-instalation ringing tone instead of phone ringing. Otherwise primary intention (hands free talking) works fine. I would like to have that to be able to hear voices from various GPS software.
2.) Since QTEK9000 is PDA and phone in single unit I would like to have in car GPS application "always on top". Like previously mentioned i can easily manage my calls with car-instalation. Therefore i would like to run Phone section in background or GPS applications on top.I hope you will understand what i would like to say
3.) I also need in-car holder for qtek. Do you have any reccomendations?
4.)
My settings:
R: 1.04.02
G: 42.37.P8
D: 1.13.64.WWE
Is that ok or should i upgrade?
Stuck in bootloader mode
Hi guys,
Got stuck in bootloader mode following an upgrade attempt. Tried to reflash radio using the files from the pload folder only to get an error saying it's for the wrong device - tried this several times with the same result.
any ideas?
Is there a binary and a tool I can just do a straight upload?
thanks
Re: Stuck in bootloader mode
Bauser_uk said:
Hi guys,
Got stuck in bootloader mode following an upgrade attempt. Tried to reflash radio using the files from the pload folder only to get an error saying it's for the wrong device - tried this several times with the same result.
any ideas?
Is there a binary and a tool I can just do a straight upload?
thanks
Click to expand...
Click to collapse
try it with this file -
1. put radio.nbf and the file attached below in the same folder and run the exe with ur device connected to usb in bootloader mode...
2. hope it flashes it
S
Thanks DreamTheater
Thanks for your help - unfortunately I got the same message, ie this rom is not meant for this device etc...
Will see O2 can do anything (who's that laughing...???) - was going to buy a new xda mini anyway...!
1. REMOVE your SD/MMC card.
2. Soft/hard reset.
3. Run the upgarde again.
Step 1 above solved my problem.
Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.
Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54
problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional
Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer
use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V
any help with magician rom?
OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???
Hello there,
Ive been running around this forum since yesterday night trying to change my qtek2020 from wm2003 to wm6. But there's a lot of dust in the air... to much information, most of it very old, so... here's where i am right now.
1-I've downloaded a rom ( a nb.nbf file)
2- donwloaded a program called HimaUpgradeUt_noID.exe, that I know it's used to install the roms.
But now, I connect the ppc to the usb cable (in vista) and run humaUpgradeUt_noID.exe, select the .nbf file and "next" it, but it always to no success.
I've tryed booting the qtek in "bootloader mode" but all I see is a "Serial v1.03" screen and nothing happens, even when connected.
So, can anyone give me a turorial on how to do this?
Thanx
the rom packets should include a readme.txt which should give a step by step guide
Thanx for your reply.
The problem is that I can't connect to my laptop on bootloader mode.
When turned on, it can connect to my laptop, but in bootloader mode it doesnt, the pocket stays in the "serial v1.03" screen.
Nevermind... solved,
As simple as... removing the SD card... LOL
The SD card is never the reason in upgrading the device using vista.
Look at this forum: http://forum.xda-developers.com/forumdisplay.php?f=387