Database Info

Always bootloader screen

Hi, I've a vodefone v1240 (HTC Tornado), i've tried to flash wm6 flash to it... but... i haven't super cid unlock... the flash is ok but phone always star in muticolor screen (botloader screen), i've tried to flash a lot of flashes but always get invalid vendor id or "only upgrade"... i've tried too with TyphoonNbfTool to edit nbf and change vendor id.. but always get the same mensaje ("invalid vendor id" or "only upgrade")...
How can i recover my phone? :S
Thanks
Sendoa

Determine your original CID first, to do this type:
Code:
info 2
into mtty or teratermpro and paste the output in the thread
Phil

Ahh, there you are ! Are you or duke_Stix still planning to cook some newer ROMs or remove bugs from the existing one ? We hardly see you guys around there days

i get this... what is the original CID? ¿?
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3CE40000 Bytes
HTCSVODA0504 㱍dHTCE
Cmd>

@anandoc: I've been fairly busy lately what with Jury Service etc but I've got a beta version in progress
Changelog:
HTC Task Manager inc
HTC File Manager inc
Application Unlocked
Fixed WiFi
HTC Comm Manager inc
Removed Wireless Manager
Removed Debug Apps
Removed Marketplace
Removed Office
Removed Voice Command,
Removed Windows Update,
Added Bluetooth DUN support for TomTom compatibility
Added Bluetooth FTP protocol
Extra's (as a separate download)
Office
MMS (semi working)
HTC Clear Storage
Jeodek Java
Button fixes
xT9 (for those who prefer it over standard T9)
xT9 lang packs (split into separate languages)
TCPMP
wm5torage
VoIp
Localisations:
Polish
Czech
Russian
However at the moment I'm having issues with initflashfiles.dat, once these are sorted, it will probably be released the same day.
Back to the topic:
Ok, using typhoonnbftool v0.41 open up a tornado nbf (wm6 or official, it doesnt matter) and then edit the header data so that the Operator field reads:
Code:
VODA0504
That is your original CID
Then save the nbf and flash it to your device
Phil

done but...
Hi, i've done but... always get a "only upgrade"... only let me to reflash wm6 flash.. but it always return to bootloader screen :S what am i doing wrong? :S
Thanks anyway
Sendoa

Try adjusting the version numbers to something ridiculous like 99.99.99.99 as well
Phil

jm012a9749 said:
@anandoc: I've been fairly busy lately what with Jury Service etc but I've got a beta version in progress
Phil
Click to expand...
Click to collapse
Hey Phil, Thanks very much for the update ! Your hard work is much appreciated here !!

Me too
I'm having the same problem as Sendoa. I flashed the WM6 ROM to my 8310but after 100% completion, the phone re-started in bootloader mode.
I can flash it again with the WM6 but the same thing happens each time (bootloader mode). I've tried to flash with several other ROMs but each time I get the "Invalid Vendor ID" error before flashing begins.
I've tried the Typhoonnbftool tool to change the header as suggested earlier in this thread but without any success. My CID is 'DNG_0501'. I'm still stuck in bootloader mode.
I'd appreciate any assistance.
Thanks,
Straker.

