O2 restoring original boot rom - JAM, MDA Compact, S100 Software Upgrading

Hi,
ok I'm a lil bit desperate right now
I got my XDA II mini today and saw an update on the o2 site and started installing it .. only to notice that it was for the XDA II and not the mini. So, this thing killed my boot rom. I then found your guys site and installed GER_11201_150_11210 RUU package which went fine ... but well, that thing is for T-Mobile and I don't want my xda to be pink
So, I was looking through the forums to see how I can get my original image as I couldn't find an O2 RUU package. So, I tried the ntrw.exe write to SD card (512MB) thing. Inserted it in my xda, did a soft reset and then a hard reset. In the display serial shows up... but I never get it to ask me Press Power to Flash ...
so a) what am I doing wrong an b) how do I get the german o2 image back on my xda?
thanks

ok I understand now why the SDCard update doesn't work .. because I didn't have a chance to backup my boot rom :/
Where can I get a GER o2 boot rom installer that works on my device?

alright, I installed the 1.12 WWE exe package with the help of MaUpgradeUt_noID.exe
... copied the existing boot rom to sd card, and extracted it from there. Overwrote the first 416 bytes in O2_GER_1.12.01_big_storage.nb1 with those of the extracted image.
Now, it's flashing with the SD card ... I'm confident that it'll work, we'll see

ok, the flashing worked ... but O2_GER_1.12.01_big_storage.nb1 is not really O2???
So, where do I get the real o2 boot image?

As much as i know it´s included in the ExtRom....
You can install it manually.
Don´t know who, but someone uploaded "Promasters Autoinstaller 1.5.zip" to the ftp. Very nice application. I would suggest you try/use it. There is an Option to change the bootlogo...
Regards
Stefan

you have to install the extended rom manually!
check the ftp

Related

Please help! My S200 has died

