hi one and all.... my xda II mini was being upgraded to the o2 1.12 rom and then halfway through, it went into bootloader mode and the pc stopped recognizing the device. Now, every time i try and reset the device, it installs the extended rom files and after 5 minutes, goes into bootloader mode. it also goes into bootloader mode on soft-reset. Can anyone help?
by the way, my current rom and radio versions are 1.01
as far as i known ROM 1.12 is for O2 Mini Black Limited Edition .....
If Your Device Not Limited Edition It Can't Upgradeable to 1.12 ROM ....
The Latest ROM For Your Device 1.11 .....
Or just install any Magician rom version 1.13. But before you do that, copy everything out from the extended rom first.
To make you device an O2 device, you need to install the After_Sales_Service_100121.sa.CAB (from 1.11 rom). After that, you can install any O2 application you want.
i can't upgrade my rom though; the 1.13 rom (t-mobile uk) doesn't work, and when i try to upgrade using that, it gives me some error - re the rom update wasn't designed for my device.... so i am stuck to using it without turning it off, else the thing just runs into botloader mode... whish is quite irritating... i've even tried using ma_upgrade_noid.exe from toomuchdogfur's guide but it doesn't work. nothing seems to work....
Related
Hi,
I tried to upgrade my Qtek S200 with the newest ROM release from PdaMobiz (the 16M pooling page one), but encountered some problems...
It's a Portuguese TMN Qtek (or at least it displays the operator logo when started), although the software is in English.
IPL is 2.09 and SPL is 2.15...
However, after upgrading it, it kept displaying the Operator logo with IPL and SPL, and freezed, so it never worked. When I tried to revert it, I wasn't able to do it, because every time I try to install a different ROM (all of them for the G3 device) it just installs the new ROM, and then goes to that screen and freezes...
It never gave me any error during the upgrading/downgrading, because when it checks the version of the ROM, it displays no information, so it just says that is going to replace the inexistant version with the new one...
Is there a step a missed (I didn't put it in bootloader mode before doing the first upgrade, but I had already done that before with other ROMs and it worked fine...)?
Now I'm stuck without knowing if I should have done an unlock CID before upgrading it, or if there is another steped I missed... Please help me out...
Thanks in advance,
Nuno
Tried this?
Read this in one of the threads and it solved his problem:
Extract the rom file you are using to flash your phone, to a folder on your pc, than Extract the file i attached ("ROMUpdateUtility-NoVendorID.zip") into this folder. than connect your phone to pc and double click on "ROMUpdateUtility-NoVendorID.exe".
I personally have not tried it, but I downloaded the prog just in case, Hope it helps.
Now it gives me an error...
Hi,
Just tried what you advised, but now it jusk keeps giving me the error 208, which is supposed to happen because I have other programs open on my computer... Tried rebooting, closing most aplications with task manager, and still it doesn't work.
Also tried to downgrade to lower ROM upgrade, but it gives me the error that I can't downgrade, only upgrade...
When I upgrade it with AKU 2.3, it goes all the way through the upgrade, and then when it reboots, it just keeps giving me the operator logo screen with the version info on the display.
If I try to reboot to bootloader mode, I'm not able, the only way to do it is by removing the battery...
I'm probably still doing something I shouldn't... It should be able to work the downgrade utility...
Anyone can help?
Thanks,
Nuno
Try this rom:
ftp://xda:[email protected]_021921_DOP_ASIA_WWE_Ship-NoVendorID.zip
It shoud be ok.
If your prophet has spl end up with 2.xx.0001 check at
ftp://xda:[email protected]/Uploads/Prophet/
find out the rom which can solve for SPL 2.xx.0001.
Good luck
Thanks Chan! Problem solved!
I was starting to review all my steps ir order to see what I could have done wrong...
Would you advise me to upgrade now to the PDAMobiz latest ROM (the one with the biggest pooling page)?
Thanks again.
Nuno
1. Unlock cid
Since your prophet spl is 2.15, you have to follow this step.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=437
From file you can get from ftp://xda:[email protected]/Uploads/Prophet/
Your PC has to connect to network or internet (to have ip address), becuase in that script use ping command for delay 4 seconds.
It's just downgrade and unlock cid.
You may verify if cid unlocked, by backup rom to sd card. (use romupdate.exe with r2sd all command, check at wiki)
2. Upgrade to official rom
ftp://xda:[email protected]_021921_DOP_ASIA_WWE_Ship-NoVendorID.zip
3. Upgade to pdamobiz, I suggest you to upgrade 12 Mb pagepool version. (even 8 mb version is ok). Because 16 mb has smallest ram space.
Good luck
All solved!
Again,
Thank you very much for your help!
After some tries, upgrading, downgrading, upgrading again, etc, I finally got it, so now its running the PDAMobiz version, which by the way, seems great so far!
Next time I'll come to you directly and then try to make things on my own...
Thanks again!
Nuno Eça
Hello , I am owner of imate kjam unlocked phone.
My IPL / SPL ver is 2.16.
MY GSM ver is 02.07.10.
My OS ver is2.16.9.1.
I cooked the Crossbow_Reloaded_1.7_Final using core pro.
It completed 100% ok but when i restart my phone the OS its the same.
What i am doing wrong ?
I followed all the instructions step by step without having any problem.The only error i get its when the phone starts up after the upgrade when its installed the programs i get the error \windows\autoconfig.exe does not exist.
Please help me.
Thanks
i had the same problem any ideas?
Your Phone is CIDunlocked. You need to be CIDunlocked b4 you can upload the Rom Properly
Ok after doing all that was told to do to flash a G4 (which I did sucessfully) It does now show the SPL to be 2.21.olip.
At the end of the instructions says:
"After it is complete, your device will automatically reboot. The IPL version will be 2.21.0001 and the SPL will be 2.21.olip. If you see this then HardSPL was successfully flashed to your device.
Now you have HardSPL. You can flash any ROM using the RUU provided in the ROM package, should you have trouble with upgrading, try Mun's RUU."
I flashed my G4 Wizard with the new Diamond "clean" version. I think I want more bells and whisles; Question is...Do I have to do everything all over again or can I just flash with a new rom to a better OS?
I did try to flash to the Hyperdragon 6.1 and the SNN Diamond but, I think the OS I just flashed is too new to reflash to the others (error 264). (maybe I just answered my own question) But the HardSPL IS in there.
Someone please tell me what you think.
Thanks you!
Kim
Depending on my own experience you don't need to do hard SPL all over again. all you need to do is to do a good hard reset and try to update with nice and slow steps
i had a G4 before my current G3 and i know wht i'm telling you
just care to review these steps
- 50% battery or more (100% recommended)
this is a must .. cant flash without this condition
- laptop or pc with ups (you dont want to brick ur device cause electricity was out!) or you can risk and update on power supply
- use faria RUUs (they are the best) they can be used with any rom.
- connect the wizard to the pc after the hard reset (dont forget to backup) and follow the on screen (wizard not pc) till u get working windows mobile device
- when asked for setting ur device .. click escape (as said ... this device is guest till it has the WM that i want!)
- finally try it's right rom it's G4 safe if you ask, you'll find its link in my signature, also i suggest using radio 2.19
- last hint .. never use a rom with IPL or SPL. they will brick ur device (it did to mine )
any more help?
I have two magicians, and I read many posts about nonchangeable version 2.03TX.
I test it, and upgrade one unit. After upgrade really is not possible change any (OS or bootloader). Bootloader cant vrite itself or OS memory. I try all known techniques - SDboot, TTY (lnb, s2d d2s...) via USB, and standart os upgrade via PC (of cours, noID too).
So I have two magicians, then i use good tool from "itsme" called pmemdump.exe (thank you for your good job) and download OS images and bootloader images from my magicians. The reason is:
I dont say when, and/or why, but in some magiciansThe 2.03TX destroy bootloader!!
In my flashed magician is destroyed (nulled) area from 0x10000 to 0x10080.
I attach good (before upgrade) and destroyed (after upgrade) bootloader for comparsion
Maybee if "itsme" (or anybody other? ) create new version of pnewbootloader.exe compatible with version 2.03TX (because under this version OS it not working) then tens of magicians with flashed 2.03TX will be upgradeable again . (I can send any dump if it will be need, or try apply new version on my magicians).
hi mate, i 've had installed 2.03tx and 1.13 radio on my qtek s100 for about one year...
i've had no problem in downgrading radio to 1.12 and flashing device with cotulla rom,
the only problem is that cotulla rom does not support samsung touchscreen
my bootloader is 1.02
the only trick to update i've used is to keep activesync loaded with "allow usb connection" unchecked in settings. then it worked like a charm...
I try it too with unchecked "allow USB connection" in AS (and i have XP). By me (and many others) the problem is owerwrited bootloader. You can see attached files and compare it, you will be see...
You are right, many problems with flashing is between chair and keyboard But not now.
You have the same version of bootloader like me, then probably in version of bootloader its not. I have originally T-mobile MDA compact.
Can you send me dump of your bootloader for compare?
Sorry for my bad english, i am from Czech.
yes mate no problem, link me to a guide for bootloader dumping, i've nevere done it...
ps: good luck for yours magician
Hi Shelver,
I have 2.03TX in only one magician. The second unit is powered by Cotulla WWE_03 now
Download and unzip this: http://www.nah6.com/~itsme/itsutilsbin-20090515.zip
Connect and synchronize via AS your magician, stay connected (this util working via Active Sync) and in comand line (IN win XP of course, in vista its not guaranted) go to your unzipped directory and write this (without commas):
"pmemdump 0x80000000 0x00040000 boot.bin"
and wait few seconds to done.
It read flash from address 0x80000000 to 0x80040000 (lenght 0x40000) and store dump to file "boot.bin" Its bootloader area. Then you can send me it, compare with my posted bootloaders...
shelver said:
hi mate, i 've had installed 2.03tx and 1.13 radio on my qtek s100 for about one year...
i've had no problem in downgrading radio to 1.12 and flashing device with cotulla rom,
the only problem is that cotulla rom does not support samsung touchscreen
my bootloader is 1.02
the only trick to update i've used is to keep activesync loaded with "allow usb connection" unchecked in settings. then it worked like a charm...
Click to expand...
Click to collapse
Me 2, upgraded from tx203 to Cotulla's rom and back for some SMS backup and then upgraded to Cotulla's rom again.
I think I can go as many times as I wish with my magician.
philiplam said:
Me 2, upgraded from tx203 to Cotulla's rom and back for some SMS backup and then upgraded to Cotulla's rom again.
I think I can go as many times as I wish with my magician.
Click to expand...
Click to collapse
You are lucky man I try it only one time, and bootloader is broken.
I have magicians only as toys, then, if it will be problem for me, then i repair bootloader via JTAG I only try 2.03TX, and try search some help for unlucky mans, who havent JTAG Now i have one broken, and one OK. But with Samsung LCD R3 . Maybee, i change display, or upgrade it to 128MB RAM for try _R1
I am HW developer, so HW problems is easy for me I create car multimedia PC on OMAP3530 platform now for my friends. Its better toy for me, magician is lovely history Only SW is hard to write to me
hi certik, my magician is still with cotulla rom and doesn't boot because of touchscreen driver,i've not flashed it again because of i don't use it.
i'm waiting a new rom,
however when flashed i'll send you my bootloader backup
shelver said:
hi certik, my magician is still with cotulla rom and doesn't boot because of touchscreen driver,i've not flashed it again because of i don't use it.
i'm waiting a new rom,
however when flashed i'll send you my bootloader backup
Click to expand...
Click to collapse
OK, Ill wait. I dont need it really, i have stored good copy of bootloader, i need it only for compare
And if you wish, you can flash cotulla WWE_03 ROM (you can directly from _04 to _03 say Cotulla) In this version touchscreen driver worked fine.
e-certik said:
OK, Ill wait. I dont need it really, i have stored good copy of bootloader, i need it only for compare
And if you wish, you can flash cotulla WWE_03 ROM (you can directly from _04 to _03 say Cotulla) In this version touchscreen driver worked fine.
Click to expand...
Click to collapse
humm, ok mate, just the time to flash it with WWE_03 ROM then
hi mate, done, here is my bootloader
ps:touchscreen is now ok, thanks
Hey, you are fast
Thanks for bootloader, its the same as my original bootloader
good luck mate
e-certik said:
I have two magicians, and I read many posts about nonchangeable version 2.03TX.
I test it, and upgrade one unit. After upgrade really is not possible change any (OS or bootloader). Bootloader cant vrite itself or OS memory. I try all known techniques - SDboot, TTY (lnb, s2d d2s...) via USB, and standart os upgrade via PC (of cours, noID too).
So I have two magicians, then i use good tool from "itsme" called pmemdump.exe (thank you for your good job) and download OS images and bootloader images from my magicians. The reason is:
I dont say when, and/or why, but in some magiciansThe 2.03TX destroy bootloader!!
In my flashed magician is destroyed (nulled) area from 0x10000 to 0x10080.
I attach good (before upgrade) and destroyed (after upgrade) bootloader for comparsion
Maybee if "itsme" (or anybody other? ) create new version of pnewbootloader.exe compatible with version 2.03TX (because under this version OS it not working) then tens of magicians with flashed 2.03TX will be upgradeable again . (I can send any dump if it will be need, or try apply new version on my magicians).
Click to expand...
Click to collapse
as you i still have a hope to fix my poor magician
any kind programer can do what you have said will make me and many other happy again
i have the hope
Hi everyone,
I have a big problem and I need urgent help please. I have ATT 750 unlocked and I'm outside the States now. My Treo was 6.0 then I upgrade it to 6.1 so far so good.
Then I saw a custom rom that I thought it was interesting. the custom rom was for HTC Dimond I think. without paying too much attention. I started the upgrade. It went 70% before the upgrade crashed.
Now my Treo is not responding to anything. I have the original ATT 6.0 SD upgrade and I have the 6.1 lite upgrade. I'm using CheetahUnlocker to flash the SPL (that is working) but when I try to install the 6.0 or 6.1 using Kaiser Custom RUU v1 it crash.
I saw the post above that suggest to place the original 6.0 on a freshly formated SD and install from there. that is not working either. when I try to install the software it goes into these steps before it crashes: btw, I have the tri-color bar and it has the following info:
CHEE100
IPL-0.20
SPL-1.40.01iNex
while update in progress i see the following:
CHEEIMG.nbh
SPLASH1 - OK
BOOTLOADER - OK
GSM - OK
MicroP - OK
EXTROM - Fail
OS -
After the crash I get this msg: "Update Terminate Update Failed"
Any suggestion please? need more info? then let me know
You may have corrupted your DOC, you may need to use mtty to reformat it. Do some searching on how to do it.
Or try to use T750URT.exe to restore it, it comes with the Treo desktop updater.
similar problem
Hey guys,
After I flashed a WM6.5 costum ROM in my treo750 it works fine...until 4 hour after...the display just stay black. It´s on, but black!!
I´ve tryed reset, hard reset and force to reflashed to an original WM5.0 without success.
Does anyone know what is happening with my phone??
Thanks