Was experementing with S200 recently.
It appears to be a problem with downgrading device, with using standard tools. After upgrade to RUU.Prophet-2.15.13.27-2.15.13.121-02.19.21-Dopod-Asia-WWE-Ship and attempt to return to original QTEK flash, device crashed. 3 colour screen with no possibility to flash with either original flash files or another one.
The best I could do is to use same flash file with Updater.No.Vendor.ID. It would accept the file and start the process.
But looks like not easy to return to original flash, specifically, when it was lower version. It is possible, of course, with using flasher which will copy flash image direct to device without any further checks, like vendor ID or version.
Looking for the tool (flasher/updater) which will not do any check-up during the process. No vendor ID updater does not perform vendor ID check, now need something better, which will not do any check-up at all.
Please post if you have any information on this subject.
de yl1wc
I'm looking for too
I'm in the same situation. I have the latest dopod rom, but i want to go back with the last qtek french rom: no way.
Please, help us!
I think "machina god" can do this tool.
I'm just waiting for this tool, or maybe a new french rom....
why you want back dopod rom is better than qtek
Hi,
Like I was saying above, I am experimenting. I need to have a way to go back. But with No.Vendor.ID it does not not look possible to go back.
With original ROM also.
j'aime les expérimentations
a bientôt
This become critical!
I have discovered unpleasant issues with my s200, since i have switched from original qtek to lates dopod flash. These issues relates to GSM phone. Sometimes can not connect, only soft reset helps. It was never the issue befor. When incomming call and you push on volume control side button, phone is "stuck", nothing happens and no connection.
So, guess what?
I need a tool urgent to recover functionality, to downgrade to original lower number qtek flash from existing latest dopod flash. As mentioned no.vendor.id is not a solution, because upgrade process check for version number, and if the existing version is higher than one you are flashing with, process will fail.
Please advise. Don't propose to buy a new phone
hey! there is a tool called JAWFM!people say that we can use it to upgrade with ani kind of software and it doesn't check vendor I'd!!!But there is one problem-it costs 85 $!
am I right ?
may be someone have it!?
may be that "someone " give it to us ?
Have the same thing. Want to go back to russian qtek ROM, but can not
So I purchased JafWM
JafWM have physycal lock key - so there is nothing useful with getting software alone, without key it not burn firmware.
It really can burn any firmware - but not any firmware have all components. Qtek firmware have all, but JAMIN have only OS, GSM, EXT components.
Is service center the only solution??
No, no, don't tell me this. It should be a tool (ROMUpdateUtility.exe) that does not check not only vendor id, but also version of flash and evrybody will be happy about it.
Question is where is a tool?
later.
Related
Hi Guys,
Over the last 4 days I have been reading the posts and trying all sorts of possibilites to fix my Mini O2...
I did the stupidity of upgrading it without a back up. I bought a german O2. I live in Germany, but guess what I don't speak german. So, either I waited 10 years until I can, or updated it to english.
It all went wrong... nevertheless, I manage to download the qtek and used the no id software to upgrade it. it goes well, radio, ext rom, but when updating the rom - when it gets to half way, the program says there was a problem in upgrading the rom. Maybe some german configuration problem?
Can you guys guide me please? thanks a lot!!
I sorted it out.
Thanks for all those who took the time to look at it. Somehow mx Mini is crazy. What I did in the end was uploading each batch at time. Started with the Rom itself, thereafter the ext Rom and last the radio. I did that by extracting the whole package to a folder and removing/returing the parts I wanted at time. So now I have a full english version in my German O2.
Re flashing phone with wwe rom
What you need is to go into boot up mode on comapct i.e black screen with usb and seriel showing only. then you need to get with Maupgrade patch file and then you can bypass security issues on phone and re flash to wwe roms i.e qtek or i mate jam. Hope this helps everything you need is on this site.p.s remember to unzip the wwe file to get the 7 files and replace patch there before updating. 8)
email me on [email protected] for any queries i will try to help
Re: Re flashing phone with wwe rom
leeeel said:
What you need is to go into boot up mode on comapct i.e black screen with usb and seriel showing only. then you need to get with Maupgrade patch file and then you can bypass security issues on phone and re flash to wwe roms i.e qtek or i mate jam. Hope this helps everything you need is on this site.p.s remember to unzip the wwe file to get the 7 files and replace patch there before updating. 8)
email me on [email protected] for any queries i will try to help
Click to expand...
Click to collapse
Hello , I have a similar problem : I have a Qtek S100 from France but live in the USA . I tried to switch ROM with a WWE one (WWE_11200-172_11200.exe) and got a COUNTRY ERROR msg ; then I replaced the MaUpgrade by a MaUpgrade_noID one and now i am getting an "ERROR 150 : UTILITY ERROR" message ; dont really know what else to do and my phone is on boot mode ....
Could you please help...
Thanks in advance
Hello Guys,
Disaster. I tried updating to the new ROM from the O2 website and it fails with : "ERROR114....
Tried the version from this great forum and guess what? same error.....
HELP !!!!!!!!!!!!!!!!! :shock: :shock: :shock:
My XDAIIi was brill. Now its dead...
Try putting the 2i into bootloader mode by pressing the power button, action pad down and the reset button at the same time. The screen will say serial with a version number at the bottom. When you connect it to your computer this should change to USB. Then try running the update again.
If you are using the modified version I posted on this site then the install will fail. Just run the program MAUpgradeUT_noid.exe a second time without touching the 2i at all.
Hope all goes well.
Hi Pug,
Unfortunaely that has not work. see screen shots attached.
can anyone tell me what this damn error is pls...............
oh by the way the iMate PDA2 rom fails as well with the same error. !!
If both your devices are failing to upgrade the problem must lie with your computer somewhere.
Are you using firewalls like zonealarm which may be interfering with the update process. If so try disabling them.
I assume you are connecting using USB and not serial. Do so if for no other reason than it's faster.
Are you using Activesync 4? More stable for upgrading than 3.8 but lacks sync over LAN feature - not a great deal if you've never used it. You can find this on the wiki link top left of this page.
Try downloading the packages again. I've posted the radio rom here as thats the one you seem to be having immediate problems with. Download it and overwrite the one on my modified rom.
I'll post more if I think of anything as I'm suffering a hangover right now and can't think too much cos it hurts. :?
thnx pug,
really appreciate your help. yes iam running firewall (norton). I will try your modified radio and advise. fingers crossed. and thnx once again.
using activesynch 4 as well from this forum
Hi pug,
Sorry the radio did not work. renamed the radio and ran update and the update works for nk.nbf and ms.nbf files. without radio the phone does not work but proved that there is no problem with my pc or usb cradle etc. the problem is the radio.
my IMEI is 354962000270150.
the radio file from the Launch rom from O2 does not work, so either my IIi has a damaged component or something else that I am not aware of.
copied your radio file to the other iMate upgrade and it still fails with the same error 114 !!
Any other ideas or suggestions pls, its really depressing to loose the XDAIIi permanently.
Oh I forgot to mention that the IIi is also unlocked and the ExtROm is unlocked as well. Will this make a diffeence?
The fact that the 2i is unlocked won't make any difference. The EXTRom on the 2i can't be unlocked and always results in the storage being locked which will stop the phone being updated. Maybe not at the actual update stage but certainly further down the line after the hard reset.
Ok now I have have tried various things as posted in this forum in various sections. Still get the same error.
Originally about 3 months ago, I had to hard reset, then I used the Launch ROM from the O2 website. I still have that original exe but that also NOW fails. I am now running out of options.
Any other ideas?
It might be that because you have unlocked the Extended ROM that it causes this fault, either that or you device has an internal problem which you cannot fix.
Take it back to the shop they will replace it.
114 error
I got my XDA2i back from O2 after a warranty mainboard replacement and decided to upgrade with the new O2 rom..horrors.. I got the 114 error and repeated efforts failed to cure it. I then inatalled a/sync on another PC and ran the upgrade from there...
Bingo! it worked..always worth a try if things defy logic.
Probably an old firewall that didn't uninstall properly.
One thing though, does anybody know when my backup battery will kick in and charge.
It arrived back from O2 completely dead but even with the main battery full it doesn't want to take a charge yet??
Hitla
Just humour me and try the radio upgrade on another PC... That's how i got round my 114 error
To all the people who have advised me... thank you.
I have tried the upgrade on 2 other laptops I have, one with Activesync 4 and one with Activesync 3.8.
AND..... the same failure error.
I have now taken it back to O2 and they have taken it in for repair !!
Should rcv it back next week hopefully repaired or replaced !!
Will keep you guys posted.
Once again great forum and great posters with serious technical advice.
Well done keep it up.
Soory guys,
Have been away for the last few weeks, so unable to update you all.
Well O2 replaced my device. It has the new ROM but the old radio !!
I would like to thank all of you advised me.
Hi,
I just downloaded the O2 Rom-Upgrade.
To keep my 2020i in German I only did a Radio-Update from 1.02 (ran the installer and copied the files to a different directory together with the AllUgrade kindasomething.....)
The update worked, it always worked this way, but after the update the Radio showed up as 1.00.00 (MUST be 1.03, at least that is what o2 says....)
Any idea?
Thanks, Günter
P.S.: I should add that the phone works..
Hi all,
Hoping someone could help me. My Dopod has been freezing on start-up and after doing countless hard resets i am stuck at the Windows Mobile splash screen!
I have connected it to my PC, but as Windows Mobile hasn't loaded, ActiveSync can't pick-up my Dopod. This means i cannot update or completely re-flash. Is there a way to do this without ActiveSync?
I am now stuck with a Dopod i cannot use. I have no idea what to do.
can you flash using SD card? have a search, im pretty sure that will work.
Or go through the Bricked thread
Are you sure you're doing hard resets and not soft resets? Generally when a freeze occurs, you would soft-reset.
If you have indeed been doing hard-resets, then you most likely have a hardware issue and there's not much anyone here can do to help that.
Have you updated your ROM in the past? If these freezes started after an update, then it may be a bad update, so you could either try flashing from microSD as suggested above, or boot into the bootloader as per instructions in the wiki and flash from there.
Thanks for your replies guys!
I have tried all that. My son knocked my usb cable from my Dopod whilst it was updating my ROM ... that was the cause of my Dopod current 'brick' state!
My bootloader is SPL-1.09, but i have noticed from here that the Dopod ROM that i require (for Hutchinson '3' - Australia) uses bootloader SPL-1.06. Is it true that i cannot down-grade from 1.09 to 1.06?
I ask this question as i get "Invalid Vendor ID" attempting to flash my Dopod with that ROM. When i don't get that, i get communication errors (Update Error) when attempting to run Hard-SPL-V7.
What could i be doing wrong?
Hey guys,
Think i have worked out that my CID is corrupt, therefore i can't flash any ROM even if i wanted to. I used mtty and after a bit of searching in this thread (http://forum.xda-developers.com/archive/index.php/t-291336.html) i found that the 'info 2' result i got (HTCSF kEØ(HTCE) meant my CID was corrupt.
Hopefully i haven't voided my warranty as i haven't attempted to flash any 3rd party ROMS, only the one on the Dopod website that was accidently stopped when my son tripped over the usb cable.
We shall soon find out!
Read until post 4#
Ive tried to download a rom, and i used its update tool and used mine nk.nbf, but when i click upgrade, i get the error "Error [238]: File read"
I have a G4 device - Cid unlocked
Now rom: Touch no evil (Lang: English)
Required: Normal WM5 rom (Lang: Danish)
What to do
Go to your phone's service provider website. You will find the latest update there.
It will probably be older (like, last year sometime), but it should be a single (albiet large) executable. No need for additional software, and you can remove the CID unlock, because it won't care.
If your Service Provider doesn't have it, you can download the Cingular 8125 ROM here: http://www.america.htc.com/support/8125/software-downloads.html
The TMobile MDA ROM is here: http://www.t-mobile.com/wmupgrade/
I'm sure you can find it. Use Google. Don't be lazy.
I have already downloaded the rom i want (Yes, from my provider).
But i cant update with it because it says "Invalid update tool" (I did it before)
So when i try to use another update tool it gives me an error reading the file
Remove the CID unlock. It may be hindering the default ROM from loading (it's a a crap-shoot, but it's worth a try...)
What actually is the status of your phone ? is it working normally ? what do you exactly mean by CID unlocked ? cuz a G4 device cannot be CID unlocked.Have you got it 'SoftSPL or HardSPL' ? which Rom exactly you are trying to upgrade with ?, Post your present IPL/SPL...? here,to determine the status of your phone,in order to provide you with any advise or suggestion,if you have downloaded latest official carrier's rom from it's website,there shudn't be any problem upgrading with,ok
Cheers !
Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.