I installed the latest LSVW ROM a few weeks ago and I was very happy with it.
Today I got a crash of my S200 (run out of memory). My S200 gets stuck in a totally white screen after the QTEK logo has been disappeared during a soft reset. So I have to do a hard reset. However, after the hard reset my S200 get stuck in the red-green-blue colored screen (bootloader) and will not go any further.
Can somebody help me bring my S200 back to life?
I read some articles about flashing from the bootloader, but all the ROM updates cannot find my S200. They really need a ActiveSync connection and I am not able to make one....
Can somebody please help me?
ehm, when you can get into bootloader you should be able to plugin your device and do an update via usb.
However, you should do this from an official rom. Not a rom based on PDA mobiz or something, that needs a guest activesync connection afaik.
To quote myself (for instructions):
erm... well you could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found on ftp) to upgrade (or you download RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe and take the ROMUpdateUtility_NoID.exe from that using WinRAR, but it's wasting bandwidth a bit ).
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there are some other folder (prophet -> WWE), when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
Hope this might help you out.
Very weird btw the device just crashed itself and now you are stuck in bootloader! Doesn't sound too good
Did you heavily overclocked it or something?
RaptorRVL tahnk you very much for your support, but it dis not solve my problem.
I tried it several times. I had a lot of 260 errors and at last I got a 320 error. So it seems that there is something terribly wrong with my device. I think I have to return it to QTEK.
I did not overclock my PDA, so that could not be the cause of this. I was just driving home using TomTom Navigator and the error message 'Out of memory' (error message from WM5 not form TTN) appeared on the screen with an OK option. I pressed the OK button (only thing I could do), the S200 soft resetted itself and got stuck in the totally white screen after the QTEK screen with the version numbers.
Sounds like faulty hardware indeed, perhaps bad memory or a bad motherboard. All the stuff is intergrated anyway, so they just throw the old internals away and get some new stuff in there for you.
Hope they fix it fast!

how to flash extendedROM before Warranty return

Hi I'm thinking of returning my m600 to the Orange SAV because of a speaker problem.
I tried a wm6 ROM and then downgrade (with difficulties) to my original wm5 rom , then found a way to put original orange bootloader screen, but the extendedROM is still the PDAMobiz Prophet WM6 (and there is no more installation process at hard reset like when I was using wm6), and I need to put the one which was furnished by Orange (I have a backup of it using awizard).
I succeed in unhidding the extendedROM2 folder (thanks to another post), then delete the PDAMobiz files and put the Orange one, but after hard-reset nothing install, and when I reveal the extendedROM2 folder PDAMobiz files reapear.
So I hope there is another way to restore my orange content.
What about the warranty if it has been flashed and then downgrade and make it as the original one?
thank you for helping a Newbie
Strange Official ROMs include extended_rom that are written upon flashing process. Are you sure you used an official?
Else...
You can try to use my software (WST - check signature) that, although made for wizard, i believe will work.
Best thing is to use the READ ROM feature before flashing to be sure that the addresses are the same (should result in a 10MB file that can be opened with Winimage)
The other way is to get pdocread.exe and itsutils.dll and get the extended rom partition handle and then use pdocwrite to flash an extended rom.
Last option is to get an official RUU and extract the nk.nbf and then from it extract the extended_rom chunk. Then make a nk.nbf with only that chunk and pack it back into an RUU exe.
your choice
You flash your Orange Rom wrong!
If you use a Original Firmware ... all are overwriten! Ext Rom too!
Don't worry, the first thing Orange do when the phone reachs their labs is to flash it with the official rom, test it and send it back to another customer if it works.
I think even with your pirate wm6 rom you would have met no trouble but I'm quite sure they won't even notice you changed the ext-rom.
If you really want to be sure, just unlock the extrom, delete the content and relock it

Update ROM from SD Card for Vox??

Hi there..
Is there a ROM updater/image for the Vox that can be loaded from the SD card (through bootloader or not) ?
It seems like usb connection on my Vox died. Can't get it to connect to anything and I've tried everything so far.
I can't upgrade/flash the ROM as I have no usb connectivity whatsoever.
It would much appreciated if somebody can point me in the right direction.
Thanks
Leo
Format your card to FAT32
Rename an nbh-file from the official rom package (can be opened by winrar) to vox0img.nbh and copy to sd card, go to bootloader and follow the onscreen instructions.
Erofich
Thanks for the quick response.
I'll try that and let you know how it went. Hopefully I can get my vox connecting again.
Cheers
Erofich
Thanks, got the ROM upgraded from the SD card through the bootloader. worked like a charm.
Didn't fix my problem tho. Still a brick when it comes to connecting to any pc.
Hm we should add that version of flashing to the Wiki. If anybody does it again, could you take some good pictures when you're in the bootloader and the whole process there?? PLease
How do you enter Bootloader without using USB, I want to flash the last version of WM6.1 that Dr. Gonzo posted.
Roland
Turn off phone, hold camera button and insert power cord.
You're probably going to need to flash USPL first, so this won't work with an unsigned ROM (such as New Guava).
h4waii said:
Turn off phone, hold camera button and insert power cord.
You're probably going to need to flash USPL first, so this won't work with an unsigned ROM (such as New Guava).
Click to expand...
Click to collapse
Thanks for the reply. I had flashed the USPL when I first started using New Guava. I found a way to flash to Dr. G's latest version of WM6.1 that he posted last night without using sd card flashing by using the one he had posted on the first page and renaming 5.nbh to windowsmobile6.1.hbh, copying it into the extracted folder and running RUU.
Roland
You don't need to download both archives dude, the only thing that changes is the specified NBH which is the firmware you're flashing, RUU will flash any properly blocked (and checksummed) NBH within it's directory.
I had previously downloaded the first archive as I had already flashed my ROM with the included nbh file, but could not my ROM with the new nbh file as there was no RUU with it and I could not work out how to get directly into the boot loader without using the USB cable to flash my ROM from my sd card, so used that method as a work around to flash my ROM.
Roland
frauhottelmann said:
Hm we should add that version of flashing to the Wiki. If anybody does it again, could you take some good pictures when you're in the bootloader and the whole process there?? PLease
Click to expand...
Click to collapse
There is nothing to it really, it's pretty much just a white screen with blue lettered instructions.
Unfortunately I'm hopefully not going to do it again soon. I got my sync issues sort of sorted through Bluetooth.
But if I have to flash again.. I'll take some pics.
Cheers

How to dump your original ROM and keep it ready in case of failures?

Hi,
If i have to keep my original ROM as backup to use in case of serious failures, like i am only able to boot up to boot loader and avoid INVALID VENDOR ID (294) error to reflash sucessfully this ROM. (without using USPL)
do i need to do:
1. create part00.raw, part01.raw and part02.raw using pdocread of exiting phone ROM
2. rename .raw files to .nb
3. run Dutty nbh tool and then???
What i have to provide in:
IPL, SPL, First Splash, Second Splash, OS, Ext. ROM, Radio, Device, CID Type, version, langauge, Signature?
4. Produce RRU_Signed.nbh and use it to flash with ROMUpdateUtility
Am i doing right?
Please help!
Thanks in advance
You really don't need to dump your ROM! Most of the official ROMs are available. Tell me your original ROM and I'll give you a link to it!
frauhottelmann,
I asked this because i came across this situation recently when i mistakenly upgraded my HTC S710 ROM with ORANGE UK latest ROM and in last it said corrupeted. After that i tried every things but it got only stuck at boot-loader.
From bootloader, i tried every ROM from FTP xda but everytime it was INVALID VENDOR ID or Corrupt ROM image. and worst part was; i could not use USPL.
If i would have my original ROM with me, i could have come out of this.
I had to pay some bucks in cash to HTC service and then i got it corrected. They simple put my original ROM in it, nothing else.
Thats why i asked if i have to dump my unique ROM to avoid INVALID VENDOR ID, how can i do this?
frauhottelmann,
Sorry to disturb you, can u help me on this?
So do you have an HTC S710 or the Orange version of it?
its HTC S710
And now the original HTC ROMs don't flash properly? I gues the problem was the orange ROM, if you don't flash ROMs other then HTC (or cooked - they don't use an own SPL) then this should not be a problem any more. If you flash a Orange ROM, you still have to do USPL first, because it's gonna say "No, this is no Orange phone" BUt then it still might screw up the SPL and your stuck. So just be carefull with flashing ROMs from an specific carrier.
you mean,
if i have original default HTC S710 ROM in my phone and if i try to flash with original HTC ROM like "HTC S710 ROM version 1.34.405.1" from boot loader then i should not get any error.
Also if i have Gonzo or your ROM or similar cooked ROM and try to flash with "HTC S710 ROM version 1.34.405.1" from bootloader i should not get any error.
if i have Orange or similar ROM and try to flash with any HTC ROM, failure everytime
If it is true, it would still give enough relief.
This is what I meant! The same would happen with a Vodafone or Dopod ROM!
i have the Vodafone V1415 (which is the same as the rest of the vatious Vox's) and i recently flashed an orange rom to it and it worked fine
before the orange rom, i had Mr Gonzos 6.1 v1.1, and before that, whichever one came on the device
ive never come across anything like that :S
admitedly after finally getting everything right (after various problems with different things) and the phone worked fine, i then managed to drop my vox onto a soft seat in such a way that it bounced off and the screen broke as it hit the floot
Original Htc S710 Bt Rom
frauhottelmann said:
You really don't need to dump your ROM! Most of the official ROMs are available. Tell me your original ROM and I'll give you a link to it!
Click to expand...
Click to collapse
Can you kindly show me where to download original BT ROM for HTC S710?
You will save me.
YOSEFE
I see. There is no response to my quest.
I now have to send my phone to my SP, to avoid my dead end experience, how do I backup or do a ROM dump for my original ROM?
Cheers.

RUU error (262) update error

Hello guys...
Iam not new, and i have already flashed my first(it was wasted not by my fault)KAISER, it was one year ago and i did it with HARDSLPv1, and lately added some new roms cooked by sakajati(respect)...
Yesterday i bought new one(but one year old) so i tried to flash him as well, i have used HARDSPL 1.93, and then i tried to put Sakajati"s 4th feb ROM, but i come across one big trouble, everytime i try to put it on i encounter the same RUU error:
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
what to do...????
i am very afraid that i destroyed my Kaiser...???
what it means that Wince is destroyed...
Please help me, i am desperate...
Iam not new,
Click to expand...
Click to collapse
But the solution could be found here (search)
If you see the tri color screen everythng is ok, just win mobile is destroyed. Try to flash a rom from your sd card
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
greganovak said:
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
Click to expand...
Click to collapse
Part of the problem is that 1.93 is a jump spl and should be used to upgrade to Hard spl 3.29 or 3.56, not as an spl on its own. You need to run jump spl 1.93 from your device and make sure you are connected to your computer, when you see the bootloader you need to unplug your USB, count to 10 and plug your USB back in then flash a hard spl to your phone! Again 1.93 is not a Hard Spl by itself, it is only a middle man to flash a Hard Spl.
I think the best would be to flash a stock rom at first, cause therefore you don't need an other bootloader. Then flash Hardspl (3.29 if you have a kaiser or 3.56 if you have a tilt) and then flash any rom you want
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
It realy doesnt make that much of a difference, I have a tilt and I use 3.29 and I would recomend it to anyone over 3.56 so flash either one, they will both work! And your english is great so no need to say sorry!
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
A Tilt is a At$T branded Kaiser, a TyNT II is a HTC branded Kaiser. Tilt has a different keyboard and OEM rom., only differences. People say use 3.56 if you have a Tilt because that is an AT$T Spl, but I use 3.29 on My Tilt and it works great so it doesn't really matter.
hey...
nothing seems to work...
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Then i flashed the HARD spl 3.29(have kaiser) via SD steb by step first with this instruction: http://forum.xda-developers.com/showthread.php?t=433835; and it dint go through
so i tried with this instruction: http://forum.xda-developers.com/showthread.php?t=420683
it didnt work either, they are the same I know(noticed later);
So problem is that i stuck at WHITE screen that says "LOADING..."
nothig else...???
finally i manage to load/boot the htc rom from xda-wiki site, but i have to chose another one
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Click to expand...
Click to collapse
Hey man, nice to see that your device rewakes, you can flash every rom from sd card, simply rename the nbh file to kaisimg.nbh than restart into bootloader and it will automatically take the one from the card
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
greganovak said:
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
Click to expand...
Click to collapse
Hi,
I couldn´t flash my Kaiser via SD at the first time and tried something that worked.
The SD´s are formatted in Fat16 usually, try to format to Fat32... It seems like a stupid thing, but worked for me.
Reagards and good luck.
SD must be formated FAT32, to work, also I sugest a smal card, 512 or something like that, SHDC usual doesn't work
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
greganovak said:
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
Click to expand...
Click to collapse
Yes, you still have a stock spl on there. It needs to be hard spl'd before you flash anymore. Check out the stickies at the top of the forum.
hi again...
Well, I respect the "rules" of forum, thats why i wouldnt ask for insructions that are already written(thanks for the authors) with that i mean stickys, because i read them, almost all...
But I still tried once again, and I came across the same thing, i stuck at 17% when loading RUU or if i choose the VIA SD i stuck at white screen with blue text saying (LOADING...)...
nothing else helps than loading the dafault ROM by HTC... as i already said once again...
if i manage to solve the problem i will be in touch; what do you thing about MTTY
Edit 1:
i have done everything as it says in the instruction, and just like some of you "replyed" me...
but i always stuck at 17%when loading RUU, when i flash it with SPL 1.56 or 1.93 i never get stuck at white screen it always apeare the mentioned SPLs nimbers and some other text in yellow but when i then load RUUs i stuck at excatly 17% nothing less nothing more
edit 2:
yupi....yupi
i made it...
http://forum.xda-developers.com/showthread.php?t=354061 here is my lifesavior...
those instruction were the one that helped my problem...
it is very nice to ba a part of this community....

Categories

Resources