Related
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!!!
Hi,everyone.
I tried to upgrade my XDAIIs to WM5.but met "FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed"when I tried to resize the EXT_ROM.
I've done a hard reset and install the ext_rom files as a standard procedure.Then install xda-developers_Unlocker.CAB.
I tapped unhide then did a soft_reset,'unlock' then soft_reset.So I did see the ext_rom as well as copying/deleting files in it.
But when I used the DOC repartitioning tool with default value'128kb',I received the error "FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed"
I've tried several times,still doesnt work...
ROM:1.42.00 WWE
Radio:1.13.00
EXTROM version:1.42.119 WWE
Any help will be great.Thanks for advance. :x
me too!
I had this same error on an sx66. I have 2 of them one of them gave this error and I couldnt upgrade, the other worked fine and it's upgraded to wizard v2a now and doing great. Any ideas on what this error means or how to get around it and reformat the ext rom?????
Me too
Got exactly the same issue,,, At least i have installed wm5 without reformating the rom but I'd like to find why mine BA is doing that instead of the one of a friend, exactly the same origin... For my friends it works at the first time....
Hiya
I was searching XDA-DEVELOPERS website about 2 days to find a solution for this problem, I have an I-mate PDA2K, i used all EXTROM tools on this website like this:
1- Installed EXTROM_tools,
2- run UNHIDE ,
3- then run UNHIDE,
4- Soft Reset,
5- now i can see Extended_ROM on my file explorer, i can read it , and able to write on it ... copy paste ...
6- run REPART_DOC.exe on my device,
7- tried many sizes like 128kb, 1024, 2048, 512, 61000, .................
but on this step i always get the god damned FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed,
i finally used Task 28 under MTTY but nothing happened, still have this problem,
No Wayyyyyy ! No wayyyyyyyyyy to repart my DOC size, .... noooooooooooo wayyyyyyyyyyyyyyyy
anyone going to help me plzzzzzzzzzzz ?
I second that request. I've got exactly the same problem, however with a genuine Qtek 9090. After unhiding and unlocking, I can delete all the contents of Storage and ExtROM. In fact, both are empty now. However, any attempt to use the partitioning tool only results in that %&$§/%(/ error message.
I've tried nearly any wm 2003 firmware since someone mentioned he succeeded by using an old pda2k firmware - still the same result. I've even changed the name of the Storage FS driver in the registry - no success either.
I'd be happy to provide some debug information or the like.
PLEASE HELP!
you need a language specific tool
z.b. in the german version programm files are called programme, but the link show on the englisch programm files.
hear is the german one:
wmvfan said:
you need a language specific tool
Click to expand...
Click to collapse
My ExtROM _is_ unlocked. I did write that I was able to delete all its content. So it's quite pointless to talk about localized unlockers.
Reasonable comments, anyone?
There is I believe a way to do this through MTTY. At least get everything back to normal before running the resizer tool. (A way to bring DOC chip to factory formating) Its probably corruption of the DOC. I remember doing this on the Universal, I just don't remember any of that right now. Do an all device search for MTTY and DOC for a possible solution and verify it with some of the hardware gurus first before attempting.
Well, what I did is that
set 14 0
task 28
task 0
sequence which cleared the ExtROM and corrupted the boot screens (there are white stripes across it now), but had no effect on the DOC_repart error message.
I'd really appreciate some investigation from the gurus here since the problem exists for several years(!) now without any solution.
guys...
try this...
downgrade to wm2003
unlock/unhide/repart your doc first to your liking.
then upgrade to wm5 or wm6.
downgrade to wm2003
unlock/unhide/repart your doc first to your liking.
then upgrade to wm5 or wm6.
Click to expand...
Click to collapse
I'm sorry to sound harsh, but: Is it really that difficult to read? I said that
I've tried nearly any wm 2003 firmware since someone mentioned he succeeded by using an old pda2k firmware
Click to expand...
Click to collapse
and
After unhiding and unlocking, I can delete all the contents of Storage and ExtROM. In fact, both are empty now.
Click to expand...
Click to collapse
So once again for the slow-minded: Me and my previous speakers did try this under (in fact several different) wm 2003, not wm5 or wm6. There is no ExtROM accessible in wm5 or wm6.
Again sorry, this time for repeating:
Reasonable comments, anyone?
landmark said:
I'm sorry to sound harsh, but: Is it really that difficult to read? I said that and
So once again for the slow-minded: Me and my previous speakers did try this under (in fact several different) wm 2003, not wm5 or wm6. There is no ExtROM accessible in wm5 or wm6.
Again sorry, this time for repeating:
Reasonable comments, anyone?
Click to expand...
Click to collapse
---------------
@Mods
(I hate to reply to this but i have to about questioning my reading skills)
---------------
Actually IF you tried it right for the first time you can never go wrong.
in WM2003
1. UNHIDE
2. UNLOCK
3. FORMAT_DOC set it to the smallest size
Because technically and sensibly:
You cannot unlock a hidden partition
You cannot format/resize a locked partition
That's as plain as it could ever be.
My 3-LINER INSTRUCTION is sufficient to solve your problem.
MTTY doesnt have to enter the scene it's only used if you have a broken mail button.
You(Generalizing) never said exactly where and what OS is you(Generalizing) are doing. Such WHINING deserves my straightforward answer.
So we give instructions, as we are given the problem.
What's not reasonable from what i've said?
Even a 5th grader can do instructions.
(now that's harsh)
FYI
There IS and WILL BE an Extrom in and WM5/WM6 even if you have changed it in WM2003. It's part of the BA.
You just cant see it and it's not being utilized. it's a Disk_On_Chip. if you managed to know MTTY.
You SHOULD know that.
ROLLBACK to 2003se then do everything right. Otherwise, read the WIKI.
and if you're sure you're doing everything right then you might have a faulty hardware.
nuff said.
-----------------------------------------
me said:
Me and my previous speakers did try this under (in fact several different) wm 2003, not wm5 or wm6.
Click to expand...
Click to collapse
SilverSamurai said:
ROLLBACK to 2003se then do everything right. Otherwise, read the WIKI.
Click to expand...
Click to collapse
me said:
There is no ExtROM accessible in wm5 or wm6.
Click to expand...
Click to collapse
SilverSamurai said:
There IS and WILL BE an Extrom in and WM5/WM6 (...) You just cant see it and it's not being utilized.
Click to expand...
Click to collapse
Sorry to tell it that straight, but if your answer isn't due to a failure of reading, it has to be due to a failure of understanding.
Reasonable comments, anyone?
straight? duh! it's crooked.
i guess you know logic... the flow of it, then analyze this.
hello...
im NOT the one who has the problem here...
AND you are NOT the ONLY ONE who got that problems here.
your quote above this is in response to my post, is actually a RETALIATION.
BUT PLEASE UNDERSTAND that my post's subject WERE the posts before
if its hard to comprehend then let the readers decide.
and regarding the extrom. i can access the DOC via MTTY with WM6.
which makes you wrong and im correct. nuff about that.
1. Nobody said factually and specifically that they tried it with WM2003 at one time (In General),
2. You've got a problem then im helping,
(i actually helped someone with my post and pmed me via yahoo... 3 persons)
3. I've helped... you berrated.
4. Not a good member, actually not constructive.
you wont get any reasonable answers if you yourself aint being reasonable.
actually i was the only one who posted some help for you,
and that is how you react.
ahaha... i hope the mods are reading this.
i gladly like to hear their reasonable comments and close this thread.
This thread is to investigate a software failure which circumstances are accurately described, not to please your ego. Your past contributions were useless since you didn't pay attention to the specifications given.
There's no point in repeating inapplicable phrases, and doing so in spite is not what I call "some help" - it is in fact pure nuisance and puts the problem solving at risk.
Please keep your narcissism out of this thread. Thank you for your understanding.
is this probleme solved??
Maybe you try this:
1. Downgrade to wm2003s
2. copy unhide&unlock (*.cab) to main memory and run it
3. start/program/extrom there we have 4 program ( hide, lock, unhide, unlock) --> run unhide then unlock ---> softreset
4. copy repartDOC (*.exe) to main memory and run it:
- format with 128kb --> you'll have 60Mb storage
- format with 16000kb (recomment) --> you'll have 45Mb storage
6. then Upgrade to wm5.0 or 6.0
7. after upgrade --> do a clean with record+camera+softreset --> no/ yes/ yes
Enjoy
ttrungkien said:
is this probleme solved??
Click to expand...
Click to collapse
Unfortunately, it is not.
ttrungkien said:
4. copy repartDOC (*.exe) to main memory and run it:
Click to expand...
Click to collapse
And that's the point where the mentioned error message occurs.
Some fellow posters and me tried some dozens of different wm2003(se) versions on their Blue Angels, ran virtually any unhide/unlock tools available here, cleared their ExtROM and Storage areas to the very last bit, even tampered with the bootloader accessible via MTTY to get things in order.
To me, it's out of the question that most of the posters who've reported that error could be to simpleminded to follow the few instructions. It appears that there are some devices which have to be either different by hardware or by software that can't be repartitioned by the published tool.
However it's a fact that the Blue Angel is an outdated device these days and I fear that the dev gurus won't pay attention anymore.
landmark said:
And that's the point where the mentioned error message occurs.
Click to expand...
Click to collapse
I was in this trouble 2 days ago! because i didn't go to Start/Program/extrom/ unhide then unlock then SR, before fomart the extrom!
I was in this trouble 2 days ago! because i didn't go to Start/Program/extrom/ unhide then unlock then SR, before fomart the extrom!
Click to expand...
Click to collapse
Ah. Fine. Thanks for your story.
WE DID USE WM2003SE
WE DID UNHIDE AND UNLOCK
(I even told you that we deleted all content of ExtROM and Storage)
We're NOT to crackbrained to follow some simple instructions. because of that...
PLEASE EVERYONE
STOP SUGGESTING
1) to rollback to WM2003SE
2) to use the unhide/unlock tool properly
WE DID!
*sniff* Maybe me posts are in caucasian or so and I'm the only one who sees them as english...
landmark said:
Ah. Fine. Thanks for your story.
WE DID USE WM2003SE
WE DID UNHIDE AND UNLOCK
(I even told you that we deleted all content of ExtROM and Storage)
We're NOT to crackbrained to follow some simple instructions. because of that...
PLEASE EVERYONE
STOP SUGGESTING
1) to rollback to WM2003SE
2) to use the unhide/unlock tool properly
WE DID!
*sniff* Maybe me posts are in caucasian or so and I'm the only one who sees them as english...
Click to expand...
Click to collapse
u found a solution for this ?! i've the same problem, and everybody give me this suggestion !!!
i cannot format my extrom too what's the problem ?>
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?
From what i've read in the Hermes section this tool sometimes works sometimes it doesn't , that might depend on the users expertise and on the device and the rom .
In the Trinity section I have't read about anyone getting the patcher to work yet , and as Oli has admitted he hasn't got a Trinity I suppose that getting our opinion and feedback might help him in perfecting it.
Personally I've tried it and haven't managed to get it to work yet even though I got the success message.
It might be that all that remains is to find a way to unhide the ExtRom as all the old methods including the Hermes cabs and registry changes seem not to work after the patch has been applied.
sammis said:
From what i've read in the Hermes section this tool sometimes works sometimes it doesn't , that might depend on the users expertise and on the device and the rom .
In the Trinity section I have't read about anyone getting the patcher to work yet , and as Oli has admitted he hasn't got a Trinity I suppose that getting our opinion and feedback might help him in perfecting it.
Personally I've tried it and haven't managed to get it to work yet even though I got the success message.
It might be that all that remains is to find a way to unhide the ExtRom as all the old methods including the Hermes cabs and registry changes seem not to work after the patch has been applied.
Click to expand...
Click to collapse
put it like this;
once someone has a mounted ExtROM and they use my patch and find that they can look at their ExtROM but not write it; I'll know it doesn't work, but till then, I can say it probably does work
Mine doesn't work. I've followed every step (Security Configuration Manager) and I also check the Hermes section. But I still can't see extrom after patch.
----------------
Rom 1.23.751.6
GSM 1.38.00.11
extrom 1.23.751.106
i appreciate olipro´s work for the community, but his patch did not work on my trinity.
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!