Database Develop

Is there any tool to unlock the extended rom on XDA IIi?

Is there any tool to unlock the extended rom on XDA IIi? If there is please post.
Thanks,
Mike

I also would like this.
And mike, your picture of the XDA2s is the best modification i have ever seen for it

:lol: Thanks John

Trying to keep this thread alive, does anyone know of any tool yet.... that can unlock the XDA IIi EXTENDED ROM? If there is please post.
Thanks,
Mike

No bites yet. Come on any help out there. I need to unlock the XDA IIi extended rom.

same here and keeping this thread active... is there a tool (yet) for unlocking the xdaIIi extended rom?
Unhiding is no issue. Using ExtendedROMUnlocker.arm.cab has no effect whatsoever.

@epicus:
how have you unhid the extrom? care to share?

for unhiding the extended rom, when I got the phone I explored what was installed and found a file called loadvdisk.exe inside the Windows rootdir. When I launched it I noticed there was a directory 'Extended ROM' suddenly visible, however I could do nothing with it. I could copy data from it, but could/can not put anything inside it. Kind of useless rather, unfinished. If I can 'load a v. disk' then where is the use of it??
Attached is the loadvdisk.exe, I found no keys for it in the registry, so if anyone wants a go at it, feel free, it's loaded by the basic WM2k3SE ROM.
As to a possible question if it works on a device other then an Alpine... dunno , try it.
The issue remains, how does the Extended rom get unlocked? The known registry flag for the ExtROM is set to zero.

Try this
Try http://www.myehud.com/xv6600/cabs/ExtTools.exe
If that doesn't unlock it, and gives a hardware io control
error, try using a binary editor on the file.
Look for ReIrRaH and replace it with eNiPlA
(Harrier and Alpine backward with alternating case).
Perhaps SuperDave would be kind enough to release
a version where the password is input at the keyboard...
Ehud

Thank's for your tools. It seems that will be near a solution but it's not unlock, because ;
First : TREFFS_DOC is now profile for Storage
Second : ExtRom is Profile VDIS and use VDISK.DLL and not TRUEFFS.DLL that does not exist
Third : Allocation memory is different than other version of QTEK.
And finaly, NOT USE THIS TOOLS THAT LOCKED My STORAGE, I'm HAPPY. I TRIED HARD RESET WITHOUT RESULT
!!!!

changing roms on xda2i
Does anyone know how to avoid country error code on the alpine when upgrading or switching roms? Does one follow the same procedure as that for the himalaya, or can I use the upgrade utility (with no id) that I used for the himalaya?

come on !!! i need too!! please engineers!

what do u think about this :
http://www.smartphone4u.de/xda3/grundlagen/extrom_unlocker.shtml
i tried but fail !!it can't not run!!

I need it too,please help.
I can not read/write my Storage after hard reset.

I don't understand for developer what is difficulty.
Today all owner of 2020i are locked to write in ExtRom and other (as mine) have also Storage locked in write.*
Pls Help us

Actually, there ARE tools to unlock XDA IIi, there are few doing unlock for XDA IIi on eBay, and this website: http://www.mobile2mobile.net/unlock/RemoteunlockingHTCPocketPC_Instructions.htm also handles it. Its just that this kind of tools will not be easily released to us from the underground, other wise, who will they gain profit from?
Guess we have to either wait or pay if you are really in a hurry

Very interresting, but it's not a subject.
A specail forum about unlock already exist and don't confusion betwen unlock (SIM provider) and Unlock Extended ROM. Is this last subject for we ask help to develloper

Leonzhou, we're talking about unlocking the extended ROM, not about removing the SIM lock!

sorry guys, just ignore my stupid comments, just realise it's extrom lock not simlock

thanks anyway!
come on!!!

2.21 IPL/SPL observation

Dear All,
I would like to share a bit more information on what I found regarding 2.21 IPL/SPL behaviour.
1. Now it is impossible to backup the rom from another machine with pre-2.21 ROM and then try to flash it into the machine by SD Card (i.e. use console mode to connect to the pre-2.21 ROM machine, execute r2sd, then push the SD card to the 2.21 machine w/o CID unlock and boot into flash mode (camera button), it will say 'Not allow update' in the status bar)
2. Now it is also impossible to backup the rom from 2.21 machine using console mode (i.e. r2sd), thus I got no way to extract 2.21 IPL/SPL from my machine. Again this is assumed the machine is not CID unlocked. Machine will say 'not enough security level blah blah....'
3. So what I want to know is- If a machine which is pre-CID unlocked, upgraded to ship rom 2.21+
a. is that still possible to dump the firmware out with r2sd?
b. Also will it accept rom flash in SD card dumped out from other pre 2.21 machine?
Hope we could sort out a solution to free all 2.21+ guys