Sorted
Sorted. Found another ROM (the fifth I've tried) that would flash without the 'Invalid Vendor' message. It let me get back to a standard WM5 setup.

Solved
Thanks to all
I flash it with a cingular flash with version changed to 79.79.79.79 and operator changed to VODA0504, and work again.. then i've unlock the cid and flash wm6 flash and it is working with it
Thanks again

Wow, that's cool, means I can flash my phone to WM6 without voiding my warranty ( I still got 5 months left )

lomanasq said:
Here, here they are:
cancer awareness ribbon
Click to expand...
Click to collapse
ban this MOTHA F**&&

Straker said:
Sorted. Found another ROM (the fifth I've tried) that would flash without the 'Invalid Vendor' message. It let me get back to a standard WM5 setup.
Click to expand...
Click to collapse
where did you get your flash from?

typhoonnbftool is creating only 1kb file of nk.nbf
Hi,
I have the new typhoonnbftool got it from sourceforge when i try to edit headers of a Imate rom to make it for xpa swisscom v1240 with the CID "VODA0505" i get only 1kb nbf file i try lots of thinks but no luck at all.
kind regards
Fakbrenjeri

Similar problem
I've used Typhoonnbftool to change header, but the resulting file is only ever 1kb or smaller! What am I doing wrong?

Small nbf
Straker,
Where did you get the rom that worked?

timwb said:
I've used Typhoonnbftool to change header, but the resulting file is only ever 1kb or smaller! What am I doing wrong?
Click to expand...
Click to collapse
use typhoon tools 0.4.1...
ftp://ftp.xda-developers.com/Uploads/Smartphone/Tornado/Shipped_Complete_Updates/I-mate
use the rom from here..

Stuck on BootLoader
I there!
I've tried everything that I could find here and still no luck...:-\
I've an SPV C600 and when I upload the Imate ROM it stays stuck on the BootLoader.
It only works if I upload the Orange Upgrade ROM...
I can't SuperCID it, since no app as worked till now...
What can I do?
Thank you!

try this:
http://forum.xda-developers.com/showthread.php?t=285344

Vox bootloader

Inspired by some threads in the Hermes and Trinity forums I started to explore the VOX bootloader. You can enter the bootloader by pressing the camera and power button at the same time. You see the tri-color (red/green/blue) bootscreen which shows the bootloader and CPLD version. In connection settings of activesync uncheck "allow USB connections" and connect PC and Vox with a USB cable. The PC will recognize the Vox and install an interface driver.
You need the MTTY to talk with the bootloader and send it commands. The Hermes wiki provides some good information and also has a link to MTTY:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Unfortunately the Vox bootloader (v1.16.0000) doesn't display help information. The first command you should enter is password. I found a password for Trinity and Hermes which also works for Vox:
password BsaD5SeoA
Here are a couple of other commands which work: emapiWlanEERW, emapiInit, emapiWlanMac, emapiPwrDwn, emapiRead, emapiTest, emapi, cpldver, DumpReservoir, CheckImage, calcrccheck, getdevinfo, ruustart, ruurun, progress, wdata, password, mbr, set, atcmd, ResetDevice, BTRouting, BTTestMode, SetDebugMethod, IMEI, ls, lnbs
I would like to find a way to dump the SPL and ROM to SD-card or to PC. I tried a couple of things (r2sd, d2s) to no avail.
Anyone else some ideas?
Update1
I got stuck in the bootloader and luckily found how to boot into the OS again:
http://forum.xda-developers.com/showpost.php?p=1094479&postcount=11
password BsaD5SeoA
ruurun 0
ResetDevice
Update2
I discovered the 'ls' command. Afaik it allows to dump the rom parts like SPL, IPL, splashscreen when the device is CID unlocked. My unbranded S710 is SIM unlocked, but unfortunately not CID unlocked. When I issue 'ls' there's a "not allowed" error

Update3
I found a 'good' VOX ROM upgrade (the ones on the XDA FTP are all corrupt): RUU_Vox_HTC_WWE_1.15.405.2R4_4.1.13.37_02.83.90_Ship
Another upgrade ROM is the Dopod:
RUU_Vox_DOPODASIA_WWE_1.19.707.3_4.1.13.37_02.83.90_Ship
I used NBHextract.exe to extract both ROMs. The SPL bootloaders are attached.
NBHextract shows following info for the 1.15 Vox ROM upgrade:
Code:
Device: VOX010100
CID: HTC__001
Version: 1.15.405.2
Language: UK
Extracting: 00_IPL.nb
Extracting: 01_SPL.nb
Extracting: 02_GSM.nb
Extracting: 03_MainSplash.nb
Encoding: 03_MainSplash.bmp
Extracting: 04_OS.nb
and this for the Dopod upgrade:
Code:
Device: VOX010100
CID: DOPOD001
Version: 1.19.707.3
Language: USA
Extracting: 00_IPL.nb
Extracting: 01_SPL.nb
Extracting: 02_MainSplash.nb
Encoding: 02_MainSplash.bmp
Extracting: 03_GSM.nb
Extracting: 04_OS.nb
Update4
I managed to back up my S710 using itsme's "bkondisk" tool and "prun" from his itsutils suite here and here. Copy bkondisk.exe to /Windows on your device.
After running this on your PC
Code:
prun bkondisk.exe "\Storage Card"
following files are created in \Storage Card and a log file "bkondisk.log" in \
Code:
bk_00_0000.img - IPL : ONBL1 + ONBL2
bk_02_0005.img - GSM + splash + gsmdata + simlock + serialnrs
bk_03_0025.img - OS
bk_06_0001.img - SPL
bk_08_0205.img - userfilesystem
I compared a couple of these .img files with the .nb files extracted by NBHextract from an official RUU. The IPL and SPL look quite okay, but the OS is mapped totally different. So don't think you can just rename for example bk_03_0025.img to OS.nb in order to have a flashable file !! I have attached my dumped SPL which is version 1.16
Next mission is to find a 'good' (not corrupted) version of the RUU_Vox_HTC_WWE_1.15.405.2_4.1.13.37_02.83.90_Test.exe ROM upgrade. See this Excalibur thread. I think the same applies to S710
Update5
With Dark Simpson's htc rom tool here it is possible to create a flashable image file from separate .nb files. There is also Dutty's good NBHtool 1.1 yet, but so far I haven't tried it.
What we still need to have for flashing unsigned ROM images is a SSPL. See here and here.
Alternatively we need a so called Update SPL (USPL) which unlocks CID and then allows flashing any rom to your device. The version for the ELF created by the brilliant moderator pof can be found here. Since the ELF is very similar to VOX, I will study it and see if I can use it to implement a SSPL (software SPL) which allows us to also flash any ROM, but does not require to flash an USPL. I think flashing IPL and SPL is a bit too tricky atm.

Take the Elf USPL, remove the RUU folder (to be sure you don't flash anything by mistake), in the LOADER folder change the .nb file for a Vox bootloader (different version than the one on your device) and use the same name for the .nb file, then run elf-uspl.exe on your PC.
If elf & vox are so similar, this should jump to the bootloader you've placed in the LOADER folder, to check it disable activesync usb connections and go into bootloader with mtty. Do an "info" command or whatever identifies that the bootloader you're seeing is the one you've placed on the LOADER folder and not the one actually on your device.
If you succeed in loading a custom bootloader I can help you with the don't check cid / don't check signatures... patches
Good luck!

Thanks for replying pof. I did as you said and tried it with spl 1.15 (whereas 1.16 is flashed on my S710). First I went through step1 and then went in to step2 where at 75% the screen got blank and it rebooted the phone in my native bootloader 1.16 RUU mode. I suppose that's not what we wanted to see?

Where did you find RUU_Vox_HTC_WWE_1.15.405.2R4_4.1.13.37_02.83.90_Ship? Do you have a link?
Thanks

I found it here:
http://www.leaf.co.za/Members/Member Services/Manage My Profile/

Cant Find The Bootloader For The Life of Me
Tried:
"You can enter the bootloader by pressing the camera and power button at the same time. You see the tri-color (red/green/blue) bootscreen which shows the bootloader and CPLD version."
No Luck. I must be thick. Its gotta be just that easy... but...
The S710 simply boots into my home screen.
Can someone PLEASE post a (little) more detail about how to boot into the bootloader on the s710/vox?
THANKS.
Cheers.
** EDIT **
OK- Better bootloader entry instructions for SP noobs (like myself):
1) Turn device off
2) Unplug power/usb cable from handset
3) Press and hold camera button
4) Plug power/usb cable into handset
5) Be amazed by Blue-Green-Red Bootloader screen.

