I started with i-mate JASJAR AKU 3.2 Rom Update 1.90.94 (96) then tried Ivans.,.after the upgrade I restarted the cell but got stuck at "the upgrade screen" . I tried again. Wont start the system - stops at the upgrade screen.
Ran 1.90.94(96) again to get myself back to the thing...restarted after upgrade (successful it said)...the same upgrade screen. Tried both roms again but after a so called successfull upgrade they restart in the Upgrade bootloader mode each time....
Whats going on and can i run an old O2 AKU 2 official update? or is downgrade impossible?
i had the same problem once while flashing an official ROM upgrade from i-mate.
nothing i did could get the device to work again.. i took it to i-mate, and they replaced the motherboard, as the flash chip seems to have got busted
wish i had better news
im screwed if thats the case since i used a o2 exec with a jas jar (imate) upgrade, which breaks my warranty unless i can revert somehow back to o2
EDIT UPDATE: God loves me! hehehe...an old o2 version from the O2 website saved me ! It worked ! Learning now - dont use 3.2 AKU till its totally ready
Related
ok, got cocky with flashing ROMS onto my CID locked orbit- i can now only access bootloader. I'm now waiting on imei-check to verify i am who i say i am before they'll unlock my phone for me.
In the meantime does anyone know any other cid unlockers who will do it instantly, or
where i can find a rom that will work from bootloader on my locked device (upgraderom.bat doesn't recognise my phone even though my computer does), or
anything else of any help?!
ps... i assume i can cid unlock from bootloader - is this right?
i did things too fast... not happy!
As far as I am aware you cannot unlock your device from bootloader. For the IMEI-check solution to work, your device needs to be connected and an active sync connection established?
I think your going to be stuck along with alot of other people on here awaiting an O2 UK ROM so they can restore their bricked phones.
rubbish! how frustrating!
surprises me that no one has been able to come up with an RUU for UK o2 orbit...
Did the above and only have bootloader option, "honestly" rather than o2 to release a WM6 ROM, I have sent my XDA Orbit (still under warranty) back to o2 yesterday (Sat 2nd June 2007) for a reflash, told it'll take 7-10 days. So when it comes back (will update time taken) gonna get it CID unlocked and do the WM6 update again if o2 hasn't released the official ROM..
Good luck...
@it
@it said:
Did the above and only have bootloader option, "honestly" rather than o2 to release a WM6 ROM, I have sent my XDA Orbit (still under warranty) back to o2 yesterday (Sat 2nd June 2007) for a reflash, told it'll take 7-10 days. So when it comes back (will update time taken) gonna get it CID unlocked and do the WM6 update again if o2 hasn't released the official ROM..
Good luck...
@it
Click to expand...
Click to collapse
sorry to hear that... i still have my wizard which i've reverted back to for the time being... i'm considering sending mine to imei-check who will fix and do the cid unlock for £40 + £7 shipping... thiking it may almost be worth it for my stupidity!
Still hoping that someone will manage to dump their o2 rom and produce a uk RUU though...
i read somewhere that it may be possible to modify a foregn rom with the uk ID... anyone know about this?
Why send it in when O2 is gonna release their official rom update in maybe 2 weeks or so? When it is released, you'll be able to update it from bootloader mode. Just have a little patience, btw I have the same problem, let me know when you're able to change the device ID code in RUU !
Neozzz said:
Why send it in when O2 is gonna release their official rom update in maybe 2 weeks or so? When it is released, you'll be able to update it from bootloader mode. Just have a little patience, btw I have the same problem, let me know when you're able to change the device ID code in RUU !
Click to expand...
Click to collapse
Well simple reason is that I need the XDA Orbit and we don't have any rumour or info re an official o2 WM6 release.
Simple solution I dare say and it aint gonna cost me a penny.
@it
XDA Orbit WM6 Upgrade for UK
O2 have finaly released the WM6 Upgrade,
http://www.my-xda.com/xdaOrbitSoftware.html
I have been trying for the last two days to get onto HTC web site?? still no luck with the download
The original WM5 ROM is available for download, which will run when phone in bootloader mode. Run this to unbrick your handset then unlock it.
tcfuk1962 said:
O2 have finaly released the WM6 Upgrade,
http://www.my-xda.com/xdaOrbitSoftware.html
I have been trying for the last two days to get onto HTC web site?? still no luck with the download
Click to expand...
Click to collapse
Download link has been withdrawn. The download is NOT ready yet.
Shand359 said:
The original WM5 ROM is available for download, which will run when phone in bootloader mode. Run this to unbrick your handset then unlock it.
Click to expand...
Click to collapse
Is the correct answer.....
If you don't mind going back to WM5 until it is released, here is a link to the thread with the original O2 Orbit UK ROM download on it:
http://forum.xda-developers.com/showthread.php?t=314866&page=2
@it said:
Did the above and only have bootloader option, "honestly" rather than o2 to release a WM6 ROM, I have sent my XDA Orbit (still under warranty) back to o2 yesterday (Sat 2nd June 2007) for a reflash, told it'll take 7-10 days. So when it comes back (will update time taken) gonna get it CID unlocked and do the WM6 update again if o2 hasn't released the official ROM..
Good luck...
@it
Click to expand...
Click to collapse
If you've sent it back to O2 now then they will put WM6 on as part of the 'repair' unless you asked them to put WM5 on it.
Guys,
I had lot of problems upgrading my orbit, first of all i used Pof USPL for making my CID lock phone temporaly unlocked first i got some errors such as PDA and error [270] on the "PDA phone ROM Update Utility" this was easy couse i just disabled the windows firewall an i got it to work. but when i started the black&blue wwe upgrade i got some errors there my phone was low on storage space and when i cleared the storage my phone is stuck on the bootloader meny, i tryed to update with USPL again directly with ROMupdateUtillity not with the USPL_start.exe couse my phone is not loaded to winCE and not active sync, i did this by going to bootloader meny RGB meny and stgarted the o2 german update but i get i message telling me that the phone is wrong model ID error 244
With these problems i concluded that
You have to make sure that you have installed properly USPL
You have to make sure that you have free storage space
You have to make sure that you had disabled windows firewall
Any advice is very usefull to me and the xda-developers community
Kind regards
I also managed to get pof's USPL correctly installed. I then successfully flashed a WM5 HTC ROM just to test it was working. Success. I then flashed a WM6 ROM. Unfortunately I forgot to re-flash with USPL first. Hence I "BRICKED" my phone. A quick trip to my local O2 store, my brick was sent for repair. I have just received it back. Repaired under warranty. "Software Fault". Now I paid imei-check, got it unlocked and have now flashed BEPE's WM6 ROM successfully. So much faster that WM5. Great.
can't seem to get this upgrade to work. the updater stops at about 28 percent for me with an error (286? i think) and after that i'm stuck in bootloader. Every time after that, the updater wont even start.. (a different error).
i can flash successfully a cooked ROM, but can't get the official one to work. Could it be a conflict with Des' crash-proof SPL? That's the only thing i can think of at this point..
To me said invalid device id, and got stuck on the boot loader
try back to any old offical ROM
and then copy SSPL to PDA and run it on PDA
when bootloader appear, run WM6 offical updater
I got same problem too and get fix
good luck
update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?
It installs a new bootloader that can't be hacked by the previous hacks I think.... I'm stuck in it too...
SPL-3.03.0000
racerx_ said:
update: since i managed to flash PDAVIET's rom, i thought i'd just try going back to Olipro's hard-spl and see what happens.. So i flashed it, entered bootloader and ran the WM6 update again, and SUCCESS!!
very strange though.. anyone have some thoughts as to why it wouldn't work under Des', or if this is just coincidence?
Click to expand...
Click to collapse
Hi racerx,
I've encountered the same problem as your, stuck at 28% ERROR [286] while flashing, and couldn't go over it even after recovery process following the instruction.
Could you please explain a bit more details about how to go back to Olipro's hard-spl and enter into bootloader?
Thanks, eager to flash the new ROM...
Well I was able to get out of it by running Pof's CID RUU Unlocker, however, it errors after 7%, and resets. It gets past the bootloader, however, it hardreset the phone...eh.
IT happened to me too - Update Error.
So should i go back to Official WM5 then update to WM6 (i had AX3L installed before and i just had to reflash back to AX3L coz of the error from WM6).
Kinda scared me.....LoL
well, to start with i had Des' Crash-Proof SPL on my phone... so after the updater hung at 28%, i remained in Des' bootloader. I then ran the RUU for pdaviet's ROM, which flashed successfully. After that was on and my trinity was up and running, i flashed Olipro's hard-spl. Then manually put it in bootloader again, and flashed the official ROM.
Let me say this, though. At this point, i think you should be content to get your device out of bootloader mode. This Dopod WM6 doesn't have so much to be desired in it compared to cooked ROM's on this forum, plus your bootloader will be stuck at version 3.xxxx which i don't know if anyone is sure how to deal with yet. I'm regretting flashing mine to official version. Should have waited for a chef to pack it up for me.
what does your bootloader say?
You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.
yeah saw your post on the other thread.. thanks for the tip! talk about a stressful morning haha..
i was waiting for this ROM cause my activesync has mysteriously stopped working for a couple of weeks. so i was going to flash and take it to the service center. The miracle of it, was after my device hung and i reflashed pdaviet's rom, my activesync mysteriously works now even though i reflashed a million times before trying to get it going haha..
new spl is needed for flashing new radio rom with cid locked device.
So that's why RUU reflashes SPL at first.
U could simply reflash HArd spl back by using sspl
mUn, when can we expect your much anticipated "Indigo" rom using this offical WM6 base??
Genius! thanks for the tip mun...
all i can say is one word....
INDIGOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!
I also got Invalid vendor ID when I tried to flash for the first time. But it flashed just fine after I put it into bootloader mode. Give it a try..
Flashed my mine in a breeze from LSVW version 27/05/07.
myppcsg said:
Flashed my mine in a breeze from LSVW version 27/05/07.
Click to expand...
Click to collapse
still same problem
can you post the RUU files plz
mxlaser said:
You need to actually have a device that this release is supported by. It flashes a new SPL but you can flash Olipros HARD SPL 1.20 straight over that once WM6 has flashed.
It replaces any HARD SPL before flashing, probably to ensure only official devices get this update. Those having issues are probably out of this.
The official rom is fine, not as finished or customised as some chef ones, but good none the less. Also, the new 3.0??? SPL is no issue at all and easily removed once flashed.
Click to expand...
Click to collapse
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....
geoffreyhan said:
Thanks for all the helps from you guys. This is what I did after stuck at 28% with ERROR[286]:
1. Flash back to Official OZ WM5 ROM. Had no problem to flash back as it was in the bootload mode.
2. Flash Olipro's Hard-spl. No problem as well.
3. Flash Official OZ WM6 ROM again...... and stuck at 28% again!!!!!! with ERROR [262] @#[email protected]#$.
4. Now in the process flash back to Official WM5 again... @#@#@....
5. Will flash Official WM6 straightaway after that.
6. Will update result later....
Click to expand...
Click to collapse
hehe i did that many time this day maybe hmmm 5 or 6 and im still doing that
try to use another version of RUU (the older one)
ps. plz don't post messages about indigo in other tgreads ) if u want to ask - so ask in mine thread.
I'll flash official rom today and then will make some conclusion ) but i thibk that indigo will be based on oficial release
Hi!
I've an Artemis (o2 germany-software) and i already updated it to WM5 a year ago. Now my friend bought the new artemis with WM6 on it and with that cube and everything (with the o2 branding). So i wanted to get WM6 and saw it on the o2 homepage as a free update just like WM5 update the year before. So i tried to update and a comunication error 302 appeared at 51%. After the restart only the bootloader worked. then i found out that it's possible to load the update on a fat32 formated sd-card and it worked but the hardware reset wasn't possible out of the bootloader in which it switched back every time. So i took any cooked rom for my device, tried to update and it interrupted after 3%. When i now restarted my Artemis it worked perfekt with the o2 branded WM6 soft. But that soft looked so different to my friends one. So i used the USPL update to unlock my CID and choose any rom for my device. it failed. so i had to use the original rom and another rom to get it working again. then i choose the next new rom for Artemis....
I've tried it at least 30 times now with a different Rom every time and i'm close to a complete nervous breakdown. Does anyone have an idea what i could do to get WM6 with cube?
Its simple heres the link for wm 6.1 with cube - http://forum.xda-developers.com/showthread.php?t=371182
make sure you run the tool to cid unlock firtst though.
I already tried that one. it failed at 85% with update error 302
oh man!!!!! it worked!!!!! I don't know how but the full version with cube worked!
I'm so happy! Who made that Rom?
I have Orange branded spv m700 and have unlocked and supercid'd the device using pof's tool. I then added HardSpl (Olipro 1.20). All appear to have loaded fine - phone is unlocked and Olipro shows up when put into bootloader.
So, the problem - every time I flash a cooked ROM (Ausdim, NiAx, FiNixNover...?) it won't boot past the first screen. I can rescue the situation by putting device into bootloader and flashing the official WM6 ROM (no radio, no ipl....) and it boots up just fine.
Can anybody help or at least point me in the direction of some good advice?
hmm... odd... can you list step by step what your procedure is for flashing the ROMs
I've done lots of devices - old XDA2i, SPVM600, wifes SPV M700 (unlocked, hard spl etc and flashed away!
This particular device shows IPL 0.50 & SPL 1.20 Olipro. It is unlocked (have o2 sim working in it), and should be SuperCid (I checked the box and radio shows as 1.16.00.00 - pof's patch I believe?). I also re-run HardSpl and Pof's unlock/supercid patch just in case it hadn't flashed properly.
I generally just download ROM and flash via RUU. Occasionally I get the device not responding error so I just re-run RUU from the bootloader screen.
Have tried WM 6.1 and 6.0 cooked roms but all show initial boot screen (numbers along bottom) next screen and then frozen, have waited and waited and nothing. Also, it would not flash back to Mozzers WM5 Orange UK ROM - same symptoms. I thought it was bricked, but the Dopod WM6 flashed perfectly.
Hope that helps - thanks for looking into my problem.
anybody please? por favor........
hmm.. i remember someone having a similar problem but it was some time ago..
two things to try just in case...
1) i'd manually go to bootloader (hard-spl) before flashing
2) Have you tried to flash from SD card? this method seems to provide less problems..
let me know how it goes..
A degree of success - managed to flash WM6 AX3L. All seems to be working. As I recall this is very similar to the official ROM and I used to use it last year because it is very stable. Think I moved on because of the missing email accounts problem. Will happily keep it if I can sort the email problem out. Never really had much fun with the hard reset after loading method - is there another/better way? Just wondering.
Also, now I have a "cooked" rom loaded perhaps it will stop being so sensitive.....!!
How strange! Have just flashed Akeo's new Diamond port ROM and no problems. Not only that, the ROM is FAB!!!