Someone says its also related to the G3/G4 chip (version # 2.21.0001 means G4, .0000 means G3??) I have no clue on what is that though- anyone can provide us some enlightment?

William Yeung said:
Someone says its also related to the G3/G4 chip (version # 2.21.0001 means G4, .0000 means G3??) I have no clue on what is that though- anyone can provide us some enlightment?
Click to expand...
Click to collapse
No, they are just the software version and dont have any relation with the Chip.

Result from JAFWM
Open nk.nbf file with JAFWM v2.2 (Dopod Official Rom)
here is the result.

William Yeung said:
Dear All,
I would like to share a bit more information on what I found regarding 2.21 IPL/SPL behaviour.
1. Now it is impossible to backup the rom from another machine with pre-2.21 ROM and then try to flash it into the machine by SD Card (i.e. use console mode to connect to the pre-2.21 ROM machine, execute r2sd, then push the SD card to the 2.21 machine w/o CID unlock and boot into flash mode (camera button), it will say 'Not allow update' in the status bar)
2. Now it is also impossible to backup the rom from 2.21 machine using console mode (i.e. r2sd), thus I got no way to extract 2.21 IPL/SPL from my machine. Again this is assumed the machine is not CID unlocked. Machine will say 'not enough security level blah blah....'
3. So what I want to know is- If a machine which is pre-CID unlocked, upgraded to ship rom 2.21+
a. is that still possible to dump the firmware out with r2sd?
b. Also will it accept rom flash in SD card dumped out from other pre 2.21 machine?
Hope we could sort out a solution to free all 2.21+ guys
Click to expand...
Click to collapse
the anser to your question on point 3.a is yes.done it myself.now reflashing your device with another ones dump it may cause problems because it also flashes back the cid [whatever state it is] and since every device has a unique cid code that is related to the imei it may cause problems like the dreaded DATA CRASH one,but in other hand it could work.u just have to try to find out.if you need a unlocked dump let me know a got one ready to install.

How about the bootloader mode test result? anyone could provide?

Well I think there is a way and may be summitter can tell better.
one use typhoon nbf tools and remove the CID and save the nk.nbf and flash it to device.
secondly dump the rom parts with typho5 and just make a custom ROM with the same IPL/SPL with a new CE ROM...
I hope I am correct

That wont work, you have to try it out yourself. The main issue is if you got a machine comes with 2.21.0001+, then r2sd would not work. This is the essential step for any rom dump operation so far.
Typhoon NBF is even worse because since 2.0 (AKU 2) rom its not able to read by Typhoon NBF.
*faria: Is that mean you can still use r2sd to dump your rom even after your machine upgraded to 2.21+ ROM? Then if there is an O2 Mini S with such config updated, dump rom out, use typho5 to rebuild a new ROM without CID, chance is that we could use that to patch the unit with other rom versions.

William Yeung said:
That wont work, you have to try it out yourself. The main issue is if you got a machine comes with 2.21.0001+, then r2sd would not work. This is the essential step for any rom dump operation so far.
Typhoon NBF is even worse because since 2.0 (AKU 2) rom its not able to read by Typhoon NBF.
*faria: Is that mean you can still use r2sd to dump your rom even after your machine upgraded to 2.21+ ROM? Then if there is an O2 Mini S with such config updated, dump rom out, use typho5 to rebuild a new ROM without CID, chance is that we could use that to patch the unit with other rom versions.
Click to expand...
Click to collapse
yes you can still use r2sd in any rom above 2xxxx,but i do not use r2sd for my backups/restores, i use [wizBackup] because it bacups to sd and pc without any conversion required unlike r2sd.
i just made a sd backup of rom 2.23 and restore with out any problems.
rebuilding any rom will not work in a machine cidlocked because when we build the roms it requires the cid field to be blank,if it was that easy any modified rom like [sumiters] would do because all of those roms have the cid field blank when they are converted with nbf connverter.
to be clear about the part of the cid lock that every one is trying to unlock is not in the rom ,it is in the machine in a diferent adress [place if you like] itself so until someone cracks the cid area of the new roms there not much you can do.the problem is noone has the tools for the new roms to bypass cid.
the lokiwiz tool patches the cid area of the device only it doe nothing to yor rom.
so if you try to install a patched rom the machine will compare the cid code in the rom with the one in the machine if it does not match it does not install.1 way arround it to buid you own rom and put the machine cid code on the rom ,the it will install .but that means u cannot create a universal rom, it has to be 1 rom per singe machine with matching cid number.
and yes u can use typho5 to decode/incode 2.xxx roms with any problems,i have been using it i my roms without problems.

Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:

raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.

summiter said:
raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.
Click to expand...
Click to collapse
I am reading this forum and i learned a lot from it. This is the reason i donate and will continue to donate as long as this forum is helpfull because the guys are handling this forum simply deserve it, webspace cost money, traffic costs money and they also spend a lot of time for the mainatance of the forum, time is money. This is my contribution sofar.
On other way, i am not a lover of freeware. My devices costs money because i also spend my time developing it, and i also have a company with 30 employees and i am responsable every moth at 30 to pay them their salary and assure them the salary for their next month. Also my partner is dealing with phones, do you not think i would be very sad when i see that our competition unlocking/debranding phones with OUR FREE SOFTWARE ?
All i want to say, i am willing share information, but i am not willing share any information regarding unlocking/debranding since it will affect my own buiness.

raskal said:
summiter said:
raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.
Click to expand...
Click to collapse
I am reading this forum and i learned a lot from it. This is the reason i donate and will continue to donate as long as this forum is helpfull because the guys are handling this forum simply deserve it, webspace cost money, traffic costs money and they also spend a lot of time for the mainatance of the forum, time is money. This is my contribution sofar.
On other way, i am not a lover of freeware. My devices costs money because i also spend my time developing it, and i also have a company with 30 employees and i am responsable every moth at 30 to pay them their salary and assure them the salary for their next month. Also my partner is dealing with phones, do you not think i would be very sad when i see that our competition unlocking/debranding phones with OUR FREE SOFTWARE ?
All i want to say, i am willing share information, but i am not willing share any information regarding unlocking/debranding since it will affect my own buiness.
Click to expand...
Click to collapse
I'm pretty sure that nowhere in my message was there a request for free software.
We'll continue our efforts here as a community to share ideas and create working and free solutions for all.
Quick question - does your ROM collection include any of the custom ROMs created by and for folks here on xda-dev?

well, at least he donates a fair bit to the site... machinagod!! When can we see Lokiwiz 3.x with CID Unlocking!!?

i guess if machinegod and others, did not post is tools and info here,some companys would have a dent in their revenue. and then one would think....
why do i bother?!!!!

hjkl;' why no delete?

To our gurus (DES, Olipro, lvsw, mun_rus, ...): Help me get started on ROM cooking

Hello,
I may be new to this scene but I am very interested in being a helpful member of this community. Specifically, I would like to make a german GPS-enabled ROM from a romdump.
I found a lot of very usefull information on this board and the wiki. However I'm a little afraid to brick my little P3600 in the process.
So here are my questions to the XDA-Developer gurus:
1) Any suggestions on what NOT to do, i.e. which actions can potentially brick a device
2) Can I take any safety precautions that make the ROM cooking life easier or safer?
3) Could one of you help me by chat (IRC, ICQ, MSN, Skype) in case I have some specific issues?
4) Any other comments, interesting howtos or must-reads?
Thanks in advance, I hope I'll be able to pull this off.
PS: Also if someone with a german GPS-enabled ROM reads this, please contact me! I need a romdump first

