(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks
yes you can flash the rom but your phone may not work after that
Well the goal is to have a working phone after the flash
So I won't be able to from from GSM to CDMA then I take it?
uhh no he just answered your question. it may flash but wont work. its like saying can u put diesel into a Corvette- sure, will it run- no.
Doh, so I guess it's no use trying it then if you are pretty sure it will brick the phone.
A Good Question
MrTek said:
(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks
Click to expand...
Click to collapse
I believe that the trouble lies within the hardware of a device.
Unlike PCs that have the ability to run multiple OSs phones may not share parts that, given the right instructions, allow them to work on different infrastructures (e.g., CDMA and GSM).
I've not looked into this fully but know that certain chip sets on board a device are compatible only with that type of network.
While a PC/Notebook owner can freely choose his or her ISP it is more difficult, in the Cell Phone industry, than just simply swapping a Sim Card.
I know that a certain GSM provider is looking into locking certain phones onto their network via hardware; think of the implications.
Somebody may come up with a relatively simple solder-in of a compatible chip set or, perhaps, board swap to make this happen but then the consumer would have to balance the risks, money and effort of this option over purchasing a new phone and hopping over to a preferred service.
If/when standardization trumps the proprietary then your dream comes true; but can you wait?!
To make this work, you would have to:
1. Dump your WM5 ROM.
2. Separate dump into SYS and OEM packages.
3. Extract XIP.
4. Build new XIP with WM6.1 MSXIPKERNEL.
5. Build new IMGFS with new WM6.1 SYS folder.
6. G'Reloc the entire ROM.
7. BuildOS to create a dump.
8. Use Tadzio's tools to create a .bin, then to a .nb file.
9. Flash the .nb file.
This is sure to work, but isn't simple to do. If you're new to ROM cooking in general, you'll have a lot to learn before you can even attempt this. I've been cooking ROMs for 4-months and I still have a lot to learn.
And it will not boot this way, you have to mess a lil with the kernel (nk.exe) of your original rom in order to boot WM6/6.1, but GnatGoSplat is right , you need to recook a WM6.1 rom for your device with your devices OEM drivers and software in order to work. You can not use GSM rom on CDMA device because the drivers are difrend
Hmmm....I wonder if it could be done.
At worst, If I have a bootloader in tact, I should be able to revert back,no?
I already extracted the WM5 ROM, and I extracted the XIP from a Startrek 6.1 rom already.
Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.
Gnat,
Thanks for the help. I am really curious now that you say it can be done.
This is what I have done so far:
I started with the nbh file with WM6.1 from the StarTrek which I grabbed from here: http://forum.xda-developers.com/showthread.php?t=374397
I then used Dutty's NBH tool to decompile the NBH into NB
Then used the extracted OS.NB with nbsplit (nbsplit -sp?) to break apart the payload and extra.
I then tried to use the rommaster tool to extract the XIP, but I always get:
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77422c11, but file lengt
is 0x025a95b0.
I suspect this might be related to the nbsplit -sp parameter?
diffeent providers
Hey, what about using another providers rom on your phone? cuz for the phone I have telus has a 6.1 upgrade, while bell doesnt seem to... would that work by any chance?
thank you for any help (have been trying to find information for ages)
Danial
It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.
GnatGoSplat said:
It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.
Click to expand...
Click to collapse
Is there any forums, or FAQs or anything about doing this?? Bell will not release 6.1, and custom roms do not work....ridiculous that there is no support for this phone at all....
You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.
GnatGoSplat said:
You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.
Click to expand...
Click to collapse
Thx for the link.... but from wat iv read before my phone (HTC S720, HTC Libra) doesnt seem to have a bootloader :S....
the vox does have one, im not too sure if it would work on it or not?
and specifically this phone has no support on any website that i can see :S....
is there any guide or something as to find the SPC lock?
Thx alot by the way, your the first member whos actually replied to me about this
Danial
GnatGoSplat said:
Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.
Click to expand...
Click to collapse
It's time to propose this idea.
The unbrickable ROM. Works regardless of GSM or CDMA, keyboard or no keyboard.
Technologically speaking, why can't this be worked on? Even if it takes 12-18 months, it's worth the effort and time to finally create "The unbrickable ROM".
this is the wrong place for questions,
please refer to the Q&A section
thank you
Related
Hi,
I'm trying to get around the problem of the quiet sound with the AT&T rom, I have another XDA running the latest T-Mo rom and was hoping to mess around with some dll's from the TMo rom to see if I could sort the problem, but the drivers used for the sound are protected somehow in the rom, so it won't let me copy them to my SD card or PC (which means I can't try it on the AT&T rom)
Is there any way of copying these files out ? and then into the AT&T rom ??
Cheers
Neil
see dumprom
No good for me then, I only have Windows Machines here..
Ok, I have thought of a possible work around, but I need someone with the T-Mobile WM2003 Rom (Pref 4.01.16) & Linux/Unix to copy the wavedev.dll & waveapi.dll from the \Windows folder and send them to me so it can try it out..
I'm sure its not only me that this "feature" annoys. it makes Tomtom especially useless on the voice prompt side of things.
Cheers
Neil
?? I don't see the problem, dumprom is a windows tool.
in case you had not found it yet, I added the link to the binary to the wiki page.
Ah right, excellent.
Sorry I assumed it was the same as the makerom tool which states its unix/linux.
-=edit=- I just tried the link on the dumprom wiki page, and get the dreaded 404 error
Thanks
Neil
oeps. a common wiki error, I forgot to '~'-escape the '~' in the url.
Thanks mate, it seems to be working now
I'll have a play about with it when I get home.
Cheers
Neil
Back again :lol:
The dumprom app crashes (tried on two machines) when I try to execute it. I have tried it with various command line configuations but the little windows xp error box pops up saying that the program must be closed
dumprom crash
Hi Swifty
Yeah I got this too - until I realised that I was the problem. I was omitting the myrom.nb1 filename (or whatever you have called yours) from the command line! D'Oh! What is your exact command line that you use?
it is known to be buggy and crash on certain roms.
I am working on an improved version in perl - dumpxip.pl
but it does not extract files stored as 'xip' yet.
:lol:
Silly me I done the same thing as you and omitted the rom file.. thanks
I have now extracted the AT&T and TMobile roms and compared the files, the AT&T's wavedev.dll is larger in size, I think this is where the modifications were made.. but I can't rebuild the TMo version into the AT&T rom because I don't use linux
Hopefully someone can help me out and we will finally have a perfect WM2003 Rom -=edit=- IF it works :lol: :roll:
Cheers
Neil
Carefull!
i fearbthat just swapping in the new dll may not help... it may have other dependancies that also need changing. The interface / entry points may also have changed and you may need a whole slew of other stuff and some other registry settings too. But pls go ahead and try... let us know!
Carefull!
i fearbthat just swapping in the new dll may not help... it may have other dependancies that also need changing. The interface / entry points may also have changed and you may need a whole slew of other stuff and some other registry settings too. But pls go ahead and try... let us know!
Swifty said:
:lol:
Silly me I done the same thing as you and omitted the rom file.. thanks
I have now extracted the AT&T and TMobile roms and compared the files, the AT&T's wavedev.dll is larger in size, I think this is where the modifications were made.. but I can't rebuild the TMo version into the AT&T rom because I don't use linux
Hopefully someone can help me out and we will finally have a perfect WM2003 Rom -=edit=- IF it works :lol: :roll:
Cheers
Neil
Click to expand...
Click to collapse
Neil,
Use CYGWIN it's an excellent "Linux running as a command line in Windows" environment. It's easy to install, start and run commands. It comes up as a DOS box-like interface and Voila! You have Linux, stable, clean and fast, including the ability to build ROMs.
I am going to unlock a MDA compact 3 with the imei-check unlocker and I was wondering if I could help to make a free unlock tool....
So which tools do I need...
Start here, and read the whole thread accurately:
http://forum.xda-developers.com/showthread.php?t=280819
SIMLock
So is this nice little Programm you developed in so many hard steps also capable of unlocking the new HTC Artemis (MDA Compact III)?? I would need to know that before bying such a nice device.
On the Homepage of the IMEI-Check the Artemis is cracked with the exact same programm you can download there, but i don't feel like paying for the Unlock key ^^ I read the whole Thread in the Hermes Forum but the Artemis isn't mentioned there, so i wonder if this C3v1Unlocker will work with this Key Unlock key you posted because this Key is surely computed for a Hermes based device... Answers appreciated And thanks for your Great work!
Samson711 said:
So is this nice little Programm you developed in so many hard steps also capable of unlocking the new HTC Artemis (MDA Compact III)??
Click to expand...
Click to collapse
no, it patches the Hermes radio will not be valid for Artemis... although should be a very similar patch, because both devices are quite the same.
Samson711 said:
i wonder if this C3v1Unlocker will work with this Key Unlock key you posted because this Key is surely computed for a Hermes based device...
Click to expand...
Click to collapse
The "unlock key" is only valid after patching the radio.
Ah, okay, i see. Is anybody already working on a Radio Patch for the Artemis? I imagine, if the Radio is patched, it should be possible to create a similar Program for the Artemis, once someone gets a key for his Artemis IMEI, or am i wrong with that?
I've been investigating about this, it is not correct what I said previously: the patched radio method used in Hermes or Universal will not work on Artemis.
On Artemis (and other OMAP based devices) the SIM & CID lock area is stored encrypted on Disk-on-Chip (DOC), on the first block of binary partition 1 which can be accessed with pdocread.
I guess imei-check reads this area and patches it (probably they have to load a "fake" bootloader in RAM first to get SecLevel=0, as they did with the activesync part of the Hermes unlocker).
I don't have Artemis and can't do much more, but if someone is interested in researching I will be watching this thread and try to help, so feel free to post tech questions here if you are serious about writing a free unlocker for the Artemis.
thagangsta said:
I am going to unlock a MDA compact 3 with the imei-check unlocker and I was wondering if I could help to make a free unlock tool....
So which tools do I need...
Click to expand...
Click to collapse
have you read this tread ? -> http://forum.xda-developers.com/showthread.php?t=274860
I have "reconstruct" what actually that utility do. Actually utility uses ITSME utilities to access phone, but on exactly adresses. First it reads some area form RADIO of the phone to the file. That area is 16K large and contains IMEI.
pdocread.exe -n 1 0x040000 0x4000 -b 0x4000 "pdocread.dat"
After that in temp file pdocread.dat at addresss 0x300C - 0x3013 is stored IMEI. One digit is for some CRC check, I think CRC8 but didn't check at all. So that "IMEI Wizard" changes IMEI in file pdocread.dat, calculates and changes CRC digit, and writes file back to the RADIO of the phone with command:
pdocwrite.exe -n 1 "pdocread.dat" 0x040000 0x4000 -b 0x4000
So simple and working.
When it doesn't work ? It doesn't work on new G4 phones, even WIZARD and PROPHET. It works on the same phones, but with old G3 chipset. And phone MUST be CID unlocked and RAPI enabled. The reason ultility fail to work on new G4 phones is that pdocwrite is not ready yet to work with that phones. I am looking for utility to change IMEI on P3300 (Artemis i think) or S200 (PROPHET) too.
IMEI Change?!
The "older" HTC Devices can all be unlocked without changing the IMEI i think, there has to be a way to unlock this phone without changing the IMEI of the unit. Apart from the unlocking process being illegal already, changing the IMEI of a Celluar Phone is even worse Maybe i got your post wrong and you do not intend to really change the IMEI, i dunno...
Samson711 said:
The "older" HTC Devices can all be unlocked without changing the IMEI i think, there has to be a way to unlock this phone without changing the IMEI of the unit. Apart from the unlocking process being illegal already, changing the IMEI of a Celluar Phone is even worse Maybe i got your post wrong and you do not intend to really change the IMEI, i dunno...
Click to expand...
Click to collapse
I DO intend to change IMEI. Who do you think are ? My mother ? What's next ? To pull my ears ?
Yes, we ALL know consequences from changing IMEI. And we ALL read well-written topic about it >> IMEI changing is going to get you sore!. << Did you ?
And did you know that is some countries you just MUST to change IMEI to use your phone ? I will save your time for searching and point one of hundreds topics about this >> To all TURKISH fellows and others a must read story !!! <<. And because of this I can't upgrade to better phone ... for now.
So .. if you don't offer anything constructive but just criticism - please, go to flame on some other topic. Or better - just shut up.
serious business!
Kircho cool down and tell me something
I may be coming to Turkey early next year (January, maybe). Please confirm that roaming with my current provider for a week is no problem? Or do I have to carry my receipt?
kircho,
Probably you've been confused because the company that sells SIM-Unlocker for the Artemis is called "imei-check", but we were discussing about SIM-Unlock here, not imei-changing.
Haha!
Lol, Kircho... how old are you??
I don't care what you do with you IMEI, believe me, i really don't! All i said is that i would love to have a method to disable SIM Lock without messing around with my units IMEI, thats all.
It was NO CRITICISM of your work, my knowledge with PDAs and Windows Mobile does not suffice to render any code to unlock a device and i am not flaming here. If this thing you figured out works for your device, thats cool and i am glad for you, i just wouldn't do it with my device, thats it...
victoradjei said:
Kircho cool down and tell me something
I may be coming to Turkey early next year (January, maybe). Please confirm that roaming with my current provider for a week is no problem? Or do I have to carry my receipt?
Click to expand...
Click to collapse
There is no problem with roaming. If your SIM card is issued by some forign operator like UK Vodafone or Dutch KPN - you can use any phone in Turkey with such card.
Pof
Do you know of a way to unlock extended rom on Artemis? I tried the wizard unlock. It appeared to work for a while but ultimately it has done strange things. The extended rom seems to be visible but not the files within...after a while even the visibility of extended rom is lost.
Thanks, a.
I again have a Artemis (dutch mda compact 3) and I can test with for 2 days...
Im gonna unlock it with the paid imei check software....
I have tried to enter bootloader but it won't enter...
How can I be helpfull to do make an unlock tool...
@apap: sorry I don't have an Artemis, and I don't know.
@thagangsta:
Have a look at this thread in order to understand how this was done in the Hermes:
Reverse engineering the HERMES imei-check unlocker
The bootloader commands for the Hermes are explained in these wiki pages, someone should start researching Artemis bootloader and put the commands on the wiki, it is very similar to Hermes.
Hermes Bootloader Information
Hermes Radio Bootloader and AT command interpreter
Some hints that may help you:
1. You can run the unlocker as many times as you want, it doesn't matter if you've already unlocked your device, the imei-check unlocker will behave the same.
2. In order for the USB monitor capture to be useful, you need to click on the "COMPLETE" tab and when you have captured it, export it as ANSI TEXT.
3. If the app fails (communication error) you need to create 2 admin users, 1 for running usb monitor and the other for running the unlocker. Use right click, "run as..." and then select the other admin user. You need to repeat this process several times until you can successfully get the log.
4. be careful on what you post here, as imei-check has intelectual property rights on their work. Do not "copy" their solution, but reimplement it in another way.
EHh Pof
Just read the thread for the hermes unlocking. I'm not a complete noob but i'm still stunned by the technical data.
Removed a unformiliar program a week ago called "- -" after canceling a imeicheck upgrade (had no valid .unl file)
Reading "First the imei-check unlocker transfers a CAB file to the device via ActiveSync which installs an application named "- -", which contains at least MIGsoft LTD security certificate (used to sign the NBH file with the bootloader upgrade) and runs some other stuff like this (not completed):"
This must mean the unlockers of the hermes and the artemis work in the same way.
Main Questions are:
Is an unlock for the Artemis using imei-check able to use SuperCID?
Which bootloader can we use that is able to flash all roms?
Which code can we use for unlocking.
Edit
I've found an crack for themida secured files. POF You've stated that the .unl files are themida protected could some people post their unl files.
Could be an easy solution......
Perjan said:
Removed a unformiliar program a week ago called "- -" after canceling a imeicheck upgrade (had no valid .unl file)
Click to expand...
Click to collapse
You can usb-sniff what is transfered over activesync without the need to pay for it, it is done before it requests .unl file. For sniff the rest of the process (which is done in bootloader mode without activesync) you need to pay for the unlocker.
Perjan said:
This must mean the unlockers of the hermes and the artemis work in the same way.
Click to expand...
Click to collapse
Yes, they must be very similar.
Perjan said:
Is an unlock for the Artemis using imei-check able to use SuperCID?
Click to expand...
Click to collapse
Yes, but it's not sticky (will loose it after 1st rom flash after applying unlocker). I have solution for this to make supercid sticky if you reverse the process.
Perjan said:
Which bootloader can we use that is able to flash all roms?
Click to expand...
Click to collapse
Most probably the earliest shipped bootloader version. See to which version of bootloader imei-check unlocker downgrades your device when run with the proper key.
Perjan said:
Which code can we use for unlocking.
Click to expand...
Click to collapse
You will see it when usb-sniffing the unlocker.
Perjan said:
I've found an crack for themida secured files. POF You've stated that the .unl files are themida protected could some people post their unl files.
Click to expand...
Click to collapse
Available cracks for themida are for older versions... this is not the way to go for sure, I also investigated and got nowhere.
About .unl files I don't know... I said exe unlocker file is packed with themida, never looked at .unl myself, I think its pointless because usb-sniffing is easier.
Good luck!
Just used the monitor with the unlocker but i'm not able to understand what it does and don't have a .unl file.
Here is the logfile ftp://xdaupload:[email protected]/Artemis/Mdacompac3_unlock_no_unl_file.ms2
Pof Could you help me further.
ms2 is not useful... export capture in ANSI text format please.
Edit -> Export and Save as type "ANSI Text files".
Well, I posted this in the Hermes forum originally, but I really want people with other devices to find out if this actually works or not;
Basically, this will dump an NBH directly from the source file, meaning that no intermediate file is created, hence making the entire dumping process many times faster than performed by other versions.
Having tested it with Hermes ROM's, I've found it to work fine, but I've no idea if it'll work with other device NBH's (as a special note: if your device takes different addresses for each .NB to the hermes, then you'll end up with a .NB called Unknown - just so you know that's not a fault; send me the correct ID's of the NB files for your device and I'll be able to add them to the app so it can recognise them.
I'm bringing a GUI to this very soon... but could people *please* try it.
You can explain how it works… although it is briefly. GREETINGS
does the same job as NBHExtract... except much faster.
Hi, after some research (German and Spanish ROM from HP, and dumped ROM from spgi), I present you a modest modification of prepare_imgfs which works with the ROMs is it supposed to.
Of course, the dumped ROM from spgi doesn't need it to be correctly extracted since it's a dump (and dumps are not encoded!)
to use it:
prepare_imgfs.exe CEOS.nbf -i (or -ipaqHW69xx)
and then to extract the content (a dump directory will be created):
viewimgfs.exe imgfs_raw_data.bin
Modifications "should" work but I cannot test it (I just did it for pleasure).
Of course: thanks itsme, mamaich and all gurus who share source code.
Modifications: rate=0x10089; step=0x10000; skip=0x89;
and now make_imgfs
USE IT AT YOUR OWN RISK...
make_imgfs.exe YOURROMFILE.nba -i (or -ipaqHW69xx)
Should work (tested by comparing a ROM with a decrypted and re-encrypted ROM => no change).
As addfile/delfile/buildimgfs works only in nosplit mode, the imgfs_removed_data.bin file could be invalid, so keep a safe backup of these data (just in case) and restore it before using make_imgfs. That way, the imgfs_removed_data.bin file will remain as valid as possible (if it's a CRC or sth like that... it could not work).
Try to make a very small modification (like a background image) to see if it works before cooking.
Good luck!
Need more info
Try to explain with more details.
Drahtman
I don't know!
drahtman said:
Try to explain with more details.
Drahtman
Click to expand...
Click to collapse
I don't even have a 6915!
All I know is:
-nobody made it for 6915
-based on a correct imgfs_raw_data.bin + correct imgfs_removed_data.bin + correct ROM (for bootloader and headers), you obtain a valid ROM
now you have to find how to create a correct imgfs_raw_data.bin and a correct imgfs_removed_data.bin. More informations are available on ROM kitchen making guides (all along the threads) and one of the already found methods may work (with small modifications)
I tried to make a buildimgfs, it should work but some things in the source code are obscure to me, and doesn't permit me to validate the tool...
But you can find it by yourself... I made those tools without having the device... you have the device, you could try WITH MASSIVE PRECAUTIONS! read all ROM problem threads to be sure you cleared every possible problems! Reading is the only thing important in such operations... Then try to create a ROM, see if this ROM can be dumped as an official one...
You need to try to use USB Monitor during an upgrade to see if more informations are needed (if we could be sure imgfs_removed_data.bin is useless, it would make the thing easier)
Read, Read, Read!
Many others problems (CID Unlock) seem to have be done, but nobody shares the how to, same for ROM Dump from device...
It's just sad the 6915 community doesn't try to solve their problems by themselves... I mean the community as an ensemble...
bumpity bump
Will Try Soon, And Post Results
I have did this about a 8 months ago, and got some error, my data cable is broke, so once my new one gets in I will post the results
This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.
Backup Everything
Please man, If you want me to port a rom, I still need this with the errors,
mdelleman said:
This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.
Click to expand...
Click to collapse
I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.
mdelleman said:
I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.
Click to expand...
Click to collapse
Try this one also, post that, in the meantime I will work with your awizard os backup.
Hi there,
I've looked for information about this topic and I get this explanation:
IF you have a patched nk.exe then make sure the rilphone from the new radio is named rilphone2.dll, copy it into the windows folder of your device, edit the registry with your favorite reg editor go to HKLM/Drivers/BiultIn/RIL edit the Dll key and change it from rilphone to rilphone2
Click to expand...
Click to collapse
After that I have downloaded the Rilphone.dll for 2.07 version, which is the radio I have installed know, and I followed the instructions but after soft reset, the phone doesn't work.
Could someone explain, step by step, how I can change the rilphone?
Thanks in advantage.
I dont know where u got that info but:
*-How can I install a new rilphone.dll to my already installed ROM?
* You can make a CAB or use Resco Explorer... However, it has to be put in \Windows\ directory (and, of course, you need to reboot after the installation!)
from here ... end of first post
http://forum.xda-developers.com/showthread.php?t=611787
Yes, I found this information too but I don't know how to make a cab and the only way I have to change the rilphone it is by using the Resco software and this is the way I followed with the commented result.
The rilphone.dlls are operator specific so first of all you have to know that the one that you are wishing to use is indeed the one that will work!!!
After you flash a chosen radio, if it works then there really is no need to tamper with it any further.
If it doesn't then it could well be the rilphone file that has upset , or that could improve things, so be careful.
A US rilphone, (and who knows where they come from?) may have no beneficial effect on a UK radio and vice versa!
Try the radios with whatever you have already (a stock radio could improve with an "in the wild" rilphone variant), but, there's no guarantee.
Remember rilphone files are not ROM or radio dependant, they are operator dependant so logic dictates that a rilphone extracted from a specific operator ROM should "enable" that operators access protocols and could be the one to use with any later radio flash.
Horses for courses!
Thanks pa49.