Yeah, it won't boot in bootloader mode if the usb cable is connected. Well, it's sometimes better to find out things all by yourself
Besides, I don't think anyone other than myself is researching this stuff on Vox. Too many ordinary users and nearly noone in to h*cking.
You don't have 1.04 on your phone by any chance?

RE: older bootloader
No joy.
Sorry.
Its 1.15
My SP has vanilla mods.
Its just out of the box the last 4 days in NYC!
The phones not even available AFAIK in the US yet-- except special order.
Got mine in London last week.
Still working out the kinks.
BTW:
Im looking for info/docs/someone who has forced GSM codec through WM6 to this handset through Asterisk LOCALLY-- Asterisk SIP logs show successful codec negotiation and initial start of audio delivery-- but the stream pukes out on my handset immediately-- ideas? Im begining to think it may be a cpu issue. Thanks.

850mph said:
BTW:
Im looking for info/docs/someone who has forced GSM codec through WM6 to this handset through Asterisk LOCALLY-- Asterisk SIP logs show successful codec negotiation and initial start of audio delivery-- but the stream pukes out on my handset immediately-- ideas? Im begining to think it may be a cpu issue. Thanks.
Click to expand...
Click to collapse
Yeah saw that. I don't think it's a CPU issue, could run GSM codec just fine on a stone old iPaq. Try trunning omap overclocker and set it to 240MHz and see if it makes a difference. Keep using the SIP thread for any replies on this