ZakMcRofl said:
1) Any suggestions on what NOT to do, i.e. which actions can potentially brick a device
Click to expand...
Click to collapse
1) Use aChefs utils 2.0 only.
2) Don't forget to check your ouput OS.nb file with OCchecker by Olipro
3) You should have SPL 1.01 MFG, coz if your device doesn't boot you wont be able to use sspl for downgrade.
4) Read more about bootloader commands
5) Don't use special tytn's tools for rom coocking, coz there is some difference. You have big risk to brick your device if you flash it.
6) You need some resource editor tool and you should know how to sign the ouput files
7) You do all at your own risk

Thanks mun_rus that is very helpful.
Concerning 5): I intend to follow these tutorials:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoReconstruct
As far as I can tell all those tools are not TYTN-specific, right?
By the way, I think its great that you give "newbie"-cooks a chance. Maybe I'll soon be able to return something to this great community!

Concerning 5): I intend to follow these tutorials:
Click to expand...
Click to collapse
Use aChef tools for creating dump and reconstructing a rom) it's more easier

If by "aChef Tools" you mean this: http://forum.xda-developers.com/showthread.php?t=294364&highlight=achef
I don't see any mention of a dumping tool. Maybe i used the term cooking wrong: I want to produce a flashable ROM from a ROM dump that somebody else will do.
In my mind the steps should be:
1) Dump german GPS ROM
2) Extract all files from part02.raw
3) Reconstruct os using any proper tool (you recommend aChef)
4) Check os.nb with OCchecker
5) Flash os.nb to my Trinity (install Hard-SPL first)
6) Flash radio ROM with GPS support to my Trinity (actually its already on there
7) Enjoy german GPS rom
8) Make it easy for others to flash, maybe package of OS and radio ROM.
Any corrections?

