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
Related
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
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!
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.
I have a Cingular 8125, I have flashed many ROMs and the last one is TNT 20273, IPL/SPL 3.08 and radio 2.19
Recently each time I have to soft reset it takes a very long time to reboot. It can be several hours.
I tried to downgrade to official Cingular rom but RUU doesn't work anymore, there is always a connection problem and it only makes a soft reset that takes hours to come back.
I tried also to force bootloader mode with camera button+reset, running enterbl.exe and disabling usb connection in Activesync but nothing worked.
Once it restarts it works fine until I have to reset but when it happens I have to wait hours to use it again.
I am desperate, I will appreciate any help or comment.
Thanks in advance
talvae
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
S.V.I said:
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
Click to expand...
Click to collapse
Thank you S.V.I., it s a G3.
Let me check if I understood, what you suggest is to use WST to flash a nb containing only ipl/spl 2.25?
If it is correct, do you think reflashing ipl/spl 3.08 could fix the problem?
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Nicely thing
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
I think it is so much process to reflash but its interesant to try dump original roms... i never heard it... it sound very cool. just try to reflash from begining like it never was unlocked... wizard love etc etc etc.
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
Thank you S.V.I,
I have extracted the IPL and SPL from the original 2.26 cingular rom using the last version of WST, I have four .nb files.
Now I have to write them to my wizard but I would appreciate some advise.
Should I write each file using WST? or nessesarily I should make one rom with only this blocks and write that file?
talvae
Hi guys,
I have a touch pro with a few issues (the same as everyone else) and I want to try a few things out in order to try and fix it. I just need to know I can revert it back to its original state if I need to...
This is my first Windows Mobile device, I have flashed hardspl to the device as the thread gives instructions on how to flash back, I'm just a bit concerned about restoring the original rom if I change it; The wiki has a few stock roms available, but it seems they include the SPL which I've read wont work correctly with hardspl installed. I've backed up the rom using pdocread, can I flash it back with pdocwrite without any issues? Obviously if I reconstruct it to flash back, it wont have the HTC signature so if I put the original SPL back on I will have a brick.
I'd like to mess around in the kitchen but need a way to revert it back to retail. How is this usually done?
Thanks.
Simply flash your chosen stock ROM (from the wiki as you pointed out). This will not overwrite your SPL. Hard SPL simply enables you to flash any ROM, stock or otherwise. There is a Stock SPL that you can flash for warranty purposes in post #1 of the HardSPL thread.
Caind said:
Hi guys,
I have a touch pro with a few issues (the same as everyone else) and I want to try a few things out in order to try and fix it. I just need to know I can revert it back to its original state if I need to...
This is my first Windows Mobile device, I have flashed hardspl to the device as the thread gives instructions on how to flash back, I'm just a bit concerned about restoring the original rom if I change it; The wiki has a few stock roms available, but it seems they include the SPL which I've read wont work correctly with hardspl installed. I've backed up the rom using pdocread, can I flash it back with pdocwrite without any issues? Obviously if I reconstruct it to flash back, it wont have the HTC signature so if I put the original SPL back on I will have a brick.
I'd like to mess around in the kitchen but need a way to revert it back to retail. How is this usually done?
Thanks.
Click to expand...
Click to collapse
Upload Part01.raw and Part02.raw somewhere and i will reconstruct for you into NBH file ready to flash
Cheers