POF's O2/Nova Solution
jockyw2001-
I suppose youve seen Pof's post #89 (dated 4-8) in the "ELF Update SPL (USPL)" thread which calls for running enable-rapi.cab (on O2 Nova) BEFORE elf-uspl.exe?
Id try it myself but want a few days of joy with my handset BEFORE creating a potential brick.
From my reading if the elf-uspl.exe makes it to 75% in stage 2 before white-screening-- you're close (well, 75% anyway.. wink!). Seems like Pof could have a couple of suggestions at that point. Maybe hell be kind enough to comment?
You're on it.. but I thought Id ask.
Cheers.

Heres something I am trying to work out-- even after many hours of reading:
I understand that there is an exploit in the 1.04 bootloader which can potentially bypass CID and Certs when flashing a new ROM image on both SPs and PPCs..
I also understand that bootloaders 1.09+ cant be downgraded.
So am I right in assuming that potential VOX ROM-chefs have at least ** TWO ** potential paths to solving the bootloader issue:
1) Find a 1.04 bootloader **AND** a tool which will load it successfully
-- Then use the exploit (which I read about-- but cant find) to flash the ROM
-or-
2) Find a way to Flash **ANY** bootloader onto the vox with elf-uspl.exe
-- Then (keeping our fingers crossed) elf-uspl.exe can be patched to defeat the CID&CERT issues with the vox
Now heres the question:
I am right in assuming that we **DONT** need to find a way to flash **SPECIFICALLY** the 1.04 bootloader onto the ROM **BEFORE** we can take advantage of a patched elf-uspl.exe?
Is that correct?
Cheers.

Oh yeah.. AM I right in assuming that the WM5/6 bootloaders are EXACTLY the same code (except for dated revs) across all WM SP and PCC devices-- sort of like the ability to install grub or lilo on **ANY VENDORS PC** no matter what OS or eventual Software Packages end up on the box?
Looked at another way:
When they talk about the 1.15 bootloader in the Blue Angel Board they are talking about the EXACT SAME 1.15 bootloader in the VOX board?
I mean, I know this is gotta be the case but I need a little reassurance here-- As Im still a bit confused on why PPC software should run on SP devices-- even understanding that they use (generally) the same subset (WM5/6) of the CE5/6 API-- But have different CPUs.