Spl 1.01 Mfg
mun_rus said:
...You should have SPL 1.01 MFG, coz if your device doesn't boot you wont be able to use sspl for downgrade...
Click to expand...
Click to collapse
mun_rus, where can we download this bootloader version? I am in desperate need of it.
Thank you!

prsnow said:
mun_rus, where can we download this bootloader version? I am in desperate need of it.
Thank you!
Click to expand...
Click to collapse
Ive got this bootloader when i unlocked my phone with imeicheck unlocker. I don't know where you can download it.

mun_rus said:
Ive got this bootloader when i unlocked my phone with imeicheck unlocker. I don't know where you can download it.
Click to expand...
Click to collapse
But you won't dump it and post it here, will you?

FL_IOCTL_BDTL_HW_PROTECTION - Need help unlocking ExtROM

Hello.
I want to upgrade my device to WM6 and need to unlock the ExtROM for merging the ExtROM and storage to one big storage.
I run the "unhide" command and can see the ExtROM, but writing and deleting is not allowed.
When I execute "unlock" or "unlockextrom -unlock -xda3" I always get the following errors:
ERROR:
FL_IOCTL_BDTL_HW_PROTECTION
A device attached to the system is not functioning
Since two days I google for a solution and found out that many people seem to have exactly the same problem - but there is currently no way!
Is it perhaps possible that the password for unlocking the ExtROM has changed? How can I find it out?
I tried it with the latest offical ROM (1.42) and now downgraded to 1.22 - always the same error.
Hmm, it's strange because the official tool (T-Mobile Germany) can write to ExtROM, so there must be a way to unlock it.
When I try to format the ExtROM, I get the error:
FL_IOCTL_FORMAT_PHYSICAL_DRIVE; of course because the ExtROM is still locked.
I am surprised to see that it is possible develop and provide upgrades to WM6 for Blue Angel - but nobody knows what is wrong with the ExtROM.
Thanks in advance for good ideas.
Best regards,
Ace of Aces

So, I have same problem. Nobody knows how to way out ?

are you sure that you didn't miss the step in the wiki?

Any progress for it?

@Ace_of_Aces
which wiki page did u get the info on how to do unlock EXTROM from? i've done this ages ago. cant remember anymore.

I had the same problem and this one solved it...
[http://www.ziddu.com/download/2371710/Unlocker.rar.html]
...cheers!

Mass Flash

Evenin' all.
Might be a long shot, and I think I walready know the answer but thought I would just double check quickly.
I have about 100 HTC TyTnII phones that are on windows mobile 6.1 and need be downgraded to windows mobile 6.0 due to incompatible software.
Each day i am also having to do the same with a small handful of other TyTnII phones.
I have flashed a load of them with no problems using USB. Yesterday i tried to use an SD card which also worked fine on a test phone that we use for development, but it wont work on phones arriving direct from the factory.
Im pretty certain that its because i ened to unlock the CID (???) or flash the SPL (???) but this is time consuming and tedious.
Is there anyway of doing this part using an SD card? If not, what is the fastest way to do it on the road or on site when i dont have access to my computer?
Any ideas that you can bounce at me would be appreciated, and also it would be a good help if you can verify if what i have said is correct.
Cheers guys.
-AJ

Moved as not ROM Development.
As long as you use the original carrier ROM then CID won't be an issue.

Sorry about posting in the wrong place, was searching the forum for an answer and see a post in this area regarding a similar issue.
When you say original carrier ROM, do you meant the extaxt same rom that came with the phone, or a ROM from the same network provider ect?
They are English Orange WM6.1, so would I need any other English Orange WM6.0 rom? Or am i (probably) mistaken?

Your correct CID checks the vendor ID so you have Orange WM6.1 you will want Orange WM6 ROM as then vendor ID matches.
The other option is to just hard-spl them all wouldn't take long with laptop 5 mins each then you can bypass vendor ID check. "may be easier as don't know if Orange WM6 easily available?"

Would I be able to use WinRar to extract the NBH file from here and use that to flash the phone via SD Card without modifying or touching anything else on the phone?
RUU_Kaiser_ORANGE_UK_1.81.61.2_radio_sign_22.45.88.07_1.27.12.29R_Ship.exe

Just wondering if anyone has got any more info on this?

avisonjohn said:
Just wondering if anyone has got any more info on this?
Click to expand...
Click to collapse
Well if they branded Orange it will work, lol you got so many i thought you would have tried it by now