850mph: cool to see there actually are brothers in arms
I've tested pof's USPL extensively, but haven't got it to work (yet).
Actually you need to run enable-rapi.cab only if your phone isn't yet application unlocked, i.e. if it doesn't allow to run unsigned apps. Mine is application unlocked so I can skip that step.
The next step is to load a modded SPL in RAM at physical address 0x10000000 and to run it. Once this modded SPL is running another modded SPL can be flashed.
I've tried to load an unmodified SPL in RAM (e.g. SPL 1.15) and to run it. This can be done with following 2 steps:
1) psetmem.exe -f -p 0x10000000 spl.nb
2) run haret.exe on device (can use cecopy & cerun); cerun -b CE:\haret.exe
Note: haret.exe is a linux kernel loader which was modified by pof to run a USPL from 0x10000000
What happens is that my phone reboots into the stock bootloader (SPL 1.16) in RUU mode. I have to use MTTY in order to boot the phone in WM again (see post #1 and #2 in this thread).
Actually I think haret.exe does run the SPL 1.15 which is loaded in RAM, but that at some point the code resets the device.
I'm quite sure we can run a specially prepared USPL or SSPL which allows flashing another specially prepared SPL such that the device is effectively CID unlocked which again means that any vendor's firmware can be flashed. I also think we don't absolutely need the SPL 1.04 for that purpose.

This is good info.
I see what you are trying to do now.
Im gonna take some time to get up to speed on Dumping/Reading/Flashing from the Trinity Hermes and Elf pages. Until then Im afraid Ill be of little use.
Until now Ive strictly been a Linux/GCC-guy. Im tempted (but not convinced) that I want to take the time to learn Microsofts WM5/6 IDE. Its a time issue (obviously).
But I will spend some time on the whole S710 ROM-cooking (and bootloader) issue this week. It looks manageable.
I see you have basically been mixing and matching the various ROM cooking tools-- including using Msofts CE powerToys. Is there no single suite (besides the ImagefsTools) which you can recommend I look at first (With the understanding we need to solve the bootloader issue specifically for the vox first)-- I see various kitchens for various devices. Do any of them see plausible as a starting point for an HTC/Vox kitchen suite?
GOOD LUCK.
Cheers.
** EDIT **
I REALLY think the S710/S730spec are GREAT devices-- couple of minor issues-- but just fantastic form-factors.

new in the sandbox
Hi guys,
I just got my XPA 1415 some days ago (for info, it's just the same than the others (HTC S710, SPV E650 and Vodafone V1415, VOX, ...) but from Swisscom (Swiss provider).
I've been reading around and found this thread that was the most related. I actually tried to use the techniques provided by jockyw2001 with no luck.
Doing a prun bkondisk does not work, neither any of the itsutil tools. I do think that my device is somehow protected, but I've no clues how to proceed next. I'm going to continue searching, but if any of you has an idea, it's more than welcome.
If I manage to dump that *damned* ROM, I'll make it available...
I've currently (on booloader ONBL 1.23.0000, SPL 1.23.0000, CPLD 04)
Cheers,
Nick

Nevermind...
I think I've been able to proceed with the backup (I've used the Microsoft Security Configuration Manager) when I realized that my system (Windows 2003 x64) the tool was not working.
Which made me think that maybe the procread and the other prun bkondisk might also have been blocked by the x64.
I've tested on my laptop (regular XP) and it works fine... just FYI !
** EDIT **
I've also tested the ELF haret with a downoaded SPL and I got the same result as jockyw2001...
BTW, jocky, did you find a way to re-create a proper nh from the bkondisk end result (bk_##_####.img) ?

nwaelti said:
BTW, jocky, did you find a way to re-create a proper nh from the bkondisk end result (bk_##_####.img) ?
Click to expand...
Click to collapse
The IPL and SPL are useable. The radio dump called bk_02_0005.img is from offset 0xA0000 identical to the radio rom. The first 0xA0000 bytes are other parts, probably splash + gsmdata + simlock + serialnrs. The OS file seems not directly useable and must be reordered somehow. More interesting is the ROM reconstruction method described here. Of course first we need to be able to flash unlock the Vox. I think the SSPL is most suitable for this purpose, this may need some reversing of the SPL with IDA Pro.

Thanks for those info, I'll try to go in that direction. Would be nice to find which one is splash, which one is gsm and the others below 0xA000.
I know we need to rev. SSPL. Don't exactly know where to start though I can't flash mine with any original ROM as Swisscom is not providing any.
BTW. viewimgfs gives me back a "packing DLL not found" (or some similar). Anyone had that also ?
I'll try to download IDA Pro...

It's below 0xA0000
I will do some testing again with the Vox today. I will see if I can paint the screen with a few instructions @0x10000000
I think I can not just run the SPL on VOX in the same way as you can on the ELF. The IPL on the VOX is 128kB, whereas on ELF it is only 2kB. So I think I will have to patch the IPL and run that first. I'm afraid that it will take a bit more time. Basically it will then be a SSPL (search forum for SSPL and user 'des') with both IPL and SPL patched and running in RAM.
But maybe it is also possible to patch just the SPL, because it could be that the default action initiated by IPL is to reset the device in RUU bootloader mode.
Given some time it can all be done I'm sure

[REF]Wiki entry: HOWTO - Backup your Elf or Elfin ROM - dump and restore

Edit:
moved the HOWTO to the Wiki:
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
feel free to update/correct the Wiki if you find failures, bugs or updates
It worked for me - but I cannot guarantee that you don't brick your Touch.
So be warned.
Thanks to dsixda for updating the Wiki for Elfin
MOD EDIT: See this post in case the Wiki is not working:
http://forum.xda-developers.com/showpost.php?p=7662245&postcount=214

Will ruu_signed.nbh be suitable for traditional chinese?

Works perfect for me, now a way to rebuild my os with les software

With this method can someone build a french custumized ROM like the 62MB+ and 4MB PagePool one ?? It will be awesome !! Nice work r0p3!! It's workiiiiiiiiiiiiing !!

Works fine for me, thanks for the good guide
Greetings Denis

Now ... How to modify it ??
P.S : Can I include the extRom when i build the ROM with the OS?

I got my work cut out this week.
I'll try this big Up
(it's a bit more clearer then wiki info, maybe you can update it)

Noonski said:
I got my work cut out this week.
I'll try this big Up
(it's a bit more clearer then wiki info, maybe you can update it)
Click to expand...
Click to collapse
Wiki updated:
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom

r0p3 said:
Wiki updated:
http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom
Click to expand...
Click to collapse
Can I dump my touch with all installed programs, cooking a complete rom including installed programs?

No - that's not possible I Think.
But you can use sprite backup.
It worked perfectly for me when I flashed the ROM back.
But keep in mind that it only will work correctly on the same language of the ROMs.

r0p3 said:
No - that's not possible I Think.
But you can use sprite backup.
It worked perfectly for me when I flashed the ROM back.
But keep in mind that it only will work correctly on the same language of the ROMs.
Click to expand...
Click to collapse
I have Sprite Backup, but after flashing the device with the same rom, the restore didn't work, so I had to install the programs again.

eefurt said:
I have Sprite Backup, but after flashing the device with the same rom, the restore didn't work, so I had to install the programs again.
Click to expand...
Click to collapse
Here is a trick I have used for quite some times with Sprite Backup 5.1
Sprite Backup version 5.1, version 6.02 is more fancy, 5.1 is good enough.
1. Do a full backup, make sure option Create Self Extract Exec
2. Hard reset (optional)
3. Flash new ROM
4. Run the backup file, make sure the Upgrade Mode Restore Option is Check.
5. Kneel down and pray (optional, or take a cup of coffee).
SKtools is handy.
Step 4 is most important. When it asks you for the upgrade fine, Click None. Minor cleanup unavoidable but heck a lot better than of re-install all the softwares.
Sometimes you may find the machine run slugglish by doing that. I am not sure why.
You may flash the new ROM, re-install all the softwares, see if the machine run faster, but few days later, you will feel it run slugglish. I am not sure why. (The laptop runs runs much faster than once I bought it and take it home and installed with applications.)
So I just keep buying new machines... hahaha

holy moly.
going great at 10% of flashing.
but i feel confident the tute was on the spot.
muchos gracias.
And yes you are right (you didn't say it but you must have thought it), I could have added it myself to WIKI. But just had to try it myself first off course.
And am i right in believing i could have allready replaced some of the graphical files in the dumped "ROM" directory?
Or is it to dangerous at this change because the file size needs to fit?
92%
100%,... first boot screen passed........second boot screen passed....
The audience is in Awe. It works.
Next step, getting familiar with hypercore kitchen.

Thanks for this tutorial.
Now i can safely backup my Dutch rom and test some custom ****..
Regards,
Schmia

And am i right in believing i could have allready replaced some of the graphical files in the dumped "ROM" directory?
Or is it to dangerous at this change because the file size needs to fit?
Click to expand...
Click to collapse
Do NOT change files in the dump directory without proper tools!!!
You will mess up the ROM
When you have a look at the dump directory there are some info files with data for the places in the ROM which need to be recalculated.
Noonski said:
holy moly.
going great at 10% of flashing.
but i feel confident the tute was on the spot.
muchos gracias.
And yes you are right (you didn't say it but you must have thought it), I could have added it myself to WIKI. But just had to try it myself first off course.
92%
100%,... first boot screen passed........second boot screen passed....
The audience is in Awe. It works.
Next step, getting familiar with hypercore kitchen.
Click to expand...
Click to collapse
Thanks! I'm happy that it worked - nice feeling - eh?

Dumping Elf WM6 Italian version ROM
Before trying to put new Rom images, i would like to backup the original one.
I followed the (simply) tutorial, but i'm confused about this step:
"need the ruu_signed.nbh from valid update (extract with winrar)"
Which file do I need?
I don't understand why I need a valid ROM when I'm trying to dump a Rom from my Elf
Can I use an other language ROM version (English, Dutch....) or is needed only an Italian one?
Thx in adv and sorry for my poor english
Ciauz

junkyarddog said:
Before trying to put new Rom images, i would like to backup the original one.
I followed the (simply) tutorial, but i'm confused about this step:
"need the ruu_signed.nbh from valid update (extract with winrar)"
Which file do I need?
I don't understand why I need a valid ROM when I'm trying to dump a Rom from my Elf
Can I use an other language ROM version (English, Dutch....) or is needed only an Italian one?
Thx in adv and sorry for my poor english
Ciauz
Click to expand...
Click to collapse
you need this as a "shell" or "template" because the .nbh files are made in a way that cannot be recontructed (so far I understand - correct me if I'm wrong).
And yes you can use an ROM with another language. I took the Australian ROM - look at the first paragraph "files you need"
This is usually a .exe file that you can extract with winrar (or winzip maybe)
P.S.: your english is not so bad

r0p3 said:
you need this as a "shell" or "template" because the .nbh files are made in a way that cannot be recontructed (so far I understand - correct me if I'm wrong).
And yes you can use an ROM with another language. I took the Australian ROM - look at the first paragraph "files you need"
Click to expand...
Click to collapse
Thx very much!!!
All worked fine, flashing the "new" dumped rom worked perfectly, I'll put it on FTP to make it avaiable to other users.
Ciao

r0p3 said:
Do NOT change files in the dump directory without proper tools!!!
You will mess up the ROM
When you have a look at the dump directory there are some info files with data for the places in the ROM which need to be recalculated.
Thanks! I'm happy that it worked - nice feeling - eh?
Click to expand...
Click to collapse
Pfew thanks, nice knowing this. Iwas allready worried that it would need correct file info.
junkyarddog said:
Thx very much!!!
All worked fine, flashing the "new" dumped rom worked perfectly, I'll put it on FTP to make it avaiable to other users.
Ciao
Click to expand...
Click to collapse
Don't upload to XDA. I've seen some directories with full roms on FTP. But this is no longer allowed and files will be deleted.
XDA's allready been in trouble with MS about this. So either use third party file sharing or privatly owned FTP.
r0p3..
So to get the radio and SPL do i need to redo first extraction but then for these files? Or are these IPL/SPL?
| 3.06M (0x30fc00) Part00
| 3.06M (0x310000) Part01

Noonski said:
r0p3..
So to get the radio and SPL do i need to redo first extraction but then for these files? Or are these IPL/SPL?
| 3.06M (0x30fc00) Part00
| 3.06M (0x310000) Part01
Click to expand...
Click to collapse
I don't know yet - I still have to dig in the wiki about that.
It's very dangerous in this area - if you mess up IPL or SPL your baby is usually lost forever. I don't mind about those as long pof's USPL works beautiful.
Radio might be not so critical. But 2.97. is already available - so it would only be for the fun of it

O2 XDA Mini S (G4) Not flashing

Well, i've flashed the X50v and HTC Touch Elfin before, however I seem to be having some problems with the Wizard. I'm trying different ROMS and none seem to be working. Once a flash appeared to go through correctly, and the splash screen at startup was changed, but it still booted into WM5.
Now even though it is CID unlocked, it says that the RUU is out of date and won't update the phone.
IPL is 2.21.0001
SPL is 2.21.0001

have you downloaded and flashed with Wizard_Love_2.26.10.2_WWE_Novii_CF2 first if not then do. using the SoftSPL-V0.1 just extract then copy over the nk.nbf file after which do the same for the wm6 rom you wish to use. i advice using the TNT.20273_Professional_Wizard_HTC_Home_FREE rom or the TNT.20273 Professional Wizard rom. either are good roms.
i have the same phone and it worked a treat

Obsidiandesire said:
Well, i've flashed the X50v and HTC Touch Elfin before, however I seem to be having some problems with the Wizard. I'm trying different ROMS and none seem to be working. Once a flash appeared to go through correctly, and the splash screen at startup was changed, but it still booted into WM5.
Now even though it is CID unlocked, it says that the RUU is out of date and won't update the phone.
IPL is 2.21.0001
SPL is 2.21.0001
Click to expand...
Click to collapse
How do you confirm its CID unlocked,as G4 device cannot be CID unlocked and with its present IPL/SPL it isn't even HardSPL ?
A G4 phone can only be upgraded to wm6,either through SoftSPL or HardSPL,you can read about them in the G4 sub forum posted as stickies.

Thanks for the help guys, for some reason the hardSPL wasn't working, but now I have 6.1 on my phone! I have another problem, however which I'm going to create another thread for later today, here it is if anyone see's this:
Since upgrading to Winmo6.1, my keyboard layout has been broken. I have an O2XDA MiniS, so it's a UK phone.
Here's the layout I should get:
QWERTYUIOP
ASDFGHJKL (Del)
(cap)ZXCVBNM(up)(Enter)
(Dot)(Tab)(Windows)(Ok)(Space)(period)(left)(down)(Right)
And with dot-shift (Don't know the actual term)
1234567890
[email protected]#$%&*() (Del)
(cap) - _ € £ + = ; : (enter)
(dot) ~ (Win) " (sym what does this do?) , ' / ?
This is what I Get
QWERTY is exactly the same, its the symbols with Dot-Shift that have changed
123456790
[email protected]#$%&() (del)
(cap) ` -_+ = * ; : (Enter)
(dot) (Tab[Should be ~]) (win) " , ' / ?
I have tried the Et9 cab file which didn't seem to do anything, let alone work.
There was a post I saw which had a link to a rapidshare file which has now expired.
Some people have tried registry settings, that hasn't worked for me.
I've spent the last hour searching, this keyboard means a lot to me.
I bought this phone for my girlfriend but ended up keeping it since I love the keyboard, sometimes do Python scripting on the go, editing word docs + email browsing is easier. So she now has my Touch Elfin (which is newer)
So yeah, i'll pretty much copy + Paste that into a new topic if this doesn't get any replies by say 8PM GMT?
I don't really like making hundreds of new topics for every little problem I Have. Otherwise there'd be one for Opera + Hardware buttons (Plus the internet button on HTC home screen)
one for it not staying in landscape mode when the keyboard is down, and one for my myriad of MiniSD card troubles

sorry forgot about this issue about the keyboard its simple to put it back to uk even if its a pain.
step 1 open regedit
step 2 open HKEY_CURRENT_USER
step 3 open ControlPanel
step 4 open Keybd
step 5 select Locale and change it from 0409 to 0809
and now everything should be in the right place
anything else feel free to ask

Change the startup picture

Hello
I used the Icy ROM for my Herald and installed now another rom.
But when i boot the device i still see that Icy picture.
I would like to have no picture or another.
how can i change it?

Search before posting.
http://forum.xda-developers.com/showthread.php?t=389830
http://forum.xda-developers.com/showthread.php?t=224877
http://forum.xda-developers.com/showthread.php?t=286812

I didn't read everything but most of them say that i have to change the picture in the .nbh file and set up the device again.
I'm not going to do that... It's too complicated.
Thank you anyway